superpatosainz's comments

superpatosainz | 8 years ago | on: We took a hacker to a public WiFi café (2014)

There was once even an easy to use software that shipped with an attack. It was called Firesheep and it let anyone skillful enough to install a browser extension get into the Facebook and Twitter sessions of anyone who shares the same network.

superpatosainz | 9 years ago | on: The Hard Raise

That's kind of what Socrates did. Not everybody thinks it's acceptable (just look at how well it turned out for him), but it's important to challenge all beliefs.

superpatosainz | 9 years ago | on: Diversity and Inclusion at GitHub

To add (and replying to rco8786): I think this is not racism. Because ethnicity is not race, and almost everybody by now through mestizaje has native blood. The early colonial period might have a racist component with "sistema de castas" (Spaniard born in America = Criollo, Spaniard with Native = Mestizo, Spaniard with African slave = Mulato, so on).

But now race doesn't even matter because we are all almost the same genetically (it just happens that at least in Chile, the fair-haired blue-eyed people are the richest, but hate here is about wealth and politics rather than race itself).

superpatosainz | 9 years ago | on: Diversity and Inclusion at GitHub

Mapuches you mean?

Well, living in Chile, I've learnt that there's no racism here BUT:

-There's classism, a lot. Both from the lower classes to the upper and vice versa. There's also a lot of anger left from the various dictatorships that ruled in the eighties.

-In some countries, here included, there's also big prejudice against native cultures like the Mapuches. "They're all lazy drunkards".

These problems mostly stem from colonial times, where the Spanish didn't respect native culture and since the Europeans were seen as the "civilized, more advanced people", the aristocrats here did everything to imitate their lifestyle.

See also: mestizaje.

superpatosainz | 11 years ago | on: A Richter scale for outages

It's a very interesting concept, because now in 2015 I've seen more and more things using technology and computers where they shouldn't be used. People seem to not understand that the gimmick feature that needs a computer just adds a billion moving parts (one for each transistor, statement of code, etc) that may fail.

I was in the process of buying a new TV and I couldn't find a good ol' TV, nope, all there was "super awesome smart voice commanded can see the weather TVs"... so I bought one intending to just use it for cable (I still used netflix in my computer) and after a whole damn day of updating firmwares and waiting for it to boot (I miss the CRT days)... some capacitors that were in the backlight circuit blew. Thank you very much Samsung. (Btw another clear example of misusing technology was yesterday's post about trains using GPS for "smart door controls")

Oh also, the scale in your post is more of a Mercali than Richter.

superpatosainz | 11 years ago | on: The Magic SysRq key

Well, at least in my Spanish keyboard there are two functions for the SysRq key, as the keycap says:

Impr. Pant. | Pet. Sis. -- which is expanded to --> Imprimir Pantalla | Petición a Sistema -- which translates to --> Prnt Scr | SysRq

So that binding makes the key actually useful for everyday activities.

superpatosainz | 11 years ago | on: One second per second is harder than it sounds

Yes, there is. Just not in the client side, it's server-to-server, and due to the centralised nature of IRC, it's critical.

For example, here's a paragraph from the UnrealIRCd server protocol (http://www.unrealircd.com/files/docs/technical/serverprotoco...):

> Unreal is very time-dependant. Users and channels, for example, are timestamped, and if server clocks are not synchronized properly, things can go very wrong very fast. See http://vulnscan.org/UnrealIrcd/faq/#67 for more information on this. Note that there is a slight difference between server time and what is actually reported by the UNIX date command or by the C time() function.

The other major side of IRC server protocol is the TS6 protocol (You can see it by yourself at http://irc-wiki.org/IRCd_Comparison). TS stands for TimeStamp, and you can see how critical timestamps are at https://github.com/avenj/irc-server-pluggable/blob/master/do... and https://github.com/atheme/charybdis/blob/master/doc/technica.... You can see TS are what control almost everything related to nicks, channels and their properties.

Before the implementation of TimeStamps and Services, it was really easy to abuse netsplits to take over channels and people's nicks.

There's a complete explanation at http://codeidol.com/internet/irc/The-IRC-Protocol/Timestamp-... (and of course, a Wikipedia link: http://en.wikipedia.org/wiki/Internet_Relay_Chat#Timestampin...).

superpatosainz | 11 years ago | on: One second per second is harder than it sounds

IRC: everything is timestamped to the subsecond. Any drifting causes channel takeovers and "random" nick kills, even links fail. Also, since a message from a server is broadcasted across the entire network, one misconfigured server can cause chaos in your hubs or completely unrelated leafs.

Or at least that's how I remember my experience managing an unstable (as in ddosed, every irc service in active development, a few in-house bots, etc) IRC network and having read the IRC and IRCv3 specs and unreal's and TS6 server message specs. If I'm wrong I'm sure someone here could correct me.

page 1