BluePower

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.

Maybe a new plugin, a new stuff (like the Hub) or just some other features added into already-made stuff that was just introduced in Perchance after you joined the community and made a few generators. Mine was the Select Until Plugin, introduced around April 2022 when the comments plugin still looks pretty basic and has minimal functionality.

Bonus stuff: Speaking of the comments plugin, I've found a very early copy of the plugin that was made on July 2nd, 2020(!), in which the comments there are broken, and also there wasn't any documentation on how to apply custom fonts into comment sections.

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.

Yeah, I've just got one of the most impressive moments once again, after manually updating the data on the Generator Statistics spreadsheet. One of my generators just reached the barrier of 1.0k views gained in a week amongst all of the generators I've been made.

And now, I've got a thought. Seems like updating it to get it on the flag generator don't have any sort of effect at all, maybe the influence on that many views gained is from the descriptive keywords, or the amount of interesting-ness the generator has, or something like that. But will this apply on my Generator Manager too, considering it only grew up to 750 to 800 views per week?

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

One of the most popular (if not the most popular) generator hub pages ever created and discovered, cat-generators, has just reached the 80.0k views milestone, coincidentally noticing this when just visited my generator hub collection page. Hasn't it been so long ago since it was on the 70k marathon?

(Change the sort by option to Most viewed!)

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.

There was one missing functionality in the Date Plugin, which is an ability to get relative times which you can do by passing the parameters into the function in the Moment.js library. But it looks like you can't do that in the plugin itself, which is simply a part of writing mistake in the plugin's source.

I see in the source you can actually pass some arguments into the plugin, and it should iterate those arguments into the moment() function instead like this:

  if(!window._alreadyLoadedDatePluginCode8934792) {
    loadPluginCode();
    window._alreadyLoadedDatePluginCode8934792 = true;
  }
  return moment(...args);

So now, getting relative times directly from the date plugin should work, just like what you would in the original Moment.js library. And there should also be a documentation somewhere in the plugin page.

Update on the issue (and the solution)

It seems like a possible solution (at least to me) is to probably avoid having a generator tab open with so many comment frames at once, as they're constantly filling up the whole TCP connection with requests for listening for new comments every time, which is what's causing the "stalled" problem every time I load and save generators.

See this comment for a reference.

Update 1: Now I've just sort of reproduced this by opening the Comments Plugin tab while one of my generators is saving, and then after the tab is being open and then closed, the saving process just stalled out of nowhere.

Recently I was hit by the problem where the saving process just stuck in the background, and when I checked the DevTools Network, there's a lot of stalled connections when fetching a few resources required for the generator page to fully load. The stall eventually ends for a short time (1-30 min), but sometimes even longer (30-60 minutes), and even after that, it's either still hangs on "saving" whatsoever, or it rolls back to the perviously "unsaved" state.

I also got the problem with loading generators too, where it hangs very frequently now, for the same reason, except that I sometimes get an ERR_QUIC_PROTOCOL_ERROR from the console whenever the generator fails to load after the stalled connections.

Is this maybe just because of the internet connection, my browser, or probably the "cache-busting" issue in the end? I tried logging into my other browser (Firefox) and saving the same generator and found no issues. It also loads generators perfectly fine.