[twitter-dev] Re: Possible to find out how many people have see a tweet?
I would guess finding retweets of a given tweet would have a similar api call. The documentation at http://dev.twitter.com/doc/get/statuses/retweets/:id states it will return up to 100 of the first retweets of a given tweet. - Mohan -- 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: Access tokens changing on their own?
There's an open issue about this: http://code.google.com/p/twitter-api/issues/detail?id=2197 -- 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] Update Limit reached... alternatives/suggestions?
Hi Twitter-developers, I'm kind of a twitter-api-newby trying to use this rest-api in a oauth- enabled server app to send out (too) many updates/tweets. The application is for swim-meets, where we wanted to send out the swimmers' events, like signed-up event# with associated info, heat and lane info as they become available, and results of the race as they become available. This info is tweeted out from one account such that the participants and relatives/friends can easily get that information on their smart- phones by following or searching the tweets and without having to go to print-outs that are taped on the wall. As we have a few hundred swimmers, possibly 50+ events, 4-8 heats, 6-8 lanes... lots of tweets... and I was hitting this update limit after the first test case after about 40-50 tweets. The idea for the app seemed so neat and twitter seemed such a natural vehicle to spread this info...but all the twitter-docs about these update limits seem to indicate that our current set-up simply won't work with twitter. Any advice/suggestions to get this somehow to work is greatly appreciated. Regards, FrankS. -- 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] Stream API and OAuth
Twitter Stream API supports OAuth login now and no username and password? -- 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] Is there api for invite friend?????????????
Hi Everyone, Hoping you guy's doing there. It is my first mail and i am newbie in this google mail group. Might be my question is silly OR obvious , But i am not able to figure out my problem. I want to add invite friend in my RUBY ON RAILS project like facebook(http://developers.facebook.com/docs/reference/ dialogs/requests/). Is it possible on twitter.??? if yes then give me like of API. I am aware about Follow Button and tweetbutton API. But i want some improvement in tweetbutton API. There should be selection button for select followers to whom my tweet will visible. IF it possible then, how will i achieve this. any suggestion will be appreciated . Thanks for giving your great time. + Pravin Mishra -- 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] Query based on the number of followers
Is it possible to get a list of all Twitter Users who have more than 2000 followers (or some number) with an API or any other easy way? I have been doing a lot of research from a long time but could not find a easy answer. Really appreciate if some one can throw a hint! -- 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] Query based on the number of followers
Hi Venu, There aren't any API methods that return this kind of ranked information provided by Twitter. Thanks, @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jun 28, 2011 at 5:41 AM, Venu ven...@gmail.com wrote: Is it possible to get a list of all Twitter Users who have more than 2000 followers (or some number) with an API or any other easy way? I have been doing a lot of research from a long time but could not find a easy answer. Really appreciate if some one can throw a hint! -- 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] Is there api for invite friend?????????????
There's nothing explicit like the function Facebook has. Instead, you could encourage the user to craft a tweet @mentioning their friend that they would recommend the product to and instead of your app sending the invite the user would send the invite from their own account. The Tweet Button/Tweet Web Intent are great for this purpose as it allows you to pre-prepare the text and the user still retains control over the message they actually send. The Tweet Button is documented here: http://dev.twitter.com/pages/tweet_button and the Tweet Web Intent can be read about here: http://dev.twitter.com/pages/intents#tweet-intent If you have/want or more rich Twitter API integration, you could use the API to accomplish this instead. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jun 28, 2011 at 5:16 AM, Pravin Mishra pravin.mis...@startupsourcing.com wrote: Hi Everyone, Hoping you guy's doing there. It is my first mail and i am newbie in this google mail group. Might be my question is silly OR obvious , But i am not able to figure out my problem. I want to add invite friend in my RUBY ON RAILS project like facebook(http://developers.facebook.com/docs/reference/ dialogs/requests/). Is it possible on twitter.??? if yes then give me like of API. I am aware about Follow Button and tweetbutton API. But i want some improvement in tweetbutton API. There should be selection button for select followers to whom my tweet will visible. IF it possible then, how will i achieve this. any suggestion will be appreciated . Thanks for giving your great time. + Pravin Mishra -- 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] Stream API and OAuth
The parts of the Streaming API on stream.twitter.com support both three-legged OAuth (an access token is required for the account attempting to connect) or basic auth (username and password). Other parts of the Streaming API like User Streams and Site Streams are OAuth-only. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jun 28, 2011 at 12:03 AM, Tudor Claudiu Florea tudor.claudiu.flo...@gmail.com wrote: Twitter Stream API supports OAuth login now and no username and password? -- 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] New permission level enforcement happens this Thursday (30th June)
Hey everyone,
Just a quick reminder that we'll be enforcing the new permission level this
Thursday, 30th June.
When we enforce the new permission level Read (R) and Read Write (RW)
access tokens will be unable to use the following API methods:
/1/direct_messages.{format}
/1/direct_messages/sent.{format}
/1/direct_messages/show.{format}
/1/direct_messages/destroy.{format}
Any requests made to those endpoints with R or RW tokens will receive an
HTTP 403 Forbidden error with the response body:
{errors:[{code:93,message:This application is not allowed to
access or delete your direct messages}]}
Some key points
* If you do not need to read or delete a user's direct messages you do not
need to do anything. You can always ask a user to reauthorize at a greater
permission level.
* Existing tokens will still work but only those with Read, Write, and
Direct Messages access will be able to read and delete direct messages.
* Read Write access tokens can still send direct messages.
* You can verify the permission level of the token you are using by
inspecting the X-Access-Level header. This header is included when a
successful OAuth request is made to the API.
* When a user reauthorizes your application at the Read, Write, and Direct
Messages (RWD) level, the oauth_token returned by the
https://api.twitter.com/oauth/access_tokenrequest will be different than the
one you already have. This is because we issue new tokens whenever the
permission level is changed. If the permission level is the same the token
is not recreated, e.g. you have an RWD token and you ask the user to
reauthorize at RWD level, you will get the existing token back. If you have
an RW token and you ask the user to reauthorize at RWD level, you will get a
new token back.
Recently there was a question on the mailing list about how to inform users
of the new permission level. Ultimately the method you choose is up to you
and the opportunities and information your application or service provides.
Some applications would prefer to be proactive, whilst others can be
reactive. Which your preferred approach below are a a few suggestions we
have seen or heard other developers will do:
* On your first attempt to read direct messages that responds with an error,
display a helpful message indicating the application cannot read the direct
messages until the user has reauthorized.
* On their first use of your updated application or service, prompt them to
reauthorize.
* If you know the email address of the users of your app send a message
about the new permission and link to our blog post (
http://blog.twitter.com/2011/05/mission-permission.html)
* Send a Tweet as the account that represents your application. This Tweet
can let users know an update is available for the application to accomodate
the new permission level on Twitter.
* Add a blog post on your application or services homepage about the new
permission level and what it means for your applications.
* Prepare a support response or FAQ entry that you can give to users if they
contact you saying they cannot access their direct messages anymore
In case you missed any of the previous emails or questions we've compiled an
overview page and FAQ on our developer resources site:
* https://dev.twitter.com/pages/application-permission-model
* https://dev.twitter.com/pages/application-permission-model-faq
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, 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-dev] One news feed inc twitter and our own new database
Instead of our news page having two feeds, one from our own database for the news and another from twitter, I would like to consolidate the two, preferably in date order, newest at the top. Can I do that with the twitter api? I guess I would need to create an array containing news items and twitter items, put them together then output on the page. To easily distinguish between the two I would colour code them. -- 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: Recipe for getting Follow button working on an https website?
Hi Taylor, The same problem occurs with the Tweet button on SSL-based sites: Google Chrome refuses to show the tweet button, instead showing a bright red warning, Firefox likewise but shows just an empty light- gray box where the button would have been etc. The reason appears to be that the js code loads the button imagery from the Akamai content distribution network rather than a Twitter domain. Cheers, @vinsci On Jun 20, 3:36 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Rob, The Follow Button doesn't yet support SSL -- only unencrypted HTTP, which is why you get this error when trying to use the Follow Button on a SSL-based site. We'll let everyone know when SSL support arrives for the Follow Button and Tweet Button. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Fri, Jun 17, 2011 at 9:32 AM, Rob robert.osbo...@gmail.com wrote: I'm trying to add a follow or tweet button to a site that uses https by default. My choices appear to be scare my users with a insecure content on page or, if I change the url tohttps://platform.twitter.com/, an invalid certificate error. Is there an easy recipe for this? Google reveals hacks like copy everything local. Why doesn'thttps://platform.twitter.com/have a valid certificate? -- 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] 401 Unauthorized in Python/Twisted app
Hi Taylor, Thank you for your response. Originally, I did forget to add an oauth_timestamp field. I've since included one, but still have the same problem. I modified my app to dump out the base string. Here's what I got: GEThttps%3A%2F%2Fuserstream.twitter.com%2F2%2Fuser.jsondelimited%3Dlength%26oauth_nonce%3D05963995484855701581311629784779%26oauth_timestamp%3D1309276024%26oauth_version%3D1.0 Does that look right? Eryn On 2011-06-27, at 08:10, Taylor Singletary wrote: Hi Eryn, I'm not too familiar with the Twisted framework or its implementation of OAuth, so take what I recommend with a grain of salt. * Access tokens generated through the OAuth flow on Twitter, regardless of the technique used (PIN code, xAuth, vanilla OAuth) are long-lived and do not expire until the end-user makes an explicit effort to revoke the access. You store the access token and access token secret. * While OAuth in theory should just work when it works in one spot, there's a great amount of variation in the amount of wrongness that given services will tolerate when evaluating the credentials. Long- term, we're working to normalize the entire validation procedure across all of our services, but in reality the streaming API and the REST API use different OAuth engines to evaluate the validity of the request -- the streaming API's OAuth verification is considerably stricter than the REST API's more forgiving implementation. * I notice that your authorization header is missing a oauth_timestamp parameter -- is that a copy and paste error? Do you know how to locate the OAuth signature base string in the Python library you are using -- it can often be buried under private or protected methods but the string is invaluable in debugging issues like this. Thanks, Taylor On Jun 24, 7:54 pm, Eryn Wells e...@3b518c.com wrote: Hello all, I'm quite new to OAuth and the Twitter API, and this is my first post to this list. I'm working on an app in Python using the Twisted framework. It uses brosner's fork of python-oauth2[1] to do the initial authentication and subsequent request signing. I'm using the PIN code flow for authentication. Do access tokens need to be generated every time you start the app, or can they be stored between runs and reused? If so, how long are the valid? Right now, my code writes the access token and secret out to a file and recovers it the next time it starts. The procedure seems to go just fine – I don't get any errors – but I can't really verify that everything is Correct because I don't really know what I'm looking for… Second thing, I'm at the point where I'm trying to do the initial connection tohttps://userstream.twitter.com/2/user.json. I'm using SSLConnect and web.HTTPClient, if that helps… I write out the command (GET url), and the headers (a Host and an Authorization header). The OAuth library generates the following Authorization header content. I get back a 401 Unauthorized error with a WWW-Authenticate: Basic header. I've heard from @twitterapi that User Streams require OAuth, so why am I getting a Basic auth response? OAuth realm=Firehose, oauth_nonce=25622603816219309853125867384777, oauth_consumer_key=cut, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_token=cut, oauth_signature=1AV5YG4DsfCV4jDoQcOCOmxZ2Gw%3D Anything obvious there that I'm doing wrong? Thanks, Eryn -- 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] Site Streams
We've gone live with Site Streams for paying customers of our TweetRoost product. I wrote a blog with technical details which some people might find interesting. See it at http://www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-site-streams/ -- it is not a product blog or a pitch :) (and I am a big fan of Site Streams, it was a great project for us to implement) Mark Krieger President @mediaroost -- 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] 503 response on API calls
Hi, just wondering if anyone can advise my on the following. If I request this URL from the twitter API... https://api.twitter.com/1/followers/ids.json?user_id=194615674 ... then I will receive JSON in the response. However If I request the same API call but for a more popular account ID https://api.twitter.com/1/followers/ids.json?user_id=34613288 ... then I get the 503 error and the twitter is over capacity page. Can anyone provide some information on why I'm experiencing this? I'm using OAuth but it's not required for the call and I get the same behaviour whether I authenticate or not. - Tom -- 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] /oauth/request_token - Can't get one
First off, i'm uncertain which keys i can and can not post, so i'll
obscure them.
My main problem is that i don't know which keys to send to the
request_token.
Here is that i'm trying to send:
(Note: time matches the servers, i've made sure of that)
(Note: I have checked so that _all_ my keys are correct)
(Note: I've also made sure that the signature matches up to my content
of POST)
POST /oauth/request_token HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth oauth_nonce=1309272106, oauth_callback=,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1309272106,
oauth_consumer_key=pk...8pw, oauth_token=,
oauth_signature=T5...5pQ%3D, oauth_version=1.0
User-Agent: InetCheck
Host: api.twitter.com
Keep-Alive: 115
Content-Length: 171
oauth_callback=oauth_consumer_key=pk...
8pwoauth_nonce=1309272106oauth_signature_method=HMAC-
SHA1oauth_timestamp=1309272106oauth_token=oauth_version=1.0
After tat i recive either Failed to validate oauth signature and
token or just a 401 return code.
I'm trying to get my hands dirty here by developing my own API for
Python.
I know there are some out there but i don't like em + i don't trust
other people.
So i'm running Python2.6.5
And i'm using the modules:
from socket import *
from time import time, gmtime
from random import randint
import base64
import hashlib
import hmac
import urllib
(i know, you're not supposed to do from m import * but i'm just
making some basic code for a skeleton atm).
The code to generate the header + POST data:
(again, just a skeleton, ugly code, will be fixed when i got a working
copy)
dstr = ''
if data:
dstr += ''
for k in ('oauth_callback', 'oauth_consumer_key',
'oauth_nonce',
'oauth_signature_method', 'oauth_timestamp', 'oauth_token',
'oauth_version'):
if not k in data: raise KeyError(Missing + k
+ , please
specify it at the login)
dstr += k + '=' + data[k] + ''
dstr = dstr[:-1]
secr = self.keySet[1]
sign_key_base = 'POST' + '' + urllib.quote_plus('http://
api.twitter.com/oauth/request_token') + ''
sign_key_base += urllib.quote_plus(dstr)
print 'Using sign base:'
print '\t' + sign_key_base + '\n'
print '\t Key:'
print '\t\t', [data['consumer_secret'] + '']
print '\t\t', [hmac.new(data['consumer_secret'] + '',
sign_key_base, hashlib.sha1).digest()]
print '\t\t',
[base64.encodestring(hmac.new(data['consumer_secret']
+ '', sign_key_base, hashlib.sha1).digest())]
secr =
urllib.quote(base64.encodestring(hmac.new(data['consumer_secret'] +
'', sign_key_base, hashlib.sha1).digest()).replace('\n', ''))
print '\t\t', [secr], '\n'
ret = 'POST ' + URL + ' HTTP/1.1\r\n'
ret += 'Content-Type: application/x-www-form-urlencoded\r\n'
ret += 'Authorization: OAuth oauth_nonce=' +
data['oauth_nonce'] +
', '
ret += 'oauth_callback=' + data['oauth_callback'] + ', '
ret += 'oauth_signature_method=HMAC-SHA1, '
ret += 'oauth_timestamp=' + data['oauth_nonce'] + ', '
ret += 'oauth_consumer_key=' + data['oauth_consumer_key'] +
', '
ret += 'oauth_token=' + data['oauth_token'] + ', '
ret += 'oauth_signature=' + secr + ', '
ret += 'oauth_version=1.0\r\n'
ret += 'User-Agent: InetCheck\r\n'
ret += 'Host: ' + host + '\r\n'
ret += 'Keep-Alive: 115\r\nContent-Length: ' + str(len(dstr)) +
'\r\n
\r\n' + dstr
Please help me, it's getting on my nerves this oAuth stuff,
really never ever came in contact with it until Twitter, sure it looks
like a good security implementation but atm i don't like it :/
Any help is apritiated.
Also, validated my oauth_signature and content via:
http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
Everyting matches up against what i'm sending to the server.
So if Twitter follows that standard it should all be good.
I don't know tho if i should skip oauth_callback since it's an empty
string anyways, or if i should skip oauth_token because i don't have
one (also a empty string).
--
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: Query based on the number of followers
Hi Taylor, Thanks a bunch for the answer. You saved a lot of my time. Is it possible to do this in any other way??? Even if it is time taking! Thanks again. Venu. On Jun 28, 3:16 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Venu, There aren't any API methods that return this kind of ranked information provided by Twitter. Thanks, @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jun 28, 2011 at 5:41 AM, Venu ven...@gmail.com wrote: Is it possible to get a list of all Twitter Users who have more than 2000 followers (or some number) with an API or any other easy way? I have been doing a lot of research from a long time but could not find a easy answer. Really appreciate if some one can throw a hint! -- 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] Pixelated Avatar and Twitter Logo
Hello, Does anyone know why I am getting pixelation on my website with the integrated Twitter Feed? www.bucycling.com Please help. -Robert -- 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] Pixelated Avatar and Twitter Logo
Hi Robert,
You website stylesheet includes this rule:
#home_main_right img {
width: 150px;
height: 150px;
}
This rule is telling the webpage to render the img's at the 150x150
resolution and is the reason for the images in the widgets being pixelated.
To resolve the issue you should restrict the scope of that CSS rule by
adding something like a class on the img you want to be 150x150
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Tue, Jun 28, 2011 at 11:58 AM, Robert Winnett winnett2...@gmail.comwrote:
Hello,
Does anyone know why I am getting pixelation on my website with the
integrated Twitter Feed?
www.bucycling.com
Please help.
-Robert
--
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] Pixelated Avatar and Twitter Logo
On Tue, Jun 28, 2011 at 1:58 PM, Robert Winnett winnett2...@gmail.com wrote: Hello, Does anyone know why I am getting pixelation on my website with the integrated Twitter Feed? www.bucycling.com Something else - I noticed that the home page loads slowly because the header picture is 4703.21 KB (4816086 bytes). That is HUGE. For faster loading, try reducing the image filesize to 24-32 kb. -- 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: /oauth/request_token - Can't get one
After talking with a nice guy at the IRC channel he mentioned that i
needed to sort my headers and my POST data.
Sad and done, i sorted my things but still didn't help, any other
suggestions?
Here's a output (readable version) of my HEAD+POST:
http://pastebin.com/H8uSuEd0
On Jun 28, 5:31 pm, DoXiD anton.do...@gmail.com wrote:
First off, i'm uncertain which keys i can and can not post, so i'll
obscure them.
My main problem is that i don't know which keys to send to the
request_token.
Here is that i'm trying to send:
(Note: time matches the servers, i've made sure of that)
(Note: I have checked so that _all_ my keys are correct)
(Note: I've also made sure that the signature matches up to my content
of POST)
POST /oauth/request_token HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth oauth_nonce=1309272106, oauth_callback=,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1309272106,
oauth_consumer_key=pk...8pw, oauth_token=,
oauth_signature=T5...5pQ%3D, oauth_version=1.0
User-Agent: InetCheck
Host: api.twitter.com
Keep-Alive: 115
Content-Length: 171
oauth_callback=oauth_consumer_key=pk...
8pwoauth_nonce=1309272106oauth_signature_method=HMAC-
SHA1oauth_timestamp=1309272106oauth_token=oauth_version=1.0
After tat i recive either Failed to validate oauth signature and
token or just a 401 return code.
I'm trying to get my hands dirty here by developing my own API for
Python.
I know there are some out there but i don't like em + i don't trust
other people.
So i'm running Python2.6.5
And i'm using the modules:
from socket import *
from time import time, gmtime
from random import randint
import base64
import hashlib
import hmac
import urllib
(i know, you're not supposed to do from m import * but i'm just
making some basic code for a skeleton atm).
The code to generate the header + POST data:
(again, just a skeleton, ugly code, will be fixed when i got a working
copy)
dstr = ''
if data:
dstr += ''
for k in ('oauth_callback', 'oauth_consumer_key',
'oauth_nonce',
'oauth_signature_method', 'oauth_timestamp', 'oauth_token',
'oauth_version'):
if not k in data: raise KeyError(Missing +
k + , please
specify it at the login)
dstr += k + '=' + data[k] + ''
dstr = dstr[:-1]
secr = self.keySet[1]
sign_key_base = 'POST' + '' + urllib.quote_plus('http://
api.twitter.com/oauth/request_token') + ''
sign_key_base += urllib.quote_plus(dstr)
print 'Using sign base:'
print '\t' + sign_key_base + '\n'
print '\t Key:'
print '\t\t', [data['consumer_secret'] + '']
print '\t\t', [hmac.new(data['consumer_secret'] + '',
sign_key_base, hashlib.sha1).digest()]
print '\t\t',
[base64.encodestring(hmac.new(data['consumer_secret']
+ '', sign_key_base, hashlib.sha1).digest())]
secr =
urllib.quote(base64.encodestring(hmac.new(data['consumer_secret'] +
'', sign_key_base, hashlib.sha1).digest()).replace('\n', ''))
print '\t\t', [secr], '\n'
ret = 'POST ' + URL + ' HTTP/1.1\r\n'
ret += 'Content-Type: application/x-www-form-urlencoded\r\n'
ret += 'Authorization: OAuth oauth_nonce=' +
data['oauth_nonce'] +
', '
ret += 'oauth_callback=' + data['oauth_callback'] + ', '
ret += 'oauth_signature_method=HMAC-SHA1, '
ret += 'oauth_timestamp=' + data['oauth_nonce'] + ', '
ret += 'oauth_consumer_key=' + data['oauth_consumer_key'] +
', '
ret += 'oauth_token=' + data['oauth_token'] + ', '
ret += 'oauth_signature=' + secr + ', '
ret += 'oauth_version=1.0\r\n'
ret += 'User-Agent: InetCheck\r\n'
ret += 'Host: ' + host + '\r\n'
ret += 'Keep-Alive: 115\r\nContent-Length: ' + str(len(dstr))
+ '\r\n
\r\n' + dstr
Please help me, it's getting on my nerves this oAuth stuff,
really never ever came in contact with it until Twitter, sure it looks
like a good security implementation but atm i don't like it :/
Any help is apritiated.
Also, validated my oauth_signature and content
via:http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
Everyting matches up against what i'm sending to the server.
So if Twitter follows that standard it should all be good.
I don't know tho if i should skip oauth_callback since it's an empty
string anyways, or if i should skip oauth_token because i don't have
one (also a empty string).
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Re: [twitter-dev] Pixelated Avatar and Twitter Logo
Hey Matt,
Do you know what size the Twitter Logo is suppose to be??
-Robert
On Tue, Jun 28, 2011 at 3:10 PM, Matt Harris thematthar...@twitter.comwrote:
Hi Robert,
You website stylesheet includes this rule:
#home_main_right img {
width: 150px;
height: 150px;
}
This rule is telling the webpage to render the img's at the 150x150
resolution and is the reason for the images in the widgets being pixelated.
To resolve the issue you should restrict the scope of that CSS rule by
adding something like a class on the img you want to be 150x150
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Tue, Jun 28, 2011 at 11:58 AM, Robert Winnett winnett2...@gmail.comwrote:
Hello,
Does anyone know why I am getting pixelation on my website with the
integrated Twitter Feed?
www.bucycling.com
Please help.
-Robert
--
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] Pixelated Avatar and Twitter Logo
Hi Matt,
Wow... why didnt I think of that. I did not develop the theme but damn I
should have known.
Thank you! Ill fix that right away.
-Robert
On Tue, Jun 28, 2011 at 3:10 PM, Matt Harris thematthar...@twitter.comwrote:
Hi Robert,
You website stylesheet includes this rule:
#home_main_right img {
width: 150px;
height: 150px;
}
This rule is telling the webpage to render the img's at the 150x150
resolution and is the reason for the images in the widgets being pixelated.
To resolve the issue you should restrict the scope of that CSS rule by
adding something like a class on the img you want to be 150x150
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Tue, Jun 28, 2011 at 11:58 AM, Robert Winnett winnett2...@gmail.comwrote:
Hello,
Does anyone know why I am getting pixelation on my website with the
integrated Twitter Feed?
www.bucycling.com
Please help.
-Robert
--
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-dev] Re: Introduce yourself!
Hi everyone this is Anirup.I am a wannabe computer programmer.I a PhD student in Computer Science.Just completed my Bachelors. I mainly work in LAMP environment.Also I love jquery.If I wasn't doing my PhD,my motto would have been people who don't do PhD do PHP. I developed http://heybuddy.in/ http://heybuddy.in/%20using twitter and facebook api because I wanted my updates to appear on both the sites. I mainly work with opensource software and believe in opensource ideology http://heybuddy.in/ http://heybuddy.in/ https://github.com/anirupdutta (Recently put up some of my code on github) http://community.elgg.org/pg/plugins/developer/anirupdutta (Some of the plugins that I wrote for elgg) -- 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] Feedback wanted on Twitter + iOS
Hey all, With iOS 5 and the Twitter integration coming in a few months, we have been getting a ton of inbound interest and questions around how to effectively leverage the Twitter integration. We wanted to get your feedback on how we can best support you and your users in developing meaningful experiences. I also hope you have had a chance to dig into the documentationhttps://developer.apple.com/library/prerelease/ios/#documentation/Twitter/Reference/TwitterFrameworkReference/_index.html%23//apple_ref/doc/uid/TP40011014and watch the WWDC session videohttps://deimos.apple.com/WebObjects/Core.woa/BrowsePrivately/adc.apple.com.8270634034.08270634040.8367260933?i=1372307634 . We've heard that it would be helpful for us to provide some standard graphics for use with your upcoming iOS integrations. We wanted to understand what types of buttons and styles would be most helpful. We think the most common use case is going to be Sign in with Twitter (SSO) but let us know what formats would be helpful. The two use cases that we're hearing the most interest around are: 1. Instant personalization - frictionless Single Sign-on (SSO) and social graph will allow apps to provide a personalized experience to their users with one click. What things can we provide to make this more effective for you. 2. Distribution - using the build-in Tweet Sheet functionality to post great content from your app out to the Twitter stream where it will drive engagement and clicks back to your application. Let us know if there are any other resources that would help make your Twitter iOS integrations easier on you or help you provide more value to your users on iOS. We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Ryan -- Ryan Sarver @rsarver https://twitter.com/intent/follow?screen_name=rsarver -- 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] Feedback wanted on Twitter + iOS
Ryan, On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote: We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Simple, open up access to DMs via the API. --- Paul Haddad paul.had...@gmail.com, p...@tapbots.com, p...@pth.com -- 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] Feedback wanted on Twitter + iOS
Ryan, On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote: We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Simple, open up access to DMs via the API. This. l8r Sean -- 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] Feedback wanted on Twitter + iOS
First of all, I think Twitter should make it more clear that this implementation is focused on providing Twitter access for non-client apps. Think of this implementation as a 'post on Twitter' feature that doesn't require any API knowledge or other very complicated stuff. That, and you have the ability to get some information about the user. I think it would be a very bad thing if this gave the app DM level access as that kind of access is either abused or for client apps and this framework isn't for either of those. What I noticed while studying the framework (and I'll avoid violating the Apple NDA here) is that the requests are signed using a fixed pair of credentials and always say 'from iOS'. It would be very nice to be able to make that say something like 'from appname on iOS' or something. I think that a LOT of devs are going to ask for that. I have some other ideas but they are improvements over the current framework and if I posted them on a public list I'd have to shoot you ;-) Tom On Jun 29, 2011, at 1:44 AM, Ryan Sarver rsar...@twitter.com wrote: Hey all, With iOS 5 and the Twitter integration coming in a few months, we have been getting a ton of inbound interest and questions around how to effectively leverage the Twitter integration. We wanted to get your feedback on how we can best support you and your users in developing meaningful experiences. I also hope you have had a chance to dig into the documentation and watch the WWDC session video. We've heard that it would be helpful for us to provide some standard graphics for use with your upcoming iOS integrations. We wanted to understand what types of buttons and styles would be most helpful. We think the most common use case is going to be Sign in with Twitter (SSO) but let us know what formats would be helpful. The two use cases that we're hearing the most interest around are: 1. Instant personalization - frictionless Single Sign-on (SSO) and social graph will allow apps to provide a personalized experience to their users with one click. What things can we provide to make this more effective for you. 2. Distribution - using the build-in Tweet Sheet functionality to post great content from your app out to the Twitter stream where it will drive engagement and clicks back to your application. Let us know if there are any other resources that would help make your Twitter iOS integrations easier on you or help you provide more value to your users on iOS. We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Ryan -- Ryan Sarver @rsarver -- 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] Feedback wanted on Twitter + iOS
Absolutely disagree. No DM access via twitter.framework. Would be a major threat to the user's privacy. Tom On Jun 29, 2011, at 2:05 AM, Sean Heber s...@spiffytech.com wrote: Ryan, On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote: We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Simple, open up access to DMs via the API. This. l8r Sean -- 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: Feedback wanted on Twitter + iOS
Ability to access DMs, with a system-supplied modal dialog (a la the Location Services dialog), would be ideal. Steve -- 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] Feedback wanted on Twitter + iOS
On Jun 28, 2011, at 7:09 PM, Tom van der Woerdt wrote: Absolutely disagree. No DM access via twitter.framework. Would be a major threat to the user's privacy. This could be handled by different wording on the Alert Panel that asks for permission, or by app id white listing or probably a handful of other solutions. If this framework is supposedly only going to be used for non client applications then can we assume that Twitter for IOS won't have access to it either? --- Paul Haddad paul.had...@gmail.com, p...@tapbots.com, p...@pth.com -- 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: Feedback wanted on Twitter + iOS
Simple - Access to read/write direct messages, and just have a HIG rule (maybe) about what they're doing below the login box. -- 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] Feedback wanted on Twitter + iOS
Paul, thanks for following up and we definitely understand where you are coming from. The current Apple implementation allows for a single permission for all apps and therefore we have to err on the side of being less permissive. The vast majority of the apps will not need DM read access and we need to optimize for that. We definitely understand the needs and we're exploring options on our side to make it happen. stay tuned -- Ryan Sarver @rsarver https://twitter.com/intent/follow?screen_name=rsarver On Tue, Jun 28, 2011 at 4:48 PM, Paul Haddad paul.had...@gmail.com wrote: Ryan, On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote: We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Simple, open up access to DMs via the API. --- Paul Haddad paul.had...@gmail.com, p...@tapbots.com, p...@pth.com -- 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] Feedback wanted on Twitter + iOS
Tom, by the time this launches all apps using TWRequest will get proper attribution like from YourApp on iOS :) -- Ryan Sarver @rsarver https://twitter.com/intent/follow?screen_name=rsarver On Tue, Jun 28, 2011 at 5:07 PM, Tom van der Woerdt i...@tvdw.eu wrote: First of all, I think Twitter should make it more clear that this implementation is focused on providing Twitter access for non-client apps. Think of this implementation as a 'post on Twitter' feature that doesn't require any API knowledge or other very complicated stuff. That, and you have the ability to get some information about the user. I think it would be a very bad thing if this gave the app DM level access as that kind of access is either abused or for client apps and this framework isn't for either of those. What I noticed while studying the framework (and I'll avoid violating the Apple NDA here) is that the requests are signed using a fixed pair of credentials and always say 'from iOS'. It would be very nice to be able to make that say something like 'from appname on iOS' or something. I think that a LOT of devs are going to ask for that. I have some other ideas but they are improvements over the current framework and if I posted them on a public list I'd have to shoot you ;-) Tom On Jun 29, 2011, at 1:44 AM, Ryan Sarver rsar...@twitter.com wrote: Hey all, With iOS 5 and the Twitter integration coming in a few months, we have been getting a ton of inbound interest and questions around how to effectively leverage the Twitter integration. We wanted to get your feedback on how we can best support you and your users in developing meaningful experiences. I also hope you have had a chance to dig into the documentationhttps://developer.apple.com/library/prerelease/ios/#documentation/Twitter/Reference/TwitterFrameworkReference/_index.html%23//apple_ref/doc/uid/TP40011014and watch the WWDC session videohttps://deimos.apple.com/WebObjects/Core.woa/BrowsePrivately/adc.apple.com.8270634034.08270634040.8367260933?i=1372307634 . We've heard that it would be helpful for us to provide some standard graphics for use with your upcoming iOS integrations. We wanted to understand what types of buttons and styles would be most helpful. We think the most common use case is going to be Sign in with Twitter (SSO) but let us know what formats would be helpful. The two use cases that we're hearing the most interest around are: 1. Instant personalization - frictionless Single Sign-on (SSO) and social graph will allow apps to provide a personalized experience to their users with one click. What things can we provide to make this more effective for you. 2. Distribution - using the build-in Tweet Sheet functionality to post great content from your app out to the Twitter stream where it will drive engagement and clicks back to your application. Let us know if there are any other resources that would help make your Twitter iOS integrations easier on you or help you provide more value to your users on iOS. We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Ryan -- Ryan Sarver @rsarver https://twitter.com/intent/follow?screen_name=rsarver -- Twitter developer documentation and resources: https://dev.twitter.com/dochttps://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk 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] Feedback wanted on Twitter + iOS
Ryan, Thanks for the reply, I'm glad to hear that at least its under consideration. On Jun 28, 2011, at 8:02 PM, Ryan Sarver wrote: Paul, thanks for following up and we definitely understand where you are coming from. The current Apple implementation allows for a single permission for all apps and therefore we have to err on the side of being less permissive. The vast majority of the apps will not need DM read access and we need to optimize for that. We definitely understand the needs and we're exploring options on our side to make it happen. stay tuned -- Ryan Sarver @rsarver --- Paul Haddad paul.had...@gmail.com, p...@tapbots.com, p...@pth.com -- 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] Documentation for streaming events
Hi all, Is there any documentation for the various events a client can receive via the user and/or streaming APIs? Eryn -- 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] Slow Image Requests
I've noticed that some requests to Twitter's image servers have been slow for a few weeks now. Any plan to fix that? For example: it would take over a minute to load Twitter backgrounds or Twitter avatar images. -- Kyle Mulka http://twilk.com -- 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
