I’m sorry that happened. I’ve never seen stuff like this happen but this is likely because I disable as much shit as I can every time I set Firefox up on a new system, but as you can see from the list of recs I pinked above, it’s a bit of a chore.
There are definitely smarter ways to go about it, like scripting the disablement of stupid shit in Firefox (or using a privacy respecting fork of the browser), but I like to do this / monitor this manually to keep track of any newly introduced anti features.
running_ragged@lemmy.world 2 days ago
I feel like it’s the OS’s job to provide the means to mute or defer notifications in certain contexts, and the games jobs to enter that context in full screen.
halcyoncmdr@lemmy.world 2 days ago
I feel like a year ago, Windows was much better at not interrupting. There is literally a setting to engage Do No Disturb mode when playing a game. But it definitely seems to have stopped doing that from my experience despite that being a default setting and still enabled on my gaming rig. Something changed, and I doubt it’s every game.
the_crotch@sh.itjust.works 1 day ago
I feel like it’s not the browsers job to congratulate me for installing an update that includes new features
running_ragged@lemmy.world 1 day ago
I think that’s a fair position.
But the browser is just an app like any other. Apps have notification systems tied to the OSs notification system. Each app independently decides what they think it important to take advantage of that notification system.
The OS should have a notification system that supports mute/deferrals, and other apps, games, media players or whatever else the use wants should use that system for the users benefit.