/v/ - Video Games

make your archive a public thing so people can download/upload to it, that way your content gets spread far and wide

of course you will get reamed by the jews if you do this

>>14894934

That's the thing, I was talking about private archives. Publicly setting up an FTP server with such content is too risky. That's why we have P2P.

>>14894949

It does still carry risk, but only seeders in nanny states will get fucked, not every one will get taken down. That way, content is still available. It's not the same as having one server with one guy responsible for it, as opposed to a network of people sharing the same file.

Besides, I don't know much about FTP servers, but I do know that you need its IP or domain name in order to connect, and it's not so difficult to find an IP corresponding to a domain.

There is no such thing as secure storage for the long term. Not even really in the short term. There is only redundancy, and redundancy is only workable if you keep making fresh backups on newer drives/disks/servers/etc.

DON'T STORE DIGITALLY! Do it physical instead and bury it on your farm.

(((They))) will use EMPs and weapons to destroy all that kind of stuff. You think it hasn't been thought of? You think you can stash your porn and that version of Mein Kampf and get away with it?

>>14895270

This, though some company is supposedly working on CDs that are physically engraved rather than using laser activated dyes. Should make archival purposes a lot easier.

>>14894929

There's that archive thread and board.

There's that IPFS(?) thing in /tech/.

There's literally hundreds of MEGA links.

I personally keep multiple backups of everything.

Also trying to catch up on all those mentioned above, figuring out which is a good secure way to share shit.

>>14894929

If you plan to archive stuff on a drive that won't be used for two years or more, don't use Flash-based memories like SSDs. That shit loses all info when depowered for too long.