pudquick

I'm saying the primary gateway most iOS users are using for loading a QR code - the camera app - will not present a transition to load your URL in this situation

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.

data: URI URLs aren't supported in it, it has nothing to do with the size / length of the QR code

For example, this self-contained webpage: <html><body>Hi!</body></html>

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.

Runs buttery smooth on my M2 here in Safari on macOS 14.2.1

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.

In 2016, that laptop also came with System Integrity Protection - you couldn't change /usr/bin/python if you wanted to. And you still can't to this very day. Changing System-provided python was always against recommendations in prior OS versions because the next OS update could re-replace it at any time.

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.

That being said - python 3 was released in 2008. A 12 year transition is pretty respectable.

The next time you'd like to diagnose, you can reboot into Recovery and use "csrutil enable --without dtrace --without debug" and you should be able to avoid those issues.

This is different than in prior macOS versions.

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.

Possibly. It's not actually running two apps.

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.

I would love to see this develop into a widely adopted standard. Apple uses a similar technology with their Airport Express devices for printer sharing, always been annoyed it was so restrictive in being able to connect to it.

It's using third-party APIs for the .torrent content and search engines for content.

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.

This makes me a little sad to learn that's the method involved.

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".