@thatbrickster Just because some parts of your computer run proprietary software means that you must run more?
I'm not sure what the use case of 802,11ax is really, as 802.11n is plenty fast as far as wireless goes - if you really want a very fast and reliable connection, you shouldn't use wireless and you should go for 1000BASE-T over cat6 instead.
@thatbrickster >802.11ax I' think you'll never find a entirely free/libre hardware/driver then, as stated many years ago by thinkpenguin FCC laws passed in the past decade made it non legal to have free/libre implementations due to "security" concerns.
@Suiseiseki If the kernel already has a driver for it, I wouldn't be adding any more blobs. I'd be using what's already there.
AX has better latency than N, not to mention newer dongles have better signal performance. The TP-LINK dongle I'm using is certified to work under linux-libre, I have it because it's virtually guaranteed to work. The main downside is that it doesn't pick up my network very well.
I'm with you on going wired. I'd love to have a WiFi-free home, alas I can't afford that luxury. I've yet to set up an old Xiaomi router as a wireless bridge since I haven't had time lately to do that.
@thatbrickster >If the kernel already has a driver for it, I wouldn't be adding any more blobs. Linux doesn't contain much proprietary firmware anymore, most was moved to the separately distributed linux-firmware (but of course there is still some left).
You're certainty going to add a crapload more of proprietary software by downloading linux-firmware mind you.
>AX has better latency than N, not to mention newer dongles have better signal performance Minor convenience features drives you to go out of your way to give up more of your freedom?
"The FCC has attacked TP-Link's non-compliance with new FCC rules despite being mostly in compliance via a total lock down. This has caused the lock down situation to go from bad to worse. While this is being sold in the media as FCC doing good by forcing companies to cooperate with the open source community it's actually undermining the communities values and ability to get a complete set of source code upstream for *any* modern devices. It's not acceptable that we should have to lock down the main firmwares, but it's worse to ask manufacturers to lock down specific wifi firmwares only."
@thatbrickster >Someone's not reading the thread. I've read the thread just fine.
>If you'd have told me the FCC was bullying makers not to share source That wouldn't be the truth. The FCC is bullying manufacturers into implementing digital handcuffs, but they don't specifically mandate that the wireless firmware is proprietary.
Sure the FCC is encouraging proprietary wireless firmware, but every single 802.11ac and 802.11ax wireless chipset manufacturer made the decision to do that from the start all by themselves and that would be the same if the FCC was to no longer exist.
Sharing source? Is that a line from the "open source" infidels about "sharing" proprietary software?
>rather than belittle me for thinking about this I'm asking questions, the only person being belittled is you belittling yourself, as you won't give me honest answers.
@Suiseiseki Someone's not reading the thread. If you'd have told me the FCC was bullying makers not to share source, rather than belittle me for thinking about this, you'd be more persuasive.