Signal Snap Maintainer here, this is because of a DMCA takedown request from lawyers representing Signal. Canonical is currently working with them to clear things up.

Canonical's communication to me was initially lacking due to issues in their process, the process has been amended and I'm back in the loop again.

Yet another reason not to use Signal. The correct behavior would have been for signal to offer an official snap or to contact the maintainer. Instead they send their legal team...

kevin_b_er

What this is is also another reason not to use Snap.

This is a multi-level failure.

1. Signal-Desktop is AGPLv3: https://github.com/signalapp/Signal-Desktop

2. The snap package metadata is AGPLv3: https://github.com/snapcrafters/signal-desktop

So, this looks like a fraudulent DMCA claim by Signal, as the snap package maintainers and Canonicial have an open source license! This shows malice by Signal.

3. No-one from Canonical contacted the package maintainer(s) about the DMCA, so they have no opportunity to counterclaim or defend.

This is an open sign Snap should not be used. Because utterly unjustified DMCA claims will result in the removal of a package without any way to contest. This is compounded by Canoncial's controlling methodology with Snap where it is ostensibly open-source but Canonical controls what is permitted with snap through a closed-source server.