Re: [twitter-dev] Unwanted T.CO shortening
Agreed : further absolutely unnecessary obfuscation of links. The whole reason for the use of shorteners and even the 140 character limit was in place due to the character restrictions on SMS. SO: Why not JUST shorten these links for SMS messages they send out?? I'm sure SMS only users are in a vast minority compared to mobile client and web/desktop clients. Unfortunately it seems to be the way things are going with Twitter. I have no idea why they just don't acquire bit.ly (and apply it to t.courls) with all it's great features for those who simply must shorten urls. FYI: The data API does provide the actual url (and character positions) of any original urls This is obviously only useful if you're creating your own client / ui to tweets. On 10 June 2011 21:00, Mo maur...@moluv.com wrote: How do I register my domain as a URL shortener (like bit.ly or ow.ly) so that the links I post do not get shortened with a T.CO domain when I use intents? I just looked through some old tweets and apparently even those URLs have been replaced with T.CO. When someone looks at my tweet stream they should see the domains I post, not T.CO. If I want to talk about a friend or partners site, they should see that URL, not T.CO. If I want to help promote a non- profit like the Red Cross, Oil Spill Relief, Joplin, Missouri Tornado Relief, etc., they should see their URLs not T.CO. There was a time when developers were really rooting for Twitter. Moves like this only benefit Twitter AND are detrimental to everyone else. Not only is changing links to past tweets bad for developers, but for marketers as well. Not to mention that it borders on being unethical. Can you imagine Google, Facebook, Yahoo, or Bing replacing URLs with their shorteners? Of course, they could do it, if they chose to, but they won't. I realize it's your company, you have a great product, and you can do what you want. But, Twitter's success came on the backs of many dedicated developers, who also have the choice of putting their time elsewhere. If only there were an open source microblogging solution. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Unwanted T.CO shortening
Yes. I use the API to lengthen t.co links (and also bit.ly links using their API) The massive trouble I have with all this is that I like to know what the hell I'm clicking on before clicking a link. It's kind of my right as a citizen of the web. I personally can't stand it when, for example a link fires up iTunes or goes to some site I don't want to waste (possibly mobile and limited) bandwidth on. I like to choose WHO I give MY visit/traffic to. It feels like some kind of Russian roulette ;) It's the unknown. The fact that they are heading towards t.co-ifying *every* link eventually is very worrying and extremely off-putting indeed. /me shakes fist at Twitter HQ On 10 June 2011 21:13, Tom van der Woerdt i...@tvdw.eu wrote: It's a certain level of control which Twitter gets. If a spammy application gets to Twitter, they can simply block those URLs via their URL shortener. This is a level of spam control they don't get with bit.ly, etc. I'd like to point out that the API returns full URLs and all official Twitter applications (and a lot of 3rd party ones) will display these URLs as well. If you shorten a bit.ly URL you'll still see that bit.ly URL, not a t.co URL. As long as Twitter doesn't start abusing this t.co thing, and as long as it's not down, it's fine with me. Tom On 6/10/11 10:09 PM, Kosso wrote: Agreed : further absolutely unnecessary obfuscation of links. The whole reason for the use of shorteners and even the 140 character limit was in place due to the character restrictions on SMS. SO: Why not JUST shorten these links for SMS messages they send out?? I'm sure SMS only users are in a vast minority compared to mobile client and web/desktop clients. Unfortunately it seems to be the way things are going with Twitter. I have no idea why they just don't acquire bit.ly (and apply it to t.courls) with all it's great features for those who simply must shorten urls. FYI: The data API does provide the actual url (and character positions) of any original urls This is obviously only useful if you're creating your own client / ui to tweets. On 10 June 2011 21:00, Mo maur...@moluv.com wrote: How do I register my domain as a URL shortener (like bit.ly or ow.ly) so that the links I post do not get shortened with a T.CO domain when I use intents? I just looked through some old tweets and apparently even those URLs have been replaced with T.CO. When someone looks at my tweet stream they should see the domains I post, not T.CO. If I want to talk about a friend or partners site, they should see that URL, not T.CO. If I want to help promote a non- profit like the Red Cross, Oil Spill Relief, Joplin, Missouri Tornado Relief, etc., they should see their URLs not T.CO. There was a time when developers were really rooting for Twitter. Moves like this only benefit Twitter AND are detrimental to everyone else. Not only is changing links to past tweets bad for developers, but for marketers as well. Not to mention that it borders on being unethical. Can you imagine Google, Facebook, Yahoo, or Bing replacing URLs with their shorteners? Of course, they could do it, if they chose to, but they won't. I realize it's your company, you have a great product, and you can do what you want. But, Twitter's success came on the backs of many dedicated developers, who also have the choice of putting their time elsewhere. If only there were an open source microblogging solution. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Unwanted T.CO shortening
I agree, the API does make it very easy to never see the t.co links, but for those of us on the website (particularly 'old' twitter) it can be a pain. I totally get that Twitter want to make their own shortener, and the 'new' twitter website does at least show the domain to where links go, but I just really wish they had the same info '+' pages which bit.ly urls have too. The lack of these features only serves to make us feel like we're giving them the data without getting the info on the traffic etc. - aside from the obfuscation issue. K On 11 June 2011 02:12, Tom van der Woerdt i...@tvdw.eu wrote: What they do in the background is irrelevant for the general public and for the purpose of this discussion. I very much disagree on that it's not relevant. If Twitter clients implement t.co properly, it's nothing more than a background process. I haven't seen a t.co link in days, as I finally implemented automatic unshortening of t.co links in my client - just like a lot of other clients do. If a link gets automatically unshortened on display, it's effectively nothing more than a background process. Tom On 6/11/11 3:03 AM, Mo wrote: The shortened links I originally saw were all in HootSuite. I've since logged out and logged back in and the T.CO shortened URLs went away. However, my original question was never answered. Is there a process for getting on a list of approved shortened URLs? Ben, your screenshot and the tweet page do not have the same content in the mouseover. John, you're smoking something. I just checked Google, Facebook, Bing, and Yahoo with a search of the term PHP. None of the exposed URLs are shortened. What they do in the background is irrelevant for the general public and for the purpose of this discussion. Kosso, I'm with you on the unexpected destinations. In short, whoever is in control at Twitter is either not in direct communication with users and developers in regard to this or is simply not listening. -Mo On Jun 10, 2:23 pm, Ben Wardbenw...@twitter.com wrote: On Jun 10, 2011, at 1:21 PM, Kosso wrote: The massive trouble I have with all this is that I like to know what the hell I'm clicking on before clicking a link. It's kind of my right as a citizen of the web. I personally can't stand it when, for example a link fires up iTunes or goes to some site I don't want to waste (possibly mobile and limited) bandwidth on. I like to choose WHO I give MY visit/traffic to. To be clear, the API returns all the information for all clients to display the original short URL, and navigate via t.co. We also look up the full destination URL and return that too, allowing even clearer navigation of where you as a user will end up when following a link. You can see this implemented on twitter.com today: https://twitter.com/joshtpm/status/79283124747501568 * The URL destination points to t.co * The displayed text of the URL is a cropped and shortened version of the real URL * The title (tooltip) of the URL displays the full address of the destination. I've further illustrated it with a screenshot here: https://skitch.com/benward/frff8/ The documentation for the URL entities that provide all of this information in the API response is here: http://dev.twitter.com/pages/tweet_entities Ben -- Platform Developer, Twitter -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Do new ToS conditions apply to my app?
Out of interest, what did you get rejected by Apple for? Was it anything to do with Twitter? Or was it all objectiveC stuff? I too have a Twitter client waiting in the wings for submission. Not long to go now. I'm just going to launch it and see what happens. if Twitter 'rejects'/disables it (considering they actually hold the 'keys' to whether the app is allowed to communicate - thanks oAuth) then I'll be making a big fuss about it ;) Good luck! K On Mar 11, 10:27 pm, howardk howar...@gmail.com wrote: I've just read the new Terms of Service referenced in the announcement consistency and ecosystem opportunities. It's unclear to me if those terms apply to an app I've just finished. I've developed a very simple iPad app that allows the user to maintain a list of feeds and stream any of those timelines banner-wise across the screen on demand. It's useful if you want to quickly check the most recent tweets from a particular source and also serves as a vehicle to show off some interesting and creative use of 3D typography on the iPad to display the content. There's almost no interface: Tweet content is shown exactly as-is, with only the addition of a username to identify the feed and an elapsed-time-since-publication placard. I submitted this app to the app store in December and was rejected. I've rewritten the app in response to Apple concerns and am one (1) day away from resubmitting to the app store. I've got +/- five months of effort into this project and will be devastated if I'm disallowed from publishing at this late date. Who can I talk to re determining whether what I've done falls under the umbrella of applications that are now prohibited by the new ToS? Best, Howard Katz -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Issues with OAuth
Yup. it's down. has been for hours. users of my app can't log in / authenticate their twitter accounts. If they're already logged in, they're fine. ie: other API calls work. On Jul 19, 4:02 pm, cyclemenow cycleme...@gmail.com wrote: I'm unable to use my own app! The status page implies that everything is up right now (http:// dev.twitter.com/status). I haven't been able to use OAuth almost the entire day. Does this issue affect everybody? Are there any workarounds? -Matthew On Jul 19, 3:10 pm, CJ ctj...@gmail.com wrote: Hi Ap, I thought I've broken my software. I had exactly the same error message after my software performed a HTTP GET for /oauth/ access_token?oauth_token=.oauth_verifier=PIN. Hope this issue can be resolved asap. CJ On Jul 19, 10:04 pm, Tim Davies timgrantdav...@gmail.com wrote: I've also been having this issue solidly for the last 5 hrs.
[twitter-dev] Re: @twitterapi meetup @ Twitter HQ
Out of interest, will there be any (legal?) reason why any of the attendants can't stream the meetup to UStream, for example? Also, do we need to bring a ticket, or will we sign in using OAuth? ;) heh On Feb 26, 2:19 pm, Ryan Sarver rsar...@twitter.com wrote: We won't be having a live video stream of the event this time around. We will be in the IRC channel and we'll be using Google Moderator to take questions from people both at the event and people who are remote. We'll walk before we run :) On Fri, Feb 26, 2010 at 12:42 PM, M. Edward (Ed) Borasky zzn...@gmail.com wrote: On Feb 26, 12:33 pm, Abraham Williams 4bra...@gmail.com wrote: A live feed would be awesome. Also the event says March 1st through April 1st... Ah ... an early April Fools' joke? ;-) I'm waiting for Linus Torvalds' April Fool email - I'm guessing this year he'll announce that he is buying Twitter ;-) But I'd settle for an IRC channel today and a Live from Twitter HQ broadcast in full streaming fashion at a later date ;-)
[twitter-dev] Re: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst
my problems are opposite (using some php scripts) verification is ok, tweeting ok, but verified timelines (friends and mentions) not ok. On Jul 27, 9:29 pm, winrich winric...@gmail.com wrote: ok guys. so my calls were failing on the verify_credentials call and not on the update or timeline calls. the only difference i saw was the the verify_credential call wasn't secured. i changed it to https and it worked. ??? lol On Jul 27, 9:19 pm, Chad Etzel jazzyc...@gmail.com wrote: On Mon, Jul 27, 2009 at 11:55 PM, Duane Roelandsduane.roela...@gmail.com wrote: RTFM is not a helpful answer, especially when many developers are relying on libraries that they did not write. That's a risk you run when using code you didn't write. I'm not saying that this situation doesn't suck for those affected. I'm sure that it does. But, for a technology so new as OAuth, the libraries may not be mature yet. Officially, Twitter OAuth is still in Public Beta and has never been officially recommended to integrate into production code. That being said, there could still be a problem on Twitter's end with their signature verification mechanism and the libraries could all be valid. I don't have a way of knowing. I do agree that at least a note that a security change was pushed today would be nice, though. -Chad
[twitter-dev] Re: Change callback url?
Go to http://twitter.com/oauth_clients (assuming it's the oAuth callback url you're asking about) Then select your app and click 'edit application settings' hth On Jul 26, 6:08 pm, Bob Fishel bobfis...@gmail.com wrote: How can I change my callback URL?
[twitter-dev] Re: This is a really dumb question. How can I get back to my application information page
Go to your 'settings' - then 'connections' - then the link is on the right, if you have registered apps : http://twitter.com/oauth_clients hth On Jul 26, 2:34 pm, Bob Fishel bobfis...@gmail.com wrote: So i registered an application to learn the ins and outs of the twitter api for a personal project, but I clicked off the page and now I can't figure out how to get back to change my applications settings and get my keys. I have honestly looked everywhere I can think of to try and get back to this page, and my google-fu is failing. Any help is appreciated. Thanks -Bob
[twitter-dev] Re: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst
same here. all was working fine (using abraham's php scripts linked from the examples) - has not been working for the past couple of hours. On Jul 27, 7:44 pm, Duane Roelands duane.roela...@gmail.com wrote: I am receiving 401 (Unauthorized) when callinghttp://twitter.com/statuses/update.xml and passing the following querystring: oauth_consumer_key=[removed] oauth_nonce=912352oauth_signature_method=HMAC- SHA1oauth_timestamp=1248748647oauth_token=19068738- hKO8qRlHPfJWqRHRkd62dGb4IiyXaXUy35Cqz58oauth_version=1.0status=This +is+a+testoauth_signature=Fl0kqJdHY5MkvxjUZQ%2bFn%2fxGORo%3d This code was working this afternoon and has not been changed. On Jul 27, 10:38 pm, goodtest goodtest...@gmail.com wrote: Are we sure there is no further regression bug in this new fix? On Jul 27, 7:14 pm, Doug Williams d...@twitter.com wrote: If you are still seeing errors you should check your code to ensure that you are sending the correct signature. Thanks, Doug On Mon, Jul 27, 2009 at 7:10 PM, winrich winric...@gmail.com wrote: mine broke too. i wonder though, i'm using the oauth python libraries On Jul 27, 6:35 pm, chinaski007 chinaski...@gmail.com wrote: Doug: Does this mean that Marcel made a fix for this? Or rather that we should examine our code to find the culprit? Thanks, Peter Bray On Jul 27, 6:24 pm, Doug Williams d...@twitter.com wrote: Updating you guys on this problem. A bug was reported off list that informed us we were not always verifying signatures. Today we shipped a fix for this problem which ensures that we are correctly verifying signatures. If you are still seeing invalid signature errors you should examine your code and ensure you are correctly signing requests as per the spec. Thanks, Doug On Mon, Jul 27, 2009 at 6:05 PM, Doug Williams d...@twitter.com wrote: Marcel is shipping a fix for this as I type. Thanks, Doug 2009/7/27 João Pereira joaomiguel.pere...@gmail.com Same here. On Tue, Jul 28, 2009 at 1:26 AM, goodtest goodtest...@gmail.com wrote: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst
[twitter-dev] Re: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst
agreed. please Twitter, tell us WHAT the fix required was. what should we look for. have you tested your 'fix' against all the code examples you link from the API pages? that would be nice. thx. I'm getting some posts through. some not. so something's still up/down On Jul 27, 8:04 pm, Duane Roelands duane.roela...@gmail.com wrote: You introduced a breaking change into the API with no warning and no help for developers as to the specifics of what we need to fix? Developers need better support than that. Is there some reason why posting updates to some accounts would work and posting to others would not? Using the same code, I'm able to post to my development test account but not to my personal account. On Jul 27, 10:59 pm, Doug Williams d...@twitter.com wrote: As stated above, some applications were sending invalid signatures which we were accepting as valid. This vulnerability was pointed out by a developer. Some libraries and code which may have previously worked may be broken by this security fix. Thanks, Doug On Mon, Jul 27, 2009 at 7:44 PM, Duane Roelands duane.roela...@gmail.comwrote: I am receiving 401 (Unauthorized) when calling http://twitter.com/statuses/update.xml and passing the following querystring: oauth_consumer_key=[removed] oauth_nonce=912352oauth_signature_method=HMAC- SHA1oauth_timestamp=1248748647oauth_token=19068738- hKO8qRlHPfJWqRHRkd62dGb4IiyXaXUy35Cqz58oauth_version=1.0status=This +is+a+testoauth_signature=Fl0kqJdHY5MkvxjUZQ%2bFn%2fxGORo%3d This code was working this afternoon and has not been changed. On Jul 27, 10:38 pm, goodtest goodtest...@gmail.com wrote: Are we sure there is no further regression bug in this new fix? On Jul 27, 7:14 pm, Doug Williams d...@twitter.com wrote: If you are still seeing errors you should check your code to ensure that you are sending the correct signature. Thanks, Doug On Mon, Jul 27, 2009 at 7:10 PM, winrich winric...@gmail.com wrote: mine broke too. i wonder though, i'm using the oauth python libraries On Jul 27, 6:35 pm, chinaski007 chinaski...@gmail.com wrote: Doug: Does this mean that Marcel made a fix for this? Or rather that we should examine our code to find the culprit? Thanks, Peter Bray On Jul 27, 6:24 pm, Doug Williams d...@twitter.com wrote: Updating you guys on this problem. A bug was reported off list that informed us we were not always verifying signatures. Today we shipped a fix for this problem which ensures that we are correctly verifying signatures. If you are still seeing invalid signature errors you should examine your code and ensure you are correctly signing requests as per the spec. Thanks, Doug On Mon, Jul 27, 2009 at 6:05 PM, Doug Williams d...@twitter.com wrote: Marcel is shipping a fix for this as I type. Thanks, Doug 2009/7/27 João Pereira joaomiguel.pere...@gmail.com Same here. On Tue, Jul 28, 2009 at 1:26 AM, goodtest goodtest...@gmail.com wrote: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst
[twitter-dev] Re: Twitpocalypse Announcement - 21:00 GMT
Just a heads up for British devs (and Matt) : The UK is currently in 'BST' (British Summer Time) - meaning that the Twitpocalypse will occur at 10PM. (GMT + 1) @kosso On Jun 12, 11:30 am, Matt Sanford m...@twitter.com wrote: Hello again, The responses to @twitterapi and all discussions internally show a preference to not waiting until the middle of the night. The current plan is to force this issue at 21:00 GMT (2:00pm Pacific/5:00pm Eastern for those in the US). This will let us make sure we have all staff available in the unlikely event something goes wrong on our end. We'll also be available when people who don't follow the twitter-dev- talk list start reporting errors. While we did warn developers about the Twitpocalypse I'm sorry we didn't think about setting a drop-dead date and scheduling this previously. We'll keep trying to improve on warnings like this. Good night, and good luck. Thanks; – Matt Sanford / @mzsanford Twitter Dev On Jun 12, 2009, at 10:23 AM, Matt Sanford wrote: Hi all, The overflow of the 32-bit signed integer value for status ids (a.k.a The Twitpocalypse [1]) is fast approaching. The current estimate is around tomorrow at around 11am GMT, or 3:00am Pacific time in the case of Twitter. There is some discussion internally about accelerating things so we'll be in the office and able to cope. Nobody is their freshest at 3:00am, not to mention it would be nice to not have apps broken throughout the weekend if one-person developer teams don't notice. No decision has been made yet but I wanted to get something out to you all so you know what's going on in the event we decide to do this. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] -http://www.twitpocalypse.com/
[twitter-dev] If your OAuth 'verify_credentials.xml' API just broke....
... they appear to have changed the call from a POST to a GET.
I didn't see an update/change about this.
So, in PHP use:
$to = new TwitterOAuth($consumer_key, $consumer_secret,
$twitterOAuthToken, $twitterOAuthSecret);
$content = $to-OAuthRequest('https://twitter.com/account/
verify_credentials.xml', array(), 'GET');
In the original example PHP scripts, the call was a POST, which used
to work. Until I saw the API returning 'this method requires a GET.'
this morning.
hth
[twitter-dev] OAuth application icon reset?
Hi, I have a Twitter OAuth application running successfully since yesterday and all was good. Today, the application icon I had uploaded in the settings page seems to have reverted back to the default 'cogs' icon. I this a known issue? I tried re-uploading to no avail. Many thanks for finally implementing OAuth! Great news! Regards, @kosso
