[keybits]

atproto feels like a move in the right direction for personal publishing that makes content discovery easier withtout the need to post to multiple channels / platforms. https://standard.site/ is one initiative working towards making this a reality.

[iamkonstantin]

I don’t think it does. ATProto is merely “managed storage for apps” by Bluesky and it’s quite opposing to POSSE - You rely on third parties entirely, not just for hosting but also access and moderation to your own content.

What you can and can’t do with your own content is also limited and managed by someone else. The entire premise that you can move your posts history etc, while technically true, is not compatible with the web (e.g. support for things like redirects, canonical urls being handled currently etc is again all outside of your control and a not a goal of Bluesky).

ATProto is in many ways like the custom HTML extensions Microsoft had in Internet Explorer to “make better user experience”.

For me one of the main points of POSSE is resilience. If the VCs behind Bluesky got tired of it tomorrow, all that would die is some links to your website. Your posts and content, RSS subscribers, people who linked or bookmarked your website etc - remain unaffected.

[knowtheory]

I think you're missing the point.

With the IndieWeb version of POSSE, the source of truth is the webpage you control.

For the ATProto version of POSSE, the source of truth is the record in your PDS. That record is interesting because it is both content-addressed and signed with your private key.

Where ever that record is syndicated, the reader (or app displaying the content) should be able to demonstrably verify the authenticity of the record.

And you can host your own PDS entirely independent of Bluesky, there are several interfaces for both reading and publishing Standard.site records:

* Leaflet (https://leaflet.pub/ )

* pckt (https://pckt.blog/ )

* Wordpress (https://github.com/pfefferle/wordpress-atproto )

It's also not that hard to write your own display interface for just your data if you want.

[iamkonstantin]

> the source of truth is the record in your PDS

> content-addressed and signed with your private key

Technically valid but also not required. ATProto works hard to present them as valuable or needed, like added value of sorts but:

- The need for signed content is niche to specific use-cases. Not sure even news outlets need this as long as they control their domain.

- The PDS is a funny contraption of protocols and technologies that are quite complex and probably can't (usefully) exist on their own outside the "atmosphere" ... even if you manage to set one up.

The question would be, why bother with all this complexity and layers when you can self-host your website anyway.

The added value of a PDS/ATProto is to participate in the social cloud of Bluesky. Without it, the entire thing is more of an engineering showcase than a useful tool.

[sph]

ATProto is a great idea that will never go anywhere because of its close association with Bluesky the service, and Bluesky the company, and that's a shame.

[keybits]

atproto has an active IETF Working Group: https://datatracker.ietf.org/wg/atp/about/

[prmoustache]

XMPP had one too.