meshtastic
Added audio_permitted to ChannelSettings
Audio over meshtastic may not be an elegant experience and this will help ensure that audio was intended by the channel originator. Not expecting this to be a hard stop on bad actors, but it's a start.
I don't believe there is risk of this happening currently on the tradition band LoRA meshes due to audio module only being available on 2.4GHz LoRA, but it's a good idea to guard against its eventual usage there. I'm wondering if there are other portnums of traffic we might guard against by default though. Perhaps we could have a uint32 as an enum w/ flags enabling those portnums on a channel.
I don't believe there is risk of this happening currently on the tradition band LoRA meshes due to audio module only being available on 2.4GHz LoRA, but it's a good idea to guard against its eventual usage there. I'm wondering if there are other portnums of traffic we might guard against by default though. Perhaps we could have a uint32 as an enum w/ flags enabling those portnums on a channel.
Re: Only available on 2.4ghz - I'm planning on changing that. :)
Great idea idea on the enum!
Re: Only available on 2.4ghz - I'm planning on changing that. :)
I'm keen on this idea as well. Especially the idea of a voice memo over the mesh. The T-Deck has full i2s audio that we are just utilizing for ringtones currently. Way under-utilized IMO.