Comments are about as old and basic as the social web gets, so I assumed ATProto would have them figured out. It doesn’t, not yet. Here is my take on why standard.site deferred comments on pu…
atproto-comments
Renders an AT Protocol (Bluesky) thread as a comment section. Supports SSR, sign-in, replies, and live updates.
Habitat's road to release: 06 commenting - building [at] habitat
Using atproto space inheritance to power comments on our doc editor
Footnotes (@footnotes.social)
Link aggregation and post comments on ATProto. https://tangled.org/@footnotes.social
How to Read an RFC
Requests for Comments (RFCs) are how we specify many protocols on the Internet. These documents are alternatively treated as holy texts by developers who parse them for hidden meanings, then shunned as irrelevant because they can’t be understood. This often leads to frustration and – more significantly – interoperability and security issues. However, with some insight into how they’re constructed and published, it’s a bit easier to understand what you’re looking at.
There's lots I haven't yet understood about atproto, but I simply won't do the standard.site thing whilst it offers a worse UX than… not doing it.
Guido X Jansen
It keeps confusing me that the main call to action in these cards (the button) does NOT go to the article but to the main website Is it just me that finds this weird...? The main visual CTA for a card about an article should go to that article no...?
Thinking about atproto as an identity and data *substrate* of the web. RSS couldn't go all the way because it built within the boundaries of the same-origin paradigm, just like the closed platforms that ended up enclosing most of the web.
P(aul) Frazee
Yeah I'd say RSS was directionally right - it was an underpowered database replication protocol. It just needed to go all the way
Thinking about atproto as an identity and data *substrate* of the web. RSS couldn't go all the way because it built within the boundaries of the same-origin paradigm, just like the closed platforms that ended up enclosing most of the web.
P(aul) Frazee
Yeah I'd say RSS was directionally right - it was an underpowered database replication protocol. It just needed to go all the way
Every post, like, and blog entry on atproto sits in your Personal Data Server (PDS) as structured data you own, which means building experiences that are extremely customized to you has never been easier. atproto + AI is incredibly powerful! #atproto
Atproto Is the Context Window You Own - The Tropopause
pckt.blogInspired by @danielroe.dev I added comments functionality to my portfolio using barebones AT Protocol query. Definitely not necessary, but amazing that it's even possible 😅
<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
atproto.svebcomponents.devConversation 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.
Building Through Every Wave: Mike Mcue on the Internet, Mobile, & AI Eras
www.youtube.com<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
atproto.svebcomponents.dev
