@freemo

Qoto's web UI stopped working for me. Attached screenshot is all I get, the stacktrace the error message gives me (hooray for JS minimization /s) can be found at pastebin.com/XGFmNtUN. My browser is Firefox 92.0.1 on Linux.

@robryk Weird im on the web page right now. Have you not be aable to refresh it?

@freemo No, refreshing lands me at the same error. The error appears after ~5s. During those 5s everything but the Home timeline is loaded, Home timeline contains just a spinner, and everything is nonresponsive.

@robryk have you per chance tried doing a hard reload instead (where it refreshes your cache)? Let me try that on my end too.

@robryk i cant replicate the error here with a hard refresh... if a hard refresh doesnt fix it for you do you know how to open up a debug console so you can see what client-side errors might be logged?

@freemo Hard refresh doesn't change anything. JS console contains only the mathjax-related "CSP blocked a stylesheet" errors and the error that I pasted in pastebin.

@robryk ok I deleted the suspect post. Can you do another hard reload and tell me if it fixed itself maybe?

@robryk Oh wow, ok good to know. Well thats a bug and a vulnerability. :)

@freemo The annoying thing is that I don't know of any way to edit my filters other than the web UI, so the obvious solution had a bootstrapping problem.

@robryk well the problem should never happen in the first place. It seems that our generous character limit can be exploited by just filing the limit with emojis that ultimately take way too long to run and is rendered recursively for some reason.

Follow

@robryk next update I will keep the character limit but limit the number of emojis a post can have to something generous but reasonable (maybe 50 max)

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.