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.

Funny, Mastodon just posted a similar thing about creating a foundation. But the problem is, the existence of a foundation does nothing to prevent billionaires from controlling social media. For billionaires its very easy to donate a few hundred thousand USD to the foundation and gain influence that way. I expect that Bluesky will be fine for the first years (maybe like early Twitter), but sooner or later the foundation will take decisions that the users dont like, and there is nothing they can do about it.

In my view, the only way to avoid influence from billionaires is to avoid any large centralized structures. In the Fediverse there are dozens of platforms and thousands of instances. Even if a billionaire were to take control over a couple of projects or large instances, people would create forks in a matter of days. Some admins would block these corrupted instances, and their users would barely notice that anything changed.

So Bluesky is just trying to repeat something that has already failed. The Fediverse is the future, but it will take a long time for most people to understand that.

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.

For biggest protocol it’s also important to consider the number of instances. In that regard Activitypub is far ahead of everything else (Bluesky only consists of a single instance).

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.

Sounds like you are familiar with this topic. I dont have time to work more on this particular aspect (there are lots of other tasks like comment support, federation with Lemmy, etc). But contributions are definitely welcome, preferably directly to leptos_use so that others can benefit and its easier to maintain.

It uses the browser preference for light/dark theme by default. After you click the theme toggle on the site, it keeps using that chosen theme by storing it in a cookie.

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.

Seems unlikely, but maybe it will happen in many years if Ibis shows that its possible and desirable.

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