The various observations @trwnh makes are spot on.
“Scattered to the winds” is also my observation. Anyone noted the new HTTP Signatures proposal to the ActivityPub community? Maybe by coincidence or by having a good ‘following’ collection. Or maybe because I created a cross-reference as a commons janitor. It means now at least there’s archive that it happened, though the content of the discussion may already be gone, link-rotted as happens on microblog timelines.
What does it mean to be federated as a forum? That is what I mused about in the fragmentation discussion, and I formulated a Need:
Support the communication and cocreation of all participants in the ActivityPub ecosystem to help foster healthy growth and evolution of the Fediverse.
Note there is not the word “community” here. It is the vaguest term when it is just dropped casually. What is the “FOSS community” for instance? I claim it doesn’t exist unless you use “community” in most handwavy terms. Long ago as facilitator I came to the conclusion that SocialHub was not a community, but just a discussion forum. And that though that is a shame, that still is valuable. These discussions are in the archives of this forum. 
What should we do?
In order to be able to talk about “community” it has to be well defined what that entails ..
-
Collect problems that hold the AP dev community back from collaborating and evolve the foundational technologies that the dev ecosystem of the fediverse relies on.
-
Collect the challenges SocialHub faces to address these problems.
-
Refine the Need above, breakdown into more granular needs and find other requirements for a prolongation of SocialHub on a healthy trajectory.
-
Let people and groups thereof, like @strypey before (please boost his call to action), step up and announce themselves
-
I propose everyone to step up to prepare a Community Plan consisting of ..
- Wiki post (such that it bumps the list upon edits) with a summary of the plan.
- Separate discussion topic referenced from the wiki post, to discuss details of the plan.
Objective: Convince @how that responsible custodianship is taken care of, and it is responsible to hand over these tasks to the new community custodians.
Listing some needs and requirements that SocialHub always had, or for a long time already ..
- Reach the AP dev community, connect people for focused discussion.
- Provide insight in ongoing discussions such that others can chime in in real-time.
- Keep record and archive that can be searched, quoted and cross-referenced.
- Provide entry point to the ecosystem where newcomers can discover, onboard themselves.
- Become native to the fediverse. SocialHub is to be part of the fediverse via federation.
- Help guarantee a bottom-up (commons based), open and decentralized ecosystem.
- Be a helpful tool to allow the FEP Process to fulfill its custodianship role for FEP’s.
On diversity @jdp23 I would add that point 5 equates to the diversity of the fediverse itself (iff ‘federation-done-well’) and that point 6 acknowledges the need for a decentralized developer environment, where there can be many independent dev hubs furthering AS/AP et al. This notion promotes diversity in itself, and SocialHub in this setup does not take an authoritative position nor gatekeeper position.
The diversity problem + challenges then boil down to 1) the diversity that the microbloggoverse fedi and its moderation processes gives, and 2) how forum federation / threadiverse is able to forge community on top of that (as a well-defined concept) using the fediverse social graph where ecosystem participants and prospects (newcomer onboarding) engage.
And that brings this to a mighty interesting applied research area, on the basis of which alone a SocialHub reboot might be a very worthy undertaking. As mentioned above both @strypey and me in that fragmentation discussion were wondering:
What does it mean when we say that a Discussion forum has become “part of the fediverse”?
If I might give this a shot to formulate a definition ..
Federated discussion forums are like collaborative gardening centers where a group of fedizens gathers together around a theme and fosters a curated garden of relevant information and connections to other groups and people to interact with, have insightful discussions and deepen relationships, and to enrich the collective knowledge base together.
From a more technical perspective you might consider Federated discussion forum software to constitute a collaborative / multi-user ActivityPub client with dedicated management features for content curation, aggregation and moderation.