joeyh

The commit it reverted has a high probability of also being generated with an LLM, though without disclosing that in the commit message.

Amusingly, the only DCFCs near me that charge by time and not kwh are run by utilities.

That PR was apparently accepted by the operator, not by the bot. Kind of weird.

Current branch without bloat is to cat .git/HEAD, and if that didn't exist, run git symbolic-ref HEAD. The first is faster and works in the common case where you're in the top of a git repo. In either case, run it through ${branch##*/} to strip down to just the current branch.

I have used this for a long time, never understood how people would put all of git in between them and the next prompt.

This video has been edited at 0:42, likely removing something from it. Source: CBC analyst

The command is `bts` in devscripts. I wrote it in 2001.

The best way to do this is to design something that is not appealing for those people to use, but is appealing for the people you want to support to use.

It's worth noting that a new installation of Debian will still display the same Eastern, Central, Mountain, Pacific menu to the user as shown in the screenshot. It just maps those to the non-deprecated names now.

You are confusing Russ Allbery with me, while at the same time making it sound like I have a problem with systemd, which is not the case. Russ remains a debian developer.

NEWS.Debian entries are displayed by apt-listchanges in a pager by default when running apt upgrade, as well as sent by email.

I have driven 20 thousand EV miles in the past year, with 50% of my charging being at public chargers (and 50% at home). I have never needed to wait in line, and have never needed to interact with anyone regarding charging.

A common misconception. git has always used binary deltas for pack files. Consider that git tree objects are themselves not text files, and git needs efficiently store slightly modified versions of the same tree.

This reminds of of a web page that did this for Ithaca NY circa 1995. The page was a static hardcoded shade of grey.

Steve Langasek decided to work on this problem in the last few years of his life and was a significant driver of progress on it. He will be missed, and I'll always think of him when I see a 64 bit time_t.

Hybrids have a smaller battery, so C rate limits maximum regen. For example, a prius can regen at 2 kw, while a model 3 can regen at 76+ kw.

Wise (nee Transferwise) requires a passport style photo taken by a webapp for KYC when transferring money. I was recently unable to complete that process over a dozen tries, because the image processing didn't like something about my face. (Photos met all criteria.)

On contacting their support, I learned that they refused to use any other process. Also it became apparent that they had outsourced it to some other company and had no insight into the process and so no way to help. Apparently closing one's account will cause an escalation to a team who determines where to send the money, which would presumably put some human flexability back into the process.

(In the end I was able to get their web app to work by trying several other devices, one had a camera that for whatever reason satisfied their checks that my face was within the required oval etc.)

Nothing in the ToU says this is local only or not for ads.

When did you request that firefox back up the content to your profile? Bear in mind that a nontechnical user has no idea it does this, and a technical user only realizes it does this after reading the code or experiencing a crash. You "requested" this behavior implicitly by using firefox. So any behavior firefox has, now, or in the future with data you input is implicitly something you requested.

If firefox starts backing up your profile to a mozilla server, encrypted, you requested it. If there is an additional encryption key that lets mozilla decrypt it and sell it to OpenAI, you requested it.

Also, I am requesting that firefox send this post to HN by pressing the reply button. By the terms of firefox's ToU, this gives Mozilla a license to this content. That license is not limited to the duration of the http call if other firefox behavior that I have "requested" uses that content later. Perhaps they will scrape my comments from HN and use their content in targeted ads that firefox will display to me later. All allowed by the ToU.

Those tariffs have were entirely worked around on the Chinese side before the ink was dry. One easy dodge: Manufacture in eg India for a little bit more, sell those to the US, transport Chinese solar panels for installation in India.

I bought a pallet just after the tariffs were announced and the price today is cheaper.

Tea is absolutely NOT "taking steps to remediate this problem". They are grifters and part of their grift is claiming to take steps when called out.

vim-tiny is installed by default on debian (providing a vim command), and also has X removed.

about time to program websites to serve JWZ balls when HN tries these tricks to confuse its users IMHO

holy gratuitous question mark hackernewsman

decompressing gcc.tar.xz which contains foo.png followed by main.c, the decompressor is instructed by the hidden data in the png how to alter the code.

Running xz in a sandbox would not prevent an attack that causes it to modify source code in a .tar.xz that is being streamed through it.

dpkg-deb is linked with liblzma

Since a liblzma backdoor could be used to modify compiler packages that are installed on some distributions, it gets right back to a trusting trust attack.

Although initial detection via eg strace would be possible, if the backdoor was later removed or went quiescentit would be full trusting trust territory.

Not really. xz worked fine 2 years ago. Roll back to 5.3.1 and apply a fix for the 1 security hole that was fixed since that old version. (ZDI-CAN-16587)

Slight oversimplification, see https://bugs.debian.org/1068024 discussion.

details please? I do not see any such contributions to https://github.com/facebook/zstd

See comments about "Hans Janson" upthread, he appeared to collaborate on the exploit in other ways as well.