In D49773#1153892, @bz wrote:

Yes, you have vht80p80 supported apparently. That is 160Mhz on two non-consecutive channels. I have an open TODO here to get back to you to see as-to why that is not selected but given you are the only one so far I have noticed seeing this.

I've also tested it today, and things are much the same as they were. I'm finding conflicting information as to whether the base station I'm connected to supports 160 wide channels or not. Some resources I find say yes, some say no (it's a TP-Link Deco M9Plus - which is 'AC2200' it says). Either way, I'm not getting a 160 connection, and ifconfig still shows -vht160:

Suggestions as per jrm guidance

Insert newline, as per lwhsu.

OK, it's not a binary, phab thinks it is. Discussed with @dch.

Does this look better? 8859 -> UTF8 conversion It is NOT a binary, despite
what phab thinks. cc dch

Weird! I did notice on the diff that vim had replaced some none printing characters with correct versions - I presume because UTF8 support now versus when the file was probably submitted in 2016? Why it’s saying it’s a binary is beyond me though. Let me try redoing it, and see if I can convince vim to ignore changing characters.

We could add SRI hash (as I do with my own site, running Hugo) — which requires monitoring for changes. I have that in place on my site (cronjob, perl — I'm old — checker) and would be happy to monitor it here too. Extra work, but I've no problem 'owning' that.

Hey folks. This is the stats I'd like to add to the website in the simplest and quickest way possible. With a couple of upcoming blog series we have planned, it would be fantastic to see how they land across the main, doc and foundation websites. Thanks!