https://support.apple.com/guide/security/contents-a-localpol...

The manpage for the command provides information on credential usage on Apple Silicon devices.

Whether the resulting HTML game is playable in Safari is a different discussion.

The QR code, as generated, is effectively "not clickable" for most iOS users, unless they are using something other than the most common way to read QR codes on their phone like a 3rd party QR code reading app or similar.

For example, this self-contained webpage: Hi!

encoded is: data:text/html;base64,PGh0bWw+PGJvZHk+SGkhPC9ib2R5PjwvaHRtbD4=

If you paste that into a browser, it will render "Hi!". Very short and easy.

But if you encode is as a QR code, it won't work in this situation.

Tried them out in Chrome and they're mostly all the same though I do notice a slight jitter to the rendering in the smoke example.

I agree that it probably contributed to python 2 inertia as it was re-exposing people to the idea that "typing python in the Terminal gets me python 2" and "I just used what I already had" - but it definitely wasn't stopping people installing a newer version.

If it's a signed response, at some point there's another piece of code that checks that the signature is valid and returns a yes/no.

I think the reason Apple's sensor was mentioned in this instance was due to how Apple handled storage and usage of biometrics as described in here https://www.apple.com/business/docs/iOS_Security_Guide.pdf

Compare that to, say, other laptop vendors: https://support.lenovo.com/us/en/product_security/len-15999

By default, this is currently enabled, as noted here: https://stackoverflow.com/questions/11712322/error-the-times...

You have to go out of your way when signing an app on macOS to disable timestamping in current OS versions.

Edit: Ah, and another comment here provided the answer: https://news.ycombinator.com/item?id=12654917

In prior versions, it was stored in Login keychain, which was not synchronized.

Additionally, the items were visible in the security command line tool and in Keychain Access, so you could delete them.

The Local Items keychain / iCloud Keychain is a new style keychain that was back ported from iOS. The security and Keychain Access tools have no visibility into it, it's 100% handled by the secd service.

Edit: Ah, sorry, you meant in Sierra specifically. Yes. But I'll leave these clarifying details here for posterity :)

Edit2: Additional detail - in prior OSes, there was a GUI prompt asking if you wanted to store the passphrase in the keychain. This is gone now. It just does it (unless you preemptively edited the ssh config file to disable keychain storage in advance)

Edit3: Can confirm that "ssh-add -K -d" does in fact delete the passphrase from the keychain, even though it may throw an agent error.

There's an IL interpreter in the mix - it's simulating an app and what it would do based on the opcodes emitted by the compiler for the code you write.

This is indeed in line with existing scripting languages (Lua, Python, etc) which are in the App Store.

But the presentation of it might be too close for comfort for Apple. He's not presenting it as ".NET scripting" but specifically mentioned porting the .NET Roslyn compiler.

It all boils down to the same thing, but I wouldn't be surprised to see an App Store submission reviewer deny it, misunderstanding what's they've read/seen.

But it doesn't even need that. You can use a .torrent or magnet URL from anywhere on the latest builds.

Just drag-n-drop a .torrent file onto the UI or simply paste (Ctrl-V / Cmd-V) a magnet URL that you already had on your clipboard and it will gladly attempt to live stream any arbitrary torrent.

The built-in video player generally works the best with .mp4 video files, but I've seen it successfully stream other media types as well.

When the torrent file in question contains multiple media files, a file chooser dialog appears letting you select which one you wish to watch.

The application could literally be re-written at any time to use any torrent site for showing content.

.. and since it's open source, the genie is out of the bottle.

All the timelapse video now proves is that the drone was in the proper position to flash its light.

Out of position (as measured by the precise laser rangefinder)?

Then don't flash the light yet, drift/adjust, check again, repeat until correct - then flash.

It's not precision as much as it's "eventual precision".

EDIT: WOWOW

Major difference! Definitely sticking with 3!! Thank you :D

Extremely fast in comparison to 2.

I'm using Sublime 2 on OS X and large files + regular expressions are generally a cause for pain.

Do you have any default settings changed like disabled document preview or similar?

The only thing I generally feel is a champ at regular expressions + insanely large files on OS X is TextWrangler/BBEdit. In fact, I keep TextWrangler around specifically for the large file excellence experience which I (currently) don't receive on Sublime Text 2.

Nowhere did I imply that. Everything I mentioned was webpage reading/viewing content that the publishers themselves announced across the world, hoping to get readers - who in turn would view their ads.

Not only are they publishing it, they're announcing its presence on social media, performing "search engine optimizations", and cross-promoting it on other non-web technologies (radio, tv, printed media, etc.).

... At no point, as a consumer of this content, did I get presented with so much as a simple "In return for consuming this content, you agree that you will look at the ads being shown here".

I also haven't agreed to such things for cable tv or radio - but guess what? I don't generally consume those media products, in large part because the formats are linear and full of "unskippable" ads.

Nothing is stopping the web from moving to this format. There are many sites out there that present an interstitial of some sort before moving onto the main content. And every time I end up on one of those sites, if my ad blocker isn't dealing with it somehow, I generally remember and avoid visiting the next time.

If you want me to pay for the web content that you're publishing because that's the business model you've decided on, be up front and attempt to get a paid agreement from me. Or deal with the fact that I'm part of the audience that doesn't look at the ads in print media, mutes or skips channels on TV, and installs ad blockers for the web.