[2024-08-03T00:04:02 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 720.9 seconds after connection; 420.2 seconds after heartbeat.
[2024-08-03T00:11:06 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 423.3 seconds after connection; 123.2 seconds after heartbeat.
[2024-08-03T00:11:08 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1269.5 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T00:11:16 UTC]: teward/Cerberus: main SE WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 11772.1 seconds after connection; 57.7 seconds after heartbeat.
[2024-08-03T00:13:47 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 158.6 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T00:23:37 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 589.8 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T00:43:00 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1914.5 seconds after connection; 36.7 seconds after heartbeat.
[2024-08-03T00:54:06 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1829.8 seconds after connection; No heartbeats have been received on the current WebSocket.
@Cow I have written a bookmarklet that searches SE for the selected text, as well as copying a watch command to your clipboard and searching MS for that watch.
2
Note that the bookmarklet is slightly smart about how it creates the watch, but only for a couple specific things (currently, spaces and dots), so the watch it generates is not guaranteed to match the text it was generated from if it contains special characters (or the selection is not at a word boundary). It will also, by design, match things that don't contain the selected text verbatim, for text that contain spaces (it accepts any non-word character or an underscore in place of the space).
You'll also likely need to disable your popup blocker on sites that you use it on.
@Cow if you use FIRE (i think you do) in the bottom there is a domains section with a button/hyperlink called SE search. you can click on that to do the search on URLs that @JeffSchaller was talking about (stop being an old man about it Jeff :P).
otherwise the other thing i usually do is run a quick search here metasmoke.erwaysoftware.com/search with the URL with escaping like you would for the watch command. paste the url in the body section and check the box for regex
there are other things you can do, but those are the main ones i think of
[2024-08-03T01:32:05 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 2278.4 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T02:27:59 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 3354.5 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T02:31:25 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 6505.0 seconds after connection; 282.3 seconds after heartbeat.
[2024-08-03T04:19:38 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 2836.6 seconds after connection; 448.6 seconds after heartbeat.
[2024-08-03T05:35:51 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 4573.3 seconds after connection; 576.3 seconds after heartbeat.
[2024-08-03T05:45:10 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 10191.1 seconds after connection; No heartbeats have been received on the current WebSocket.
@VLAZ That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[2024-08-03T06:02:16 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1025.4 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T06:04:08 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 1697.2 seconds after connection; 496.2 seconds after heartbeat.
[2024-08-03T06:34:31 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1935.7 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T06:46:28 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 716.7 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T07:16:35 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1806.9 seconds after connection; No heartbeats have been received on the current WebSocket.
@Dragonrage That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[2024-08-03T07:30:10 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 5161.3 seconds after connection; 408.9 seconds after heartbeat.
[2024-08-03T07:37:25 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketTimeoutException: Connection timed out. 435.3 seconds after connection; No heartbeats have been received on the current WebSocket.
@NisseEngström That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[2024-08-03T07:44:38 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 433.2 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T08:16:07 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1888.8 seconds after connection; 388.5 seconds after heartbeat.
[2024-08-03T09:20:16 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1489.5 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T09:35:38 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 922.6 seconds after connection; No heartbeats have been received on the current WebSocket.
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title (101): bitcoin recovery experts by Tiana Mason on bitcoin.SE
[2024-08-03T10:02:46 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1627.9 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T10:38:21 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 2134.8 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T10:39:00 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1380.8 seconds after connection; 47.0 seconds after heartbeat.
[2024-08-03T10:42:40 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 220.2 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T10:45:06 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 146.7 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T10:54:45 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 578.7 seconds after connection; 277.9 seconds after heartbeat.
[2024-08-03T10:55:21 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1019.9 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T13:18:27 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 8586.3 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-08-03T13:26:06 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 9081.0 seconds after connection; 219.1 seconds after heartbeat.
@JeffSchaller A normalized version, {{'8106199194'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number 8106-199-194 to determine which entries on the number lists match that pattern, which would tell you: Matched by 8106-199-194(?#NO NorAm) on line 4543 of watched_numbers.txt: 8106-199-194 found verbatim
[2024-08-03T13:31:33 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 785.8 seconds after connection; No heartbeats have been received on the current WebSocket.
> Potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-39: reparationchassiscoulissantbruxelles.be Potentially bad keyword in title - Position 0-39: reparationchassiscoulissantbruxelles.be Potentially bad keyword in username - Position 0-39: reparationchassiscoulissantbruxelles.be Potentially bad ns for domain in body - reparationchassiscoulissantbruxelles.be NS suspicious dns2.namecheaphosting.com.,dns1.name…
Yeah, that message is a bit confusing. We're sorry about that. metasmoke posts that message here in Charcoal HQ the first time you give feedback via chat on each chat server, so up to three times. So, it will also be in here for feedback that was given on chat.SO or chat.meta.SE, which is a bit confusing. For being your "first time", MS doesn't take into account any feedback which was done via the MS API (e.g. via userscripts) or on MS itself.
@ElementsInSpace "up to three times". It's only posted in Charcoal HQ. It's posted once per chat server upon the first time you give feedback in chat on that chat server, so once when you first give feedback in chat on chat.SE, once when you first give feedback in chat on chat.MSE, and once when you first give feedback in chat on chat.SO.
