13
Parzi
3y

I wrote a file transfer thing to appease the initial idea that keeps coming back into my head every so often, like it's trying to haunt me. Problem: No mobile provider will let me test it, as it's meant to throw disgusting numbers of SMS messages at someone waiting for them. How many, you ask? Well, 1MB of data translates to about 8100 "standard-length" SMS messages. (Standardized length, non-"long" SMS messages are, at best, 70 UCS-2, 140 ASCII, or 160 7-bit characters.) It does work, though, as if I just write out all the SMS messages to files and read those in (in place of actual SMS messages, different delivery of the same data) it works flawlessly.

Why would I ever wanna make this? Well, T-Mobile seems to be more concerned with building new cell towers, rather than fucking fixing the ones currently working. The mobile data component usually dies for 8 or 9 hours a day in this medium-size city, but SMS still works, so... just use that to transfer data!

Comments
  • 4
    I just did some quick math: the maximum supported number of messages per transaction is 9,999,999,999, plus the initial metadata message. At 129 bytes per SMS, that's... 1200GB, give or take? The only figure I can find for how much Twilio charges per message is $0.0075, which would make that one transaction... JUST SHY of $75 million.
  • 2
    I have seen a marine software doing something similar but over satellite.
    Utility would convert export from software (can have files too) into text that was fed into satellite terminal. Slowly emails over satellite connection took over
  • 0
    @theKarlisK ,MS typically needs the mobile data component of a network to work. The entire point is avoiding that.
  • 2
    Use FM radio band ;p
  • 1
    Managed to get it up to 135 bytes/message, with support for 1099511627776 messages/transaction. That's 135TB of data at maximum! (That's also $8.2 billion to transfer a maxed-out transaction via Twilio!)
Add Comment