The example videos actually show Sora generating multiple shots for a single video. I think the larger problem is similar to why it's difficult to get GPT-4 to write a novel or DALL-E to draw a comic book: it's hard to get current models to maintain consistency across a long time. You need some way to get characters and places to look recognizably the same in different shots, and that's not something our current technology handles well.

On movies with long takes, Hitchcock's Rope is a classic example. Birdman is a more recent film which plays with the idea (the film appears to be a single continuous take, albeit with intentionally obvious use of CGI to achieve that effect).

This is broken thinking. Processes never go wrong due to a single mistake. If you think there was only one mistake, then the second mistake was not designing the process to have a check for that category of mistake. If this computation was so important, surely there should have at least been a second set of eyes on it. I guess we're reading this article because there was a second pass on the computation, it just happened months too late.

The separate SSIDs thing was never the right way to set up a network. I still see it all the time. As far as I can tell, it was a workaround for some clients being stupid when 5GHz Wi-Fi was first introduced, but this 12-year old StackExchange answer says it's an obsolete idea.

Aren't QR codes just text in a format that's easy to read for a machine? How are the risks any different from going to a random website, which should be limited to browser bugs or whatever you do on the website (the internet has a lot of warnings about phishing via QR codes... which doesn't seem relevant to viewing restaurant menus unless they also do ordering through the smartphone)? i.e. you'd have the same risks if the menu link were given as a URL shortener or otherwise obfuscated link.

I believe you that a bug in the QR code processing code existed, but I can't find any reference to its existence in a quick web search. Other than that, my phone shows the text of the QR code and asks me what to do with it before taking an action, even if I use the camera app it came with to read the QR code. Is that not what every phone does?

This makes no sense. If you and the staff think they should be paid more for serving more customers, then pay them a commission and increase the price of the food enough to cover the commission. That would come out approximately the same as tipping except for it involves the prices on the menu being the real prices and no weird perverse incentives created by random customers deciding how much the staff should be paid.

This whole post is SPOILERS.

I did feel like this wasn't stated explicitly in the TV episodes, so you had to infer it from Holston dying after he took his helmet off, but the video of it looking lovely out there is a fake video shown on the helmet of the suit. The toxic wasteland is the truth. (Notice there's never a camera shot of the outside not filtered through the helmet camera or the cafeteria screen, so it's never made explicit.) Also, it's strongly implied that prior to the start of the series, cleanings have been decades apart, so people wouldn't have a good memory of a prior cleaning... but I agree it didn't make sense that Holston still cleaned knowing what he knew. I do recall when I saw the screens in the TV series, they were a lot bigger and clearer than I had imagined from the description in the books,

That said, a lot of the worldbuilding, including the people deciding to clean doesn't really quite make sense. Like how all the stuff they have has survived hundreds of years (or, equivalently, where they're fitting the manufacturing capacity to remake it).

Discord logins aren't by username, so they don't have that problem. Logins are keyed to email and/or phone number. The database master key is a string of digits (visible to the bot API, never intentionally shown to the user, although the mobile app shows it when it fails to load a username).

The username + 4 digits thing is used in Discord to simultaneously handle having a default "display name" of "@username" while also have a user-facing global identifier of "@username#1234" (you can also set a per-community ("server") display name to override your default display name, but people in that community can always see your global profile). The proposed change is to split the two into an arbitrary display name (similar rules to the current "username") and a user-facing global identifier that they're now calling a username so you'll have to be "@username1234" (or come up with something more creative if you want). But that user-facing global identifier will be pushed even further into obscurity since it will be decoupled from the default display name.

Making public IDs incrementing numbers makes them guessable and makes IDs leak information about the order accounts were created (Slashdot considers this a feature, not a bug), which can be a problem. In this case, that could let you easily spam friend requests to a lot of accounts by just enumerating them. Sure, you could (and should) have additional layers of security preventing an attacker from making use of successfully guessing an ID, but making the IDs not guessable in the first place is generally considered a good design pattern.

(There might also be some distributed system / race condition details of not requiring your servers to agree on what the next ID is?)

I don't remember which tool I used last time I bought a flash drive, but this Ask Ubuntu question has answers recommending a few options. The top answer recommends a tool called f3, which also has instructions for installing on Windows/Mac (although it also has a fast mode that's Linux-only).

I'm in Seattle, which I gather is an outlier in how common masks are. In the grocery store and transit at off-peak times, I see maybe 10% of people wearing masks at most. They're there, but not common. The few times I've been on transit at peak times, it's been a clear majority wearing masks (mainly KN95s).

Of course, at events that require masks or at the doctor's office, I see 100% of people wearing masks, with a mix of N95s and KN95s and the occasional surgical mask.

Clicking through the links on the technical details, I found a link to the GitHub page for proton-bridge, so it is indeed open source. It sounds like it's a PGP key manager of sorts. It's not explicit, but it sounds like ProtonMail stores all of their users' PGP keys with the private keys encrypted with your password such that they never see your password so they can't decrypt the key. And the bridge just handles doing the key requests and encryption/decryption for any emails sent to/from other ProtonMail accounts.

It seems like if you were a more technical user and had an email client with PGP support, your email client should be able to just have a plugin for dealing with ProtonMail's key distribution and then you wouldn't need the bridge.

There's no income tax in Seattle or anywhere in Washington State. It's an ongoing political issue, with the latest being a capital gains tax on gains over $250k which may or may not get struck down by the courts or removed by a new voter initiative.

While it does seem difficult to study, there actually is research on this by the UK: One dose of COVID-19 vaccine can cut household transmission by up to half.

Mobileye is not new. They have provided the tech behind the driving-assist technology in multiple makes of cars for over a decade, including originally doing Tesla's before Tesla dumped them in 2016. Of course, there's a big gap between driving-assist and full-self-driving and they may be over-promising like seems common in this space, but Mobileye isn't coming out of nowhere.

It's really hacky, but this script I developed does that by piping the phone's camera through a WebRTC connection made by using the mobile web browser, which connects to the desktop using gstreamer. It's pretty fiddly and doesn't actually work very well in practice, but it's at least a proof-of-concept that it's possible, without even needing to install an app on your phone past the web browser it already has.