3 ms·
We do not need to boil the oceans to decide what notifications are spam: We need to recognize the notifications API was a bad idea and should either deprecate i
by ocdtrekkie 1y ago
We do not need to boil the oceans to decide what notifications are spam: We need to recognize the notifications API was a bad idea and should either deprecate it entirely or, like Safari, only permit it for apps installed to the home screen.
- hdjrudni 1y agoI think it has its uses. For apps. I've been meaning to add notifications to my app but I haven't gotten around to it. It's a b2b so it'd be strictly for their benefit, I don't get anything out of it. It's just a very, very small # of apps have useful enough notifications that I'd want to enable them. I wish there was some other way to present "This app supports notifications" and allow users to opt in that wasn't quite so intrusive. Or maybe require that the user spends at least 10 minutes on the site/app before its allowed to show the popup or something. I don't know. The little RSS icons we used to have are maybe not quite noticeable enough.
- mook 1y agoI've seen it useful for things like logs of long running build jobs. But the API should have been done so that notifications can only be registered upon user action, like how pop-up window detection works. But to a first approximation, a function that always returns "no" will probably be close enough for most users. Somehow I don't think their priorities align with mine.
- cosmic_cheese 1y agoTo me the easiest fix is to just default notifications to off for all sites, remove the prompt, and if the user wants to turn on notifications for a particular site they can do so manually. Keeps the functionality while making it impractical for sites to harass users into approving and defeats those stupid in-site “we need to maintain the ability to prompt the user” pre-prompts all in one swoop.