The "hack" outlined in the article requires knowing the username and password of the person you want to "hack". Of course CSRF tokens don't protect you when your credentials are lost.
1,391 karma · joined October 24, 2009
The "hack" outlined in the article requires knowing the username and password of the person you want to "hack". Of course CSRF tokens don't protect you when your credentials are lost.
That said, the ability to manage sockets sounds very interesting, hopefully simplifying my stack even more (my current use case is in getting the most performance out of a small VPS, so removing things from the stack would hopefully clear up RAM for actual web workers). I've been running a small site using nginx->circus->chaussette->django and it's faster (and was simpler to configure) than my standard nginx->supervisord->uwsgi->django deployment.
Also, supervisord isn't without its issues, and one of them is managing processes at scale (see https://github.com/Supervisor/supervisor/issues/26, that bug is 2 years in the making). Circus at least claims they intend to support thousands (via http://circus.readthedocs.org/en/0.9.2/rationale/) so I'd be interested in seeing what they bring to the table on that front.
Sure, they have their downsides and there are way better solutions that one can envision, and they are light years better than the things they are meant to replace and our world isn't ready yet for the better alternatives.
So when you say "Only if you claim every radio has an average of one listener by this methodology as well", I think you misunderstand the core problem, which is that the article compares stats that aren't equivalent.
The issue is in how these listens are counted. So yes, you can pretty much claim every Pandora device has an average of one listener. Users of Pandora have their own personalized streams, and every time a song is played on a person's stream, it's counted as 1 play, and is heard by 1 person.
In contrast, radio stations have one stream that many many people listen to. When a radio station broadcasts a song once it's counted as 1 play even though that song is received by X radio-receivers and heard by X people (where X is the reach that station has, for example, 150k).
The issue is the article compares plays on Pandora (where each play as counted reaches 1 listener on average) to plays on radio (where each play as counted reaches upwards of 150k listeners).
I'd say the Pandora 1 track per customer is a safe assumption. Sure, I've known cafes and dinner parties where Pandora was streaming to multiple people at once, but I've also known lots of friends who have Pandora playing on their headphones even when their headphones aren't on their heads. Nobody I know who uses Pandora actively pauses it every time they leave their computers, so I expect it washes out in the end.
Secondly, I don't think anyone has claimed that they maintain a deep relationship using FB only. Like I mention in a nearby reply, having the constant superficial connection through FB strengthens the actual time spent together.
It's also worth noting that hiding has improved dramatically since it was first introduced. Now, you have more control over what gets hidden. For example, you can remove a "friend" from your feed but still get notified when they have a major update or life event (e.g. get married, move away). That way, you can get rid of the noise that person creates but not throw out the signal at the same time.
The only thing I miss in bitbucket from the github world are gists.
So you could possibly argue that XML (a la SVG) is the right format to represent the vector files within that container, but it wouldn't be appropriate for the container file itself since binary data really bloats XML.
That's just the nature of things though, it's hard to keep a handle on huge channels unless the channel ops are eternally vigilant. I was in #python some time ago, and there were good moments but there were lots of bad moments.