/tg/Station 13

Bottom post of the previous page:

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

i was gonna make the changes until i discovered oranges and spookydonut already did them: https://github.com/optimumtact/-tg-stat ... 33197ed097

i don't see any culture or history here worth losing github access over

We could also move to gitlab and just archive this repo's PR/issue bodies/comments so we don't have to worry about this kinda stuff in the future

Does the word faggot count as culture?

yam_difficult_perc wrote:Does the word faggot count as culture?

It is a traditional dish in the united kingdom, banning the use of this word is an act of hatred and racism towards the english people and indescribably intolerant towards native anglo culture. I will gladly stand with the discriminated and persecuted to make it known to github and certain other people that hatred has no place in 2020 and that diversity will prevail!

BONERMASTER wrote:

yam_difficult_perc wrote:Does the word faggot count as culture?

It is a traditional dish in the united kingdom, banning the use of this word is an act of hatred and racism towards the english people and indescribably intolerant towards native anglo culture. I will gladly stand with the discriminated and persecuted to make it known to github and certain other people that hatred has no place in 2020 and that diversity will prevail!

you can't be racist to white people.

edit:hmm this does appear to not be the hut thread so i'd like to say our problem is easily solved with config fill ins and just removing some bad offenders that aren't worth keeping, gitlab is totally out of the picture now that github is giving us a day to clean it all up

MrDoomBringer wrote:We could also move to gitlab and just archive this repo's PR/issue bodies/comments so we don't have to worry about this kinda stuff in the future

according to oranges in discord, gitlab has the same language rules but i was under the impression it didnt but idk

deedubya wrote:

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

I'm pretty sure that would eliminate all possibility of a CI system or simple webhooks though, depending it might also ruin pull requests and issues depending on what service you pick. Obviously pull requests and the like will be a non-issue if it's something like a private gitlab instance, but CI will still be a problem.

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

huge fucking lol

i don't know why i didn't put quotation marks around culture and history

i'm not british but hours of intensive research into the matter have lead me to believe the faggots in-game are better described as meatballs anyway due to the lack of organs involved in making them

the other important piece of culture and heritage we're losing is the conjecture surrounding george melons' sexuality which while irrelevant to his status as a griefer or traitor is nonetheless potentially queer erasure which is an important issue that should be handled with the utmost of care and respect

I am kinda sad that we'll lose moments like when some tider beat me up because i cooked up a faggot for him

MrDoomBringer wrote:We could also move to gitlab and just archive this repo's PR/issue bodies/comments so we don't have to worry about this kinda stuff in the future

That's implying and assuming that GitLab won't eventually have the same policy. Better process is to just remove it. We don't lose anything significant and we avoid the goddamn nightmare moving repos is going to cause.

Quality code comment

yaay we did it its back

Despite the ToS violation, it's still frustrating that Github would just ban a large, active open-source codebase with no warning and no reason given, make everyone wait a week for a response, and then only give a day to make any corrections.
Like, all they had to do was ask nicely.

Cheridan wrote:Despite the ToS violation, it's still frustrating that Github would just ban a large, active open-source codebase with no warning and no reason given, make everyone wait a week for a response, and then only give a day to make any corrections.
Like, all they had to do was ask nicely.

I suspect the quality of the service provided is proportional to https://github.com/pricing

Moving to self-hosted services doesn't preclude webhooks, Selfhosting git platforms exist, CI would be a bit harder, as you'de likely have to run that yourself as well, there's nothing outright *preventing* TG from moving to that model.

make a fully open source github alternative to complete the circle

TheSmallBlue wrote:I am kinda sad that we'll lose moments like when some tider beat me up because i cooked up a faggot for him

u can use pen to name it a faggot so we are still good

To the people talking about self hosting

Hosting a git instance is not as easy as turning on a VM and installing gitea or gitlab packages, the installation is 1% of the effort, 99% of it is maintaining a performing, secure and backed up service and upgrading it from time to time. You are grossly GROSSLY misunderstanding the effort required to run a modern service with as much complexity as gitlab/github and the amount of man hours that needs to be spent on that.

Bear in mind that we
A) can just barely afford the game servers we have
B) still do not have an operations team maintaining that infrastructure.

We do not have the staffing to maintain infrastructure to the same level as gitlab or github or even to a level of quality I would find acceptable and as such we would have to sacrifice in security, in stability, in performance and in CI/integrations.

A simple cost benefit analysis of that indicates that the obvious answer is to make the changes, which were small and non particularly burdensome.

To the people dragging on support

There is a worldwide health pandemic ripping through most countries and it was over a long weekend in most countries.

Cheridan wrote:Despite the ToS violation, it's still frustrating that Github would just ban a large, active open-source codebase with no warning and no reason given, make everyone wait a week for a response, and then only give a day to make any corrections.
Like, all they had to do was ask nicely.

I highly doubt anyone actually went through the repo with any context or thought. I'm 95% certain they just ran it through a script or just searched for it, found a no-no word, and slapped a ban on it. There's also the possibility that whoever ran the script or answered our ticket was outsourced to some guy in a 3rd world country if Microsoft is involved. That's just how modern tech does things now a days. Fickle, out of focus, and in a constant self preservation mode to have the least potential of a law suit.

I said it earlier but we all knew years ago that this could happen, Only thing we can do it make sure we have a back up and keep playing the "I found something I don't like, so now you're gone" game.

Replace all instances of "retard" with "github employee", problem solved.

Durkel wrote:

Cheridan wrote:Despite the ToS violation, it's still frustrating that Github would just ban a large, active open-source codebase with no warning and no reason given, make everyone wait a week for a response, and then only give a day to make any corrections.
Like, all they had to do was ask nicely.

I highly doubt anyone actually went through the repo with any context or thought. I'm 95% certain they just ran it through a script or just searched for it, found a no-no word, and slapped a ban on it. There's also the possibility that whoever ran the script or answered our ticket was outsourced to some guy in a 3rd world country if Microsoft is involved. That's just how modern tech does things now a days. Fickle, out of focus, and in a constant self preservation mode to have the least potential of a law suit.

I said it earlier but we all knew years ago that this could happen, Only thing we can do it make sure we have a back up and keep playing the "I found something I don't like, so now you're gone" game.

Spoiler:

Seriously though, the lack of a warning or even having someone contacting the repo owner is absolutely appalling on their part. Reminds me when they goof got banned and lost all of his shit, Like fuck. Give at least a 24 hour notice to fix it or that you're gonna get shit canned.

Speaking of when goof got banned, I think it's dumb as fuck that they have a literal banbot actively scanning for comments that say "retard" instead of just wordfiltering "retard" so you can't post it in the first place

PKPenguin321 wrote:

Durkel wrote:

Cheridan wrote:Despite the ToS violation, it's still frustrating that Github would just ban a large, active open-source codebase with no warning and no reason given, make everyone wait a week for a response, and then only give a day to make any corrections.
Like, all they had to do was ask nicely.

I highly doubt anyone actually went through the repo with any context or thought. I'm 95% certain they just ran it through a script or just searched for it, found a no-no word, and slapped a ban on it. There's also the possibility that whoever ran the script or answered our ticket was outsourced to some guy in a 3rd world country if Microsoft is involved. That's just how modern tech does things now a days. Fickle, out of focus, and in a constant self preservation mode to have the least potential of a law suit.

I said it earlier but we all knew years ago that this could happen, Only thing we can do it make sure we have a back up and keep playing the "I found something I don't like, so now you're gone" game.

Spoiler:

Seriously though, the lack of a warning or even having someone contacting the repo owner is absolutely appalling on their part. Reminds me when they goof got banned and lost all of his shit, Like fuck. Give at least a 24 hour notice to fix it or that you're gonna get shit canned.

Speaking of when goof got banned, I think it's dumb as fuck that they have a literal banbot actively scanning for comments that say "retard" instead of just wordfiltering "retard" so you can't post it in the first place

they dont have banbots scanning, they act on reports, i said many bad words on github but only got banned once when i called out a citadel maint

what if whoever reported it wanted to frame iamgoofball

When did the hub get back online?

Did github give a reason?

Can someone update the OP topic, ty

PKPenguin321 wrote:

Durkel wrote:

Cheridan wrote:Despite the ToS violation, it's still frustrating that Github would just ban a large, active open-source codebase with no warning and no reason given, make everyone wait a week for a response, and then only give a day to make any corrections.
Like, all they had to do was ask nicely.

I highly doubt anyone actually went through the repo with any context or thought. I'm 95% certain they just ran it through a script or just searched for it, found a no-no word, and slapped a ban on it. There's also the possibility that whoever ran the script or answered our ticket was outsourced to some guy in a 3rd world country if Microsoft is involved. That's just how modern tech does things now a days. Fickle, out of focus, and in a constant self preservation mode to have the least potential of a law suit.

I said it earlier but we all knew years ago that this could happen, Only thing we can do it make sure we have a back up and keep playing the "I found something I don't like, so now you're gone" game.

Spoiler:

Seriously though, the lack of a warning or even having someone contacting the repo owner is absolutely appalling on their part. Reminds me when they goof got banned and lost all of his shit, Like fuck. Give at least a 24 hour notice to fix it or that you're gonna get shit canned.

Speaking of when goof got banned, I think it's dumb as fuck that they have a literal banbot actively scanning for comments that say "retard" instead of just wordfiltering "retard" so you can't post it in the first place

I'm not a big fan of protecting line-toers personally, if someone is going to break a rule (or try the rules), they should be held responsible.

>we want to ban these words so that people arent triggered
>BUT we need to allow you to post these words so you can be held responsible
>now they can get triggered AND you can get banned!
>hooray, nobody wins!

>Well gentlemen, 9/11 happened last week and the airports need to reopen. What do you say to implementing these preventative measures, which would stop terrorists from hijacking planes?
>"Get the fuck out of here, we need to LET them hijack the planes so that we can hold them responsible after the fact. That way everyone can see how strong our virtues are!"

PKPenguin321 wrote:>Well gentlemen, 9/11 happened last week and the airports need to reopen. What do you say to implementing these preventative measures, which would stop terrorists from hijacking planes?
>"Get the fuck out of here, we need to LET them hijack the planes so that we can hold them responsible after the fact. That way everyone can see how strong our virtues are!"

>"Oh boy you were trying to sneak a bomb through the airport inside your shoe! We check shoes for bombs, you know, come back later with a better hidden bomb!"

What people are saying without bringing in 9/11 is that the ic in ooc filter config was a good idea, github should follow in our stead

XDTM wrote:

PKPenguin321 wrote:>Well gentlemen, 9/11 happened last week and the airports need to reopen. What do you say to implementing these preventative measures, which would stop terrorists from hijacking planes?
>"Get the fuck out of here, we need to LET them hijack the planes so that we can hold them responsible after the fact. That way everyone can see how strong our virtues are!"

>"Oh boy you were trying to sneak a bomb through the airport inside your shoe! We check shoes for bombs, you know, come back later with a better hidden bomb!"

this is literally how it works in real life

PKPenguin321 wrote:

XDTM wrote:

PKPenguin321 wrote:>Well gentlemen, 9/11 happened last week and the airports need to reopen. What do you say to implementing these preventative measures, which would stop terrorists from hijacking planes?
>"Get the fuck out of here, we need to LET them hijack the planes so that we can hold them responsible after the fact. That way everyone can see how strong our virtues are!"

>"Oh boy you were trying to sneak a bomb through the airport inside your shoe! We check shoes for bombs, you know, come back later with a better hidden bomb!"

this is literally how it works in real life

i'd think you get arrested or something, but maybe i'm just misinformed

Anyway i don't mind either method of policing language from github for comments, although for whole repos a bit of warning would definitely be better than insta-disabling it, i'd think most would simply solve the issue and avoid breaking the rule anymore without the week-long blackout.