Live data from Hacker News

We need a federation of forges

blog.tangled.org

161–170 of 424 posts

Re: We need a federation of forges

#161

I'm confused on what exactly we need to add to decentralized git to get where we want to be - if it's identities, why aren't we using what git itself supports (gpg keys; if someone has your private key, they are you no matter where )? Or in other words, what specifically does GitHub "do" that can't be done by using git as a backing store?

As a project member, I want users to already be logged in to the bug tracker. The lack of friction, likely from being the network effect winner, is key. I know fossil has this, but people don't have their private keys in fossil, they (I) don't even have fossil installed.

Re: We need a federation of forges

#162
It took me a minute to figure out what this was even talking about.

Tangles is, apparently, a gitlab-type project where PRs and bug reports and stuff are available on something called "at protocol" which is the bluesky social network "federated protocol".

at protocol competes with ActivityPub, which is mastadon

--

so you could, in theory, have a little federation of gitlabs peer-to-peering with each other, which is desirable for some reason.

Re: We need a federation of forges

#163

I'm confused on what exactly we need to add to decentralized git to get where we want to be - if it's identities, why aren't we using what git itself supports (gpg keys; if someone has your private key, they are you no matter where )? Or in other words, what specifically does GitHub "do" that can't be done by using git as a backing store?

I think it's just nice to have things in a central place ; no one's really gotten decentralized tech right and things like discoverability, interaction, job running, etc. is really nice to have in one place.

Mastodon and email are the closest I've felt to a distributed system that works, but for oss stuff ... I think we're getting closer, but it's still a very hard problem to solve.

Re: We need a federation of forges

#164

It took me a minute to figure out what this was even talking about. Tangles is, apparently, a gitlab-type project where PRs and bug reports and stuff are available on something called "at protocol" which is the bluesky social network "federated protocol". at protocol competes with ActivityPub, which is mastadon -- so you could, in theory, have a little federation of gitlabs peer-to-peering with each other, which is d…

The "some reason" isn't mysterious... it's redundancy and avoiding a single point of failure and ownership.

Re: We need a federation of forges

#165
It appears that git format-patch + git send-email is a mature and widely used approach. Wouldn’t it make more sense for the open source community to work on streamlining that process instead of trying to build momentum with new approaches?

Re: We need a federation of forges

#166
post #108

You will never get around the free rider problem. If I want to create 100 repos of vibe coded projects every month someone will have to pay for it. At this point, just give me an honest version of GitHub that tells me what things actually cost. 5$ a repo, and another 1 per gb stored in LFS, cool.

The cool thing is you can just host your own knot then. Host repos of whatever size you want.

Man I really want to like this thing but this jargon is so stupid.

Re: We need a federation of forges

#167
post #156

I'd like to preface I'm pretty active in atprotocol ecosystem, so my experience is more than likely a bit more biased, but thought I'd share some of my thoughts as a big fan of tangled. I've really enjoyed Tangled. It has so far been what I've wanted from a GitHub replacement, is simpler and does not have as many features, but it has been the main social/git provider I've been using for personal open source projects…

I'm afraid that atproto will suffer from Bluesky's irrelevance. Not sure if that's a valid fear.

Fair enough! We are a pretty small ecosystem all in all. I will say in Tangled's case their infrastructure is separate from Bluesky's for the most part, and the rest can be switched easily enough if ever needed.

One example is if you don't care anything about atproto, you can create a new account on Tangled's website that creates the account on their servers, but thanks to how atproto works it's just like you made one on Bluesky and can still interact with Tangled and everyone on the protocol for it's social features.

Re: We need a federation of forges

#169

It appears that git format-patch + git send-email is a mature and widely used approach. Wouldn’t it make more sense for the open source community to work on streamlining that process instead of trying to build momentum with new approaches?

For what it's worth, under the hood tangled is extremely similar to this approach.

Personally as just a random person in the community I've been building an appview for tangled that lets you interact with it as if you were just using git format-patch + git send-email + some MUA.

You can conceptually treat the tangled lexicon as a schema for encoding a git patchset based mailing list into IPLD/atproto records and vice versa. Doing this is slightly lossy but only barely. Otherwise it's pretty seamless.

Re: We need a federation of forges

#170

I'm confused on what exactly we need to add to decentralized git to get where we want to be - if it's identities, why aren't we using what git itself supports (gpg keys; if someone has your private key, they are you no matter where )? Or in other words, what specifically does GitHub "do" that can't be done by using git as a backing store?

People need more than a VCS. A way to search all of open source project's code, issues, and pull requests. A way to distribute software releases for free. A way to share code snippets. A way to discover new projects. A way to see what your friends are working on. An issue tracker and pull request area that is easy for users to submit through.
Post reply on HN