From my understanding, Linux-libre actively blocks known proprietary firmware
somehow. I don't think this is a good idea. It's like if an OS scanned
binaries to detect if they were known proprietary programs and refused to run
them; it's a digital restriction mechanism. The blobs should just be taken
out, not blocked (like Debian's de-blobbed kernel).
However, an anti-feature being present in a free/libre program doesn't mean
you don't have freedom with it. You can take Linux-libre, remove the code
that blocks non-libre firmware, and compile it.
Of course, the irony is the only reason to remove this particular digital
restriction mechanism would be to sacrifice your freedom, so those of us most
likely to use Linux-libre aren't going to care about it (after all, if you
want to sacrifice your freedom, mainline Linux has you covered). The only
reason I care at all about it is I think actively blocking the blobs makes
the project look hypocritical to outsiders, and it doesn't do anything
useful.
