None of these are patent-able or sell-able. Many such ideas already exists and are sold. This is a one-off solution where I have built for my son and his friends. I could have bought a subscription and devices from elsewhere - but thought otherwise.
I could, potentially, build up infrastructure and expand - but, that's too much of a financial constraint and too much time away from my personal life.
The code and designs are out there for anyone to stand this up for themselves. Or I can help assist to set it up.
Fair point and unsolicited parental advice. There is only so much a son or daughter wants to play with you. By the time they are 10, they have their social circle built up. You also want them to have a circle (na unsolicited advice from me), as you don't want them to grow up all alone with none but their parents.
To answer: Yes, I am trying as much as possible I can (and he can) with each other.
Looks like, Tor may be an overkill for this project - according to Claude. That said, it advised there are several things we can borrow from your project:
1. Opus at 16 kbps
2. The voice-message model as a saved voicemail
3. In-call text chat
4. PTT chime
I may borrow the Opus, as I now send uncompressed PCM. May consider voicemail and chat (this may kill the joy, though - going away from ham-like experience).
Opus has incredible compression rates with high intelligibility I recommend if bandwidth is an issue...a few mild voice effects like static could be fun for the kids to make it seem like it's a real ham transmission, opus makes that easy.
It may be confused with what the voicemail was. Nothing actually gets saved like a voicemail, still destroyed after playback...I found record then send was the only way to overcome the latency of TCP and Tor.
Your setup is far more streamlined for lower latency coms for sure
So ... There are two options while recording. By default, only the absolute necessary traffic is captured for effective playback by any LLM. The other option is to capture all - that would be for sleuth - privacy and security abusive investigation.
The API drift is something I need to think about. They are bound to change over time - webbridge_update was made for that for now.
I am not entirely understanding "over fitting", can you please explain more?
Senior Product Manager with 16 years in legal tech + hands-on coding. Led Lexis+ AI launches (1,400 MAU Canada, 20k MAU US). Explored PI claims analytics in 2022. Strong SQL/data analysis—achieved 13% NPS increase through experimentation. I code my own solutions: shipped 5 AI projects in the past year (NPS Analyzer, RAG systems, LLM wrappers, semantic chunking). Seeking PM roles at AI startups building complex workflow products—particularly document generation, decision-support tools, or legal tech. Earned Paralegal cert to understand users better. Comfortable working with ML researchers. Ready to move from enterprise to startup velocity.
Thank you. Is that even normal/new norm? Back then when we released OS-native (read windows) code, we had to deploy without debug (assuming bitcode = debug) symbols.
Never mind, it seems like Bitcode has been disabled awhile ago. It’s been a hot minute since I last did mobile dev.
The promise of Bitcode was you’d upload an IR artifact and not the final binary (that held every supported platform). The App Store would then compile it for every supported platform and strip out all other platform’s aspects of it to optimize size.
None of these are patent-able or sell-able. Many such ideas already exists and are sold. This is a one-off solution where I have built for my son and his friends. I could have bought a subscription and devices from elsewhere - but thought otherwise.
I could, potentially, build up infrastructure and expand - but, that's too much of a financial constraint and too much time away from my personal life.
The code and designs are out there for anyone to stand this up for themselves. Or I can help assist to set it up.