Yes, you can test it yourself by registering an account on voyager.lemmy.ml with the sidebar button (direct link). There are also lots of other new features available, I really need to write a post about them. To name just a few: private communities (followers require mod approval), webassembly plugins, post tags (ui is not finished yet), and more…

lemmy.ml fits those criteria.

This is a known issue and will be fixed in Lemmy 1.0: https://github.com/LemmyNet/lemmy/issues/5210

The best channel is through the issue tracker, for example github.com/LemmyNet/lemmy-ui. In practice Im not sure how the UI could be changed to make this clearer. Do you have an idea, or an example how another website handles this?

I had a video chat with them once, but afterwards they ignored me. So they are clearly not interested in giving us a grant.

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

Good point, this is one of those features which is already implemented in the backend but not added to lemmy-ui yet. Made a pull request for it.

https://github.com/LemmyNet/lemmy-ui/pull/3220/files

Lemmy has an open API, and instance admins have even more data available by accessing the database directly. One of the lemmy.world admins is also working on a feature for vote analytics, though at Lemmy’s current size it seems very low priority.

I thought about that too, have to figure out how it can be implemented (im not very good at frontend stuff).

No worries. Make sure to follow the documentation on join-lemmy.org for development, and use the release/v0.19 branch for both lemmy and lemmy-ui as the main branch is currently broken due to 1.0 changes.

Makes sense. My idea is to use a fixed order for the different types of results, eg always put communities first, then users etc. What do you think? For communities it would make sense to display the short description as well, and for users both post and comment count?

https://github.com/LemmyNet/lemmy-ui/pull/3219

The tabs could make sense, but then they should be between the search bar and results, because each tab has the same buttons. You can make a pull request with what you have so far and then we can discuss it in detail.

Right, this is because it currently uses two separate api calls for search and resolve object. It will be fixed in 1.0 with https://github.com/LemmyNet/lemmy/pull/5752.