Earlier quoted context omitted.
If an app on the app store abuses push notifications though, they can get kicked. Apple can’t kick a website off the web.
Technically they could blacklist certain behaviors from certain sites. They and all other major browsers already do this in a privacy-preserving way for Safe Browsing, certificate revocation, etc.
Private client-side-only PWAs are hard, but now Apple made them impossible
921–927 of 927 posts
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#922Earlier quoted context omitted.
I was thinking about a particular announcement where Mozilla announcing that they are working with Microsoft on MDN. Color me surprised when I discovered that also Google is mentioned there! Here is the announcement: https://blog.mozilla.org/blog/2017/10/18/mozilla-brings-micr... Reading that announcement makes b1tr0t's statement "We've started to consolidate docs under web.dev" even worse, as they previously said th…
Our team actively contributes to MDN. Web.dev is not an MDN replacement, it's a channel for guides & other supporting documentation.
As I understand, the Product Advisory Board for MDN was created with Mozilla + others in order to combat the fragmentation of information, but your actions seems to do the opposite.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#923Earlier quoted context omitted.
The deletion occurs if you use the app for seven days and don't visit the site. Pinned sites cannot meet those criteria and will not trigger deletion.
How about pinned sites that have not been accessed for > 7 days? I neither use the app nor visited the site for e.g. 2 weeks.. what will happen to e data for e pinned site? Apple is being vague here.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#924Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#925Earlier quoted context omitted.
All browsers on iOS are webkit (read: safari) under the hood. Firefox and Chrome are just skins.
Thanks for correcting my ignorance :) that makes more sense.
To be clear, only the rendering engine is fixed on iOS. Chrome, FF get some leeway to build other bits of the browser themselves on iOS, such as the netstack and the UI. But all new web features are limited to what webkit supports bc, well, it's webkit.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#926Earlier quoted context omitted.
By your logic they should just remove push notifications completely from iOS because it uses power. Wouldn't that be bad? Web push is better than native app push when it comes to power consumption as web push is stricter on what you can do.
If an app on the app store abuses push notifications though, they can get kicked. Apple can’t kick a website off the web.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#927Earlier quoted context omitted.
My iPod Classic has no intranet or internet. What does the "i" mean in that case???
iPod was that Harddrive MP3 Player that piggybacked on the MP3 download craze people were doing on the internet , obviously.
I had never thought of that!! I wonder if that same idea came into naming the iMac then??