Tangled and Radicle are both really cool, but add too much mental gymnastics compared to just running Forgejo.

What I like about (the idea of) ForgeFed is that it lets existing forges speak to each other.

In practice I probably just need Forgejo and GitLab to be able to speak to each other.

I believe the future of GitHub, for me, is to solve two problems:

  - Discoverability for public open-source projects
  - Backup since self-hosting is fragile long-term

So many times when I try to visit the source code of some package uploaded to crates.io, the self-hosted git no longer exists.

GitHub repos sit stale for decades.

For day-to-day reliance, my self-hosted Forgejo and CI runners have better uptime.

Only pet peeve with Forgejo:

  - It's a highly active project, RFCs, tons of PRs and issues.
  - Becoming a daily user, I want to extend it, and in its beautiful simplicity, it's not highly extensible.
  - So to avoid maintaining a fork of a very active project, extending it in unison is a social commitment.

What a luxury problem, but still.

I'd like to see more hosted Forgejo solutions pop up; it's very low-resource cost.

▲ IshKebab 3 days ago | parent [-]

I agree, these things just seem to add too much mental complexity compared to the advantages. Even the sign-up process is wierd, e.g. I put in my username as `dave` but if you try to log in as `dave` it says "did you mean dave.tngld.sh?" What? Then when you log in it takes you immediately to a second OAuth screen where you have to put your password in again, immediately after you logged in. I'm sure they would try to justify this bad UX with technical reasons...

I think the main attractive thing about Tangled is that it supports proper stacked PRs. But on the other hand it doesn't support private repos at all, and Github is getting stacked PR support soon (fucking finally)...

It's hard to see the advantage of Tangled over Codeberg for example.

▲

sshine 3 days ago | parent [-]

It seems like Forgejo isn't actively planning to have stacked PRs:

https://codeberg.org/forgejo/design/pulls/48

Which is totally understandable.

Managing a healthy highly-popular open-source codebase requires effort to not bloat it.

Which brings me back to wanting good APIs for native Kubernetes CI runners and time-limited PATs for agentic coding.

I can vibe that in a day. But it sure as heck won't be aligned with the future of all Forgejo users.

▲

IshKebab 3 days ago | parent [-]

> Which is totally understandable. > Managing a healthy highly-popular open-source codebase requires effort to not bloat it.

I would not call stacked PRs bloat. It's a super important workflow. The fact that Github hasn't supported it for so long is insane.

	▲	sshine 3 days ago \| parent [-]
		It’s not bloat. The argument is maintainer bandwidth/fatigue. From the closed issue: > Closing this out for the time being, as noted previously (I'm currently leaning towards designing some review refinements and shelving the stacked concept design for the moment) and to clarify that it isn't current and active work.