"XXX needs your permission to enable desktop notifications" - no you *really* don't. Because I *already* *actively* took away your capability to do notifications because *I* *do* *not* *want* your notifications!

Since when did it become OK for software to try and pull a Carthāgō dēlenda est on its users?

To just blatantly ignore user choice and keep nagging? This is even a service I am paying for, for crying out loud.

I hate how technology has become a means for companies to remotely manipulate u̶s̶e̶r̶s̶ herds of assets instead of a tool of enlightenment and liberation.

It didn't use to be like this.
It wasn't supposed to be like this.

@bjonte @Retrograde If this is a web site thing and not some mobile thing, one thing I've started doing is saying "yes" when the web site itself asks, then permanently denying permission when the browser asks. That usually keeps them from ever asking again.

@vertigo @freakazoid @bjonte @Retrograde

I just recently discovered the uBlock lightning bolt tool and it is my favorite thing ever.

@Retrograde As an amateur browser dev here's how I'd deal with this:

First I won't support the same notification API mainstream browsers do, JS requires too much effort to implement & constrains my design flexibility.

Second if I do implement an alternative mechanism (if someone's interested in it) I'd make the button to enable notifications (and live updates) inconspicuous. If it's something readers want they can look for it, rather than having websites beg!

Sign in to participate in the conversation
OldBytes Space - Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!