Pretend this is horribly offensive and should be removed. I forgot. I can't report my own submissions. Someone please report this post. Thanks, @ass@voyager.lemmy.ml. I see the report, but no notification due to HTTP 400 response from `/api/v3/report_count` endpoint. Same behaviour on lemmy-ui, so doesn't seem to be an issue on Tesseract's end (or, at least, not _just_ an issue with Tesseract). Ok, so the `/api/v3/report_count` errors seem to be CORS related. ``` Acess to XMLHttpRequest at 'https://voyager.lemmy.ml/api/v3/user/report_count?auth={redacted}' from origin 'https://dev.dubvee.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. ``` I can understand that not working from my cross-origin app, but it also returns a 400 in Lemmy-UI without any CORS issue. So might be two unrelated 400's? Also I need to update the service worker that polls for those to use the auth header. Also, it looks like single quotes are getting mangled in the DB or somewhere. They're randomly turning into `&#x27`. >They're randomly turning into `&#x27`. This is _fine_. don't Every time a post/comment is edited, any special characters seem to get re-sanitized. Testing in Lemmy-UI to see if it makes any difference. Nope, same behaviour in lemmy ui, so must be a backend thing.
This is a test post from the Tesseract 0.19.0 branch. Testing edit to post.