Just remember to also always post !community@instance, because the link will only work after one other person from your instance subscribed. That’s especially relevant for a community called “New Communities”, but also generally for people who are on smaller instances (the one I’m on has only 1,466 users).
This allows users to hand-copy the visible link to discover the community in their search. Or to click it and view the community from their home instance (while remaining logged in).
Are there any downsides to this, or better approaches?
It probably works well enough, I like it on its own line, so I can double-click the text to highlight (which would open the link here), but that’s complaining on a high level ;)
I went out of my way to have everything, see my post here, even a direct link to the search via [Experimental direct search](/search/q/!folkmetal%40discuss.tchncs.de/type/All/sort/TopAll/listing_type/All/community_id/0/creator_id/0/page/1), though I don’t know if that properly works across instances.
First and last are only the same if you are also on tchncs ;) the first is the local link you asked for.
Kbin: I registered there first because of the better UI, then switched to tchncs mainly after they got overloaded. That’s why I even knew about the search difference.
Experimental: because I’ve not seen anyone else use it and thought there must be a reason :D
And I assume eventually, something like this will be automatic. Or rather, federated community links will just work and not throw a 404.
Just remember to also always post
!community@instance, because the link will only work after one other person from your instance subscribed. That’s especially relevant for a community called “New Communities”, but also generally for people who are on smaller instances (the one I’m on has only 1,466 users).Okay I will then. But what’s the difference? And why so many linking methods?
It’s one of the many small papercuts from federation and the software just being not that polished, yet.
I like to combine both. Example:
!lemmytips@discuss.tchncs.de
I wrote: [!lemmytips@discuss.tchncs.de](/c/lemmytips@discuss.tchncs.de)
This allows users to hand-copy the visible link to discover the community in their search. Or to click it and view the community from their home instance (while remaining logged in).
Are there any downsides to this, or better approaches?
It probably works well enough, I like it on its own line, so I can double-click the text to highlight (which would open the link here), but that’s complaining on a high level ;)
I went out of my way to have everything, see my post here, even a direct link to the search via
[Experimental direct search](/search/q/!folkmetal%40discuss.tchncs.de/type/All/sort/TopAll/listing_type/All/community_id/0/creator_id/0/page/1), though I don’t know if that properly works across instances.Ah, you’re right! I think that’s a valuable objection.
That is exemplary, thank you!
What’s the difference between the first and last line? What use case would prefer the first, what’s the advantage of the second? https://discuss.tchncs.de/c/folkmetal@discuss.tchncs.de vs https://discuss.tchncs.de/c/folkmetal
I found it interesting to see kbin included. Will try to do that in the future.
I suggest to include an instance-independent link: folkmetal as seen from your instance
THAT is AMAZING! Worked like a charm for me, community auto discovered. Why experimental, any downsides or reported misbehaviours?
Now I wish we had a lightweight tool.
Input: A link in any format.
Output: Each possibly useful variation. Can be individually copied, or the whole as a preformatted block.
Ultimately, I wish this was somehow incorporated in the fediverse so we don’t have to make/understand it manually.
First and last are only the same if you are also on tchncs ;) the first is the local link you asked for.
Kbin: I registered there first because of the better UI, then switched to tchncs mainly after they got overloaded. That’s why I even knew about the search difference.
Experimental: because I’ve not seen anyone else use it and thought there must be a reason :D
And I assume eventually, something like this will be automatic. Or rather, federated community links will just work and not throw a 404.