|
Top-level
 @John Use a private web browser. They probably won't appear at all. I think Mastodon checks whenever you click on a notification, to see if it exists and to expand the thread. That's why deleted replies still appear in notifications. They're still in the browser's storage, but when you click on them, the React code does an API call and then removes it since it no longer exists. You should be able to see the calls if you open the dev tools. 6 comments
Maybe I do need to summon the great @Gargron ... is this a feature of 3.2.1 - disappearing notifications once read? Seems that way  @Gargron It's the same error 500 feature I hunted down when people have incorrectly upgraded to master branch but I did not in this one... unless git totally failed me and it could have @John You can get certainty about this by looking into the logs of the mastodon-web unit @Gargron That's what I did, and traced it back to the same guy who did this in the issues list. Luckily I have a testing space I can pull from :) |
Gregory's Server
@djsumdog Thanks! I did have an issue with migrating to the master branch on accident (different instance) and saw notification issues that @Gargron pointed out was due to a missing column (maybe this read column now in 3.2.1).