all 26 comments

sorted by: hot top controversial new old
[–] 84 points 10 months ago* (last edited 10 months ago) (11 children)

I think sometimes people forget that one of the main features of Git is that it's decentralized. You don't need Github; just push your repo to a different remote.

Everyone that clones the repo (usually) has a full copy of it, including all history, and theoretically you can clone the repo directly from their copy. Of course, that's often not practical, which is how we ended up with these centralized services.

The main issue with losing a Github repo is the auxiliary non-Git-powered features of Github, like issue tracking.

  • source
  • hideshow 11 child comments
  • [–] 34 points 10 months ago* (last edited 10 months ago)

    This aspect of it being decentralized is so important to remember.

    People sometimes give me quizzical responses when I point them to the repository for the Bypass Paywalls Clean plugin because it's hosted on a Russian git site (gitflic.ru). The plugin was chased off the Firefox add-ons site/Chrome add-ons site, it was chased off of Gitlab, it was chased off of Github, all over DMCA takedown requests. People act like "well it must be shady because it's not on a well known git site" and yet is hosted in a country that doesn't respect the US copyright cabals control over media literally because that's the only safe harbor for it. The developer even has this snippet on his description of the plugin:

    PS although the add-on was removed from Mozilla’s add-on store (AMO) (because of DMCA Takedown Notice) it’s still signed and manually checked for security by Mozilla (hence the delay in signing).

    Yet it's super common for people to be absolutely suspicious of it. Including being suspicious of the traffic leaving the plugin when it's not being used which turns out to be the plug-in checking for updates every time.

    Using alternative gits is so important and is literally what allows programming and especially open source programming, to thrive.

  • source
  • parent
  • [–] 25 points 10 months ago (8 children)
  • [–] 3 points 10 months ago (6 children)

    Why forgejo over self-hosted gitlab?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 19 points 10 months ago (3 children)

    Depending on what your needs and available resources are, GitLab is fairly heavy especially in comparison to Forgejo.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 10 months ago (1 child)

    Fair! Mind you, the question was genuine curiosity. I don't have projects of my own hosted at this time, but I may soon.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 10 months ago

    No worries at all! I battled with that choice for a while when I was self hosting. I had already been so deep into using GitLab CI that it would've been a pain to migrate to Forgejo Actions, though to be fair when I had setup GitLab the Actions system didn't actually exist yet.

    And if you plan to expose it to the Internet, GitLab being a much larger project has more potential security issues to keep up with which is another important note.

    (Though as always when publicly exposing services to the Internet, keep up with patches either way and stay safe!)

  • source
  • parent
  • [–] 46 points 10 months ago*

    and Won't Explain Why

    They've made it pretty clear. They're banning porn because being a dumbass puritan is all the rage nowadays (and they probably want to avoid accidentally training their precious AI on porn). Seems like it's not well automated, though. Quite a few NSFW repos are still up. Probably requires manual user reports or some such.

  • source
  • [–] 34 points 10 months ago*

    Sweet. I hope forgejo et al become more popular.

    I strongly encourage Microsoft to keep making all their products worse while destroying user trust. It's a brilliant strategy that can make the world a better place.

  • source
  • [–] 30 points 10 months ago* (1 child)

    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.

    A developer who goes by Sauceke, who Github suspended in mid-November without explanation, said their open-source adult toy mod users are now encountering broken links or simply can’t find any of their work.

    Hmm. Buttplug.io's GitHub repositories are still up, and I'd think that that'd be rather-more-prominent if the issue is sex toy code.

  • source
  • hideshow 1 child comment
  • [–] 27 points 10 months ago

    It's owned by Microsoft and they're doing this with all their products at this point.

  • source
  • [–] 26 points 10 months ago

    Github is Microsoft, that's why.

  • source
  • [–] 16 points 10 months ago*

    So that's why Australia initially included GitHub, on the list of "social-media" platforms to be banned under 16?

  • source
  • [–] 13 points 10 months ago

    Leave the sinking ship if you don't want a bad experience.

  • source
  • [–] 12 points 10 months ago

    Everyone is fleeing GitHub anyway.

  • source
  • [–] 10 points 10 months ago

    My gut says that they are taking a shortcut to clean up copilot.

  • source
  • [–] 5 points 10 months ago

    I'm a bit sad, now copilot won't learn dirty tricks, foul mouth code comments and all that to parrot for vibe coders living in VSCode

  • source
  • [–] 5 points 10 months ago

    Does the developers age matter?

    /s

  • source
  • [–] 4 points 10 months ago

    The tighter they squeeze

  • source
  • [–] 10 points 10 months ago

    That's what you get for hosting your shit on GitHub

  • source
  • 102 comments in c/games@lemmy.world view that post
    4 comments in c/DeclineIntoCensorship@lemmy.dbzer0.com view that post