raxod502

I received an email at 9:22am PT this morning saying that my fork of this repository from July 2023 was violating the terms of service. So, this was not something that was added to the repository recently, and GitHub had more than enough time to resolve the issue in a less aggressive manner if they wanted to. It seems more likely like malicious action by GitHub on behalf of a copyright troll or other bad-faith entity like Google.

Here is the full text of the email I received, which contains no evidence for the alleged terms of service violation:

> Access to the raxod502/AdguardFilters repository has been disabled by GitHub staff due to a terms of service violation.

> When making content moderation decisions, we consider information from a variety of sources, including: account profile data, information contained in submitted reports/notices or discovered through our own voluntarily initiated investigations, and context around the contents of the repository.

> If you wish to regain access to the disabled content or would like to dispute that a violation occurred and can provide additional information to show that a different decision should have been reached, please review our Appeal and Reinstatement Policy and submit a request via our form.

> You may review our terms of service here: GitHub's Terms of Service

> Please feel free to Contact GitHub Support if you have any questions.

I filed support ticket 2981480 to complain about this communication.

My GitHub profile is automatically updated with the estimated length of my email backlog: https://github.com/raxod502/github-email-backlog

That doesn't work unless you can assume that every developer is willing to install all the dependencies of your project globally, with no control over what versions are used.

Actually, UPM fully supports Windows, as far as I know. You can install it directly as an executable, or via Scoop.

Original author here.

I can confirm that the actual reason is that at the time I thought typing "print" instead of "System.out.println" was a great idea.

See https://github.com/BusyByte/TerraFrame/pull/1.

Original author here.

The fact that all the methods were so ridiculously large made declaring loop indices globally less of a problem. But trust me, it caused plenty of bugs... :P

Original author here.

It's actually a method to convert from the index of an inventory hotkey slot into the keystroke used to access it -- there were ten hotkey slots, which were numbered 1–9 and 0 at the end.

But I like all the other interesting interpretations here :P (They all assume way more knowledge than I had at the time.)