@freemo he asked about fixing the CORS headers for the instance. QOTO isn't working in the web client he wants to use, and he's been told it's due to our CORS configuration. I think this is also why the MathJax/LaTeX thing has been broken since forever, so might kill two birds with one stone here if you are able to fix it.
🇳🇱
Ahh yes, our codebase has this fixed... its the upgrade to all the other stuff that is overwhelming and holding me back... its more than i can catchup with alone and despite offering to pay to hire someone to help no one as stepped up.... So i am struggling to get the code releasable even though this specific problem has been fixed int he code.
There are other issues behind the scenes too that are harder to explain .I have a system admin who helps run the code itself but he is trying to move away from custom hosting and thus ont he next release we need to prepare to move servers and me taking over without his help... which just adds to the fact that I have no help and we have gotten too big for me to go alone in terms of time commitement to keep up on code, release, and admin.
I have more freetime now so **maybe** i can catch up... but doing **everything** with no technical help is still a lot on a custom code base.
Wonderful, yea the migration allows us to fix the CORS header at the load balancer which i think is why this appears fixed now. We actually have an update that fixes it server side but thats redundant.
