Their API has also done both simultaneously at various times, mogrifying tweets as they transition between queues/memcache.
SMS doesn't actually use bytes natively -- it's 160 7-bit characters packed into 140 bytes. As is their way, Twitter fucks this up: they use the 20 spare characters for the "username: " prefix, but limit usernames to 15 characters -- 3 are completely wasted! Why not allow usernames to be 18 characters?
They've historically fucked up plenty of other SMS encoding details like sending & escaped as & and murdering unicode in weird ways -- always truncating the message at an arbitrary tier instead of validating/refusing it up front.
SMS doesn't actually use bytes natively -- it's 160 7-bit characters packed into 140 bytes. As is their way, Twitter fucks this up: they use the 20 spare characters for the "username: " prefix, but limit usernames to 15 characters -- 3 are completely wasted! Why not allow usernames to be 18 characters?
They've historically fucked up plenty of other SMS encoding details like sending & escaped as & and murdering unicode in weird ways -- always truncating the message at an arbitrary tier instead of validating/refusing it up front.