Freenet is also based on middle-out compression.

No. Trying to push 30TB into Freenet will be interpreted as an attack on the network by other peers and they'll disconnect from your peer.

Freenet is better viewed as a communication medium than a storage medium. Data is prioritized according to demand, somewhat like an LRU cache. You can't upload 30TB and expect the network to preserve it for you.

On liability, running a Freenet peer is more like running network infrastructure that automatically routes and caches other people's traffic than intentionally publishing it. US law explicitly recognizes this distinction in the DMCA's provisions for transitory network communications and system caching. We discuss this in more detail in the FAQ.

You obviously haven't tried Freenet. You can join our room on River and you'll see no spam, no fraud, no hate speech, none of that.

Decentralized doesn't mean unmoderated. Systems built on Freenet can be moderated however their creators and communities want. River is moderated.

The difference is that nobody running one service gets to decide what everyone else is allowed to run.

Thanks for your questions, Freenet caches data but it isn’t meant to be a long-term storage network. It’s better to think of it as a communication system. Data persists as long as at least one node remains subscribed to it. If nobody subscribes (including the author), it will eventually disappear from the network. So yes, if only your node subscribes then the data will only exist there and won’t be available when your machine is offline. But if other nodes subscribe it will be replicated automatically and remain available even if your node goes offline.

Not from 2023, the linked video is from last month. https://www.youtube.com/watch?...

Corrupt government officials? WTF? Is this really Slashdot? Show your evidence.

There are two ways around that.

First, if you happen to be attacking your neighbor and you share L2 WAN with them, you simply put the 10.x address in as destination IP and the neighbor MAC address as destination MAC. Done. No NAT required, the traffic will just pass.

Second, some NAT implementations look at only a three-tuple of IP, port, and protocol. If you connect from port 40000 to some random site, the NAT will translate that to a different port, say 30000, and it will allow any traffic from the entire world to port 30000 to hit port 40000 on your device. Hopefully your device does not have anything running on 40000 so it will all be fine -- but it might not be. This type of NAT used to be VERY popular, because it makes things like P2P traffic work without having to configure anything.

So you are saying that the firewall on the ISP device is going to save you from the attack that NAT failed to save you from? Why don't you trust the ISP to get the firewall right for IPv6 then?

If there ever was a comment to show Slashdots decline, this one is it.

Reading all these comments makes it clear that we on Slashdot have become who we used to ridicule: Science-denying zealots.

That is somewhat misleading. In this case you control (more or less) the client, so you can install a root certificate on your firewall and the client and let the firewall do its MitM on all your traffic. If Windows tries to evade that, the firewall will fail to decrypt the traffic and block it, which was the intended result. If Windows does not evade the MitM, the firewall can do full L7 filtering just like in the good old days.

It is wild that companies get to manage pension funds. That kind of thing is not legal around here...

You can't do that. The copilot is not a real key to the keyboard protocol. It sends something like Windows, Shift, F23. You cannot sensibly combine it with other keys or make it reliably control a modifier state. This is completely unlike the Windows key which is not only its own unique keycode but also typically gets non-conflicting lines on the keyboard matrix, so the hardware lets you combine it with any other key.

There are still unused keycodes available, AFAIK. It makes zero sense that the Copilot key was crippled. If it was only crippled in hardware, vendors could fix that, but the only way to fix the Copilot key is to reprogram the keyboard controller firmware, which then makes it incompatible with Windows.