Warpinator's do not connect to each other after cloning of installation.

[ihatetheantichrist-1]

Version and configuration:
ALL

Issue
After I cloned the installation from PC to Laptop Warpinator's did not found each other on network.
Issue is caused by unique identifier stored in /home/user/.config/warpinator/.group that does not change or is removed even after apt purge of Warpinator.

Steps to reproduce
Clone installation to other computer and use Warpinator.

Expected behaviour
apt purge warpinator* should remove unique identifier from /home/user/.config/warpinator/.groupfor reinstall.
Or better unique identifier could be cleared and regenerated in Warpinator settings.

Other information
Unique identifier in /home/user/.config/warpinator/.group that is not visible to user causes problems even after reinstall.

[ALTracer]

Define "clone". Timeshift? Rsync? Git dotfiles?
apt purge must never touch users' configuration in ~/.config (imagine browser bookmarks disappearing, or saved pop3 mail)

Why do you consider this an issue of warpinator? Its GUI perfectly shows the group code setting and allows redefining it. If you decided to automate / rollout something, just include the settings file into your management routine.

[ihatetheantichrist-1]

Define "clone". Timeshift? Rsync? Git dotfiles? apt purge must never touch users' configuration in ~/.config (imagine browser bookmarks disappearing, or saved pop3 mail)

Why do you consider this an issue of warpinator? Its GUI perfectly shows the group code setting and allows redefining it. If you decided to automate / rollout something, just include the settings file into your management routine.

Disc cloning, but does the same in every method like tar.
This identificator is not group code but unique identificator for machine - they are 2 separate things.
And btw removal script in deb can be defined to remove specific file.