FALSE ALARM, CULPRIT FOUND: I had a MalwareBytes browser extension that slowed the emote picker down. The extension has been purged and now both the popup and the inline picker are working well.

The original post before I did testing

I try to fidel-salute in a Hexbear comment. The picture takes forever to even load in the picker so it takes a while to see if I’ve even selected the right emote. Most of the emotes in the list I can’t even see the pictures unless I step away for a minute and come back after they’ve all loaded. I hit submit comment. It takes forever to post. I can hear the fans whirring. If I’m streaming vid on blorptube while posting something from the emote picker, sometimes the video will just pause and stop loading until whatever process the emotes have kicked off completes. I don’t know why some emotes are visible while others aren’t it doesn’t appear to be related to order that they show up in the list

I think “Well I’m on the ESR of Firefox, maybe it’s just old” but then I boot into Linux with cutting-edge up to date Firefox and it still behaves largely the same.

I have wondered if it’s an internet speed thing but it seems to behave this way whether I’m on ethernet or 802.11n wireless, whether or not my VPN is on.

It also takes quite some time for emotes to load in the emote picker on Blorp, come to think of it.

I’ve got 16GB of RAM, that should be plenty. Yes I know the web has gotten more intensive since this computer was made 13 years ago but come on, compared to hell sites like twitter, facebook, and new.reddit, lemmy seems downright lightweight. NoScript and other blockers aren’t blocking a ton of bloat here.

I’m not criticizing the unsung heroic devs of Hexbear. I’m no good at web dev, hated it when I had to do it for work, and couldn’t fix or optimize this either. But I would like to understand what the root cause of this problem is and

(If the answer is “upgrade your hardware or live with it” then I’m living with it, because my precious little computer is my buddy and I’m not abandoning it)

  • D61 [any]@hexbear.netEnglish
    13·
    6 days ago

    Most of the time, if I’m trying to post a comment:

    • I need to type everything in the comment box and click the submit button.

    • Select All and Cut everything out of the comment box while the hexbear logo is spinning in the submit box.

    • Click the Reload Page button. A little box with “Type Error” pops up at the bottom of the screen.

    • After the page reloads, paste everything back into the comment box and click submit. 90% of the time it works like a charm.-

    • BoarAvoir [they/them]@hexbear.netEnglish
      13·
      6 days ago

      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

      • D61 [any]@hexbear.netEnglish
        2·
        5 days ago

        the Type Error is I think, expected when reloading while a request is in progress,

        the-more-you-know Good to know.

        Typically I’m lacking in patience to wait. Sometimes I’ll have multiple tabs open and just click the submit button and go do other things. On rare occasions, after clicking submit while the spinning hexbear icon is doing its thing and seems to be stalled, I can reload the page and the comment will have posted.

        Linux Mint, basic Firefox with Ublock and NoScript, on a frankenPC with a few parts that have got to be close to 20 years old by now (which is why I don’t think to mention it when skimming posts/comments about the site misbehaving).