I have recently wrote a graphical, GTK+-based Shazam client for Linux, SongRec: https://github.com/marin-m/SongRec
I have began distributing it through a few channels, it was validated on Flathub:
- hxxps://launchpad.net/~marin-m/+archive/ubuntu/songrec/+packages (I’m redacting the protocol because of the limit of two links per message for new users)
I have uploaded a Snap package to Snapcraft, which isn’t public yet due to the requirement of approval for the DBus service interface: hxxps://dashboard.snapcraft.io/snaps/songrec/revisions/2/
The source of the concerned Snap package is publicly available here: hxxps://github.com/marin-m/SongRec/blob/master/packaging/snap/snapcraft.yaml
I am requesting here:
- Auto-connection for the “audio-record” interface plug: this is required to achieve the basic functionality of the application (song recognition from the microphone). Also, there isn’t any possible privacy risk/ because the upstream servers that perform recognition don’t receive actual audio (they just receive an array of some (amplitude, frequency, time) tuples for the strongest peaks of a sound excerpt, which can lead to recognize a known song but isn’t hearable sound).
- Auto-connection for the “dbus-svc” slot for the “com.github.marinm.songrec” DBus interface: this is required for the app to launch because this is a standard GTK+ 3 app which binds to a DBus service when launched, in order to handle multi-instance behavior, etc. If this interface slot is not set, then the app fails with an AppArmor error message at startup.