Btw: The settings I changed on my server were removing all servers from the “allowed” list. It seems I misunderstood the instructions during setup, I thought I had to add some servers quasi as a seed. But actually, by giving permission to certain servers, it is implied that I don’t want to allow any other.

Ok… After changing some settings, I got this log:

2023-06-13T15:16:56.808411Z ERROR HTTP request{http.method=GET http.scheme="http" http.host=lemmy.pathoris.de http.target=/api/v3/ws otel.kind="server" request_id=6603f30f-4523-4548-a82c-f38c22d1889f http.status_code=101 otel.status_code="OK"}: lemmy_server::api_routes_websocket: only_mods_can_post_in_community: only_mods_can_post_in_community

That explains a lot, I think :-)

Apparently my instance does try to push, as I expected, but the community is protected on lemmy.world. That’s a bit surprising still, since I thought it is a test group to test federation and such, but since that wasn’t specified anywhere, it’s fair enough that this could be a test-group by lemmy.world for lemmy.world :-)

Ok, here is a link to the community replicated to my own server: EDIT: https://lemmy.pathoris.de/c/lemmyworldtest@lemmy.world

It’s the first test for you job-application :-)

The community is originally from lemmy.world, I subscribed on my own instance. In my example it was just “lemmyworldtest”, but a proper use-case would be to subscribe to https://lemmy.world/c/techsupport on my own instance and post an article to that community. Since the community has its home on lemmy.world, I would expect/need my post to be visible there in order to actually receive some support.

Also, at the time I’m writing this, your comment to my post is not yet visible on my own instance although I’m subscribed there as well.