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
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
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
Thanks for the heads up. Will look into it.
Did this just start today?
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.
Agreed on IZ, that emote has been renamed :iz-shaka: (and tagged appropriately so it's hopefully still findable)
The rest is tbd, thank you for your efforts making it, and your patience!

(Note: this is not in any way an official statement by the admin team, I'm just a tech dweeb)
We have the ability to add basically unlimited alt-names or descriptors to the tags for each emote, which has made searching in the emoji picker much more viable even for obscure emotes (provided they are well-tagged). Problem is, nobody uses the emoji picker, most people don't even know it exists.
Make sure the library is reasonably well tagged and make that tweak to the searching and this whole conundrum goes away.
Examples below of some existing tags from a previous effort to tag all the emotes:

We might also want to make the alt-text more descriptive for people with screen readers but that's a separate conversation
Edit: Oh it looks like a dev (comrade makotech222) has already chimed in on this below:
also, its maybe possible we can enhance the inline emoji window to use keywords as well. would have to do some experimentation with it.
This would also basically address the following other suggestions:
https://hexbear.net/comment/4396592
https://hexbear.net/comment/4397267
https://hexbear.net/comment/4396837
https://hexbear.net/comment/4396793
https://hexbear.net/comment/4396237
https://hexbear.net/comment/4395861
https://hexbear.net/comment/4397894
https://hexbear.net/comment/4395895
https://hexbear.net/comment/4397730
https://hexbear.net/comment/4397711
secondary option if this isn't feasible: remove the unicode emojis from the emoji picker so it goes straight to our custom emotes when opened, and make it more prominent in the UI somehow (highlight it in a different color, make it bigger, make it sparkle, idc). And still finish the job tagging them all
As others have mentioned, that was implemented in a hurry due to tightening up security and safety around embedded images. I've brought it up to the devs to hopefully rectify, as if an instance is trustworthy enough to federate with (aka, not actively malicious) then it is probably safe to show their embeds (behind a blur).
At the latest, this restriction will go away when lemmy upgrades to pictrs 0.5 which will support proxying image requests, but unless there are objections from the rest of the team we will likely add all federated instances to the image allowlist before then.
I really hope we can restore the old Active algorithm, it's still on the table afaik, but I'm told the way that lemmy's database schema works has changed enough that it isn't trivial to switch back to.
HOW AM I JUST FINDING OUT WE OWN HEXBEAR.COM???? WHICH ONE OF YOUZE
yes! Movie night going on now at live.hexbear.net
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)