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