this post was submitted on 01 May 2026
2 points (100.0% liked)

Perchance - Create a Random Text Generator

1844 readers
31 users here now

⚄︎ Perchance

This is a Lemmy Community for perchance.org, a platform for sharing and creating random text generators.

Feel free to ask for help, share your generators, and start friendly discussions at your leisure :)

This community is mainly for discussions between those who are building generators. For discussions about using generators, especially the popular AI ones, the community-led Casual Perchance forum is likely a more appropriate venue.

See this post for the Complete Guide to Posting Here on the Community!

Rules

1. Please follow the Lemmy.World instance rules.

2. Be kind and friendly.

  • Please be kind to others on this community (and also in general), and remember that for many people Perchance is their first experience with coding. We have members for whom English is not their first language, so please be take that into account too :)

3. Be thankful to those who try to help you.

  • If you ask a question and someone has made a effort to help you out, please remember to be thankful! Even if they don't manage to help you solve your problem - remember that they're spending time out of their day to try to help a stranger :)

4. Only post about stuff related to perchance.

  • Please only post about perchance related stuff like generators on it, bugs, and the site.

5. Refrain from requesting Prompts for the AI Tools.

  • We would like to ask to refrain from posting here needing help specifically with prompting/achieving certain results with the AI plugins (text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"
  • See Perchance AI FAQ for FAQ about the AI tools.
  • You can ask for help with prompting at the 'sister' community Casual Perchance, which is for more casual discussions.
  • We will still be helping/answering questions about the plugins as long as it is related to building generators with them.

6. Search through the Community Before Posting.

  • Please Search through the Community Posts here (and on Reddit) before posting to see if what you will post has similar post/already been posted.

founded 2 years ago
MODERATORS
 

as well as old "sent button lagged", there's new syndrome:

cannot scroll up, the chatlog will auto bounce back to bottom. resolved after a refresh.

I think it might related especially have multiple chat channel switching or stay open at once.

Source: desktop and mobile Vivaldi and some other users feedback.

top 8 comments
sorted by: hot top controversial new old
[–] perchance@lemmy.world 1 points 4 days ago* (last edited 4 days ago) (3 children)

Thanks! It should be fixed now. Note that it's a client-side issue so if users report the issue still, it's possible they still have the old code, so they should refresh the page. If they still get the issue after refresh, then let me know.

[–] ccufcc@lemmy.world 1 points 1 day ago (1 children)

sorry the dev:

  1. chat scroll up bouncing back <= solved
  2. comment dual chat panel mode input snap nonclipped to another input box <= less frequency but it just happened again. Windows 11 Vivaldi browser.
  3. submit comment send button lag (please wait...) <= almost unchanged.
[–] ccufcc@lemmy.world 1 points 1 day ago

also multiple users complaint about : "double messaged" might due to lag or not

[–] ccufcc@lemmy.world 1 points 2 days ago

the send button "please wait..." lagging is still mediocre, about 10sec to 1 minutes from time to time, more than a few users complained.

[–] ccufcc@lemmy.world 1 points 3 days ago
[–] zodd95@lemmy.world 1 points 6 days ago

I've also found, on mobile using Chrome, that furiously scrolling up seem to eventually fix it haha

[–] ccufcc@lemmy.world 1 points 6 days ago (1 children)
[–] ccufcc@lemmy.world 1 points 5 days ago* (last edited 5 days ago)

also new symptom: on desktop, wielding dual chat channel mode:

sometimes the input focus snap to the other channel without clicking in mid-typing, which is new to me. I suspected it's related with the scroll problem? we are scrolling the wrong panel all the time?