//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfilePosts









Loading...
the best tokens of my generation are spent thinking about how to, etc, etc
I'm headed to NYC for a few days! roaming around with friends. hit me up if you want to hang, good events, or new things worth checking out (I haven't spent much time there since 2016)
This is massive for the future of un-enshittified Social Media in Europe. Atmosphere ❤️ Fediverse ❤️ Matrix
I sent an email with more context to the WG mailing list, but in short: this iteration is trying to capture what is currently deployed. WG may end up doing small changes to the spec later. a whole lot is out of scope for these docs under current charter: explicitly not getting in to AT-URI or DIDs
if you have done close detail work on repos or firehose, and you notice gaps or errors in these drafts, we'd love to hear! also keep track of small changes you'd like to see as part of the WG process.
💭 Oblivious HTTP is interesting! the stated use cases are anonymous/stateless, and in atproto this could help with client privacy for identity lookups (eg, PLC resolution) but seems like it could also help with pseudonymity? eg PLC op submissions. and even PDS proxying (!)
3d
5d
5d
5d
5d