[jauntywundrkind]

Tangled very nicely gets rid of the having to run a server problem, yet still gives you a sovereign platform for doing git from. Truly divine.

The barrier is largely that Tangled is so new. People don't know about it. People don't know what Bsky & the Personal Data Server offer or they haven't been enticed out of the zero energy local minima.

There's some need for more features. For more tangled dev. Ideally for alternate clients, just because. But it's already enormously solid, the early adopters are living the better life, the future is already here and we are just waiting for devs to redistribute themselves appropriately.

[pythonaut_16]

Does Tangled offer any solutions or suggestions for backing up data stored on the Knots?

[icy]

Hi! Knots just serve up git repositories over an XRPC API. The actual state on disk is really just a sqlite + your git bare repositories—the two can be tarballed and moved elsewhere easily!

We will work on more first party backup/migrate solutions though.

[skybrian]

That sounds reasonable, but do your repos get replicated into your PDS? Where else does the data end up?

[icy]

Git repos don't get replicated anywhere. They live on disk, either on our knot server or yours. Knots are essentially our extension to the AT architecture, allowing user ownership of what's essentially "off-protocol data" (git).

[skybrian]

Thanks. What does get replicated?

I'm not sure what I'm looking at, but I see records that look like source code here:

https://ufos.microcosm.blue/collection/?nsid=sh.tangled.stri...

[ItsHarper]

I mean you can self host your own knot if you want, so it's at bare minimum possible to back it up if you're doing that