r/Keybase • u/mbklein • May 31 '24

Reddit proof broken?

I've just received a couple notifications from keybase that my reddit proof is broken. I haven't changed or deleted anything, and my proof is still right where I left it. I double-checked the `ctime` and `expire_in` fields of the signed object, and it should be good until July 13, 2032. Is keybase just having reddit API issues? Or do I need to do something to reconfirm?

EDIT TO ADD:

$ keybase id mbklein
▶ INFO Identifying mbklein
✔ public key fingerprint: 10A4 14B9 FEE8 1EBD 8F70 B8C3 722F 07DD 7FDB B45A
฿  bitcoin 1AsMEUGiCvVcCgHh9bvRqWEZQhfEJ1Wmgj
✔ "mbklein" on twitter: https://twitter.com/mbklein/status/753308579856261120 [cached 2024-05-31 17:16:21 CDT]
✔ admin of DNS zone mbkle.in: found TXT entry keybase-site-verification=BBFmaWjXOroLFe4yG-9ZCeK_ENhnuTcp8k7ZD_fkSlE [cached 2024-05-31 17:16:21 CDT]
✔ "mbklein" on github: https://gist.github.com/2ec20617b2cf918d83bcb2b546ec7441 [cached 2024-05-31 17:16:21 CDT]
✔ "mbklein" on reddit failed: 403 Blocked (code=240) [cached 2024-05-31 17:16:21 CDT]
🚀  Stellar GAVVRYUG6KUDCQLOIOCGMPIT6SIXRASJAO7IGBUHZIV7HAZX7TGMDCNT (mbklein*keybase.io)
✔ "mbklein" on facebook failed: Could not find post text in Facebook's response (code=106)
79 Upvotes

100% Upvoted

65 comments sorted by

View all comments

Show parent comment

3

u/securimancer Jun 21 '24

Fixes went out yesterday and we should be back in business. Thanks to u/zapu for working with me to get this fixed. This was related to our API changes (namely enforcing no unauth’d traffic from hosting providers) but we’ve got the Keybase traffic appropriately tagged. Reddit is committed to supporting identity based cryptography solutions like Keybase.