![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/1e752249-fae3-4e01-9c47-fc57c3e8a489.png)
The setting is tied to your instance account, because the backend delivers the results with the specified sorting. If you change it via the browser, it should be reflected in Jerboa.
The setting is tied to your instance account, because the backend delivers the results with the specified sorting. If you change it via the browser, it should be reflected in Jerboa.
You mean a version later than 0.0.34alpha? Sorry, maybe I’m blind, I can’t find it. Could you post the direct link?
Since account creation does not happen in the app, but requires visiting the instance’s home page, where registration requirements, federation status and other peculiarities are plainly visible, I don’t think this belongs in the app.
I read somewhere that this is just an artifact of the “ban” event being propagated, basically as a “FYI”, but essentially meaningless for your instance, because those remote accounts could only log in on their home instance and interact with yours from there anyway.
It’s not ideal that this clutters the list of the banned users on your instance though.
I believe any two posts linking to the same URL are treated as a cross-post, and that is discovered at instance-level. There’s nothing more to it than creating two posts in different communities with the same link.
ETA: But to answer your question directly, there’s no support for doing that as a single action with Jerboa yet.
src: https://github.com/LemmyNet/lemmy/blob/63d3759c481ff2d7594d391ae86e881e2aeca56d/crates/api_common/src/post.rs#L61