"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]I mean, that this #VersionHurdle make the "Nomadic Identity" pledge of Hubzilla implausible.[/i]

exportImport #NomadicIdentity #HubzillaPromotion #NomadicIdentityPledge @hubzilla+470+ @support+457+

[zrl=https://hub.freecommunication.org/photos/nmoplus/image/0f34d9caf77dc41e7e116f0a7b4663e5018145c464023f1f2cef9593e62b89d8][zmg=586x640]https://hub.freecommunication.org/photo/0f34d9caf77dc41e7e116f0a7b4663e5018145c464023f1f2cef9593e62b89d8-2.png[/zmg][/zrl]

[zrl=https://hub.webgoeslocal.net/channel/dm42/&f=&mid=088621e3ff39c140f2a8db385d91f5362f71af34f2b5d7e5a87637c2a82e3e4a@hub.webgoeslocal.net&f=&mid=088621e3ff39c140f2a8db385d91f5362f71af34f2b5d7e5a87637c2a82e3e4a@hub.webgoeslocal.net?f=&jsdisabled=0]PR Submitted for CART core functionality[/zrl]