I use Audible a lot, and so far they've been good-to-okay about labelling ChatGPT as a co-author, Virtual Voice as a narrator, etc. It's not the labelling I have a problem with. It's that I can't use that to then just exclude them from my searches.

If an app says "I'd like local network access to find other copies of myself", and you say yes - you're not giving it permission to find other copies of itself. You're giving it all local network access.

If you give it 'full disk access' because it wanted to access one file, and 'local network access' because it wanted to scan for copies of itself - you've given it full permission to export all of your data to your LGTV.

https://www.youtube.com/watch?v=pFwiLa3TYwg&list=PL1T3N4t2kU...

> Sunspots: LeVar Burton, Michael Dorn, Jonathan Frakes, Patrick Stewart.

uNF!

The xkcd was 2007 [0], the Debian issue was 2008 [1].

It was used in pretty much every blogpost describing the Debian issue, but it wasn't created because of the Debian issue (unless they gave Randall an 8-month head-start before disclosing it).

(I don't mean this as a "well akshully" - but for me it's more impressive that it's a truism that keeps coming true, than if it was just a swipe at them in the first place)

[0] https://web.archive.org/web/20070930232116/https://xkcd.com/...

[1] https://lists.debian.org/debian-security-announce/2008/msg00...

(This may not translate well for USians; Quake disregarded keymaps, so the console wasn't actually on ~, but on "the key that would be labelled ~ in the US". On UK-PC, that's backtick, on Uk-Mac, that's §.)

I pictured having a current driver on each plane, so the data bits coming in would be enable bits for the current drivers. Which obviously means 18xQty current drivers.

I think you're describing having one big current driver for the whole job, and then data bits drive the inhibits to counter them.

I guess I'm looking through too modern a lens - pumping 18*600mA into the write cycle, plus (up to 18)*600mA into the inhibit, sounds insane to me (hitting 20A for a write) - but I can see that multiplying the current drivers may have sounded nuts in the 50s.

If a write cycle is just a read cycle with a) a reversed polarity and b) you don't care about the contents of the sense line - I don't get why current coincidence is sufficient during the read cycle, but not during the write cycle?

Every description of this I've ever read, sound like inhibit and current coincidence solve the same problem - but have never left me clear on why we need to solve it twice.

Also the same way we got viruses, long before anyone I knew had the Internet.

    journalctl >/tmp/all.log  0m59.763s
    journalctl | grep -c sshd 0m57.767s  (otherwise >all is the only example encumbered by write speeds)
    wc -l /tmp/all.log        0m0.336s
    grep -c sshd /tmp/all.log 0m1.776s

We blame usb-c for all this, but it does feel like some mffrs are going out of their way to screw it up.

It seems this should just be a single input field styled appropriately, but it feels like there must be an underlying reason I'm missing.

Almost 30 years, and every so often I still wonder about where that got him.

(Not that I'm claiming anything's original here, ftp & smtp are both in the nwg/ietf family tree, which makes it easy to draw parallels. There's probably 100 other influences.)

I think it's neat that you can still find echoes of this. MAIL worked by just appending to MLFL, separating records with CRLF.CRLF - which is still how Data segments are terminated in SMTP.

But this cost-effective route isn't readily available to most people, as most people don't build homes. Developers build lots, and then sell finished homes. So you need to entice developers. And historically, "the stick" is the only enticement developers remotely pay attention to.

"If you want a swift brick, install one yourself" is much easier said than done - you're talking about removing an existing brick, replacing it, hoping you don't damage the course or the cavity, probably voiding any warranty on a new home, etc. It's certainly not a £35 retrofit.