News for hackers. Stuff that matters.
Re:Apple rejects Puffin Browser on iOS by phobius on Friday January 26, 2018 @12:02AM (#16237147)
Is it not possible there's just a security violation they need to sort out?

Am unfamiliar with Puffin, but the post leaping straight to "it's a conspiracy!" without indicating what the stated rationale for rejection was appears a bit off.

(I'd I'm normally first in line to attribute things to corporate greed)

Re:Apple rejects Puffin Browser on iOS by b4lancesh33t on Friday January 26, 2018 @12:20AM (#16237198)
Their medium article explains the reason apple rejected them. They use chromium on their servers to render pages. Apple wants them to use webkit.
Re:Apple rejects Puffin Browser on iOS by pier25 on Friday January 26, 2018 @12:29AM (#16237221)
If this is really the case it’s nonsense that an iOS policy would extend into your servers too.
Re:Apple rejects Puffin Browser on iOS by martin_bech on Friday January 26, 2018 @12:33AM (#16237229)
The problem isnt that its serverside, its thats a different renderingengine, and therefor visually could/is rendering differently than safari/webkit.
Re:Apple rejects Puffin Browser on iOS by hungerstrike on Friday January 26, 2018 @03:02AM (#16237647)
Who cares?

There are tons of games in the App Store with custom user interfaces that don’t match anything from Apple.

Re:Apple rejects Puffin Browser on iOS by martin_bech on Friday January 26, 2018 @05:56AM (#16238276)
Thats not the issue, the issue is that cnn or whatever.com might render differently or not at all if viewed in one browser, instead of the other. I dont know the internals of puffin, but security and js attack vector, might be different as well.
Re:Apple rejects Puffin Browser on iOS by hungerstrike on Friday January 26, 2018 @01:00PM (#16241299)
You said "and therefor visually could/is rendering differently than safari/webkit"

You didn't say anything about security, but there is no security problem either.

The client side wouldn't be evaluating JavaScript outside of Apple's JS engine so there is no security risk whatsoever.