Kitchenowl creator has been flagged without warning making all of their repositories return 404, while in their settings all of the repositories still look normal with public visibility. (lemmy.ml)

submitted 1 day ago by iByteABit@lemmy.ml to c/opensource@lemmy.ml

27 comments fedilink hide all child comments

Here is the message where he found out what happened:

I didn't receive any information about it but when creating a support ticket I was told my account has been flagged and I had to do some extra verification. I've created a support ticket now and will keep you posted. I'll believe it's nothing major though, I use 2FA everywhere, the last commit on all repos is what I expect, and all sessions and usages look fine

Absolutely fuck Github and Microslop, they can just vanish your projects without notice whenever they want with barely any justification for it, and then take their sweet time to fix it too.

you are viewing a single comment's thread
view the rest of the comments

[-] danielquinn@lemmy.ca 30 points 1 day ago

What is it going to take to push FLOSS software out of GitHub? Everyone here can move their projects literally anywhere else today. I did it for my own (roughly 10 projects) five years ago and it only took about an hour:

Create an account with Codeberg, GitLab, or whatever you like.
Use their built-in tools to copy your repo over to your new account. In GitLab's case, this will even migrate over some of the additional features, like issues.
Update the places where you publish the project: PyPI, npm, whatever, with the new project home URL.
Archive the old project on GitHub, with a pointing link to the new project home.
(Optional) announce the above in any of the social spaces where people care about your project.

[-] WhyJiffie@sh.itjust.works 7 points 13 hours ago

for anyone reading this, Codeberg/Forgejo can migrate issues too! use the "new migration" function in the menu where you create new repositories, and tick the box for copying issues and wiki. it is a one time copy only, though, so if you are dedicated you should restrict issues on the github repo to collaborators only, so that people can't open new issues (which won't be able to be synced anymore), but old ones are still readable in their original form.

syncing issues cannot be done later, it's for new repos only

[-] danielquinn@lemmy.ca 3 points 12 hours ago

Oh I didn't know this was available in Codeberg! Thanks for sharing.

[-] tofu@lemmy.nocturnal.garden 12 points 23 hours ago

The problem is that everyone already had a GitHub account and creating an account on 10 different forges just for reporting issues is annoying. GitHub was comfortable.

Forgejo is actively working on federation for this and I think it's super important. Create account somewhere, send issues, comments and PRs to projects on other instances.

[-] def@aussie.zone 3 points 12 hours ago* (last edited 12 hours ago)

GitHub lets you use them as an oauth provider. Issue solved.

Instance fragmentation is annoying in the sense while you can unify log in with oauth you can’t share settings between instances of the same software. Would be cool if oauth could have a generic user_data field to store json of settings maybe…

[-] danielquinn@lemmy.ca 7 points 23 hours ago* (last edited 23 hours ago)

That's a worthy goal, but the problem isn't so insurmountable that we have to wait for some theoretical new feature to be available and adopted. There are three dominant players out there, one of which has demonstrated a willingness to screw everyone and the "it's not perfect yet" excuse is getting pretty thin.

Switch to Codeberg today and there's a good chance that this federated login will be supported there when/if it's ever available. GitLab could do it too, and moving there will give you a bunch of nice things you don't even get in GitHub let alone Codeberg.

But it's long passed time to move. Microsoft has stolen our code to feed into their slop machine and enshittified the platform. Sticking around because a perfect alternative isn't available only serves to harden the network effect that keeps GitHub dominant.

[-] tofu@lemmy.nocturnal.garden 6 points 20 hours ago

Agree with Codeberg. I wouldn't recommend Gitlab, nothing stopping them from becoming the next GitHub if they get enough people.

[-] danielquinn@lemmy.ca 5 points 20 hours ago

It's true. They're for-profit, so the motivations are still there. Fragmentation helps a lot though. If a third of us move to one, and another third to the other, that would cripple any party's ability to enshittify.

this post was submitted on 06 Apr 2026

92 points (98.9% liked)

Open Source

46008 readers

176 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Posts must be relevant to the open source ideology
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 6 years ago

MODERATORS

Cloak@lemmy.ml

kevincox@lemmy.ml

CrypticCoffee@lemmy.ml

Lettuceeatlettuce@lemmy.ml