Hacker News Reader

Comment by google234123 | Hacker News Reader

That is just next year :P We are already halfway through this year, right?

Anyway, I look forward to every shitty site asking for permission to send notifications adding to the trillions of requests a year...

View on HN

All the denied sites shitting up my notification-apps list with noise isn't welcome, either.

The whole thing's a mis-feature. If it must exist at all, sites shouldn't be able to prompt for it, but simply advertise the functionality and let browsers add a little button or something for the user to actively engage with if they want to see a permissions prompt. Like the way browsers used to handle sites that advertised RSS feeds.

> Users opt into notifications by first indicating interest through a user gesture — such as clicking a button. Then, they’ll be prompted to give permission for your site or app to send notifications. Users will be able to view and manage notifications in Notifications Center, and customize styles and turn notifications off per website in Notifications Settings.

Looks like there will be some interaction required to prompt it.

That being said, hoping there's a browser-level option to just turn it off.

I came here to ask about that line.

Is that user flow described actually a requirement somehow, or is that just an "ideal scenario"? Cause right after that it says "If you’ve already implemented Web Push for your web app or website using industry best practices, it will automatically work in Safari" and existing implementations don't require a button press that they used in their example. Facebook just pops up the browser prompts to allow or block as soon as you visit the page, as do many news sites and other stuff I don't want notifications from.

Maybe the "using industry best practices" part is key, and they somehow will block implementations like Facebook.

It should be a browser-level option to just turn it ON.

This is already the case for the install prompt used by PWA. The browser uses an interaction heuristic to send an event that allows a PWA to show an install button.

> and let browsers add a little button or something for the user to actively engage with

Meh, you'll just get full screen modals begging you to push the button. So long as a feature which (ostensibly) drives engagement exists, every ad based website is going to do whatever they can to get you to use it.

There are some really good use cases for it, but I think the balance is tipped by the far too many bad (for the user) use cases.

Having seen it in the wild I agree that it's more trouble than it's worth, and we'd be better off if the whole feature was ditched until/unless it can get a serious re-think. I'd be very surprised if the ratio of unwanted-to-wanted web-push messages is better than 10:1. I'd not be at all surprised if it's closer to 100:1.

A mozilla study showed that sites already try and show <<100s billion notifications to users a year.

> Notification prompts are very unpopular. On Release, about 99% of notification prompts go unaccepted, with 48% being actively denied by the user.

So 99%+ are spam and the rest are probably users who accidentally hit accept.

For a while I would get web pushes from some new site I just have visited once and accidentally accepted. I had no clue how to disable them for ages until a friend showed me. (Yes I could have looked it up, never reached critical energy)

I have to imagine many people are in the same boat.

But engagement is up 3%!

Reply on news.ycombinator.com