Thomas Ward

@SmokeDetector k

@SmokeDetector k

@DanGetz no idea. that's way beyond my understanding of the code base :p

it's been a while since I went code hunting :P

yeah i saw your messages. But I'm deferring to Makyen and others who are more familiar with the code at the moment than I am

if i have to :p

i can close it myself

@JeffSchaller not my fault I missed it but i'm surprised it didn't fail on other commit tests yesterday, etc.

!!/pull

for the typo :P

i already committed a fix

yeah i saw

!!/pull

i've already pushed a fix

GH Actions are failing because a watched NS entry is now NXDOMAIN

!!/watch hoploninfosec\.com

@SmokeDetector f

@SmokeDetector f

you have some pings for private spaces you should read

@Makyen its fixed for now

but i don't expect a quick fix currently for that 403 you're seeing (which is unrelated to the thing that broke SD with the chat changes)

i'll chat with SE staff and see if there's any long term 'fixing' solution we can do or something

so the ongoing known issues otherwise still exist

no chat login repeatedly means SD explodes and there's no antispam controls from Charcoal/SmokeDetector/Metasmoke working

@DanGetz yeah but that's a problem deeper in the system than login not working

with that in place both of the SD instances (mine and Makyen's) should function going forward without issue

@DanGetz yeah that was the ChatExchange problems, which thanks to @JohnB a rapid fix to the new page code was put in that 'restored' the entry points at which ChatExchange under the hood uses to start the login / auth process and such

!!/location

oops?

!!/standby Makyen

and for rapid-fixing things too (especially you @JohnB for poking the new UI to 'match' a little like the original system used at least to enter the login/process flows)

thank you to @JohnB and @Emerson and the vast number of other SE staff who have been dragged into this hell JUST from this here incident with Smokey who responded and are looking to see how we can improve things going forward :D

\o/

!!/pull

oh wait wtf reverted mode

... SONOFABITCH

o.o

... did... this just suddenly start working o.O

!!/pull

!!/location

!!/status

I've got @JohnB privately and we're poking code so

which means that in the next 2 hours there's only a few solutions: revert changes in Chat, or SE has to help us fix CE to adapt to the new environment. (or 3: they adjust the new stuff to add the things that CE is looking for to get into the login flows)

@HenryWHHackv3.0 answer: probably

@Mithical THIS 100% @JohnB

We are aware that SmokeDetector is not working, the fault lies with the changes to the Chat UI and frontend which SmokeDetector is dependent on, which means SD can't login.

(don't ask me how I know, just know that I know)

so it's a legit thing

because StackOverflow Inc. is now the actual corporate entity name

@DLosc StackOverflow Network