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!
1. Please follow the Lemmy.World instance rules.
2. Be kind and friendly.
3. Be thankful to those who try to help you.
4. Only post about stuff related to perchance.
5. Refrain from requesting Prompts for the AI Tools.
text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"6. Search through the Community Before Posting.
Hello everyone. Today I have found /huge-emoji-list.
And I duplicated it into /cocells-emoji.
But why am I speaking of this? Well, since the comment essentially relies on URL. And the list literally consists of almost 87k emojis.
I want to understand what fellow developers have to say about this? Because this generator is pre-loaded with so many resources, but the constrain lies in the URL. After all, it essentially contains 20000000+ characters, well, an estimate.
If you have more than ~10k emojis, I'd definitely recommend that you put all your <name> = <url> lines into a text file, and upload that text file to perchance.org/upload
If you put >80k names/urls into a generator directly, and try to use that, then I think many/most web browsers won't load the comments plugin properly, because the data is actually passed in the iframe URL hash, which has a size limit. So if you use the customEmojis = https://user-uploads.perchance.org/file/0575b613c0c3b61cde5c11225e7b846a.txt approach, then it just passes that text file URL into the comments plugin iframe, and the comments plugin itself does a fetch request to grab the lines and parse them.
This has the disadvantage that it's slower to update the emoji list (since you need to re-upload the file each time), so I just added the ability to import a text file URL of emoji lines, but then also add your own ones to it like normal:
commentOptions
customEmojis
@import = https://user-uploads.perchance.org/file/0575b613c0c3b61cde5c11225e7b846a.txt // <-- this is a big text file full of emoji lines like the ones below
catjam = https://user-uploads.perchance.org/file/a43d0b52d94c91dddb00cf157dd8c989.webp
catcrythumbsup = https://user-uploads.perchance.org/file/14c78e8fbd9767e69a6b86d26817bacb.png
i.e. you can add @import = <url> to import a huge "base" list of emojis, and then add your own on top of that. You can also import the URL like @import = {import:huge-emoji-list}, of course.
https://perchance.org/comments-plugin-custom-emojis-import-url-example#edit
Thank you very much. 🫠
I have a question, can I import the text file even if it is hosted outside perchance, for example I would want to import it from GitHub, would it be possible?
No, it must be user-uploads.perchance.org URL. I don't like seeing generators break, due to people using random file hosts that later shut down (or worse, using random links to e.g. pinterest images, fandom/wiki images, etc. which are often only temporary CDN urls), so my plugins in the future will require using perchance URL uploads in most cases.
and then when the apocalypse happens and the world needs to restart, all important info of the world will have been saved on the perchance server and it will be easy.
BROO 💀
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.