I'm increasingly gaining appreciation for the atproto model of differentiating hosting your own data from hosting your own webview and your own moderation - I don't *want* to host my own Mastodon frontend, but I can't otherwise host my data locally. Equally, tangled lets me keep my git repos and metadata in a format I can migrate without needing to worry about hosting an entire forge myself. This seems closer to what most users interested in data ownership would want?

@mjg59 but the bsky kind of "ownership" is like comically pointless? it's barely better than making local backups? like what's the point of "owning the data" if it doesn't involve owning the actual exchange/communication? Social networks are all about the exchange, not about data at rest

@mjg59 is pdc-to-pdc direct following actually a thing?? i was under the impression that all following happens through a relay.

the docs are kinda opaque, the closest thing in the list of "what a pdc does" is "data synchronisation using repository event streams" which says nothing

@valpackett You do need a relay, but there's already more than one relay out there and they're basically an optimisation detail - I don't think there's anything fundamentally stopping you from having some other pipe between a PDS and a frontend, it just makes it harder to maintain the property of having all information be available.