[twitter-dev] Tweet button duplicating in ie8
Hi, all. I am having a problem with a retweet button that I added for a client (healthandwealth101.com). The problem occurs in ie8 if you click a blog post and then click the back button in your browser, the tweet button is duplicated (the duplicate tweet button is placed where the former facebook like button appeared). Any thoughts? Cheers, Brad -- 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: list members cursor is wrong
doh! Thanks, Matt, I should have diagnosed that myself. it's working
now.
much obliged.
Brad
On Sep 15, 6:15 pm, themattharris thematthar...@twitter.com wrote:
Hey Brad,
Your full request URL doesn't contain the cursor parameter. It looks
like when you add the OAuth parameters you are dropping the cursor
one.
We recommend, instead of using query string or the POST body for OAuth
paramters you instead use the authorisation header.
In your case this would mean your URL would be:
http://api.twitter.com/1/endlesscities/urban/members.json?cursor=1343...
and in your request headers you would have:
Authorization: OAuth oauth_consumer_key=MgdaAGLAt4VQzGKvoczhA,
oauth_nonce=68156293, oauth_signature=QkEP3%2BsCmz0C
%2FdjHJcdgUyTDbuI%3D, oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1284515562, oauth_token=18904533-
Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx, oauth_version=1.0
Hope that helps,
Matt
On Sep 14, 7:09 pm, Brad bdeg...@gmail.com wrote:
Thanks, Matt,
This is the full
requesthttp://api.twitter.com/1/endlesscities/urban/members.json?oauth_nonce...
doing a urllib.urlopen( ) on that.
This is the Python request object {'http_url': 'http://api.twitter.com/
1/endlesscities/urban/members.json?cursor=1343981850785981701',
'http_method': 'GET', 'parameters': {'oauth_nonce': '68156293',
'oauth_timestamp': 1284515562, 'oauth_consumer_key':
'MgdaAGLAt4VQzGKvoczhA', 'oauth_signature_method': 'HMAC-SHA1',
'oauth_version': '1.0', 'oauth_token': '18904533-
Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx', 'oauth_signature':
'QkEP3+sCmz0C/djHJcdgUyTDbuI='}}
I get results back, so the auth is working, but the cursor stays the
same.
thanks for whatever insight you can give.
On Sep 14, 10:37 am, Matt Harris thematthar...@twitter.com wrote:
GET works fine for this method and when I test the cursors for your
list below everything works correctly. So we can work out what is
going on can you share the headers you are sending to the API.
Also, you will want to update your URLs to the correct host. The
correct URL to use ishttp://api.twitter.com/1/--makingyour
request:
http://api.twitter.com/1/endlesscities/urban/members.json?cursor=-1
Best,
Matt
On Sun, Sep 12, 2010 at 6:44 PM, Brad bdeg...@gmail.com wrote:
maybe I'm doing something wrong, but the cursor returned from the list
members call seems to be misbehaving.
if I hit:
http://twitter.com/endlesscities/urban/members.json?cursor=-1
it returns
next_cursor:1343981850785981701, previous_cursor:0
if I pass it that new cursor:
http://twitter.com/endlesscities/urban/members.json?cursor=1343981850...
it returns the same thing:
next_cursor:1343981850785981701, previous_cursor:0
What's up with that? This has cropped up thanks to switching from
basic Auth to Oauth. I'm doing a GET because it won't allow me to do a
POST.
thanks in advance for any help.
--
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?hl=en
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
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?hl=en
[twitter-dev] Re: list members cursor is wrong
Thanks, Matt,
This is the full request
http://api.twitter.com/1/endlesscities/urban/members.json?oauth_nonce=84284551oauth_timestamp=1284515127oauth_consumer_key=MgdaAGLAt4VQzGKvoczhAoauth_signature_method=HMAC-SHA1oauth_version=1.0oauth_token=18904533-Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNxoauth_signature=05FtplBSA2OosDkvt5nDBKfmjxI%3D
doing a urllib.urlopen( ) on that.
This is the Python request object {'http_url': 'http://api.twitter.com/
1/endlesscities/urban/members.json?cursor=1343981850785981701',
'http_method': 'GET', 'parameters': {'oauth_nonce': '68156293',
'oauth_timestamp': 1284515562, 'oauth_consumer_key':
'MgdaAGLAt4VQzGKvoczhA', 'oauth_signature_method': 'HMAC-SHA1',
'oauth_version': '1.0', 'oauth_token': '18904533-
Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx', 'oauth_signature':
'QkEP3+sCmz0C/djHJcdgUyTDbuI='}}
I get results back, so the auth is working, but the cursor stays the
same.
thanks for whatever insight you can give.
On Sep 14, 10:37 am, Matt Harris thematthar...@twitter.com wrote:
GET works fine for this method and when I test the cursors for your
list below everything works correctly. So we can work out what is
going on can you share the headers you are sending to the API.
Also, you will want to update your URLs to the correct host. The
correct URL to use ishttp://api.twitter.com/1/-- making your
request:
http://api.twitter.com/1/endlesscities/urban/members.json?cursor=-1
Best,
Matt
On Sun, Sep 12, 2010 at 6:44 PM, Brad bdeg...@gmail.com wrote:
maybe I'm doing something wrong, but the cursor returned from the list
members call seems to be misbehaving.
if I hit:
http://twitter.com/endlesscities/urban/members.json?cursor=-1
it returns
next_cursor:1343981850785981701, previous_cursor:0
if I pass it that new cursor:
http://twitter.com/endlesscities/urban/members.json?cursor=1343981850...
it returns the same thing:
next_cursor:1343981850785981701, previous_cursor:0
What's up with that? This has cropped up thanks to switching from
basic Auth to Oauth. I'm doing a GET because it won't allow me to do a
POST.
thanks in advance for any help.
--
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?hl=en
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
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?hl=en
[twitter-dev] list members cursor is wrong
maybe I'm doing something wrong, but the cursor returned from the list members call seems to be misbehaving. if I hit: http://twitter.com/endlesscities/urban/members.json?cursor=-1 it returns next_cursor:1343981850785981701, previous_cursor:0 if I pass it that new cursor: http://twitter.com/endlesscities/urban/members.json?cursor=1343981850785981701 it returns the same thing: next_cursor:1343981850785981701, previous_cursor:0 What's up with that? This has cropped up thanks to switching from basic Auth to Oauth. I'm doing a GET because it won't allow me to do a POST. thanks in advance for any help. -- 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?hl=en
Re: [twitter-dev] Re: Open Source Android/Twitter Application
Clay, I've been waiting for it too! Hopefully they don't back out of the promise. Regards, Brad Bosley On Fri, Aug 13, 2010 at 6:07 PM, Clay Graham claytan...@sightlyinc.com wrote: Ed, Thanks for the advice. I have emailed Tim directly, no reply. Will keep trying. Can I be the only one who is hungry for this? Clay
[twitter-dev] Re: @replies missing
Hey John - Thanks for the update, though it appears that it's not only a matter of latency. Some users are reporting that their replies are missing entirely. On Jul 4, 3:25 pm, John Kalucki j...@twitter.com wrote: The mentions timelines were updating with additional latency, perhaps a few minutes, for about a day, but they were updating. They should be updating in near real time now. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, Jul 4, 2010 at 1:16 PM, Naveen Ayyagari nav...@getsocialscope.comwrote: Hello, Hoping we can get post on status.twitter.com about @replies not showing up... We have been getting a lot of reports that they are missing, and a quick twitter search seems to indicate it is not limited to our application. http://search.twitter.com/search?had_popular=trueq=repliesresult_ty...
[twitter-dev] Have you read the OneForty.com Developer Contract?
There has been a lot of buzz around OneForty.com and what it will mean for all of us Twitter app developers. However, some of the things in their developer contract (that you have to agree to in order to claim your application on their side) gave us (Squeejee) pause after we decided to read the fine print. Please see read the contract for yourself (http://oneforty.com/terms/ publisher_contract), see our blog post with our concerns (http:// squeejee.com/blog/2009/10/08/questions-for-oneforty) and leave your comments! Laura Fitton, the founder of oneforty.com, has been very receptive and wants to engage in open dialogue about the contract. Please add to the discussion!
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
wow, somehow managed to totally miss that thread... thanks! On Oct 8, 6:07 pm, Dewald Pretorius dpr...@gmail.com wrote: There's another thread herehttp://bit.ly/Owfvdwhere the developer contract also raised some eyebrows. Dewald On Oct 8, 7:25 pm, brad...@squeejee.com brad...@praexis.com wrote: There has been a lot of buzz around OneForty.com and what it will mean for all of us Twitter app developers. However, some of the things in their developer contract (that you have to agree to in order to claim your application on their side) gave us (Squeejee) pause after we decided to read the fine print. Please see read the contract for yourself (http://oneforty.com/terms/ publisher_contract), see our blog post with our concerns (http:// squeejee.com/blog/2009/10/08/questions-for-oneforty) and leave your comments! Laura Fitton, the founder of oneforty.com, has been very receptive and wants to engage in open dialogue about the contract. Please add to the discussion!
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
I am reposting the @oneforty response to my blog post here for the benefit of everyone: --- Hey everyone, thank you for taking the time to help us better understand and better serve the developer community. We read this and shared it with our investors, advisors and even our @oneforty and @pistachio Twitter readers. We're glad this conversation about the contract is happening. We've been trying to gather feedback via our developer alpha this summer and the Twitter API developers list. We're listening earnestly. We especially want to get this contract right before we start pilot tests that will let developers sell directly on oneforty. There's also a bunch of things you didn't raise (others have) that we're changing. just a few of them: -We already killed the we get a share of offsite sales clause -We are seriously reexamining how to improve the minimum payments threshold and time delay before payments get sent out -We're changing the cancellation terms These -- and quite a few other -- things are being actively reevaluated. We know it's lame to hear we're working on it as our main answer to you right now, but that's the plain truth. Quick specifics on what you raised: 2.1 Needs to be more clearly expressed what this even means. This unclear language confused at least one developer into thinking our model is royalty based (it's not) and that all payments would be made to developers as donations/gifts instead of regular income (they're not going to be) 2.2 Trial versions should only apply to trial versions distributed through us. Not ANY trial version you ever share. 3.2 We're not trying to force you to provide phone support, so we need to rewrite that 4.0 FEES - we agree we need much more explanation and support around how we imagine all of this working 5.2 We need to work out fair terms under which the customer relationship gets shared. What's in the contract now ain't it yet. We'd particularly love to hear your concerns about sharing the relationship with the customer fairly. (ie, the part about not contacting them in any way except to provide support.) That's a tough one to figure out. Whatever we end up with needs to protect developers, oneforty and honor oneforty community privacy expectations. We feel strongly that the marketplace needs to grow as a partnership between oneforty and the communities it serves. More on why we feel this way, from our FAQ http://oneforty.com/pages/faq#developers What if I disagree with the terms of the developer contract? Tell us. We're here to cultivate and serve a community in which everybody thrives. If our terms preclude that, we're not doing our jobs, and we want to know it. We rely heavily on feedback from the developer community Thanks for opening up this dialog and we look forward to more of it. Warmly, Laura, Mike, Michael Robby (@oneforty) Laura Fitton (@pistachio) Mike Champion (@graysky) Michael Macasek (@macasek) Robby Grossman (@freerobby)
[twitter-dev] Re: Don't take twitter down for maintenance today!
On Mon, Jun 15, 2009 at 10:54 AM, Christian Plesner Hansenples...@quenta.org wrote: It's critical that #iranelection stays up. Take a look at what people are posting to @Twitter about this. If you read the Twitter Status blog about this maintenance period (http://status.twitter.com/post/124145031/maintenance-window-tonight-9-45p-pacific) you'd know that Twitter can't control the timing of this, so asking them to change it probably won't get you anywhere. Brad.
Re: IP ranges from The Planet will be blocked
On Jan 6, 8:52 am, Alex Payne a...@twitter.com wrote: I've put our operations staff in touch with someone from The Planet. We'll see what happens! I realize it's only been three days, but has there been any movement on this issue? I just discovered that my host is at The Planet and was contemplating deploying an app sometime soon...
