I do value the inconvenience. When I put an album on, I put an album on. I don't hit next, random, go wandering off down rabbitholes. I put the album on.
And I do see the cost as a feature, somewhat. It feels like I got something for my money, in a way that paying for a zip doesn't.
What you'll tend to notice with "willing participants" is that they're not looking for truth, they're looking for confirmation. No-one asks for proof when you tell them what they want to hear.
In my family it's the other way around - it's the people that used to tell us not to talk to strangers on the internet, and not to believe everything we see on the internet, who are now doing precisely that.
My understanding is that the "nugget of truth" that birthed the "routing around nuclear attack" myth, is that it was a consideration in Paul Baran's packet-switching work at RAND.
So it wasn't a design consideration for ARPANET, but it would have shown up in enough early papers to give the myth some legs.
bps are easy. packets per second is the crunch. Say you've got 64 bytes per packet, which would be a worst-case-scenario - you're down to 150Mpacket/sec. Sending one byte after another is the easy bit, the decisions are made per-packet.
> How do you physically solder a chip the wrong way around?
With effort, and bodge-wire. I've seen chips done dead-bug style when the board's been messed up (eg, the footprint is orientated for the bottom of the board, but placed on the top, and vice-versa).
It's definitely not something you'd ship, but a kludge that can get you working until the next board spin.
Which doesn't make any sense, because the article also claims that the chip was soldered in place. Solder generally only works between two pieces of metal, making an electrical connection.
So either the chip was glued in place and not soldered or it was soldered and electrical connections were made. Either way, the article is wrong.
Standard operating procedure for a board with a messed up footprint is to glue the chip into place upside down, and then use patch wires to make the correct connections. Obviously you fix this for production boards, but I have personally seen this done for prototype boards.
Training personnel on prototype boards is also very common. It's also very common to do training on non-working boards.
> Our experiences with that programme informed the development of Raspberry Pi 400, our all-in-one PC, whose form factor (and name) harks back to the great 8-bit and 16-bit computers – the BBC Micro, Sinclair Spectrum, and Commodore Amiga – of the 1980s and 1990s.
(emphasis mine)
So the 400 name is explicitly inspired by such systems, their next one is called the 500, and the upgrade to that is called the 500+. I'd say it's a pretty safe bet that's exactly the inspiration.
One of the main differences between the ZX Spectrum and Spectrum+ was the upgraded keyboard. The original had the famous mushy rubber keys but the Spectrum+ had an injection-moulded keyboard
Jobs was "inspired" by a visit at Xerox labs, they showed him a GUI built using Smalltalk (which they'd also invented). So naturally, he ran back to his office and invented GUI ;)
Or for third I guess lol Jobs demoed a mac gui to Gates, and apparently Gates ran strait to his Microsoft office, where he too invented gui. Jobs was very upset for years.
I think it actually was an Apple innovation, at least for {hobbyist, home, personal} computers. I did some digging and wasn't able to find anything before the Apple II+ in 1979. Please do prove me wrong, though!
And the co-creator of ARM, Sophie Wilson, still works for Broadcom - the company which bought part of the remnants of Acorn (Element 14). This is where Eben Upton worked before going off to start the Raspberry Pi foundation.
Jack Lang was involved in the Pi, having also been involved in Netchannel, the STB company which used the Acorn technology and had funding from Hermann Hauser, co-founder of Acorn.
David Braben, co-author of Elite (and author of Zarch/Lander for the Acorn Archimedes) was an early Pi supporter.
I think the common mistake they’re alluding to is Europe and north America having conflicting standards for colour-coding the pumps. So here green is unleaded and black is diesel, which can catch American tourists unaware. (Especially so with language barriers, “sans plomb” in French is not intuitively petrol/gas/benzo)
It'd be some fluke of an accident. You'd need to be targeting not only debian:testing/unstable, but specifically debian:testing-20240311. And then - making sure not to apt upgrade at any point so you don't accidentally get any updates from the last 18 months - you'd need to also install openssh-server to avail of the backdoor, plus a service manager because running sshd in the foreground killswitches said backdoor. And then don't forget to expose the ssh port otherwise our effort is wasted.
The most realistic way to hit this would be to have built an image 18 months ago, on top of :testing or :unstable, and then not update or rebuild it at any time in those 18 months - in which case removing anything from the repo wouldn't help you. Or be purposely trying to recreate an affected environment for testing/research, in which case it's on you.
You're not wrong that we should keep our shields up - but "update sometime in the last 18 months" perhaps isn't such a revelation.
One thing does come to mind though - I do wonder if there's a way to strongarm apt's dependencies mechanism into having openssh-server conflict with affected libxz versions, so that if you did apt update && apt install openssh-server in an affected image, it'd bring a fixed libxz along for the ride. (and the images don't carry apt manifests, so apt update is required and you would have today's package list.) You could still pin an affected version, so there'd still be enough rope to allow you to recreate a research environment.
I do value the inconvenience. When I put an album on, I put an album on. I don't hit next, random, go wandering off down rabbitholes. I put the album on.
And I do see the cost as a feature, somewhat. It feels like I got something for my money, in a way that paying for a zip doesn't.