I've revamped the mobile commit list view in #forgejo recently for use in #Codefloe.

Changes are summarized in https://codeberg.org/forgejo/forgejo/issues/8043.

If you view https://codefloe.com/codefloe/forgejo-codefloe/commits/branch/main on a mobile device (or use the mobile view in your browsers devtools), you'll see the difference to other Forgejo instances (e.g #codeberg).

Not sure if it will ever make it upstream, but I needed this fix so badly, and I couldn't wait for a lengthy (and likely complicated) upstream discussion first 😄️

@timbray

So they use #Gitea under the hood and don't reference it once?

That's a very questionable business model, especially if the underlying tool is #FOSS.

Btw, there are more open/transparent other Forgejo/Gitea-based instances like #codeberg (https://codeberg.org) or #codefloe (https://coefloe.com)

@mrmasterkeyboard @solblack

People started moving a long time ago but didn't post about it so actively. It only recently happens more actively on social media.

It also has to do with code being used for AI learning and other business related tools. The alternatives focus more on privacy.

There are just now alternatives emerging such as #codeberg or #codefloe (https://codefloe.com)