• fiah
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Quick question: I noticed the API calls aren’t (weren’t?) compressed, is that on purpose?

    • gkd@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Going outbound or inbound? Outbound the requests are super basic, inbound they are pretty large. There’s a lot of limitations on that.

      For example to get basic user info you have to receive a bunch of other information that you’re not going to bother using. Hopefully in time this will get changed, because there’s no reason to be receiving so much data whenever you really only need a few bytes.

        • gkd@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          Ohh you’re referring to wefwef. I’m not the wefwef dev, I’m the memmy dev. Thought you were talking about API calls memmy makes.

          • EmpathicVagrant@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            The fact that you’re not just actively engaging here, but advocating another route, makes me want memmy on apple.

            • gkd@lemmy.ml
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              The key to making Lemmy work in my opinion is being a real community. That means having everyone help out in any way they can and working together. Memmy alone can never fill all the gaps, nor can anything else. A wide selection of options is key to getting more people on board.

              Already we are seeing varying designs and implementations, and that is great since users definitely don’t want to be locked in to a single option. Glad to see it.

          • fiah
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            oh shit sorry, apparently I can’t read worth a damn