Sorry about this. It was caused by an erroneous emojo making the site info endpoint fail to load. Issue is fixed now.
Fixed!
Give me a sec, I'll check it out.
Not sure. I didn't load it.
How do you know I haven't always been the hacker who's in control? :D
We were affected by the XSS vulnerability, and have applied the fix from the lemmy devs.
We were affected by a lemmy vulnerability and have applied the fix from the lemmy devs.
Yes. We were affected and have applied the fix from the lemmy devs.
And then you had a girlfirend who just happened to have injectable E just lying around...
Thanks lovely. I'm back on my feet mostly now.. still pretty sore but better every day.
I'm a good way there now. Thanks!
It wasn't an actual emojo. The script processed the SQL header column names as an emojo and tried to add them. Unfortunately
publicUrlis not a valid URL, so lemmy's/api/v3/sitemetadata endpoint started returning an errorrelative URL without a baseinstead of the JSON that the website was expecting and so the site just stopped working for everyone the next time it tried to load that url.