There seem to be a variety of possible causes for getting an 403 error
in responses to a calling statuses/update... you could be duplicating
a tweet or hitting the update limit for an hour or for the day.
How can you tell which one these errors actually occurred?
The only 2 ways I can think of
Thanks for the clarification, Ryan. This distinction isn't clear in
the original blog post. I also wasn't sure what the difference was
between me posting a message that I love Reebok shoes and Starbucks
posting they have a special on Frappuccinos. If advertising was
prohibited from Tweets, it
I stopped development on my Twitter appa year after realizing that the twitter API was not yet stable enough to allow an individual developer to create a stable product. I continue to follow the exchange between developers and Twitter as much for entertainment as to keep track. Twitter understands
This is probably so obvious I'm missing it. How do I delete a retweet?
We tweet jobs for customers to not only our accounts, but to their branded
accounts as well. Companies like this because they can outsource this
mechanism to a third party without getting their IT groups involved. We
don't do any advertising within the tweet, other than provide a bit.ly link
Hi everyone,
I have been working on getting twitpic upload to work with my client,
and some of it is now functioning with oauth echo.
There are some things that look broken / not implemented on the twitpic
side, perhaps someone knows more and can verify:
- it seems to make a difference
Hi guys, im developing an Android application for twitter that will
sync data coming from the people you follow.
The problem is that:
http://api.twitter.com/1/statuses/friends.json
provides me the last 100 persons ive followed and i wanted to display
only 20 for each 'page'.
I believe that the
Sir, I HAVE a problem,
I try @anywhere Service, for My Wordpress www.OriflameNews.com (can
you see it)
I Have Done All of Registration and Installing that but error like
that :
Callback URL i set to www.oriflamenews.com
But the error like that :
Sorry, something went wrong.
Small_robot The
I created a curl command using the example in your API Documentation:
CURL COMMAND START -
curl -v -H 'X-Auth-Service-Provider:
https://api.twitter.com/1/account/verify_credentials.json'
-H 'X-Verify-Credentials-Authorization: OAuth realm=http://
api.twitter.com/,
So, Tweetie for Mac, which shows an ad at the top of my friends timeline
... will no longer be allowed to do so?
http://i.imgur.com/pazT3.png
Is this another misinterpretation of the policy, too?
On 5/25/10 1:28 AM, Ryan Sarver wrote:
It *does prohibit* an application from calling out to a
Tried changing the the callback url to oriflamenews.com? Looks like it
is complaining because you have set the subdomain to www on the
callback but your pages automatically redirect to a domain url without
it. Least thats my best guess.
On May 25, 7:28 am, Teofilus teofi...@gmail.com wrote:
Sir,
On May 25, 1:28 am, Ryan Sarver rsar...@twitter.com wrote:
The language is somewhat nuanced but it sounds like we might need to make
the policy more explicit as a number of people are misinterpreting it.
It sounds like most people are misinterpreting it which might have
to do with how the
Hi Guys
In my own tinkering with the @anywhere stuff, I've noticed the
@anywhere OAuth flow is using a much-better designed OAuth screen than
regular OAuth at the moment: particularly in making clear which
account you're linking the @anywhere app to. Any chance these
improvements will be brought
I created a curl command using the example in your API Documentation:
CURL COMMAND START -
curl -v -H 'X-Auth-Service-Provider:
https://api.twitter.com/1/account/verify_credentials.json'
-H 'X-Verify-Credentials-Authorization:
Just use Authorization:.
--
I created a curl command using the example in your API Documentation:
CURL COMMAND START -
curl -v -H 'X-Auth-Service-Provider:
https://api.twitter.com/1/account/verify_credentials.json'
-H 'X-Verify-Credentials-Authorization:
Just use Authorization:.
Er, sorry: try
On Tue, May 25, 2010 at 4:16 AM, mycro...@lifewithindustry.com wrote:
I stopped development on my Twitter app a year after realizing that the
twitter API was not yet stable enough to allow an individual developer to
create a stable product. I continue to follow the exchange between
I really don't like the fact that calling users.lookup() returns the
last 100 users I have friended.
Is there a way to retrieve users in a more random fashion or with some
kind of ordering (ascending/descending)? I'm looking for more
optional parameters.
Suppose, for instance, that I have 500
Matt, Doug,
I will often use the following query at http://search.twitter.com to
monitor links posted with my Social.com application:
j.mp source:social.com
I noticed over the last few weeks that sometimes the source:
operator would stop working altogether for all applications, but
usually
Try adding count=20.
https://api.twitter.com/1/statuses/friends.xml?screen_name=abrahamcount=2
Abraham
On Mon, May 24, 2010 at 22:41, Dave Molinaro duber...@gmail.com wrote:
Hi guys, im developing an Android application for twitter that will
sync data coming from the people you follow.
The
Hey! How are you doing?
We read your post on “Twitter Development Talk”
‘Google Group’. You are right that, developing a twitter app individually is a
very hard work. Or, in crux, it’s really impossible.
But, please don’t give up. If you still like
All,
Should be interesting to this mailing list:
http://www.semanticweb.com/on/semantic_wave_hits_ecommerce_part_2_current_innovation_161798.asp
Twitter Annotation implications are towards the end of the article, best
you read the entire article for context.
--
Regards,
Kingsley Idehen
I'd love to see some clarification from Dick on this statement and/or
a possible change in the TOS. The press has wildly heralded it as the
end of all advertising on Twitter not coming from Promoted Tweets.
Even if this is not true the public perception certain impacts all of
our
Ryan,
Thanks for writing the clarification. It sounds as if the intent of
the ban is to prevent anyone from emulating and distributing a stream
of Twitter data to Twitter mobile/web/desktop clients and inserting
ads into it. Tweets posted in individual accounts by account owners
or by
Uniqlo created a (web?) app that allows people to enter a contest or get a
discount by tweeting a message from their account; see [1]. (It also seems
like they’re not using OAuth as the tweets are “via API,” but that’s not
why I’m writing.) So many people are entering the contest that “UNIQLO
Unfollow/block the people who participate, if it bothers you. But,
don't prohibit it in the Twitter ToS, please!
On 5/25/10 3:57 PM, Brian Smith wrote:
Personally, I find these kinds of campaigns extremely annoying because
they turn my friends into spammers. But, it seems like they are not
Maybe
build an app that identifies these spam(like) messages and then
provides an API for other apps to help filter the spam(ish) messages.
On Tue, May 25, 2010 at 4:10 PM, Dossy Shiobara do...@panoptic.com wrote:
Unfollow/block the people who participate, if it bothers you. But,
don't
Hi,
currently it appears that there is no facility for an application
(consumer) to expire authorization.
The twitter server can't do it automatically, since it doesn't really
know when the consumer is finished with the authorized session, if ever.
The user doesn't even know that authorization
南北外交断絶問題発生によって韓朝鮮半島のtwitter ＧＰＳ障害が存在しているのでしょうか
Nobody?
On May 25, 12:14 pm, cballou ball...@gmail.com wrote:
I really don't like the fact that calling users.lookup() returns the
last 100 users I have friended.
Is there a way to retrieve users in a more random fashion or with some
kind of ordering (ascending/descending)? I'm looking for
Hi,
I was messing around with the users search REST API (http://
apiwiki.twitter.com/Twitter-REST-API-Method:-users-search) and I was
curious how the transition towards OAuth-only will change this method
call.
Can I access this resource with OAuth (and how?)? Or will BASIC Auth
be available for
I have confirmed a problem with xAuth/OAUth that I believe resides
within Twitter OAuth implementation that has been a thorn in our side
for a while. I say *believe* because I do not claim to know for sure,
thus this post.
I assume no one at Twitter will be inclined to do me any favours, but
It seems like there are two issues:
1) whether Twitter should disallow these messages to be sent out and
2) whether Twitter should screen these spammy messages out of the
possible choices for trending topics.
This is known and expected behavior. There have been other threads about it
in the last couple of weeks. If you get a 401 response, you should compare
the Date header of Twitter's response to the current system time. If it is
significantly off then you should warn the user so they can fix it
I've been having this same problem. In my case it seem related to
anywhere having a hard time figuring out what username is being
hovered over:
My structure is as follows:
li title=@username
a
div.../div
div@username/div
div
img/img
/div
/a
/li
I've tried adding hovercards
I'll make this much clearer in the documentation, and also include
tips to work around it dynamically.
We have a revision of our OAuth implementation that we'll be gradually
introducing into the system in the near future. It's going to be
opt-in for awhile so that we can work out any kinks, as
On Tue, 25 May 2010 19:49:28 -0500
Brian Smith br...@briansmith.org wrote:
This is known and expected behavior. There have been other threads
about it in the last couple of weeks. If you get a 401 response, you
should compare the Date header of Twitter's response to the current
system time.
Thanks. I did look through the archives before posting but did not
find anything. I will look harder next time. I still don't see where
in the OAuth specifications it says this comparison is necessary, but
I will continue to look around.
--ejw
Eric Woodward
Email: e...@nambu.com
On May 25,
This question is sort of pedantic, but I'm wondering why the API
refers to friends instead of followers. The API say's that
friends == following, but I understand (e.g. see this nice little
article
Twitter has evolved quite a bit over the last 4 years. It's not always
possible to evolve the API at the same pace.
I wouldn't say that mutual followers are friends. They're just mutual
followers.
On Tue, May 25, 2010 at 7:43 PM, Miles Parker milespar...@gmail.com wrote:
This question is
I've taken a look at recent posts on locations and geo-tagging. My
read of all of this is that we can associate tweets with locations in
~3 ways..
1. Geo-tags (user opt-in)
2. Location (user provided, pretty um.. low quality)
3. Some kind of behind the scenes magic that Twitter is doing
For case
On May 25, 8:05 pm, John Kalucki j...@twitter.com wrote:
It's not always possible to evolve the API at the same pace.
Of course..not moaning, just curious.
I wouldn't say that mutual followers are friends. They're just mutual
followers.
Yes, I guess that's a matter of semantic interpretation.
Are you talking about this - http://api.twitter.com/version/users/lookup.format
The above API returns whatever ids you have passed. Am I missing
something?
-Nischal
On May 26, 4:38 am, cballou ball...@gmail.com wrote:
Nobody?
On May 25, 12:14 pm, cballou ball...@gmail.com wrote:
I
Are you talking about this - http://api.twitter.com/version/users/lookup.format
The above API returns whatever ids you have passed. Am I missing
something?
-Nischal
On May 26, 4:38 am, cballou ball...@gmail.com wrote:
Nobody?
On May 25, 12:14 pm, cballou ball...@gmail.com wrote:
I
43 matches
Mail list logo
