perchance @ perchance @lemmy.world

Posts

25

Comments

440

Joined

2 yr. ago

Moderating

---

Okay, sorry about that, can you try clearing and then importing again? I've added another fix.

Possible explanation: https://www.reddit.com/r/perchance/comments/1isr339/comment/mdyvhnl

But actually, looking at the URL just now, it's the "cookie popup" script which is used for GDPR type stuff, which is legally required in the European Union: https://user-uploads.perchance.org/file/63c85ff7ce3ecc0323e0bbd555078fad.js This script is used at the platform level - not within any particular generator, so it's not specific to the story generator.

I'm not sure why NordVPN has flagged it. I have NordVPN and I haven't received any warnings for this (but I'm not in the EU - maybe that matters). Either way, it should be fine to just block it.

I've just tried something to fix this - can you try again?

Thanks! Fixed.

Can you try in Chrome guest mode? By clicking the profile pic circle in the top right (next to the 3 vertical dots) and clicking "Open Guest Profile"? @someone_random@lemmy.world was seemingly able to get it working in Guest mode (actually @someone_random you checked https://perchance.org/a5lshnqjrq in guest mode and it worked, but could you also check https://perchance.org/ai-character-chat ?)

If it works in guest mode then it's almost certainly something to do with browser extensions or broken browser caching. The latter could actually be related to a Windows 11 update, but it is definitely not the first thing I'd guess, especially since incognito mode definitely shouldn't be using the same cache.

Also, @someone_random, you mentioned that incognito is the closest thing OperaGX has to guest mode, but note that some browser extensions may still be enabled in that case, so testing in incognito mode doesn't necessarily rule out browser extensions being the cause.

Okay this time I've done a much more comprehensive fix, so it should patch ~all the functionality that older browsers don't yet have.

if i stay too long it’s crashed

I'm not sure what's causing this, but let me know if it still occurs after checking the above fix and we can debug further.

Hmm so it's working on Chrome guest profile which confirms that it's not your network - can you see if your OperaGX browser has a similar "guest mode" and test with that?

Since you mentioned that it has the same error in Edge and Chrome (when in 'normal'/non-guest mode) - is there a browser extension that you have for all 3 browsers? You can try temporarily disabling your browser extensions one by one on the extensions manager page of your browser.

This error from your earlier screenshot is not coming from Perchance code, so it might be from a browser extension that's causing an issue:

If you do manage to find the culprit, please do share it here so we can more easily help others with similar issues in the future.

Can you try visiting this: https://user-uploads.perchance.org/file/4cc84b2c503aad595e5c6e9fffe24602.js and let me know if there's error or if you see the script (a bunch of code stuff like (function (global, factory) { ...)

If you do see code at the above URL (i.e. no error), then can you use Chrome in guest mode (click profile pic thing in top-right corner, next to 3 vertical dots, and click the item at the bottom "Open Guest Profile") and screenshot this: https://perchance.org/a5lshnqjrq

Also, is this only a problem on your university wifi? Do you have access to any other internet connection to test, so we can determine whether it's specifically the network that's the cause?

Sorry about that I think I had a bug - can you please try again? https://perchance.org/a5lshnqjrq

Also, if you happen to have another browser installed, can you try with that too, so we can cross-check against e.g. network issues vs browser extension issues, etc.

Testing your OperaGX browser in "guest" mode (i.e. without any extensions enabled), would also be useful info for me.

If it still doesn't work in other browsers, then, if possible (it's fine if not - just ignore this part), can you tell me the company name of your ISP? I.e. "Internet Service Provider" - the company that provides your wifi/mobile data. There were some malicious uploads to user-uploads.perchance.org which caused some ISPs to temporarily ban the subdomain, but it seems that some ISPs have "permabanned" it, so I'd need to reach out to them to ask them to lift the ban I think.

Sorry about that, I think that was a bug from a different change I made. I think I've fixed it now. Can you please try again?

I've just added deletionUrl to the returned values of the upload plugin:https://perchance.org/upload-plugin-deletion-example#edit And I've added a button in the t2i framework which uses it in the "share link" popup.

@thknas@lemmy.world Despite file upload URLs being unguessable (in a cryptographic sense), I think it's a very fair point that there should it should be obvious to the user when they're about to initiate an upload, or it should be easy to easily undo. I considered adding an auto-expiry (which the upload plugin already supports), but I figure this "deletion button" approach is probably the most intuitive one for most users, who may not read the "this link expires in N days" message, and be surprised/dismayed when their character link gets randomly deleted after a few days.

Another option would be to use the URL hash to store data (i.e. massively long link where the data, including the character image, is embedded within it), so no upload is required. This wouldn't solve your browser history thing, but tbh I think that's not really something that Perchance can solve for you - browser history is more something for you to manage, especially since web pages (like many on Perchance) can use localStorage, so it's not just about the URL of the page. So in general I think you ought to be in incognito when you don't want your browsing history to be recorded by your browser.

In any case, thanks for the good feedback - let me know if you have any thoughts on the new design.

Can you try again now? I think it's because you're using an old browser version, but I've just added something that should work around the issue.

@VioneT@lemmy.world I've actually fixed this by adding the polyfill at the 'platform' level - i.e. with code like this in the iframe, before the generator code runs:

    
if(!window.structuredClone) await import("https://cdn.jsdelivr.net/npm/core-js@3.40.0/web/structured-clone.js/+esm");


  

If there are any more platform-level polyfills that you think should be added from https://github.com/zloirock/core-js (or elsewhere) let me know. Easy for me to add, and saves every dev from having to add their own polyfills for the longtail of old browsers.

Hmm, the code/logs that you've pasted isn't actually from perchance - looks like it's coming from a browser extension or something.

Can you tell me what you see when you visit this page? https://perchance.org/dl0tvy489b#edit If it's working you should just see function(e){return t(e)} appear in the middle of the page.

Can you please try visiting this page and telling/screenshotting what you see? --> https://perchance.org/a5lshnqjrq

For some reason the CBOR library doesn't seem to be loading in your browser. It could be a browser extension causing an issue, or maybe due to an old browser version, or weird browser. Can you let me know the browser name and version?

Sorry about this, and sorry for the delayed response - I think it was a rate limiting bug/oversight (that I've just fixed). Could you try again and let me know if it's still not working?

Aside: It is weird that you tried on phone data and it still didn't work though - if rate limiting is/was the issue, then testing using your mobile should have worked. Are you sure you had your wifi turned off on your phone when you tested? If not, then your phone was probably automatically using your wifi connection instead of your mobile data.

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/

@VioneT@lemmy.world

¹ 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.