@XanderHenderson @RRL @JoséCarlosSantos @Saad: Amazingly, junk has been undeleted. Also same junk. Same user posts other junk that should be closed.

D1, D2, D3.

D4, D5, D6.

D7, D8, D9.

D10, D11, D12.

C1, C2, C3.

C4, C5, C6.

@user21820 I can't see any titles on your deletion links via the script (but I see them for the closures). Any idea why that is true? Is it a bug in the script, or due to how the requests are composed? If the latter it would be very helpful if you could please compose the requests so that the titles show - just as they do for closures.

@BillDubuque I've no idea because I haven't started to use the script. Also, if I recall Makyen said something about this before; that if the post is not public (deleted) then some info can't be retrieved via the standard API.

@BillDubuque I am not sure that this is "bug" so much as a limitation in the ability of the script to access MSE. Low XP users cannot see deleted posts. The script likely operates as a no XP user, and therefore cannot see the deleted posts.

Or, exactly what @user21820 said.

I am redundant. :\

@user21820 I don't see the titles even before they were deleted. Iirc I did see them in other requests (e.g. some of Xander's), so I think it may have something to do with how the requests are composed. W/o titles I have to manually inspect each question (making it more likely that I will take interest in it and possibly act on it! - something I'd rather not waste so much time on)

@BillDubuque If you want, you can let me know which delete requests you can see the title of, and then I can compare with mine.

@user21820 I can't see any right now, but they are all deleted so it's not a good test. Next time you post a delete request ping me and we can test it.

@BillDubuque Alright, I found another PSQ that isn't yet deleted:

D13.

@user21820 Ok, I see the title on that. It showed "wait" for a few secs so I wonder if maybe there are cases where it times out.

@BillDubuque Ok so it's probably just a site lag issue.

@user21820 Possibly combined with the fact that it doesn't cache the titles so it can still access them after deletion.

@makyen Is it expected that titles disappear after deletion? (see above)

@BillDubuque I seem to recall that the script only gets the status of questions every five minutes, maybe? So there might be some delay between the time that a question is posted here, and the time that the status of the question is meaningful.

cv-pls calculus Missing context or other details; too broad (there are three questions being asked, at least); suffers from FGITW. Complex numbers in polar exponential form‭ - MathGeek101‭ 2019-03-12 14:15:18Z

@XanderHenderson The options menu (gear icon on RHS of input box) shows 2 parameters: "auto-update status: min delay" (default 5 secs), and "Update question status every" (default 5m). Likely the former applies to new messages posted, since I saw it update in < 5 mins. There is also a checkbox ("Change bare question URLs to question's title") which I do have checked.

Ah, I had not played with all of those settings. I see.

After experimenting with disabling "Change bare URL" it appears that the problem is indeed that the script cannot access the titles after the question is deleted. Hopefully there is a workaround, e.g. if caching is not easy then simply not overwriting (blanking) any existing title after a deletion update

@XanderHenderson The question has now been edited to invalidate the two FGITW answers. The question itself has been reduced to a bare-bones PSQ.

@BillDubuque You are correct in your understanding of what those options do. I was writing the following, but you've already determined much of it:

If the script has obtained the data prior to the post being deleted, then the display has already been updated in the DOM and will remain, even if the post is subsequently deleted. The script does not delete it once added. There's nothing the script can do to get that information if a tab is not open to the chat. In addition, currently, in order to reduce the number of requests that it makes and reduce compute load, the script does not update unless the page is actually being viewed.

Not updating when the chat is not viewed is likely causing a significant portion of your issue. An option can be added to have the script update while the page is not viewed, which would almost eliminate the number of times you don't see titles inserted for requests added after you load the chat in a tab, as long as you leave the tab open.

Not updating when not actually viewed was added over initial concerns of possibly making too many requests. However, testing has indicated that updating all the time should not actually increase the number of requests all that much. Increasing the number of requests should only be a problem if you're keeping multiple tabs open with the chat page, or opening a large number of transcript/user/search pages, or if you use other scripts which use a large number of requests.

The "(wait)" indicates that the script has detected the message, but that it is doing any of: A) in the process of fetching the data from the SE API, which can have a human-noticeable delay, under some conditions; B) waiting for the SE API specified minimum delay between identical requests (1 minute), which would not be the case if a new message was shown in chat; or C) that it's waiting for the minimum delay between updates set by the user in the options page (default is 5 seconds).

@Makyen That explains it. Many times the questions are deleted so quickly that it happens during periods where I have not viewed the room. How can I force the script to update say every 5 mins. Surely this can't be an issue since I could actually be doing so myself if I were viewing the room

@BillDubuque I've added a note to have updating while the tab is not viewed as an option in the next version. If you want to modify the script, it's easy to do. To do so, comment out this line and not the next line, but the line below that which contains only }. Do not comment out the single line between those two.

@Makyen Thanks very much. Btw, how does one go about using the script in another chatroom?

i.e. does anything depend specifically on this room?

@BillDubuque If it is a chatroom that is also for Mathematics, then you can add that to the list of room numbers which is in the three @include lines at the top of the script. To have it work properly on the transcript pages for those rooms, the name of the room, as displayed by SE, needs to be added as an additional condition to the if statement starting on line 30.

If you are wanting it to work on rooms that are not for Mathematics, then that is significantly more complex, but doable, as a separate script.

The intended goal is to make the script into something you can enable on any chat page for the site the room is associated with. It's unclear at the moment if that functionality will be in the next main-release version, or if the next main-release will only be available in a list of known rooms.

@Makyen That'll work fine (I'm only concerned with Mathematics at the moment). And yes, I do understand what you meant be removing the "(!document.hidden)" conditionalization (no need to explain basic syntax)

@BillDubuque Sorry, I tend to over-explain, which can be annoying sometimes.

@Makyen That's a good thing, esp. when you don't know the exact knowledge level of the audience. I mentioned that only to help you so you can save some time when explaining things to me.

@BillDubuque OK. Thanks.

@BillDubuque If you'd like, I can add any Mathematics rooms which you or others here would like to the list of those which the CRUDE version runs (i.e. so you don't have to re-make such changes in any new version).

I'd just need a list of the rooms you want.

@Makyen It will likely prove useful for some other rooms (I don't need it just yet)

@Makyen I should provide a bit more explanation, in case someone unfamiliar with the syntax also wants edit their list of rooms. The first 3 @include lines at the top of the script (line 7) are regular expressions containing (?:2165|88696). That indicates the script will run in rooms 2165 and 88696. If you wanted to add the "Tagging" room, which is room number 3740, then you'd add |3740, making it: (?:2165|88696|3740). The same change would need to be made to each of those three lines.

[ SmokeDetector | MS ] Bad keyword with email in body (63): Shares and dividend by Abhinav Ghosh on math.SE

psq math.stackexchange.com/q/3145295/29335

For deletion: DA, DB, DC, DD, DE, DF, DG, DH

For deletion: DI, DJ, DK, DL, DM, DN, DO, DP

For closure: PSQ1, PSQ2, PSQ3, PSQ4, PSQ5, PSQ6, PSQ7