process I can go through to get our app approved for use of
direct messages without using oAuth?
Thanks,
Jim Cortez
On 5/18/11 10:01 AM, Matt Harris wrote:
Hey everyone,
We recently updated our OAuth screens to give users greater
transparency about the level of access applications have to
ave a perfect
accuracy: only the first 41 bits can be used to sort, the other 23 bits
are to make sure that the ID is unique. If you have two tweets where the
first 41 bits are the same, there is no way to know which one was first.
Tom
On 11/2/10 6:25 PM, Jim Cortez wrote:
Can anyone help out on
Can anyone help out on this? My question is: If I compare Direct Message
ID's to each other to determine send/receive order, will it work under
Snowflake?
Thanks,
Jim
On 11/1/10 12:27 PM, Jim Cortez wrote:
When 2 numeric strings are compared, they are done by magnitude. Some
e
sure it is actually an unique ID.
The question remains where the loss of accuracy is: in the first 11 bits
or the last 11 bits. If it's the last 11 bits that get ignored, there is
no problem with comparing the numbers. If it's the first 11 bits that
get ignored, you will have to sh
I have learned that I can safely compare 2 long integer strings without
any problem. Is comparing Snowflake direct message id's in the manner
described safe?
Jim
On 11/1/10 11:29 AM, Jim Cortez wrote:
Hello all,
I have an non-browser xAuth client written in Javascript. I am in
?
Thank you,
Jim Cortez
--
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
Use xAuth: http://dev.twitter.com/pages/xauth
No web server required.
Jim
On 10/25/10 12:28 PM, Keiya Bachhuber wrote:
Is the next version of twitter going to be written in C++ and use GTK+
for rendering? Because that's what you're asking desktop developers to
do by forcing OAuth. I have to inc
://api.twitter.com/1/favorites/create/15738870223.json and it
should work.
On Tue, Jun 8, 2010 at 5:04 PM, Jim Cortez <mailto:j...@jimcortez.com>> wrote:
Hi all,
I am having trouble with setting favorites through the oAuth
API (with xAuth). Must other api's work (e
t;:"/1/favorites/15738870223/create.json","error":"Not found"}
Now on the web, this is fine:
http://twitter.com/twitterapi/status/15738870223
I tried removing the id as post data, but then I got an invalid
signature error. Any ideas?
Thanks,
Jim Cortez
