News for hackers. Stuff that matters.
Re:The Federated Code Forge by kstrauser on Friday October 30, 2026 @12:30PM (#50306295)
I’m excited about this direction. I’ve moved most of my own projects onto my own Forgejo, but miss it being easy for remote strangers to open PRs and such without registering in my system, which I have zero desire to allow.

So what’s the state of Tangled today? Say I have a Tangled server (instance? host?) up and running with my repos. Some stranger wants to contribute. What do they have to do before they can open issues or send PRs or whatever?

Re:The Federated Code Forge by icy on Friday October 30, 2026 @12:40PM (#50306446)
That's exactly the problem we want to solve. Of course, they still need identity of some kind -- in this case, they'll need an AT Protocol account -- either by self-hosting a Personal Data Server[0], or signing up with a provider such as Tangled or Bluesky/Blacksky, etc. This is the last ever account they'll need (and it's theirs, and portable!). They can then begin contributing; they'll use this same account for all of Tangled and other AT Protocol services.

Your Tangled git server that you'd want to run is a 'knot'[1]. It's not exactly analogous to Forgejo because it's headless, but that makes it super light on resources to run.

[0]: https://atproto.com/guides/the-at-stack#pds [1]: https://tangled.org/docs/knots/self-hosting/

Re:The Federated Code Forge by kstrauser on Friday October 30, 2026 @12:46PM (#50306541)
Got it. I'm still trying slightly unsuccessfully to wrap my head around this, but I've run a Mastodon instance for about 10 years and it took me a little while to wrap my head around that, too.

This is great. I'm delighted at the idea of having my own knot hosting my projects, talking to my friend's knot, and coordinating on a global project's knot, all without having to lock everyone into one centralized point of failure (even mine). Amazing. I love it!

Re:The Federated Code Forge by theothershoe on Tuesday November 03, 2026 @09:24PM (#50360828)
I've been setting up my own self-hosted knot, with excitement - this is the kind of forge I've been wishing for! There's an architecture document, but I'll leave some notes on how I've come to understand things so far. https://tangled.org/permadeath.com/atgc/blob/main/docs/archi...

You have options for self-hosting one or all of three pieces: a headless git host (the knot) which you get direct ssh access to through a limited ssh interface like other forges use, a CI service (the spindle), and the service that provides your user identity and metadata (the PDS). Account metadata such as which repos are in your account, and public SSH keys are recorded in the PDS, while repo data such as pull requests are recorded in the knot (I think. There might be some cross-over for publishing user activity via the PDS, I'm not sure).

Tangled owns the frontend, which everyone accesses through tangled.org. That's the web interface for both git features, and for CI. The frontend is an "AppView" which is difficult to self-host because it requires ingesting and aggregating a lot of network data. That's what assembles the network-wide activity feed you see on tangled.org, and that's where "Bobbin" comes in. But you _could_ access everything through a different AppView because your identity, data, and metadata are all owned by your PDS and knot.

The AppView concept is a point where Atmosphere differs from the Fediverse. In all my Fediverse experiences the service that I log into is the same service that runs the app frontend. With Atmosphere an AppView uses OAuth to authenticate you with your PDS. So I can log in to both Bluesky and Tangled with the same identity, compared to Fediverse where I need different Mastodon and Lemmy accounts to use both "apps". (Bluesky is also an AppView btw.) Instead of many federated frontend+backend instances, Atmosphere tends toward many federated, headless backends, with a small number of centralized frontends.

The PDS provides your DID which is your unique identifier in the atmosphere. It seems like the knot, in addition to hosting git repos and providing SSH access, does some PDS-like things. The knot provides DIDs for your repos, and holds metadata. But again, the metadata in the knot applies to the repo - metadata that applies to you as a person lives in your PDS.

I'm self-hosting a knot, and I'm planning to self-host a spindle. But for the moment I'm using a PDS provided by Bluesky.

Re:The Federated Code Forge by nerdypepper on Friday October 30, 2026 @12:35PM (#50306367)
all they would need is an atproto account. you can get one of these on Tangled itself, or bring your own. they can then open issues on your repository.

soon, repos will be able to declare a contribution policy: presently its open to all (anybody can open an issue), but owners can choose to limit this to just contributors for example.

Re:The Federated Code Forge by kstrauser on Friday October 30, 2026 @12:49PM (#50306594)
How soon will that be, do you suppose? It's not a blocker for most of my projects, but I can think of a few that I'd like to keep more closed (while still making them publicly cloneable). That doesn't keep me from using Tangled today for the open repos. It just means I'd need to have at least a couple of sharing setups - Tangled plus Forgejo - going at the same time for a while.

Also, will Tangled support private repos that are only visible or fetchable to specific people? Would that even make sense in its model?

Re:The Federated Code Forge by nerdypepper on Friday October 30, 2026 @12:52PM (#50306647)
for collaboration policies: its already part of the protocol, just needs to be baked into the flagship client!

private repos are coming very soon, we have a working demo of private repositories.

Re:The Federated Code Forge by kstrauser on Friday October 30, 2026 @01:27PM (#50307226)
Love it. Thanks!