Built In Art Glazing / Preventative AI Art

[Rudy-Orozco]

Describe the Feature

The feature I would like to see added is possibly some sort of built-in Art Glazing to prevent art being used in AI Learning/Web Scraping.

Additional Notes:

• Have users either opt-in/out on this feature
• When a user sends a picture, that exact picture would be replaced with a glazed picture when replaced
• Resource I found: https://glaze.cs.uchicago.edu/index.html

I'm not a professional programmer and still in university studying CS so I don't know how feasible implementing a feature like this is or if there is any sort of API available out there, but I thought this idea/request would be good to bring up given the state of the world and the internet, and possibly give peace of mind to artists who would like to post their art without worrying their art may be scraped in the internet for AI training.

Attachments

No response

Describe Alternatives

If not possible to implement a feature, possibly require users to log in to view any images or such.

Not a lot of alternatives I can think of as of this moment.

Additional Context

This feature comes from concerns from users who are artists and/or people who usually post a lot of art. Thinking that having a built in functionality that will automatically protect art/images from Generative AI would make the process of sharing art publicly more streamlined and easy.

[surfdude29]

This is an interesting idea, but unfortunately the Glaze software doesn't seem to be open-source, so I think Bluesky would have to enter into some sort of commercial arrangement with the University of Chicago.

There might be money in the Bluesky budget for that, but I wouldn't bet on it tbh.

I think it might be more feasible – in the short-term, at least – to spread awareness among artists that they can "glaze" their own images, either on their computer if they have one that meets the system requirements, or by using the free WebGlaze service: https://glaze.cs.uchicago.edu/webglaze.html before they upload their art to Bluesky.

[celozaga]

"If not possible to implement a feature, possibly require users to log in to view any images or such."

This is a terrible idea, this will not solve the issue either, since bluesky use an open protocol, so your content could be in another client. Unfortunately you will have to live on a web that scrapes your content for AI, there is not much you can do about it.

[kyefox]

Burning money on expensive GPU time on questionable copy protection is...questionable.

[Invertex]

An alternative compromise here might be to have a profile setting that allows users to input an "uploaded content processor service". So when a user makes a post, the URL is queried with this content, and returns the processed images/video to use in the actual post.

I don't think such a service exists yet, but if BSKY laid out some expected send and response structures, then it would open the door for that to be built.
Basically a similar idea to Feeds. We could end up with free options but that are slow, and premium providers that give really fast results for a small subscription fee. People would even be able to link to their own self-hosted processors.

This kind of feature would also allow people to extend it beyond just Glazing, I could see people implementing automatic watermarking/branding for example so they don't need to manually add it to their works each time.

Ideally the request would continually send back a progress report as well so the user knows it's being processed and can judge how much longer it's going to take.