slow in performance (short-lived bursty TCP connections) if it was ever used to transfer resource heavy HTML pages.

https://en.wikipedia.org/wiki/Gemini_(protocol)#Reception

Well duh. A bicycle is also overloaded and cumbersome, if it was ever used as a car.

Edit: to clarify, the whole point of the gemini web is to avoid heavy and complex site layouts. Automatic embedding and stuff just doesn’t happen there. Also doesn’t use HTML but Gemtext. So, short-lived and bursty connections, are a ideal fit.

  • glimse@lemmy.worldEnglish
    9·
    1 day ago

    You seem pretty knowledgeable on the subject, go ahead and edit it! Seriously. I mean that with zero snark.

    Someone without your skillset is going to read that section and not know any better. Just delete it and explain why. I’ve made hundreds of edits over the years and I’ve never even made an account.

    My encouragement here is real. We rely on each other’s expertise. People like me who know nothing of the Gemini protocol need people like you to keep this page accurate.

    Now for a tiny bit of playful snark: I am mildly infuriated that you noticed this yesterday and still haven’t changed it. Do it! Be the change you wish to see!

    • MonkderVierte@lemmy.zipOPEnglish
      3·
      1 day ago

      The whole Reception section is gone now. Looks like somebody was faster.

      And no, i’m no expert in Gemini, no regular user either, though i welcome the whole Gemini + Gopher + co. idea. A bit too minimalistic for my taste.

      • glimse@lemmy.worldEnglish
        3·
        23 hours ago

        Couldn’t have been me :)

        But still. I encourage you to make those edits in the future. Sometimes writers are wrong, sometimes they’re pushing an agenda. I’m inclined to think whoever added that section did so maliciously and since it’s not a popular article, no one noticed. Wikipedia thrives in part because of people like us!