"cloned channel not found" by migration from hub version 3.4RC to hub version 3.2.2 - bug or feature?
Hubzilla community advertise the Nomadic Identity feature as unique feature of Hubzilla accounts. I get the hint "Cloned channel not found" when I attempt import the channel from one hub with version 3.4RC to hub with version 3.2.2. Is this behavior a bug or feature? I mean, that this #VersionHurdle make the "Nomadic Identity" pledge of Hubzilla implausible.
@Hubzilla Support Forum+