It does not seems to be OATH problem since user gets logged-in fine
but there is some issue while setting/uploading background..
If its OATH problem, it gave 'Invalid OATH signature Error'
On Nov 17, 6:16 am, jmathai jmat...@gmail.com wrote:
Which library are you using? Looking at this line:
Hi all,
I wondered if we already could start using the retweet API methods -
for example statuses/retweet.
Currently statuses/mentions also returns retweets , so what is the
difference between thos and how
should they be organized in an application implementing this
functionality/
Thanks.
Mentions are anyone who replies or mentions or retweets you, retweets
are exactly that, just retweets?
On Nov 17, 10:15 am, twittme_mobi nlupa...@googlemail.com wrote:
Hi all,
I wondered if we already could start using the retweet API methods -
for example statuses/retweet.
Currently
Still happening to me, and it only occurs when I login via my own
server (87.117.224.42). I've started using oauth which works fine, but
worried that other people using my site are also having issues.
Thanks
Ryan
On Nov 17, 5:59 am, Mark McBride mmcbr...@twitter.com wrote:
Is this still
Hello, we have built a little test page here:
http://twavatars-dev.appspot.com/test?screen_name=freddyxyz
And I'll head over to the code tracker now to post the URL and a
comment.
-H
On Nov 16, 3:19 pm, Raffi Krikorian ra...@twitter.com wrote:
Hi.
This is a known issue and is being tracked
Thanks thats great to know. I'm sure with this information some sort
of new design that can be found. I'll be giving it some thought at the
end of the week.
Ben
On Nov 16, 10:55 pm, John Kalucki jkalu...@gmail.com wrote:
If you have a fairly stable set of tags, you should absolutely obtain
Mentions are any tweets that contain @yourscreenname in the tweet.
Retweets are tweets that repeat a previously posted tweet (kind of
like email forwarding).
On Tue, Nov 17, 2009 at 7:08 AM, Rich rhyl...@gmail.com wrote:
Mentions are anyone who replies or mentions or retweets you, retweets
I re-read the section on updating filter predicates in the api doc and
it seems to say that reconnecting every 2 min is acceptable. If thats
the case that would have an impact on the design I'm kicking around.
Ben
On Nov 16, 10:55 pm, John Kalucki jkalu...@gmail.com wrote:
If you have a fairly
I've been having this same issue when connecting to https://api.twitter.com.
I would have thought that if it is a problem with my code, I would
always get this error. However, it is intermittent. Most times it
works, but a few times an hour I will get the error. Also, I never
have this problem
Ops has been trying to track down this problem for a while. They
confirmed that all servers have the correct cert. The current
hypothesis is that there are some rogue servers that are being load
balanced to that we don't expect to be accepting api.twitter.com
traffic that do not have the correct
On Nov 17, 2009, at 10:50 AM, David Dellanave wrote:
Could this be related to when an API request returns raw HTML like
the over-loaded page? That would be my first guess.
SSL/TLS negotiation happens much earlier in the transaction, so no,
raw HTML is not a cause of this.
-john
Hi guys,
I'm wondering if anyone can clarify.
The services I run often shown tweets that are several months old, and offer
the RT button next to them. If someone clicks to RT the tweet, how does the
tweet get presented to people that aren't following the original tweeter?
Is it placed at the
Hi Marcel,
Thanks for following up on this. The bad cert responses I got were
inconsistent. Often it would work fine, so what you've outlined here is one
theory that would explain it.
I think I'll switch back to twitter.com for this app, and look at using
api.twitter.com in a future update.
Should appear as a new tweet with the time of the retweet, not the
original tweet creation time. That assumes though that no one else has
retweeted it to you yet. If someone else has then this additional
retweet won't appear in your timelines except for the
statuses/retweets/id resource that
Marcel,
This collapsing behavior is far from ideal and will cause people with
busy timelines to completely miss retweets.
Nobody is online 24x7, and if only the first retweet of an update is
shown in a user's timeline, they will miss completely it if the first
retweet happened several hours
Hey Dewald,
What if your twitter client had a feature of showing you tweets in your
timeline that had been retweeted by 10 or more people? That's possible now.
It was very very difficult before.
Marcel, thanks for your reply earlier. I noticed something yesterday that
indicated this
Does everyone have access to the ReTweet beta now? If not when is
expected deployment. I have a fully working ReTweet API
implementation but I don't want to submit it to Apple until everyone
has access to it.
On Nov 17, 9:19 pm, Marcel Molina mar...@twitter.com wrote:
As Tim mentioned, clients
The retweet feature is currently rolled out to 50% of users. We
gradually ramping it up. Full availability should be soon unless
issues arise as we incrementally roll it out. Thanks for your
patience. It's awesome to have people ready to pull the trigger on
retweet.
On Tue, Nov 17, 2009 at 1:27
After doing some righteous spelunking our ops team discovered a small
misconfiguration that was very likely the culprit of the intermittent
untrusted cert error people were getting when trying to hit
api.twitter.com over SSL. This should be all fixed now. To those who
reported the problem thank
Hi All,
Am new to twitter and wants to create an application in twitter for
sharing information from my site.
For this I have downloaded an PHP library for working with
Twitter's OAuth API from the below link
http://github.com/abraham/twitteroauth
with the help specified in the link
Are there any plans to add an API call to return all posts that are
in_reply_to a specific post? I'm constantly coming across tweets that
are questions directed at specific users and I have no easy way of
finding whether that user responded or not short of searching their
timeline around the
Hi All,
We have been noticing gaps appearing in search results at times when
doing geocoded searches in particular. For example with this search
over South Eastern Australia :
http://search.twitter.com/search.json?rpp=100lang=enpage=1geocode=-35.2,144.0,1000km
Occasionally produces results
hi, I've added search to blazingstreams.com in order to find news from
our database of real time news (curated, filtered, ranked and
classified by category/topics in near real time). If somebody is
interested in using search for a 3rd party, please let me know, I will
be happy to expose an API for
Hai,
I have send a request to Twitter API for the tweets by using request URL
including Geo Code with location *US* and radius 2400 KM then i got error
*Please provide a more specific query* , if i decreased radius from 2400KM
then i got tweets at a particular radius but some times it worked at
24 matches
Mail list logo
