Update again: There are some cases where the generator stalls at loading for an even longer time, from 40 minutes to almost an hour. The initial page load wasn’t stalled, only the generator load after the perchance framework was loaded.
As shown in the screenshot below, I only left one other Perchance generator instance open and active during this period of time.
Yeah, in this case, only the author of the generator can change and moderate anything I think (same with any other AI image generators in Perchance), even if we offer to add the admin account by yourself, unless if you remix the generator so that you can moderate the comments by yourself (i.e. create a “safe” version of the generator with moderated comments of your own).
Okay, I now understand there’s now a clear documented window.ignorePerchanceErrors and clearPerchanceErrors() function in the advanced generator, the last time I took a look at the page, it wasn’t there (here’s a snapshot of the page from 2022). Overall, the alternative method only hides the error box out of the generator and does not clear the errors, whilst it does with clearPerchanceErrors() so you cannot see them when you programatically open the error dialog (as in the example).
Okay, so I got some more reports today. I woke up and opened my browser with a tab heading to the Comments Plugin page, with all the comments sections already loaded up. Then, I opened my Generator Manager, and it loaded just as usual, but when I saved it, it took a really long time, up to around 30 minutes, with usual long-stalling requests initiated by the /api/cv request. It even spit out a Couldn’t get generator dependencies error midway. I left only the Comments Plugin tab and the Generator Manager tab open for the rest of the time in the same browser while doing some outside work.
After trying to save it again after a couple of minutes though, it did save pretty well.
Update: Now, almost every time I opened and saved my Generator Manager, the other generators I’ve opened seems to start loading for a very long time, while the saving requests from the generator hub page also clogs out of nowhere. It’s in the 30-minute mark again.
@perchance Just saw a typo in the sentence generator! Also, if the generator has somehow been updated with new sentences or so, please let me know so I can add them into my generator.
Ideally I’d replace the letters with a dingbat font or something so there’s more visual distinction between the tags.
I’ve also had a similar kind of idea by having an auto-generated nickname based on the user’s tag in my advanced comments plugin demo. For example: B134 becomes BtereHariman34 (though the tag-to-nickname system is still in underlying development, and I might change the names on the database so it looks less like nonsense to read on)
I remember this one using only the localStorage thing and I think I’m actually using this in some of my generators. After trying this a bit, I found a benefit from using this method, that the data will stay in the input even if the generator is reloaded through the auto-reload feature when editing the generator’s code.
Using the remember plugin, in normal circumstances, that would reset the value when it’s auto-reloading. And I’d also like this kind of behavior to be implemented right into the plugin so that remembered variables (and not just the user inputs) can retain its value even when auto-reloading generators.
No, that’d be impractical, unless the server is stored somewhere on space and there was a technology that makes the server accessible from the ground, without any sort of latency or slow connection. But I guess the reason is that the perchance upload server would be guaranteed to be maintained forever so it’s very, very unlikely that a file would randomly disappear from the server.
Some suggestion before I go to nighttime - is there a way to remove entries completely through leaderboard.remove()? The reason why is because the leaderboards in my Complete the Number Blocktrains game gets “wiped out” gradually every time an entry gets added in the “core engine” of the leaderboard when someone completes a round, and to remedy that issue, I instead want the previous entry to be then replaced with the new one with the new score from the same player. Also, each entry should have its unique ID so you know which ones have to be removed (can be through an index too).
The suggestion applies to the Leaderboard v1 plugin which I use for the game (and v2 as well if you want to).