« first day (3943 days earlier)      last day (171 days later) » 

Cow
Cow
15:00
I'm still thinking about those 120 wpm hands you got, I want to hear that machinegun go
I used to be a fast typer, but then I learned Dvorak. Then I became slow at both Dvorak and QWERTY. I tried it for a few years, but I just realized I'd rather have one set of keyboard shortcuts to know.
!!/approve 13072
!!/blacklist-keyword fastwebrecovery
@Cow Oh man, that reminds me of this.
!!/approve 13071
Cow
Cow
@Spevacus holy sh** I was actually scarred there for a moment
15:05
!!/approve 13070
@Cow CRAM just calmly considering a warcrime for a moment. Hahaha.
Cow
Cow
wtf roflmao
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad keyword in body (2): LINE REACTORS (INPUT CHOKES / OUTPUT CHOKES)‭ by Noemi Shielding Technology‭ on electronics.SE
15:06
Anywho, back to your regularly-scheduled spam.
!!/watch noemiglobal\.com
Cow
Cow
oh man if those passengers knew that
getting targeted by a massive robot that could take out that place in seconds
I do believe CIWS systems have a manual trigger, so an operator would need to press the "Destroy" button for anything to happen, but still!
Cow
Cow
there's the button again
15:08
Cow
Cow
Just got this mail: Access to the Cowm00/SmokeDetector repository has been disabled by GitHub staff due to a terms of service violation.
Uh... that's weird.
Cow
Cow
did someone take over the Github?
it got hacked?
I have no access at all to the Github
It looks like the main GH repo for Smokey and every single fork has just been disabled.
Well that's not good. @Makyen @tripleee The Github repository for SmokeDetector has been disabled by Github staff. Please take a look.
15:09
Which... is a problem.
Do you think it has something to do with us having a master list of spam-catching regex and spam phone numbers? :P
Cow
Cow
hehe no idea
Cow
Cow
yeah I get the same
i got this on my fork too
Cow
Cow
15:11
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): What's a good test network right now?‭ by Peter Clark‭ on ethereum.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Reading and Writing Fill in the Blanks‭ by Edutrainex22‭ on mathoverflow.net
Yeah, I got the mail as well... That's messed up.
Cow
Cow
@Cerbrus yeah the two who can do something has been pinged
15:16
Surely it's a mistake. I can't imagine what ToS violation SD could've done. Perhaps they responded to a flood of false reports with an automated removal?
Cow
Cow
I have never seen so many people here
only goes to show how much it means
Well, anyone that has done anything with the repo has been mailed with a GH service violation notification...
Hopefully once the main repo is restored the forks will be, too. I'd rather not fill out the appeal form.
@Mithical yep, got a mail about that as well.
15:19
Pretty sure everybody's here for the same reason with the same confusion :)
Cow
Cow
maybe someone closed it and took all the cryptocurrency
oh wait..
I'm guessing it's probably flagged as containing malicious software / code or something like that...
Cow
Cow
I just hope it's not something ridiculous
15:21
Or spammers got clever and started reporting the repo 😅
But it is malicious against spam ...
I sent them an appeal just now, no idea what happened but they sent an email with instructions for how to respond
Thank ya.
Cow
Cow
@tripleee thank you!
15:22
they disabled my personal fork as well which was at least a day or two behind so it's not likely to have been caused by a very recent commit
@Spevacus I did, if only to add another voice saying "this shouldn't have happened".
Cow
Cow
yeah all my forks are dead too
@tripleee Did you get any more information on why it was locked down?
@tripleee Mine was years behind and got disabled.
This may be related to me. I reported someone on an unrelated GitHub project, And they took down my fork
15:22
I can speculate that some disgruntled spammer might have complained about something, or that our blacklists contain addresses of sites they have started to block
@Cerbrus nope, just a brief notice, presumably automated
SmokeDetector's GitHub repository has been disabled. It is unclear why beyond "for a ToS violation". Forks were also affected. An appeal has been filed.
@micsthepick How does someone being reported get your fork locked down?
github.com/tripleee/SmokeDeTest is still live but it contains some random chaff from my testing yesterday
GitHub rarely disables a repo while leaving forks open, so it probably won't help much speculating
I suspect it the bad words list
15:24
@micsthepick Did your fork get locked (significantly) earlier than ~17 minutes ago?
Received my copy of email notification at 15:07 UTC today
7 past the hour
if its' some sort of automated testing, we have some unsavory Tor sites in the website blacklist which they may be scanning for
The person I reported is likely to have had motivation to strike back at me
@micsthepick That's when the main repo was locked, so your report is probably completely unrelated
15:26
okay so its not just my fork that is impacted
i am raising my own hell with GitHub.
I have a local copy of all my important repos, sans issues and PRs of course
@micsthepick all your other repos are available so it seems unlikely that it is related specifically to you, though of course there may be scenarios where your clone of our repo was the one they decided to attack
the report form was kind of wacky so I'm not 100% sure my submission went through
I had a fork that got tanked too, that hadn't been touched in years. Nothing else on my GH account is affected. Email also received at 15:07 UTC
15:28
Thomas have you received some sort of ack or etc?
@tripleee You should have gotten a "view this ticket" button after submission, as well as an email about it.
Can we have a summary and timeline of events?
15:07 UTC - Github locked the repo
That's it.
That's about it. ^
We don't yet, nothing more than having the repo locked
15:29
I don't think there is much more beyond that, no (-:
Maybe tripleee could add one line - 15:xx appeal submitted
15:21 UTC - Tripleee sent in an appeal (successfully?)
For the moment, I do think SD can operate on limited functionality. So long as we don't perform git actions, we should be okay?
:21 I sent in an appeal for my fork as well
@Cerbrus Now I know you live in UTC+2 :)
15:30
well if the form submission didn't work that's not true, the email had one broken link and one appeal site which didn't seem to work well with my mobile browser
@iBug self-doxxed T.T xD
@tripleee Did you get an email after you submitted the appeal?
@tripleee did you get a confirmation email?
Wow, I haven't been in here in a long time... not a great occasion to meet everyone again but hi :) Same thing on my years old fork and all, unsurprisingly.
15:32
Well, time to open that ticket an automate [F5] :D
Whatever they say, GitHub has a good track record of handling support tickets in a timely manner.
@Mithical nothing so far, submitted the form again just now
and this time the screen displays "Thanks for getting in touch with us", not just the same form
weirdly, the first time, the form asked about my phone number and other details; not so now
Cow
Cow
hmm
i'm preparing for my own war against GH here
i'm polling a few of my Law Enforcement sources in the Feds to see if they can pressure GH as well if SE can't push it
Cow
Cow
:x
15:38
so the War is approaching
> This is an anti spam tool for detecting spam. I am fine if it is not generally available except for the appropriate age group if that is a concern, please don't mark my account down for trying to make the internet safer.
Reword?
@ThomasWard calling in the big guns, eh?
militant as ever...
"except for the appropriate age group" don't give 'em any ideas, that implies login-required to clone
Cow
Cow
finds pitch fork
15:39
@micsthepick Maybe not a popular suggestion but have you tried ChatGPT for rewording?
@ThomasWard Inb4 GH locks everything down "Please communicate through our lawyers"
This is what I sent in, you can blame jetlag for any awkward wording.
Cow
Cow
lights the torch
> The primary SmokeDetector repository run by the Charcoal-SE organization along with apparently every single fork has been suddenly disabled without warning or explanation.

SmokeDetector is an open-source spam detector that automatically detects and helps to remove spam posted to the Stack Exchange network, such as Stack Overflow, and has become an integral part of the efforts to keep those sites spam-free. Hundreds of thousands of volunteer hours and hundreds of real-life dollars have been invested in this project.
2
Recommend ya'll sit back and relax - this'll get resolved, there's not much of a reason for us to worry about it. One of the few things SE management is still good at is having wealthy well-connected people in charge.
15:39
Well is there a problem? Does it ci
@micsthepick all GH and Git related actions are broken while its suspended.
Onvey the appropriate info
@Undo CAlling in some favours, eh? Wink wink
in accordance i'm also doing a force git push of master/deploy from what's in Smokey/Cerberus now to my own git as acopy in case we have to get back online fast.
@ThomasWard That one is probably old AF
15:41
Cerberus is my latest instance lol
!!/location
^^ that one
Ooooh
Yep, you're an instance now, Cerbrus. How's it feel?
15:41
For a moment, I felt important T.T
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): How can a startup create a successful digital marketing plan on a limited budget?‭ by Tushar‭ on stackoverflow.com
I'll just close my ports :3
FWIW, GitHub has been tolerant of large projects in the past but eventually they do notice high-volume stuff
we're nowhere near that kind of volume, and we basically never do full clones outside of CI
15:43
@Machavity That sounds like a few orders of magnitude larger
cocoapods/homebrew were using GH as a CDN, that's what put them on the radar.
That sounds like abuse (or at least misuse)
and for the record I got an email ack for the ticket too around the time I submitted it
@Machavity Size differences aside, that's a fantastic response by that infra engineer. Really well-written.
I suspect Microsoft ownership has lowered their tolerances considerably
15:45
@Machavity That is... a confusing abbreviation to use in this context
@Spevacus It's still probably one of the best community responses I've ever seen. Open, honest, and the CP team was responsive in making changes
definitely not a volume thing, this is going to be a bad-words thing
@Mithical Microsoft has a hatred of spam and stuff. It's a Microsoft problem
as long as we get this solved we'll be fine
15:46
@Mithical Yeah, shoulda remembered the context here
they whacked another one from ye olden times too
thus not a volume thing
@Undo WORST CASE we move the large huge blocklists, etc. to a separate source or a git subrepo that pulls form elsewhere
but i digress
@Undo was this a fork with a peculiar name or a completely independent copy?
completely different thing
in probably 2016 I messed with the NLP of the day
Then it's probably some content in there that was also in the larger SD repo
15:47
I forget what was in there, but probably a bunch of stuff from metasmoke
Certain keywords / lines
@ThomasWard Ya'll can do what you want, but at some point should consider whether the world is saying it just doesn't want the service we provide
@Undo oh it's always on my mind
Fighting with people to do something good for them is draining
but, can't touch private git hosting so :p
15:49
can't touch it yet
No good deed goes unpunished
That's a little dramatic
@ThomasWard you just haven't angered enough Brazilian judges
@Undo well if it's not internet-exposed then they can't touch it at all muahahahahah
I mean
i could just shut off Metasmoke too and piss off everyone
!!/location
@SmokeDetector Didn't realize we were up to 10-char commit short-hashes, looks kinda cool
@ThomasWard Metric for impact on society: How many people you could piss off but choose not to
11
Oh... reads transcript, it isn't just gone/removed for me
@cocomac hreading stars would've been sufficient too :)
GitHub staff really came back from Labor Day weekend and chose violence :P
This is one way to get anyone who's participated to Smokey in the past to check in...
15:52
Blow up the repo, -> See, our chatroom is active with actual people!
@Spevacus with a side of (metaphorical) nuclear warfare too.
need shades with all these diamonds sparkling
@Cow Heh. It can get pretty loud, since I prefer mechanical keyboards. The Model M is my favorite, but I have a limited stock of those. I also recently bought a board with Cherry MX Green switches, which are like the MX Blues, but higher actuation force (so more like the buckling springs in the Model M), and I quite like that one. I like the clickiness of the MX Blues, but they're too soft. I can't rest my fingers on them, which means I am using muscles to hover my fingers off the keys, which leads to increased fatigue. Sadly, all of this meticulous preference goes out the window when I have to use a laptop. My typing speed is very much dependent on the keyboard. The 120 WPM is a realistic number on a laptop with a decent keyboard, but it goes higher under ideal conditions.
@GeneralGrievance Exactly that is why I've never been interested in learning Dvorak or any other alternative layout. I switch around to different machines all the time. I don't want to sit down somewhere and be completely lost.
@Spevacus Err... wow. That's probably some kind of illegal.

« first day (3943 days earlier)      last day (171 days later) »