[twitter-dev] Requesting Whitelisting for Rate Limit
Hello! How often should you send a request to be whitelisted? I am finding that in the span of time while I'm waiting for an answer, the nature of my project has changed drastically. So I then resend a request. Does this affect whether you will be whitelisted or not? And should I wait for a rejection before rerequesting in the future? Thank you, - Cassie -- 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] Still Seeing things twice? Still Seeing things twice? Yes.
Hi everyone, I know Twitter says this was resolved (http://status.twitter.com/post/ 1258614492/seeing-things-twice-seeing-things-twice) but: Direct messages sent through the api are appearing twice for me on the receiver's end (but not for the sender). Is anyone else having this issue? I am confident that I am only sending them once, and this is reaffirmed by the fact that the sender appears to only have sent 1. Thanks! - Cassie -- 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: Still Seeing things twice? Still Seeing things twice? Yes.
Also as an update to this: I get emails when I am direct messaged, and I am only getting 1 email. On Oct 7, 2:39 pm, Cassie Lynn cassie.schwendi...@gmail.com wrote: Hi everyone, I know Twitter says this was resolved (http://status.twitter.com/post/ 1258614492/seeing-things-twice-seeing-things-twice) but: Direct messages sent through the api are appearing twice for me on the receiver's end (but not for the sender). Is anyone else having this issue? I am confident that I am only sending them once, and this is reaffirmed by the fact that the sender appears to only have sent 1. Thanks! - Cassie -- 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: Using @Anywhere under SSL
yet? Do we have any way of knowing when this might happen? And thanks for asking this here Justin! I asked on @anywhere and no one has replied (it has been almost a week). Thanks! - Cassie On Sep 20, 5:00 am, Tom van der Woerdt i...@tvdw.eu wrote: FYI, there's a Mailing List specifically for @Anywhere. The list you mailed to is the API developer list. http://groups.google.com/group/twitter-dev-anywhere To answer your question: no, there's no SSL version (yet). Tom On Mon, 20 Sep 2010 02:53:05 -0700 (PDT), Justin justin.realw...@gmail.com wrote: I would love to use the Connect with Twitter @Anywhere function but I would need to use it in a secure enviroment - that is under SSL. I first tried this when @Anywhere was first launched adn gave up thinking that perhaps it's a little too early? Having recently returned to it, I was disapointed to discover that the situation doesn't seem to have changed. Does anyone know if this is possible? Simply adding an s to http://platform.twitter.com/anywhere.jsdoesn't work, I wonder if there's another unpublished URL, or if Twitter have any plans to impliment this. I'd prefer to use @Anywhere over oAuth, but may not have a choice :-( Thanks Justin -- 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: Twitter button with custom URL shortener
Hello! I am creating my own tweet links as described at the bottom of http://dev.twitter.com/pages/tweet_button Through this method, I am not able to provide a 'data-url' attribute, and instead append url=myshorturl to the end of the share url. It comes up as a t.co url, and when I post it, it remains a t.co url. Also, I try to get around this by appending my short url to the end of the text= field, and setting url=, which makes the tweet display correctly. However, when I post it, it is converted to a a t.co url. Additionally, anything I tweet via the twitter.com/share url that has a url in it is shortened to the t.co url. Is there a way to use our own shortener for the custom share links? Thanks. - Cassie On Aug 17, 9:28 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/17/10 3:37 PM, romainst wrote: Hi everyone! I'm developer for a French News TV Channel, and as we already own a bit.ly Pro Entreprise account to have our own URL shortener with our domain, I just wanted to know if it were possible to deactivate t.co shortening on tweet buttons to keep our custom shortened URLs? Thanks! Regards, Romain You can't deactivate it but you can work around it by using the data-url attribute on your button and putting your URL in it. Tom
