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 Mastodon isn't the only player in the Fediverse, though?
@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 I’ve been idly browsing documentation for atproto lately and really like what I see, especially with the incoming work to allow private data stores, which seems the big missing piece so far.
@mjg59 what I worry about with the disconnection between storage and usage is the potential proliferation of dead formats. That is, if the webview rots what option do you have to continue interacting with the data stored in your atproto data server? I feel like keeping the two together keeps both more active... Possibly. Might be over thinking it
@mjg59 Why do you need a Mastodon frontend with Mastodon ? Can't you host just the API and use an app of your chosing and never expose the UI?
@penguin42 The webview seems like the lightest part of it? I'd still need postgres and redis and sidekiq and to worry about database migrations and everything.
@nogweii I think that's an interesting question - tangled deals with it by punting the hard part (git, the format they don't control) out of scope due to git already having a story there. But if you can't enforce format migration on people's PDSes (because you don't have any way to touch them) you do likely end up having to care about ancient design decisions.
@valpackett My canonical location never changes. Me moving between different frontends with different moderation policies has zero impact on whoever's following me.
@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.
@jwildeboer Which other implementations implement stuff like "Actually fetch the fucking replies"?