@Spevacus In the future, you can see if a watch is already caught by looking at the reasons it was caught. For watch it will probably be potentially bad keyword in.... And you can edit messages to fix typos, SD takes them as "new commands"
@Daniil That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-16: surveymonkey.com, Position 19-26: C3MJFLQ Potentially bad keyword in title - Position 0-16: surveymonkey.com, Position 19-26: C3MJFLQ Potentially bad keyword in username - Position 0-16: surveymonkey.com, Position 19-26: C3MJFLQ
@Daniil reinstalled, recleared the settings, reprovided token (got confirmation token was accepted), reautorized SE. All scripts disabled except FIRE and ublock turned off. Still error.
@Spevacus FIRE is expecting a response from MS that tells it what the error is, which includes not having an account on the site. The code exists in FIRE and has previously worked to report that there's no account for that user. If it's not working, then something has changed on MS or SE.
FIRE specifically will translate the response "No account on this site." from MS into displaying "This post could not be flagged.<br/>You don\'t have an account on that site."
@Spevacus FIRE is expecting a response from MS that tells it what the error is, which includes not having an account on the site. The code exists in FIRE and has previously worked to report that there's no account for that user. If it's not working, then something has changed on MS or SE.
@thesecretmaster in case any of the recent PRs on MS could have broken ^ that
but Internet as a whole took a crap and a lot of services are still restoring slowly
user435118
> If you hear about a Level 3 Internet outage today and haven’t heard this company mentioned before, then you might be wondering how problems involving the Level3 network could take down your access to Yahoo Mail, PSN, Xbox Live, Outlook, BT, Twitch, HBO Go, Craigslist, and other networks/services.
@thesecretmaster At least the Osiris issue is that a room in which SD listens for commands was changed to private, but SD wasn't granted read/write privileges. It affected all SD instances, but Osiris is just the last to be manually updated.
Now there's work to do on SD, so we don't have similar problems in the future:
The temporary solution was to just remove the room from rooms.yml. The next stage is waiting for that site's mods to grant SD access, then reverting the change to rooms.yml. The slightly longer term issue is to catch the error and let SD boot up all the way. If there's at least one debug room that is joined, then report the problem, if not, reboot. The next layer to fix/adjust is to change how SD recovers from issues which result in it crashing repeatedly prior to booting all the way up.
The algorithm we currently use is we just keep reverting to older and older commits. That's good if the issue is that the most recent change on GitHub is what caused the issue, but we've had a number of times where the issue is external to SD.
In that case, what we need is for SD to pull in any new changes on GitHub, so it pulls in any fix that's pushed out. We probably should have it keep reverting, but each time it's going to revert, check to see if there's a new commit on GitHub. If there's a new version, then pull that and try it. If it's still rebooting, go back to reverting from where it left of. Repeat, continuing revert and to look for new commits.
@Makyen It is theoretically problematic to keep reverting, as let's say there is a issue fixed in SD in a commit x; and a moderator who desperately wants to make some damage can cause SD to revert prior to x and then actually cause damage. Maybe there should be some restrictions on how many times SD may revert.
@SmokeDetector Without some stronger indication that this is an actual spam seed, I'm having a hard time seeing this as more than just a run of the mill question. It may be a spam seed, but that's certainly not clear to me at this time.
@SmokeDetector No evidence currently that this is a 'spam seed' as was the reason for the manual report. More information needed to determine if it's actually a spam seed.