This is rather frustrating for me. I was corrected on a different post when I used @community@instance and told to use !community@instance. Now I’m being told I got it wrong again. Not angry at you, just angry that I got it wrong twice.

I was told to use !community@instance because it would leave people able to browse and subscribe to the community through their own instance instead of being kicked to a different URL (e.g. !community@instance lets you browse and subscribe from @instance, while @magazine kicks you to the instance.com website), so that’s what I’m using here. I am currently under the impression that viewing from your own instance also means you won’t see any content unless someone on your instance has subscribed to that community before, as an intentional part of how the Fediverse works; while going to the instance.com website directly will show you everything. That’s probably why my links send kbin users to a search result: because on kbin, from the search result you can click and look at the instance or subscribe without ever leaving your own instance.

When you say the correct way to link a magazine is @community@instance for kbin, do you mean I should do it that way for links that point to a kbin instance, or is that how I have to format links to any instance at all (whether lemmy or kbin or even something else like Mastodon) for it to work properly for kbin users? Or is this just about wishing that I sent you to the instance’s website with all the content instead of somewhere you can view through your own instance? If it’s the latter, I’m really not sure what the etiquette is for what I’m supposed to send you to: your own instance or the source instance, seeing as I am getting corrected about this here to use @community@instance for you but was previously told to use !community@instance.

Once people stop commenting with new communities I can comment the list with links formatted as @community@instance.