There are ISO country codes.

https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes

Most AI image generators that generate images add EXIF metadata indicating that the image is AI-generated. This helps people who want to identify AI-generated images readily.

In the case of ComfyUI, it even includes the entire workflow

like, another ComfyUI user can just grab the image, drop it onto their ComfyUI Web UI and they'll be right where the generating user was.

Unfortunately, EXIF metadata can contain location information

some cameras and such add it

and this metadata led to people posting images at places like Reddit being doxxed after they didn't realize that they were posting their GPS location and maybe real name, stuff that some cameras attach. As a result, a number of image-hosting places simply strip all metadata, to prevent users from from accidentally leaking this information.

Pict-rs, the software package that Lemmy hosts run to permit image uploads, does this. Unfortunately, it means that those "this is an AI-generated image" tags get stripped off.

So, for example, on my system, with ComfyUI, using ImageMagick:

$ identify -verbose output/ComfyUI_00312_.png 

"Properties:prompt" has a JSON encoding of the workflow.

Sample images generated by various AI image generators are readily-available on civitai.com.

For this generator that generated this image on civitai, it looks like the parameter is "Properties:parameters".

I believe that there are a small number of such tags today.

It would be technically possible to just not have pict-rs strip that particular tag (or tags, if there are multiple that a given generator adds?) off, have a list of "AI-generated tags", then have Lemmy add some visual indicator that an image is AI-generated. I'd suggest that this is probably a better longer-term route to indicate that an image is AI-generated than manually-tagging post titles, for a couple of reasons:

• Spiders that index images on the Web will know that the image is AI-generated and can flag that for users and let them use that as a filtering criteria (e.g. Kagi Images permits for this). They aren't going to understand tags in post titles, but the metadata tags are somewhat universal.

• Doesn't require manual effort if an image can have some indicator or flair or whatever put on it automatically. And I guarantee that some users are going to get this wrong just by accident, because different instances have different rules. Easier to change how a computer works than to change human behavior across-the-board.

• Works on all instances.

• The information remains attached to the image even if downloaded.

• Works for images that aren't just the subject of single-image posts and don't have an associated title.

• Speaking purely for myself, I kind of like the open-source, collaborative aspect of sharing the workflows or prompts, since it helps other users see how an image was created and learn from it; it's something that I'm glad to see the generators include, and I'm kind of sad that we strip it off on the Threadiverse.

Yeah, I remember reading about AI Horde a while back and thought about it, but wasn't comfortable with having an system that fields requests from the outside world, as my GPU is on a desktop and I'm not totally sold on how well these guys have hardened the thing. If I had a dedicated compute node for doing renders, I'd probably be fine with it, as it just eats some electricity then.

Hahaha, that's fantastic. Thanks, @db@lemmy.dbzer0.com. I can't believe that I had been unaware of this for years.

I've got local hardware myself, but this makes generation way more accessible to random users on the Threadiverse without tying them to commercial services, including users who are using a phone and can't really run the stuff locally.

skims bot FAQ more

It does look like the bot tries to block NSFW stuff, but outside of that, it looks pretty permissive of whatever, and while the style list doesn't clearly distinguish between styles consisting of prompts for one model and different models, there are a lot of models in there that I recognize. Just append style: flux to the end of the prompt. It's got Flux (style: flux), Pony (style: pony), Pony Realism (style: pony realism), the Nova family (style: nova anime xl, style: nova, style: nova furry pony), Stable Diffusion 3 (style: sd3), SDXL (style: sdxl), Mistoon (style: mistoon anime), just from a very quick skim. I guess AI Horde must have a list of models and the ability to just download models or something if it doesn't already have them present on a node?

skims bot FAQ

Oh, dang, it even runs multiple models, and it looks like it can run Flux, which can handle fairly English-language-looking prompts.

I gotta see this.

@aihorde@lemmy.dbzer0.com draw for me An engraving of a skunk. style: flux

Hahaha, awesome, db0, didn't know that you'd set this up until now.

A couple of my favorites from that thread:

@FlyingSquid@lemmy.world

@ThunderWhiskers@lemmy.world

@YodaDaCoda@sh.itjust.works

@DredUnicorn@lemmy.world

@Thelsim@sh.itjust.works

@anonymoose@lemmy.ca

@itslilith@lemmy.blahaj.zone

@starcat@lemmy.world

@Tlaloc_Temporal@lemmy.ca

@Usernameblankface@lemmy.world (also OP here, also the person who brought the idea up in another thread)

@WandFliesenWodka@lemmy.world

Link to the original version of this thread to which OP is referring, which was quite a hit some time back:

https://lemmy.world/post/7371120

Up to par with your usual work, merde!

@mutilated_sphincter@lemmy.world:

Operating on the assumption that even merde may not want to touch this one, using realmixXL_v15:

Sure! I use ComfyUI locally. Replacing the underscore with a space under the assumption that this is the intended wording and using flux1-dev-fp8:

With stoiqNewrealityFLUXSD35_f1DAlphaTwo:

With realmixXL_v15:

considers

Fair enough; I can do one for you. I have a local ComfyUI setup, so prompt data won't go anywhere. Heck, even if I were generating it on a service, it'd be useless for letting said service gain information about you, as I don't know who or where you are.

For "over_clox", using stoiqNewrealityFLUXSD35_f1DAlphaTwo: