The Twitter API call is working correctly. (
http://twitter.com/statuses/user_timeline/zenbullets.xml?count=5 ).
I would recommend asking in a Flex developer forum where they specialize in
Flex development.
Abraham
On Wed, Sep 9, 2009 at 09:10, Markus thonhau...@gmail.com wrote:
Hi!
I'm
I've always just stored as 64bit integers, I'd assumed that 32bit wouldn't be
enough.
Now, if it goes above 64bit then I'm screwed, because neither my language or
database have built in support for that! :P
From: JDG
Sent: Thursday, September 10, 2009 4:21 AM
To:
What is the documented range for status IDs? (How high can they go?)
Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
-Original Message-
From: twitter-development-talk@googlegroups.com [mailto:twitter-
Here is the Verified Account info: http://twitter.com/help/verified
http://twitter.com/help/verifiedAbraham
On Tue, Sep 8, 2009 at 07:20, hughes...@sbcglobal.net wrote:
Howard,
Can you do that on the regular set up account page or do you have to go
through something else?
Sent from my
PHP libraries / examples are here: http://apiwiki.twitter.com/Libraries#PHP
On Sep 10, 6:55 am, Joel Strellner j...@twitturly.com wrote:
Something like this is going to require a server-side language, like PHP,
Perl, Ruby, etc. JavaScript wont cut it.
I'm not sure how you'd do this without
Seeing as 32bit signed was 2,147,483,647 and 32bit unsigned is
4,294,967,295
And 64bit signed is 9,223,372,036,854,775,807, I'd say we're safe for
a good little while yet!
On Sep 10, 7:23 am, Ted Neward ted.new...@gmail.com wrote:
What is the documented range for status IDs? (How high can they
and if they are, just store the twos complement of the ID in the DB and do
the math when you retrieve if it's negative. :)
On Thu, Sep 10, 2009 at 00:12, Rob Ashton robash...@codeofrob.com wrote:
I've always just stored as 64bit integers, I'd assumed that 32bit
wouldn't be enough.
Now, if
You need to add:
result=onRes(event)
to the mx:HTTPService, because if you add a breakpoint to your onRes
function it never gets called as its not told what to do on getting
any result back.
On Sep 9, 3:10 pm, Markus thonhau...@gmail.com wrote:
Hi!
I'm trying to display a twitterfeed in my
Hello Twitter Developers,
Is there a way to use the search API to get Tweets not from a
particular source (i.e via web, TweetDeck etc)? I am trying to get a
search full of tweet that isn't from my application but is referencing
a hash tag.
Is this possible?
Thanks,
Greg
I want to complain to Twitter, because Dana Web Pro post links to my
Twitter pages rying to get my pages sut down, you see from the link
below one is good one advertising his site and the other one going to
give me a warning.- I paid Dana Web Pro to do some work for me, so he
had my password to
I'm still seeing this recurring problem. Are only oauth users
experiencing this? If so, maybe its time for us to give up on OAuth?
On Sep 9, 12:16 pm, John Kalucki jkalu...@gmail.com wrote:
Point your mobile device through a web proxy that you control. Monitor
the traffic there with tcpdump.
Call me crazy, but I store any data from a 3rd party in strings.
Typically, I used a text blob to store some serialized object (like
json or a python pickle) which maximizes flexibility. For the tweet
id, I think I used 64 chars.
In about 10 years, after I've cleared all the other higher
hello raffi and everyone,
a demo and a question;
GeoMeme is geo-app using the Location field to provide measurement and
comparison of real-time local twitter trends, e.g. see http://www.geome.me/51ARK
to compare New Yorkers tweeting about Snow Leopard vs. Windows 7.
when geolocation is
hey bob.
will the geo tags be contained in results from the public Search API
/or just the REST API?
the plan is to have geo in the public search API as well!
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
On Wed, Sep 9, 2009 at 1:07 AM, Matt Sanford m...@twitter.com wrote:
I more than agree with the above statement that a character is a
character and Twitter shouldn't care. Data should be data. The main
issue with that is that some clients compose characters and some
don't. My common
Hey developers, any hints/tips on how I can get the Twitter API team
to focus on this issue? It's hard to build a business on the Twitter
API when a crucial feature like this just stops working and we get
radio silence for days. Any tips on how I can help the team focus on
this??
On Sep 9, 10:10
I'm not developer, but couldn't find better place to report. I looked
around to see if this issue as been submited but not seen. The
folowing discussion is from 2 weeks ago (forgot to report). The issue
is that if you don't put space at the end of link, the bracket is sent
to bit.ly engine for
Yes, you need to ask twitter to fix that. They are using our api, but
obviously, they are encoding the ) after the .jpg. Thanks for
letting us know, but yes, this is a twitter issue.
Good luck with that. Since it is acceptable to have the unencoded )
character in a URL, I don't know how they
People are working on this as a high-priority issue. I'd imagine that
the API team will have an update soon.
On Sep 10, 2:09 pm, Monica Keller monica.kel...@gmail.com wrote:
We see this error 75% of the time. Have you guys made an progress on
resolving the issue ?
On Sep 6, 8:14 pm, archF6
Yet another reason Twitter should NOT be bit.ly encoding URLs that do not
cause tweets to go 140 chars. (or at all for that matter, leave that up to
the users)
On Thu, Sep 10, 2009 at 13:42, Matthew Terenzio mteren...@gmail.com wrote:
Yes, you need to ask twitter to fix that. They are using
I completely agree with the sentiment as stated, but have a question.
Does the URL shortening happen only for tweets entered at twitter.com?
Or does it also happen for tweets created via the API? The former is a
twitter UI issue, and if they want to shorten tweets, well, that's their
business.
Hi guys,
I don't seem to have found any trace of this report before, so I
thought I should post it.
According to the http://apiwiki.twitter.com/Twitter-REST-API-Method:-friends ids
documentation, you can actually get the results using any of the
following 4 URIs:
On Thu, Sep 10, 2009 at 2:45 PM, Jim Renkel james.ren...@gmail.com
wrote:
Does the URL shortening happen only for tweets entered at twitter.com?
Or does it also happen for tweets created via the API? The former is a
twitter UI issue, and if they want to shorten tweets, well, that’s their
Hi,
Our app has been using twitter RSS for a while for fetching status
updates of users. (e.g.
http://twitter.com/statuses/user_timeline/serenity.atom). Its worked
fine. But in the last couple of days we are getting more and more
error 400 when we do the HTTP get on the ATOM URL. The IP of the
I recently switched from search api to stream api. Consquently, I
needed to use the getInReplyToScreenName() to get the reply name.
However, this is returning null.
Therefore, I am parsing the tweet text directly to extract the
@lithium token.
If in fact URL shortening is possible via the API, then there should at
least be an option to suppress it.
I have seen the API shorten URLs that I have already shortened which has
caused problems but I never got an answer on what the rules were because I
have also noticede some longer URLs
To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've
posted a draft of the Twitter API rules at
http://twitter.com/apirules. As the subject states, these rules are a
work in progress and feedback is welcome. Please read the TOS
announcement at http://bit.ly/2ZXsyW for some
The only link that was did like was the person did them purposely he is web
master, he know what he was doing.
On Thu, Sep 10, 2009 at 4:31 PM, Mytweetopics monsoon@gmail.com wrote:
Hi,
Our app has been using twitter RSS for a while for fetching status
updates of users. (e.g.
I expected to see more along the lines of rules of which the violation
would cause a blacklisting of the app.
No problems with what is in the draft at present.
Dewald
No offence but can you please post these 'draft' rules along with the
current API rules.
Sorry if I sound 'overtly suspicious' but as you can imagine I'm a
little wary of anything that twitter inc says at the moment and would
like to have all of the rules in a single location as it causes
Dean,
That's basically what I meant. We know those are not the only rules,
so the other rules should also in the draft, shouldn't they?
Dewald
On Sep 10, 9:50 pm, Dean Collins d...@cognation.net wrote:
No offence but can you please post these 'draft' rules along with the
current API rules.
This is great news! Regarding sending Tweets on a user's behalf, does
that refer to DMs as well, and when seeking permission, must it be on a
tweet-by-tweet basis, or can a user give you permission beforehand to have
complete control over Tweeting on their behalf? I'd like to see that part
Yep exactly - having ALL of the rules clearly spelled out will save
confusion.
It's probably an automatic suspension because the twittersphere went
crazy today talking about the Titans V's Steelers game tonight but my
@LiveNFLchat twitter account has been suspended this afternoon even
though
Jesse,
I know where you are heading with this. ;-)
If a user explicitly activates a feature in an app that sends DMs on
their behalf, they at that point explicitly grants the app permission
to do so.
Dewald
On Sep 10, 10:10 pm, Jesse Stay jesses...@gmail.com wrote:
This is great news!
Dewald, I'm not heading anywhere with it. I just want Twitter to clarify the
terms, that's all. Feel free to leave your input if you have an opinion on
what those details should be.
Jesse
On Thu, Sep 10, 2009 at 7:35 PM, Dewald Pretorius dpr...@gmail.com wrote:
Jesse,
I know where you are
Jesse,
I apologize. Then I made incorrect assumptions. I thought you saw it
as the potential Excalibur in the fight against auto-DMs.
In my case, not only does the user activate the feature, he also
provides the exact text that must be sent. Not only is that express
consent, it is express
I think I understand this better now and have applied for a white
listed IP.
Thanks,
rahul
On Sep 10, 4:31 pm, Mytweetopics monsoon@gmail.com wrote:
Hi,
Our app has been using twitter RSS for a while for fetching status
updates of users.
Hi there,
A few notes on the new cursor-based API.
Despite promises a month ago, it's not documented (except in an e-mail
to this list)
Rather than have the old, admittedly broken API return errors, you've
elected to keep it up, corrupting databases everywhere. What was the
thinking behind
There is a in_reply_to_screen_name field prepopulated for you on a
Streaming API methods. The Streaming API cannot return null, as you
cannot represent null over HTTP. I suspect you are having other
problems.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sep 10, 4:43 pm,
We believe an unannounced Twitter API change happened today or
yesterday, and we just want to fill the group in on our findings.
This change caused some consternation from some of our user base
(your app doesn't work!), and we want to help preclude that for
others.
As you know, if user A blocks
This document needs further detail, specifics, and allowances.
1. Identify the user that authored or provided the Tweet
What do you mean by this? Presumably the author of the tweet is the
person for whom the tweet appears on Twitter.com and who therefore
actually made the tweet or authorized
41 matches
Mail list logo
