[twitter-dev] Re: @anywhere login code samples
I get 401 Unauthorized when I use this example code with my API key of
course.
On Apr 15, 6:08 am, siggy andrewseig...@gmail.com wrote:
Hi there,
Some of the @anywhere sample code in the Working with the current
user section required some tweaks to get working.
The text specifies a User Callback function but the sample code does
not.
Also, thetwttr.anywhere() function does not appear to work with an
API key, instead I specify it with the anywhere.js file.
Here is a modified code snippet that appears to work:
//var anywhereApiKey = abcdefghi-123;
//twttr.anywhere(anywhereApiKey, 1.0.0,
onAnywhereLoad);twttr.anywhere(onAnywhereLoad);
function onAnywhereLoad(twitter)
{
// Conditionally display theConnectButton based on current logged
in state:
if (twitter.isConnected)
{
twitter.User.current(user_callback);
}
else
{
twitter(#twitter-connect-placeholder).connectButton();
}
};
function user_callback(currentUser)
{
screenName = currentUser.data('screen_name');
profileImage = currentUser.data('profile_image_url');
profileImageTag = img src=' + profileImage + '/;
$('#twitter-connect-placeholder').innerHTML = Logged in as +
profileImageTag + + screenName;
};
Thanks,
Andrew
twitter.com/siggy_sf
[twitter-dev] Re: stopping bit.ly automatic shortening of urls
this is a topic of interest to me for a long while. been meaning to start a thread. i'm often bothered by the automatic shortening of urls when in fact the url does not need to be shortened. in these cases, i of course do not want to hide the real url by using a forced 3rd party service like bit.ly. i have use cases where all that is posted is a url. and the url includes a long detailed description of the link. this, in my opinion, is smart as the only object to maintain is the url itself which provides a hyperlink and a short message combined. sometimes, these use cases are using natural language vanity urls to form short sentences. ie. http://john.tot.al.ly/wiped-out-on-this-huge-wave-in-hawaii-at-the-Surf-Hawaii-Surf-School-on-the-island-of-Oahu the other annoying thing that is related to the twitter UI is how long urls are cut-off//trimmed even if they dont need to be. the above example would be destroyed because it would result in something like: http://john.tot.al.ly/wip actually, i'm not certain if that is still the case as it seems to me that every url is shortened with bit.ly now. i grok the value in tracking urls and bit.ly may be bought by twitter at some point and this notion of url tracking will be fully integrated but the debate about url shortners in general how they can break the natural web, are vulnerable to massive broken links and simply thr cryptic format itself that hides the true location are all to be considered and continued to be debated. at the very least, 3rd party developers should get an override toggle. that is something i think we all need to start demanding. and yes, an official doc explaining the current and future impementations of url shortening on twitter is definitely needed now. http://plea.se/twitter-dont-shorten-this-url-with-bitly-since-it-does-not-need-to-be-shortened-with-8-available-characters-remaining http://twitter.com/sull/status/2534470050 @sull On Jul 8, 4:50 am, Swaroop rh.swar...@gmail.com wrote: However, if you paste in a link that is less than 30 characters, we'll post it in its entirety. If it's longer than 30 characters, we'll convert it to a shorter URL. Source:http://help.twitter.com/portal
[twitter-dev] Re: stopping bit.ly automatic shortening of urls
ironically, my example urls are shortened here ;) On Jul 8, 12:20 pm, sull sullele...@gmail.com wrote: this is a topic of interest to me for a long while. been meaning to start a thread. i'm often bothered by the automatic shortening of urls when in fact the url does not need to be shortened. in these cases, i of course do not want to hide the real url by using a forced 3rd party service like bit.ly. i have use cases where all that is posted is a url. and the url includes a long detailed description of the link. this, in my opinion, is smart as the only object to maintain is the url itself which provides a hyperlink and a short message combined. sometimes, these use cases are using natural language vanity urls to form short sentences. ie.http://john.tot.al.ly/wiped-out-on-this-huge-wave-in-hawaii-at-the-Su... the other annoying thing that is related to the twitter UI is how long urls are cut-off//trimmed even if they dont need to be. the above example would be destroyed because it would result in something like: http://john.tot.al.ly/wip actually, i'm not certain if that is still the case as it seems to me that every url is shortened with bit.ly now. i grok the value in tracking urls and bit.ly may be bought by twitter at some point and this notion of url tracking will be fully integrated but the debate about url shortners in general how they can break the natural web, are vulnerable to massive broken links and simply thr cryptic format itself that hides the true location are all to be considered and continued to be debated. at the very least, 3rd party developers should get an override toggle. that is something i think we all need to start demanding. and yes, an official doc explaining the current and future impementations of url shortening on twitter is definitely needed now. http://plea.se/twitter-dont-shorten-this-url-with-bitly-since-it-does... http://twitter.com/sull/status/2534470050 @sull On Jul 8, 4:50 am, Swaroop rh.swar...@gmail.com wrote: However, if you paste in a link that is less than 30 characters, we'll post it in its entirety. If it's longer than 30 characters, we'll convert it to a shorter URL. Source:http://help.twitter.com/portal
[twitter-dev] Re: stopping bit.ly automatic shortening of urls
yes, twitter is after all a text based service. anyway, adding html to a tweet opens up a can of worms. it wont happen. it shouldnt happen. yes, twtr could provide, via the web UI at least, a way to add metadata to a tweet that is extra (not the text message itself, but associated data that can be exposed on certain UIs. but thats a different topic and i'd like to improve the current issue of short urling. also of interest - http://twitterdata.org On Jul 8, 4:42 pm, Joel Strellner j...@twitturly.com wrote: It goes back to the root of twitter originally being a SMS application. I recall hearing or reading someone on the Twitter team saying that. -Joel On Jul 8, 2009, at 1:31 PM, whoiskb whoi...@gmail.com wrote: I am curious if there has ever been an official response from twitter on why some simple HTML has not been allowed in a tweet? If we were able to use an anchor tag, and the HTML did not count against the 140 character limit, then the need for a URL shortener service would not be needed. On Jul 8, 10:27 am, sull sullele...@gmail.com wrote: ironically, my example urls are shortened here ;) On Jul 8, 12:20 pm, sull sullele...@gmail.com wrote: this is a topic of interest to me for a long while. been meaning to start a thread. i'm often bothered by the automatic shortening of urls when in fact the url does not need to be shortened. in these cases, i of course do not want to hide the real url by using a forced 3rd party service like bit.ly. i have use cases where all that is posted is a url. and the url includes a long detailed description of the link. this, in my opinion, is smart as the only object to maintain is the url itself which provides a hyperlink and a short message combined. sometimes, these use cases are using natural language vanity urls to form short sentences. ie.http://john.tot.al.ly/wiped-out-on-this-huge-wave-in-hawaii-at- the-Su... the other annoying thing that is related to the twitter UI is how long urls are cut-off//trimmed even if they dont need to be. the above example would be destroyed because it would result in something like: http://john.tot.al.ly/wip actually, i'm not certain if that is still the case as it seems to me that every url is shortened with bit.ly now. i grok the value in tracking urls and bit.ly may be bought by twitter at some point and this notion of url tracking will be fully integrated but the debate about url shortners in general how they can break the natural web, are vulnerable to massive broken links and simply thr cryptic format itself that hides the true location are all to be considered and continued to be debated. at the very least, 3rd party developers should get an override toggle. that is something i think we all need to start demanding. and yes, an official doc explaining the current and future impementations of url shortening on twitter is definitely needed now. http://plea.se/twitter-dont-shorten-this-url-with-bitly-since-it-does ... http://twitter.com/sull/status/2534470050 @sull On Jul 8, 4:50 am, Swaroop rh.swar...@gmail.com wrote: However, if you paste in a link that is less than 30 characters, we'll post it in its entirety. If it's longer than 30 characters, we'll convert it to a shorter URL. Source:http://help.twitter.com/portal
[twitter-dev] Re: How to list followers, including icons and usernames?
yes it's a tough one all i wanted was to populate a dropdown menu
with followers names for direct message form.
would prefer a more efficient way.
but i am doing a follower import/update.
it's expensive on first session but not so bad if the user comes back
and only has a small batch of new followers.
still prefer a direct call to get usernames and ids.
this:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-followers%C2%A0ids
should return both ids. numerical id and screen_name id.
they are both referred to ids elsewhere so both can be included in
this method without naming confusion.
i assume, however, that the querying for the screen_name and numeric
id is resource intensive on twitters end which is why it is not
available.
twitter assumes/hopes that you will import and cache.
On Jun 29, 8:02 am, Aaron Rankin aran...@gmail.com wrote:
It looks like status/followers gets you part of the way there. First,
some questions for Twitter:
1) Does status/followers return statuses for distinct users? E.g., if
one of my followers has changed their status twice in the past minute,
will this method return the latest or both?
2) For every follower, will this definitely return the last status for
each, even if they've been idle for some time?
Since this returns statuses in batches of 100, to get all data for all
followers, you'll still to run a query for every 100 (including the
remainder at the end). At least in the JSON, status/followers doesn't
tell you how many followers there are. To know the number of queries
(pages of 100) to fetch, you also need to query followers/ids. It's
clearly better than 1 query per follower + 1 call to follower/ids for
the main user in question.
Is this the best way to get information for each follower of a given
user?
Thanks,
Aaron
On Jun 28, 12:41 pm, Abraham Williams 4bra...@gmail.com wrote:
Check out this
method:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0f...
On Sun, Jun 28, 2009 at 12:26, Bemmubemmu@gmail.com wrote:
I'm wanting to do a friend selector that looks something like the
selector on Facebook, where the user sees a list of their followers'
names and icons, and can select some of them. Right now the only way I
can think of is first getting all IDs of followers from /followers/
ids, and then calling /users/show.json?user_id= for each. Seems
expensive and slow.
What's the right way to do this? I see some apps have follower
selectors, but I don't know if they screen scrape http://twitter.com/
followers/1401881, or do as I just described and simply not work for
people with too many followers.
My dream API method would allow sorting by name or follower count,
something like this:
Query: /followers/list.json?sort=follower_countpage=1per_page=1000
Response:
[
{ 'id' : 12345, 'icon' : 'http://...somethingjpg', 'username' :
'a' },
{ 'id' : 67890, 'icon' : 'http://...somethingjpg', 'username' :
'b' },
...
]
Since many users will probably have thousands of followers, I thought
I could ease the
--
Abraham Williams | Community Evangelist |http://web608.org
Hacker |http://abrah.am|http://twitter.com/abraham
Project |http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: Whoa there error after Oauth authorization.
confirmed. this has been happening to me over the past week as well. On Jun 25, 10:51 am, Abraham Williams 4bra...@gmail.com wrote: I do remember running into this a few days ago but assumed it was a random occurrence. I did just replicate the issue though by: Log out of twitter. Go tohttp://twitter.abrah.amand start authenticate process. Provide username:password to twitter and authorized. go tohttps://twitter.com/in a new tab and log in. You are then redirected to /oauth/authorize. You should probably add an issue to issue tracker. Abraham On Thu, Jun 25, 2009 at 09:28, mruhlinmruh...@gmail.com wrote: We're testing an app and have seen some strange behavior after OAuthing. The user goes through the norma OAuth process just fine, closes our tab and then just opens up a new tab towww.twitter.com. Once they login they're redirected tohttp://twitter.com/oauth/authorize, which shows an error. Anybody else seen this? -- Abraham Williams | Community Evangelist |http://web608.org Hacker |http://abrah.am|http://twitter.com/abraham Project |http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: tool to let you know when twitter name is available
nice. i've used http://www.changedetect.com for this in the past. will give your service a try. On Jun 24, 2:22 am, drew pushespr...@gmail.com wrote: Hi everyone, I wrote a quick tool to email you when the Twitter name you want is available:http://www.tweettaker.com/ It seems Twitter currently might not be deleting inactive accounts, but they plan to resume automatically deleting them in the future. Any feedback is appreciated. Thanks, Drew
[twitter-dev] Re: get all friend screen_names
it's not critical, so i was mainly trying to make sure that i was not missing something in the API. i'm just doing a check on the response with the page parameter. if it's empty, then i've reached the last page and will combine the result sets (from each page). problem solved. On Jun 18, 12:47 am, Developer In London ebilliona...@gmail.com wrote: why would you need the screen_names of all the friends? usually you can use the twitterID for making any API calls 2009/6/18 sull sullele...@gmail.com i actually started out using statuses/friends until i realized that it was only 100 results per call. then i would have to go into paging. plus i didnt need the other data that is returned. so then i decided that their must be a more direct call to make. i suppose not. so if i return to statuses/friends approach, i would have to determine how many pages of friends exist for that user so i can import all the friends. it would have been helpful if in the data response, the total # of pages was listed as well. but i cna calculate based on friends_count###/friends_count. any other thoughts? is this what others are doing to get complete friends list? thanks. sull On Jun 17, 10:30 pm, Abraham Williams 4bra...@gmail.com wrote: statuses/friends would probably be faster. On Wed, Jun 17, 2009 at 20:11, sull sullele...@gmail.com wrote: i found it odd that i cannot seem to get a simple API response with all of a user's friends screen_names, only user ids. do i need to make a request from users/show after i do friends/ids ? am i missing a direct call or more efficient method? thanks. -- Abraham Williams | Community |http://web608.org Hacker |http://abrah.am|http://twitter.com/abraham Project |http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. -- cashflowclublondon.co.uk (`-''-/).___..--''`-._ `6_ 6 ) `-. ( ).`-.__.`) (_Y_.)' ._ ) `._ `. ``-..-' _..`--'_..-_/ /--'_.' ,' (il),-'' (li),' ((!.-' .
[twitter-dev] Re: get all friend screen_names
i've discovered other threads about this limitation and ways to deal with it (albeit not efficient). over time, with caching results, it should suffice. but their are issues. would be nice if at least there was a a count parameter for all endpoints that have a page parameter. On Jun 18, 2:19 am, sull sullele...@gmail.com wrote: it's not critical, so i was mainly trying to make sure that i was not missing something in the API. i'm just doing a check on the response with the page parameter. if it's empty, then i've reached the last page and will combine the result sets (from each page). problem solved. On Jun 18, 12:47 am, Developer In London ebilliona...@gmail.com wrote: why would you need the screen_names of all the friends? usually you can use the twitterID for making any API calls 2009/6/18 sull sullele...@gmail.com i actually started out using statuses/friends until i realized that it was only 100 results per call. then i would have to go into paging. plus i didnt need the other data that is returned. so then i decided that their must be a more direct call to make. i suppose not. so if i return to statuses/friends approach, i would have to determine how many pages of friends exist for that user so i can import all the friends. it would have been helpful if in the data response, the total # of pages was listed as well. but i cna calculate based on friends_count###/friends_count. any other thoughts? is this what others are doing to get complete friends list? thanks. sull On Jun 17, 10:30 pm, Abraham Williams 4bra...@gmail.com wrote: statuses/friends would probably be faster. On Wed, Jun 17, 2009 at 20:11, sull sullele...@gmail.com wrote: i found it odd that i cannot seem to get a simple API response with all of a user's friends screen_names, only user ids. do i need to make a request from users/show after i do friends/ids ? am i missing a direct call or more efficient method? thanks. -- Abraham Williams | Community |http://web608.org Hacker |http://abrah.am|http://twitter.com/abraham Project |http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. -- cashflowclublondon.co.uk (`-''-/).___..--''`-._ `6_ 6 ) `-. ( ).`-.__.`) (_Y_.)' ._ ) `._ `. ``-..-' _..`--'_..-_/ /--'_.' ,' (il),-'' (li),' ((!.-' .
[twitter-dev] Re: oAuth - Application Website
this happened to me last week. it also happened again when i made edits to the registered app but those edits did not take effect (though the changes were displayed properly from oauth_clients management page. both times, deleting my app from twitter and recreating it helped. On Jun 17, 1:23 pm, Wallace wallace.b.mccl...@gmail.com wrote: I have gotten my oAuth based app to deploy (finally - its a long story). One problem I am seeing is that when I look at the url link for my app, it is different from the url entered into on my app on the oAuth_clients setting for Application Website The entry is correct in my application's settings but the link is going to the incorrect place in the url link for my app. Anyway to get this resolved? Wally
