you’d make an entire new email address, and perchance account, and set that up in your browser so you can have both accounts open at once?
I might haven't good enough at describing it - basically I'll just stay logged out of Perchance entirely for that profile, and not creating an entirely new account, and I might also save the password and the generator link in my massive notes text file in case I lost it. In that case though, I think the private window could be a good alternative besides using a separate browser profile.
Are you planning on signing out every time you want to work on a version? And making a new version?
No, I would instead create a whole separate browser profile, so I don't have to log out every single time on my primary browser profile.
What I do while working on a new version is, I work on a private/unlisted copy of the generator.
Hmm... I could do that, however I've had a fear that the supposedly private generator would go out in the generators page immediately before I quickly set it to private, and that someone would be able to click the link through that page, so I thought creating a separate generator and saving it while not logging in would be a better option, since Perchance will un-list them right after, albeit still being publicly accessible. I know that this phenomenon is very unlikely to happen, but I'm just afraid that it would happen at all.
This is really cool! I've tried it now, and I think the saved generator is unlisted by default? If so, I could utilize this feature when working on my generator updates (especially my Generator Manager) so I don't have to dump the generator codes to a text file every time!
That "saved" interface reminds me of the times when the connection was not good that Perchance was only showing the "save" and "account" buttons, and the save button would still work just like normal.
Nice! How about nights? Create some night landscape pictures or something that just represents a night view.
I think the Perchance Dev makes the AI Character Generator. You can message them instead: @[email protected]
It seems like either the OP responded to my message, or they just figured it out by themselves.
I just made an image with a prompt of a combination of [100 random objects] and some of them has unusual containers for the popcorn or even non-food objects being put inside of that stack of popcorn. The prompt does contain the word bag of popcorn, just to mention.
Perchance already has a dedicated dark mode button for their t2i-based generators like ai-text-to-image-generator, so I think they could implement something like that into the main pages too.
Are you mentioning AI generators or all sorts of Perchance generators? Either way you should ping @[email protected] for stuff like this.
You can't assign variables in the middle of a list, instead you would move this part to the output assignment so it would actually create the variable that could be evaluated by the ..., r = recipies.selectOne, r.name] instance:
[f=createInstance(ingredients.flour.selectOne), createInstance(b=ingredients.flour.selectOne)]
Like this:
Why does this happen?
Perchance recognizes and evaluates the f variable assignment block I've mentioned before as the child of the list pie which is a child of the list recipies, making it unusable when called it directly within the variable's name. To fix this you'd need to execute that assignment before the recipies list is evaluated (as I've said before).
I was having too much fun while in a cycle of boredom and distress, and so I played with the DevTools Console in my advanced comments plugin demo once again and had some stock of https://perchance.org/ai-text-rewriter text to create this kind of stuff.
It's in the stories channel of the plugin demo, if you want to check it out.
This is yet another super weird bug I've discovered recently when creating a generator update. Tried on the generator first (while working on the update), but when I try on the Programmatic Get/Set/Submit Example, running the update() function into the testing panel seems to trigger this bug. I also got an error too, which writes as follows:
DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
at ___updateTemplatedNodes (https://210cadb7fe3ad106894dfb4649d8ce79.perchance.org/programmatic-get-set-submit-comments-plugin-example?__initWithDataFromParentWindow=1:470:30)
at update (https://210cadb7fe3ad106894dfb4649d8ce79.perchance.org/programmatic-get-set-submit-comments-plugin-example?__initWithDataFromParentWindow=1:412:5)
at eval (eval at <anonymous> (https://perchance.org/lib/perchance/evaluateSquareBlock.js?v=3ds06dgd27d:66:38), <anonymous>:1:12)
at Proxy.<anonymous> (https://perchance.org/lib/perchance/evaluateSquareBlock.js?v=3ds06dgd27d:66:38)
at __evaluateSquareBlock (https://perchance.org/lib/perchance/evaluateSquareBlock.js?v=3ds06dgd27d:66:77)
at __evaluateText (https://perchance.org/lib/perchance/createPerchanceTree.js?v=21ads3j533dgddldddfd337132fdwf3:1386:20)
at https://210cadb7fe3ad106894dfb4649d8ce79.perchance.org/programmatic-get-set-submit-comments-plugin-example?__initWithDataFromParentWindow=1:536:44
And that "nullifies" the com object which of course renders the comments section's programmatic submission ability to stop working:
So, if you've tried to implement the programmatic interaction features inside of the minimal template (or any generator that has a practical "randomize" button that executes the update() function), chances are you've probably already stumbled upon this bug.
https://mastodon.social/@BluePower/112613444964542682
Just a post about a bit of recap of how my generator manager has progressed through a very long waiting gap since the second big milestone... though the announcement WILL (hopefully) be up before June 15 or the upcoming days (if I have time, of course).
⚡⚡⚡
NB: the announcement will be all about "internal" changes; how I will make my daily job of exploring and managing generators here even more flexible, relaxed, and overall, a bit better of course. And also, there are a few exciting generator updates too, as usual, including the long-awaited 2.0.20.1 update.
Just recently, I've tried to add an option that disables loading all comments upon reload of the page (with the disableCommentsLoad option) but hasn't been quite possible yet ever since. Been stuck on this entire frame loading problem in my "under-construction" advanced comments plugin demo and it's been really hard to resolve as of right now. I also added a ?disableCommentsLoad=true URL parameter into the generator page so that it disables reloading all comments directly after page load.
It would also be great if that feature would actually be implemented into the comments plugin itself. Could be very handy to avoid situations like the "connection stalling" problem (see this post and the comment), and just to overall reduce unnecessary background connections, especially if you're on a browser that doesn't have a "memory saver" feature (essentially to "sleep" tabs like that to stop all the connections in the background).
But yeah, this time I wanted to make a post instead of troubleshooting the problem myself to see what solutions from other people could be (and especially for the known issues on the project). 🙂
Here's a demonstration from the thumbnail (with the disableCommentsLoad option enabled).
When I open my view counter experiment page to check around, I noticed a pretty surprising hit on one of the biggest official generators on all of Perchance. The ai-text-to-image-generator generator has passed 10 million views! Yup, millions, not thousands. That's far off from other official generators which have gotten around one to four million views.
And that's just a few moments ago, now it has already gotten over 50.0k additional views as of this post was created.
Screenshot in the thumbnail from The View Counter Experiment
I've been seeing more of this bizarre type of request whenever I look at the DevTools Network, with a strange request URL from https://perchance.org/cdn-cgi/rum. But whenever it stalls or not, it sometimes still lets me save the generator properly, and in some cases, it halts the saving and loading process almost indefinitely. But any good explanation is appreciated!
That is the details of the "pending" rum request:
After so many days of suspension due to so many activities outside the generator building stuff earlier this month, I'm finally back from that and now trying to get back to work on this very announcement thing. I know it might have been late now, but it's never been too late to do it.
Here's a quick artwork to represent what'll happen in the next couple days from when this post was created.
This is just a little bit of an encouragement post to me - but more is about to come this month!
If you were looking at The View Counter Experiment lately, you might have noticed that I've added a new "Random Stuff" tab in the right side, and there lies a "sentence-based" poem generator powered by the AI Text Plugin.
The poem was based on the sentence from the synthetic sentence generator:
We are sure glaringly thunderstorm introduce is enough.
The poem was cool enough that I wanted to post it here on the community.
Here's the poem just in case the image does not load
The sky's tumultuous fury, a symphony of sound, A thunderous boom, a flash of lightning's bound, The clouds, once white, now dark as night, We stand beneath and wonder, "Is this really right?"
As rain, once gentle, now comes down hard, The earth, once dry, now quivers and yields, The world around us, now drenched and wet, We feel the power of the storm, and yet,
We know that life must go on, despite, The tempests that may rage, both in and out, For in the midst of chaos, there's a spark, A hope that peace will come, that doubt will shrink.
I think the Perchance engine has its own way to handle variable declarations, since it's also having its own syntax for list coding, maybe that's why.