[twitter-dev] statuses/update 403 error
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 is to try and parse the error message, or to follow up the request with a query about whether you've hit any limits. The problem with checking the error message is that: 1) It's fragile. If the twitter dev team decides to change the error msg, the solution breaks. 2) I'd have to know the error message first... and the specific error messages for hitting the update limit don't seem to be documented anywhere that I can see. Not in the wiki for sure. Which means that I'd have to hit the limit to find out directly what the messages are... not exactly practical, especially for the 1000 per day limit. It would take me a minimum of 7 hours to hit that limit, since I'd get capped by the hourly limit first. The problem with a follow-up request is that: I can't seem to find a way to get current remaining tweets available to the user before hitting the status update limit in the api. There's one for rate limiting: account/rate_limit_status But where's the corresponding api for the status update limits? What should I do about this? Is there some third, better way to find out which specific error resulted from the update attempt?
[twitter-dev] Re: Twitter Platform blog post
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 would apply to commercial accounts as well as individual ones. But you say that's not the case. At this point, I'm not sure what services DO fall under the prohibition guidelines but I guess they are ones where the users have given advertisers blanket control to post whatever they want on their Tweetstream. In effect, this sounds like advertising spam with a third party taking over individual users' accounts. Liz nwjersey...@yahoo.com
RE: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
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 the eco-system that is evolving no better than the rest of us but it still wants to control and direct the evolution. Each bit of control it exerts trims off branches of evolution that do not support the main stem. By cutting off branches twitter is possibly denying the evolution of future success. Original Message Subject: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISINGFrom: Eric Woodward e...@nambu.comDate: Mon, May 24, 2010 1:34 pmTo: Twitter Development Talktwitter-development-talk@googlegroups.comAt this point I am not why anyone that cares enough to be in thisgroup is surprised. It is clear that Twitter is going to take*everything* for themselves. I don't understand why anyone wouldcontinue to develop on Twitter's platform as anything more than ahobby. First it was us (Twitter clients) and now it is the adplatforms' turn. Next it will be somebody else.Lots of us enjoy developing for its own sake, and that is what Twitteris now: a feature you add to something else, or a hobby activity. Timewe all just faced up to it.--ejwEric WoodwardEmail: e...@nambu.com
[twitter-dev] Deleting a retweet
This is probably so obvious I'm missing it. How do I delete a retweet?
RE: [twitter-dev] Re: Twitter Platform blog post
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 that takes jobseekers to more detail about the job. Are these considered ads? Is this considered a violation? In the past, the folks at Twitter have told me that we're OK, but has this changed with the new TOC? If so, there's going to be a lot of upset brand-name companies. Thanks, Gary Zukowski TweetMyJOBS.com This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -Original Message- From: Liz [mailto:nwjersey...@gmail.com] Sent: Tuesday, May 25, 2010 6:36 AM To: Twitter Development Talk Subject: [twitter-dev] Re: Twitter Platform blog post 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 would apply to commercial accounts as well as individual ones. But you say that's not the case. At this point, I'm not sure what services DO fall under the prohibition guidelines but I guess they are ones where the users have given advertisers blanket control to post whatever they want on their Tweetstream. In effect, this sounds like advertising spam with a third party taking over individual users' accounts. Liz nwjersey...@yahoo.com
[twitter-dev] twipic OAuth Echo status
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 whether I use http://api.twitpic.com/2/upload.xml or http://api.twitpic.com/2/upload.json The difference being that for json it works, and for xml twitpic complains that twitter rejected my signature. I am making sure that the format (xml/json) is the same on the twitpic request, and on the fake twitter request that is being signed. Next, I noticed that the message paramenter being present doesn't seem to cause twitpic to post a message on twitter. When I use .../uploadAndPost.json instead of .../upload.json, the behaviour is the same - pic goes to twitpic, nothing to twitter. Perhaps the missing twitter post is because of this: Twitter Message from raffi a.k.a raffi sent on Tue May 25 01:09:27 2010 Curious how to do uploadAndPost in OAuth Echo? http://post.ly/hEdl Where raffi explains who uploadAndPost *will* work. Any comments ? Advice ? -- Bernd Stramm bernd.str...@gmail.com
[twitter-dev] Pagination - Twitter’s people you fo llow
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 'cursor' parameter doesnt do what i need, so i'm trying to figure out a way to store it. Can you guys give me enlightenment? Thanks in advance
[twitter-dev] Problem After Press Connect Twitter, WordPress
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 provided callback url http://oriflamenews.com/oriflame/2010/05/25/tanpa-berbuat-nyata-motivasi-oriflame/oriflame-online/oriflame-news/oriflame is not authorized for the client registered to 'http:// www.oriflamenews.com'. SCR SHT : http://twitpic.com/1qu4uj Best Regard, Teofilus Candra @TeofilusCandra @OriflameNews
[twitter-dev] Re: oAuth Echo problems
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/, oauth_consumer_key=9tMgFXW0rFtb2YLrBIFbIQ,
oauth_signature_method=HMAC-SHA1, oauth_token=69570246-
r0Z9nrgf5OKy2qyrTyOSKzvJn75hO2RcLurK9H3S8,
oauth_timestamp=1274766777, oauth_nonce=19583AFE-D5AD-4DD7-BAF7-
E842254D1CA7, oauth_version=1.0, oauth_signature=RidHgN2dR4NZNJMq
%2FSrfFuPN1HQ%3D%3D' -F key= MYAPPKEY -F med...@./
Picture11.png http://api.twitpic.com/2/upload.json
CURL COMMAND END -
And the response i keep getting is:
-- RESPONSE START
* About to connect() to api.twitpic.com port 80 (#0)
* Trying 174.36.58.233... connected
* Connected to api.twitpic.com (174.36.58.233) port 80 (#0)
POST /2/upload.json HTTP/1.1
User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3
OpenSSL/0.9.7l zlib/1.2.3
Host: api.twitpic.com
Accept: */*
X-Auth-Service-Provider:
https://api.twitter.com/1/account/verify_credentials.json
X-Verify-Credentials-Authorization: OAuth realm=http://api.twitter.com/;,
oauth_consumer_key=9tMgFXW0rFtb2YLrBIFbIQ,
oauth_signature_method=HMAC-SHA1,
oauth_token=69570246-r0Z9nrgf5OKy2qyrTyOSKzvJn75hO2RcLurK9H3S8,
oauth_timestamp=1274766777,
oauth_nonce=19583AFE-D5AD-4DD7-BAF7-E842254D1CA7, oauth_version=1.0,
oauth_signature=RidHgN2dR4NZNJMq%2FSrfFuPN1HQ%3D%3D
Content-Length: 1831
Expect: 100-continue
Content-Type: multipart/form-data;
boundary=e33c68df21fa
HTTP/1.1 100 Continue
HTTP/1.1 401 Unauthorized
Server: nginx
Date: Tue, 25 May 2010 05:52:06 GMT
Content-Type: application/json
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/5.3.2
* Connection #0 to host api.twitpic.com left intact
* Closing connection #0
{errors:[{code:401,message:Could not authenticate you (header
rejected by twitter).}]}
-- RESPONSE END
can you please tell me what am i doing wrong so i can integrate the
Oauth Functionality in my twitpic app ASAP.
Thanks!
On May 22, 12:14 pm, Rich rhyl...@gmail.com wrote:
The request to verify_credentials should be a GET and shouldn't
contain any of the parameters you intend to send to TwitPic either
On May 22, 4:51 am, Miguel de Icaza miguel.de.ic...@gmail.com wrote:
Hello,
1) You do not oAuth sign the actual request toTwitPic
2) You make a fake request to Twitter's verify credentials api over
SSL and grab the Authorization header that would be sent, however when
you create the header make sure you include a 'Realm'
ofhttps://api.twitter.com
3) Create a new post request toTwitPicand put the oAuth header that
you grabbed from Authorization in the HTTP header X-Verify-Credentials-
Authorization
4) Add a X-Auth-Service-Provider header with the URL to verify
credentials.
5) You should be good to go after that
I tried this, but I am getting the following message from TwitPic:
could not authenticate you (header rejected by twitter)
I created the OAuth headers as if I was trying to send an OAuth
request tohttps://api.twitter.com/1/account/verify_credentials.json
and added those headers to X-Verify-Credential-Authorization
The headers contain realm http://api.twitter.com; (tried also with
https)
Any ideas what Header rejected by twitter means?
If you get the signature right, it will work as I and a few others
have got it working when we were liasing with their engineers on
Sunday
On May 19, 3:41 am, uprise78 des...@gmail.com wrote:
I'm in the same boat. My call to Twitter works fine but I get 401's
fromTwitPicevery time.
Re: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
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 service to find an ad to serve to Liz that will get inserted into the timeline she is viewing. 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. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: Problem After Press Connect Twitter, WordPress
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, 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 towww.oriflamenews.com But the error like that : Sorry, something went wrong. Small_robot The provided callback urlhttp://oriflamenews.com/oriflame/2010/05/25/tanpa-berbuat-nyata-motiv... is not authorized for the client registered to 'http://www.oriflamenews.com'. SCR SHT :http://twitpic.com/1qu4uj Best Regard, Teofilus Candra @TeofilusCandra @OriflameNews
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
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 information was conveyed and not the intelligence of the readers. Maybe Twitter should have engineers/developers write all blog posts concerning parameters of what is allowed or banned with the Twitter API. Liz nwjersey...@yahoo.com
[twitter-dev] Differing UI for @Anywhere OAuth and Application OAuth
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 over to the other OAuth flows in the near future? We're using the PIN code OAuth in Socialite, and one of the issues we see (besides the entirely unfamiliarity of PIN code-based OAuth) is folks who are unclear in which account they're authenticating. Kind Regards, @nikf -- Nik Fletcher Support / QA Manager, Realmac Software http://www.realmacsoftware.com
Re: [twitter-dev] Re: oAuth Echo problems
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:. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- You can't have everything. Where would you put it? -- Steven Wright
Re: [twitter-dev] Re: oAuth Echo problems
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 X-OAuth-Authorization:. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Experience only makes you more interesting and marketable. -- Judy Blackburn
Re: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
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 developers and Twitter as much for entertainment as to keep track. Twitter understands the eco-system that is evolving no better than the rest of us but it still wants to control and direct the evolution. Each bit of control it exerts trims off branches of evolution that do not support the main stem. By cutting off branches twitter is possibly denying the evolution of future success. My experience and thoughts exactly, also. Nick
[twitter-dev] users.lookup() pulls by friendship date
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 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Twitter Search source: operator stopped working for sources with an embedded dot?
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 starts working again.For the past many days I have been unable to get it to work with the above query, though it does seem to work for other applications without a dot in the name. Has support for applications with a dot in the name been dropped (hoping this isn't the case)? I get the error: Unknown source 'social.com' FYI - there are posts going to Twitter with via Social.com Thanks, Scott
Re: [twitter-dev] Pagination - Twitter’s people yo u follow
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 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 'cursor' parameter doesnt do what i need, so i'm trying to figure out a way to store it. Can you guys give me enlightenment? Thanks in advance -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
RE: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
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 to create the twitter app or want to help in the development work, then you have the option to join us! We, Steel Sendras Group, is an organization providing various non-profit for-profit services worldwide. And, recently, we want to develop a really cool, efficient, smart, reliable twitter app along with other softwares. So, you can come on board. We are a community of people working together to make the web a better place. If you think it’s a spam, then please feel free to contact us. Cheers.. Steel Sendras Group Follow us on Twitter at: http://twitter.com/SteelSendras From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of mycro...@lifewithindustry.com Sent: Tuesday, 25 May, 2010 4:46 pm To: twitter-development-talk@googlegroups.com Subject: RE: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING 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 developers and Twitter as much for entertainment as to keep track. Twitter understands the eco-system that is evolving no better than the rest of us but it still wants to control and direct the evolution. Each bit of control it exerts trims off branches of evolution that do not support the main stem. By cutting off branches twitter is possibly denying the evolution of future success. Original Message Subject: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING From: Eric Woodward e...@nambu.com Date: Mon, May 24, 2010 1:34 pm To: Twitter Development Talk twitter-development-talk@googlegroups.com At this point I am not why anyone that cares enough to be in this group is surprised. It is clear that Twitter is going to take *everything* for themselves. I don't understand why anyone would continue to develop on Twitter's platform as anything more than a hobby. First it was us (Twitter clients) and now it is the ad platforms' turn. Next it will be somebody else. Lots of us enjoy developing for its own sake, and that is what Twitter is now: a feature you add to something else, or a hobby activity. Time we all just faced up to it. --ejw Eric Woodward Email: e...@nambu.com No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2895 - Release Date: 05/25/10 11:56:00
[twitter-dev] Twitter Annotation Potential Article
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 President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
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 businessesand if we are to develop with any level of trust what's stated clearly and publicly is still going to be more important than internal confirmations. Look forward to hearing a clearer stance on this. On May 24, 10:28 pm, Ryan Sarver rsar...@twitter.com wrote: I want to make sure this part is clear -- this policy change isn't meant to say that we are going to start policing if the content of something a user tweets is an ad or not. The policy change affects 3rd party services that were putting ads in the middle of a timeline. So if Liz is paid by Reebok to tweet about how much she loves their new shoes, we are not going to be policing that any more than we were on Friday. This policy also *does not prohibit* services like Ad.ly that help facilitate those relationships or even help her post the ads to her timeline on her behalf. It *does prohibit* an application from calling out to a service to find an ad to serve to Liz that will get inserted into the timeline she is viewing. 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. Let me know if you have more questions. Ryan On Mon, May 24, 2010 at 12:26 PM, Dewald Pretorius dpr...@gmail.com wrote: Liz, You are 100% correct in summarizing the problem. Not only were those businesses built with the full knowledge of Twitter, Twitter even had specific rules governing sponsored tweets (had to be clearly marked as sponsored, etc.). I'm really baffled by this decision of Twitter, because I don't understand how they expect to have integrity and trust with developers while doing this type of stuff. Right now we are all being pointed to Annotations as the holy grail of new development. But how do we know that they won't yet again change a rule in the future that will kill businesses that were built on top of Annotations? On May 24, 3:56 pm, Liz nwjersey...@gmail.com wrote: Peter, I think the problem is that business have been created, received funding and developed over the past year, with the full knowledge of Twitter, and this just undercuts destroys them. I think people can understand the rationale (and the desire for Twitter to eliminate competition) but this is a policy decision that should have been made over a year ago. Twitter should have included this in an earlier terms of service instead of giving an implicit okay to services like Sponsored Tweets which has turned into a successful company. It also seems disingenuous that the blog post says that a guiding principle of Twitter is that We don't seek to control what users tweet. And users own their own tweets. and allow adult-oriented content and photos but for some reason, users can't Tweet ads. That sounds like control of content to me. Liz
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
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 proxies/3rd parties on behalf of the account owners are still allowed. The blog post did not suggest that this was the case, nor did most of the press about the subject (as mentioned earlier in this thread). Your post clears this up a lot. Apologies to Dick On May 24, 10:28 pm, Ryan Sarver rsar...@twitter.com wrote: I want to make sure this part is clear -- this policy change isn't meant to say that we are going to start policing if the content of something a user tweets is an ad or not. The policy change affects 3rd party services that were putting ads in the middle of a timeline. So if Liz is paid by Reebok to tweet about how much she loves their new shoes, we are not going to be policing that any more than we were on Friday. This policy also *does not prohibit* services like Ad.ly that help facilitate those relationships or even help her post the ads to her timeline on her behalf. It *does prohibit* an application from calling out to a service to find an ad to serve to Liz that will get inserted into the timeline she is viewing. 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. Let me know if you have more questions. Ryan On Mon, May 24, 2010 at 12:26 PM, Dewald Pretorius dpr...@gmail.com wrote: Liz, You are 100% correct in summarizing the problem. Not only were those businesses built with the full knowledge of Twitter, Twitter even had specific rules governing sponsored tweets (had to be clearly marked as sponsored, etc.). I'm really baffled by this decision of Twitter, because I don't understand how they expect to have integrity and trust with developers while doing this type of stuff. Right now we are all being pointed to Annotations as the holy grail of new development. But how do we know that they won't yet again change a rule in the future that will kill businesses that were built on top of Annotations? On May 24, 3:56 pm, Liz nwjersey...@gmail.com wrote: Peter, I think the problem is that business have been created, received funding and developed over the past year, with the full knowledge of Twitter, and this just undercuts destroys them. I think people can understand the rationale (and the desire for Twitter to eliminate competition) but this is a policy decision that should have been made over a year ago. Twitter should have included this in an earlier terms of service instead of giving an implicit okay to services like Sponsored Tweets which has turned into a successful company. It also seems disingenuous that the blog post says that a guiding principle of Twitter is that We don't seek to control what users tweet. And users own their own tweets. and allow adult-oriented content and photos but for some reason, users can't Tweet ads. That sounds like control of content to me. Liz
[twitter-dev] Why is UNIQLO LUCKY LINEに行列 tr ending?
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 LUCKY LINEに行列” has been the top trending topic for the last couple of days. I am curious about the future of this kind of marketing campaign. I have had people contact me about creating these kinds of apps-not so much “tweet to win” but “tweet to get a discount.” Are they going to be allowed indefinitely? Is it acceptable for stores to set up a kiosk at the cash register for users to sign into, in order to send a (pre-written) from their account? Are there any guidelines at all? Personally, I find these kinds of campaigns extremely annoying because they turn my friends into spammers. But, it seems like they are not excluded from even the new ToS. Regards, Brian [1] http://www.independent.co.uk/life-style/fashion/uniqlo-twitters-top-trending -topic-thanks-to-virtual-line-campaign-1982399.html
Re: [twitter-dev] Why is UNIQLO LUCKY LINEに行列 trending?
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 excluded from even the new ToS. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Why is UNIQLO LUCKY LINEに行列 trending?
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 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 excluded from even the new ToS. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- imby - in my back yard An Experiment in Local Professional Networking http://madison.imby.info/p/Philip.Crawford
[twitter-dev] oauth expire
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 tokens and secrets exist, for the most part. However it could be good in some cases to enable the consumer application to explicitly say that it doesn't want the authorization any more. This would protect against the case of token/secret pair and consumer key/secret pairs being re-used by others. Is there any consideration for this? Basically all that would be needed is an API entry point where the consumer says thanks but no more, signed and verified as normal. -- Bernd Stramm bernd.str...@gmail.com
[twitter-dev] GPS check Korea Peninsula?
南北外交断絶問題発生によって韓朝鮮半島のtwitter ＧＰＳ障害が存在しているのでしょうか
[twitter-dev] Re: users.lookup() pulls by friendship date
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 more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Users Search OAuth
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 this call for a while? Thanks.
[twitter-dev] Twitter OAuth Timestamps
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 please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here: http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Re: Why is UNIQLO LUCKY LINEに行列 trending?
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.
RE: [twitter-dev] Twitter OAuth Timestamps
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 and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Eric Woodward Sent: Tuesday, May 25, 2010 7:40 PM To: Twitter Development Talk Subject: [twitter-dev] Twitter OAuth Timestamps 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 please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here: http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Re: Browser hover over ID sometimes says, Sorry, this does not appear to be an active Twitter account
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 two ways:
T(li).hovercards({
infer: true
});
and:
T(li).hovercards({
username: function(node) {
return node.title;
}
});
The problem is node could be equal to either the li, a, div, or img
nodes. Unless title is defined for all of those, the hovercard non-
deterministically fails.
Anyone found a fix to this problem??
On May 12, 4:12 am, Ken k...@cimas.ch wrote:
Perhaps related to this issue, the hover thing prevents me from
clicking on the username and visiting their account, which is why I
would be hovering in that vicinity.
Fwiw, thehovercarditself doesn't contain any information I need -
I'd just as soon disable it.
On May 12, 12:31 am, M. Edward (Ed) Borasky zzn...@gmail.com
wrote:
Occasionally, in Firefox 3.6.3 on Linux, when I mouse over a user
name, I see
that message. It's intermittent - I haven't had any luck trying to
reproduce
it. The account in question is always an active one - I can click on
the
screen name and get to the page just fine.
I have heard from another user that this also happens on Macs using
Safari. I
suspect it's getting some kind of error from Twitter and returning
that
message.
Speaking of errors, it also seems like page load times on my blog
involving
@anywhere interactions, like loading a follow @znmeb on Twitter
button, have
gotten longer. At some point, I plan to load up the Google speed tools
and try
to find out what's happening. But if there's something happening at
the
Twitter end, it would be good to get it fixed, because Google now
penalizes
slow pages in search placement, and that's not a good thing for
@anywhere.
--
M. Edward (Ed) Boraskyhttp://borasky-research.net/m-edward-ed-borasky/@znmeb
A mathematician is a device for turning coffee into theorems. ~ Paul
Erdős
Re: [twitter-dev] Twitter OAuth Timestamps
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 it's going to be a bit stricter to the spec. The new implementation will have the added benefits of more detailed error messages throughout OAuth authentication and authorization, including better messages as to the reason of the rejected request and signature base strings on signature mis-matches. Thanks, Taylor On Tue, May 25, 2010 at 5:49 PM, 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. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Eric Woodward Sent: Tuesday, May 25, 2010 7:40 PM To: Twitter Development Talk Subject: [twitter-dev] Twitter OAuth Timestamps 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 please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here: http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
Re: [twitter-dev] Twitter OAuth Timestamps
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. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian I am seeing headers coming back from twitter with Expires : Tue, 31 Mar 1981 05:00:00 GMT on replies with good status. Nothing going wrong, auth works fine. Just a funny looking date in there. Is that sombody's epoch? It looks vaguely familiar. -- Bernd Stramm bernd.str...@gmail.com
[twitter-dev] Re: Twitter OAuth Timestamps
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, 5:49 pm, 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. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Eric Woodward Sent: Tuesday, May 25, 2010 7:40 PM To: Twitter Development Talk Subject: [twitter-dev] Twitter OAuth Timestamps 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 please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here:http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Friends and followers
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 http://andrewchenblog.com/2009/03/16/friends-versus-followers-twitters-elegant-design-for-grouping-contacts/) that friends are mutual followers, that is: 1. I follow you (following)- 2. You follow me (follower) - 3. We follow each other (friends)- 4. Nada ø So would it be correct to substitute following for friends WRT to API? To keep it straight on my side, I'm going to have to come up with a word that means friends in the sense of 3 above.
Re: [twitter-dev] Friends and followers
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 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 http://andrewchenblog.com/2009/03/16/friends-versus-followers-twitters-elegant-design-for-grouping-contacts/ ) that friends are mutual followers, that is: 1. I follow you (following)- 2. You follow me (follower) - 3. We follow each other (friends)- 4. Nada ø So would it be correct to substitute following for friends WRT to API? To keep it straight on my side, I'm going to have to come up with a word that means friends in the sense of 3 above.
[twitter-dev] Location finding practices
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 3, that means that when we specify geo-boxes we're getting something more than just 1. Is there anything available publicly about how this is done? i.e. is it parsing of User.location, some kind of IP thing, spy satellites..? ;) As someone posted a while back, it seems that we can get all tweets within a geo-box, but we can't get the inverse, i.e. an (approximate) lat lon for an arbitrary tweet. So suppose: Tg[] = all tweets within box g. Tg[k] = some tweet in that bounding box, *without* a geo-location U[l].tweets.contains(Tg[k]) From which I know that Tg[k] is in g. Now, is that based solely on info from U[l] or does it take into account anything about Tg[k]? And, is my understanding correct that if I discovered Tg[k] from somewhere outside of that location search, I *can't* determine g (unless of course it is geo-tagged or I do some kind of bone-headed exhaustive search..) ? Finally, has anyone else in API-consumer land come up with a good set of heuristics for determining location from the user.location alone? I mean, there are some obvious steps, but I don't want to re-invent the wheel and given the uncertainty about the data available (TeaPartyVille,USA, Beer City In Flavor Country (sounds like a nice place to visit)) I'm not certain it's worth it. Are people having pretty good results about just parsing place names? Code? :) And of course, does anyone want to tell us/speculate about what TrendsMaps is doing here? My assumption is that they are just doing searches based on the twitter geo-boxing, but perhaps there is more magic here that might be sharable. enquiring minds... Miles
[twitter-dev] Re: Friends and followers
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. :D Personally I find the whole friending thing a bit obnoxious and I'm quite happy to see that the term hasn't been asopted for the web UI.
[twitter-dev] Re: users.lookup() pulls by friendship date
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 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 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Re: users.lookup() pulls by friendship date
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 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 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
