@moanos @codebergstatus Not really at least in Forgejo specifically. Forgejo doesn't have the "expensive" option recently introduced in Gitea, that requires signin only on some of the more expensive routes and leaves the rest public. Last time I checked they had some cookie setter/checker that triggered on most things outside of the main repo page and I guess that still isn't enough.
Timeline
Post
Remote status
Context
1
@phnt @moanos @codebergstatus
> Forgejo doesn't have the "expensive" option recently introduced in Gitea
lol wat why wouldn't they just cherry-pick that?
Gitea continues to be the superior fork for having less nonsense and continued reasonable developer behavior. Like when I pinged about this:
https://github.com/go-gitea/gitea/issues/34521
now Forgejo devs saw this come through and made the same change on their end, but look at the code style differences here. Gitea's is far superior IMHO
https://github.com/go-gitea/gitea/pull/37985/changes
https://codeberg.org/forgejo/forgejo/pulls/12905/files
> Forgejo doesn't have the "expensive" option recently introduced in Gitea
lol wat why wouldn't they just cherry-pick that?
Gitea continues to be the superior fork for having less nonsense and continued reasonable developer behavior. Like when I pinged about this:
https://github.com/go-gitea/gitea/issues/34521
now Forgejo devs saw this come through and made the same change on their end, but look at the code style differences here. Gitea's is far superior IMHO
https://github.com/go-gitea/gitea/pull/37985/changes
https://codeberg.org/forgejo/forgejo/pulls/12905/files
Replies
0Fetching replies…