> [@strypey@mastodon.nzoss.nz](https://activitypub.space/user/strypey%40mastodon.nzoss.nz) [said](https://activitypub.space/post/https%3A%2F%2Fmastodon.nzoss.nz%2Fusers%2Fstrypey%2Fstatuses%2F116071781202626645):
-
> @strypey@mastodon.nzoss.nz said:
>
> We could instead try to agree on a separate place for all discussions about fediverse coordination (would it rub anyone up the wrong way if I described this as fediverse governance?). But it does makes sense to discuss a federated network in a federated network, rather than a separate, centralised forum.I keep harping on this one point because it just makes so much sense that it'd be silly not to. The new blood (new software devs implementing AP) always appear on fedi, not some third-party site, first.
To your main point, fedi on Mastodon is all just everybody talking in the same room. Certainly that's why it seems like there's so much meta-discussion about AP.
This isn't the case on the threadiverse, where discussions are segregated/categorized by community.
-
Right, which ActivityPub.Space follows and auto categorizes, which ends up as a way for microblog content to make its way into the threadiverse. @strypey@mastodon.nzoss.nz
@silverpill@mitra.social sorry for interjecting

-
@strypey@mastodon.nzoss.nz is that true, though? Mastodon doesn't segregate topics by interest group or community because that's a UX decision by Mastodon. It's a wilful ignorance of explicit categorization by design.
Now, I want to be very explicit here that I'm not saying this is a bad thing. Mastodon doesn't have any major incentive to implement groups, much less implement them like the threadiverse does.
But it is by design that it's all lumped together into a singular feed.
-
@strypey@mastodon.nzoss.nz I disagree, I view the content not as a function of its lowest common denominator (the singular note adrift in a sea of other notes), but as a part of a larger entity, the thread, or a category/community.
That microblogs are incapable of realizing that is a design decision on their part

-
R relay@relay.an.exchange shared this topic on