On Jun 1, 3:16 pm, Doug Williams d...@twitter.com wrote:
Leo,This has been covered many times before. It's 140 UTF-8 characters.
Please search the archives of this group for the complete conversation,
If you cared to read my messages, you’d have seen that they reference
half a dozen
Leo,This has been covered many times before. It's 140 UTF-8 characters.
Please search the archives of this group for the complete conversation,
If you cared to read my messages, you_d have seen that they reference
half a dozen conversations in this list, with employee participation
as
if i worked at Twitter and was dealing with issues like unplanned down time
[1]. Clarifying if users can post 140 bytes or 141 bytes is the last thing I
would be dealing with. Just play it safe and round down. Or run your own
laconi.ca server where you can make your own esoteric rules.
On Mon,
[1] http://status.twitter.com/post/115523264/unscheduled-downtime
On Mon, Jun 1, 2009 at 12:16, Abraham Williams 4bra...@gmail.com wrote:
if i worked at Twitter and was dealing with issues like unplanned down time
[1]. Clarifying if users can post 140 bytes or 141 bytes is the last thing I
Leo,This has been covered many times before. It's 140 UTF-8 characters.
Please search the archives of this group for the complete conversation,
including Twitter employee participation. We certainly care, but we are
still a small team who need people to help themselves as much as possible.
As
I think everyone would like an open system for doing this :)
On May 15, 9:58 pm, Eric Martin emarti...@gmail.com wrote:
I'd be interested to see a document that details the standards for
this as well.
On May 15, 12:01 pm, leoboiko leobo...@gmail.com wrote:
On May 15, 2:03 pm, leoboiko
On May 15, 2:03 pm, leoboiko leobo...@gmail.com wrote:
Later I intend to thoroughly replace “characters” by “bytes” (or
“UTF-8 byte count”, c.) in the API wiki.
My bad; it seems the API wiki is not publicly-writable? Could someone
with write access do this?
--
Leonardo Boiko
On May 15, 2:03 pm, leoboiko leobo...@gmail.com wrote:
while one with 71 UTF-8
bytes might not (if they’re all non-GSM, say, ‘ç’ repeated 71 times).
Sorry, that was a bad example: 71 ‘ç’s take up 142 bytes in UTF-8, not
71.
Consider instead 71 ‘^’ (or ‘\’, ‘[’ c.). These take one byte in
I'd be interested to see a document that details the standards for
this as well.
On May 15, 12:01 pm, leoboiko leobo...@gmail.com wrote:
On May 15, 2:03 pm, leoboiko leobo...@gmail.com wrote:
while one with 71 UTF-8
bytes might not (if they’re all non-GSM, say, ‘ç’ repeated 71 times).
