adding insult to injury ... prolific spammer www.unair.ac.id and www.geeksforgeeks.org share a pair of Akamai IP addresses which I had been hoping I could blacklist
@tripleee Added solutionsdesign\.tech to watchlist However, the blacklists were not reloaded at this time. The most likely issue is another change was made on SD's master branch on GitHub and everything is waiting for CI to pass and MS to update the deploy branch. That could take a few to several minutes. If SD doesn't automatically reload the blacklists or automatically reboot after that time, then someone should investigate why that hasn't happened.
@SmokeDetector naa Azure sometimes gives a $200 credit to new users. I’m guessing this user didn’t receive it and doesn’t know better than to ask for help in an answer
@RadvylfPrograms Thanks for the heads-up, but, no, we're good. We use ChatExchange, which no longer uses openID, unless during the login process SE explicitly instructs us to.
@Spevacus Yes, this should be a non-issue for us at this point. The work for it was done back in 2018-07. There is some residual code that does reference openid, but that is only used if SE responds to the current authorization flow with a popup indicating that it should be used. I expect that portion of the code hasn't been actually used in a long time, but can't confirm that it's impossible for SE to send us there, so I haven't submitted a PR to completely remove it.
Cool, sorry for bothering y'all then. It's been a bit of a headache over in TNB since several of our bots all used either the same library or shiny new ones...which used the same login flow the old one did since we used it as a reference :p
@RadvylfPrograms Giving us a head-up is not a problem at all. We appreciate it. Thank you. I'm sorry the information about it going away didn't get to y'all sooner, so you could implement something else prior to everything breaking. I would have hoped that SE would have identified which users were still using that flow and specifically informed them that it was going away.
@RadvylfPrograms @Makyen There were some announcements, like this one in 2018. It was a known problem then.
All of the chat libraries and bots that I know of use openid.stackexchange.com since that’s what the web login uses (or at least it did when we reverse-engineered it). We can update everything to use a new system, and some of us in SOBotics want to write up some unofficial documentation on login and chat, but advance notice of any breaking changes would be awesome, so we don’t wake up one morning to find everything falling apart (especially Smokey). — NobodyNadaMar 7, 2018 at 6:07
This user was created today, and the user has written 3 answers, of which 2 has been removed as spam (visible to +10k users):
How to connect to remote desktop, Kali Linux from ubuntu?
Multi-user remote desktop from windows to linux machine
Multiple users use linux pc at the same time
All answer...
@Ethan A normalized version, {{'18448908582', '8448908582'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number 18448908582 to determine which entries on the number lists match that pattern, which would tell you: Matched by 844-890-8582 on line 656 of blacklisted_numbers.txt: 18448908582 found normalized
This user was created today, and the user has written 3 answers, of which 2 has been removed as spam (visible to +10k users):
How to connect to remote desktop, Kali Linux from ubuntu?
Multi-user remote desktop from windows to linux machine
Multiple users use linux pc at the same time
All answer...
