pleroma.debian.social

pleroma.debian.social

Wouter Verhelst | @wouter@pleroma.debian.social

Debian Developer. husband. ex-FOSDEM organizer. Tennis lover. Amateur musician.

If it ain't fun, you're not doing it right.

Doing this incentivises the device manufacturers, who are in a better position than anyone to write free replacement firmware, to actually do so.

Instead, the fsf caved to the people who push non free embedded software and told them it's allowed, as long as the fsf can pretend the embedded software is not there.

I find this sad, and a betrayal of everything the free software movement stands for.
@lxo
@mjg59

I would have been fine with an ryf campaign that said, say, at least X amount of the embedded software in the device must be free software, and no device can be used that requires non free software if alternative for the same function that doesn't require it exists, and no device, whether with free software or not may require cryptographic signatures for changes unless the owner can control the keys.
@lxo
@mjg59

That's software, but it can't really be free software (because you can't change it even if your wanted to)

Anything that can theoretically be updated or loaded from outside the die though is software. It doesn't matter whether it is "indistinguishable" from hardware, the fact is that it *is* software. And as it is software, the only ethical thing for it is to be free.
@mjg59 @lxo

@lxo
Let me put it this way.

There are only very few cases in which firmware really needs to be embedded in the hardware and can't be put elsewhere.

The initial few opcodes of a CPU are a good example: those can't be outside the CPU because it still needs to initialise its components and so there is absolutely no possible way it can be outside the CPU die, and it's small enough that it doesnt matter if it's not updatable. @mjg59

@lxo
That's an opinion, not a fact, and one I very much disagree with.

Software is software. It doesn't matter whether the software is burned in ROM, it's still software.

To claim otherwise means you're fine with running non free software.

I'm not. I accept that it's not possible in today's world, but it's still not a good thing.
@mjg59

@lxo
And although I don't think it works for me, I can understand the argument for Linux-Libre. If there is no free firmware, and you prefer to keep your hardware unmodified, sure.

What I'm saying though is that forbidding any form of update, ever, of the firmware, and doing so in hardware, is wrong, because it makes it equally impossible to replace the non free firmware with a free one.
@mjg59

@lxo
It would be one thing if you advocated against firmware that can't be changed without a signature by the hardware manufacturer, but that's not the case here. You're generalizing that all hardware requires signed firmware blobs.

I agree that verifying firmware signatures in hardware is evil and should be outlawed. But hardware that does no verification, or that verifies only a checksum, in hardware? That's perfectly fine.
@mjg59

@lxo
When there was no free GNU system yet, most people believed that Emacs was a nice editor but there is no chance they'll ever succeed in writing a free os.

When there was a free compiler and a free libc, must people were like, this is a nice user space but nobody will ever make it a fully free os.

At every stage, the GNU project proved them wrong.

Why would the situation be different for non free firmware replacements?
@mjg59

@lxo
Worse, they required that firmware not be updatable for a piece of hardware to achieve the 'restricts your freedom' badge. As a result, if someone builds a free replacement for a bit of non free firmware in the device, you can't even make it free anymore.

This is sad.
@mjg59

@lxo
Today, there is no way to run a computer without non free firmware. The good and proper way to handle that would have been to accept that (as with the non free operating systems in the early 80s) and to fund/promote/encourage projects to produce free replacements.

Instead, the fsf chose to put their heads in the sand and pretend non free firmware doesn't exist when it's burned to ROM.
@mjg59

@lxo
In the early 80s, the fsf accepted having to run non free operating systems as there was no option at the time to run a free operating system instead. As soon as that stopped being true, they stopped accepting that. This was good and proper.
@mjg59

@lxo
Software loaded to ROM chips is still software. Otherwise I can make Windows be freedom-respecting by burning it to ROM chips.
@mjg59

@hrw
I don't have that, as I do server auction, not Hetzner cloud.

@hrw
I do like the 'restrict your freedom' bit though. Mind if I steal it? ๐Ÿ˜‚

@hrw
I mean, what you call 'rant' is what I call 'the whole point of that blog post', but sure ๐Ÿ˜‚

Got an email from Hetzner.

'Update on our pricing'

Long and extensive text about how the market is evolving and things are getting more expensive and how they're genuinely sorry and and and that I skip past after the first three or so sentences to just figure out how much they're bumping things by.

โ‚ฌ1.27/month

๐Ÿ˜‚

No sweat Hetzner. But this kind of information? That's why I love you guys.

@mcc
Oh, I see now that this is a 'no AI' thread. Sorry, missed that.
@liw

@mcc
I use keepassxc on my laptop, which is synced using nextcloud to my phone. There, I use keepassdx which is able to read the same files.

https://f-droid.org/packages/com.kunzisoft.keepass.libre
@liw

watch nerd question
@brennen
Since it was a birthday present I don't know how much it cost at the time, but I can say that
- my parents and my 4 siblings all put money together to pay for it, so it wasn't cheap, and
- whatever the price was, it was worth it given the number of years I've gotten out of it.

ยป