Hello, I would like to test if communities behave differently from regular groups on the Mastodon side, since they have a moderator and regular groups don’t. I will post a reply and ask a moderator to remove it to see if something happens on the Mastodon view of this thread.
Picture is a picrew by Gyadam/그야담 , for funsies.
@Berin@discuss.tchncs.de @Berin@mastodon.social
I’ve just removed your comment as requested
Thank you! Unfortunately, somehow this post didn’t show up on the community’s group account at all for some reason (even though older threads from about a week ago do show up normally), so I couldn’t make any observations😔 I tried it again on !test_posts@reddthat.com, and so far the thread shows up alright, so I guess I’ll continue my test over there
Edit: Now that I’m looking more closely, actually, this community doesn’t seem to be a group at all! It should have a “Group” tag in its profile. 🤔 !test_posts@reddthat.com seems to be a proper group however, maybe that’s why it behaves differently?
Hmmm, cross-referencing the joined date in your screenshot, it seems to be showing the test user and not the test community.
… :0 Huh, that’s interesting. Functionally, I don’t think there’s a way to differentiate between groups/communities and users on Mastodon. You should be able to search up the community by using its full URL (in this case https://sh.itjust.works/c/test), then it should point you to the corresponding group account. But it doesn’t show up when I try. That’s why I searched for the username directly. It also very weird that the user seems to be boosting threads and comments as a group would.
It’s not a problem with the instance either, I can search and find other communities on this instance that way just fine. Looks like a bug to me? And not a Mastodon-exclusive one, on my side-account on goblin.band I get the same behaviour.
Maybe it depends which federated first initially (user vs community)