Lemmy maintainer
- 105 Posts
- 676 Comments
3·24 天前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_useso 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.
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.
5·2 个月前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.
3·2 个月前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.
2·2 个月前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.urlfrom 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 runanalyzeas 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 @[email protected], thanks for that!
It will be rejected by the api (or by federation).
The average peasant in medieval Europe would certainly never see an African person in his lifetime.
Some people get faith and hope from Christianity. Or Islam, or Buddhistm or others. Nothing wrong with that.
Maybe there never was a real Jesus.
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.