« first day (2781 days earlier)      last day (1336 days later) » 
00:00 - 14:0014:00 - 00:00

14:01
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Transfer files using scp: permission denied by tiennsloit on unix.SE
The quota_remaining property was not in the API response. Error: no method found with this name at 14:03:26 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: no method found with this name at 14:03:31 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/1659590
The quota_remaining property was not in the API response. Error: no method found with this name at 14:03:55 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
We're back!
!!/reboot
Makyen/EC2-linux: Goodbye, cruel world
Hm. I think the websockets are still suffering. I'm not seeing live refresh when posts are voted on or new comments are posted.
Which means Smokey's probably going to be unresponsive for a little while at least.
!!/alive
@Spevacus Of course
@Spevacus Yup
@Spevacus ¯\_(ツ)_/¯
14:23
sdc watch- peoplentech\.com\.bd
Uh oh.
@Ollie That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@Ollie That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
!!/standby-except Osiris
Makyen/EC2-linux is switching to standby
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
iBug/Lily is switching to standby
@SmokeDetector I said it once.
Ohh
sdc coffee
@Ollie brews a cup of Americano for @Ollie
!!/report superuser.com/q/1659748/1097321 "On behalf of David Postill"
!!/location
sdc alive
@Ollie You doubt me?
Given your current state?
I think its websocket connection is shot due to ongoing problems at SE. I don't think we're going to be able to report or get reports for a short while.
Would it be possible to force it?
14:27
Post 1: That does not look like a valid post URL.
Post 2: That does not look like a valid post URL.
Post 3: That does not look like a valid post URL.
Post 4: That does not look like a valid post URL.
Post 5: That does not look like a valid post URL.
Perhaps not.
It's gone already, so it'll need an SU mod.
The domain's already watched, thankfully.
[ SmokeDetector ] SmokeDetector started at rev c17b6b9eb (Makyen: MS instance: prevent automatic revert to earlier commit) (running on Makyen/MS-Relay, Python 3.6.12)
Restart: API quota is 11837.
!!/pull
Yeah, SD, I know you're having problems, but it's not the code.
!!/reboot
teward/Osiris: Goodbye, cruel world
[ SmokeDetector ] SmokeDetector started at rev b7f9f2f9c (SmokeDetector: Auto watch of zoshdigitate\.com by Spevacus) (running on teward/Osiris, Python 3.8.5)
Restart: API quota is 11825.
[ SmokeDetector ] SmokeDetector started at rev c17b6b9eb (Makyen: MS instance: prevent automatic revert to earlier commit) (running on Makyen/MS-Relay, Python 3.6.12)
14:49
Nicolas Naparstek has formally announced that flag retraction via the API is now possible on Undo's feature request.
8
Apparently there's a new version of the API - would that break things for y'all, @Makyen ?
There's been no scan activity for 3 status pings. There may be a problem.
3
Q: API 2.3 Release

Nicolas NaparstekToday we are releasing version 2.3 of the Stack Exchange API. It includes new functionality around Collectives and Articles as well as the ability to retract flags. Check out the Change Log.

7
@Catija No, it should be fine for us and everyone else, as long as the 2.2 version remains available (which it has so far). The 2.3 version of the API has been around for quite a while (years), but undocumented. As far as I'm aware, it's primarily been used in the SE Aps. The addition of being able to retract flags should be great for us.
There's been no scan activity for 3 status pings. There may be a problem.
15:02
If the 2.2 version of the API goes away, then everything that uses the API will need to be updated. "Normal" procedure for something like this would be to have the 2.2 and 2.3 versions of the API active and available at the same time, so that code which was written for 2.2 will continue to run. Applications will, progressively, make the switch to 2.3 over time.
There's been no scan activity for 3 status pings. There may be a problem.
@Makyen Ah. OK. :) That's good. Hopefully people will start moving to the new version, particularly if it has features that are useful.
There's been no scan activity for 3 status pings. There may be a problem.
@Catija Yep, I'm sure they will. This sort of process is usually something that takes years for people to update, unless forced by turning off the old version. I'm sure people will progressively move to the new version, particularly now that the documentation shows that as the one to use, but doing so for each application requires updating the code. As I understand it, the new version is backward compatible, so the changes, for existing functionality, should be trivial to make.
Thanks for the explanation.
15:11
np
@Catija I'm assuming that SE is aware that the SE WebSocket is non-functional at this point. Unlike a few prior times, this time it's completely non-functional and returning errors.
I can double check. They said that the websockets were back up but were returning to order slowly but it seems like it's been a long time. Should they normally come back up more quickly than this? I don't know much about them.
Usually websockets are basically binary
How fast that will happen will depend on the problem, solution, servers, etc. (e.g. they may be rebooting multiple servers).
They said they had load balancing issues.
There's been no scan activity for 3 status pings. There may be a problem.
15:16
@Makyen Can you give me the errors? Dean's asking.
He's seeing some issues, too, so he's looking but it sounds like the error messages could help.
!!/ping
@ThomasWard No such command 'ping'.
hmmmmm
Is dead.
@ThomasWard It's a problem with SE's WebSocket.
15:18
ok
[ SmokeDetector ] SmokeDetector started in reverted mode at rev ce11c0b12 (tripleee: ! Watch IP 162.241.85.198) (running on teward/Osiris)
[ SmokeDetector ] SmokeDetector started at rev c17b6b9eb (Makyen: MS instance: prevent automatic revert to earlier commit) (running on Makyen/MS-Relay, Python 3.6.12)
@Catija It looks like the errors are generated in the browser. Firefox shows NS_ERROR_NET_RESET. When attempting to connect, there's just no response. The connection, from the WebSocket protocol's POV, doesn't open.
Restart: API quota is 11816.
... and now I'm getting a "normal" response...
15:25
Dean kicked it and it's actually coming back now.
!!/pull
I even got an inbox notification.
@Catija Great! That's a really good indication. :)
!!/reboot
teward/Osiris: Goodbye, cruel world
[ SmokeDetector ] SmokeDetector started at rev b7f9f2f9c (SmokeDetector: Auto watch of zoshdigitate\.com by Spevacus) (running on teward/Osiris, Python 3.8.5)
Restart: API quota is 11781.
[ SmokeDetector | MS ] Messaging number in body, pattern-matching email in body (154): Making a letter head for certificate page of thesis by Ryan on stackoverflow.com
16:19
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Images storage performance react native (base64 vs uri path) by Sowthri Ganth Selvakumar on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): makefile.unix:188: obj/magirpc.o Error 1 when compiling ✏️ by swanserquack on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): why wont it let me type anything in the vm? by Sling Ring on askubuntu.com (@Ollie)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Solar Charging for 4 x 18650 (Bat) & 4 x TP4056 ✏️ by John Connor on electronics.SE
@SmokeDetector fp- Will need an extensive edit.
is something like this spam seed / probable spam seed, or just blatantly off-topic garbage?
It's gone @hyper-neutrino.
lemme get a screenshot real quick it just got deleted
@hyper-neutrino just looks like garbage.
16:30
alright, thanks. just making sure it didn't need a report or spam nuke or anything
np
[ SmokeDetector | MS ] Link at beginning of answer (34): mechanical load of an alternator by Rui Carvalho on electronics.SE
user435118
@Makyen Will we utilise the functionality to retract flags via the API?
[ SmokeDetector | MS ] Link at beginning of body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title (43): A great website - Hotnewsbox by Bobotsang888 on superuser.com
@Xnero Given that we were the ones to request it (actually Undo), and it's something we've wanted for a long time, I'd be surprised if we didn't use it. When that happens, however, is a different question.
16:38
tpu- feedback received on [MS] A great website - Hotnewsbox
sdc watch- hotnewsbox\.com
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
Deng it.
@hyper-neutrino It might be a spam seed, but without seeing that some spam gets posted on it (commonly by an associated account or the same user), we assume good faith and presume that it's just a user asking a really off-topic question.
@Makyen Okay, thanks for letting me know :)
16:40
np
Thanks for checking.
16:52
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Help with finding a password with a brute-force attack by Thiago Costa on softwareengineering.SE
[ SmokeDetector | MS ] Link at beginning of body (40): c++ making a game of chutes and ladders by Simply Trestin on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): What are the best tools for coverage gathering for c? by Ilya Zlatkin on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Problem with Youtube API into the Academy LMS by Sergio Cordoba on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, username similar to website in answer (67): What is IP squat space by Brander Group on networkengineering.SE
tpu- feedback received on [MS] What is IP squat space
@SmokeDetector Undisclosed affiliation, username is identical to host name.
However, it's vaguely relevant and may not warrant a spam flag.
Left a comment. We'll see. Can always flag later.
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, blacklisted website in answer (265): What substances should you avoid contact with your bare hands? by Amy on diy.SE
@hyper-neutrino Could be either. If this was on code-golf, there's a good chance it was indeed spam. But as Makyen said, we don't know.
[ SmokeDetector | MS ] Bad ns for domain in body (96): Reparar arquivos excel usando python by Luiz Felipe de Barros Jordao C on stackoverflow.com
@DavidPostill Post 1: Could not find data for this post in the API. It may already have been deleted.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): weird numbers in http response body during python socket programming ✏️ by a0zplt on stackoverflow.com
17:12
sdc watch brandergroup\.net
user435118
@Makyen So what needs to be happen to use it? Do the exact specifics of what we want to use it for need to be decided? Does code need to be written to match that specification? Or both? Or something else?
@Xnero Yes.
user435118
@Makyen Yes to what?
17:17
Given that we've currently been operating for quite a while under the presumption that the ability to retract flags was not going to be done, I imagine there's a lot that needs to be decided, coded, tested, and talked about before we start seeing use of the ability to retract flags.
@Xnero All of the questions you just asked. I know that it's a bit flippant as an answer, but, yes, what, exactly, we desire to have happen needs to be figured out, code needs to be written/tested, but before the code can be written, we'll need to test the API calls to make sure we understand how they are really supposed to work, and that they do work.
If an MSE diamond wants to, you can report this spam. It seems I tried to report it earlier when SD was not getting reports. It's not a big deal, because the spam domain is already recorded in MS.
I deleted that. :P
You want me to undelete, report and delete or is it necessary?
17:31
No, it's fine. We have a record of the domain in a previous spam post, so it's not a big deal. Thanks.
@Xnero At least from my point of view, what will first need to happen is some experimentation to verify the API functionality and that we understand how it works.
Then, or in parallel, think about what features we'd like to see from MS. As I see it, we want something along the following (cc @Undo (and ArtOfCode, who isn't pingable) as you've both certainly thought about this and have a high probability of being the ones doing much of the work):
⠀⠀A. The token container functionality expanded to accept retraction requests and perform that action.
⠀⠀B. The code which detects that a FP/NAA feedback has been given on an autoflagged post be expanded to automatically retract autoflags when it gets such feedback. I'd like to see the following wrt. auto-retraction:
⠀⠀⠀⠀1. Not auto-retract an autoflag if that user has given TP feedback.
⠀⠀⠀⠀2. Delay auto-retraction of flags for some number of seconds (e.g. 10) in order to account for someone making a mistake in feedback, which is not uncommon. Only actually auto-retract after that time if there's still non-TP feedback on the post (i.e. give the person some time to correct their feedback mistake). This delay could be short-circuited if there's more than one FP/NAA feedback on the post.
⠀⠀⠀⠀3. Don't auto-retract flags placed manually.
⠀⠀⠀⠀4. There's likely more I'm not thinking of off the top of my head.
⠀⠀C. Expand the MS API to include an endpoint which allows MS API requests to retract flags.
[ SmokeDetector | MS ] Mostly punctuation marks in body (28): Read Ad to Wishlist data from Facebook API by zzstar on stackoverflow.com
[ SmokeDetector ] SmokeDetector started at rev 6b453a9c9 (Makyen: MS instance: prevent automatic revert to earlier commit) (running on Makyen/MS-Relay, Python 3.6.12)
[ SmokeDetector ] GitHub Actions: success on eeed611 by makyen in the master branch
CI on eeed611 succeeded.
!!/pull
[ SmokeDetector ] SmokeDetector started at rev eeed6116c (Makyen: Add command line option "no_deletion_watcher".) (running on teward/Osiris, Python 3.8.5)
Restart: API quota is 10123.
user435118
18:06
@Makyen Any timeframe on that?
@Xnero When it gets done. Basically, no, there isn't a timeframe at this time. Seriously, it's only been a couple/few hours since it was announced that it actually had happened, so people haven't formed a response or made decisions yet. There's also a bit lower activity on it right at this moment as a result of it being pre-announced.
Please also keep in mind that it's the middle of the work day for a portion of the people who work on the project, so they may not be able to drop everything just now, even if it's something they really want to work on.
18:31
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Will a motor with 1,16Nm rotate a 50mm gear moving about 12K by LeandroIP on engineering.SE
18:44
!!/bisect banglanotice.com
@Spevacus Matched by banglanotice\.com on line 30292 of watched_keywords.txt
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad keyword in answer (2): Beautiful soup div with class and id both by Bilal on stackoverflow.com
[ SmokeDetector | MS ] Bad ns for domain in body (96): Repair excel files in python by Luiz Felipe de Barros Jordao C on stackoverflow.com
[ SmokeDetector | MS ] Offensive body detected, potentially bad keyword in body, toxic body detected (102): Printer Deployment via email address with IP address ✏️ by Kodo on stackoverflow.com
[ charcoal-se.github.io ] GitHub Actions: success on 47b3bd9 by iBug in the site branch
[ charcoal-se.github.io ] GitHub Pages: success on be6f6e9 by github-actions[bot] in the master branch
[ SmokeDetector | MS ] Linked punctuation in body, one-character link in body, potentially bad keyword in body (42): Using PHP how can I develop a search engine? by Shaherbano Mirza on stackoverflow.com
sdc watch totalsportek\.app
19:11
@10Rep That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
19:23
[ SmokeDetector | MS ] Bad keyword in body (95): Code for Relative Strength against Index ETF by Alex G. M on stackoverflow.com
@metasmoke Might be a spam seed, but seems very unlikely.
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad ns for domain in title (2): gigarettes.com UK by oliver vinchenco on webapps.SE
tpu- feedback received on [MS] gigarettes.com UK
!!/watch- gigarettes\.com
API quota rolled over with 9121 requests remaining. Current quota: 19999.
stackoverflow: 1542
math: 751
ru.stackoverflow: 533
physics: 441
superuser: 439
es.stackoverflow: 434
askubuntu: 302
unix: 251
electronics: 251
stats: 241
pt.stackoverflow: 232
gis: 217
tex: 185
mathoverflow.net: 174
blender: 172
serverfault: 171
salesforce: 158
codegolf: 154
diy: 127
english: 125
apple: 117
magento: 114
ethereum: 109
dba: 108
scifi: 108
ell: 104
datascience: 92
law: 88
wordpress: 87
chemistry: 84
meta: 81
worldbuilding: 81
mathematica: 74
sharepoint: 72
money: 70
codereview: 67
[ SmokeDetector | MS ] Pattern-matching website in answer (77): What generic icon could be used to symbolize a brand (McDonalds, Apple, etc..)? by Cowboybowline on graphicdesign.SE
20:00
sdc watch jojorecipes\.com
sdc watch emojikeyboard\.top
[ SmokeDetector | MS ] Link at beginning of body (40): Looking for a famous event free APi? by ShadowHunter on stackoverflow.com
sdc watch- waidapi\.com
PR#6567 ("10 Rep: Watch waidapi\.com") opened by SmokeDetector
sdc approve 6567
fp- feedback received on [MS] Repair excel files in python
[ SmokeDetector | MS ] Link at end of answer (61): Running Visual Studio without Admin Rights by steve h on superuser.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer (1): Administrator access to EJBCA gives "intrerrupted while the page was loading" error by Alex G. on stackoverflow.com
20:17
[ SmokeDetector | MS ] Bad keyword with email in answer (85): How to extract number plates from a video of moving vehicles? by Zahid hussain on stackoverflow.com
iBug/Lily: Executing automatic scheduled reboot.
Makyen/EC2-linux: Executing automatic scheduled reboot.
21:08
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How to beat level 31? ✏️ by Captain Fancypants on gaming.SE
fp- feedback received on [MS] How to beat level 31?
21:58
[ SmokeDetector | MS ] Few unique characters in answer, mostly punctuation marks in answer (124): Lower CS:GO Volume When Alt-tabbed by Max Owen on gaming.SE
naa- feedback received on [MS] Lower CS:GO Volume When Alt-tabbed
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Objects in texture and material view appear black by ssss on blender.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, username similar to website in answer (67): Open two months in datepicker by Seokaos on stackoverflow.com
@SmokeDetector tpu- copied from accepted answer stackoverflow.com/a/43442498 with spam link added.
sdc watch seokaos\.com
[ SmokeDetector ] Blacklists reloaded at rev f7934007c (SmokeDetector: Auto watch of seokaos\.com by cigien) (running on teward/Osiris)
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): makefile.unix:188: obj/magirpc.o Error 1 when compiling ✏️ by swanserquack on stackoverflow.com
22:39
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, blacklisted website in answer (265): Account/Contact sharing issue by Rosalyn on salesforce.SE
tp feedback received on [MS] Account/Contact sharing issue
23:01
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How to remove any kind of selectable fields in PDF by Whimper on ebooks.SE
23:55
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 6b453a9c9 (Makyen: MS instance: prevent automatic revert to earlier commit) (running on Makyen/MS-Relay, Python 3.6.12)
00:00 - 14:0014:00 - 00:00

« first day (2781 days earlier)      last day (1336 days later) »