At one time I heeded advice not to rely on 2FA SMS because you know it's not secure, so I kept everything in a 2FA app.
Well through an unfortunate sequence of button clicks I wiped my 2FA state and had a hell of a time getting into the apps that I removed my SMS from.
In theory yes SMS is an attack vector but personally the safety and convenience of SMS is more valuable than the odds that someone impersonates me at my mobile provider.
(Also I stopped using that 2FA app and just use a keepass db stored in onedrive).
This is a habit tech people fall into. "Amazon deleted my book" -> well just strip the DRM off it. "My ISP monitors me" -> well just use a VPN instead. "Ads make it hard to use the internet" -> well just use an ad blocker.
Ironically if more tech people just rawdogged the internet I think we would have more progress.
Spotify works mostly fine for me but there's weird rough edges that I don't always see in "simpler" apps.
Stuff like transitioning between desktop and mobile - it tries to work and most of the time it does, but sometimes I need to manually make my desktop play on my desktop. Not a big deal but sometimes I'd be happier if this feature didn't exist at all.
On my desktop, Spotify can be finicky when I connect/disconnect my bluetooth headphones. Sometimes it refuses to play after I connect my headphones, and I need to restart the app. I think it's trying to do something magically for me after it detects the headphones and gets into a wedged state, but a simpler "play to active speaker, whatever it is" audio app wouldn't have this problem.
Someone who flew this exact airframe wrote that this plane "likes to float when empty, so if you’re not firm with putting it down, especially with those winds, it’ll just keep floating in ground effect."
I'm not a pilot but from my understanding there's a lot of failsafes to ensure things that slow the plane down only trigger when the plane is actually on the ground. Considering that the left gear touched down at 0:19 and pilot called for TOGA at 0:15 they didn't stand a chance.
The prevailing opinion on PPRuNe is that the approach was totally botched from many miles out and the touchdown should never have been attempted (many participants there are professional pilots). There might have been a gust of wing as they were about to touch down, but they were also way too fast and lowered the flaps very late, literally as they crossed the runway threshold, causing extra float due to ground effect.
The pilot flying appears to have been dead set on landing on the first try no matter the cost and the first officer did not intervene as he should have.
They got incredibly lucky and both survived, however likely will never be behind the controls ever again.
This happens to me too and I enable 'Live Captions' (not meeting transcriptions) so that I always have a scroll back in case I miss something.
It's built into the meeting software I use and probably in most mainstream ones.
I tried OS transcription but those don't split out who's talking (since it's a single audio stream) so much less useful.
Anyways all that to say that at least in online meetings this problem is solved and addressing this problem in a stack that doesn't have meeting context is going to result in a worse experience.
> An AI helps fill in the story from there. Fact checks each claim, connects the dots, makes it comprehensible.
I think this certainly has some value but this claim in and of itself is stated like your hand-wavy step 3. How do they fact check claims and connect the dots?
Maybe LLMs get there but currently they write in an extremely verbose manner, and things that have gotten into the context window that are no longer relevant continue to stick around (just try having it write some code, then work some of it back to simplify the problem - it will insist on writing comments about code that no longer exists).
Right now using an LLM to write documents is like taking a superhighway to travel 100 meters. Yeah you're doing a lot but is all that really necessary?
I won't deny that LLMs will never have a place in writing. But I personally don't think the current form is "the one that actually lands" (!).
Reminds me of watching my wife use her computer. I'd help her with something and realize all the little things more regular computer users just put up with. Incorrect focus, focus stealing, windows popping up behind current windows, unclear window styling, invisible scrollbars, moving page elements, unclear instructions, the list goes on and on and on.
Well through an unfortunate sequence of button clicks I wiped my 2FA state and had a hell of a time getting into the apps that I removed my SMS from.
In theory yes SMS is an attack vector but personally the safety and convenience of SMS is more valuable than the odds that someone impersonates me at my mobile provider.
(Also I stopped using that 2FA app and just use a keepass db stored in onedrive).
reply