undefined | Better HN

0 pointssaagarjha6y ago0 comments

It may not; you'll just get fake notification prompts from the page that will morph intro instructions on how to enable notifications when you click "accept".

0 comments

neurostimulant6y ago

This already happening for quite some time now. Many websites uses OneSignal and their fake prompt looks similar with Chrome's notification prompt (at least to ordinary users): https://documentation.onesignal.com/docs/permission-requests...

int_19h6y ago

From this link:

"OneSignal Prompts are a 'soft request', meaning that they are not invoking the 'hard request' of the browser's Native Permission Prompt. This is important because if a user denies the native prompt, the developer is unable to prompt the user again, unless the user goes through a multi-step process to re-enable these permissions. On the other hand, if a user dismisses a Soft Prompt, the app or website can still present them the option later on."

Speaking for myself, showing such prompts repeatedly is a very good way to ensure that I'll never visit your website ever again. No, I don't care about your mobile app, anymore so than I did two days ago.

tor2916746y ago

But it works on other people, which is why they bothered to create that in the first place.

gdeglin6y ago

Hi. I'm one of the founders of OneSignal.

To provide some context on this, we provide clients with 4 built-in prompting options and we do our best to encourage them to use the one that is best for their user experience.

We definitely want to discourage people from asking for notification permission in an obtrusive way. It's not good for anyone when that happens. We wrote a blog post with some recommendations here: https://onesignal.com/blog/web-push-permission-prompting-cha...

saagarjhaOP6y ago

I'm not sure how to put this, but your product is "abused" to such an extent that I personally took the time to pop open the Web Inspector, find the CSS selector for the notification, and use it to look up your company and mentally blacklist it and make a point of bringing it up by name when relevant: https://news.ycombinator.com/item?id=21848866. Your product is seemingly fundamentally misaligned with how users want to interact with the web, to the point where browsers are implementing behaviors that specifically target your implementation. Your blog post gives me very little confidence in your commitment to making this experience better:

> OneSignal encourages all websites to adopt a two-step prompting system if they don't already do so. This will help prevent the website from being penalized and forced to show a quieter permission prompt if too many users have denied the traditional native prompt in Chrome.

Websites are being penalized for a reason, and you know this. Simply adding another modal is just making the problem worse.

> The easiest prompt to transition to is OneSignal's Slide Prompt. Ideally, however, we encourage users to use the Custom Link prompt.

The Slide Prompt should not even be offered as a transition. It's completely at odds with the intent of this browser change, which is all about user intent. Providing facilities to present annoyances that bypass user interaction is the complete opposite of this.

> Offering a coupon in exchange for users opting-in to notifications.

…no?

Please, please, please reconsider how you are implementing these. If you are genuinely unaware of the widespread misuse of your tools, I'd be more than happy to direct you to numerous examples of zero-click, near-immediate, largely irrelevant faux notification requests coming from websites using your product.

j / k navigate · click thread line to collapse