After some debugging over the weekend and into this morning we finally have federation working as it should!
Now if you search for any community or user @mtgzone.com from another federated instance (Lemmy, Mastodon, or any app in the fediverse) you’ll be able to correctly follow it there.
For instance, if you have a Mastodon account at mastodon.social, you can login there and search for either https://mtgzone.com/c/mtg
or @mtg@mtgzone.com
and click to follow this community from your Mastodon timeline.
For the curious, ChappIO and @megan@sunny.garden in this GitHub issue finally solved this one.
I believe the Lemmy default is to allow federation anywhere, which is how it is here (no blocklists or allowlists).
Currently if you subscribe to non-MTG communities hosted elsewhere using your @mtgzone.com account, you’d see those subscriptions on your homepage here at mtgzone.com.
I’ve been thinking about this since we set it up over the weekend and I think that’s expected behavior and the most likely to help this grow. Users should be free to use their account to follow whatever they’re interested in, and while we host MTG-related content in our communities and will not expand the server outside of Magic content, that shouldn’t restrict users from using their account to follow what they want hosted elsewhere (and viewable in their account here).
The alternatives are:
For everyone to maintain multiple accounts (hisale@mtgzone.com for mtg content, hsiale@lemmy.ml for other stuff, etc). This seems untenable.
Not allow anyone to signup here for an account and require registration at other instances. This too seems counterintuitive and user-hostile.
Great point on beginner questions and setting up a general FAQ, I’ll try to draft something up with a bit of a angle towards people here and sticky it.