It’s rare to see a newborn meme. Soon it will be pixelified to all the doom.

…this hurts my brain. That being said, I’d probably also try it for the lulz, but I’d never bother support about it, because I knew what I was doing was insane.

Oh, apologies for my suggestion before seeing this comment hahaha!

CAN devices I have limited experience with, but I know at least in the automotive industry, vehicles often have various CAN devices that have various sleep states. Like, shut car off, it holds brake system for a few minutes and then unlocks the brakes and that ECU shuts down. Later on, an emissions ECU may run a self-diagnostic. After a few days being powered off, the security ECU goes into low power and turns off wireless doorlocks. After the voltage drops too low, the ECU in the head unit ostensibly shuts down, and the next time the car is started, the head unit has to do a cold-reboot and takes a fortnight.

Could be one of those CAN devices takes some time to get into the “off-adjacent” state to manifest the bug?

Could the time delay in being able to reproduce relate to some piece of code that has a timeout (thinking login timeout, cookie expiration, auth timeout, that sort of thing.) Or likewise, if the computer in question has multiple shutdown phases, like how many computers today “sleep” to RAM, and then an hour later sleep to disk in a more hibernatey fashion and fully power off? (Or some weirdness like how Windows shutdown now is ostensibly a hibernate, but a reboot is actually a full “power down power up” without shutting off power.)

I like @Buddahriffic@lemmy.world 's take on being wall-clock-based. I once had a bug with some software that would just go belly-up on certain days for no reason whatsoever in a datacenter 2000 miles away. After having worked on some bare metal servers in the past and learned all about thermal issues firsthand, I checked the weather in that region. It only seemed to happen on extremely hot summer days, at the day’s temperature peak. Turns out the datacenter vendor had a cooling problem in that section of the DC and they were unaware of it…

Crazy sometimes how bugs manifest.

There’s a weird obscure bug in M$ Remote Desktop in Windows 11 Pro I spent entirely too much time trying to track down, as a user. (Yes, the first mistake was ever getting near Windows, but anyway.)

It looks like there is some kind of counter that now exists in number of logged in sessions, and each RDP session counts as a one-time-use session. The local user does too.

• If you log in locally on first boot, there’s a 25% chance you’ll be able to log in remotely from one machine once or twice.
• If you log in as a remote user from boot, you’re more free to log in remotely, possibly from two different machines about 75% of the time, but if you just use one other machine, pretty much forever.
• Rebooting always solves the login issues, so much so that a terrible terrible workaround was employed. Enable OpenSSH server (now included in Windows) on Windows, to SSH into the box (which, reliably works every time no matter what) and reboot it.
• So many Internets on the topics, including using their old RDP driver, that the new driver may be cranky, that the host graphics drivers may have an impact, that the BIOS OOB management may have an effect. Nothing ever fixed it consistently.

Thankfully, my life means too much to me to go further down the rabbit hole and I don’t have to use Windows as much anymore, and hopefully soon never, but…its like they took a whole team of engineers to break something that has worked amazing since the early aughts and just firehosed pigeon turds all over it.

They obviously care enough to keep it working as they renamed the RDP app to “Windows App” in the last year, but don’t care enough to make it work correctly?

Yeah, it just makes you annoyed, especially when having worked on (some product) and it is years later and you are like, “we fixed this 10 years ago, you morons, how did you let this regress?”

Not with guns, or knives, or even pens, but with neglected big macs drying out on a chafing dish.

Was thinking of getting one just to do that a few weeks ago.

Learn to test for things like lead and other contaminants that one can test for at home, as another method.

Enter through the soffit vent of the attic, a vent that can’t be closed on the outside of the house. Land in the cellulose insulation, which is ostensibly shredded magazines.

Goodbye, house.

Literally not how it works at all. The body knows the amount of nicotine it wants and the smoker will smoke until that “need” is fulfilled. Weaning off nicotine is easiest in tiny amounts over time, or a few weeks of cold turkey hell.

The US has been gutting vaping as an alternative too, which forced more back on analogs. The US doesn’t want to stop smokers from smoking anyway. Lots of tax revenue.

Best thing too, the “quit” stuff like lozenges, patches, and gum, are often higher nicotine levels than a smoker is used to. The “low” dose products are for pack-a-day smokers and the “high” dose products are for 2-pack-a-day smokers. So smoker tries to quit, can’t, and ends up smoking more cigs when they return.

It’s a vicious cycle, and it seems also a natural method to combat ADHD, so it’s completely possible some people get on cigarettes, suddenly their brain is functioning correctly, and they’re addicted for life twice over.

Feel free to use your favorite internet search engine for further info. That’s what they are there for. (The last bit with ADHD is new-ish? So not sure what data is available there.)

They’d have to. They can’t replace their writers and editors with AI if they admit it’s a terrible idea right now. NYTimes has been shit forever in general though.

There’s a reason it was Ünderland in Venture Bros.

Let’s work the problem.

In the race to the bottom, we’re taking the charge! USA! USA!

My favorite is “cellulose insulation” used in attics. It’s basically literally shredded magazines. So you have this fire-starting material chilling in your attic waiting to turn your roof into the Statue of Liberty’s torch. Attics has soffit vents to let the fire motes in, and Bob’s your uncle. Foam stuff isn’t much better. Fire resistant material like fiberglass should be mandatory.

Now if only Docker could solve the “hey I’m caching a layer that I think didn’t change” (Narrator: it did) problem, that even setting the “don’t fucking cache” flag doesn’t always work. So many debug issues come up when devs don’t realize this and they’re like, “but I changed the file, and the change doesn’t work!”

docker system prune -a and beat that SSD into submission until it dies, alas.

Yet it is so surprisingly easy to not use any of them.

People thought underground coal fires burned forever.

There is no high speed, it’s not a hyperloop, it’s just some Teslas bumbling through tunnels, sometimes successfully.