Comment by nasso_dev
6 hours ago
"being on tangled" really just means "publishing sh.tangled.* atproto records"
the beauty of atproto means that you are in no way tied to the VC funded company behind the web app available at tangled.org. you merely publish your git repository using a protocol that this app will pick up and present with a nice UI
any other app that speaks atproto and looks at those same sh.tangled.* records will be able to access everything in the same way
and even the git repository itself doesn't need to be hosted by tangled the company, you can host your repository yourself. all you need is a server that can speak git, ssh, http and websocket
> the beauty of atproto means that you are in no way tied to the VC funded company behind the web app
This is false: you’re tied to both tangled (unless you want to self host a forge, which if you did you wouldn’t have picked tabgled) and Bluesky for your login to keep working (unless you want to self host a complex constellation of social media components).
> you’re tied to both tangled (unless you want to self host a forge, which if you did you wouldn’t have picked tabgled)
this is true today only because nobody has made an alternative "frontend". but the data is there, public, for anybody to see. they can't take it from you even if they really wanted to. in fact, tangled has been working on making it easier for such third-party "frontends" to exist: https://blog.tangled.org/bobbin/
> and Bluesky for your login to keep working
you seem to be misinformed. "your login" is handled by your PDS, whichever it is. self-hosting a PDS doesn't require you to host anything beyond a sqlite database and a websocket connection. they are easy and very cheap to host, nothing like a "complex constellation of social media components"
today you can already 100% use atproto apps without having any ties whatsoever to bluesky:
- data: non-bluesky-hosted pds (either your own or some other host) for your data
- identity: the did:plc directory is managed by an independent swiss association, but you can even use did:web if you really want to
- relays/apps: blacksky is an example of a fully independent stack
you can selfhost all components of tangled, takes about 200mb of memory and zero disk at the moment (api.tangled.org is completely stateless!): https://blog.tangled.org/bobbin/
Weird, I host exactly one thing (my PDS) and I am not at all tied to Bluesky for my login to keep working. Everything else is already publicly hosted by MANY others.