Mastodon 3.0.1: I'm looking for a way to disable the "unread notifications" count in the title of the window.

I would prefer to disable this server-side and make it opt-in for users.

I will settle for a way to disable this as a user.

Any ideas? I've been through Admin>Site Settings, User>Settings, User>Notifications, User>Other, and the slider menu at the top of my Notifications column, but I'm notorious for missing options. #mastodev #mastoadmin

It is important to me to note that early in Mastodon's life, showing the number of unread notifications was considered an antipattern and users were vocally pleased that Mastodon DIDN'T do this.

Show thread

@noelle not sure, you'd have to modify the server code that generates the page title

Follow

@noelle github.com/tootsuite/mastodon/

linked the pr in there if you wanna find the "files changed" and undo the change manually

@trwnh My issue is mostly that I don't want to undo the change wholesale, since obviously *someone* wants it, but figuring out Mastodon's user settings system is beyond my Friday-at-10-PM capabilities. ;)

@noelle yeah uh. checkbox somewhere in i think HAML? never actually looked at the settings code but you could copypaste something maybe and edit it to work

@trwnh That said, I am pleased that I'm not the first person to complain; I see that in github.com/tootsuite/mastodon/ @anna (I think?) had the same complaint.

@noelle honestly never noticed it bc mastodon is always focused/pinned for me :roundboi:

@noelle @trwnh it used to show how many unread things were on your home feed it was awful. still, an option would be nice for notifs to help ppl who dont want it

@noelle @trwnh fyi the Glitch-soc frontend doesn't seem to include this change but does have a similar, optional setting (and you can still use the vanilla Mastodon frontend)

@noelle @trwnh just my two cents but as a mastodon admin I have found the approach of "be incredibly personally biased about what features I leave in and which I tear out with prejudice" has worked pretty well

@InspectorCaracal @trwnh The other half of the equation, I confess, is that somewhere along the line my masto fork has managed to get completely fucked up again, and I dare not make changes because it could foul the whole thing up. >_<

@InspectorCaracal @trwnh (to illustrate: Elekk is on 3.0.1. The last tag available to the git on the elekk server is 2.9.2, and I don't know how I GOT to 3.0.1. The last tag listed on the elekk fork on github is 2.7.1, and I don't know how I got to 2.9.2 before I updated today.)

@noelle ooh yeah that's a tough one

if you don't have any customized code yet, though, it's probably just that you pulled from tootsuite and you could update your fork to 3.0.1 and then do your changes on top and pull from your own fork

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!