I guess if the copyright trolls got their way, there would be no general purpose computing.

Exactly. These kinds of statements are so naive.

I use BTRFS for the same. Being able to check for and repair silent corruptions is a must (and this is without needing to read the whole drives, only the actual files). I’ve had a lot of them over the years, including (but not only) because of a cheap USB controller also.

Unfortunately we are at a point where Cisco Cloudflare and Google are held liable for filesharing-related domains their DNS relays are resolving IPs for…

No, every service provider must remove infringing content when reported. That is not the case on Telegram.

No matter which encoding is used to store data, the hoster is still responsible for it. On mega, the data is encrypted, yet mega is still held responsible for removing content reported by copyright holders (the decryption keys being included in reports).

How come those big hosters get away with such infringements? I guess they must be less popular than Megaupload and such

i2Psnark is an alternative. With a lot less features (and not mentioning the UX)

I’m still using MPD+ncmpcpp. For remote access, I use Wireguard and stream via HTTP on VLC. It’s amazingly fast and lightweight (26MB RAM for 30K+ songs).

MALP also works on Android, might be better with no physical keyboard (now supports streaming also).

A bunch of eDonkey servers were seized in 2006. This was before the implementation of Kademlia in emule. It highlighted the vulnerable centralized part of the protocol and pushed people to alternatives. Also compared to bittorrent, the lack of moderation and low speed played a role.

The onion option makes more sense (standard solution, battle-tested). Not sure about POW resilience, compared to distributed hosting though.

Yep, you can gossip the list of peers with that identifier.

IPFS has 2 and 3 (they almost f*ed-up 3 with CID v1 actually)

This would be the identifier: rad:z3SNcAzHydhWtfaFTiq9S643GQjYU

I wish they chose IPFS instead of Bittorrent v1.

Last published attack estimated the prefix generation (not random collision) to less than 100k$.

I’m able to max out my 1gb/s card easily most of the time.

deleted by creator

Insecure checksumming though (sha-1)

I’m still waiting to see that coming to all on my apps…

Restored security (SHA-256) is the first reason.

But what’s most interesting to me is the single files hashes.
Each individual file will get it’s own hash, reachable from the DHT. It also seems that there will be some kind of standard hashing method allowing to get unique reproducible hashes (no more piece size or parameters). Two persons would always obtain the same hash for the same file even for different torrents. This is all to reduce swarm fragmentation.
So it would be similar to IPFS (except this one broke his promises by introducing several multihash versions…).