@qeef It doesn’t mean that the project does not care about FOSS. It just means that the lock-in effects are so strong that it’s not viable to cut away.

As a painful example: I had to create a github action to sign an executable. Cutting away from github would mean no more signed executables (for at least several months — if the past is an indicator, it would take 18 months in which little else is possible).

I take care to also make repos available outside github, but cannot avoid it.
@ueeu

@qeef

There's a #GiveUpGitHub [1] discussion for #Mastodon-the-main-branch [2] and a poll [3]. The discussion was originally a bug report, but Mastodon-the-main-branch maintainers didn't see #GAFAM dependence as a bug, despite it being a known vulnerability that will enshittify sooner or later.

[1] https://giveupgithub.org

[2] https://github.com/mastodon/mastodon/discussions/27765

[3] https://github.com/mastodon/mastodon/discussions/18756

@ArneBab @ueeu

@alci We’ve gone the self-hosting route, but don’t have the resources for maintenance.

When we last had our own servers, they took up the free time of one volunteer. And once you do that, you have to ensure that this is always available. The upkeep of gitlab is already annoying at work, where I get paid for 37 hours a week. For a hobby with 2-5 hours per week it’s not viable.

One option would be static hosting of the git repo (far lower maintenance cost). But then we have no PRs.

@qeef @ueeu