Thanks, that is indeed dystopian

Can someone summerize the article, for some reason it thinks I’m using AdBlock despite not and won’t let me actually read it

The very silly argument the FSF is trying to make is that device A is not programmable because the firmware is baked into the HW effectively making it part of the HW rather than a separate entity. Therefore it’s a HW limitation and not proprietary software. Device B on the other hand has proprietary software uploaded to it which is not to be allowed under any circumstances and therefore must be neutered. I call it silly because as you so rightfully point out, the firmware blob could be literally the same exact blob, just stored differently

Yeah, that would be a much more consistent setup and I agree with everything you said here. I just don’t understand how being less programmable is good, it isn’t, I don’t see any world in which it is unless there is truly NO firmware involved and it’s pure HW.

This is exactly my sentiment on the matter too. Firmware is not software in practice although it is in theory. Proprietary firmware that can be upgraded is better than firmware burned into a ROM although the FSF disagrees. I personally run nearly 100% FOSS…S as in software, I have no open firmware, I wish I did…but it just isn’t realistic at this point in time.

This is basically the same argument that caused the libreboot vs gnuboot thing and I just personally don’t get it. It seems to me like the FSF is letting perfect be the enemy of the good. Having a FOSS driver isn’t something to be celebrated it’s something to be punished if the firmware isn’t also FOSS. Yes, ofc, FOSS firmware is better than closed firmware, but when almost no modern hardware has that as an option, it’s not even something you can really vote on with your wallet unless you just run ancient hardware all the time.

It matters because for me, a good chunk of the FOSS benefit is the auditability of code. Being able to make changes is nice and that’s the freedom bit, but being able to audit it is also a huge benefit. If the code is not running on the main CPU then the driver on the main CPU can contain possible exploits of firmware using the IOMMU etc so it becomes more tolerable than a closed source driver. Basically a firmware vulnerability effectively becomes a hardware vulnerability as opposed to a driver running with full kernel privileges and no oversight or containment.

Was he worried about the kid or his network lol?

Yeah, he did that…and then kept going for some reason. A separate subnet in a separate firewall zone that doesn’t forward anywhere but the internet should be sufficiently safe

Apologies, when I said free hardware I meant design as well as somewhat blending the term with free firmware. But either way the difference they draw isn’t really all that different when you think about it. It’s sort of irrelevant whether or not the firmware can be easily updated, what really matters is where the firmware is being executed. If it’s running on the device then it can be isolated by the host system, if it’s running on the host then it’s not really firmware but rather part of the driver. The semantics don’t change just because the firmware is “easily updatable.” Having it be uploaded by the driver provides security benefits in that it can be patched by the manufacturer after the fact and having firmware in ROM which can’t be patched doesn’t guarantee it’s more secure or even less complex in design. I guess I just see it as a somewhat arbitrary line and I personally don’t agree with it

To be clear, I’m not saying I don’t want open hardware, what I’m saying is I don’t get the point of allowing closed hardware that doesn’t require a firmware blob as opposed to closed hardware that does. That’s a very arbitrary and silly line that does nothing useful. They’re going on this crusade of “no blobs.” But why? There’s lots of hardware that already has closed blobs on the HW, but because it’s not uploaded by the driver those blobs are ok? You either have to say all closed firmware is bad and we’re going to take a stance against any devices which have any amount of closed firmware, even when shipped on ROM in the HW. Or, closed firmware is tolerable so long as the driver is fully FOSS. I love the idea of not having closed firmware but I just don’t get the intellectual inconsistency here.

If I’m not mistaken doesn’t the firmware in question get uploaded to the device in question and run on said device not the host CPU? Those devices are already closed and often already running proprietary firmware. I don’t really understand the war against uploading blobs to them? I love FOSS and more power to anyone who wants to do this but it seems excessive.

Look, I love FOSS and open platforms, to the point that I will only run proprietary software if it is sufficiently sandboxed AND there is no alternative. Unfortunately, hardware just isn’t there right now. You basically cannot have a modern computing experience on fully open hardware. At some point you have to make a compromise with it, it’s unfortunate but it’s the world we live in. Typically that compromise is either all open software with closed hardware and firmware, or all open software and firmware, with incredibly old or restricted hardware (which is still closed). I have yet to see any solution that involves truly, fully open hardware and so you basically have to just draw an arbitrary line and say “this is good enough.”

Sounds pretty nifty, I’ll definitely check it out

I’ll have to test that, I have 16C/32T so I’ll try dropping my compiles down and see if I do get diminishing returns. Never really considered that. Also I do not use CCache, I’ll have to check it out though because it does sound really useful.

The IP suite is not nearly as neatly layered as OSI was and the OSI model doesn’t neatly fit the IP suite since it wasn’t actually designed for IP at all. In the IP suite layers 5 and 6 basically don’t exist in the OSI sense, TCP handles things that are part of both layers 4 and 5 in the model despite being a single protocol, etc. The OSI model is often considered obselete as it just doesn’t actually fit the IP world all that well but it’s been around so long and does have uses in certain situations that it tends to stick around.

No idea, I use mercurial mostly

What does the ChromeOS of Linux even mean? ChromeOS is already Linux

I have a friend who won’t leave windows because of League…in fact when we work on projects together I often have symlinks in my repo and he won’t even turn on developer mode to deal with them because it means if he wants to play league he has to restart his computer since it breaks the anti-cheat…so I have to make sure to desymlinkify any repo I expect him to clone…it’s cursed how much of a hold a stupid game can have.

That makes more sense and is…even worse tbh because that’s actually enforceable and so obvious I don’t know how I missed it. That would also probably impact Tor since those IPs are already heavily reputation damaged. The stuff governments have been pulling recently is just insane

You good sir underestimate the stupidity of courts