I think that when I am having link like https://lemmings.world/post/10530999 or knowing a title of the post, i can not discover in which community it has been posted… When I check same number of post on different instance: https://lemmy.ml/post/10530999 it does NOT work. Yet the search works: https://lemmy.ml/search?q=10530999 is there no other/easier way than opening one big instance after another (for example from the list https://lemmyverse.net/?order=posts&open=true ) and use search like that?

OF opinion: good not to be adicted to it or to anything actually.

Thanks, I see that the cross-posting works like this: “In order to cross post, I need to first create the post in one community, then after I create the post, I can click the two nested squares icon under the title of the post (with the pop-up text “cross post”) that shows up on mouse-over.” https://lemmy.world/post/354611

I guess You mean to create new mod rights request discussion topic inside the community, where i want mod rights (seems like an unsolicited way that pings and spends time of all members)

Regarding contacting instance admins in case community has no active mods, i assume i go to parent instance (in this case https://lemmy.ml/ ) and scroll down to see the list of “admins:” in the sidebar. I click one, it says “You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.” I am unsure how to follow ext. user via my home instance yet i have found this kind of URL: https://lemmings.world/u/username@external.instance (assuming my instance lemmings.world) and on it is a New message button that seems to be working. So it does not seems to be easy to contact custom external instance user who’s post i can not see on my instance. UPDATE: I can do it by using search icon and pasting: @username@external.instance (for the community, i use !community@external.instance) - this method is not apparent to a newbie

no, when i use ! like this: https://lemmings.world/c/!qbittorrent@lemmy.ml then it returns error “couldnt_find_community”