I'm thinking more and more about why the 280-character limit is implemented differently client- and server-side. Why would you do that?
-
Show this thread
-
What possible benefit could there be to having two different implementations of the 280-character limit?
2 replies 0 retweets 3 likesShow this thread -
It has many drawbacks. It means a client has to accept and correctly display Tweets which it nominally shouldn't be able to produce.
1 reply 0 retweets 2 likesShow this thread -
If the server-side implementation later falls into line with the client-side one, that leaves us with numerous extant "impossible Tweets".
2 replies 0 retweets 2 likesShow this thread -
Replying to @qntm
Those issues will exist anyways if Twitter decides to tweak weights or number of characters later.
1 reply 0 retweets 0 likes -
Replying to @chrideedee @qntm
Clients will have to display tweets allowed under older rules but not current, or allowed under new rules they don't know about yet.
2 replies 0 retweets 0 likes
Well at least these rules are clearly codified somewhere OH WAIT
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.