First of all, sorry if this magazine is not the correct place for such questions.
I “migrated” my small community over from kbin.social since, well, it’s dead. The community is Greece (https://fedia.io/m/Greece) and users from other instances such as lemmy.world etc don’t seem able to see any of my posts.
For example: https://lemmy.world/c/[email protected]
Any ideas for this?
You generally seem to need to have at least 1 account from that instance subscribed to your magazine for federation to kick in (which then still can take a bit of time). Same works the other way around. The unfortunate thing is that you kinda have to use external community / magazine indexers to search for them, unless you know the exact name & instance domain they’re in, since a search won’t find non indexed ones by itself.
Imo one of the largest issues regarding the fediverse.
Yeah, I hope it gets “fixed” at some point (“fixed” because I guess it is by design). For now, I created an account to most large Lemmy servers and subscribed to the magazine so future users find a fuller community :P
Language setting?
Could you elaborate a bit?
I was wondering if the language settings in a user’s profile meant that they cannot see your posts. I enabled Greek but it doesn’t seem to have made any difference.
I think the language settings only changes what you see in your main feed, and not the community feed. Though I may be wrong…
Hopefully @jerry could help us undestand the issue!
So, I created a lemmy.world account just to subscribe and check if the federation now works. It works, but only for new posts, which is not ideal either. Hopefully federation can be fixed for older posts as well (I know that comments need someone from your instance to have subscribed to that community, but posts should always be visible to others)
I subscribed to [email protected] just now (using Voyager). I’ll let you know if I see any posts.
Which lemmy instance were you not seeing it on? One of the challenges with all fediverse applications (mbin, lemmy, mastodon, etc) is that posts and comments don’t federate with other instances unless someone on the other instance follows the person or the magazine.
I do not believe existing posts and comments will federate to a different instance after someone on that instance subscribes to the magazine. Only new posts and comments will.
@[email protected] like you, after subscribing I only see new posts.
I see. Too bad, but hopefully this is something that may get fixed in a future ActivityPub protocol update (don’t know if it is sth the applications can fix themselves)