https://programming.dev/post/3666732
Change log for upcoming Lemmy version 0.19.0 I am just reposting this from the original post: https://lemmy.ml/post/5711722.
It’s interesting to see this for the software we’re all using and it makes me want to learn a bit more about the architecture. Quite a few user-facing features and some backend improvements. For example:
Outgoing Federation Queue The federation queue has been rewritten to be much more performant and reliable. This is irrelevant for client developers, but admins should look out for potential federation problems. If you run multiple Lemmy backends for horizontal scaling, be sure to read the updated documentation and set the new configuration parameters. The Troubleshooting section has information about how to find out the state of the federation queues.
You must log in or register to comment.
Time zones are an endless source of frustration, this one doesn’t sound too bad though:
Going forward, all timestamps in the API are switching from timestamps without time zone (
2023-09-27T12:29:59.113132) toISO8601timestamps (e.g.2023-10-29T15:10:51.557399+01:00orZsuffix). In order to be compatible with both 0.18 and 0.19, parse the timestamp asISO8601and add aZsuffix if it fails (for older versions).Yup, that makes total sense. Kind of surprising they didn’t have the TZ on there in the first place but it happens.
Well, time to post that Tom scott video again I guess.
Here is an alternative Piped link(s):
https://www.youtube.com/watch?v=-5wpm-gesOY&t=6
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
Neat. IIRC lemmy.world is running a ton of backends in parallel for performance, nice to see that it’s been taken into consideration by the devs 😁
Agreed. My copy lost this documentation link in the original which gives more detail about the horizontal scaling: https://join-lemmy.org/docs/administration/horizontal_scaling.html.
It seems really straightforward (which is a good thing), each backend Lemmy_server handles incoming requests and also pulls from a shared queue of other federation work.
