"Don't spend two seconds wording something clearly when publicly posting because everyone else can just figure out what you meant by inferring all of the context instead."

Sethayy

[–] sugar_in_your_tea@sh.itjust.works 6 points 1 year ago

Let's use an example from Reddit, just to eliminate the extra complication of instances.

Let's say I'm on /r/neutralnews on Reddit and I ask, "Does anyone know why HuffPost links aren't allowed?" Then imagine someone browsing /r/all sees the title then jumps in and comments, "But they are allowed, I just posted a HuffPost article yesterday!" The first poster is talking about something specific to the sub, whereas the second assumed they were talking about sitewide reddit rules. Should all posts discussing subreddit rules always include the subreddit name? That's ridiculous, it's quite obvious from context that it's talking about sub rules.

Now if we add in the complexity of instances on Lemmy, this post was made to a community that's specifically intended for discussing this instance. It's the main community for the sh.itjust.works instance, which is precisely where discussion about the instance itself should reside.

The root of the problem is addressed in this post where kbin apparently doesn't show enough information about the community and instance it's pulling. However, it still should have been obvious that, since it's a "main" community, it's talking about that particular instance. If you looked at the actual link this post is referring to, it also mentions the sh.itjust.works community. So I see two failures here:

kbin doesn't display the community name, only the short id
you didn't actually look at the linked post before commenting

The first totally isn't your fault, but the second doesn't imply that everyone else should include unnecessary data like the instance name in a post title that's made to a community that's specific to that instance.