You could also use multiple phone numbers to send SMS to avoid SMS ratelimiting. FYI most carriers consider Person to Person messaging to be below 1 message per minute and run between 40% inbound to 60% inbound messages.
One thing to watch out for is some carriers like Cellcom if I recall sell unlimited texting plans that actually have a 20,000 message cap then $0.01 per message thereafter. A cousin of mine hit this about a decade ago as she was part of many MMS groups.
>FYI most carriers consider Person to Person messaging to be below 1 message per minute and run between 40% inbound to 60% inbound messages.
Yep, I've read into that a little. I wasn't able to find anything explicitly forbidding a service like this in their terms, although there's a lot of legal documents that carriers have so I could have missed it. I read that you should expect about 1 SMS/second on consumer carriers, but it seems like I'm able to get about 2-3 SMS/second in my testing.
I didn't know about carriers having an unlimited SMS threshold... I'll have to look into that, thanks for the heads up!
Also, Google Fi has unlimited text/call for $20/m. Their SIM does work with USB GSM modems.
Nevermind most GSM stacks crash when receiving/sending many messages quickly, they aren't designed for high throughput messaging.
Sending via a carrier's multi-device calling/texting option where you bypass their cell network and connect to their servers over the web, or using VoLTE or VoNR is going to perform much better than GSM
Do you have a specific "target market" in mind, with cheap / unlimited SMS but censored internet access? E.g. China, Russia, Turkey?
As far as censorship goes, a VPN is better by all metrics than this.
There allegedly is DPI, but it only comes into play as an extra measure against things like domain fronting, proxies, and plaintext HTTP. It'd look at the SNI and inject a RST packet to drop the connection. As it does not even try to implement TCP, analyzing each IP packet in isolation, there are various interesting utilities[1] that mess with it by, for example, splitting the TLS ClientHello into two TCP packets in the middle of the domain name.
This is my second year of working on a project[1] with the goal of browsing the web, on an Android smartphone, without reliance on Wi-Fi or mobile data. While this concept might seem aimless, my goal was to provide a way for people in areas with limited, expensive, or censored cellular internet access a way to view the web in a basic format. I finished work on a basic client-server model last year[2], and this year, I implemented a new pseudo-distributed peer-to-peer model that allows any TxtNet Browser user to use their own smartphone to run a background server service that communicates via the user's own primary mobile number. The main advantage to this model over last year's use of the Twilio API is the fact that with an unlimited SMS plan from a consumer carrier, you will likely end up paying significantly less than the amount you would pay for Twilio credits (averaging about ~$0.50 per website). There's a lot going on with the stateless nature of SMS, GSM-7 encoding, and Brotli compression, so please ask any questions you might have!
I've also started up a test server instance running on a +1 country code phone number, so feel free to test out the app with your own smartphone. Like mentioned in the GitHub repo, please be aware that I (necessarily) have access to every phone number and associated request that is sent. Of course, anyone can host their own server instance, and if you would like to share it, feel free to get in touch so I can add the number to the repo! Also, there are likely many bugs still lurking, so feel free to report those.
[1] https://github.com/lukeaschenbrenner/TxtNet-Browser/
[2] https://news.ycombinator.com/item?id=32905496