anilakar
Nowadays you can just slap your site behind Cloudflare, I guess.
In other words, you are the supply chain. You're responsible for the bugs you create, but at least they are your bugs not caused by upstream's upstream's upstream's maintainer installing an infected JS library.
Shall we call this "vertically-integrated programming" then? :-)
The article is dated August 2026. Synacktiv (a different company) reported the very same vulnerability for older system managers/controllers already in 2023. Their report[1] says Danfoss told the products are EOL and should be upgraded. At no point did Danfoss fix the same issue in 800A. Typical.
Back in 2016 when we were integrating their 850 series system managers we encountered an issue with the HTTP API returning 400 series errors over slow links. We sent them PoC code written in Python 3. One month later they sent us an email, complaining that they first had to backport the PoC code to Python 2.7 as that was the newest version they could install. They also attached a "fixed" PoC code snipped where they had removed the artificial delays that did not trigger the issue. Danfoss never did anything to actively fix the issue.
One year later I browsed changelogs for the commercial RTOS that Danfoss used and realized the issue was fixed upstream in 2010 or 2011. That means their AK-SM 850 had at least six years worth of unfixed bugs.
[1] https://www.synacktiv.com/sites/default/files/2023-10/synack... (despite saying SM800, the firmware in question is for AK-SM 850)
Every now and then our customers ask if we can add remote control for specific parameters but we've always turned them down, citing liability reasons.
Re: legacy Danfoss systems such as AKM, 720 and 850 there is no way to have read-only access (for different reasons in each case). I haven't been able to find weaknesses in the new 800A yet, but that's only because I have not had to try yet.
Danfoss AK-SM 720 or 850? Pull the ethernet cord, now.
The latter can be flashed with the new 800A series firmware which is safer, but I still would not put it on the public internet under any circumstances.
Sigh. It's OpenID (the original one) all over again? Everyone wants to be the auth provider, nobody wants to accept other auth providers.
OS-specific abstractions should not leak to web apps under any circumstances.
I would only recommend using it instead of the standard Arduino Processing IDE.
Sigh.
Write a C or C++ API that works with pointers. Make it handle null pointers and errors elegantly so that the API user can safely chain calls and only check the final result. Claude decides it's better to be safe than sorry and peppers its code with intermediate nullptr and return value checks anyway.
So they were never secret in the first place.
I have never understood the desire to have voting machines when a paper ballot works just fine. We tried electronic voting in three municipal elections in 2008 and courts ended up invalidating the results due to horrible usability issues.
A relative killed herself after her therapist was hacked[1] and the data was leaked. If that is inconsequential, I do not know what isn't.
Trying to insult someone by calling them gay and nazi[1] is straight out of the Russian online troll playbook. Nobody except people who personally drink that Kool-Aid would resort to such boring insults.
> just a case of FAFO?
Who fucked around and what did they find out?
[1] https://archive-is.tumblr.com/post/807369905134518272/the-fi...
https://gyrovague.com/2026/02/01/archive-today-is-directing-...
This is only because immigrants are willing to do jobs at wages and working conditions that locals do not accept. Employers in the Finnish berry industry were just jailed for human trafficking. Meanwhile the same companies have been loudly complaining that no Finn wants to work for them.
worktree add: `git worktree add` that creates a local new branch and a directory with the same name and sets upstream to match; alternatively checks out an existing remote branch.
worktree rm: Removes worktree directory, first checking it is in porcelain state. Then prunes them and removes local branch pointers if they match the remote ones.
These all are handwritten and probably buggy, but still less prone to errors than typing out `git worktree add -b foo-123-fix-missing-semicolon foo-123-fix-missing-semicolon origin/develop` manually every time. One pass with Claude or Codex would probably do wonders.
I've solved this by running thin bash script wrappers that keep the workflow SVN-like with a root directory that contains per-branch directories and a hidden bare repo).
Stop hiding public data and I might reconsider.
You can install one on the balcony below the railing level.
The housing company is responsible for the exterior surfaces and thus also responsible for whatever happens to fall on bystanders when it will inevitably happen.
AC installers are also notoriously bad at following placement guidelines.