@a_greenberg @gwern I'm not seeing this key on the keyserver. I do see a key associated with satoshin@vistomail, but it's not the same
-
-
En réponse à @sarahjeong
@sarahjeong@a_greenberg Not sure I follow? The entropy.html key 0F7BD4AD is right there on the keyserver: https://pgp.mit.edu/pks/lookup?search=0x0F7BD4AD&op=index …1 réponse 0 Retweet 2 j'aime -
En réponse à @gwern
@gwern@a_greenberg i must be looking at an archived version that pre-dates his changed post, then.1 réponse 0 Retweet 1 j'aime -
En réponse à @sarahjeong
@gwern@a_greenberg although actually, scratch that. that makes no sense.1 réponse 0 Retweet 0 j'aime -
En réponse à @sarahjeong
@gwern@a_greenberg this is what I'm looking at on archive.ispic.twitter.com/Iyw0b2fIQT
1 réponse 1 Retweet 1 j'aime -
En réponse à @sarahjeong
@sarahjeong@gwern@a_greenberg wait, is that from the blog post? That version of SKS came out in 2014. (h/t@alfiedotwtf)2 réponses 0 Retweet 2 j'aime -
En réponse à @AsherLangton
@AsherLangton@sarahjeong@gwern@a_greenberg nah, confirmed my own key from 2005 has the same SKS version of 1.1.5 https://pgp.mit.edu/pks/lookup?op=get&search=0x0B5E91BC8A197DC9 …3 réponses 0 Retweet 1 j'aime -
En réponse à @alfiedotwtf
@alfiedotwtf@sarahjeong@gwern@a_greenberg but the blog entry was supposed to be from 2008?1 réponse 0 Retweet 1 j'aime -
En réponse à @AsherLangton
@AsherLangton@sarahjeong@gwern@a_greenberg nice pickup! I think we can call it a day2 réponses 0 Retweet 0 j'aime -
En réponse à @alfiedotwtf
@alfiedotwtf@AsherLangton@sarahjeong@gwern@a_greenberg To be clear: archived post labelled as from 2008 refers to SKS version from 2015?1 réponse 0 Retweet 1 j'aime
@topynate @alfiedotwtf @AsherLangton @gwern @a_greenberg this one wasn't the post that they were referring to, either. it was changed.
-
-
En réponse à @sarahjeong
@sarahjeong@topynate@alfiedotwtf I'm honestly baffled why this is thought to be anything other than a hoax. ¯\_(ツ)_/¯1 réponse 0 Retweet 2 j'aime - 1 réponse de plus
Nouvelle conversation -
Le chargement semble prendre du temps.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.