[twitter-dev] Re: Snowflake: An update and some very important information
@Themattharris: was there any change to the implementation timeline?
Quote: by 22nd October 2010 (Friday): String versions of ID numbers
will start appearing in the API responses
I'm still not seeing id_str, to_user_id_str and from_user_id_str etc.
in the current search API output, example:
http://search.twitter.com/search.json?geocode=52.155018%2C4.487658%2C1km
is there an updated timeline or did I miss something?
Best,
-- Johannes / @jlapoutre / @tweepsaround
On Oct 19, 2:19 am, Matt Harris thematthar...@twitter.com wrote:
Last week you may remember Twitter planned to enable the new Status ID
generator - 'Snowflake' but didn't. The purpose of this email is to explain
the reason why this didn't happen, what we are doing about it, and what the
new release plan is.
So what is Snowflake?
--
Snowflake is a service we will be using to generate unique Tweet IDs. These
Tweet IDs are unique 64bit unsigned integers, which, instead of being
sequential like the current IDs, are based on time. The full ID is composed
of a timestamp, a worker number, and a sequence number.
The problem
-
Before launch it came to our attention that some programming languages such
as Javascript cannot support numbers with 53bits. This can be easily
examined by running a command similar to: (90071992547409921).toString() in
your browsers console or by running the following JSON snippet through your
JSON parser.
{id: 10765432100123456789, id_str: 10765432100123456789}
In affected JSON parsers the ID will not be converted successfully and will
lose accuracy. In some parsers there may even be an exception.
The solution
To allow javascript and JSON parsers to read the IDs we need to include a
string version of any ID when responding in the JSON format. What this means
is Status, User, Direct Message and Saved Search IDs in the Twitter API will
now be returned as an integer and a string in JSON responses. This will
apply to the main Twitter API, the Streaming API and the Search API.
For example, a status object will now contain an id and an id_str. The
following JSON representation of a status object shows the two versions of
the ID fields for each data point.
[
{
coordinates: null,
truncated: false,
created_at: Thu Oct 14 22:20:15 + 2010,
favorited: false,
entities: {
urls: [
],
hashtags: [
],
user_mentions: [
{
name: Matt Harris,
id: 777925,
id_str: 777925,
indices: [
0,
14
],
screen_name: themattharris
}
]
},
text: @themattharris hey how are things?,
annotations: null,
contributors: [
{
id: 819797,
id_str: 819797,
screen_name: episod
}
],
id: 12738165059,
id_str: 12738165059,
retweet_count: 0,
geo: null,
retweeted: false,
in_reply_to_user_id: 777925,
in_reply_to_user_id_str: 777925,
in_reply_to_screen_name: themattharris,
user: {
id: 6253282
id_str: 6253282
},
source: web,
place: null,
in_reply_to_status_id: 12738040524
in_reply_to_status_id_str: 12738040524
}
]
What should you do - RIGHT NOW
--
The first thing you should do is attempt to decode the JSON snippet above
using your production code parser. Observe the output to confirm the ID has
not lost accuracy.
What you do next depends on what happens:
* If your code converts the ID successfully without losing accuracy you are
OK but should consider converting to the _str versions of IDs as soon as
possible.
* If your code has lost accuracy, convert your code to using the _str
version immediately. If you do not do this your code will be unable to
interact with the Twitter API reliably.
* In some language parsers, the JSON may throw an exception when reading the
ID value. If this happens in your parser you will need to ‘pre-parse’ the
data, removing or replacing ID parameters with their _str versions.
Summary
-
1) If you develop in Javascript, know that you will have to update your code
to read the string version instead of the integer version.
2) If you use a JSON decoder, validate that the example JSON, above, decodes
without throwing exceptions. If exceptions are thrown, you will need to
pre-parse the data. Please let us know the name, version, and language of
the parser which throws the exception so we can investigate.
Timeline
---
by 22nd October 2010 (Friday): String versions of ID numbers will start
appearing in the API responses
4th November 2010 (Thursday) : Snowflake will be turned on but at ~41bit
length
26th November 2010 (Friday) : Status IDs will break 53bits in length and
cease being usable as Integers in Javascript based languages
We
[twitter-dev] Re: Search with geocode does not respect search radius?
Update: the ticket is closed and @TweepsAround seems to be working fine again. Details: http://code.google.com/p/twitter-api/issues/detail?id=1930 Quote: Comment 3 by project member tokofu, Today (13 hours ago) We've deployed some changes which should have fixed this issue so i'm closing the ticket. Many thanks! On Oct 11, 9:38 pm, themattharris thematthar...@twitter.com wrote: Thanks for filing the ticket on this, we'll post there when a fix is deployed. Progress wise I checked in with the team today and they continue to work on a fix. To keep things connected there is another thread that was discussing the issue with geocoded search here: http://groups.google.com/group/twitter-development-talk/browse_thread... More information will be filed on the ticket here: http://code.google.com/p/twitter-api/issues/detail?id=1930 Thanks for bearing with us whilst we work out what went wrong with the location index and how to resolve it. Best, @themattharris On Oct 10, 9:29 pm, Nick nick.fritzkow...@gmail.com wrote: We are having issues with this as well and it has completely broken our system. We have sent many support tickets but have received no response to them. It looks to be breaking plain searches to not just those requested via the API. Some examples of broken searches are: http://search.twitter.com/search?q=bigpond+near%3Aaustralia http://search.twitter.com/search.json?q=bigpondgeocode=-27.766513,13... These were working before this issue. Best Regards Nick Fritzkowski On Oct 6, 2:42 am, Matt Harris thematthar...@twitter.com wrote: This is a know issue which the team is working on at the moment. I'll post an update when a fix is deployed. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Mon, Oct 4, 2010 at 8:36 PM, _ado adri...@tijsseling.com wrote: For what it's worth, I'm seeing the same issue. Radius parameter is completely ignored. Data returned for, for example, a 1 mile radius will return results spanning 60 miles. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Search with geocode does not respect search radius?
Hello, Since a few days it seems that search restricted by geolocation and search radius is not working correctly anymore. If I submit this request: http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C1kmrpp=100 I expect all resuls to originate from a geocode within 1km radius around the central coordinate. As of a few days ago I get many results from much farther away, up to several tens of kilometers. Is this a known issue? Any time to a fix? Or has there been an API change? Note: I revisited the API documentation ad could not find any recent changes. Best, Joe. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Search with geocode does not respect search radius?
Ouch, that is pretty nasty... I'll see what can be done as merging multiple searches will degrade response times rather badly. Thanks for the reply! On Sep 24, 4:33 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We have a bug right now effecting exactly these kinds of searches. I'm not sure how quickly it will be fixed, but I'm hoping it will be early next week. I don't think there are any functional workarounds besides merging multiple searches. Sorry about the mess! Taylor On Fri, Sep 24, 2010 at 6:57 AM, Johannes la Poutre jsixp...@gmail.comwrote: Hello, Since a few days it seems that search restricted by geolocation and search radius is not working correctly anymore. If I submit this request: http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C... I expect all resuls to originate from a geocode within 1km radius around the central coordinate. As of a few days ago I get many results from much farther away, up to several tens of kilometers. Is this a known issue? Any time to a fix? Or has there been an API change? Note: I revisited the API documentation ad could not find any recent changes. Best, Joe. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
