If you go here: https://perchance.org/ai-text-to-image-generator, enter a prompt, click on the persona/chat button of an image, click generate persona, possibly edit the result, and then click chat with them, it creates a public link with the character’s image and the generated/edited text description. How long does that link persist?
Why not just add the character data to local storage when you click “chat with them” on the ai-text-to-image-generator page and then just navigate directly to the ai-character-chat page?
Local storage is origin specific, meaning the local storage in
/ai-text-to-image-generatoris different from/ai-character-chatand there isn’t a way to pass data from one local storage to another. There are ways to pass data, but it involves using iframes and post messages.deleted by creator
These two pages share the same origin and can both access the origin specific local storage.
To see this, open https://perchance.org/ai-text-to-image-generator and https://perchance.org/ai-character-chat in two tabs of the same browser. In the first, click F12 to open dev console and paste localStorage.setItem(‘perchanceExample’, ‘iSeeYou!’) and press Enter. You will see it appear in the local storage of the second page.
Perhaps I’m not understanding what you’re saying. Or maybe am I, and it IS possible to do it the way I suggested but there is some other valid reason for not doing it like this that I haven’t thought of. The point is, it seems like you don’t really need these zip files and the fact that you have them anyway and are holding on to them indefinitely without what seems like a valid reason seems sus to me.
Each perchance page has its own local storage, which is by having a different domain. See this previous post. Then, each page is embedded on the main page, which is the top frame. By going to the Dev Console and setting the local storage there, it would be reflected on the top frame.
You can test by adding this to the HTML panel (bottom right panel after clicking ‘edit’) then clicking ‘reload’ on the bottom of the preview:
<script> localStorage.setItem("TEST", "a") </script>On one page and another, and it would be reflected to their respective domains on the local storage, instead of the top domain perchance.
I guess the purpose of saving the data is for ease of access and convenience for sharing instead of downloading the data - clicking import - selecting import file - confirm. Maybe the solution is to just add a ‘download’ button instead of creating a share link so the data is downloaded locally, but again, the steps of download - import - select file - confirm might be inconvenient for others.
As long as you don’t share the link or the file id. No one should be able to access the data from it.
@perchance - I’ll ping the dev again just in case.
Ah that makes sense now. I guess there isn’t an easy solution to what you want to do. Also I didn’t realize the sharing aspect was important. Otherwise you could pass the data from one subdomain to the other through the server with an API POST.