181–190 of 329 posts
Earlier quoted context omitted.
I don’t want websites to be able to send notifications to my phone. Sites abuses this and are always asking on my computer and it’s too easy to accidentally say accept.
> I don’t want websites to be able to send notifications to my phone. You might not, but our users requested desktop and mobile notifications. The notifications let sick patients know when their prescriptions are ready, facilitate care-provider check ups, etc.
Earlier quoted context omitted.
>> it’s a total lack of capability of even the most incremental innovative thinking Honestly, HN is a cargo cult of native only, anti web app sentiment. It’s frustrating.
Or... Your opinion isn’t held by other people, some of whom disagree with your opinion and are expressing that.
The other opinion seems "notifications cannot be disabled, therefore notifications are bad".
If you don't want to see notification requests, you never will. Granted: you need to be able to change settings, in a very restricted environment or with a custom clone of some browser you might not be able to.
For most users, that's not a problem. I'm one of them. I don't see notification requests on my desktop or phone. Neither do I see requests for geo-location, even though the browser is fundamentally capable of providing my geo-location to websites through an API; I've disabled it.
Earlier quoted context omitted.
I don’t want websites to be able to send notifications to my phone. Sites abuses this and are always asking on my computer and it’s too easy to accidentally say accept.
> I don’t want websites to be able to send notifications to my phone. You might not, but our users requested desktop and mobile notifications. The notifications let sick patients know when their prescriptions are ready, facilitate care-provider check ups, etc.
Earlier quoted context omitted.
Yeah, having to click no all the time on desktop Safari is terrible. Also websites have realized that I am going to click No in the browser, so now they popup first asking if I want to allow push notifications in JavaScript so when I click no, they can ask me again later, vs if they popped up the browser and got a "No" there they could never ask me again.
I wish developers could get it through their skulls. I don’t want your notifications. Your app is not important enough that I’m willing to be interrupted by you. The lack of notifications is a desired feature. Please stop using notifications. It is almost always a pathetic attempt to try to “drive engagement” to your app. If I want to run your app I will run it. You don’t have to nudge me into it. The world would be…
I don't want your phone calls. Your conversation is not important enough that I'm willing to be interrupted by you. The lack of phone calls is a desired feature. Please stop using phone calls. If I want to talk to you I will write you a letter. You don't have to nudge me into it.
Earlier quoted context omitted.
> How is Safari not implementing standards seen as a good thing? One, “feature” isn’t the same as a standard. And two, standards aren’t standard. They’re adopted through a dubious process and then ignored by the most powerful companies.
> And two, standards aren’t standard. They’re adopted through a dubious process and then ignored by the most powerful companies. Apple is really the only one these days ignoring these standards. Even if it a "dubious process", if there is consensus among the majority browser vendors I would call it standard.
“Consensus among the majority browser vendors” effectively means what Google does.
Earlier quoted context omitted.
That's true for the users you've seen. My users all open emails with no problem. Now do you see why "the average user" isn't useful to determine how to build something? Even if most people suck at using email, in my app it works well.
So you would agree that some users can prefer notifications over email/sms, or is that line of reasoning only self-serving?
> (Conversely, if Safari refuses to implement some alleged 'feature', it becomes much less useful even if Chrome does implement it.) The fact that Apple refuses to implement basic features in mobile Safari that Firefox and Chrome have had for years now, and the fact that they refuse to allow other browser engines on iOS is the reason why we can't have nice things like progressive web apps. I recently worked on a heal…
Earlier quoted context omitted.
You might want to give the combination of 1Blocker ( https://1blocker.com/ ) and NextDNS ( https://nextdns.io/ ) a try. Personally using both on all my Apple devices and they work great IMO.
Will definitely give 1blocker a try. I hadn't thought of going with the route of tampering with DNS but that's a good idea, same basic idea as pihole.
Moved to AdGuard, seems good for now.
Also, try Hush on iOS, I don’t know the magic behind it but it seems to be much more potent at killing nagging questions.
I love Safari as a browser, but I hate the fact that it neuters the web and makes it feel much less powerful. Web Bluetooth and webUSB are ignored by Safari and unsupported. Notification support is lacking last I checked. No PWA functionality to speak of and webNFC won’t be added. Extensions are lacking largely due to being basically native apps that bring with them all the cost and overhead of being such. As a brows…
On one hand you have people complaining Chrome kills their batteries and on the other you want to have a browser that does push notifications, Bluetooth and usb. I want my browser to be fast and light. These complaints seem to come more from companies wanting to save money and developers too lazy to develop native apps. I don’t want to load a 200Mb progressive web app that goes through 20 layers of abstraction to sho…
I think that Apple don't implement these features because they want to make more money and have developers make apps for their platform for free (and actually collect a fee from the developers that are improving the Apple ecosystem).