Hacker News new | ask | show | jobs
by theptip 14 days ago
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.
1 comments
jeremyjh 14 days ago
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.
link
blackqueeriroh 14 days ago
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.
link
jeremyjh 14 days ago
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.

link
verdverm 8 days ago
This was a really intriguing project that became Google abandonware.

https://github.com/google/git-appraise

The idea is to use git-notes for issues & PRs, because git is already distributed by design and these elements of SDLC centralized our usage.

link
theptip 13 days ago
Interesting point, I was thinking more about the latter, but you are right that issues and PRs are the more important piece.

It does look like Tangled currently does those in a weird way, ties to the issue owner rather than repo - but here’s a proposal to fix: https://leaflet.pub/p/did%3Aplc%3Axasnlahkri4ewmbuzly2rlc5/3...

Doing some weird distributed join across all your committer’s PDSs seems a bit weird, and the semantics of cross-referencing issues seems gnarly in that world.

I think I’d be OK to model a PR as a tweet, it’s more owned by the sender. But issues seem like they should be owned by the repo for sure.

link