Self hosting helps make the internet more decentralized, but at the end of the day someone else owns that series of tubes.
This is probably a pipe dream, but I think it would be cool if we self hosted not just servers but networking infrastructure as well.
I have an extra class amateur radio license and one of the many niches within the ham radio hobby I'm interested in is packet radio and wireless mesh networking.
Packet radio could technically refer to any RF communication that uses packets, including wifi, but I mostly see it used to refer to the AX.25 protocol, which works like an old-school dial-up modem in that it converts data into audio tones that are transmitted using FM or single sideband radios built for voice communication. AX.25 is used mostly nowadays in Amateur Packet Reporting System (APRS) which is used to report location and status info. There's a website, aprs.fi, where you can track vehicles sending their location or weather stations reporting conditions and so on.
In the olden days there were tons of bulletin boards hosted over AX.25 all over the globe that you could reach either directly or through repeaters. There are a few hangers on, and I even hosted one for a while but nobody visited. You could by hardware terminal node controllers (TNCs) that had a BBS feature, and nowadays there are a few software TNCs available.
Several Wifi frequency bands overlap with ham bands, and various projects have arisen that modify commercial wifi gear to turn them into mesh nodes forming a wireless wide area network, operating under FCC part 97 rules rather than the unlicensed part 15 rules that they use out of the box. This allows higher power and channels otherwise off limits to wifi stations. The project I'm most familiar with is Amateur Radio Emergency Data Network (AREDN) which uses a fork of openWRT firmware. I've tried a couple times to get the other hams in my area interested in setting up a network, but it's slow going.
There are also ham-adjacent projects like Meshtastic that I'm not as familiar with.
This barely scratches the surface of what's out there. The ham bands are explicitly non commercial and there are limits on what you can transmit and how much bandwidth you can use, but I dream of a day when everyone's wifi router meshes with all the other routers in the neighborhood which is connected to all the other neighborhoods in the city which is connected via repeaters to all the other cities and so on. Sure it would be slow, but we'd be communicating on our own system that only costs as much as the hardware you run it on.
I'm ok with both, but prefer co-ops because the members get direct voting on large decisions by default, rather than a proxy vote via an appointed government worker who answers to the municipal government.
That said, there is no reason these can't be one and the same, the local government could fund the establishment of a regional co-op and maintain audit and some other limited authority over it.
I also support long-distance fiber infrastructure being built and maintained by worker's co-ops that would then get paid for service by the regional ISPs. Worker members would be highly motivated to maintain good uptime, and hiring/training members who live local to the fiber lines in remote regions would be possible with the incentive of worker ownership. Once built it is a long term maintenance and security business with steady return, perfect for a worker's co-op that could be financed with private capital at decent ROI.