Has twitter changed to 64bits internally?
On Jun 13, 9:47 pm, Dossy Shiobara wrote:
> On 6/13/09 9:09 PM, Carlos wrote:
>
> > am I the only one that left the statud id as a string in my code? I
> > didn't feel the need to convert it.
>
> Depends on your application. Sometimes, it's necessary to
I dunno about you LAMPier guys, but in my mostly SQL Server world, I
sort by a created date/time stamp (my own internal, or Twitter's
published stamp) if I needed items in order of creation, and possibly
a ROW_NUMBER() call for paging ... never, ever, ever rely on external
IDs for anything but int
TalkingPuffin[.org] was persisting the ID values as strings, but
treating them as 32-bit ints. Changing them to 64-bit ints (in Scala)
took care of things, without having to convert any data stores.
On Sat, Jun 13, 2009 at 9:09 PM, Scott Elcomb wrote:
> On Sat, Jun 13, 2009 at 8:21 PM, Scott Elcomb wrote:
>> Hi all,
>>
>> Sorry if this comes across as a newbie question.
Well guess it was a newbie thing - I didn't realize this was a simple
support question; I have not yet
come across this inf
I have tried encoding the callback url, I have even tried changing the
oauth_verison to 1.0a and I even tried with signature type of
PLAIN_TEXT but to no avail. Has anybody done this successfully
in .NET. I would really appreciate any help thanks. I am not sure if
this is implemented yet on twitte
On 6/13/09 9:09 PM, Carlos wrote:
am I the only one that left the statud id as a string in my code? I
didn't feel the need to convert it.
Depends on your application. Sometimes, it's necessary to numerically
sort a list of tweets by ID. It's useful having it as a 64-bit integer
in those ca
am I the only one that left the statud id as a string in my code? I
didn't feel the need to convert it.
On Jun 13, 1:10 pm, Jef Poskanzer wrote:
> So how long until status ids reach 4294967296, breaking the apps that
> were "fixed" today by changing signed to unsigned? Taking twitter's
> growth
All Tweetshrap users, please update "TwitterStatus" object to use "long" for
"InReplyToStatusId" property. Otherwise you will be getting overflow errors.
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of mozT
Am 11.06.2009 um 19:02 schrieb Jochen Kaechelin:
>
> def self.consumer
> # The readkey and readsecret below are the values you get during
> registration
> OAuth::Consumer.new("X", "", { :site=>"http://
> twitter.com" })
> end
>
> def sign_in
> @request_token =
> Users
Nothing provided specifically for applications. You could do @-replies like
you mentioned. Also if you have write access for them you can follow an app
notifications account that you created and send them DMs. Of course for this
you should notify them before they authorize that you will add the acc
We've got a fix for this coming early next week. Long story short:
we'll provide a new method that returns the correct data, we'll stop
returning bad data inline (but we won't remove the attributes that
return bad data so we don't break your apps), and we'll give you more
requests per hour so you
Try encoding the callback URL first. For example: oauth_callback=http%3A%2F%
2Fprinter.example.com%2Frequest_token_ready
This example is from:
http://oauth.googlecode.com/svn/spec/core/1.0a/drafts/3/oauth-core-1_0a.html#anchor43
On Sat, Jun 13, 2009 at 13:19, Nizar wrote:
> Hi Doug,
>
> After r
It should be true/false but it is known to be unreliable. Read this:
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/42ba883b9f8e3c6e
On Sat, Jun 13, 2009 at 12:53, Bojan Rajkovic wrote:
>
> What is the type of the notifications property on users? Sometimes I
> get null,
What is the type of the notifications property on users? Sometimes I
get null, leading me to think it oughta be a string, though I've seen
false come back too. It's confusing the hell out of my JSON
deserialization, especially because I'm working in a statically typed
language (C#). Is it a tri-st
Hi Doug,
After reading your post I passed the oauth_callback parameter when
requesting a token but I keep getting 'Failed to validate oauth
signature and token'. It works as soon as I take out the callback
parameter. I am using .NET and here is my GET request please advise if
I am missing somethi
When I POST to statuses/update.json with an invalid OAuth token, I get
a non-JSON response from the server. Shouldn't the response from the
twitter.com/*.json always be JSON, even when there's an error?
For example, I see the following response when I try to POST to a read-
only Twitter-OAuth app
> So how long until status ids reach 4294967296, breaking the apps that
> were "fixed" today by changing signed to unsigned? Taking twitter's
> growth rate into account I think it's less than a year away.
I'll bet the Twoffice has a pool running on this RIGHT NOW.
--
--
So how long until status ids reach 4294967296, breaking the apps that
were "fixed" today by changing signed to unsigned? Taking twitter's
growth rate into account I think it's less than a year away.
---
Jef
Hello,
Can anyone tell me the available twitter curl with php functions. Any
sort of document will do...
Hi
Thanks for quick response. Any luck to get code in php.
On Sat, Jun 13, 2009 at 9:52 AM, Yusuke Yamamoto wrote:
> Hi all,
> Twitter4J 2.0.8 is available for download.
> http://yusuke.homeip.net/twitter4j/en/index.html#download
> It is(or will be) also available at the Maven central reposito
Minimal damage, and the website is still up and running. I think we
can call this a situation well-handled.
Dan,
If you're using an unsigned integer, you won't see problems until the
4.2billionth tweet. If you're using a signed integer (which you don't
need to, will there ever be NEGATIVE tweets?), you'll see it at the
twitpocalypse.
Thanks for playing.
- Tom
On Jun 12, 4:52 pm, Dan Udey wrote:
>
Hi Matt,
Could you also let us
know how you increment tweet numbers. It is not constantly linearly incremented
from 1, is it. That would mean there are over 2 billion tweets in the
system, which isn't.
On Sat, Jun 13, 2009 at 1:52 AM, Matt Sanford wrote:
>
> Hi there,
>
>That is indeed wha
23 matches
Mail list logo
