@ArtOfCode sorry I didn't see your comment earlier
so like with the bodyfetcher we make one instance of the DeletionWatcher class in ws.py and store it as a global var
this in turn opens up the SE websocket and creates one thread to listen to it forever
DeletionWatcher then maintains a dictionary mapping the action string (so essentially post and site ID) to a tuple with some of the post data as well as an array of callbacks
(the callbacks can also have optional expiration times)
DeletionWatcher.subscribe sends the <site id>-question-<question id> down the websocket if it hasn't already (i.e. not in the dictionary), then also registers an optional callback + expiration time
posts are always subscribed to without a callback in spamhandling.handle_spam just to get metasmoke deletion stats
the other two places are for handling the delay and delete report if post is deleted (usual stuff)
the only other thing of note is that the posts we're listening to are actually pickled
when smokey restarts, it'll use the SE API to check if they were deleted (or cull them if they were marked FP/ignore/whatever). if any weren't, it'll continue listening for them
since there's just one socket it's cheap to listen to posts, we can listen to pretty much as many as we like
I've sent 500+ actions down the SE websocket before and it didn't care as long as you didn't do it too fast
@Undo I'll read it more later, but I wanted to point out that block time isn't a factor in anything
If a room is blocked, then it just stops
The two subscriptions are for deleting the report if the post is deleted and not posting a message to a delay room if the post is deleted (I.e. tavern)
For a project I'm working on, it'd be nice to be able to retract flags through the API.
We allow people to retract flags from the web. Could this functionality be extended to the API? It could work such that you receive a 'Retract Flags' option on calls to /questions/{id}/flags/options, then pas...
@iBug It's almost certainly just a AJAX call. It would be easy to determine how to do so, it just would mean going around the SE API, which isn't "supposed" to be done.
Point is, this happens very rarely, and when it does, people are usually around to fix it themselves. Worst comes to worst, you get a declined flag once a year or so - you signed up for that a) when you enabled autoflagging, and b) when you reduce the weight below the recommended which massively increases the amount of FPs. Utlimately, we don't want to spend a long time building a large hackish solution only for it to be used by very few people, and break next time SE changes something
@Makyen This is a bookmarklet that sends the selected text to Google Translate in a new tab.
I really don't like the stock ping sound here, it's just not that noticeable. If anyone's interested, I found a userscript which allows you to set custom ping sounds (for yourself, not others): SE Chat custom notification sound. It's an updated version of this stackapps post.
@Mithrandir I usually have my volume turned quite low. I hear the others, but not the one for in here. It just uses a different frequency range. Yeah, if I have headphones on, the one for chat.SE does make me jump (literally), which is also an annoyance.
@JohnDvorak Thanks. I'll look at it. For some reason, I've been resistant to adding an extension to do the task, but I don't have a good reason for not doing so.
