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.

Showing crossposts below comments doesnt work if you have a thread with 100+ comments as it keeps auto-loading more comments. Hiding the crosspost details themselves seems unnecessary as we render them rather small. A button to expand these small details into the full post view with comments also makes sense to me.

Read posts already show with a different color. So this could be a problem with your browser, or the specific Lemmy theme you are using.

Looks similar to the new UI in the PR linked above, except you have to expand it manually.

Just noticed that this post is already two weeks old. Im aware of the other discussion, there are a lot of ideas and we still need to decide what is the best way to implement it.

Could you post a link or screenshot to see how Photon displays crossposts?

I implemented this recently: https://github.com/LemmyNet/lemmy-ui/pull/3387

Outgoing federation actions are kept for 7 days. So if your instance is down shorter than that it will catch up with everything.

This is not possible unless you are an instance admin and query the database directly with sql.

curl -H 'Accept: application/activity+json' https://piefed.europe.pub/post/35873 | jq

This directly sends the object json for https://lemmy.dbzer0.com/post/53225502 which fails domain validation. Instead https://piefed.europe.pub/post/35873 needs to send a redirect to https://lemmy.dbzer0.com/post/53225502

So far this is not possible. What you can do is embed external images with ![](). In the future it would be possible to add the same image upload functionality that Lemmy has. However I dont have much time to work on Ibis, because it has so few users and few donations compared to Lemmy.

These types of changes are rather annoying because you need to edit the file, wait about an hour for the release build to finish, then fix any problems and repeat until it works. Though its definitely good to have multiple platforms for releases.

So if you want to make a PR and get it working you are welcome to do that. Then I will add the auth token so you can test it. Github seems preferable as we already use that.

Thats doable with our CI tools (docs). Would you open an issue?

Thank you :)

Thanks!

By the way you can now try the development version of 1.0 on voyager.lemmy.ml.

Let’s also not forget that for years Lemmy had a built-in, activated by default slur filter impacting all users, still nobody made a fuss about it, admins just disabled it and called it a day.

Lots of people made a fuss about it, which is the reason we eventually removed it from the defaults.