Yep, these are a click-bait generators, seemingly a fishing site. According to WhoIs it points to a Czechia located site.
You need to block "https://loginrubbishobey.com/" in your browser security settings to prevent the generator from going there. Or even better, block it in your PC "hosts" file (On Windows usually located in folder "C:\Windows\System32\drivers\etc").
For that you will need to add this line in "hosts" file: 127.0.0.1 loginrubbishobey.com
The file is 'read-only' (by default anyway, this is to prevent inadvertent/illicit modifications) so it's a bit of a hassle when you're not familiar with OS and folder manipulation.
And make sure to prevent/block the site from creating cookies in your browser security.
You should post the prompt/negative and settings you are using and a link to the specific generator. There are way too many Perchance generators to be able to tell what might be off.
Prompt "a person wading waist-deep in the river" did it for me. No-Style, no negative.
The keyword BREAK, parenthesis () colon : semi-colon ; and dot . go a long way. While parenthesis are used for emphasis and weight, you can also use them to bundle parts of prompts. Colon to start a list, semi-colon to terminate. Won't always work as expected, but who doesn't like to fiddle.
Use BREAK to signal a new 'layer' in your image, essentially defining a new image within the image.
E.g. using art style 'casual photo' or 'professional photo' with prompt professional portrait of a female in a colorful dress BREAK a psychedelic black and white background will yield exactly that.
Below prompt, with 'professional photo' worked for me, consistently (okay, fairly), also with more than 1 image in one run:
professional full body photo of three slender lithe females BREAK one girl is a Caucasian redhead, casual wear BREAK one girl is African in a red dress, barefoot BREAK one girl is Japanse with white hair and big boots BREAK a psychedelic black and white background
The same run, 3 images:
As you can see, you will still need to be very specific between BREAKs to prevent spilling, but I think you will get the gist...
Should you wonder: the IP address 127.0.0.1 redirects to your own device. Essentially you are saying to your device "when you're instructed to go to 'loginrubbishobey.com', just go back to my device". Using IP address 0.0.0.0 will have the same effect. You can add any number of unwanted sites to the list this way.
remember = true is not related to the remember-plugin but part of t2i-framework-plugin-v2.
Basically both plugins save the value of a select to localStorage when activated and it can happen that one of the plugins has updated localStorage while the other hasn't (just yet). Especially when you close a generator before image/text generation has finished localStorage can (or may) contain two different values of the same select causing your issue. Depending on how you created the generator AND the order values get retrieved from localStorage it may SEEM that your generator suffers from dementia.
You can (probably) resolve this by using either one, just not both 'remember' methods. I am still on the learning track, so don't ask me how to solve your specific problem. I need to figure out a lot more before ever being any use in that respect...
Off the bat I'd say don't use remember = true when you're using the remember-plugin.
Love your work!! I'm not sure I will listen much, but, as a retired software engineer, dang, I'd say: impressive!
I've been looking at the code and the link to the Meta Template in The Meta-Template Concept is dead.
Don't worry, I'm well aware (from reading prior posts) that you are using AI to create your work. The output you've created thus far (made AI create, duh), tells me that you are very good at specifying and describing a problem in such way that others (or the AI) can create code from (nearly?) scratch. That ability is much more valuable than decades of coding experience based on specs others supply.
Let's face it: if you can't properly describe a problem, how will you ever be able to come up with the right solution? And mind you, the world is full of know-it-alls who come up with solutions for the wrong problems. And it costs billions, each year.
So, kudos!
Having said that (of course there's more), one obvious flaw I noticed in the [GEN] PODCASTS app is the use of fixed units (px) in the CSS instead of relative units (rem, em, etc). With responsive design that's a no-go. You will need to do some tweaking there. Some guidance on the subject is too much for this post, but you can DM me should you require some insight. I haven't checked your other apps, but since you are using a template, I guess(!) they all have the same issue...
Yah, me too, and it will probably rid the 'recently added/updated generators' list from a lot of straightforward 'I wonder what the [save] button does' copies.
I picked a random text2image generator from the generator list
Art Style: No Style
No Negative, Guidance Scale 7
With the prompts you really need to be aware that an x year old woman can yield quite older looking females than an x year young woman. The same can be said of woman vs. girl vs. female. Depending on the run the differences can be quite distinct.
And A professional casual photo... vs. A casual photo... will definitely yield different results. The same goes for professional casual and casual professional.
...old woman
Prompt: A casual photo of a genuine {23|24|25|26|27}-year old woman, she has an {aquiline|up-turned|celestial|button} nose, and is of {German|Dutch|Belgian|French|Welsh} ancestry.
...young woman
Prompt: A casual photo of a genuine {23|24|25|26|27}-year young woman, she has an {aquiline|up-turned|celestial|button} nose, and is of {German|Dutch|Belgian|French|Welsh} ancestry.
...young female
Prompt: A casual photo of a genuine {23|24|25|26|27}-year young female, she has an {aquiline|up-turned|celestial|button} nose, and is of {German|Dutch|Belgian|French|Welsh} ancestry.
Depending on the age of a person you require, some obvious choices:
newborn, baby, toddler, x-th grader, middle/high-schooler, (pre) adolescent, teen(ager), tween, x-something, middle-aged, elderly, ancient, etc., optionally combined with early/late (though 'late ancient' must be minutes before death).
x aged girl/woman/female, be careful though, as 'aged' also means 'grown old'.
use old/young only if you're out of options (or just don't care).
don't mix human speech/slang/street-talk with proper grammar/spelling.
assume AI is stupid, just an algo traversing statistics and weight values.
Yah, the perks of the English language disambiguity will require you to be quite specific in your prompts. Using a dash (-) between words worked for SD, but Flux can be quite quirky (using the '-' as a negatory?).
Additionally, the t2i-framework-plugin-v2 [brain] button (, which uses the ai-text-plugin) does wonders for none-native English people like me.
FYI: use 'guy' for male versions as 'man' usually yields a hairy body builder with a 'wishful-thinking' reproductive organ.
Thanks for the input, but this is a Javascript coding issue inside the plugin(s), not directly related to Perchance syntax for creating generator lists.
I'm using either Chrome or Firefox on Windows PC, straightforward, no VPN/Sandbox, or any other tool (maybe stupid Windows notepad to save snippets). Both browsers ran into the same issue, however, in the version I just tested, the chat responses seem to work now. FYI, I've never heard of either Thorium or Brave browser. I use Chrome, Edge, Firefox and for very old stuff Palemoon, on occasion Vivaldi (which is Chromium). So, no Linux.
Regarding 'what is $root?', it is a global variable inside Perchance, just like $meta. As you can see, Perchance AI-text-plugin understood perfectly what I meant. This is what your AI helper has to say about it (and I have no better explanation myself):
Hello! In the context of Perchance.org, $root is a special variable that represents the root scope of your Perchance script. The root scope is the global context in which all of your code runs, and it's where you define the core settings, functions, and data structures that are accessible throughout your script. Here's a simple example of how you might use $root to define a global variable: javascript // Define a global variable using $root $root.myGlobalVariable = "Hello, Perchance!"; // Now you can access this variable anywhere in your script console.log($root.myGlobalVariable); // Outputs: Hello, Perchance! When you create functions or objects that you want to be available globally, you can assign them to properties of $root. This way, you can avoid conflicts with other variables and ensure they are easily accessible from any part of your script. javascript // Define a global function $root.myGlobalFunction = function() { console.log("This is a global function!"); }; // Call the global function from anywhere in your script myGlobalFunction(); // Outputs: This is a global function! In Perchance, $root is also used to define custom functions and settings that are available in the story editor's interface. For example, you might define a function to manipulate story elements or set up a custom configuration for your story: javascript // Define a custom function that's available in the story editor $root.myCustomFunction = function(args) { // Your custom logic here }; // Use the custom function in the story editor { "type": "choice", "text": "What's your favorite color?", "choices": [ { "text": "Red", "value": "red" }, { "text": "Green", "value": "green" }, { "text": "Blue", "value": "blue" } ], "onChoose": [ { "name": "myCustomFunction", "args": ["green"] } ] } In this code snippet, myCustomFunction is a custom function defined on $root. When the user makes a choice in the story editor, the onChoose event triggers, and the specified name function is called with the provided args. The custom function can then perform an action based on the choice made. Remember, while $root is powerful, it's important to use it judiciously to avoid cluttering the global namespace and potentially causing conflicts with other code. Keep your global declarations to a minimum and use them only when necessary.
However, the chat-reply shows the three back-ticks of the MD code, not a marked down snippet like here in Lemmy. What's your intention with the markup of the code snippets? Show the code examples properly marked down or have the user copy the code and paste it to get a better view? It's not clear to me, something like the below is not really workable, esp. on smartphones (which I personally don't use to code):
A 'regular Perchance user' (none-programmer, that is) has no clue that they are about to use a 'bare-bones' generator when reading the below intro-message, heck as a developer I didn't:
Maybe adjust that with a better explanation, not everyone will enter edit-mode to check out the code (initially I didn't either, not until you suggested it in your comment).
Closing, I am not sure what this is about, the error occurs when the chat-reply finishes:
I went to your site (PC Firefox, Windows, 1920x1200, not logged in, advert bar at the bottom. PC Chrome logged in, no advert bar) and entered 'what is $root?' in the chat-input.
It starts to come up with an explanation, but when the output field fills the chat-messages, it removes the explanation and displays 'Sorry, I encountered an error. Please try again.', seemingly when finalizing the explanation. I tried it 3 times with 3 times the same result in both browsers.
Tried 'what is $meta?', same result.
Dito with 'what are nested lists?'
Furthermore:
The markdown of the code/chat output does not work, making code examples quite hard to read.
Are you using a timer outputting the text? It is really slow at posting the the text character by character. On average people do read a lot faster than that.
Love the idea, so don't get discouraged, as I think something like this will be a great help!!
The parentheses can be used to add more weight to a (piece) of a prompt. Given that no parentheses is a weight of 1, then a single () is 1.1 * 1 weight, (()) is 1.1 * 1.1 * 1 weight and so on. Or they can be used like: (some really important piece of prompt):1.21, adding a certain weight directly. Don't overdo the decimal, something between 1.1 and 1.7 will usually do the trick.
The colon : is often used like a sum-up, e.g. the female is wearing: ..., ..., ... and ... ending with a dot or a semi-colon.
The semi-colon ; is used to split part of a scene like they are dancing; optimal lighting, low camera angle; leisure time concept.
Perchance only offers TEXT-to-image generation up to now. This automatically entails that any user created generator offering IMG-to-image utillizes external (to perchance) servers to create supposed images.
But, why not post links to the generators you have been trying so we can check what might be going wrong? What image(s) you use as input and the prompts you enter.
From Perchance's perspective you are doing nothing wrong, the generators you are using are apparently unable to live up to their promis or make clear to you what input they need to generate img-to-img...
Yeah, well, being opinionated does not equal being right. I suggest you visit this site for a bit of peace of mind. When in doubt this site, they don't care about money at all.
While at it, why not show off a few of your magnificent intellectually high-quality results of software development you surely must have readily available.
@[email protected] please, don't even open that door an inch, as personally I could not give a rat's ass for the intel.
That was the old SD engine. The currently used Flux engine does not produce any kind of celebs (yet anyway, with a few exceptions like Trump, Putin and Hillary Clinton, etc). Any resemblance to existing people is pure chance.
