@ThomasWard FYI I didn't assume that failover was automatic, I pressed the button on MS manually. When the next ping came in, Smokey responded with <location> recieved failover signal, but failed to start up at all.
[ SmokeDetector | MS ] URL in title, bad keyword in body, blacklisted website in body, blacklisted website in title, repeated URL at end of long post: x4up.org/dermatensif/ by nojsentaz on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching product name in body, pattern-matching website in body: Summer Time - Manage Your Skin by joshuwefa on superuser.com
@ArtOfCode @Undo (fixed) if you try to navigate to /admin while not logged in, it throws undefined method has_role?' for nil:NilClass` on line 14 of Admin#index. Maybe change it to something like current_user.logged_in? and has_role dev so that it fails gracefully to a 404 rather than an error page?
[ SmokeDetector | MS ] Blacklisted website in body, link at end of body, pattern-matching website in body, repeated URL at end of long post: Working of Testo Edge Ex by Birs1964 on superuser.com
@SmokeDetector I got a response to that mod flag, and the mod thinks that smokey was right. They gave reference to this linkedin account: cn.linkedin.com/in/margarete-cotty-80197152
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +1 more: x4up.org/nitro-build-plus/ by wvps26 on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body: Nuvella Serum Where to Buy? by nuvellaserum on stackoverflow.com
@Cerbrus What is "Authorise FIRE with SE" meant to actually do? Should I see a different FIRE behaviour? Here clicking that button just opens a new chat tab where there is no FIRE icon and there is no FDSC feedback displayed. The original chat window works as expected. I'm very confused by this :)
@DavidPostill It should request authorization. When you accept, FIRE stores your write token (localStorage), and uses that to get more accurate "available flagging options" than the metasmoke API can provide
Functionally, an authorized FIRE versus an unauthorized FIRE look the same, other than that the "Authorize" button should disappear
What should happen is: 1. Click "Authorize" button. 2. A new window opens where you "accept" 3. That window redirects to this chat with an access token in the url hash. 4. Fire sees the hash, saves your token, then closes the new window. 5. You go back to the old window, it detects a token, and shows you a "success" message.
But I revoked authorise. It didn't ask to accept again. And I still see a button to "authorise" again. So something is not right. It is not showing authorised on the /uses/apps page in ms.
@Cerbrus Ok. FIRE has successfully authorised (according to the FIRE config button). But it is not showing in /users/apps as authorised. So I can't revoke it.
Comment and give them a chance to, you know, not get instantly banned for sharing what they think is a good answer on their blog, when they don't know you aren't allowed to.
@QPaysTaxes you need to watch how you word things. I don't always insta spam things. I obviously think it's spam. It's a one day user + spam link as the username + no disclosure == spam. Please pay attention to how you word things. There's no need to be confrontational
