Tangled Blog

> - tangled federates: https://blog.tangled.org/federation People have been talking about federation across forges for a couple of years and seems like its finally at least close to being a real thing!? That's absolutely amazing!!

We already support JJ for stacked PRs, but more native integration is planned. https://blog.tangled.org/stacking

we need to break free from monocultures: https://blog.tangled.org/federation/

Tangled is VC funded and owned by investors, not the community like Codeberg or Forgejo. https://blog.tangled.org/seed/ Avoid.

If you too are wondering their CI story, it is based on NixOS: https://blog.tangled.org/ci/ https://blog.tangled.org/spindle-microvm/

With "spindles", apparently: https://blog.tangled.org/spindle-microvm/

https://blog.tangled.org/seed/ Similar groups to Bluesky (bain capital crypto) and some notable CEOs GitHub's moat is not code hosting, they will need to build out the equivalent of Actions and figure out what private repos look like. Unclear how they intend to IAP with corporate identity systems, I have a hard time seeing ATProto break into that category.

Yep, this is similar to some other version control tools like Tangled which has vouching. https://blog.tangled.org/vouching/

Perhaps humanizing posts like this: https://blog.tangled.org/federation

You don't need to, Jujutsu[1] gives you most of mercurial with some additional stuff. And relevant for this subthread, Tangled appears to work with it[2]. [1] https://docs.jj-vcs.dev/latest/ [2] https://blog.tangled.org/stacking

Learned recently about their support for Jujutsu at JJ Con last week: https://blog.tangled.org/stacking

And then when people put comments on your commits and you force-push new ones, does it link the updated version of each commit to its previous self, giving a clear timeline of comments and changes? I don't think so. But if people write comments at the MR level and you fix them in new commits, then the throughline is clear. I think a workflow like this for atomic commits would be nice. tangled.sh supports it for jujutsu¹, and it looks really neat. But the existing code review interface is clearly designed for code review to take place at the MR level. [1]: https://blog.tangled.org/stacking

> 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

There’s this as well: https://blog.tangled.org/stacking