Some of those are automatic, such as Calendar, Connections, Directory, Files, and Photos. And those others just clutter up their interface if they are not going to use it.
Virtually all of my users need webpages, even if they don’t know it yet.
And freakin' ActivityPub??? I can't even begin to understand why this core functionality of Hubzilla isn't part of the default config.
Given that #Hubzilla's major hurdle is "more users" not "can I move to another server" this seems like a poor marketing choice.
Getting people in is more important than being able for any of them to move seamlessly once they're in.
If we compare the growth of Mastodon and the growth of Hubzilla, I think it's fair to say that Hubzilla hasn't made any good marketing choices.
cloneChannels can have clones associated with separate and otherwise unrelated accounts on independent hubs. Communications shared with a channel are synchronized among the channel clones, allowing a channel to send and receive messages and access shared content from multiple hubs. This provides resilience against network and hardware failures, which can be a significant problem for self-hosted or limited-resource web servers. Cloning allows you to completely move a channel from one hub to another, taking your data and connections with you. See nomadic identity.
Cloning allows you to completely move a channel from one hub to another, taking your data and connections with you. See nomadic identity.
Space needed for channel XY
if you backported the relevant work on this feature from Zap, the additional documentation probably not be necessary.