Holy shit, this is fucking awesome

@g-m-f Or at least like an exploding phone it something!!

@g-m-f @linuxxx I have been through worse

@dfox Would be great to get some technical background information :)

@schlomm They hash every picture. If a pic with the same hash has been uploaded recently, it notifies you. The hashing is also why it can't detect reposts if the picture was resized

@nyjan hmmm we need more power for more powerful repost prevention

https://github.com/jenssegers/...

For the curious ones

Welcome to Devrant 2017 😂

Algo no want your reposts 😂

This is GREAT news!

@dfox 10x shyt right there mate 🖒🏽

@dfox
Please don't mind the curiosity of a young dev, how do you search to check if the same image has been posted recently? Hashsum check?
I'd say maybe the gud ol' image comparison and search, but that would probably take a hell of a lot of time...

@Cybersapien I think the easiest way would be to store the Hashes in a database and on every post sumbit with a image to force a check with the DB.

I personally would go with a cached DB on a cluster to save ressources and get blazing performance. Or the cheaper one, to have a small dedicated server for it.

You just need to cache every new hash once, because they are not changing anyway.

Check above, somebody posted a github link for PHP Image Hashes

@Cybersapien yep, it's just a simple md5 hash. We also store a phash (perceptual hash) for each image but we don't use it because it seems to be extremely inaccurate.