>own 64TB server >want to host images / memes for free

>>62026952
ZFS.
Nextcloud.
Done.

File: yuru.jpg (62KB, 567x600px) Image search: [Google]

62KB, 567x600px

>>62026952
the lazy/naive approach is to just compare hashes on upload

>>62026952
Set up an SQL server with id, filename, file hash, and any additional info, and corresponding indexes

>>62027004
You still have to compare the file contents in the event of hash collision.

Hydrus Network. It's made specifically for what you're asking and can even do IPFS.


You're Welcome.

>>62026952
Preventing cheese pizza is a bigger concern

>>62027053
>You still have to compare the file contents in the event of hash collision.
No, you don't.

>kiss like a kloss kunt

>>62027053
>SQL
This is why nobody likes you

File: 1503378024602.jpg (185KB, 750x1009px) Image search: [Google]

185KB, 750x1009px

>>62027878
>preventing

>>62030539
and what would you recommend?

>>62030640
Not-SQL

>>62027878
That's not something you can prevent.. It's data.

You can create a system where it's easy to report that sort of content, but then you have to have moderators. Which is precisely what file hosters are doing now.

Any free hosting without moderation on content will get filled by cp. Literally every time.

>>62026952
>>don't know enough about webdev to detect and prevent duplicate uploads etc- 13 posts and 2 image replies shown.
look up perceptual image hashing, it absolutely owns at this

>>62030728
So moderation is the only solution?

>>62031222
Google has an API that can detect porn, no idea how well it works for THAT type of content.

>>62030640
You honestly could just keep all hashs in memory and back that up to disk every so often.
It's not like some faggot's meme hosting service would receive enough files to ever run out of ram this way.
That's probably the fastest and simplest way of doing this.