| 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. |
> 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.