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.

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.

What you list as disadvantages are exactly the main benefits of a federated wiki. For a contentious subject which can be interpreted in multiple ways, there should be multiple different articles which present these views. It can be possible to represent other viewpoints if they share a common root, but as soon as there is a fundamentally different understanding that breaks down.

Additionally, even a very large encyclopedia like Wikipedia cannot include all topics that users want to write about. For example when it comes to TV series, books or details about small places, it often doesnt meet the notability requirements and gets removed. So for these topics people need to use entirely separate platforms like Fandom (which are full of advertising). Ibis can allow all these topics to be present in a single network, accessible from a single user interface.

You can get the raw article text from fandom by clicking the edit button. Then you need to convert it from wikitext to markdown, there are various tools for that. Finally post it on Ibis. Fandom also has an API, so you could write a script to automate all this.

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.

@Blaze@feddit.org

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.

If you install with ansible it should be included by default. You can check if your nginx config contains the cache lines. There is also a line you can uncomment to see the cache status with each request.

https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx.conf#L71

Did you try to setup caching? That could reduce server load a lot.

https://github.com/LemmyNet/lemmy-ansible/issues/195

This would be neat to generate forum avatars, to show something similar to your real face.

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).

With pleasure :)

You’re welcome :)

What a shame, I spent a lot of time working on syncthing-android (probably around four years). But in the end I stopped for the same reason, it’s very demotivating to be so reliant on a corporation like Google which is entirely indifferent or even hostile to open source apps. Every year with the new Android version there are new required features or mandatory changes to implement, and if you don’t comply they don’t allow publishing new app versions. That’s not a big deal for commercial apps with fulltime developers, but it’s a lot of work for small apps maintained by volunteers. And it’s never anything that would benefit syncthing-android or it’s users, just busywork that takes away from bug fixes and feature development.

The good thing about open source is that someone else can always pickup and continue the work. Google’s shenanigans were what drove me to server administration and backend development, which finally led me to work on Lemmy. The experience with syncthing-android definitely taught me a lot about how to run a popular open source project.

Thank you, fixed!

Pictrs is only made for images (and videos), as the name implies. Supporting other types of files in pictrs wouldnt make much sense. This means that other file types would have to be stored by a different backend tool, or directly in Lemmy. As we are only two fulltime developers on Lemmy, we dont have the time or resources to work on this, and need to focus on the most popular features.

There is no way for admins or mods to modify user comments or impersonate users, except directly through the db which is unavoidable.

We had a very long discussion recently how vote privacy should be handled, and the current behaviour seems to be the best compromise.

Multi-communities is one of those popular features we are going to implement soon.