Inspiration
Lets say you run a creative e-commerce agency and you sent over an image to your client.
A few months go by and the client has now cropped this image and added text so they can run ads on it. Now they want you make similar versions of the image because the ads worked. They sent over the image on Whatsapp and give you a short deadline. Whatsapp destroys all the embedded provenance of the image. Meanwhile your agency has created 100s of AI images from different providers. How do you find the original prompt and the image?
What if there was a way to compress the information of an image into 64bits. Searchparty is an image generator that does exactly that. Once a model provider sends the raw image to the searchparty backend, it is converted into a 64 bit hash using Perpetual Hash. The image and its hash are then stored in a B2 bucket.
So when an image that was created on searchparty is cropped and altered you can still find it easily by comparing the hashes of all the images stored. PHashing works for audio and video as well. The only disadvantage is that its not completely accurate.
But this has a solution: instead of using phash, something more robust such as CLIP embeddings can be used.
What's next for Searchparty
Implement more robust searchability using Google's Image, Audio and Video Embedding models.
Note: Searchparty is on Render.com's free tier. Render's free tier spins the whole service down after roughly 15 minutes of no traffic. When it spins back up you will not see any images. This is a shortcoming of the free tier.
Log in or sign up for Devpost to join the conversation.