News for hackers. Stuff that matters.
Re:WebKit Goals for 2020 by newscracker on Saturday November 09, 2019 @02:03AM (#21490093)
Will 2020 be the year when WebKit, and the Safari browsers by extension, will have full and proper support for Service Workers and PWAs on par with other browsers? I recall reading that Safari lags behind on it, and the allegation was that Apple prefers native apps and doesn’t want web apps to be more popular.
Re:WebKit Goals for 2020 by jxdxbx on Saturday November 09, 2019 @09:27AM (#21491720)
I sure hope not. Why do I want web pages to be able to run persistent background tasks? Such an obviously bad idea. The tragedy is that Apple actually is implementing support for this garbage.
Re:WebKit Goals for 2020 by why-oh-why on Sunday November 10, 2019 @03:39AM (#21497124)
Web pages will never run persistent background tasks on iOS unless you install them. And even then, native apps are also both highly restricted and often have background tasks that you wouldn’t approve of if you knew what they were.
Re:WebKit Goals for 2020 by tannhaeuser on Saturday November 09, 2019 @02:15AM (#21490131)
Hopefully not. I'd hate to click through "This site wants to push new ads to you. Allow notifications?" modals on my shiny new iPhone (edit: in addition to content being constrained to poststamp-sized areas between GDPR banners).
Re:WebKit Goals for 2020 by joneil on Saturday November 09, 2019 @02:22AM (#21490153)
Browser vendors are finally catching on.

From Firefox 72 permission prompts won’t be shown unless they’re triggered from a user interaction.

From the blog post:

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

https://blog.mozilla.org/futurereleases/2019/11/04/restricti...

I’ve heard Chrome is moving in a similar direction

Re:WebKit Goals for 2020 by ignoramous on Saturday November 09, 2019 @03:42AM (#21490407)
When I soft-launched MVP I built to 50 odd users, I was surprised that one user said they uninstalled the app after a couple of days because they simply didn't like the app throwing nagging notifications (it seemed to me, given the nature of the app, the notifications were essential information, but apparently not). Android does let you turn off the notifications per channel per app, but I guess most users aren't aware, surprisingly, even the ones who are annoyed by notifications.
Re:WebKit Goals for 2020 by hqrlk on Saturday November 09, 2019 @03:11AM (#21490312)
So instead of getting a permission prompt on load, I will get it when I first click on something. No thanks.
Re:WebKit Goals for 2020 by royal_ts on Saturday November 09, 2019 @08:13AM (#21491314)
No. It should be done the way like Slack does it: - You want to get Notifications for Messages? Click here

So that you actually know what it's used for

Re:WebKit Goals for 2020 by saagarjha on Saturday November 09, 2019 @08:16AM (#21491331)
I'm dealing with a bug currently where Slack doesn't keep track of whether I've enabled notifications, so I always get the banner. I think I'd go mad if every website did that :(
Re:WebKit Goals for 2020 by lucasverra on Saturday November 09, 2019 @03:26AM (#21490356)
Not if you close Tab before clicking :)
Re:WebKit Goals for 2020 by hqrlk on Saturday November 09, 2019 @03:38AM (#21490388)
There's the middle ground where I can freely browse the page without ever being prompted so see notifications. Apple gets this right.
Re:WebKit Goals for 2020 by cglong on Saturday November 09, 2019 @02:21AM (#21490149)
As opposed to every native app that says the same thing?
Re:WebKit Goals for 2020 by kick on Saturday November 09, 2019 @02:25AM (#21490167)
Making the web suck more to match the native experience would be stupid. If people wanted the inconvenience of native apps, they'd use native apps.
Re:WebKit Goals for 2020 by lwansbrough on Saturday November 09, 2019 @02:45AM (#21490238)
They do use native apps, because they offer these features and other conveniences only afforded to native apps within Apple’s control.
Re:WebKit Goals for 2020 by soraminazuki on Saturday November 09, 2019 @03:45AM (#21490413)
Problems with Apple’s app review guidelines should be addressed by pushing for Apple to improve the guideline itself. Pushing for Apple to make their browser more adtech-friendly to the detriment of its users is not a solution.
Re:WebKit Goals for 2020 by saurik on Saturday November 09, 2019 @06:34AM (#21490909)
The core problem with Apple's review guidelines is that Apple should not get to set "review guidelines" for software that runs on a phone they sold to someone else, whether or not they happen to be part of a massive oligopoly wherein their sales and deployed fleet constitute some large percentage of phones being sold with quality parts (using supply chains they have locked up through contracts to prevent small competitors, along with patents on hardware features that they bundle access to only with their locked in software ecosystem). And so like, I in some sense agree? But what this means, and the reason why I agree, is that there should exist an app I can install called Chrome or Firefox that implements a web browser that works the way I might want, in addition to the ability to install whatever app I want (which may, or may not, solve the app review problem).
Re:WebKit Goals for 2020 by lwansbrough on Saturday November 09, 2019 @02:25AM (#21490161)
You should understand the argument before you form an opinion on it. First of all, there are plenty of us who have legitimate use cases for web push. Second, if you care about being bothered by shitty sites prompting you unprovoked, you have a couple options: content blockers or use different sites.

The need for notifications is real and Apple’s choice to exclude their availability in iOS is a business move not a technical move or a users-first move. Making PWAs better on iOS runs counter to Apple’s walled garden business model.

Re:WebKit Goals for 2020 by millstone on Saturday November 09, 2019 @03:39AM (#21490391)
The need for notifications is real, but the need to protect users from unwanted notifications and tracking and fingerprinting is real too, and more pressing.

Every site complains about your content blocker. Every site wants to send you notifications. Every site wants your email address to advertise at you. And with PWAs, every site will want to establish a presence on your computer.

Your motives may be pure, but your chosen platform does not place you in good company.

Re:WebKit Goals for 2020 by tannhaeuser on Saturday November 09, 2019 @02:38AM (#21490210)
> There are plenty of us who have legitimate use cases for web push

Such as? The only use case for notifications and PWAs I'm coming across are clickbait news sites creating a sense of urgency with "homepage was updated" modals obscuring content and capturing click events. Web user agents have freedoms in rendering pages to users, and Safari siding with users and power efficiency is a good thing. In line with other comments, I predict browsers will soon provide opt-out for notifications, then eventually deprecate them altogether, like they did with popups/popunders.

Now, more importantly, Safari could work on their odd pick list control rendering like a dial wheel.

Re:WebKit Goals for 2020 by nsomaru on Saturday November 09, 2019 @04:49AM (#21490593)
I run a premium retreat in rural India for which I built a web based portal to act as an “app” for the event.

I don’t have the resources to build native and web applications for each platform.

Right now we make announcements for the next schedule item. I’d like to notify attendees via the web app I wrote and have it display schedule information offline.

Re:WebKit Goals for 2020 by anoncake on Monday November 11, 2019 @08:54AM (#21504807)
> I’d like to notify attendees via the web app I wrote

You can notify them by email, SMS or using any other messenger. There's no need to force another on your customers.

> and have it display schedule information offline.

Your customers already have a calendar application, there's no need to make them visit a web page for that. At least there wouldn't if Google supported Webcal so everyone can use their favorite native applications instead. But that wouldn't push people towards Google's services and garbage web apps.

Re:WebKit Goals for 2020 by modeless on Saturday November 09, 2019 @03:06AM (#21490297)
Here's a site I made with a legitimate use of Web Push. https://james.darpinian.com/satellites/
Re:WebKit Goals for 2020 by tannhaeuser on Saturday November 09, 2019 @03:32AM (#21490370)
Ok, but I hope you can agree that the overwhelming majority of uses is a user-hostile dark pattern in news sites where they put crap onto pages so you click on it to go away, with the intent to generate additional page views and ad play-outs.
Re:WebKit Goals for 2020 by modeless on Saturday November 09, 2019 @03:41AM (#21490399)
Of course. Likewise, I hope you can agree that the abuse of Web Push and other new browser features is a problem that can and should be solved without totally giving up on those new features and blocking or removing them entirely.

I see a lot of people advocating that the Web should be essentially frozen at its current feature set or even regressed to something much less capable, and that makes me sad.

Re:WebKit Goals for 2020 by nsomaru on Saturday November 09, 2019 @04:53AM (#21490604)
You asked for a legitimate use case and are now shifting the goal posts to be about “majority.”

If the web is to improve we need new features and strategies to mitigate the negative effects of the implementation of these features. Don’t throw the baby out with the bath water.

Re:WebKit Goals for 2020 by tannhaeuser on Saturday November 09, 2019 @05:22AM (#21490672)
New features on "the web" are coming straight from Google to push their monopolist agenda (DoH, URL hiding just to name a few from this past week). Seeing as today's web is bordering on becoming useless (save for a couple enthusiast sites) and net-negative even, only helping autocrats, criminals, surveillance and privacy-invading monopolists rather than users and content creators I'd say we've already thrown out the baby with the bath water, and the "save the web" at all costs narrative needs to go away.
Re:WebKit Goals for 2020 by cjblomqvist on Saturday November 09, 2019 @04:09AM (#21490477)
In reply to tannheuser: Follow that logic, there's no need for images either (if you're in the late 90s), since the majority of the really useful content on the web is text... I understand your frustration, but I don't think the solution is to remove functionality from the web.
Re:WebKit Goals for 2020 by tannhaeuser on Saturday November 09, 2019 @04:48AM (#21490585)
That doesn't follow logically at all since we don't have to choose between the extremes of allowing sites to push ads, or disallow images altogether (your figure of speech is called the fallacy of the excluded middle in classic logic I believe).
Re:WebKit Goals for 2020 by SiVal on Saturday November 09, 2019 @06:13AM (#21490835)
The only use case for notifications and PWAs I'm coming across are clickbait news sites...

I write apps for myself, my family, and my friends. I put them on MY server and make them available to OUR devices. We should be able to notify ourselves whenever we want. Our devices should ask whether we want notifications or not to make sure, and we should be able to say yes. If a browser maker simply wants to avoid burdening the user, there should be a way to choose a default with blacklist or whitelist exceptions.

Instead, Apple (for example) says, "If you want to burden users by asking them if they want notifications, that would be very bad unless you first pay us for a dev account and keep paying and commit to using our own proprietary tech instead of using open web tech, because users aren't bothered by requests to allow notifications as long as they know it helps Apple. If you do, we will grant you the privilege of trying to persuade us that your app benefits us and not just yourself and your friends. Our App Store terms require you to show how your app isn't just a website (which we won't allow to send notifications) but serves Apple's needs in some way before we'll let you send notifications to yourself.

If it were really about serving the needs of users, iOS could allow users a choice between the default "browser that says NO" and "sides with users and power efficiency" and alternative browsers that, like App Store apps, show their contempt for users by letting them decide for themselves what they want.

Re:WebKit Goals for 2020 by lwansbrough on Saturday November 09, 2019 @02:40AM (#21490223)
> Such as?

Such as a user presses a button in order to enable push notifications.

Re:WebKit Goals for 2020 by soraminazuki on Saturday November 09, 2019 @02:59AM (#21490278)
That's an explanation of how users can allow notifications, not why they should.
Re:WebKit Goals for 2020 by paganel on Saturday November 09, 2019 @05:55AM (#21490775)
What is so “real” about the need for notifications? Apart from messenger/email for which we already have dedicated apps both on desktop and on mobile, for what else would we “really” need push notifications? I don’t really want to be interrupted by anything that isn’t urgent, and stuff other than messaging is not urgent at all (I’m talking browser interactions here, I suspect and hope that things like nuclear power plants don’t rely for their “urgent” stuff on browsers’ capabilities and I also hope they don’t have anything to do with easily-hackable browsers at all).
Re:WebKit Goals for 2020 by keeganpoppen on Saturday November 09, 2019 @02:39AM (#21490214)
wait is that "the argument" we're supposed to understand? you know, just because I use alert() in my code to debug doesn't mean that it should necessarily actually... work, and stuff... tl;dr - the tragedy of the commons exists; hence, lots of shitty technology that would otherwise be prone to it doesn't exist.
Re:WebKit Goals for 2020 by lwansbrough on Saturday November 09, 2019 @02:42AM (#21490224)
Not if you actually solve the problem.. which is basically just to make the permission only possible if the user interacts with the page in some way that satisfies a heuristic.
Re:WebKit Goals for 2020 by ori_b on Saturday November 09, 2019 @02:35AM (#21490193)
> The need for notifications is real

Do you keep metrics on acceptance rates? How many of the notification prompts that you pop up are actually accepted? How much of the time are you just annoying your users?

Re:WebKit Goals for 2020 by lwansbrough on Saturday November 09, 2019 @02:37AM (#21490204)
Like I said, our use case is legitimate in the strictest sense. Users request to enable notifications themselves. We never automatically prompt for it. So like.. 100%.
Re:WebKit Goals for 2020 by crooked-v on Saturday November 09, 2019 @02:18AM (#21490139)
Notification support is already a thing, and is separate from PWA support.
Re:WebKit Goals for 2020 by arciini on Saturday November 09, 2019 @03:48AM (#21490425)
There's been a lot of talk on this thread about the push notifications aspect. Setting that aside, at Wanderlog (https://wanderlog.com), we considered using PWA's and didn't because of another 2 WebKit limitations: storage and fast expiration.

We wanted to store pictures of where the user wants to go and cache map tiles offline. Mobile Safari has a limit of 50 MB. This is not enough for these use-cases.

Even more annoyingly, Apple deletes PWA's on iPhones after a few weeks. Our users often plan their trips months or many weeks in advance, and don't look at them for weeks at a time. By the time they go on the trip, they may be shocked to see that Apple has evicted their data from the local storage, just as they land somewhere where they no longer have access to 3G data!

I think Google's approach of providing virtually unlimited permanent storage is also probably not the best, but something in the middle might be better.

At the moment, it's clear that making PWA's capable is not an Apple-wide priority, even if the WebKit or Safari team may be in favor. We decided to avoid fighting it and build a native (React Native) app instead.

Re:WebKit Goals for 2020 by The_rationalist on Saturday November 09, 2019 @05:33AM (#21490709)
Why not choosing Cordova/IONIC? Through it's 4000 native Java plugins it can do all the things a PWA can, and even more.
Re:WebKit Goals for 2020 by iforgotpassword on Saturday November 09, 2019 @10:32AM (#21492074)
I sure hope not. Apple is the last bastion slowing down widespread use of these horrible technologies that have way more downsides than problems they solve. Privacy and increasing attack surface on your system are the primary concerns for me.
Re:WebKit Goals for 2020 by asadkn on Saturday November 09, 2019 @03:08AM (#21490303)
No PWAs, no proper service workers, no native lazyload, no WebP, always lagging behind with more buggy implementation of almost everything. Can't blame people who call it the new IE6/8.
Re:WebKit Goals for 2020 by maximegarcia on Saturday November 09, 2019 @08:48AM (#21491506)
And web share target...