Lemmy maintainer
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.
Not sure really.
If there are still problems you should open a new issue. We cant leave issues open forever because they go stale and dont account for new features. By the way we are planning to implement multi-communities.
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.
Maybe it’s different where you live, but in my country the covid pandemic has been over since at least two years.
Those stats are from some foreign country, completely irrelevant for me.
So 99 percent of the population is insane, alright.
No that is absolutely expected, but the pandemic has been over for a long time.
After so many years you are still wearing covid masks and doing tests? For me the last time I wore a mask was almost two years ago, and only because I visited another country where it was still mandatory.
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
Ah yes Im a liability to Lemmy which wouldnt even exist without my work. Troll harder kiddo.
Not sure, I just got back to work this week and need to catch up with everything.
The Lemmy backend doesnt treat this field as markdown, if you look at the Activitypub data (
curl -H "Accept: application/activity+json" https://lemmy.world/post/24241974 | jq
) the title is federated as plaintext. Only lemmy-ui decides to render it as markdown for some reason.