anilakar

15 years ago I would have dismissed this immediately as an elaborate troll but nowadays you cannot be sure anymore.

I'm suggesting moving on to IPvNN which requires device and ISP forced guarantees that the originator is not under the effect nor the lack of any medication or other substance, not being coerced and not using non-human assistants in content creation.

Wasn't the whole waterfall model originally a caricature to higlight all the issues one will inevitably encounter if they eliminate feedback loops and go with a strictly sequential development paradigm?

The missile knows...

Working hard means lots of hours paid out of owners' pockets.

Working fast and avoiding work means short time-to-market.

And when your or someone else's infra down to such a degree that you need SSH access, you do not want to depend on being able to touch that machine first. The same is true with custom AuthorizedKeysCommands that phone home.

While I absolutely despise what Israel is doing in Lebanon and Iran, it's hard to blame anyone but Hamas for the Gaza casualties.

If you have no more free territory to fight on, you have lost. Give up.

The trick to optimization is not "doing faster" but "doing less". I already feel rg is missing a ton of results I want to see because it has a very large ignore list by default.

Complaining about Smartlink is a bit hypocritical as it's the smartphone equivalent of an ankle tracker. The opportunity cost for the user is incarceration.

Here, ambulance drivers are often ex-firefighters and vice versa, and both tend to be in good physical shape. Ship and airliner captains on the other hand are often older and in less than stellar physical condition.

My hypothesis is that it's either age, physical condition or both.

Parts and labor combined that would be a 4000-5000 eurobuck job. A Nissan importer tried to weasel out of a warranty replacement on a friend's X-Trail so they first offered to completely refund options that had become unusable.

The car was full of issues and probably spent more time in the shop than on the road. Nissan finally had to buy it back after service techs failed to tighten the oil drain cap after an engine overhaul.

We had to come up with something wireless for authentication as we did not want to install anything visible like RFID readers. We also had a few Pis lying around.

Frank's guests just need to get the Doorking 16120 default key and start letting themselves in.

Edit: undergrad shenanigans from ten years ago:

Our university student-run electronics lab had an issue: technically anyone with a student card was allowed on premises at any given time, but the department only gave us a small set of keys that we had to share with the rest of the student associations. Obviously we needed a solution.

We did some snooping and found that the request-to-exit button wire was running on a cable tray alongside all the other wiring and plumbing, as the lab was in the basement. We picked a suitably dark, inconspicuous spot and wired up a Raspberry Pi driving a transistor and in turn a relay which we then wired in parallel with that button. Users could then connect to the local lab wifi and then SSH into the device. Login shell was replaced with a script that pulsed the GPIO line for half a second and subsequently caused the door to open.

We never got caught and apparently all the evidence was destroyed when the building was renovated a few years later.

Any crypto that prevents casual tinkering is enough to keep most companies from wasting resources on reverse engineering stuff.

Back in the day we wrote a simple byte-level nonce + delta obfuscator for a terrible Node-RED-like programming environment so that we could tick a "must not be human-readable" requirements checkbox.

If the cryptography, proper or not, has been written for DRM purposes, no legal department is going to permit digging into implementation details even with a ten feet pole.

Small businesses very much like to gamble with the box checking.

It actually prohibits holding the chopsticks in your mouth. You have a chopstick rest (and workarounds) for that.

Just like the next term on the list does not prohibit eating food on the bottom but rather digging into the bowl instead of eating in top down order.

You do realize that violating export regulations is a much bigger risk than losing a few individuals relying on snake oil security?

Agree. Writing code has always been the most time-consuming part that distracts me from actual design. AI just emphasizes the fact that anyone can do the keyboard mashing while reading code is the actual skill that matters.

Give a woodcutter a chainsaw instead of an axe and he'll fell ten times more trees. He'll also likely cause more than ten times the collateral damage.

Someone was asked to test untestable code so verifying mock contents was the best they could come up with.

Your design will be looked at in direct sunlight on a six inch, non-color-calibrated screen. Stop using low contrast and extralight fonts.

Next time we'll ship your Mac. No, we won't give you a new one.

Reddit's r/namecheap is also full of horror stories.

> If you want to pretend this never happened – delete your old article and post the new one you have promised. And I will not write “an OSINT investigation” on your Nazi grandfather

From hero to a Kremlin troll in five seconds.

Running microservices on Hetzner is a risky move.

Their direct internet connections rarely go down, but links between servers in their internal network suffer from intermittent failures. if you make your service reliable enough to be able to run on a single node, you could have built a monolith in the first place.

It would have resulted in an uninitialized variable access warning, though.

To be fair, there were multiple wrongs in that piece of code: avoiding typing with the forward goto cleanup pattern; not using braces; not using autoformatting that would have popped out that second goto statement; ignoring compiler warnings and IDE coloring of dead code or not having those warnings enabled in the first place.

C is hard enough as is to get right and every tool and development pattern that helps avoid common pitfalls is welcome.

Various macro tricks have existed for a long time but nobody has been able to wrap the return statement yet. The lack of RAII-style automatic cleanups was one of the root causes for the legendary goto fail;[1] bug.

[1] https://gotofail.com/

I'm sick of corporations and bootlickers who claim you cannot do games without anticheats. Even if I am not personally running that software, all the users are still normalizing spying on our devices and networks.

If your business model relies on violating the privacy of others, your business deserves to die.

I had subscribed to clearance sale newsletters from quite a few retailers but unsubscribed when I noticed they put stuff in the outlet section only when they run out of sizes S to L.

My main gripe with UB is that if a compiler is able to detect undefined behavior invocation, it is still allowed to compile (or rather omit) said code instead of crashing.

> vibe coded software with major security vulnerabilities

> vibecoded without reading any of the code

Remember when years ago people said using AI for critical tasks is not an issue because there is always a human in the loop? Turns out this was all a lie. We have become slaves to the machine.

It's quasi-legal only as long as Activision execs are unaware.