This would happen only in two ways, either the user ID is unique enough that when converted without being caught as a "bad" word in the process it turns into the ABCD visual tag, or after converted, the visual tag deemed to have bad words (or look exactly like a bad word), even after checking it more than one time, resulting in the tag falling back to the ABCD format.

I just deep dived into the comments plugin's user ID into visual ID converting algorithm behind the scenes, that's why I'm making a post related on this topic. Also, have you ever seen actual occurrences of tags like this happening on comments of generators? Share if you have one!

While updating an in-event generator for the ongoing Generator Manager Event, A Venture Poem Generator, I have tried to add the url-params-plugin to add a feature so users could disable glows on the poem for performance reasons. But when testing out the generator after saving, it doesn't work at all. Even when I test if that URL parameter exists at all, it still won't show the expected output. Whatever parameter I put into the URL, when I run [url.anyurlname], it outputs undefined instead.

I've done the same with my view counter experiment generator, and had the same issue. (Try visiting https://perchance.org/the-view-counter-experiment?name=Example, the greeting text above the tabs thing should output Hello, Example!)

This is more likely a bug with the plugin that for some reason fails to cache those URL parameters into the generator. When I try setting the url value to [Object.fromEntries([...new URL(window.location.href).searchParams.entries()])] in place of importing the plugin in that generator, that worked. And since I use two different browsers, both didn't work with the plugin imported.

cross-posted from: https://sh.itjust.works/post/21543982

> Hello and welcome to the first Generator Manager Event ever hosted! > > This is going to be a casual event that will be ongoing mostly during the times of my preparation for the huge 2.0.20.1 update, created in favor to increase the "spirit" and uprising interest in those kind of stuff to a point where I could finally be energetic enough to release the update, unlike the past few weeks where I planned the update much earlier and ended up getting delayed a lot due to massive business stuff struck around in real life. The big update turned out to be even more massive than I think would be because that's when I was aware that I wasn't going to release the update as planned and I'm going to have to set up lots and lots of things and re-wirings prior to the actual release of the update. > > As the name implies, it's about an adventure, so go make some adventure/space themed generators to be submitted into this event! > > Starts: 30 June 2024, 12:00:00 UTC > > Ends: 14 July 2024, 12:00:00 UTC > > ## Generator Rules: > - Make any adventure/space themed generators, as long as it's not explicit or adult content > - It's recommended to add some color in your generator! Maybe simply make the background colored, add some decorations or whatever you like to further glow up the generator. > - You can submit your generators to this community as well. Make sure to submit after the event started and before it ended. > > To add some spark into the preparation event, I want to mention a bit of thought I have left for the changelog of the big update: We'll be back regularly releasing some improvement updates to the generator hub page a few times every single month, and that'll happen right after we release this very exciting update! These follow-up updates will often star some massive improvements and rollouts of features planned to be in the 2.0.20.1 update that wasn't in the update afterwards, including the long-awaited dark mode and the re-aligned Home page, in the follow-up Generator Manager updates after that! So, don't miss the mark out if you're waiting for those really cool updates! (And the Event page will get a kind of an overhaul, too, for an even richer experience.) > > Happy creating and stay together for the event! 🚀 > > --- > > See the Generator Manager Events here

So I just decided to move to Firefox for the updating and managing generators stuff personally (although I might still use Edge for testing stuff) to further minimize the connection-stalling problem from happening ever again, and so I've been wondering if it's possible to move the admin login data (basically a list of generators that I just logged into admin on) and the notifications data (a list of generators and keywords I've listened to comment notifications from) into a different browser, just like importing browser data, in some ways? I want to keep things synced between two browsers and thinking of this for a while now.

I do have tried a few things such as transferring the localStorage of the comments-plugin.perchance.org (the central domain of Perchance comments plugin), and even also tried to transfer some of the cookies, and both didn't work well.

Just made a decorative plugin that adds a cool rainy effect (or ANY kind of rain effect) into a generator. Released after the 20.0k views special announcement, and soon before the staggering Generator Manager 2.0.20.1 update ultimately goes out...

There are all kinds of rains you can make from this plugin, such as:

• Lava rain
• Acid rain
• Copper rain
• Metal rain
• Ocean rain
• Golden rain

... and the list goes on. Just be creative with it.

Let it rain! 🌧️☔

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:

text 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.

Yeah, the special announcement has finally been released, this time I decided to put it into the Announcements section of the Generator Manager instead of creating a whole new generator page unlike the previous two big announcements. Asides from the usual generator updates, the announcement will also be filled with some "internal" updates for adjustments with my current workflow to make my daily job on updating and managing generators even easier to manage and more flexible in the future (hopefully).

Go check out to see what's to be expected! And to not forget, there'll still be some new projects and stuff (such as new generators and plugins) as usual.

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:

!

I've just found another pretty cool way to get rid of the error box in a generator without using the __clearPerchanceErrors() function that you can run on the testing panel to get a similar effect (as mentioned by @perchance@lemmy.world that it's probably a "private function" as well along with other alike properties in the Perchance engine), and so I made another quick example on how you can do that.

The difference is that the error box only gets "hidden" while you can still review the errors by running [__showPerchanceErrorBox(), ""] in the testing panel, whilst all the errors get removed completely with the __clearPerchanceErrors() method.

I've also showcased how you can show the error box even when there aren't any errors in the generator whatsoever.

Note to everyone who used my Power Tabs Plugin before, if you ever had so many tabs on your tabs plugin and having an overlapping text issue on the plugin like this:

!

I've recently mitigated about the issue, and well, there's now a very handy solution to this! You can use some HTML styling, by setting a fixed width across all the tabs like this:

<style> ._powerTabs td { width: 150px; } </style>

This will make all the tabs in your generator adjust its width beyond its technical limits, and thus will make the top part scrollable if those tab heads' widths occupy more than the entire width of the tab container.

Some notes:

• You can just put the HTML snippet above anywhere in the HTML panel or put the innerHTML of it into your already existing style element if you have one.
• You can see the fix in action in this example I just made.
• This fix will apply to all the tab containers in your generator if you have more than one of them, like on this example. If you want the fix to apply only on certain tabs, you'd need to wrap the [tab(...)] thing that outputs the tabs plugin into a div or a p element like this: <p class="myTab">[tabs(...)]</p> and then give a class on it, and then you can insert a different HTML styling like this: <style> .myTab ._powerTabs td { width: 150px; } </style>
• If you want to set the tab to be wider, you can change the width to a larger number like 200px, 225px, 250px, and so on.

I've just updated the plugin with a small addition of adding a special class to the outer layer of the tab container, so you'll be able to do this fix by yourself and, in addition, do some advanced CSS styling on the plugin (which you'll be able to do through the lists soon!)

---

Additional info worth to mention: If you have the wordwrap option set to wrap in your tabs, the tab heads will adjust to the minimum width needed to fit on to the titles, but not adjusting to its fixed width. If that fix doesn't work, try replacing the width part after ._powerTabs td { with min-width so the tab heads will explicitly adjust to their minimum width.

You can actually apply the wordwrap = wrap behavior only for the tab content without affecting the tab heads so the fix above will still work: ._powerTabs > div > div { word-wrap: break-word; }

I've been enabling/disabling the auto-reload pretty frequently now for many reasons and doing that with a move of the mouse sometimes annoys me when I had to move my cursor away from the left side of my screen. Will there be a dedicated keyboard shortcut for that rather than having to click on the checkbox in the editor every time?

I have just made this quick fork of the sentence generator from the useful generators page and released it as a new Small Generator on my Generator Manager. And on this I've added a mechanism that replaces certain words on the generated sentence with a different one pulled from a bunch of other useful generators (i.e. you might get the same sentence structure set at the end but with different words instead of getting the same sentence with the same set of words sometimes). This often creates sentences that look nonsense to some people, though, such as Title in the corner to find the uneven shirt.

This might not be the only generator I'll make before this month ends. 🙂 Though let me know if new sets of sentences have been added to the original generator so I can add them to this generator.

Not mentioned: There was a typo I found in line 502 of the original generator, but I've corrected it on this remix of the generator.

So, after a bit of testing with the example from the super-fetch-plugin, I've tried different kinds of websites and it worked, including a URL from comments-plugin.perchance.org, which I got from inspecting a comments plugin iframe from the DevTools. But in this case, not from user-uploads.perchance.org, it kept having the same CORS issues just like the ordinary fetch function. Specifically I wanted to get a text content from a file mentioned in the huge-emoji-list pack.

I think it's a very neat concept when we could "superfetch" a content uploaded from https://perchance.org/upload right from any generator, but at least, that's I'm getting for now.

I've found today that search engines not only index generators by their descriptions, but also the contents of the page and sometimes the source code of the generator to make them somewhat easier to find on the search page. (I'm also speculating that this might be the cause my generator manager performed much faster than it did 5 months ago when I returned due to so much influence on the content that I put onto it even though I don't have so many descriptive keywords in the description.)

!

!

When searching for "smartwatch perchance", my Chat in the Smartwatch generator comes at the first place, but interestingly, my generator hub page also comes at 11th-12th place (amongst other sites). So, the meta description might not be the only way to make your generator more findable and indexable (unless you have very little content in your generator/source to feed to). The generator hub page that was shown also links to the Templates page (?page=templates) and not heading up to my home page.

!

I've also tried to search for "the coolest generator hub on perchance", and my generator hub collection page came up at 3rd place, while the Generator Manager comes at 4th and 5th place (for the ?page=last and ?page=templates links that both got indexed for some bizarre reason).

!

!

I've made another example where you can make a comments section from a generator with the comments plugin to properly "grab" comments from another generator besides yours (e.g., comments from generators on my power-generator-manager), even ones that don't even have the comments-plugin built into it, without without using any direct iframe linking to the generator, that is all using just a simple execution of square-bracket-enclosed code in HTML (or lists). In the example page, you can even choose the generator source and the channel you want to load the comments from. And yes, the users would also be able to comment from the example generator, and the comments would be stored on the generator page the comments was taken from (so it'll also display on the same page).

I've also found the same technique long time ago, but using a different technique, and I've actually been using it in one of my abandoned generators, Comments Customizer (which now doesn't work anymore due to new default URL structure which the generator doesn't support).

Not to mention, if you have multiple comments section in your generator, all those comments will get replaced by the comments from the same generator you've set to grab them from. Also, the options from the generator the comments were taken from will not reflect to the comments from the generator, such as bannedUsers and adminPasswordHash, so you'll be able to see the banned users and see admin comments that are not flagged as "admin".

Is there a way to make the plugin accept a direct input of a text instead of putting it into a separate list and then reference the plugin for it? Or if not, could there be a possibility for it? So, when e.g. when I want to format just a few pieces of text, we'd just write this:

[markdown(`**Hi!**`)]

instead of this:

[markdown(hi)]

hi **Hi!**

I've recently been motivated to work on this little project that I've been working for about a day in total. But my fears for the bad comments to be thrown over the experiment generator again and considering of some complexities to move it there have decided me to not put it up on that generator page and keeping it on this generator page.

This is an early implementation of what could I say as an improved, more "advanced" version of the original comments plugin, with these features outside of the original comments plugin that utilizes the onComment/onLoad features and a bit of the programmatic submission feature:

• A re-made set of Markdown formatting syntaxes, so you could format comments (lists, quotes and code blocks aren't supported currently, but you can highlight, glow, or change font size of any text!)
• Default nicknames set with generated arbitrary words based on tags
• Notification sounds
• URL blocking
• And many more

And I also want to mention these:

• Upcoming support for reposting, liking, replying, and saving on comments(!) using hundreds of comment containers (aka "servers") to store these

Asides, you can also select from a set of generator names as a source outside of the generator page (so the comments from there will be linked to this, and you'll be able to comment from that generator right on this page), and you can also add new generator names (of course, there'll be some blocked names like generators to avoid some flooding and stuff like that).

I've also kept some of the Dev's notes from the onComment/onLoad example, just because I forked this little teaser from that.

Some known issues:

• The "No comments yet" placeholder does not show up when the frame gets reloaded with a new generator source/channel selection
• Since the comments formatting uses a remake version of the Markdown formatting parser I made myself (with some regexes taken from different online sources), there are still missing token on formats (e.g., lists, quotes, etc.)
• When inputting some text into the "fake" input section (the upper one), it seems like it doesn't put the text into the actual input area straight away from the upper one. And when you logged into admin, the input text doesn't (just because there's not any variable that determines whether user is logged in as admin or not yet).

I don't know what else can I say about the project, but if anyone wants to contribute into describing it much further, or maybe suggest new features, please let me know! 😊

Sometimes when I save generators while it was still unfinished or, in a case, it's still under development, I'd like to add a note into any of these generators that it's unfinished on under development while I can keep them private for a long time. Or you could write anything you want as a note to any generator in the menu.