51–60 of 109 posts
Cute and clever. Browsing the web at 140 characters at a time.
He's not doing this at "140 characters at a time"
Cute and clever. Browsing the web at 140 characters at a time.
Earlier quoted context omitted.
Who pays for the MMS you send back? You or the recipient? (Or is it free?)
The recipient pays if they don't have a messaging plan. You can send an MMS to a US T-Mobile customer by emailing 1115557777@tmomail.net (if their phone number were (111) 555-7777), so that's how I do that.
Probably not for long!
One of these days, the network providers are going to stop putting arbitrary labels on their data, as though "voice", "text" and "data" are not all travelling through the same towers and pipes.
Earlier quoted context omitted.
That's not true. PNG has some filters that pre-compress the image before sending it to zlib.
I'd say that still falls under the realm of being " pretty much a zlib compressed bitmap", no?
The png optimizers you see (optipng, pngcrush, etc)? What they do is carefully pick the optimum filters to get the best file size. So I'd say those filters were the most important part of the compression.
Earlier quoted context omitted.
>While I was testing it, the whole pipeline, from pressing the "go" button to the page being fully rendered could take as little as 15 seconds. How is that possible? I thought the whole point of SMS was that it resided in the wasted bytes towers use when they "ping" phones. The reason text messages aren't instant is that these pings aren't sent frequently. I could be way out to lunch on my understanding, but this see…
The responses aren't sent by SMS, but MMS. My understanding is that to download an MMS you essentially get a data connection with your provider that only lets you download MMSes.
Never underestimate the bandwidth of a truck loaded with hard disks :)
Earlier quoted context omitted.
Nice. I hope the app has a "don't send passwords" warning in there ;) Also, how do you (do you?) handle SSL operations, specially POSTs?
It doesn't have a "don't send passwords" warning. I should definitely add some kind of warning/disclaimer page that pops up when you boot the app. I display a warning when the user tries to navigate to an HTTPS URL that messages sent to/from Smozzy aren't encrypted and it's not recommended that you proceed. I had a general idea for an encryption scheme (hardcode Smozzy's certificate's public key into the application…
Cute and clever. Browsing the web at 140 characters at a time.
Wrong on two counts, the first being that SMS messages are 160 characters, Twitter is 140, the second being that SMS is only used for sending requests, the real data arrives via MMS.