Hacker Newsnew | past | comments | ask | show | jobs | submit | mrmanner's commentslogin

which they have to be anyway, to support normal iphones and maybe ipads and in many cases a cackle of Android phones too. (but I still think this is brilliant design)

in this thread many people have clearly never developed for iOS

Here's just the screen sizes, not even taking into account actual resolution:

    iPhone (2007)     3.5" 74.0 × 49.3    36 cm²
    iPhone 5          4.0" 88.6 × 49.8    44 cm²
    iPhone 12 mini    5.4" 124.5 × 57.5   72 cm²
    iPhone Duo, cover 5.4" 113.4 × 77.2   88 cm²
    iPhone 6 Plus     5.5" 121.8 × 68.5   83 cm²
    iPhone X          5.8" 133.7 × 61.8   83 cm²
    iPhone Air        6.5" 150.0 × 69.1  104 cm²
    iPhone 18 Pro Max 6.9" 159.2 × 73.3  117 cm²
    iPhone Duo, inner 7.6" 157.6 × 111.5 176 cm²
Now, you can leave out a few of those as hopelessly obsolete like the OG iphone, 5, 12 mini, arguably the x, but it's still a pretty wide selection.

Good list. And if you support both portrait and landscape, you need to support twice that, and you need to be able to switch on the fly.

But for the apps that don't currently support both orientations, it's possible they don't have support for switching aspect ratio on the fly. This design might help with those apps not completely breaking when folding/unfolding.


Yeah to be fair I'm all for the 1/sqrt(2) aspect ratio, I just think it's funny that it's treated as some kind of holy design constraint when they're all over the map on phone sizing :)

And the extra irony is I'm currently shipping an app that doesn't deal well with different size phones (just pads the edges), heh, so do as I say, not as I do.


12 mini and 13 mini remain supported in iOS 27.

In this day and age it makes sense to amend Tim's statement to "canonical urls don't change". And cool web sites have a canonical URL for most pages.

That way we a) don't lose track of relevant content but b) can have nice things such as short URLs with good names.


Came here to say this. I've no idea what the app does, I presume that is because I'm old.

And that doesn't matter. It's cool to make apps in any case!


Trains AND solar power. Awesome.


I had the same thought at first, but in context I think the quoted text refers to business relationships. Which makes all the difference.


They're really the same thing. I think of the classic Walmart/Vlasic pickle story.

https://eng121.net/online%20textbook/cause-effect/The%20Wall...


I noticed how they've marked the features that only Chrome supports (e.g. installation) but not the feature that only Firefox supports (orientation).

(tbh I don't know if the list is simply Chrome-centric or if there's a good reason behind, but it struck me as interesting)


I mean technically a flash drive could be "a secure environment walled-off from the internet"


An intranet could be a secure environment walled off from the internet


Hard disagree. How can it be “walled off” from the internet if it’s not connected? Despite the jokes, cutting access on its own is not the same as air gapping or a firewall. As soon as it’s plugged in there are zero controls.


Technically they could claim it’s a backup


An unplanned, decentralized, public backup?


And it is not connected to the internet, the internet is connected to it (I’m not in here with you, you’re in here with me)


Maybe I just haven’t discovered the track changes feature in word processors enough, but I find it lacking: no explicit grouping of changes (the git commit), no clear timeline of changes, no tagging / naming of versions etc.

Not saying that a line-by-line diff is that much better. Neither is great imo.


> On the government endpoint, which returns X that the platform uses as "evidence" for you being an adult, yes, that's tied to your identity, as the certificate/whatever is tied to your identity.

In this scenario the government knows all the age-restricted sites I've visited. I'd argue that is worse than if all the age-restricted sites I've visited know who I am...

(FTR I don't know what I think about age restrictions in general, but I'm pretty sure there's no implementation that comes without negative side effects)


Not necessarily. The age verification proof doesn't need to be site-specific. But again, that reduces the incentive "for the citizen to make sure their authentication isn't shared" because there's nothing tying it to them.

I also kinda hate the whole idea of needing explicit permission from the government to access the open web, regardless of whether or not they know which specific sites they're giving me permission to access.


There's actually a much better idea that's been floating around. Require over-18 sites to set a certain header. Then anyone who wants to can install a browser on their kid's device that will block pages with the header. There's no privacy implications, no surveillance implications, no need to make VPNs illegal as long as they pass it through; it's just a plain old parental block with a regulation keeping it always up to date. Yes, you may have to stop your kid installing random software on the device to bypass whatever blocking you set up, but you had to do that anyway. If it's Apple or Google they could easily enough require everything in the app store to respect the flag when the device is set to kid mode.

(If the government does the incredibly overbearing thing and does not do the simple and effective and unintrusive thing, it proves their motivations are surveillance)


Already exists; the industry called it RTA (Restricted To Adults). Nobody used it... and it's 19 years old. Complete failure categorized under "we already tried that."

https://www.rtalabel.org

You can use it too, just put this in as a meta tag:

<meta name="RATING" content="RTA-5042-1996-1400-1577-RTA" />

Or send the following header:

Rating: RTA-5042-1996-1400-1577-RTA


Was it legally mandated? I think that's the main idea GP is proposing. Obviously without any incentive to actually implement it there's no point.


I don't think that it matters. The big porn sites have served RTA tags for many years. Android, Windows, macOS, and iOS can all be configured to block adult content tagged with this system. That still hasn't stopped a bunch of states from passing age verification laws ostensibly targeted at protecting children from these sites.


Because the laws aren't about protecting children. If they were, they'd say browsers have to enforce this header and sites have to send it.


In order to accomplish that working, you'd have to legally mandate parents put the blockers on their kids devices.

Similar things exist that block based upon lists and content keywords and such.

Most parents do not want to block stuff from their kids or they would be.

If thousands of them demanded that devices came with blockers then the market would provide such devices.

Many moons ago you could argue parents did not know what the youngins would find on the internet. Today's parents definitely know, and most do nothing to restrict access.


It doesn't have to be mandated - parents could choose.

Even if it's mandated that kids can only use phones with a special "kid mode" turned on, even if you had to present ID to turn it on or off or buy a phone with it turned off, that would still be way less bad than what's being rammed through parliaments right now.


Germany let's the ID cards themselves mint such proofs in a way similar to how Intel's attestation doesn't leak the CPU's serial number.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: