Most have two character codes, but other than " and maybe newline it's rarepic.twitter.com/jQwFT1XXGV
I'm worried that the baby thinks people can't change.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Most have two character codes, but other than " and maybe newline it's rarepic.twitter.com/jQwFT1XXGV
unicodes in json are 6 string characters. '\u007F'. If you do it Casey's way, it's two '\'+chr(0x7F).
The problem is very simple. If you are handed a buffer and you need to know how much space the JSON encode will take, right now it's 6*size. If you fixed this, it would be 2*size. It is an important difference.
The strings being encoded, other than the ones in the image can be as is. utf8 with a codepoint >0x19 is all good
This doesn't affect the problem at all. The maximum size before parsing is still 6*size, and always will be, because until you inspect the contents of the input, you don't know whether it will contain, for example, entirely 0x01's.
It would be interesting to see if counting and doing a single allocation would be fastests. On the parsing side it has shown to be the case. Luckily the string can be treated as hex and then it becomes a single allocation with O(1) size lookup * 2
I have no idea what you're talking about. You cannot "treat" the string as anything in particular. You just have an input buffer of size n and you need to write the output into a JSON buffer, and that requires 6*n space in the worst case. Period. That is all there is to say?
If both sides agree the string can be encoded as hex. This isn't uncommon for binary data as string in json. Doesnt work for dropbox though
If both sides agree you don't have to send JSON! How is that helping?
Putting hex in a string is within the spec. Either way, yeah it’s bigger
BUT IF BOTH SIDES AGREE YOU DO NOT NEED TO SEND JSON. YOU WOULD JUST SEND THE STRING AS A RAW BINARY AND IT IS 1X THE SIZE. At the risk of stating the obvious, nobody who cares about these things would ever send JSON to each other. You'd use a more efficient encoding.
This discussion is about JSON, the format, as is necessary to use to send strings to things like web services, which you do not control. Which is the point of the JSON spec, and my complaint.
It isn't JSON issue. It's trying to encode within the limitations of a HTTP URL. JSON doesn't care as long as your code point is >0x19. It offers a mechanism, I agree that is 6x because Javascript did it that way, but generally it's not a problem. Here is it
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.