- cross-posted to:
- lemmy@lemmy.ml
- cross-posted to:
- lemmy@lemmy.ml
Its been a hectic week everyone, so I apologize that I haven’t been as responsive as usual. We realized that we could either spend all our day answering questions, or coding to make lemmy better, so we’re prioritizing the latter.
Reddit caught us right in the middle of one of our larger performance improvements, so I apologize for the instability of instances like this one. But I’m confident that lemmy will improve, especially due to all the new contributors helping out with performance, security fixes, and stability.
Please use our the issue trackers for the various lemmy projects to report issues, otherwise they will likely get lost.
Call for testers
- You can help us test patch releases like this one at https://enterprise.lemmy.ml
- We’re readying the
0.18.0release soon, you can help us test at https://voyager.lemmy.ml , and https://ds9.lemmy.ml- App devs should use voyager.lemmy.ml to test and prepare for
0.18.0, which should come in the next few weeks. The API changes and new types can be seen here. 0.18.0should give servers a big performance boost by removing websockets and switching entirely to HTTP. It also will add a lot of features like 2fa / TOTP.
- App devs should use voyager.lemmy.ml to test and prepare for
By “switching entirely to HTTP”, do you mean Server-Sent Events, or do you mean polling? I havent tried 0.18.0 yet, but in general polling can end up using far more resources unless you’re doing something clever like passing the last update timestamp to the server and only querying the DB for new content since that timestamp (and timestamps are indexed in the DB).