> implying server side isn't also JS The future!
Because who needs server side checks. It's 2017 and JS is all we need.https://twitter.com/MaximeEuziere/status/912981874372481026 …
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
API endpoint seems to enforce a limit of 280 characters, but complains that your tweet exceeds 140 characters if it actually exceeds 280
-
... although I guess it still is 140 for certain languages by counting certain unicode characters as two?
- Show replies
New conversation -
-
-
"Your Tweet was over 140 characters. You'll have to be more clever."
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Well, once it‘s enabled server-side, why even care about the people who just enable it on their client?
- Show replies
New conversation -
-
To be fair, they plan to roll it out to everyone eventually. It’s not like they’re permanently firewalling it off.
-
They have no server side checks for neither the length algorithm nor the actual feature being enabled. That's a severe roll-out failure.
- Show replies
New conversation -
-
-
But what if the server only accepts tweets <=280 characters??
-
The problem is it accepts tweets with 280 Japanese characters. Which is not supposed to happen.
- Show replies
New conversation -
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.