There are a lot of examples, but the most notable is the endorsement / promotion of the X60 / X200 with non-free EC firmware and a dial-up modem that requires non-free software to work.
While not a freedom issue, they endorsed PureOS even though it uses a Debian kernel (linux-libre Vs. Debian kernel, not going to get into that here) while another distro was denied for that specific thing.
> endorsement / promotion of the X60 [...] with non-free EC firmware and a dial-up modem that requires non-free software to work
Sorry, I may need a source on this. My X60 boots perfectly without any non-free firmware, and everything works (except the wireless card I swapped in, I don't know if also the original needed them). I'm asking for a source because I would like to understand how they endorsed it. If it boots without problems and you need an external dongle to get wifi I don't see a problem with that, from a freedom standpoint.
Really, I'm not trying to be a contrarian, just trying to better understand where my money is going.
> What is the boundary, in digital devices, between hardware and software? It follows from the definitions. Software is the operational part of a device that can be copied and changed in a computer; hardware is the operational part that can't be. This is the right way to make the distinction because it relates to the practical consequences.
> There is a gray area between hardware and software that contains firmware that can be upgraded or replaced, but is not meant ever to be upgraded or replaced once the product is sold.
Debian's kernel is deblobbed and contains only free software. If you can find an example contrary to this, it is a bug.
The poster on the thread you linked is making the argument that free software shouldn't be looking for non-free firmware, even when it isn't installed. That's... interesting and not something I've ever heard complained about.
The FSF doesn't endorse Debian because of the non-free repository which, while not officially a part of Debian, they consider a Debian. If you install only the "main" repository you will get only free software. The default install only contains the "main" repository.
It has long been the case that FSF-endorsed distros could not use the Debian kernel, even though it contains only free software.
It had always been my understanding that the intention is that the messages the Debian kernel displays looks like an error
message suggesting that the module should have been present. Even if
it looks less like an error, and is more matter-of-factly "such and
such functionality is disabled because nonfree.bin could not be
loaded"; reading between the lines, that sounds a lot like "install
nonfree.bin for that functionality".
However, following the more recent discussion, particularly the comments of Alexandre Oliva (the Linux-libre maintainer), I'm not so sure. I hadn't realized that many of the extreme deblobbing measures (replacing firmare filenames with "/* DEBLOBBED /") in Linux-libre were because it must not load non-free blobs even on distros that are hostile to that goal. On FSF-endorsed distros that are not hostile to that goal, what measures are* necessary?
Ironically, many GNU manuals are included in the non-free sections because Debian considers the GNU FDL non-free because it allows invariant sections - sections that cannot be changed.
While not a freedom issue, they endorsed PureOS even though it uses a Debian kernel (linux-libre Vs. Debian kernel, not going to get into that here) while another distro was denied for that specific thing.