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)

Lemmygrad is a good bet, though official announcements of this sort should also be posted to https://toots.matapacos.dog/@hexbear

Edit: I see FloridaBoi beat me to it.

Announcement post here with a brief explanation of what happened

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

It's fixed

(thank you for letting us know)

Also dosent all modern operating systems have extracting files Just build in regardless of the format?

No.