Some personal/protocol news!
Looking forward to helping make PLC the trustworthy and auditable bedrock of identity on atproto.
Catch me, @wseltzer.bsky.social, or @bnewbold.net at #AtmosphereConf if you want to chat!
We’re still getting started but want to be transparent even in the early stages.
Filippo Valsorda
🙏
🙏
🙏
🙏
🙏
Filippo Valsorda
🙏
🙏
🙏
Filippo Valsorda
🙏
🙏
🙏
🙏
Filippo Valsorda
Yep, this looks like it, probably a bug in whatever SDK or library the bots are using, which only breaks their posts when replying to a reply (where root != parent).
Last year, I thought we still had time to design PQ auth systems.
Now, based on the pace of progress and on statements like Google's, I believe
1. we need to finish rolling out PQ kex yesterday
2. we need to start rolling out PQ auth now
3. it's too late to ship any new non-PQ design or system
Filippo Valsorda
I’m giving a lighting talk at 4:30pm in Room 2301 at #AtmosphereConf showing how we can make it easy to add transparency logs to atproto collections!
Developing on atproto might turn out to be the easiest way to deploy a tlog for your data.
It’s also livestreamed ✨
Looking forward to catching everyone on @youandme.at!
I am extremely excited by all the atproto apps, but I am a bit uncomfortable with how many store data in the repo but don't surface in the UX the fact that you can see other users' data.
You and I know that all data is public (for now!), but the average user needs the UX hint or very explicit text.
Filippo Valsorda
Hey #AtmosphereConf, I am flying in tomorrow evening! 🥳
I was going to rest after a week in Taipei, and then @knowtheory.net and @ngerakines.me got me excited about bringing tlogs (as seen in CT, Go's sumdb, Sigsum, Sigstore) to atproto... and now I have a lightning talk on Sunday 😅
Filippo Valsorda
Filippo Valsorda
I’m at #AtmosphereConf, look for me in the teddy bear sweater and say hi!
If you’re not at the conference, consider muting this thread 😅
Here's something weird: this post is the reply.parent of 4 posts, but also the reply.root of 2 of those posts, despite having a different reply.root itself.
pdsls.dev/at://did:plc...
The result is that bsky.app shows 4 as the reply counter, but only shows 2 replies. Any idea how this happened?
