So when using https://perchance.org/ai-story-generator which I love using! I keep getting this error and when I refresh the page it goes back to where I loaded my AI Story how do I get rid of this, Change it, Or is it whoever made the Ai story generator? here is the Error! (I know noting about Coding as well!) :An error has occurred somewhere in your code (in lists or HTML): In the function called antiAntiLayoutJank within your lists editor, near line number 283, there’s a mistake in your code that’s causing this error:
QuotaExceededError: Failed to set a named property ‘storySoFar’ on ‘Storage’: Setting the value of ‘storySoFar’ exceeded the quota. I even tried Google Chrome same issue! I’m using Microsoft edge.
You can solve this by pulling out a paper and a pen (or pencil, if you prefer) and writing your own stories without using AI.
Yeah, but that requires, uhhh, checks notes, work, ya, that requires work mate, who has time for that, it’s SLOP-time!
AI is not looked upon kindly in most places on Lemmy, for good reason.
Far as your problem goes, learn how to read? The error message doesn’t have too much extraneous shit in it.
Ignore the start part, as that’s clearly talking about the HTML, the building blocks of the site.
Quota exceeded in ‘storySoFar’. Whatever it’s storing as storySoFar is too big. You aren’t the developer, but that’s a pretty clear variable name. The story so far exceeds the quota. The story so far is too big.
I swear, reading error messages shouldn’t be a god damn super power. I’ve never used this slop generator in my life, I just read your error message.
I swear, reading error messages shouldn’t be a god damn super power.
If the author had any reading/writing skills, he’d not be using a slop generator.
Hey sorry everyone’s being a twat. There’s nothing wrong with using the available tools at your disposal to try to learn about things that interest you. Just make sure it’s still a learning process and not a hand holding process. Leverage AI, don’t make it support your full weight.
I can tell you this problem is out of your hands. The web app you’re using is causing it’s own error here.


