atproto'd my website a bit further (beyond the @standard.site integration): 1) added a "Right now" box on the homage that pulls in all kinds of atproto activity like @bsky.app posts, @popfeed.social film ratings, @bookhive.buzz reads, @tangled.org repo's etc.

Folks, this isn't some cute side-project where you can just switch out tens of thousands of paying users and force them to use atproto It's a nice idea, but those are the sort of things only possible on new early stage projects

@thisismissem.social @divy.zone and I recently went through an exploration of how the browser can help you login to websites with atproto accounts. We recently presented to the FedID CG and here is a sneak peek in case you couldn't join! This is early but we'd love your input before we go too far!

Want to distribute compute to members of your organization in an ATProto native way? Check out socialweb.computer!

Conversation here is very helpful framing for ATProto builders. The protocol has re-created the opportunity to restore the web as an open curation ecosystem that isn't controlled by any one platform, built not just on links between pages, but on the relationships between people, links and sources.

<atproto-comments> is a web component that allows you to simply drop a thread onto your page and have users read & write comments on your site. all your users need is an ATmosphere account (bluesky, eurosky, their own PDS hosted from their basement) to log in using oauth. atproto.svebcomponents.dev

<atproto-comments> is a web component that allows you to simply drop a thread onto your page and have users read & write comments on your site. all your users need is an ATmosphere account (bluesky, eurosky, their own PDS hosted from their basement) to log in using oauth. atproto.svebcomponents.dev

anyone have tips for building atproto stuff without a backend ? i’d like to make userinput better, currently it can be kinda slow. looking for best practices i may not have thought of.