wthit56

joined 1 year ago
[–] wthit56@lemmy.world 1 points 2 days ago (1 children)

I'm confused... you've literally put your own nsfw notice on the page. Why did you do that if there's no chance of nsfw content on the page?

Something to bear in mind is that any image generator page can generate and display nsfw images.

I don't know about the stuff in that other comment though.

[–] wthit56@lemmy.world 1 points 2 days ago (1 children)

You can block users from bring shown in the gallery.

https://perchance.org/text-to-image-plugin has the options documented. Look for the "Gallery Moderation" heading.

[–] wthit56@lemmy.world 1 points 2 days ago

They're part of the gallery mode of the AI image generator.

[–] wthit56@lemmy.world 1 points 2 days ago

Well done on making something more involved and complex 👍

What does "Fegless" mean?

I don't understand asking for a donation because you're down to 512mb of data... how is that related to the generator? What data are you talking about? Why do you want people's email addresses?

Clicking "AI?" just generates whatever the AI feels like. For me it generates some python code for no apparent reason. I'm not sure what that button is meant to be doing, but presumably it's not doing it.

And clicking "AI prompt" puts both the prompt to the text AI and what it returns (the actual image prompt it produces). Which also is presumably not what was intended.

"Import" puts a random actual image prompt in, and doesn't actually "import" anything as far as the user is concerned.

The part of the prompts your page adds have a formatting that doesn't actually help the image generator, but could certainly confuse it. It's written as plain english, with little headings and such, but that's not how image generators use the text. It may have better results if you wrote those prompts in a more image-generator-ish way.

Clicking "random" in the picture settings doesn't change the settings to random things. It just starts a new generation that ignores the prompt entirely, which is unexpected. I don't know what this button is meant to do.

When I go to the page I see an error: "Failed to fetch."

Would be good to have "Random" be an option for picture style/lighting.

Would also be more useful if a randomised setting was picked at random for each generated image, rather than once and then applied to all generations in that set. So that if you generated 4 images with a random location, you'd see 4 random locations for example.

Character background: false, Character personality: false. I don't understand what these mean.

[–] wthit56@lemmy.world 1 points 2 days ago

Fix what? What is the problem?

[–] wthit56@lemmy.world 1 points 6 months ago

Yeah if you're setting it in the prompt, that overrides whatever other settings there are.

[–] wthit56@lemmy.world 1 points 6 months ago (1 children)

Your post is not formatted how you wanted it to be. Maybe use a code block around your code so we can read it easier.

[–] wthit56@lemmy.world 1 points 6 months ago (1 children)

Yeah just export it, download that file, and load it on your other device. When you "share" the file is put on the server and anyone with the link can import/see that file, basically. So it'll be more private to just download the file and use it yourself.

[–] wthit56@lemmy.world 1 points 6 months ago

Try using "character turnaround" or other similar terms for that kind of layout.

I just tried using this prompt, and got stuff that look something like what you're after: head to toe character design, character turnaround, front back side plain background BREAK background grey

So don't think that you are describing an image, it is imagining an image based on your description, and then drawing that image. That's not what is going on at all.

AI isn't being dumb or obstinate. AI is not thinking. It has no brain. It has seen lots of images, with text associated with them. It's compared them and noticed patterns associated with a particular term. When you put terms into the prompt, it is lining up those patterns and using them to form an image. AI is not smart, it is not feeling cooperative or unhelpful. So thinking of it in that way is not useful. It actually is dumb.

It's job, in its dumb way, is to trick people into thinking it's an image made by a real person. That's all.

[–] wthit56@lemmy.world 1 points 6 months ago (3 children)

No, generators usually only store things locally, unless you click a button to "share" it or things like that.

[–] wthit56@lemmy.world 1 points 6 months ago

I'm not sure what you're referring to. I've never seen code just be added without my typing it or asking it to write it.

[–] wthit56@lemmy.world 1 points 6 months ago

Sounds like just a plain ol' AI chatbot would be fine for that. As opposed to a preprogrammed thing that has pre-set aspects of the world it will generate. I do have a simple AI chatbot page you could try using: https://perchance.org/quick-chat

(It doesn't save your chats, but does have an export feature explained before you start chatting.)

1
submitted 6 months ago* (last edited 6 months ago) by wthit56@lemmy.world to c/perchance@lemmy.world
 

https://perchance.org/46iutpmh9i#edit

The examples in the above generator page demonstrate the issue.

If in the HTML there's an onclick that updates itself and calls stopPropagation, it will update itself and stop propagation.

It seems if the HTML of the element in question was generated and injected by a [square block], then stopPropagation prevents the update from happening somehow?

...Actually, perhaps no updates work at all, if generated from a square block?! Wait, is this actually to do with the idea that it wasn't in the HTML from the start, so it doesn't think there was anything in that element to update?

 

Currently, as far as I've figured out, in the HTML we can have {import:...} and it will be accessed. So we can use that to actually run code immediately. Using it this way means it won't be included in the lists for when it's imported into other generators, but we can still use it in that specific page.

But we can't use {import:...}.property or {import:...}(args).

In the lists, we can have imported={import:...} and it will load in but not be accessed. To trigger the access, we have to use [imported] someplace that is accessed--in the HTML, or perhaps $output depending on the situation, something like that. Which is counter-intuitive, as the code we're writing to import it in the first place is literally an assignment (by how it looks at least).

But if it's in the list at all, it's now part of the dependencies included when importing it into another generator. Which, if we're only importing it into the list to be able to call in the HTML, is not explicitly intended by the creator. As this kind of assignment doesn't actually access the imported thing, at least it's not going to actively do anything. But ideally it just would not be required.

On the other hand, it would be useful to be able to simply say {import:...} and have it import, even without a name to store it under. It's clear what the creator wants, from that code. And it works exactly as expected in the HTML panel. On the other-other hand there's no way to call an imported function or access an imported property from just the HTML so it needs to be part of the dependencies of the plugin itself.

If my plugins were actually used by anyone (LOL) this would have been a pretty big issue when I recently made a typo (and got stuck being unable to fix it for a time) in a not-required-at-all import that had to be there purely for the plugin's page to use.

If I could've just imported it and used it all within the HTML panel, it wouldn't have been so urgent, because the error would not have affected any users of the plugin--only my own page presenting it.

The main thing here is, they work differently--seemingly (from the outside from an average creator's point of view) for no real reason. So learning how import works correctly is made more difficult. And learning how it works just for lists or just for HTML is easy... but of course trying to use that knowledge in the other panel leads to confusion and frustration because actually there are different unforeseeable rules there.

Could well be that for backwards-compatibility some of this could not be changed. But perhaps things could be expanded to allow for more features to be cross-compatible, and more expected/very common features to "just work."

view more: next ›