Jakub Kuczys @JakubKuczys@qoto.org

I tried registering today and accidentally found that the password requirement validator on Broadcom's registration form has EVEN MORE "quirks" than you already presented. Apparently, the "Should not have three or more consecutive characters that match any portion of the user email address" requirement on their website is checked by generating a regex without escaping user input and validating with that. The form disappears as soon as you start inputting a password...

Hmm, something seems wrong with #qoto's performance for me today, it takes over 10 seconds to show anything but a blank page due to a failing request (status 503) to `https://miy.pw/css/12.css`? Same happened when I was earlier today on mobile network though I can't really verify it's waiting for that request there as well.

I'm not sure what that resource is for but since the page eventually shows up and seems fine, does DOM rendering really need to wait for that request to end?

Has anyone on #qoto tried using #pinafore? Based on the link it gives, it seems like it requires CORS to be allowed for /api endpoint (which should be the default but maybe qoto is doing something special)? 👀
https://github.com/nolanlawson/pinafore/blob/master/docs/Admin-Guide.md