True. I am considering getting a retirement residency somewhere near Bremen, to have a nice beach with Coconut trees at the North Sea beach... (Still ~20 years to go till retirement, if I plant coconut trees now, they might thrive by the time I retire)

As much as I dislike US hegemony and think they need other powers to limit their powers, I'd not want it exchanged for a Chinese or (haha) Russian hegemony. And while it is purely for selfish reasons, I'm pretty sure the US would actually defend the Philippines in case China got too ambitious in that region.

Didn't Trump try to throw his previous lawyers under the bus by getting them to provide wrong confirmation? Weren't they only saved from being liable themselves because communication acquired by the FBI proved they were mislead themselves?

Well, actions have consequences, even if it took waaaay too long in this case. I mean, even if he's sentenced for life, how long will that be?

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 :-)

Sure. But things don’t push to remote communities, it’s a pull system.

I understand that I complete communities are not pushed, but for articles this seems counter-intuitive:

1. My comments to remote posts are automatically replicated, so it is not only pull

2. What's the point of subscribing to a remote community via my server if the articles I post to that remote community are not pushed? My own instance is basically useless if questions to e.g. support-communities remain only on my own instance and I have to create an account on the remote instance in order to actually interact with that community.

So can you see the lemmy.world community you subscribed to from your instance?

Yes, although the comments to this article, for example, are still not replicated. But it seems comments are slowly arriving on my server...

I get that, but it is not my community. It's the community on lemmy.world, to which I subscribed.

Ok, here is a link to the community replicated to my own server: EDIT: https://lemmy.pathoris.de/c/[email protected]

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.

Reddit SysAdmin can protest too, no?

Not legally by sabotaging the infrastructure they are supposed to run, I expect.

But accidents happen, of course...

Seems the lemmy-container was supposed to use nginx as a reverse proxy to reach other servers, but for some reason that didn't work. I added

lemmy:
    ....
    networks:
        ....
        - lemmyexternalproxy

Now it works... I assume there should be a better option for me to fix it, maybe something in the nginx.conf or so?

I saw the same issue, but would like to provide some additional information (for my case): I searched for https://lemmy.world/c/mildlyinfuriating on my instance. According to https://join-lemmy.org/docs/en/administration/federation_getting_started.html, my expectation was I'll see the community within a couple of seconds.

My lemmy-log shows

> lemmy_1 | 2023-06-12T15:14:49.089405Z ERROR HTTP request{http.method=GET http.scheme="http" http.host=lemmy.pathoris.de http.target=/api/v3/ws otel.kind="server" request_id=7c0dd0ef-2766-4e69-b9de-53d1459556ff http.status_code=101 otel.status_code="OK"}: lemmy_server::api_routes_websocket: couldnt_find_object: Request error: error sending request for url (https://lemmy.world/c/mildlyinfuriating): error trying to connect: dns error: failed to lookup address information: Try again

My setup is based on docker-compose, https://join-lemmy.org/docs/en/administration/install_docker.html

Any ideas?

EDIT: It might be Centos 7 issue with default configuration or something I did in the past :-( I connected to lemmy_1 via docker exec and wasn't able to initiate any outgoing connection from within the container. Seems I'm filtering it somewhere.