it means the site sent a request in the background and it failed in a way that the devs didn't bother to code a user-facing error message for. It's been happening lately due to timeouts when replying to certain users
this post was submitted on 01 Nov 2024
43 points (100.0% liked)
askchapo
22830 readers
255 users here now
Ask Hexbear is the place to ask and answer ~~thought-provoking~~ questions.
Rules:
-
Posts must ask a question.
-
If the question asked is serious, answer seriously.
-
Questions where you want to learn more about socialism are allowed, but questions in bad faith are not.
-
Try !feedback@hexbear.net if you're having questions about regarding moderation, site policy, the site itself, development, volunteering or the mod team.
founded 4 years ago
MODERATORS
https://www.npmjs.com/package/react-toastify
I assume it's something a dev is fucking about with, or maybe a placeholder that someone forgot to remove
This is a subtle nod to Mortal Kombat 2, when a player performed certain fatalities an audio track would be played that would say "Toasty!"
It's a sample message, Toastify is the JS library used for notification popups. I've seen this a couple times when Hexbear didn't load completely, so I just refreshed it
It's reverse psychology and toastifer sucks actually
I don't know either but Toastify is pretty awesome
Does Hexbear use toastr? we use it in work(we also use TS ) and I haven't looked leemy/hexbear source since year one