Lemmy maintainer
This is correct, the changes on main branch will be released as 0.20 because there are lots of breaking changes now. We sometimes backport commits to 0.19.x, but only for minor changes or bug fixes.
The post yes, but not the comments at depth > 50.
No the max comment depth is generally lower now. However this doesnt affect comments created before upgrading.
Changing post.url
from varchar(512) to varchar(2000) really messed up database performance so lemmy.ml became unusable. Turns out that column statistics are removed when the type is changed, so we had to run analyze
as part of the migration. Seems like a bug in postgres.
https://github.com/LemmyNet/lemmy/issues/4983#issuecomment-2446945046
Dont think I did, it was really a team effort. And in the end the working solution was suggested by @phiresky@lemmy.world, thanks for that!
It will be rejected by the api (or by federation).
In principle it’s finished, but last time we put it on lemmy.ml for testing there were performance problems and we had to revert. So far it’s not clear what caused those problems, so we need to try again somehow.
Just move the towel around randomly until Im halfway dry. Doesnt matter if there is some water left, it will dry soon enough.
Good reply, like you explain this wouldn’t work. Just one thing:
Lemmy doesn’t aim to be an uncensorable platform.
https://join-lemmy.org/docs/users/05-censorship-resistance.html
deleted by creator
Its not merged/deployed yet.
Second attempt, I removed lemmy.world from the blocklist and instead added some code to hide any instances with more than 30% of all active users.
Or even some logic to automatically exclude from the list any instance with more than x% of active users.
I posted about this in the admin chat on matrix, but you’re right the pull request was merged very quickly.
The lemmyverse link is also a good idea, but users only see it after filling in their email and password. At that point it’s unlikely that they would cancel it and go to a different website.
Edit: I’m now thinking to change the joinlemmy code so that any instance with more than x% of active users will automatically be hidden.
Right, I didn’t think how it would affect the total active user count. Will have to think of a solution for that.
Why don’t you post about these stories then?
@threelonmusketeers@sh.itjust.works This. If youre interested to work on this feature or others, feel free to ask for guidance in the relevant issue, or in the dev chat.
I wonder where they are taking this information from. This seems to be the cited European Union’s climate change monitoring service, but there is no such news item from July 8.
I can definitely say that this June was much colder than usual here in the north of Spain Spain. Lots of rain and low temperatures, it seems that summer is starting 1-2 months later than usual (similar to last year).
It’s like Blaze says, we are already working towards version 0.20 now which will have various breaking changes. There will be an announcement a while before the final release to let developers know about the changes. Also the current api v3 will still be available for backwards compatibility.