Any ideas?
Yes.
While I no longer remember the contents of your "Anonymous" reply, I definitely read it because I noted with near certainty
that it was yet another "anonymous" SunnyD reply -- presumably due to the usual giveaways of
a code-free reply of home-spun wisdoms, platitudes, cliches, truisms and banalities,
decorated with extravagant typography, stylistic devices, flowery analogies,
underlines-without-a-hyperlink, and unnecessary quotes.
I could be wrong, but this "no such node" reaping business looks like some sort of harsh new anti-SunnyD countermeasure,
begun in early November 2021.
| [reply] |
G'day eyepopslikeamosquito,
++
Thanks for the information.
I followed your link and can see that this has been happening for a little over a month.
I do recall some reaping (without prior consideration) recently, with a reason of "admin reap" or something like that.
While I'm quite happy for this to be occurring, an improved notification would have been useful
(not your problem — see below).
To pmdev and/or gods:
-
Please change the notification message.
Perhaps something like: "A reply to your X post, from Y, has been reaped and purged from the system."
-
Please update Tidings when changes are made.
| [reply] |
> Please change the notification message.
The message was created instantaneously when you got the reply.
The included [id://node-id] is resolved whenever you read your message box.
That's why title edits by the author are always reflected in your message box.
Someone purged the whole node, such that the title can't be resolved anymore.
But the related notifications are still artifacts in the system.
| [reply]
[d/l] |