780 karma · joined January 18, 2012
> Twitter is good for two things: engaging with #Brands, and broadcasting messages to whoever wants to read them.
I almost never engage with brands on Twitter.
I do broadcast messages — to anybody who has chosen to follow me and hasn't chosen to unfollow me, both of which are freely done without any social consequences.
On the flip side, I read that which others have broadcast, provided I follow them. And I'm free to shape exactly who's in that set of people, without worrying about circles or unfriending or which IRC channels to sit in.
The author writes about communities, and about moderating IRC channels and making decisions about who can stay and who is banned. Perhaps he prefers to shape and steer communities in a way that Twitter doesn't facilitate.
Personally, the ephemeral and asymmetric nature of the Twitter social graph is the defining feature. The 140 character limit is perhaps just a constraint which helped that feature survive.
The author also mentioned harassment on Twitter. I've never been on the receiving end of it, and I hope I've never been on the other end either. But I believe it's a real problem. I hope there's a solution, but “Twitter going away” isn't that solution.
That's the same situation as USA.
Australia actually briefly had it better than USA, with the AU iTunes store releasing HBO shows like GoT within a day or two of their USA cable release. But then HBO + Foxtel broke that.
Nexus 6: 5.96" 2560×1440 (493 ppi)
The iPhone 6 Plus is comically enormous. This thing is ridiculous. And the same resolution as the current 27" Apple displays.
2.7 GHz quad core vs iPhone's 1.4 GHz dual core (but 32-bit, vs Apple's 64-bit).
That is some serious hardware.
> Disabling SSL 3.0 support, or CBC-mode ciphers with SSL 3.0, is sufficient to mitigate this issue, but presents significant compatibility problems, even today.
No collisions published to the public doesn't mean no collisions have been found.
As the article says; “we should assume that the worst vulnerabilities go undisclosed.”
Github Flavored Markdown means “Gruber's thing, but with some GitHub things added”; and that's what it is.
Standard Markdown means “the main/real/most-widely-used Markdown”; but it's none of those things.
Common Markdown means almost exactly the same thing. If Standard Markdown is not okay, neither is Common Markdown.
Gruber suggested “Strict Markdown” or “Pedantic Markdown”. These names clearly describe how the project differs from Gruber's thing.
This has very little to do with whether the name contains the word “Markdown”. It's about semantics; describing what this thing is. Also, prematurely calling something Standard or Common is a classic mistake.
> His prone figure sprawled on the street for four hours in the unforgiving August sun, with blood on the asphalt—an indignity in sharp contrast with the quick departure of the officer from the scene.
> Police, some outfitted in riot gear, others in military fatigues, barricaded the streets. At least one of them draped a black bandana over his face; others covered their badges.
> One homeowner walked out of his house to find a spent flash grenade on his lawn. An armored truck rolled down the street, a flume of tear gas issuing from the back.
It seems the "6502 risc or cisc" debate was never really solved, as a Google search for that phrase will show.
> 5 years from now [1992 -> 1997] everyone will be running free GNU on their 200 MIPS, 64M SPARCstation-5
> My point is that writing a new operating system that is closely tied to any particular piece of hardware, especially a weird one like the Intel line, is basically wrong.
That's not to detract from the functionality it does offer; just making sure people don't get the wrong idea.
To ease this pain across a large team, I'm considering using netfilter/iptables or a TCP proxy to make the old port available in our VM environment during transition.
https://github.com/dotcloud/docker/commit/5febba93babcf8c4b0...
Nope.