@BillDubuque Thanks, It's good to be back in the room. Sorry, I forgot about the issue of being pingable. I'll try to make sure that I remain pingable here. I should have already been doing that, but forgot to double check that my browser was continuing to automatically open up the room when my browsing session was restored.
Another time, you can ping a user, regardless of when they were last in the room, by creating a reply to one of their messages. I usually find one I can reply to by searching for someone else @ pinging the person and clicking on the link to see the transcript for that message. Sometimes it's then necessary to click on the "reply arrow" on the left of the message you see in the transcript to go to the message by the user you want to ping, then selecting to reply in the message's popup.
Most, if not all, of the messages which were moved into CRUDE Archive were actual requests, rather than informational messages. I'm sorry if having them there caused you some problems.
@Makyen Btw, did you ever add an option to scrape the titles, etc? For me this is the biggest problem now with the script. It causes much wasted time for me in some cases.
@BillDubuque I've tried a few things. None of which has been fully effective. How effective what's currently in there will be appears to depend on the userscript manager, the user's configuration, and the browser. I still need to implement something that is fully effective.
@Makyen I can test on Chrome, Firefox and Edge (on Win7). It doesn't need to be auto-magic. Even if it requires manual invocation to scrape this is still much quicker than having to manually peruse all the unannotated links (e.g. after a browser crash/reload, or after moving to a long idle device).
@BillDubuque Hmmm... are you meaning titles for deleted questions being added to CRUDE and CRUDE transcripts by the URRS script? I thought we were discussing the Request Generator getting accurate title information when creating requests.
If you're asking about the URRS filling in titles for questions deleted prior to the script knowing of their existence, I'm not sure there's a good solution that complies with what SE has stated as their desires/requirements for how scripts handle deleted questions. I might be able to do something, but I'm not sure anything other than the user actually visiting the question is legit under their requirements.
I have a couple of ideas. But, at a minimum, I'll need to do some experimentation to see what can be done and what I can do to minimize the impact on SE. At least some possible ways of doing that are likely to trigger an IP block, preventing any access to SE for a time. SE recently tightened up their algorithm for determining when to apply an IP level block, so that might get tricky.
@Makyen Yes, I'm talking about about questions deleted before the script can cache them. Recall we discussed this in the past. Iirc you said that you had some ideas about doing this that wouldn't lead to too much overhead. But even if I have to manually invoke it for a one time refresh that's ok by me.
@BillDubuque Yep, I recalled our prior conversation when reading your message about being able to test under win7. Prior to that I had been thinking about the Request Generator. I'm going to need to do some experimentation to see if some possibilities pan out, and, if so, how far those can be pushed. At a minimum, everything I'm thinking of will only work for users with >10k rep. I don't have a possible solution in mind for users with < 10k rep.
Thank you for reminding me that I'm behind in working on this.
@Makyen Thanks much for your efforts. It is, alas, one of the few pieces of state that I can't easily recover after a browser crash/reload or device switch. Making it the last such would be really sweet....
@BillDubuque From this is sounds like it would go a significant distance towards helping you if the URRS just remembered titles (persistent through reload/browser crash/reboot/etc.) for now-deleted questions which it was previously able to get data on while the question was live. Doing that, which is part of what I was thinking about for a full solution, has significantly lower limitations. Basically, it doesn't require re-obtaining the information from SE.
There would need to be some limitations. For example, they would need to only be remembered for some period of time, say several days, or maybe a month, or limited by the amount of storage space used for them. But, overall, storing the already acquired titles is less of an issue.
Being able to transfer them from one device to another would require some external place to put them. A typical implementation for such a thing would require a server of one type or another. That's a significantly larger issue.
@Makyen That would help somewhat. But I forgot to mention that perhaps the most annoying (recurring) instances occur due to timezone differences: overnight someone posts a flurry of links many of which are already deleted by the time I logon in the morning.
