/tg/Station 13

Hello! Github disabled our tgstation/tgstation repo. This code repository houses the main game code, and is what the game servers look to when updating between rounds.

The reported reason is "ToS Violations". No explanation byond that. No email was received from github about the suspension.

DMCA's look different, this is not a DMCA related suspension.

Our HeadCoder has filed a ticket with github to find out more, but he is a kiwi, so it will be at least 8 hours until we know if github responded.

The servers will remain online, and we have a backup of the code repo, (because of how git works). (but not a backup of issues and pr comments)

Most coding will still happen. (that's a lie, all the coders are distracted because of this). Github is only needed for the review stage, and this will not likely last long enough (one way or the other) to seriously impact that.

Other threads:

Coder Bus: https://tgstation13.org/phpBB/viewtopic.php?f=5&t=26317

digg: https://www.digg.com/r/SS13/comments/ ... thub_gone/

Timeline (NZST), dates in ISO yyyy-mm-dd format.

Repo disabled for ToS violation, cause unknown (this is approximate) - 12:14 am 2020-04-10 (NZST)

Initial ticket opened - 12:20am 2020-04-10 (NZST)

Follow up after I had the chance to sleep - 6:49am 2020-04-10 (NZST)

Bumped the ticket with this image https://file.house/WV7H.png - 17:58pm 2020-04-14 (NZST)

Response - 2020-04-15 - https://tgstation13.org/phpBB/viewtopic ... 37#p555437

Current status: Responded, awaiting repo being restored

Decision point: 2020-04-19 (NZST), if no response by this time, we will begin moving to gitlab

why is my fork linking to this https://github.com/Crestednewt/-tg-station

that is the first person to ever fork tg... (i think)

so i've heard that some jannie reported the repos (hippie got flagged too) because they have the word nigger (hippie, on a sign) and faggot (the food item) in the code
i don't know if that's true but that's a good meme

terranaut wrote:so i've heard that some jannie reported the repos (hippie got flagged too) because they have the word nigger (hippie, on a sign) and faggot (the food item) in the code
i don't know if that's true but that's a good meme

polaris and its downstreams have not been hit and they renamed the F O R B I D D E N S N A C K to "meatball" a good while ago

For anyone who's wondering about what happens if GitHub doesn't unban us, we probably go to GitLab and nothing changes.

can't we just go to gitlab already?

We will still get owned by subpar GitLab services.

we should make our own github
call it "tgihub"

"moving git forward"

"advancing git"

Skubhub

Skub.club

donk.co if you wan't me to link that site somewhere besides the main page

cool

Microsoft claimed another one

To be fair, this was one of the concerns we had back when we heard that microsoft was buying github. I wouldn't be surprised if the reason for the ban was extremely stupid and brought on by some ass hurt player looking to stir shit or some awful auto moderator feature. Props to the coding team for being prepared for this for years now.

Obviously conjecture, but for anyone reading there's a nonzero chance that it was due to someone reporting our usage of the ol' faggot word

MrDoomBringer wrote: Obviously conjecture, but for anyone reading there's a nonzero chance that it was due to someone reporting our usage of the ol' faggot word

The "Faggot is a type of meatball" defence isn't really going to work when it is also used as an insult in the code, now is it?

PKPenguin321 wrote:we should make our own github
call it "tgihub"

If you call it TGIhub we're just gonna get sued by the crappy restaurant.

Decision point: 2020-04-19 (NZST), if no response by this time, we will begin moving to gitlab

genuine shame to lose so much history if that ends up being the case, i enjoyed sometimes looking through all my old PRs

hadn't even thought about that. that's going to suck ass. it's useful being able to go back to old PRs and see why something was added or removed or wasn't added or removed. anyway this seems like a big misunderstanding based on some targeted report that can be ironed out once they get back to orange

If the repo does return, I hope someone sets up a bot that maintains a local copy. Also, while writing this comment, I did a quick search regarding repo backups, and discovered that there are both third-party tools for maintaining such an archive, and existing third-party archives of all of github. Maybe gharchive or ghtorrent has a copy of (almost?) all of the old issues and PRs that could be migrated to a new platform, if github never replies or never restores the repo itself?

So there is no way to download the master(or whatever its called) file until the github page is back up, right?

Alex Crimson wrote:So there is no way to download the master(or whatever its called) file until the github page is back up, right?

https://github.com/mrstonedone/tgstation

The only thing github has that we do not have is the issues text and their comments; as well as the pull request text/body and comments/code review remarks.

The actual master code (and sprites) and the history of code changes (commits) to the master code is downloaded by every coder in order to even structure their changes in a way that can be submitted back to the /tg/station repo, so we have MANY copies of that. The game servers also download the commit history just because it's better and faster then re-downloading all ~150mb of code and sprites every update.

Github support has replied:

Thanks for writing in about this and apologies for our delay in responding. The https://github.com/tgstation/tgstation repository was disabled following reports that its activity may have been in violation of the following prohibition found in our Acceptable Use Policies:

Under no circumstances will Users upload, post, host, execute, or transmit any Content to any repositories that:

is discriminatory or abusive toward any individual or group;

Please also note, from our Community Guidelines,

don’t post anything that a reasonable person would consider offensive, abusive, or hate speech.

Specifically, the content that was reported included the use of racial and homophobic slurs within the project code, which we found to be against the spirit of our Community Guidelines.

We'd be willing to reinstate the repository for one (1) business day in order to give you the opportunity to remove this language from the code.


I will speak to the maintainers but this shouldn't be unreasonable to abide by.

Meatball time.

I'm torn

I personally think using these type of slurs in jest or the spirit of rp are fine. I personally say the old gamer word a lot among my friends and members of /tg/ and people always know i'm not some white supremacist.

I also think that anyone who uses these slurs to genuinely insult someone is not fine.

At the end of the day we're at the whim of Github and there's honestly no real argument to preserving these words in the codebase other than "the spirit of the game".

worst case scenario: have it pull from a config. they just don't want to host slurs and that's fine. it's probably much easier to just right up remove all the slurs anyway tho, i was talking for things where it doesn't really work without the slur like tourettes

Nigger > DB_BADWORD_N
Pulls N word from DB
ifndef > idiot

Changing it or not is a separate issue and a fine one to prevent such problems in the future if thats the call. Unsurprisingly this was their answer and goes to show that the move to another spot should be done nonetheless, for if they shall police your works like this now they will certainly do it again.

I don't like it, I think it's stupid, and I think any company trying to claim moral superiority is composed almost entirely of hypocrtical dog turds.
I'm also begrudgingly a pragmatist, and I realize burning the whole thing down, even over a matter of principle, would primarily be an exercise in masturbation.
My main curiosity is if the word filter is allowed to stay.

the word filter is not in the code, it's a configurable setting, any actual words are on the servers filesystems

They would still appear in code in the filter list for some of the speech mutations, but those should probably be a config anyway. Any other appearance is entirely unnecessary and can be removed or changed just fine (including faggots the food item which are clearly meatballs since you make spaghetti and meatballs with them.)

Glad to see that this issue can be solved with a simple patch.

lol

Pomf123 wrote:lol

reported

Wondering how far it stretchs

The immovable rod penetrates you when it kills you as a funny since it's penetrating your body

But that's a word with sexual undertones. Think that breaks TOS?

At least it's an easy fix. Stupid that we should have to fix it (should be the community's decision to police that kind of stuff, not GitHub's) but whatever.

Probably should get rid of the gamer word in the word filter too, just to be sure.

No I think it's pretty reasonable that when there are two lines containing the word faggot or nigger in your code, that your project can be shutdown and your access removed for the greater good.

BONERMASTER wrote:No I think it's pretty reasonable that when there are two lines containing the word faggot or nigger in your code, that your project can be shutdown and your access removed for the greater good.

TBH try to put yourself in the shoes of someone reviewing an ss13 codebase, who is not familiar with it's internet cancer origins.

I never really understood why people always gravitate towards services run by big companies and then scream about having to follow rules.

Kyrah Abattoir wrote:TBH try to put yourself in the shoes of someone reviewing an ss13 codebase, who is not familiar with it's internet cancer origins.

Haha repo go brrrrr

It's unacceptable.
Debate me.

can we move to gitlab anyway?

things which are just about the same level of effort:

> disabling a repo through an automated process that already exists (such as a complaint)
> not using shit language in the first place
> removing shit language you don't actually care about if someone says you have to in order to keep using a useful service
> maintaining standards moving forward

things which require more effort:

> actually building and deploying at large a new automated system for searching for and pursuing "naughty" language in your customers/users' repos (perfectly doable but it is an effort)
> enforcing that rule consistently across a wide variety of otherwise-unmanaged repos
> shifting a large coding project and developer community to a completely different platform because you're butthurt and want to protect dumbasses
> having a nuanced understanding of whether or not use of a particular word is bad or not in a given new context, en masse

i suspect that someone grepped, complained, github did the easy thing and verified, and they pressed butan

that's the path of least effort with the most work done on the part of whoever was mad enough in the first place to make the complaint

the path of least effort here is to remove dumbass comments that nobody cares about in the first place; staging some kind of free speech protest _over these specific commits_ is lol and makes a lot more work for everyone and would probably give the person who dropped the initial complaint an even bigger chuckle

There's really zero reason not to make the changes. Doing some sort of 'purity protest' shit doesn't do anything in our favor. If it's between moving the whole repo to GitLab and removing gamer words from code, one of those is significantly easier.

yeah just delete them, we lose nothing of value

RIP tourettes

okay we lose that faggot traitor george melons griefing me help but that's from goon anyway

help george melons griefing my github admins please

Vekter wrote:There's really zero reason not to make the changes.

protecting the culture and history of ss13 versus appeasing some butthurt SJWs

frankly with the resources you guys have I'm surprised you don't have the option of a privately hosted git