HN Reader

Tangled, a Git collaboration platform built on atproto

332

This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies.

I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services.

For example, most forges: host your git repo, web view, collab tool, ci/cd pipeline, and task management.

I don’t see why these necessarily need to be bundled together.

For example, as long as we are comfortable not having direct access to the git repo, we can have a purely static web viewer for git: https://pgit.pico.sh

For collab, as long as we are comfortable sharing patchsets and reviewing locally, we can have a collab server that doesn’t need a git repo in order to function: https://pr.pico.sh

Then self hosting your own bare git repo on a VPS is trivial.

Git is already decentralized, centralizing it because all the other services require it is the anti pattern

3 months agoby qudat

Hey HN, co-founder of Tangled here!

We recently shipped a change to switch out our OAuth library—which introduced a regression, preventing new users from being added to the default knot and spindle (the git hosting server & CI runner). We just discovered this and pushed a fix—please log out and log back in again and you should be able to create repositories!

Otherwise, happy to answer any questions!

3 months agoby icy

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

3 months agoby jolux

Github is no longer a trusted nor a reliable platform. Moving at least the oss stack to atproto (or any other open network) is an excellent way to safeguard it against Big Tech, Government censorship etc. Love to see this.

3 months agoby pm90

I was in the first ~100 users to sign up for tangled after seeing that they were roadmapping stacked patch style pull request review and being generally impressed with how quickly they were building and shipping features all off the excitement from a budding community in the world of atproto. I am very excited to see where this goes and how they continue shipping.

There are a lot of opportunities here that could be levered to offer much better experiences and fundamental control and long term viability if they continue to execute this way.

3 months agoby rhgraysonii

I really like the idea of more decentralized git collaboration. What do people think are the biggest blockers to adoption in this space? Having to run a server or manage some kind of private keys? Is it purely network effect?

3 months agoby nickmonad

I'm increasingly becoming convinced that atproto is pointless. Federation is good, but this idea of implementing "take everything with you" at the protocol level is unnecessarily complicated and centralizing. With Bluesky it might make a little more sense, but with Git? So many better, easier options here. Archive your repo and a) learn how to the do the real decentralized thing OR b) make your own centralized thing OR c) just move to Gitlab or similar.

"Take everything with you" is just downstream from "find or be a trustworthy node."

3 months agoby jrm4

Why not improve upon https://radicle.xyz? It's been running for a while now with promising future. From my naive understanding of running a radicle node, it consumes around 40G of storage for the current network of 5k repos

3 months agoby udev4096

New tomorrow: "Spaghetti", a no-code platform to run your business on, and "Lock-in", a vault to keep all your important data safe.

3 months agoby danpalmer

I was pleased to see that this has CI pipeline support, but am saddened to see that it looks roughly GitHub-actions shaped.

I don't see the point in writing a sequence of serial steps in YAML. A bash script can already do that. YAML configuration for pipelines should be focused on expressing the dependencies of a DAG, not the serial execution of a program.

Buildkite got this right.

3 months agoby hamandcheese

For stacked diffs, check out https://gitpatch.com/

3 months agoby shayief

Is there any story for private/enterprise work here? the tangled stacked diff review flow looks very good for work stuff.

3 months agoby rtpg

It doesn’t seem to address this, but I’m curious whether this could be used for trivially relocatable package identifiers.

3 months agoby binary132

since ATProto had a Merkle Tree of its own, I wonder if tangled utillize this internally to interop with git

3 months agoby est

I am obliged to use a public GitHub org for work. Is it “blessed path” to try do the CR part in tangled and sync back to GitHub? I would love to profit from my nice jj habits at the review stage!

3 months agoby scottgg