In the aftermath of Github banning or suspending dozens of popular accounts, the erotic game modding community wonders if they should move to platforms like GitGoon instead.

Developers making mods and plugins for hentai games and sex toys say Github recently unleashed a wave of suspensions and bans against their repositories, and the platform hasn’t explained why.

Developers I spoke to said the community estimated around 80 to 90 repositories containing the work of 40 to 50 people went down recently, with many becoming inaccessible around late November and early December. Many of the affected accounts are part of the modding community for games made by the now-defunct Japanese video game studio Illusion, which made popular games with varying degrees of erotic content. One of the accounts Github banned contained the work of more than 30 contributors in more than 40 repositories, according to members of the modding community that I spoke to.

Github didn’t tell most suspended users what terms they broke to earn a suspension or ban, and developers told me they have no idea why their accounts went down without notice. They said they thought they were within Github’s acceptable use guidelines; even though they make mods for hentai games and things like interactive vibrator plugins, they took care to not host anything explicit directly in their repositories.

Archive: http://archive.today/eNOI1

  • dejected_warp_core@lemmy.worldEnglish
    391·
    2 days ago

    For anyone that needs to know: it’s criminally easy to set up git for multiple remotes, making a migration from GitHub a lot easier.

    Remember that origin is just the default, and you can have any number configured you want.

    • View all remotes: git remote -v
    • Add new remote: git remote add $name $url
    • Push to another remote: git push $remotename $branchname
    • Pull from a specific remote: git pull $remotename/$branchname (note the slash)
    • Fetch from all remotes: git fetch --all

    The first two are just one-time setup, and the rest just get bolted onto your existing workflow. At some point, you’ll want to use git remote move names around, possibly even making origin something other than GitHub. Cheers.

    • dev_null@lemmy.mlEnglish
      3·
      18 hours ago

      Except the difficulty in migrating from GitHub is not moving the source code, that’s the trivial part.

      It’s moving the discussions, issues, releases, free CI on GitHub Actions, free hosting on GitHub Pages, stars, visibility, existing community around the project on GitHub, losing contributors. These are the problems, not configuring git for another remote.

      • dejected_warp_core@lemmy.worldEnglish
        1·
        7 hours ago

        True, but the article is about projects getting de-platformed, so all that goes away under those circumstances. There’s value tied up in all that data, but the codebase itself might be far harder to replace securely if the public repo just vanishes. Better to have at least an alternate offsite backup - on another service even - if all you do is maintain a project-owner-controlled clone.

        Plus, I know it’s a small gesture, but some folks might need that tiny push to migrate if they’re already fence-sitting about leaving.

    • orgrinrt@lemmy.worldEnglish
      7·
      2 days ago

      If only the forge parts were part of the spec like I believe in fossil for example. They are pretty much standardized already. All of the forges have issues, prs, releases. If there exists a git extension for this already, we really ought to spread that via word of mouth because at least I’m not aware of one. If not, I hope someone more familiar with the git spec could work one out and write helpful contribution guides to go with it. I, same as a lot of others I would believe, would be very much interested in helping build one.