Believe it or not, the server issues on March 5th were unrelated to the size of the mega.
We occasionally get hit with large waves of bots scraping the site, just doing full pageloads for every. individual. comment. on every single post, which DDOS'es the most fragile part of the server stack, the frontend/UI (normally, initial pageload is only done once and then navigating around the site just fetches the data needed from the API which is much more stable). Once the fresh batch of bots were blocked it came back up (and then the mega was rotated hours later)
The comment count does seem to impact the performance of the page in people's browsers though, eventually (especially with lots of embedded content)
The popup picker and the inline picker are both external js libraries lemmy-ui uses, with varying degrees of customizability. The inline picker uses "tribute", a JS library meant mainly for things like @mentions, and the popup is a component called "Emoji Mart". I have looked at the search code for the inline picker and found it is pretty simplistic so I'm not shocked that you'd prefer the emoji mart (I haven't reviewed that code).
Totally agreed about the emoji mart popup inserting at the end. I don't know how easy or hard that change will be to make but it would be a welcome one for sure.
I also think we could still improve loading performance on emojis, though mako's lazy loading change helped a lot. They don't generally change, so they can be cached pretty aggressively, it's just been challenging to get that working right.
We could and have also accepted patches other ways (matrix primarily) but it's currently the primary place. I'd appreciate any contributions! If you are on matrix reach out to carcosa or me about getting added to a dev chat when/if you're ready
This is concerning. It's certainly not ever been bulletproof but it shouldn't be failing out anywhere near every time (the Type Error is I think, expected when reloading while a request is in progress, but I'm assuming you reload because otherwise it never successfully posts?) Any further errors you can share? the developer console/network tab can show a lot of useful details but I'm not even sure where to start with this one. OS and browser details, I guess?
edit: and this comment posted pretty much instantly for me, using a firefox fork on a like 4 year old linux box
When you refer to the emote picker, do you mean the one that pops up when you start typing out the shortcode (e.g. fidel ) or the one above the text input box under the little smiley icon?
Both have performance issues to some degree, but there probably isn't much you can do on your machine about it. Maybe there's some sort of extension that can force cache them? It's something we've tried addressing from the server side in the past with limited success, but it could use more work.
It was likely related to the other issues reported with Voyager. The server was temporarily reporting the wrong backend version number after the update.
Sorry gamers, there's been an ongoing denial of service issue, and then a bungled code deploy today. Hopefully will be a bit more stable going forward.
Believe it or not, the server issues on March 5th were unrelated to the size of the mega.
We occasionally get hit with large waves of bots scraping the site, just doing full pageloads for every. individual. comment. on every single post, which DDOS'es the most fragile part of the server stack, the frontend/UI (normally, initial pageload is only done once and then navigating around the site just fetches the data needed from the API which is much more stable). Once the fresh batch of bots were blocked it came back up (and then the mega was rotated hours later)
The comment count does seem to impact the performance of the page in people's browsers though, eventually (especially with lots of embedded content)