also it is completely bonkers that @bsky.app requires you to select a "Hosting Provider" on login and i have to remember whatever @eurosky.social's address is. guys, if you want this decentralization thing to happen, it should not suck so much to use! the Bluesky app should just read it from my DID

A discussion I had with @pfrazee.com @bnewbold.net and @dholms.at at the conference that I wanted to dig as a community is a TLD for atproto handles. Lots of challenges, but I think I'm looking forward to a world where I'm @goto (syntactic sugar for goto.handle) on the web rather than @sgo.to

The reason I've become such a @standard.site stan is because it's forming into the first real multi-service parallel ecosystem on atproto that can survive on it's own without the need of the @bsky.app lexicons and infra

Something awesome about Bluesky: 1. I see a post I'd like to load in my agent. 2. "wouldn't it be nice if I could give it the atproto link?" 3. Wait, markdown would be better, let's try renaming the domain to bsky.md on the off-chance… 4. It works 🤯

happy Monday, I wrote up my decision-making around our new endpoints.bsky.app HTTP reference! Thanks everyone for the push to do this 😊

atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935

Bluesky is scared to commit to making a universal app that works with any atproto lexicon. I am not. And am pretty committed to our social-app fork being able to work with more and more content types (short video, fintech, blogs, music, etc.) Acorn customers get this for their communities too.

Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.

@iheartnoise.bandcamp.com how did you set your bluesky handle to match your bandcamp domain? To my understanding, bandcamp manages dns on this end. Did not know you could adapt it for bsky

+1 to this. having tld in our handles is silly and counter-intuitive I am notplants.bsky.social still simply because i dont want to be myname.com unless im doing it as a bit. a tld in your handle lowkey feels like being named after a billboard

atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935

@tynanpurdy.com asked for this feature and I like it: every atproto app should support AT-URIs as top level routes, @pds.ls-style. Makes it super easy to integrate. So this would be an argument for e.g.: `https://bsky.app/at://did:plc:rbvrr34edl5ddpuwcubjiost/app.bsky.feed.post/3micfxauzu22c`

In 2026, @bsky.app is focused on what’s next for open social: bringing together users for conversations around live events, creator and platform monetization, and private state, giving users truly private data while preserving ownership and portability at the protocol level.

Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.

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.