3 ms·

That's absolutely so dangerous, so forking someone's repo on GitHub could potentially get you child porn charges? Insane. Fucking insane.

• Crosseye_Jack 3y ago
  Well you can get arrested and charged for pretty much anything. Will those charges stick, and will you have to defend them is the real question. As for CP, in the UK and the US there is the defence that you were not aware of the CP, you should be fine, but you may have to spend time/money convincing cops/prosecutors that. As for the repo on my account that got spammed with reports today there are 2 things to highlight 1) the reports were nothing to do with CP, but “Sexually explicit content suited only for mature audiences.” 2) the repo was a fork of GitHub’s own (discontinued) Atom editor, it doesn’t even have the files in question included in the repo. The email I got (will paste below) talks about files in another repo that were updated ~9 months ago (couldn’t be arsed to look into the files history to see if they had existed before then and that date was just the last time they were updated). My fork was from 2022 when GH discontinued Atom (was still using it for a couple of projects, so took a fork just in case, but ended up never needing it). So the atom repo fork got restricted (would need to be logged in to GH to access it) for content it for what I can tell never even contained any porn, lol. Guess because the user in question also had a fork or just a repo with a similar name “atom-ng” someone or group mass spammed reports on those repos, because I got 5 emails from GH all with 1 min about this one repo that had been untouched for over a year. Anyway enough rambling, what follows is that email. Note the yiff folder never appeared in my fork at any time, but it was still flagged by GH Edit: looks like my fork was flagged mearly because another fork of the atom editor had porn in it at some point even though my fork never interacted with that fork nor ever had porn in it, guess it was more “mass reporting” by the people than something done by GitHub themselves. I just deleted my forked repo, because I no longer needed it anyway. ————————————————————— Access to the /atom repository has been limited due to concerns from our community that the contents of the repository may include the following: Sexually explicit content suited only for mature audiences. Going forward, users must be logged in to a GitHub account to view the repository and will be presented with a notice related to its content giving them the option of viewing the repository or discovering other content on GitHub. You may contact us for more information or to request a review of this decision: Appeal and Reinstatement Visibility and access to your repository has been restricted due to reports of sexually explicit content located in the following directory: https://github.com/Alex313031/atom-ng/tree/master/packages/yiff/assets https://github.com/Alex313031/atom-ng/tree/master/packages/y... For more information on the relevant policy see: - https://docs.github.com/en/site-policy/acceptable-use-policies/github-sexually-obscene-content https://docs.github.com/en/site-policy/acceptable-use-polici... Please contact us as soon as possible if you wish to resolve this issue and remove the restrictions from the repository.
• chupapimunyenyo 3y ago
  https://github.com/Alex313031/Alex313031.github.io/tree/1648104f48568bc1f7ddb7513649421f86bb2099/misc/sexuallymutilatedchild.org https://github.com/Alex313031/Alex313031.github.io/tree/1648... here are the images. They are not sexual/erotic at all and have been hosted on github for more than a year