@SFTP I almost feel bad for the regular nonsense people. Normally takes 1-2 mins to nuke stuff, but today it's like opening a door and finding a pack of hungry wolves
[:43700867] Blacklisted user - blacklisted for //stackoverflow.com/a/49557657 (https://m.erwaysoftware.com/posts/by-url?url=//stackoverflow.com/a/49557657) by the metasmoke API
It just locked me out the room because "Only nominated users can talk here" and I pressed the request access button and about a minute later it just reloaded with the chat box. Anyone else experiencing the same thing?
@YvetteColomb @Videonauth @Glorfindel @K.Dᴀᴠɪs @JF @CalvT븃 AIM: the error reported when chat first loads is a problem introduced in MS with yesterday's deployment (GitHub Issue) @ArtOfCode is already aware. There's not much AIM can do to alternately get the desired data (V1 API might work). AIM could change to just not try, but functionality would be reduced, and it'd need to change back once MS is fixed.
@Makyen yep its ok I deactivated AIM for now and will check in a few days, being very busy IRL lately, so its no big loss for me actually to have AIM deactivated
@Videonauth Then you've been lucky. It's been a chronic issue which pops up at least every few days. I expect we can induce more problems by adding load to MS (e.g. do lots of searches/database access, etc.).
@K.Dᴀᴠɪs Yeah, I'd also experienced a time where it might have been that I didn't get the warning. I've assumed that's an issue with reporting (possibly related to SE scripts not being ready yet). But, I haven't tried to track down why it's not reported on some occasions.
