Cocell

joined 2 years ago
[–] Cocell@lemmy.world 1 points 3 months ago

This is not a place of promotion. Take it elsewhere.

[–] Cocell@lemmy.world 1 points 3 months ago

So, I decided to to look into Perchance's internal code myself, since I couldn't get an answer.

A screenshot that shows Perchance's internal scripts using the __generatorLastEditTime parameter and __initWithDataFromParentWindow parameter along with some other logic.

And it looks like Both the __generatorLastEditTime parameter and the __initWithDataFromParentWindow parameter are needed ONLY during the initial load.

And looking at this part of the code, it seems like Perchance dev is already moving away from the __generatorLastEditTime parameter.

// if(window.location.href.includes("__generatorLastEditTime=")) return;

So, I am assuming it is fine to remove these two parameters after the app has loaded. However, I could be wrong, these are just my general understanding after looking into the internal logic.

[–] Cocell@lemmy.world 1 points 3 months ago

The exact type of bug is undisclosed.

Also they could be inactive, could be busy, could be working. You never know.

[–] Cocell@lemmy.world 1 points 3 months ago (2 children)

When the bug is fixed. 👍

 

The parameter I am talking about specifically is the __generatorLastEditTime parameter.

This is a visual example:

The URL: https://perchance.org/vue-router?__generatorLastEditTime=1752040569107#/

Is there any problem in removing it?

I was using Vue Router with its createWebHashHistory() API to make hash routes for an application, since Perchance doesn't support actual routes for apps.

I made a simple logic to simply remove it.

const url = new URL(location.href)
url.searchParams.delete('__generatorLastEditTime')
history.replaceState(null, '', url)

Now you get a cleaner URL instead.

The URL: https://perchance.org/vue-router#/about

You can check out the project here.

[–] Cocell@lemmy.world 3 points 3 months ago

I once forked Blank as Blank Private, if this suggestion isn't implemented, Blank Private could stop the annoyance of having to set the generator to private.

[–] Cocell@lemmy.world 1 points 3 months ago

Perchance dev, I can confirm. It collects user data and sends it to a Firebase app.

[–] Cocell@lemmy.world 1 points 3 months ago

No wonder the quality of the images changed.

[–] Cocell@lemmy.world 0 points 3 months ago* (last edited 3 months ago) (3 children)

WE NOW USE FLUX? When did that happen?

Hm, it says SD.

 

Is it possible to import plugins with normal JavaScript from the HTML panel?

 

Perchance Dev, does Perchance have any issues against using Puppeteer or Playwright to set codes from GitHub automatically?

 

VioneT, can we use service workers in Perchance?

 

Dear Perchance Dev, I have created a private generator to house the list of people banned from another one of my generators. However, upon opening it, I saw this:

Why is a private generator flagged with NSFW?

The link is this if you want to look into it.

1
submitted 8 months ago* (last edited 8 months ago) by Cocell@lemmy.world to c/perchance@lemmy.world
 

Dear Perchance Dev, would it be possible to add blockedByCurrentUser or a similar blocked property to the objects of the other users, so their message could be hidden and toggled to provide a better user experience?

Note, I am asking this because; when a user replies to the message of a person that is blocked by the current user, that message object's contents are presented to the current user even though they have blocked them.

 

@VioneT I was wondering if it was possible to load modules like reference = {import:...} through the vanilla JavaScript, inside a script tag instead of writing them directly in the Perchance model text editor?

 

@VioneT Would it be possible to have environment variables in Perchance one day?

 

Guys! Do any of you know what version of the Llama model Perchance AI Chat plugin uses specifically?

 

Dear Perchance Dev ,

I would kindly like to make a request for a new plugin, "Live User." Traditionally this required a web socket server. I have personally set it up via Glitch with Express to create a WebSocket and then use it.

But I think if you create this as a plugin it would be easier for other people to implement them without so many hassles.

The essential things I personally think would be good are;

  • It would be good if it returned a numeric value, so potentially math can be done if needed.
  • Another feature could be to display combined user count from different generators. However, whether this is strictly required, is a decision I am leaving upto you.

Also, now that I think about it, maybe the comment's section too could display how many users are using it at the moment. 😮

 

I have noticed that the comments could be styled through the Perchance Panel, however I noticed that the style are not as comprehensive as using traditional CSS would be. It can be easily mitigated by using a CSS file and if there was a way to link the CSS file to the comments plugin. It can be easily achieved as well, if there was an option to write the URL of the CSS file, the comments plugin would only need to append a link with href and rel as style at the end of the iframe to use completely custom and comprehensive CSS.

I have many generators, and in all of them, I use darkmode, and since there were no darkmode buttons for the comments plugin, I just decided to use darkmode as default, however recently I have noticed that some people have eye condition where it is hard for them to read text in darkmode. So it would have been great if the dev could implement a message listener so I could post a message for darkmode from the parent window to the container, of course this would require the comments plugin to handle a darkmode function to apply the dark class to the body inside the iframe. If the dev is consider this, I believe not everyone uses dark as class, so I think making another option for the Perchance Panel as to what the class name could be is great.

Next up, I have thought about images, we upload images in the comments, however what if, we as creators were to predefine sets of images to be used? I think the smarter way would be to look for image links. However the reason I am proposing this is because I wanted to predefine sets of custom emoji, for example, :husk:, I could predefine it and the plugin could format them before sending.

Next, I have thoughts of being able to set up bots. It could be a great innovation. However I do not think this suggestion could be taken into consideration due to its complexity. Bots could be written through JS and the reason I am suggesting this is because I thought of being able to set up an AI using the Perchance AI Text plugin. If the dev is indeed considering this, I believe many people would create their own bots, and thus, there should be a way to share them, which could be done as pure codes, or shared links for files. This suggestion is extremely complex, but this is just my suggestions.

Next, the Perchance Comments Plugin by default has a border, which is completely fine, but I noticed that we are unable to remove that border even if we try to style the container in the Perchance Panel, I am merely bringing this up as a graphical issue, however this, too, should be solved upon being able to use custom comprehensive CSS.

In summary, what I would like are as follows:

  • Custom CSS Linking: I would appreciate adding an option to the Perchance Comments Plugin to allow users to specify a URL for a custom CSS file, allowing comprehensive styling beyond the current options.

  • Dark Mode Accessibility: Implement a message listener for dark mode toggling from the parent window to the plugin container, allowing users to switch between dark and light modes. Additionally, allow customization of the CSS class for dark mode (e.g., .dark).

  • Predefined Images and Custom Emoji: Allow creators to define sets of images to be used in comments. Also, enable the formatting of custom emoji (e.g., :husk:) by predefining them in the plugin.

  • Bots and AI Integration: Though complex, consider adding the ability to set up bots using JavaScript, along with perhaps the ability to use Perchance Plugins. Provide a means to share bot configurations, either as code or shared links for files.

  • Border Styling: Currently, the Perchance Comments Plugin has a default border that cannot be removed even with container styling. This issue should be addressed alongside the ability to use custom CSS.

view more: next ›