No, every service provider must remove infringing content when reported. That is not the case on Telegram.
Also on Mastodon: @[email protected]
Want to send me a tip? XMR:89oiUKyACFZ655sTikh42RF8wpd46EQDmbTQUQiHHRWFEatjp5xxj4tZBhMMfjC4X45qvq4EdEGXkBsdxT1kP9xyVia8mPD
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)
It’s so hard to differenciate manipulators from plain idiots 😔
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.
Insecure checksumming though (sha-1)
Or use the open-source Minetest instead?