While those two may be of concern, they are also moderately normal. More importantly, they shouldn't affect the token or feedback. Both AIM and FIRE use the WebSocket.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching product name in body, potentially bad ns for domain in body, +2 more (495): [email protected] by maurrocardeenass on askubuntu.com
@AJ Can you try disabling Privacy Badger for this site, at least temporarily?
When it's asking every 15 minutes for a token, are you leaving a tab open to the chat room, or reloading the chat room? In other words, it is asking you for a token in the same tab after you've already been giving feedback in that tab?
@Makyen 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.
[ SmokeDetector | MS ] Bad keyword in title, blacklisted website in title, pattern-matching website in title, potentially bad ns for domain in title (299): topwellnessblog.com/vito-brain/ by nogenelo on askubuntu.com
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, +4 more (499): walgreensdiet.com/marine-flex-ultra/ by qmishalrow on askubuntu.com
@AJ Check to make sure you don't have two versions of the userscript installed and running, possibly with an additional userscript manager. When it looses the token, does it also loose any other settings you've changed in FIRE (e.g. where notifications are displayed, for how long they are displayed, or other things you can set from the settings dialog)?
In the console, do you get reasonable output from console.log(localStorage['fire-user-data']);? It should be a JSON string with some values. If you copy the text output to chat, or other public place, remove the value from stackexchangeWriteToken and metasmokeWriteToken, as those should remain private.
@Makyen 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.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, potentially bad ns for domain in body, potentially bad keyword in body (295): weight reduction. Shedding pound by joewestonnn on superuser.com
@AJ Do you see toastr notifications saying "Can't send feedback to metasmoke - not authenticated."? If you do, then you should see such a notification in a prior action before your click on the FIRE button shows the Request Token dialog.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, potentially bad ip for hostname in body, +2 more (395): What Is Garcinia Vita Uk? by helenhukil on askubuntu.com
@AJ Hmmm... It wouldn't necessarily be at the same time. It could be separated by any arbitrary period of time, but would be at the most recent time feedback and/or flagging via MS is attempted prior to being asked again to request a token. The only path that should be available to clear the token from FIRE should display that notification when it does it. Any other way should result in there being more things lost.
If it's done by some other script, there should be more lost, or it's specifically only clearing that value (i.e. it's intentionally clearing just that value).
I don't get such error, so it's probably some script clearing this value. Can you tell me which specific value I should look for next time when it asks me for a token?
metasmokeWriteToken is the value that must be missing for the Request Token popup to be shown. To be specific, the JSON that's in localStorage['fire-user-data'] when converted to an Object has to end up with trying to access the property metasmokeWriteToken as a falsy value.
If it's another script, then it's something really specific. Just clearing the complete value from localStorage['fire-user-data'] would result in either loosing other settings or very noticeable malfunction.
[ SmokeDetector | MS ] Bad keyword in answer, blacklisted website in answer, pattern-matching website in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer (259): Printer is not printing by sophiapage on unix.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title (294): Wonder Full Keto Buy Niow! Reviews by wozokozo on drupal.SE
I did post code in here about 1.5 years ago which would result in the MS token being cleared, but given that it has to clear only one value in a JSON string, it's not something that would happen for most bugs. You'd basically need code specifically trying to modify that value (or someone using a RegExp to modify it and not getting the RegExp correct).
You should be able to go to your list of authorized apps to see what apps MS thinks you've authorized. As far as I know, you can have an effectively unlimited number of tokens authorized for each app. Looking at mine, I have 16 tokens authorized for FIRE (as a result of script testing and not manually revoking access for tokens).
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, potentially bad ns for domain in body, potentially bad keyword in body (296): Workbench installation error by Fastrunt87 on askubuntu.com
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (160): How offensive is 他妈的? by somebody on chinese.SE (@TetsuyaYamamoto)
@Makyen That pattern looks like it's already caught by Pattern-matching product name in body, Potentially bad keyword in answer, and Potentially bad keyword in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Bad keyword in answer, Bad keyword in body, and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen 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.
@Makyen That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
@Makyen 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.
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, pattern-matching website in body, +5 more (594): walgreensdiet.com/marine-flex-ultra/ by aanniebush on graphicdesign.SE
[ SmokeDetector | MS ] Blacklisted website in body, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title (199): https walgreensdiet com marine flex ultra by kaathyfarmer on superuser.com
> Url in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 12-24: lookchup.com Potentially bad keyword in title - Position 12-24: lookchup.com Potentially bad keyword in username - Position 12-24: lookchup.com Url in title - Position 0-24: https://www.lookchup.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-12: lookchup.com Potentially bad keyword in title - Position 0-12: lookchup.com Potentially bad keyword in username - Position 0-12: lookchup.com
