I was hoping to read about bitfields or bit flags.

The tailscale article is about UDP, but here we are talking about TCP.

Are you drinking alcohol ocasionally? I observed that there are two kind of pepole: - one who spend their spare time drinking - others who exercise

Both are fine for the soul :)

I like drinking while I'm doing it, and not after I've done it, but exercise is the other way around.

(OK only some exercise, and usually I already like it while I'm doing it, I just don't want to go out to do it.)

I exercise drinking

I don't drink in my spare time , but I can understand you comment and :)

Some people exercise to get fit.

I exercise to work up a thirst.

Change one character and the hash will not match anymore...

I would be interested in those tricks

A big one is 'masking' all client requests that a proxy can't effectively cache the response since the request always changes.

The RFC explains it: https://datatracker.ietf.org/doc/html/rfc6455#section-5.3

Yes, usually some more intelligent auth is needed, depending on your app logic. For example the MRTC SIP-WebRTC gateway will do the usual SIP digest auth first, then will send a temporary TURN password to the WebRTC client + it will allow only the current source IP to use the TURN service (with an extra auth message exchane if the IP changes during the call).

I am also affected. Can somebody suggest a good alternative?

Paddle. FastSpring.

2checkout (used them in the past, switched again since last month). Some people recommend PayPro Global (don't misread it as PayPal like I did at first).

itch.io

I am also affected. Can somebody suggest a good alternative?

Maybe Lemon Squeezy? Stripe recently acquired them, so they're probably not going insolvent any time soon.

VoIP reinvented?

If your question is why AOO does not use any of the (many) existing audio network protocols:

We wanted a protocol that

1. is simple to understand and implement

2. supports all the required features (as outlined in https://aoo.iem.sh/overview/)

If you know of any existing protocol that could achieve that I would be honestly curious to know!

I have a VoIP software (https://www.mizu-voip.com/Software/SIPSDK/JavaSIPSDK.aspx) and I am trying to market it as the interface between AI and real time audio/video. It already has real-time in/out streaming capabilities, i just want to add some more helper methods to make it more obvious for AI input/output. Can you help me with a little feedback? I am trying to think with the mind of an AI developer and I am interested on your thoughts on how to implement the real-time interactivity for your software/service? Is our JVoIP library close to your requirements or are you going to use something completly different to interact with the endusers and/or backend services? (To what kind of software/service are you thinking more exactly to cover this part?)