this post was submitted on 13 Jun 2023
27 points (100.0% liked)

Selfhosted

40445 readers
248 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
27
Articles on self-hosted servers not propagated? (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
14 comments fedilink hide all child comments
 

I set up a self-hosted instance yesterday, so far it runs fine. I can subscribe from there to communities hosted on other instances, I can comment from my instance and the comments show up on other instances.

However, I subscribed to https://lemmy.world/c/lemmyworldtest from my own instance to test if my posts will be propagated, and that seems not to work (yet?).

Is this a known problem? Would the upstream instance subscribe to my instance for this to work? Or is this a bug in my configuration?

top 12 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 1 year ago (1 children)

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

[–] [email protected] 4 points 1 year ago

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.

[–] [email protected] 4 points 1 year ago (1 children)

Sorry... I am not understanding fully, I think. So you want to see if posts on your self-hosted instance will propagate to other instances? In this case, only if someone on the other instance has searched for your community.

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)

You might want to link your self hosted instance so we can get a better sense of what’s going on here.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

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

[–] [email protected] 0 points 1 year ago (1 children)

Things don’t automatically propagate to other instances FYI. Someone from a remote instance would need to follow your community

[–] [email protected] 3 points 1 year ago (1 children)

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

[–] [email protected] 0 points 1 year ago (2 children)

Sure. But things don’t push to remote communities, it’s a pull system. So can you see the lemmy.world community you subscribed to from your instance?

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

pretty sure you webfinger resolve the community and it gives you an inbox for activitypub that you publish to. Everything is push, nothing is pull.

and i'm pretty sure that when the community receives the post, it then pushes it to all the subscribers.

[–] [email protected] 2 points 1 year ago

Hmm, I may need to freshen up my understanding of ActivityPub dynamics

[–] [email protected] 2 points 1 year ago

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...

load more comments
view more: next ›