bentcorner

In some ways Lenovo's implementation would have been better to just openly advertise that this is how it works - easier to not do encryption at all than to claim you did but make some mistake along the way. Fingerprint would thus keep honest people honest and if you needed something more resistant you knew you would need to do it yourself.

Kind of makes me wonder how knowledge transfer is going to work in the future.

How many times have you found a random forum post solving your problem? How many countless people has that post likely helped?

Now every single person facing the same problem will regenerate from scratch the entire thought process and result. What a waste.

There needs to be some way to close the feedback loop from the work that LLMs do.

How do you feel about signing in through Muse? The first time I asked it something that was only available in Maps browser it popped the browser and asked me to login to google and it just felt wrong. How secure are their VMs?

It's started rubbing off on me too and I find it irritating when I'm chatting with someone and an AI-ism starts rolling off my tongue.

I'm beginning to think I should: a) ask my agents to unslop[1] themselves when communicating back to me, and b) decide upon some writing standard and ask my agents to adhere to that.

[1] https://github.com/cursor/plugins/blob/main/pstack/skills/un...

This kind of approach works so well.

I was trying to upload HDR photos to Instagram and couldn't figure out how to make it preserve the HDR-ness of my photos, and was going back and forth with an agent - step by step we'd slowly iterate on a photo, I'd upload, then I'd download the jpg and give it to the agent and it'd think, change something in the format, and we'd try again.

I got impatient and just said fuck it and gave it chrome-devtools and a blank instagram account and a test photo, and it figured the whole thing out in about a half hour. I built a little browser-based tool from what it discovered, and I use it to run my HDR photos through to format them correctly for instagram and it works a treat.

My work provides me a Mac laptop plus remote Windows VMs and I've completely stopped using my Mac for agent builds/tests - I give them ssh access to WSL instances and they can go hog wild on the VMs.

It's all a bit adhoc - agents still need to pull (or I need to keep the main enlistment up to date on these machines) - I'm thinking of using containers or something else like github actions keep things cleaner, but right now it's "good enough".

Regardless I'm pretty happy with how it's working so far. Previously I'd be letting agents do work in the background and they'd kick off builds in the middle of a meeting or something and I'd start dropping video streams until I killed everything.

I use an agent to author my nix config - personally I don't have the determination to have picked Nix up entirely on my own so I find it to be a godsend. I can code review config changes and keep it all in git - also makes it easy to pick up the entire config and deploy it on a different machine.

And dropbox is just rsync and some UI

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

https://www.reddit.com/r/aviation/comments/1w9jsrb/put_toget...

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.

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.

I think at best you could propose that public information be available without login.

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

Probably because they used a secret third method and don't want anyone to know.

Deleting career fields in and of itself is not a problem with technology, but when it's like the eye of sauron scouring workplaces and snapping jobs away (pardon the mixed universes), it starts to become a little alarming.

University graduates are often considered min-bar for white-collar work hiring, so if it takes 4 years to train someone, how are people supposed to decide on a career path when it takes less time than that to completely alter the workplace?

My daughter is entering her first year of nursing, a career path that she is greatly looking towards. Who says in 3 years that robotics companies don't actually deliver on their promises and completely up-end the care industry? While I think that unlikely, it's not like people aren't trying to automate nurses away.

The worst thing is that I know there's something interesting in there but I'm too arsed to take the time and decode what data the author must have used to generate that text.

> People don't usually remember the average amount of time they wait. They fixate on those times when the elevator took FOREVER, the p90 case.

I would always get a chuckle out of seeing some poor soul waiting 3 hours to go down a few floors after work, only because I failed to add stairs to the lobby.

I spent about an hour in a VR entertainment space, where you donned a headset and played a game designed for a large play-space.

It was incredibly fun, but afterwards driving my car home I felt like the driving experience wasn't "real", and I had to put more conscious effort into my driving than usual to remain a safe driver. It took a few hours to wear away.

(This was a very distinct experience from what I have felt when binging a VR game like Half-Life: Alyx at home, where I get urges to teleport-move around my house and my hand-perception is off).

xda is older than github and has a lot of institutional inertia. Also I get the impression that many of the people involved in the xda ecosystem are hobbyists that just kind of learn things as they go along and have less exposure to bigco software engineering practices.

I've been using cmux for a long time too but am pretty happy with it. It's not perfect but much better than plain tmux/ghostty. I'll give herdr a shot too.

You can find drawstring threaders (bodkins?) on amazon pretty cheaply - if you have clothes with drawstrings it's handy to have one of these around the house.

Not just accidental, there are many tools/processes/weapons that are powered by software written by engineers who knowingly write their code to do harm.

But people gotta eat and all so who am I to blame.

I am a casual American football viewer but my understanding is that the kneel ends the current play but keeps the clock running. Each team has something like 40s to setup their formation and snap the ball after the previous play has ended. If the game clock is still running (this is concurrent to their 40s of "setup time"), the team that is in possession of the ball can just use the full setup time (idk the formal term for this) to just run out the game clock.

Each team has 4 attempts to move the ball forward 10 yards, where if the ball moves >= 10 yards they get a fresh set of 4 attempts. These are called "downs".

If the team has any downs left when they kneel then they can maintain possession of the ball and can thus run out the clock. Most (all?) of the time the teams end the game even if there is time left on the clock.

Note that either team can call a timeout pre-snap which freezes the game clock. Certain plays also result in the game clock freezing between plays. There is also a 2-minute warning at the end of the 2nd/4th quarter that also freezes the game clock.

IMO clock management adds a very interesting strategic layer to NFL football.

The conspiracy theorist in me says that LLM providers do this regularly (or at least, don't bother optimizing for it) beyond some arbitrary "$/task" metric. I am not sure of there is enough SOTA model competition to avoid this.

My dad had a fairly sizable collection of C64/Apple games and I never really learned where he got them from.

"Cracked by The Vulture" was something that I was very used to seeing upon booting up a game.