discord-api-docs VS Mumble

Discord documentation - all things related to the Discord Developer API,

Just like how denying View Channel prevents someone from sending messages in that channel, denying Connect implicitly denies the other permissions. I don't think this behaviour is new - it looks like it was documented a year ago

Twitter - https://developer.twitter.com/en/docs/twitter-api Facebook / Instagram / Whatsapp - https://developers.facebook.com/ Linkedin - https://developer.linkedin.com/product-catalog Pinterest - https://developers.pinterest.com/ TikTok - https://developers.tiktok.com/ Youtube - https://developers.google.com/youtube/v3 Twitch - https://dev.twitch.tv/docs/api/ Discord - https://discord.com/developers/docs/intro

WS = WebSocket? I think integrating with the Discord API would've been one use case until they added the slash commands & webhooks.

But looks like Discord Gateway blocks CF Workers: https://github.com/discord/discord-api-docs/issues/6145#issu...

Kinda sort of, only if it's used in the first line of a message. You can not match multiline with (?m) because of a bug in Discord's regex implementation: https://github.com/discord/discord-api-docs/issues/6094

It's usually possible to match that too using (?m), but Discord's regex implementation has a confirmed bug with it's newline implementation, so it currently doesn't work: https://github.com/discord/discord-api-docs/issues/6094

A bug

I think Sonobus is overkill. I suggest you look at a couple of relatively old-school gamer voice chat tools - Mumble or Teamspeak. Mumble is open-source and the connection is always encrypted, Teamspeak is commercial but the free tier should be fine for you - but you have to make sure to manually turn encryption on yourself. It has been a long time since I used either, so I don't know which is easier. Both of them require you to run their matching server software.

Mumble's latency is unbeatable imo, it's basically their main focus and shows.

The sticking point for me is the lack of persistent messages, something the devs strangely think is a privacy plus. Issue open since 2016: https://github.com/mumble-voip/mumble/issues/2560

If you drop out for a minute you won't have access to anything that was posted in chat, which makes it useless for anything other than voice only comms, that might suit some business purposes but I've always needed to post links or screenshots in chat during meetings.

There's any number of alternative chat applications available, like Element, Mumble, Teamspeak etc.

Mumble?

I think Mumble might fit what you're looking for. It's been a very long time since I've used it, but it seems to still exist: https://www.mumble.info/ - I've used previously for exactly what you're describing, events with lots of crew dispersed around and no budget for radios. I had it installed on an AP running OpenWRT so it was just a case of plugging that in and getting people to install the app and connect to it.

Along with the options already mentioned, if you're not into TeamSpeak, there is an open source alternative called Mumble which operates in the same manner. No internet required, and is supported on multiple platforms.