This thread was going:

https://slrpnk.net/post/44026568

comments back and forth until the mod cancelled the post. Probably a rightful mod action as the post was a bit unrelated to the community. I received a notification that someone replied to my comment in that thread before the whole thread was removed.

The notification still rightfully reached me, but it neglected to inform me that the thread was killed. There is still a reply option! WTF? Don’t offer a reply function if replies are impossible. I naturally clicked it and got a blank reply form. I took the time to write a relatively high-effort reply. Then I clicked REPLY. The button even animated to indicate registering my click. But the piece of shit did nothing. The form just sits there, unsubmitted and unsubmittable.

At first it just appears like a slow or unreliable network, because a long pause after a submission is how Lemmy apps behave when the network is stalled. So then I click again, but with concern that I might be posting a duplicate (because indeed that is another Lemmy bug to create dupes like this). Still nothing.

2nd bug: The app decides “fuck it, no need to inform the user”. It was not until I tried to visit the thread that I noticed it was mysteriously gone. And not until I read the modlog that I became informed. So now I have a comment sitting a form that’s falsely presented as submitable. Time wasted, and other user does not see my reply unless I dm them. But if I do that then they may possibly be unable to reach the thread for context.

It’s not merely bad timing. Refreshing notifications long after a thread is removed, even a day, still yields comments with false reply buttons.