linuxandrew

They use SHA-2-512 everywhere else already, presumably for post-quantum resistance. I guess it gives them a smaller cipher footprint? They use the same data type in their codebase for hashes? 512 bits is sufficiently future proof? Future use cases that haven't been thought of yet, that require a secure hash? 64 bytes isn't that much overhead?

But I'm really just guessing, I'm not sure what their reasons are.

I agree in principle - SHA-2-256 could be a reasonable hash function whilst maintaining the properties of a secure hash function - or less than that if collision resistance isn't needed.

I always though the 16 bit port was too little.

GNUNet CADET (admittedly a very experimental and non-production system) uses a 512 bit port number. A port can be a string, like "https" or "my-secret-port" which is hashed with SHA-512 to produce the port number. I like this idea very much and dream of it becoming a reality on the web.

OP mentions DigitalOcean as a compute provider. Is there much info on which compute providers will ban you for, say, P2P or BitTorrent activity? Presumably this is against the ToS for most providers.

There aren't many good alternatives to ZFS if you specifically want snapshots and compression.

LVM? Managing it sucks and the performance is bad (there's plenty of information on this).

I think Red Hat's Stratis was supposed to improve on some of this but it's not mainlined yet. For a while it sounded like Red Hat were going down the device-mapper functionality route of Stratis, VDO, dm-integrity and XFS, but I don't know where this is at.

Btrfs is probably the closest bet, but it's software RAID 5/6 has the known write hole bug.

Still waiting for bcachefs to get mainlined.

ext4 doesn't do CoW. XFS kinda does with its reflink functionality but it doesn't do filesystem-level snapshots.

Short answer, yes

As you mention, it differs from system to system.

When it hits that threshold it becomes immediately noticeable - I/O performance will basically fall right down. At my old job we noticed it around 93% on Solaris 11.x, and maybe 85% on Solaris 10 off the top of my head, on two different production systems. Best practice was considered to keep pools on any ZFS system (OpenZFS or Solaris) below 80%.

In terms of the protocol IPNS, DNSLink and PubSub come to mind. You can publish things that change over time.

IPFS also does some deduplication against the data when you publish things.

In terms of the software, browser integration, which there isn't a whole lot around for BitTorrent AFAIK.

I've been meaning to use Manyverse for ages, but admittedly I've been delayed by procrastinating setting up my own SSSB pub node.

The DHT sounds nice, in theory, but I heard in practice it doesn't work well which is a shame.

I might just be living under a rock down under, but I don't really get what's satirical about that news segment. Is it the lockdown whilst having low case numbers? Only one death in Sydney on that day?

Just keep in mind Australia has, unfortunately, low vaccination (< 15%) due to low supply. The low case numbers are due to the sharp lockdowns. The sharp regional lockdowns are to contain the virus so the rest of the country stays relatively free of the virus. Things have been relatively "normal" outside of the lockdowns.