> the engineer can operate the server but can't copy data out

Someone forgot about uuencode or base64.

Best guesses:

> I had not even taken my phone out of flight mode yet, but somehow the app knew where I was, despite not having mobile service, wifi or bluetooth enabled.

None of which are GPS, which is likely what Uber used to know you had "touched down". And GPS, being "receive only" may not be disabled by "airplane mode".

> I also have settings for the application set to only allow location while the app is in use.

Is that a phone setting, or an app. internal setting (i.e., a setting inside the Uber app. itself)?

If it is a phone setting (external to the app) then this would imply that it may not really do what it says it does.

If the setting is inside the Uber app. itself, then that is just a "promise" by the app. developer that they will behave, and if it is this case, then they clearly did not behave.

Edit to add: Checking my android phone just now, GPS is not disabled by airplane mode.

App setting

Yes I understand that GPS still works in airplane mode, but the app should not have my location made available to it when I am not using it

If it was an "inside the app" setting, then Uber did not behave.

> but the app should not have my location made available to it when I am not using it

Unfortunately, not how Android works. You can turn "location permission" on or off for individual apps, but if it is on for an app (and Uber's app likely demanded it be allowed "location permission" upon install) then if the global GPS is turned on, any app with "location permission" can ask the phone "where am I" at any time.

Browsing with Ublock Origin blocking all of the javascript resulted in the article appearing, but zero ads.

There is already one for posts, "flag" them.

Flag them when you see them on the new page.

Downvote and/or flag and move along.

But I've already read the comment at that point. I dont want to read these bait and switch comments.

It's a team effort, you flag some, I flag some.

unfortunately flag button is somewhat hidden on hn so most ppl dont go through that extra step for this to be effective

Maybe that’s proof-of-work?

And probably a feature because downvoting is usually enough.

Because movies (in film form) are projected an entire frame at a time instead of scanned a line (well, actually a dot moving in a line) at a time onto the screen. I read somewhere (but no longer have the link) that when projecting the entire frame at once as film projectors do lower frame rates are not as noticeable. I do not know if modern digital projectors continue to project "whole frames at once" on screen.

Movies are not projected using the scan and hold approach used by typical computer displays. They have a rotating shutter which blinks every frame at you multiple times. This both helps to hide the advance to the next frame but also greatly increases motion clarity despite the poor framerate.

But blinking a frame multiple times rather than once creates a double (or triple etc) image effect. To get optimal motion clarity which compensates Smooth Pursuit without double images, one would need to flash each frame once, as short as possible. But that's not feasible for 24 FPS because it would lead to intense flickering. It would be possible for higher frame rates though.

> It is a completely normal garden-variety ARM SoC

To mis-quote the politician quip:

How can you tell a marketer is lying?

Answer: His/her mouth is moving.

> I'm not sure I fully grok the hypothesis that Meta is materially advantaged by pushing for OS-level age verification.

These laws, that attempt to move "age verification" into the OS, 100% absolve Meta (and all the Meta owned "properties") from any legal liability so long as all of Meta's app's follow the law's required "ask the OS for the age signal of the user".

Any "bad stuff" which then gets shown to "underage users" then becomes "not Meta's fault, they followed the legally proscribed way to check the age of the user, and the OS said this user was 'old enough'" and Apple/Google then get to shoulder the liability (and pay out for the class action lawsuits) for failing to provide a proper age signal.

That's the "material advantage" gained by Meta by pushing these laws.

My point is that they already know how old you are, within some confidence interval, even if you never tell them or you lie to them, because they actively watch what you do and classify your behaviors with your age cohort. So why do they care so much that they gain another signal that only says "the user is over 18" rather than a much more valuable signal like "the user is 36 and lives in Albany" that they'd gain by doing the KYC internally?

I don't think absolution of legal liability has ever crossed any of these fools' empty heads. The threat of being fined & punished by the USG for doing something bad hasn't been a factor in corporate decision-making for decades.

OP answered your question. Meta is tired of being sued, so they're trying to make Apple & Co responsible instead. And honestly, can you blame them?

That is client dependent. On rtorrent, there is a separate "off" setting for the speed throttle that means "no throttle" with the result that "zero" actually means "no uploading".