upvote

points

by julianlam10 hours ago |
comments
upvoteby nerdypepper10 hours ago|
next
[-]
disclaimer: i maintain tangled, some reasons to try might be:

- tangled federates: https://blog.tangled.org/federation

- native stacked PRs: https://blog.tangled.org/stacking

- tangled implements mitchell's vouch system: https://blog.tangled.org/vouching

reply
upvoteby benrutter10 hours ago|
parent|
next
[-]
> - tangled federates: https://blog.tangled.org/federation

People have been talking about federation across forges for a couple of years and seems like its finally at least close to being a real thing!? That's absolutely amazing!!

reply
upvoteby avsm10 hours ago|
parent|
[-]
yep, I host two separate Tangled knots; one for my personal use and another for work at the Cambridge Computer Science department. Having large git repos on a server near me is great, and because I can sync the bare git repos it’s easy to run a local forge as well.
reply
upvoteby ashu14616 hours ago|
parent|
prev|
[-]
What are some of the practical use cases of federation in git workflows ?
reply
upvoteby jeremyjh10 hours ago|
prev|
next
[-]
It also has a pretty fundamental design flaw: issue /PR comments belong to the server where the commenter is hosted, not to the repo. I’m sure they will find a workaround but finding that reduced confidence they actually understand the problem they are solving.
reply
upvoteby nerdypepper10 hours ago|
parent|
next
[-]
this is changing very soon :)

see knot2[0] for some initial experiments: https://tangled.org/oyster.cafe/knot2

> As time goes on we are re-assessing the idea of users owning what is "collaborative data" (issues, PRs, etc.) on their PDSes - soon may come the day that an issue also lives on the knot as a source of truth, with an accompanying pointer record on user PDS to attest that it's theirs

reply
upvoteby icy10 hours ago|
parent|
prev|
[-]
We’re solving for this very issue. Issues & pulls will belong to the repo, backed by a “COB” (collaborative object) system.
reply
upvoteby chaosharmonic9 hours ago|
prev|
next
[-]
> something more established like Codeberg, or if f/loss, Forgejo or Gitea?

Codeberg's git hosting is a Forgejo instance, actually.

reply
upvoteby arikrahman10 hours ago|
prev|
[-]
Yes, separation between git storage and identity. Very simple to use your own Knot instead of the default knot1, just enter your own website link to it. Not as beholden to Github downtimes that are out of your hands.

I was using Codeberg this morning, now I'm on Tangled. All I had to do was switch remote origin.

reply