When you view the global post listing from all communities, it shouldnt display posts in languages that you dont speak. Similarly it shouldnt be possible to make a post in Danish or Polish in a German community. With Lemmy 1.0 there will be automatic language detection available so you wont have to specify it manually for each comment. And translations could be implemented using Libretranslate (selfhosted).

Of course its possible, afaik Piefed uses Libretranslate for this. So the same would work for Lemmy, someone just needs to find the time to implement it.

What you should do as a mod is set the allowed languages in the community settings. Then people wont be able to post in other languages. Though I realize that the UI for this isnt so good for now.

This will come with Lemmy 1.0

In theory apps can do anything that the website can, but this app probably hasnt implemented the feature yet.

You are using Piefed but this community is only for help with Lemmy.

This is a problem with your instance (lemmy.org) so you will have to contact the admin.

These logs are from the api, not from federation. So a client is trying to access posts and comments which dont exist. Is the Lemmy frontpage looking normal? Regarding federation, other instances would have marked your instance as dead by now. This should be reset automatically after a few days, or you can manually trigger it (eg unfollow and refollow remote communities).

I would also suggest you join the admin chat on Matrix to get more help: https://matrix.to/#/#lemmy-support-general:discuss.online

It seems that the post is getting refetched over federation and marked as deleted again. So you will have to run that SQL query regularly (eg in a cronjob) to restore the post every time. Its also worth setting locked = true to prevent users from commenting.

By the way I opened an issue to fix this properly: https://github.com/LemmyNet/lemmy/issues/6044

You can run the SQL command update post where id = 53505862 set deleted = false. That way it will be visible on db0 again, although not on other instances.

Adding a new sort type is not a big deal, so dont worry about it. And a new admin setting for this would also require UI changes, so the new sort type is easier overall.

The current sort options calculate the rank for each post only from the data on that post (number of votes, creation time). Your suggested algorithm looks much more complicated than that, as it requires two iterations and needs to access data from multiple posts at once. Im not sure if this can really be implemented in a way thats performant enough for production use. Anyway feel free to open a pull request, then hopefully other contributors can help you to get it working.

Sounds interesting, though from your links it’s not clear to me how exactly it works. Depending on that it could make more sense to implement as a separate sort option, then each user could try and compare it to the existing sorts.

The proxied images will be refetched from the origin if they cant be found locally. There should also be a configurable maximum size for the image cache but I dont see it mentioned in the pictrs readme. So like Dessalines said you need to ask the developer directly.

The ranking is implemented in a rather complicated way for performance reasons:

• First there are SQL functions which calculate the rank for a specific post or comment (defined here)
• These SQL functions are used by a scheduled task which updates post ranks at a regular interval (defined here)
• Then there are the database tables which store the calculated rank (eg post.hot_rank)
• Also the API parameters to specify the requested sort, and preferences for default sort options etc
• These params are used in the post listing db query to sort posts by the given rank field (here)

The “Chat” option does just that, with newest comments at the top.

This feature is already implemented for Lemmy and will be in version 1.0

Its the first time Im hearing about this problem. If no one reports it on the issue tracker we cant fix it.

Edit: You can block a community that banned you under /settings, but not directly on the community page. Issue link

Localization is done through our Weblate. Theres also an open issue to let admins add extra email text: https://github.com/LemmyNet/lemmy/issues/5612

User profiles are only updated every 24 hours so that is normal. The url parsing is handled in lemmy-ui, you can check the issue tracker or open a pull request.

Tested it on https://enterprise.lemmy.ml/c/test and changes to the community name are visible immediately.