Selfhosted

39435 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Lemmy - Increasing Federation (lemmi.social)

submitted 1 year ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

I’m hosting my own Lemmy instance and so far everything has been pretty smooth. However I’m noticing some issues with specific instances, communities, or comments not showing up through my own instance.

I had added instances to the allow list initially but I cleared those so that it’s wide open now. I have an account on lemm.ee and I use that periodically to compare feeds, and like I said sometimes a post or comment is missing, actually I often see a comment that looks like it’s responding to a another comment, but I cannot see the parent comment.

Initially I took my admin account and subscribed to all of the most popular communities I could find, but that seems to have left some holes.

Is there a way to force federation with more Lemmy instances?

Thank you for any direction you can provide.

you are viewing a single comment's thread
view the rest of the comments

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

Fwiw, federation is known to be relatively unreliable at the moment. https://github.com/LemmyNet/lemmy/issues/3101 is marked as closed, but it seems pretty clear to me that many of these behaviors persist in 0.18.3. There may well have been improvements, but we haven't yet achieved full resolution of these things.