| ▲ | propstober 9 hours ago |
| if anyone has more info on tangled would love to hear. been looking for a decentralized git provider for a while. started self hosting but was missing the social element |
|
| ▲ | Arubis 9 hours ago | parent | next [-] |
| [Radicle](https://radicle.dev/) gets a wee bit closer. It’s selfhostable and federated. You’ll have a hard time finding something with the same social gravity well as GitHub; it remains to be seen whether that’s a separable element or if it needs to ship as part of the forge itself. |
| |
| ▲ | theptip 8 hours ago | parent | next [-] | | I’ve been testing Radicle and it’s more focused on the distributed protocol for federating git repos, I.e. the data plane. The social / coordination control-plane angle is really thin, following users and repos goes by opaque IDs, etc. It could be a better solution for agents that don’t bounce off such mundane complexity. It could be better for private repo federation (eg private collective or agent swarm.) I’m interested in Tangled for the OSS/community aspect, it seems to have an advantage there with the richer identity layer for humans. | | |
| ▲ | jeremyjh 7 hours ago | parent [-] | | Issue and PR content are not social artifacts, they belong in the repo or at least its hosting instance. Likes and activity feed are the sort of thing that belongs in the social layer. | | |
| ▲ | blackqueeriroh 3 hours ago | parent [-] | | Issues and PR content are absolutely social artifacts, as they communicate information to others, whether opened by the repo owner or not. In fact, other people can interact with them, and are supposed to do so, which makes them even more inherently social. | | |
| ▲ | jeremyjh 2 hours ago | parent [-] | | The more important thing about issues & PRs is that they explain why the code is the way that it is. Knowing why the code is the way it is, is almost the entire reason we have a repository to begin with. They belong to the code, not some social graph. Yes, code is largely about communication as well - with others as well as our future selves. That doesn’t mean it’s a social media experience. There are lots of ways to communicate that aren’t that. |
|
|
| |
| ▲ | Certhas 7 hours ago | parent | prev | next [-] | | Can I interact with and discover any federated instance without having to know it exists? My experience with Bluesky Vs Mastodon really showed that the friction of federation in the latter can really kill the experience for me. I think we need something like Signal is to WhatsApp but for GitHub and my impression is that the ATProto world is the only one with the potential to deliver this. | |
| ▲ | jeremyjh 8 hours ago | parent | prev [-] | | This looks like a much more sensible design for code repos: all the artifacts live in the repo. |
|
|
| ▲ | p-e-w 9 hours ago | parent | prev | next [-] |
| I’d be interested too. Besides the fact that the company appears to be registered in Finland, I haven’t been able to find any information on who’s behind this, how they are funded, etc. |
| |
| ▲ | verdverm 9 hours ago | parent [-] | | 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. | | |
| ▲ | dgellow 9 hours ago | parent | next [-] | | Oh they raised a pretty large seed. But they don’t seem to have a business model, or at least I cannot find details on how they plan to make an actual business | | |
| ▲ | OneDeuxTriSeiGo 8 hours ago | parent [-] | | I'm not sure what's been published but as someone who plays with tangled as a hobby the immediate monetisation paths I could see are: - Charging to bypass the (admittedly very reasonable) rate limits on the main appview - Providing paid hosting tiers for private git knots, high traffic git knots, git LOP knots, CI runners/spindles, web page hosting (via their github pages equivalent), etc - Introducing a paid-for and permissioned nix binary cache platform since their CI spindle system is already nix-first. - providing paid PDS hosting for corporate/business customers with SSO integration etc. - SLAs and support contracts There's enough options here that they have a pretty flexible path towards profitability. | | |
| ▲ | dgellow 6 hours ago | parent [-] | | There are always options, I’m interested to know what their actual plan is. Given that seed investment and who the investors are I would be worried they would try to extract value from people code by training on it |
|
| |
| ▲ | p-e-w 9 hours ago | parent | prev [-] | | > GitHub's moat is not code hosting Of course not, it’s the number of people who are already signed up. Instagram’s moat also most certainly isn’t a scrollable photo timeline. | | |
| ▲ | verdverm 9 hours ago | parent [-] | | There's more to it than the number of people. Actions, GitHub apps/external integrations, identity/permission management The most significant, near-term, non-moaty gap is still private repos, which isn't all that big of a feature on the surface, but will have major work under the surface because of how bluesky is designing private spaces. I also think being primarily nix/jj focussed turns a lot of people away. Those techs are not my cup of tea, so I don't see myself using tangled. I'd be curious to hear tangled's thoughts on the path to financial sustainability. Without something that sounds plausible, I'm unwilling to migrate my code forge, for risk of going away / obsolescence. | | |
| ▲ | arikrahman 8 hours ago | parent [-] | | I see it attracting more people than it dissuades. You can use jj as just a prefix for Git commands like jj git init. Yet you get supercharged repo navigation abilities. If obscelecene is your concern, jujutsu is VCS agnostic and doesn't have to use Git in the future. Nix is as simple as it gets, even better than docker. Just 'nix run' whatever flake file someone gives you and everything works magically. This codeforge going away can't happen for me because I self-host it. |
|
|
|
|
|
| ▲ | vixalien 9 hours ago | parent | prev [-] |
| I think it's currently non-selfhostable. You can host your own git server (knot) and CI runner (spindle) but not really the UI/API itself, but they're working on changing it. Currently it's a bit centralised |
| |
