-

Fri, 24 Sep 2021 13:32:55 +0200

adminsforum@hubzilla.org

neue medienordnung plus wrote the following post Fri, 24 Sep 2021 13:32:53 +0200

Channel cloning

In the Hubzilla help you can read:

clone
Channels 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.

Where can I look up what data is imported when importing channel X on hub Y? What are the requirements for cloning a channel X to clone the articles published on that channel? Is it even possible to clone the articles published on the channel? Surely the "Articles" app is not yet installed at the time when channel X is imported on hub Y?

#ChannelCloning #cloning #HubzillaCloning #HubzillaHilfe #NomadicIdentity

show all 4 comments

Sun, 26 Sep 2021 09:36:51 +0200

neue medienordnung plus

nmoplus@realtime.fyi

@mike Can you specify what the content_import addon step requires a Hubzilla user, who is not an admin, on the target hub to do? Can you specify what the content_import addon step requires a Hubzilla admin, on the target hub to do? For a Hubzilla novice, who is correctly warned frequently "Channel clones are important to the availability of your Hubzilla identity!" it would be very helpful to have robust export-import instructions in hand as part of the Hubzilla documentation. Guidance that prevents the user from neglecting the relevant steps you mention. As of now, I don't know which steps specifically.

I searched the Hubzilla doc with the search terms "export" and "import" and unfortunately didn't find anything that matched. Helpful for the Hubzilla users who are not Hubzilla admins, if they had the possibility to determine before the import, how much storage space the channel XY needs on the target hub. And perfect would be, if before the import the Hubzilla engine would warn the user "There is not enough space available for channel XY on the target hub".

I believe making the value "Space needed for channel XY" available to a channel owner, who is not a Hubzilla admin is critical in determining whether potential Hubzilla users can take advantage of Hubzilla benefits. And it is crucial whether potential Hubzilla users can use Hubzilla productively.

Mon, 27 Sep 2021 17:11:07 +0200

neue medienordnung plus

nmoplus@realtime.fyi

To understand the meaning of this statement

if you backported the relevant work on this feature from Zap, the additional documentation probably not be necessary.

to derive practical recommendations for action from this statement, I would be grateful if someone (@mike ?) explains to me, describes with other words what is meant by backporting in this context. About my context: I am a diligent Hubzilla user and evangelist for exactly years. I have had little, if any, contact with Zap.

Mon, 27 Sep 2021 17:12:59 +0200

neue medienordnung plus

nmoplus@realtime.fyi

Supplement: I am a diligent Hubzilla user and Hubzilla evangelist for exactly 5 years.