riking

Their converter probably has its own share of vulnerabilities, but the most it could probably do is start executing JS.

Go print a set of backup codes for google! It'll be 10 9-digit numbers, use them when you lose your phone.

With regards to the index - did they consider a partial index on (queue, date_sent, consumed = false) ? So that already-consumed messages aren't in the index.

For an explanation of "RCU grace periods", read "The RCU Api, 2010/2014 Edition":

2010: http://lwn.net/Articles/418853/ 2014: http://lwn.net/Articles/609904/

Or 0x00000001 next pointers, if it's using a hlist_nulls. See http://lwn.net/Articles/609904/

And, if we look at the list of people who were writing it, we see Github, Meteor, Reddit, and StackExchange people (plus JGM and Atwood) as the participants, which I think cover the top 3 sites using Markdown.

And Jeff is using Markdown for his forum project, Discourse, so that's another chunk of users.

This kind of coalition has the power of numbers to standardize on something, which is why this is so exciting.

They're probably trying to spoil the pot for the other people that are trying, by inserting extra private keys someone looking for 'just a private key' will grab one of the pushed ones.