perchance

Thank you 🫡 I will eventually get around to all your great suggestions (and the feedback from other users here) once I've got a handle on this issue and a few other important things. As always, feel free to re-ping me in comments and/or repost your most important feature requests and bug reports (once every couple of weeks or so) so I can bump them up the priority list.

Yes, sorry about this. This is priority number 1 for me right now - I've been working for the last few days on fixing this. It has turned out to be harder to fix than I anticipated. Some sort of GPU memory error due to particular driver versions or something. That said, I should be able to fix it within the next day and a half (~36 hours from the time of this comment) unless something goes terribly wrong. I'm going to upgrade the whole stack, which should fix this issue, and also give a bit of a performance boost (slightly faster text generation) as a bonus.

i have been informed that malware can be embedded within favicons

You have unfortunately been misinformed on this matter. From the perspective of web browsers, favicons are just images, and will never be executed as code. You might be thinking of web-application-specific exploits - e.g. related to vulnerable WordPress favicon plugins or something. This is not at all relevant to Perchance. Using this plugin is completely safe.

That said, I appreciate the concern!

Hmm I can't replicate this, but I did just try a quick adjustment based on a hunch, which might fix it. Can you check? If it doesn't work, can you let me know which browser + device you're using?

Thanks for reporting this! A couple of the GPUs in the text generation cluster were fried. Normally they'd throw an error and I'd detect it and remove them, but with this particular error they just output gibberish without any explicit error. I've added code to detect this now, so the issue should be resolved. Please let me know if it occurs for you again.

Edit: Hmm. Still getting reports of this in the feedback. If anyone can provide example outputs of the gibberish that you're seeing, that would be great.

I've solved the original issue already, but it sounds like you've found another (related) issue. If you answer each of these questions, I will hopefully be able to solve it:

1. Can you please share a screenshot of the error?
2. Which OS version and Safari version are you using?
3. Does the import fail if you use incognito/private browsing mode?
4. Does the import fail for newly created export files (e.g. open incognito, create a chat, export it, and then try to re-import it), or do you only get the error for old export files (e.g. ones you created a week ago or more, roughly)

Sorry about that. The original reported issue is fixed, but it sounds like there's another related issue. If you can give me more details, I might be able to fix it. E.g. screenshot of error message, details of browser version and device OS, whether it's a recent export file, or one from more than a week ago, etc.

If someone is able to DM me a link to an exported data file (whole export or thread/chat export) that is giving the error, then I'll be able to fix the problem almost immediately.

All fixed now, thanks to a DM from @[email protected]

Thanks for your report/corroboration on this! Let me know if you are still experiencing any issues.

Sorry about this. I'm not currently able to reproduce this problem. Is it occurring with recently exported files, or is it old (pre-mem-update) export files that aren't able to be imported?

Also, if you're able to give steps to reproduce the issue (e.g. open firefox, create character, send message, export thread, try to import thread), or if you've got an unimportable thread/file that you're able to share, that would be very helpful.

@[email protected] @[email protected] Heads up that I just got a support message from the email provider I use saying that it has been suspended for suspected spamming.

This happened several months ago, and I added stronger IP-based rate limits which apparently fixed it. Probably spammers or people doing a DDoS-type attack (spamming signup requests for emails in big public email lists) for whatever reason. I've added more guards, which will hopefully fix it, but it may be a few days before they allow sending signup emails again 🫠 So we may get a bunch of posts on Reddit and Lemmy about not being able to sign up - just letting y'all know

@[email protected] Okay, it's live on perchance.org/ai-character-chat - sorry for the huge delay! And thanks again for pestering me about this

Done, thanks!