darren_

> Google employs _engineers_ to figure out the truth.

and people say hacker news has no sense of humour

> Can't imagine using MTG to learn a language.

Note that he's starting from N2 Japanese, which is already a high level of Japanese proficiency (although it does not test writing/speaking at all, so it's very feasible to have N2 yet be terrible at conversation). He's not exactly learning hiragana from M:TG.

The M:TG competitions are giving him a framework to practice that conversation, which believe it or not can be hard to come by in Tokyo without deliberate effort (see 'expat bubble'). The vocab/grammar on the cards is mostly incidental to all that. If he was playing online M:TG in Japanese he wouldn't be getting anywhere near the payoff.

No, it's an affectation.

Both of these only apply for US citizens or permanent residents so no, it's not just about paying some amount of money to avoid the theatre.

This site works fine in safari/mobile safari, it is not ‘chromium only’

> if I turn off Lock Screen notifications and turn on time sensitive notifications then will I get no marketing notifications, and only notifications about my driver turning up?

It's up to the app developer, they get to mark notifications as time sensitive or not. So if someone decides that because a coupon is expiring soon it's "time sensitive" to ping you about it, then they can mark it as such. Hypothetically Apple could frown on this in app review, but it isn't something app reviewers are likely to be able to reliably catch.

> Something that isn't talked much about IPv6 and I believe has subtle and indirect influence on it's adoption is that it is far far far less human-readable than IPv4

What? This comes up in like 95% of ipv6 threads on HN (see also: ‘they should have just added an extra quad to v4 addresses’)

You can still backup iPhones to your desktop instead of iCloud. At least for now.

Here's exactly what it means: Someone at Facebook, when creating the listing for the Threads app on the appstore, told Apple that the app might possibly collect Health data (etc). These labels are entirely based on self reporting by the person doing the upload. That's it, that's the entirety of what these privacy label things mean: the company making the app has made these claims about what it collects.

In this case Facebook appear to have simply ticked every possible box for data collection regardless of whether the app actually does it or not. Note you can't just get health data on iOS without asking, so people would notice if they tried. My guess is that actually figuring out what they do/don't collect was too hard, so they just said yes to everything.

This link says absolutely nothing about Flutter usage.

It's about apps that are already written in native iOS code, which are currently using custom Material Design components (which are mostly/entirely in obj-c), and that going forward those custom Material components are going to be phased out and apps will use standard UIKit elements instead.

This tells you absolutely nothing about Google's commitment to flutter.

i don't find it too compelling, but this test could potentially help you understand, to some degree, how important battery consumption of an app actually is to users.

so you run a test where you intentionally consume more of some cohort of users' battery power (you could have several cohorts where you consume more and more power, even). and you look to see if the rate at which your app is deleted/force-quit by the cohorts with more power usage goes up. if it does then you can assume that you're overdoing the battery drain. if it doesn't then you can assume users don't really care (or don't care enough; maybe they're unhappy but your app is too important to them to delete).

why this could be useful is when you're deciding what to prioritize - if you've got data saying that users don't care about excessive battery consumption and they'll keep using the app anyway, you can argue against optimizing for battery life in future development, presumably letting your developers do things faster/more lazily. or, it could show that battery life is super important and be a valuable argument to prioritize power optimization work in the name of keeping your users from jumping ship.

personally i'd rather just presume that battery life is important and that optimizing for efficient use of our users' batteries is the right thing to do, regardless of hard data, but i'm sure there are people out there that think differently.

I’ve seen arguments that dark mode is important for accessibility, which seems reasonable to me, and depending on the company might be a dealbreaker.

I've mentioned this in another comment but: this update will permanently disable any 32 bit iOS apps you have on your device with no recourse or downgrade possible.

So, reason not to update: you like using software you've paid for.

This upgrade will break any 32 bit iOS apps you might have on your device, and you have absolutely no recourse and downgrading is not permitted. I've lost access to several _paid_ apps due to this.