angussidney

@Shadow10YearsWizard hmm, looks like it's working now. Not sure what happened.

!!/errorlogs

Or alternatively the MS Rails server dies, then nothing works

We've also had issues recently with our Redis server, which we use to cache certain things, particularly on the front end of metasmoke. So when it breaks, it makes MS virtually inaccessible to users. However, if the main MS Rails server is still running, background tasks will still run fine since they don't rely on Redis. So sometimes, MS will be down, but autoflagging will still work

@ShadowWizard ...it's a bit complicated. We've been having a few issues recently where a bug on SE's side has been permabanning our IP from the SE API, which breaks autoflagging among other things. Every time that happens, we have to get Nick Craver to manually clear the ban. More info on that: chat.stackexchange.com/transcript/message/50019727#50019727

@AskQuestionWizard that's very true - but us meta folks always like to dig into things :)

I just dropped in after seeing the big blog post, and I was surprised how little discussion their is about it

Great to see you too

@M.A.R.TheChemicalWizard o/

Allspam will only work for users with less than 15 posts - it can handle more because it has a built-in delay in message posting to prevent itself from being ratelimited

@ShadowWizard you can only report up to 5 posts at a time, and after reporting more than one post you must wait for 30 seconds before reporting any more, to prevent Smokey from being ratelimited in chat

If it ever becomes an issue, I'm sure we could contact SE and they wouldn't have any issues with raising our limit again

However, the API quota isn't too much of an issue - usually, we finish up the day with around 25% remaining (we carefully provision how we use the quota to avoid using it all up)

@ShadowWizard as iBug said, we don't have any specific ratelimiting on that command - to my knowledge, the only commands with specific ratelimits are the !!/report and !!/allspam commands. The !!/test command doesn't make any API requests to SE, but it may make requests to some 3rd-party sites for DNS info, toxic post detection via Perspective AI, etc

@ArtOfCode is the source for that on GitHub somewhere by any chance?

@MEEisJohannGambolputty... do you think we should flag it then?

What do you think?

The way they chucked a link to a temp mail service on the end there feels a bit spammy

Always helpful to get a second/third opinion

Thanks for your advice

@JourneymanGeek ok, I just couldn't seem to find a conclusive parttern in their past spam posts

Here's a list of previous posts that we've caught by that domain: metasmoke.erwaysoftware.com/domains/19275

@SmokeDetector What do you all think about this post? User is new today, first and only post, linked site seems to show Windows 10 (not 7 as in the question)

Anyway, gtg

@JourneymanGeek Everything I say is assuming that the community response to this post is positive. If it's not, then we're not going to switch this on - at least without another large discussion with everyone who should be involved.

@JourneymanGeek yeah, that was wrong

@Rob I still stand by my argument that a very small amount of work for one person is not unreasonable to expect, compared to the work required for us, when we have already determined that the status quo is 'turn it on'

@Rob that's why we will let people opt-out whenever they want. If a mod or community is against the status quo, let us know and we will comply

@HTTP it will appear on the sidebar across every site on the network. It's impossible to miss.

@Rob FYI the entire premise of our argument is that Shog will [feature] the Meta post so that it appears across the whole network. If it doesn't.... then we can agree that not enough has been done to let people know

Compared to the work we have to put in for the other way around

@JourneymanGeek sounds awesome, thanks :)

Also, there have been a number of complaints by non-mods about how non-mods are being treated as insignificant peasants in the decision process

Sure

Also, @JourneymanGeek, would you be willing to remove the sentence in your post regarding flags being cast without the user's knowledge? It's simply wrong, and kinda paints a picture that our system is using people's accounts without their permission, which I think is unfair. That sentence was the main reason why I downvoted.

@JourneymanGeek I'd like to see who voted

Lol, ninja'd

@Rob not all mods read the TL

By the way, I want to say it again - we may disagree with some of your opinions, but we don't hate you for it. Sorry if it comes across that way. All we want is a discussion :)

Anyway, I'm going to stop chatting now, I feel like I'm piling on

@JourneymanGeek we're focusing on outliers, not the average time

@HTTP we've tried ML, but it's always been vastly inaccurate comared to our existing methods

I honestly don't see the difference between opt-in and instant opt-out. We're not taking that decision away from you, instead we're asking the overall community for their opinion on what the default should be (whether it would be reasonable to turn it on) until any communities/mods ask to turn it off. If you want it off, tell us now.

sd delete

Please direct all conversation, feedback and commands to Charcoal HQ. The aim of this room is to provide a clean feed of all new SmokeDetector reports for easy handling - so if we can keep it that way, that'd be great. Thankyou!

room topic changed to The Fire Department: Where smoke detectors keep us on our heels all day. No chit-chat please, just new reports. Ping @angussidney in chat.stackexchange.com/rooms/11540/charcoal-hq if you want access to the room/smokey privilegess. (no tags)

Other than feedback, please keep the chatter to an absolute minimum in here, as that is the purpose of this room.

Ping me in Charcoal HQ if you want access to this room or want to be added to the smokey privilege list for this room.