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
I believe making the value "Space needed for channel XY" available to a channel owner,
Guidance that prevents the user from neglecting the relevant steps you mention.
if you backported the relevant work on this feature from Zap, the additional documentation probably not be necessary.
I would be grateful if someone (@mike ?) explains to me, describes with other words what is meant by backporting in this context.
1) Group123 in my Connections2) AND !OneForumChannel