We're very busy but we'll get to it when we can.
load all comments
cmeerw 7 points 3 years ago
That said, WebSockets can be implemented very efficiently.
I agree, the main issue I was actually seeing with Lemmy's use of WebSockets was that when opening the main page it was continuously streaming all posts from the server (including posts in communities not subscribed to) to the browser client.
lemmy
@lemmy.ml
14708
1352
62
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
go to feed...
lemmy
@lemmy.ml
14708
1352
62
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
go to feed...
I appreciate all the work in this release. It's insane how much you packed into one release. Well done. I am most excited about the live updates going away. It was quite disruptive. Thanks for that.
That said, WebSockets can be implemented very efficiently. I run an open source notification service called ntfy, and the public instance ntfy.sh currently keeps 6-8k WebSocket connections and thousands more HTTP stream (long polling HTTP) open, all on a 2 core machine with 4GB of RAM. My point being that WebSockets can be implemented very efficiently. Though in Lemmy's case it's likely not necessary.
-- Another thing I wanted to notice is that I am missing mentions of security issues in the release notes. There are some tickets that sound really really really bad, like this one: https://github.com/LemmyNet/lemmy/issues/3060
Isn't that more important than anything else?
save