+1 from me for hardware-observe
(although ideally the app could just ignore this error on reading of MTU as this should not be needed to enumerate network interfaces, this should be possible via the existing network-observe
interface which is more appropriate to use for this purpose).
As for removable-media
, as detailed on Process for aliases, auto-connections and tracks there are pretty clear guidelines on what use-cases are appropriate for auto-connect of removable-media
- unfortunately I don’t think paratextlite
meets the current guidelines for this, so -1 from me for auto-connect of removable-media
(however this does not preclude the snap from using it and users manually connecting this interface, OR the use of portals etc to transparently access files on USB sticks etc).