Ah thank you! Fixed. It shouldn’t save as new gen when you’re using a collab link anymore, even if you’re logged in and not the gen’s owner.

There are a few factors here, but it’s most likely up to the laws in your country, and as far as I know, most countries do allow (or at least not explicitly ban) you to sell AI generated content, but some countries have laws which don’t allow you to claim copyright over that content - meaning that you’re allowed to sell it, but you couldn’t e.g. prevent others from copying your book cover image and using it in their own work.

Fair, sorry. I’ve taken it down. You mentioned in a comment in this thread that you’d be okay with me keeping it there if I added credit, which is nice of you. I think your profile (and your original nsfw version of this character) is probably too nsfw to link to unfortunately. A lot of the character cards and character card sites seem to be very heavy on the nsfw content.

I should probably create all the example characters from scratch with some help from Claude or R1. Some of them have already been almost completely rewritten and have different pics, but even then the original creator still deserves credit for the core idea.

(That said, I’ll probably attempt to selfishly put off a re-write of the examples for now because at some point in the hopefully-very-near future I’ll finish creating the “database plugin”, and at that point the work to redo the examples would be wasted because the examples will be removed in favor of a community-contributed database of characters, implemented using that plugin.)

I think all the weird browser issues are fixed (I think it was to do with bad cache headers resulting in different versions depending on when editor was first loaded in the browser being tested), but please let me know if not.

If the gen owner CTRL-Zs, it affects everyone’s edit if they are editing in real time.

Thanks! I think this is fixed now, if not let me know.

It needs the owner to ‘save’ the generator to create a backup of the old edit.

I’m not sure what you mean by “create a backup of the old edit” - but to be clear it should be possible for anyone with the collab link to save - i.e. not just the owner. Please let me know if that’s not the case.

Changes are to the editors are LIVE, but a reload/auto-reload is needed for generator viewers to see the changes in the preview window. If there are changes made by other collaborators and the gen owner tries to refresh the page, there would be a prompt that there are unsaved changes, but the changes are still applied to the page.

The “unsaved changes” prompt is actually correctly warning you in the sense that you need to save the changes to be sure that they’re not lost, since (currently) if all collaborators leave, then the collab server will (eventually) “garbage collect” the session. I could make it so the session state is persisted to disk - that would perhaps be more intuitive (this may have to wait for now though, so the warning should be taken seriously until it no longer appears).

Also, in https://perchance.org/collab-testing-01-01 you have Password: hello (or maybe someone else added that), but it’s not possible to manually set an “edit password” (unless I’ve forgotten a feature I added…). It should be a random string of letters/numbers. Note that the edit password is different to the collab password/link. Edit passwords are really only necessary for anon-created generators, which is why you’re not given an edit password for generators that are created when you’re logged in. The “edit password” gives you more permissions than the collab password. For example, the edit password has the capability to disable/enable collab links. Whereas the collab link/password just gives you the ability to edit/save a generator and participate in the live editing session.

It’s a good underlying question, despite some misunderstandings¹. Your overall point here is this:

technically you don’t really have privacy if you’re using someone else’s generator.

which is correct, and is unfortunately how the internet works in general. I.e. any webpage on the internet can do whatever it wants with the data that you input into it. I must stress that Perchance generators are no different to any other webpage on the internet in this regard.

(As Vionet20 mentioned, I wrote some related comments here, which includes info about how Perchance sandboxes generators, which means that in terms of privacy from ads/trackers, Perchance is arguably much more private than the average ad-supported website, since ads/trackers aren’t able to see what you input into Perchance generators at all, ever.)

That said, I’ve just added a feature which allows you to “lock down” a generator so that it can only communicate with external servers that you explicitly specify, so data can’t leave your browser unless you allow it to. Ideally this would be a feature that’s built into web browsers themselves, but until then this is an improvement.

Here’s the explainer:

https://perchance.org/custom-content-security-policy?$csp

TL;DR: Add ?$csp to the end of the generator URL (like you see in the above URL) to prevent it from making requests to external servers, which means your data will always remain in your local browser storage only. But be sure to read the above-linked page to e.g. see how to add exceptions for generators that need it, since the default filter is quite strict.

Alternate/additional tips to protect your privacy on the web:

• As mentioned on the above page, you can use a VPN, and you can also make sure you never input personal info (e.g. your real name) into any web page unless you trust it. This is the most simple and practical approach to privacy on the internet.
• Perchance-specific tip: You can fork a generator to make your own copy, so once you’ve checked it then you can be sure it won’t change. That said, you should also be sure to fork any plugins that it imports (ones that aren’t ‘official’, at least).
• Mostly Perchance-specific since other websites tend to have minified/obfuscated code: You can copy the code of a generator, and/or things it imports, and ask an AI like ChatGPT/Claude/DeepSeek to analyse it for any data exfiltration.
• You may be interested in running AI models locally, which is by far the best way privately use AI models - if you can afford the hardware that’s required (i.e. one or more high end gaming GPUs): https://www.reddit.com/r/SillyTavernAI and https://www.reddit.com/r/LocalLLaMA and https://www.reddit.com/r/StableDiffusion/

@[email protected]

¹ Misunderstanding: “ostensibly for logging purposes” - no, rather, it’s because they literally wrote the entire application/experience/game that you’re viewing - it’s not possible for the Perchance platform to shield your prompts from the generator author, since the author is the one writing the code that e.g. pre-processes your prompts (maybe adds styles to it, for example), sends those prompts to the AI, post-processes the results, integrates the resulting data with other plugins, etc. to create the whole experience. This does not mean that generator authors on Perchance automatically see your prompts. By default everything is private. They’d have to specifically write sneaky code to send your prompts to an external server, and that can be blocked by this new ?$csp feature. But to be honest, the best approach to privacy is to just (1) use a VPN and (2) never put personal/sensitive info into random websites on the internet. If you can’t do both of those, then try to use reputable websites/generators, since they presumably have a good track record and also have “more to lose” by screwing over users. They’ll also be under more public scrutiny as a result of being more popular.

it requires the gen owner to save to apply any edits […] And the collab editor saving the gen will making a new copy.

Hmm this definitely shouldn’t be the case. Anyone with the collab link should be able to save/apply the edits. Can you try again, and if you’re able to reproduce it, can you let me know the steps to take to replicate?

If someone with the collab link saves it, it should just save it as if they were the gen owner (i.e. not make a new copy).

Thank you! Done. I really appreciate the work you did to find those quick fixes 🙏

Hi, I might be misunderstanding, but the custom code below seems to work for me (after sending each message, the button’s number increases). Can you please send me a character link or some custom code which replicates this issue?

let count = 0;
oc.thread.on("MessageAdded", function() {
  count++;
  oc.thread.shortcutButtons = [{autoSend:false, insertionType:"replace", message:"/ai test", name: "test " + count, clearAfterSend:true}];
});

The issue is before many try and error

Can you let me know any details about the issue you had? It may have been that the server’s rate limits were too strict. I’ve just edited them to give a bit more leeway, so hopefully that’s solved your issue.

If there’s multiple dev, they should keep using the link for a long period without nuke the gen?

Luckily it’s not possible to ‘nuke’ the gen with this feature (even if there remain some early issues with the collab server), since you can always just open the ‘backups’ list and download any older version of your gen. That said, it’s certainly possible that there are ‘annoying’ bugs where you e.g. temporarily get out of sync with other devs in your collab due to stuff like the aforementioned rate-limiting. And again, please do let me know (and give as much info as possible) if you come across any issues like this.

Hmm can you please share the URL? When visiting the URL did you see a 404? I suspect it was just a temporary cloudflare issue or something. It definitely wasn’t deleted by the upload moderation unless something has gone catastrophically wrong, since the moderation rejects files during upload. So if it was working several hours ago, then it can’t have been due to the upload moderation.

Okay I just made it so if you add background:transparent to the containerStyle option, then that propagates into the iframe and makes the background transparent. Let me know if that doesn’t work, or if you think it should work in a different way. I’ve tested only in Chrome linux:

https://perchance.org/comments-plugin-transparent-background-example#edit

RE Perchance as a Lorebook - I think this could be used instead?

https://perchance.org/api/downloadGenerator?generatorName=noun&listsOnly=true

listsOnly=true was only documented on perchance.org/advanced-tutorial but I’ve just added a note about it to perchance.org/download-button-plugin to help make people more aware of this.

Can you share an example? I just tested and it seems to work for me:

• https://perchance.org/exporter-b7p5czgzy4#edit
• https://perchance.org/importer-b7p5czgzy4#edit

Hmm, it’s hard to say whether this should be expected behavior. I think messing with the innerHTML/innerText/textContent of a ‘templated’ HTML node is currently undefined/unspecified behavior unless someone has strong opinions that they can defend here.

Are there use cases that you can point to, which point to a desirable behavior here? Or anything that points to clearly-wrong behavior?

In any case, I’ve added it to https://perchance.org/known-bugs as something to think about

Hmm, I thought this was an easy fix, but I just reverted the changes because there are some potential complications and back-compat issues. I think we may have to treat all HTML text as if it were “Perchance item text” for now - at least until an overhaul/V2.

The crux of the complication is that in Perchance, text can be affected other text around it - like {a}, so my original solution of “just handle bracket escaping, and not \t, \n, etc.” has some subtle edge cases where behavior is different than what you might expect.

So then I thought, okay, I’ll just do this for text nodes that don’t contain any square/curly blocks. I.e. just remove the backslashes from escaped curly/square brackets, and don’t process stuff like \t. But then we have potentially counter-intuitive discontinuity in behavior. I.e. you take away a square block from some text in the HTML, and you get a bunch of other thing changing (e.g. newlines in a pre element) as a result.

So I think this needs some more thought… I’ve added to perchance.org/known-bugs for now - if you have any thoughts please let me know. Thanks!

Thanks! I think this is solved now - please let me know if there are any more issues.

Thank you! I received a bunch of feedback messages/reports, but no one gave the clue that it only happens if you’ve got a long existing story in the editor, and then you’re loading another one. With that clue I was able to reproduce it and fix it, so it should be working now. Please let me know if not, or if you have any other issues with the new editor.

Can you check if your device storage is nearly full? Should be a page for checking storage usage in device system settings.

Hmm can you check if your device storage is nearly full? It may be clearing the site data due to storage pressure.

Also, which Android browsers specifically have you tested? Chrome and Firefox?

This is a good point. I should be creating more “high-level config” layered on top of the examples that I create, so people can change a line here and there, and see how easy it is to create something new, and then maybe dive deeper from there. The ai chat/rpg/etc. generators that I’ve made aren’t very “configurable” in the same sense as the t2i framework thing.