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.
As the Memmy dev I can also highly recommend wefwef. Great product for such a short lifespan.
Quick question: I noticed the API calls aren’t (weren’t?) compressed, is that on purpose?
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.
the json coming back from requests like showing a thread was not compressed when I checked yesterday (firefox on ubuntu): https://discuss.tchncs.de/pictrs/image/1a99e758-deaa-46f6-8eff-3aa2158858ad.png
but I just checked again and now it’s correctly responding with compression (chrome on windows)
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.
The fact that you’re not just actively engaging here, but advocating another route, makes me want memmy on apple.
Memmy is on Apple, in fact I think it’s only on Apple?
oh shit sorry, apparently I can’t read worth a damn
https://i.gifer.com/3WXo.gif
Thanks for all you’re doing!