[twitter-dev] Twitter Lists Need Optional Hashtag binding with list subscription
The new lists are a great way reduce the clutter in timeline. However, I immediately notice management problems with the lists where tweets are duplicate in timeline and list for tweets that have nothing to do with the list. For example, let's say I have a sports list: http://twitter.com/#/list/leonspencer/sports I add userA that tweets about sports. But userA also tweets about food. And being a friend, userA will tweet about personal stuff. If a user tweets about sports, dining, and personal stuff, ALL of these tweets are shown under the sports list as well as my timeline. Furthermore, if I create a second list for food/dining and add userA, ALL of the tweets regardless of food or sports will display under both lists. So what would be great is for Twitter to allow the optional specification of one or more hashtags when associating an account with a list, which would indicate tweets from that account should only appear under this list IF these hashtags are part of the tweet. Leon
[twitter-dev] Re: php to json character handling
I'm doing the same thing - communicating data back to the UI via AJAX and JSON. Haven't noticed problems but I'm not using the PHP json_encode functions. Where you able to determine whether it was JQuery or PHP? Through your logging facility (e.g log4PHP and the JQuery debug console) see at what point the JSON data is corrupted. Using log4PHP, I dump all inputs & outputs to the database during development. You can check this information on your failures to help troubleshoot. For AJAX, 'm using Dojo which has a console for debugging. But I'm sure jQuery has similar debugging facility. Leon On Oct 28, 5:28 pm, Peter Denton wrote: > Hello, > We are working on a service dealing with a high volume of tweets. We are > seeing crazy things coming through in tweets and are running into recurring > issues when creating large JSON strings to pass to our parser. > > I am curious if anyone can share approach or methodology on how they are > creating valid JSON via PHP. > > - We are storing the tweets as they are first in a DB > - doing some processing > - sending them back to the UI in various forms, via jQuery ajax calls > ($.getJSON). > > 99% of the time, our server side encoding works great, but some tweets are > just bizarre and valid JSON fails. > > Any advice helps. > > Cheers > Peter
[twitter-dev] Re: Book recommendations
- Forwarded Message From: Andrew Badera To: twitter-development-talk@googlegroups.com Sent: Tue, October 27, 2009 7:35:33 AM Subject: [twitter-dev] Re: Find username/screenname through email addresses The "Address Book API" is forthcoming. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Oct 27, 6:35 am, leonspencer wrote: > Hi. > > I don't have a book (but mention a couple below) that I've used. But > there seen to be quite a few good tutorials. And you can learn a great > deal from the Twitter API Libraries under: > > http://apiwiki.twitter.com/Libraries > > If developing in PHP, I've found Tijs Verkoyen's library to be fairly > straight forward:http://classes.verkoyen.eu/twitter/ > > As far as books for the Twitter API: > > http://oreilly.com/catalog/9780596154622 > Twitter API: Up and Running > Learn How to Build Applications with the Twitter API > By Kevin Makice > > (also on Twitter @http://twitter.com/the_api_book) > > Article by > Makice:http://blog.programmableweb.com/2009/08/05/twitter-developer-tips-fro... > > There is also a .NET Twitter API book out there: > > http://search.barnesandnoble.com/Professional-Twitter-Development/Dan... > Professional Twitter Development: With Examples in .NET 3. 5 by Daniel > Crenna > > Again, I haven't used these books. I started with the online tutorials > and the opensource libraries at:http://apiwiki.twitter.com/Libraries > > Twitter API Tips & Tutorials (a few good links can't > hurt)http://www.newwebplatform.com/tips-and-tutorials/Twitterhttp://twittut.netsensei.nl/?page_id=8http://nicolasrosental.com/?p=42 > > Dig in and get your feet wet ;-) > > Leon > > On Oct 26, 8:59 pm, Tim wrote: > > > Anybody got a recommendation on a book on developing for Twitter?
[twitter-dev] Re: Book recommendations
Hi. I don't have a book (but mention a couple below) that I've used. But there seen to be quite a few good tutorials. And you can learn a great deal from the Twitter API Libraries under: http://apiwiki.twitter.com/Libraries If developing in PHP, I've found Tijs Verkoyen's library to be fairly straight forward: http://classes.verkoyen.eu/twitter/ As far as books for the Twitter API: http://oreilly.com/catalog/9780596154622 Twitter API: Up and Running Learn How to Build Applications with the Twitter API By Kevin Makice (also on Twitter @ http://twitter.com/the_api_book ) Article by Makice: http://blog.programmableweb.com/2009/08/05/twitter-developer-tips-from-the-guy-who-wrote-the-book/ There is also a .NET Twitter API book out there: http://search.barnesandnoble.com/Professional-Twitter-Development/Daniel-Crenna/e/9780470531327/ Professional Twitter Development: With Examples in .NET 3. 5 by Daniel Crenna Again, I haven't used these books. I started with the online tutorials and the opensource libraries at: http://apiwiki.twitter.com/Libraries Twitter API Tips & Tutorials (a few good links can't hurt) http://www.newwebplatform.com/tips-and-tutorials/Twitter http://twittut.netsensei.nl/?page_id=8 http://nicolasrosental.com/?p=42 Dig in and get your feet wet ;-) Leon On Oct 26, 8:59 pm, Tim wrote: > Anybody got a recommendation on a book on developing for Twitter?
[twitter-dev] Re: twitter encoding problem
Thanks. I was unfamiliar with that mechanism. Cool. So that's how it
is done?
Did you try encodeURIComponent() to the Turkish characters are handled
correctly?
Leon
On Oct 20, 1:56 am, sadullah keleş wrote:
> i have a "share on twitter" button , when user click this
> buttonhttp://twitter.com/ page will be open and the info that i send ("i am
> reading this:http://www.mypage.com/article.aspx";) will be shown in the
> "What Are you Doing?" textbox and then user will click update button on
> twitter page.
>
> On Tue, Oct 20, 2009 at 11:46 AM, leonspencer wrote:
>
>
>
> > Thanks for the clarification. Are you updating your Twitter status to
> > read:
>
> > "i am reading this:http://www.mypage.com/article.aspx";
>
> > or are you just trying to display this information in a new browser
> > window without updating your Twitter status?
>
> > Thanks,
> > Leon
>
> > On Oct 20, 1:38 am, sadullah keleş wrote:
> > > hey leonspencer,
> > > thanks for your reply. dont think title part as page title, it is just a
> > > short explanation. what i am trying to do is like "i am reading this:
> >http://www.mypage.com/article.aspx";, i mean at the beginning of the status
> > a
> > > short explanation and after that, link to the page, explanation part will
> > be
> > > taken from page title. this does not encounter any error, works properly
> > > except turkish characters :)
> > > any other idea?
[twitter-dev] Re: twitter encoding problem
Thanks for the clarification. Are you updating your Twitter status to read: "i am reading this: http://www.mypage.com/article.aspx"; or are you just trying to display this information in a new browser window without updating your Twitter status? Thanks, Leon On Oct 20, 1:38 am, sadullah keleş wrote: > hey leonspencer, > thanks for your reply. dont think title part as page title, it is just a > short explanation. what i am trying to do is like "i am reading > this:http://www.mypage.com/article.aspx";, i mean at the beginning of the > status a > short explanation and after that, link to the page, explanation part will be > taken from page title. this does not encounter any error, works properly > except turkish characters :) > any other idea?
[twitter-dev] Re: twitter encoding problem
Hi. I dont think the syntax is right for what you are trying to do. The window.open() syntax is as follows: window.open (URL, windowTitle); Combining this into one string as you have done causes all this to be interpreted as a parameters to Twitter status method, which is not what you intended. And since these are not valid parameters to the status method, you'll probably have errors too. Try the following: var strTwitterApi = 'http://twitter.com/statuses/user_timeline.xml' or var strTwitterApi = 'http://twitter.com/statuses/ user_timeline.rss' or var strTwitterApi = 'http://twitter.com/' Then window.open (strTwitterApi, 'Document Title or whatever'); Leon On Oct 20, 12:16 am, sa wrote: > hey all, > i am trying to send twitter status over my web site but having some > encoding problems, i can not see turkish characters, i use a code > snippet like this : > var sText = "http://www.twitter.com/home?status="; + document.title > + ':' + location.href; > window.open(sText); > //document.title shows my page's title and location.href is a link to > my page > do you have any idea ? how can i solve my encoding problems? > > thanks in advance. > > ps:i had tried using encodeURIComponent method with title part but it > did not work
[twitter-dev] Re: still confused about how many user I can follow
Yeah. The documentation is sketchy. I wasn't able to fine anything definitive from Twitter: http://help.twitter.com/forums/10711/entries/68916 "Additional limits if you are following 2000 or more people: The rules about aggressive following and follow churn still apply. In addition, every user can follow 2000 people total. Once you’ve followed 2000 users, there are limits to the number of additional users you can follow: this limit is different for every user and is based on your ratio of followers to following." Others have described the ratio as 10% more than you are currently following: http://www.using-twitter.com/blog/twitters-2000-follower-limit/ "So, the limit of following 2,000 people was contrived as a mechanism to prevent follow spamming. Once you have around 1,800 followers you can start following 10% followers more than are currently following you. So, at 2,000 followers following you, you can follow a total of 2,200 people on Twitter." Leon On Oct 19, 10:40 pm, Allan Zhang wrote: > >> Once you’ve followed 2000 users, there are limits to the number of > >> additional users you can follow: this limit is different for every user > >> and is based on your ratio of followers to following > > It is not very clearly document by twitter help document. Can someone > give more info about how to calculate how many users I can follow for > my account( 2001 following, 883 follower)? When I want to follow more > guys, it gives me an error message. I need to implement this algorithm > to my program. Thanks for your help in advance. > > Thanks > Allan Zhang
[twitter-dev] Re: Streaming API Permission
Hello. I havent had the opportunity to incorporate streaming into my application yet. However , user @kshep did note the following regarding the firehose: http://friendfeed.com/kshep/eb7676c9/twitter-api-wiki-streaming-documentation ""firehose - Returns all public statuses. Available only to approved parties, and requires a signed agreement to access." - Ken Sheppardson from Bookmarklet" And I recall there being some documentation imply registration or something. But I'm not sure. Look at this prior Firehose related question regarding access: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/93c3302e102dd4c6 Maybe this might help. Cheers, Leon On Oct 19, 1:58 pm, Shashi wrote: > Iam try to connectin Twitter Streaming > APIhttp://stream.twitter.com/1/statuses/firehose.json > with my twitter username and password in turn iam getting > " Http 403 User not in required role" > > Any information how to access twitter firehose streaming api helps us > lot > > Thank you > > Shashi...
[twitter-dev] Re: What is included In the "Queries are limited 140 URL encoded characters." restriction?
So the conclusion is: 1. DO NOT use the search operators that appear in the queries generated by the Twitter Advanced Search tool. For example, http://search.twitter.com/search?q=&ands= Do not use "ands" in your queries. The default interpretation of spaces in yr queries is logical AND. And these do count against query length. 2. The "query" is the q name/value pair. "?q=" (i.e. name q and proceeding "=") are not counted toward the 140 limit. Everything else up until the next parameter (delimited by "&") is counted toward the 140 character limited - including the search operators and their delimiters. Parameters (e.g. rpp), as these are separate name value pairs, are not part of the query thus not counted toward the max 140 character count. NOTE: There are exceptions and some overlap that may cause confusion. For example, Twitter defines "until:" as a search operator while you'll also see a "&until=" (i.e. "until" parameter) in the queries generated by the Advanced Search Tool. As a result, both "until:" and "&until=" are counted toward the 140 max character limit. The Twitter API is smart enough to see this overlap and recognize what you are going. However, it isn't documented. So you save you the trouble, if you are reading this, I'm noting this here. Leon On Oct 17, 9:52 pm, Scott Haneda wrote: > I brought that up the other day, "twitter eating their own dog food", > to which I was told they do, but only in some parts. It would be nice, > so that when the API is down, twitter is down, and we as developers > did not look like our apps suck, but that may not be a goal for > twitter, or it may be, I just do not know. I hope it is though. > -- > Scott * If you contact me off list replace talklists@ with scott@ *
[twitter-dev] Re: What is included In the "Queries are limited 140 URL encoded characters." restriction?
Continuing to go it along with the Advanced Search Tool to see what defines the "query" and length of 140 chars. Latest try resulted in the following response from the tool: "You must enter a query. " This is the query I entered from using the advanced search tool: http://search.twitter.com/search?q=&ands=12345678901234567890&phrase=12345678901234567890&ors=12345678901234567890¬s=12345678901234567890&tag=12345678901234567890&lang=en&from=&to=&ref=&near=&within=15&units=mi&since=&until=&rpp=15 I used order groups of 20 digits to examine the length - 12345678901234567890.
[twitter-dev] Re: What is included In the "Queries are limited 140 URL encoded characters." restriction?
Do NOT respond or post to this thread unless you can answer the question. And no, I am not "bumping" threads. Get a life. Leon On Oct 17, 8:35 pm, JDG wrote: > You do realize that Twitter's employees take the weekends off, too, just > like the rest of us? Please don't bump threads. > > > > On Sat, Oct 17, 2009 at 20:39, leonspencer wrote: > > > And still waiting on a response. More information from a associate: > > > Subject: Re: Do you know what is being counted toward "query length" > > > Yeah, because your using twitter search and not api! > > > An Api String would be > > > For Geo Locations > > >http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%... > > > Or > > For Since... > >http://search.twitter.com/search.atom?q=twitter&since_id=1520639490 > > > On Oct 17, 2:29 pm, leonspencer wrote: > > > Still waiting for a response here. I tried a query with the Twitter > > > Advanced Search tool: > >http://search.twitter.com/search?q=&ands=Allofthesewords&phrase=Thise... > > > > When I strip away the parameter names and operators, this is the > > > values stringed together: > > > AllofthesewordsThisexactphraseAnyofthesewordsNoneofthesewordsThishashtagenleonspencerleonspencerleonspencer15mi2009-10-072009-10-1815 > > > > Length is at 133 but still getting error from the advanced search: > > >http://search.twitter.com/search?q=&ands=Allofthesewords&phrase=Thise... > > > > "Sorry, your query cannot be more than 140 characters long (it is 161 > > > characters). " > > > > So I don't know what it is counting. > > -- > Internets. Serious business.
[twitter-dev] Re: What is included In the "Queries are limited 140 URL encoded characters." restriction?
And still waiting on a response. More information from a associate: Subject: Re: Do you know what is being counted toward "query length" Yeah, because your using twitter search and not api! An Api String would be For Geo Locations http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%2C25km Or For Since... http://search.twitter.com/search.atom?q=twitter&since_id=1520639490 On Oct 17, 2:29 pm, leonspencer wrote: > Still waiting for a response here. I tried a query with the Twitter > Advanced Search > tool:http://search.twitter.com/search?q=&ands=Allofthesewords&phrase=Thise...=en&from=leonspencer&to=leonspencer&ref=leonspencer&near=&within=15&units=mi&since=2009-10-07&until=2009-10-18&rpp=15 > > When I strip away the parameter names and operators, this is the > values stringed together: > > AllofthesewordsThisexactphraseAnyofthesewordsNoneofthesewordsThishashtagenleonspencerleonspencerleonspencer15mi2009-10-072009-10-1815 > > Length is at 133 but still getting error from the advanced search: > > http://search.twitter.com/search?q=&ands=Allofthesewords&phrase=Thise...=en&from=leonspencer&to=leonspencer&ref=leonspencer&near=&within=15&units=mi&since=2009-10-07&until=2009-10-18&rpp=15 > > "Sorry, your query cannot be more than 140 characters long (it is 161 > characters). " > > So I don't know what it is counting.
[twitter-dev] Re: What is included In the "Queries are limited 140 URL encoded characters." restriction?
Still waiting for a response here. I tried a query with the Twitter Advanced Search tool: http://search.twitter.com/search?q=&ands=Allofthesewords&phrase=Thisexactphrase&ors=Anyofthesewords¬s=Noneofthesewords&tag=Thishashtag〈=en&from=leonspencer&to=leonspencer&ref=leonspencer&near=&within=15&units=mi&since=2009-10-07&until=2009-10-18&rpp=15 When I strip away the parameter names and operators, this is the values stringed together: AllofthesewordsThisexactphraseAnyofthesewordsNoneofthesewordsThishashtagenleonspencerleonspencerleonspencer15mi2009-10-072009-10-1815 Length is at 133 but still getting error from the advanced search: http://search.twitter.com/search?q=&ands=Allofthesewords&phrase=Thisexactphrase&ors=Anyofthesewords¬s=Noneofthesewords&tag=Thishashtag〈=en&from=leonspencer&to=leonspencer&ref=leonspencer&near=&within=15&units=mi&since=2009-10-07&until=2009-10-18&rpp=15 "Sorry, your query cannot be more than 140 characters long (it is 161 characters). " So I don't know what it is counting. On Oct 15, 7:43 pm, leonspencer wrote: > What us being counted as part of the length of the query - entire > query string? What names (of query string name/value pair), values > (of query string name/value pair), and delimiters are counted in the > Twitter API restriction "Queries are limited 140 URL encoded > characters?" I've run the Twitter API Advanced Search Form to generate > queries: > > http://search.twitter.com/advanced > > At some point it will say the query is too large - should be 140 but > is 155 > > Query > example:http://search.twitter.com/search?q=&ands=All+of+these+words&phrase=Th... > > What us being included in this length? The entire query string? (i.e. ? > q to the end or just the length of the values? > > Thank you
[twitter-dev] Re: Laying the foundation for API versioning
Marcel, Is the API description available as a markup file (e.g. XSD)? Or is there some other way of programmatically scanning the APi that I've missed. Thank you, Leon On Oct 16, 12:26 am, Marcel Molina wrote: > We've taken the first steps toward introducing versioning into the > Twitter REST API. With a versioned API we can make ambitious > improvements *today*, not tomorrow, without worrying about breaking > backwards compatibility. This will lead to both a better and more > reliable API. > > Available right now, the API's new home is athttp://api.twitter.com. > Currently only one version is supported: version 1 :-) Version 1 > should be in all ways functionally equivalent to the API you're using > at the main twitter.com url (if you find what seems like an > incompatibility please submit what you've found on our issue > tracker:http://code.google.com/p/twitter-api/issues/list). > > To make a request with the new versioned API, you just need to prefix > every path with the desired version. For now that's just 1. > > So for example, what was > > http://twitter.com/users/show/noradio.xml > > becomes > > http://api.twitter.com/1/users/show/noradio.xml > > For now we're keeping it simple. No subversions, no implicit version > defaults, no fancy-pants etc. We're leaving our approach open to these > types of additions, but we aren't going to support them until we feel > a compelling need to. > > We haven't yet determined how many versions will be supported at once > or how long a version will continue to be supported once it's > deprecated. We'll be figuring out answers to these questions once we > spend some time supporting multiple versions and seeing how new APIs > emerge and iterate. We suspect though that we'll support deprecated > versions for at least 6 months. > > We also don't have a hard date for when API requests tohttp://twitter.comwill > no longer be serviced. We aren't planning on > pulling the rug out from anyone though. Please update your > applications to the newhttp://api.twitter.com/1at your soonest > convenience. The non API urls likely won't be supported forever. > > Though having a versioned API should greatly decrease the likelihood > that a change in the API breaks your application, one of the notable > exceptions is bug fixes. When bugs are discovered they will be fixed > and backported immediately to all supported versions of the API. > > We're kicking the tires onhttp://api.twitter.com/1but we hope to > havehttp://api.twitter.com/2close around the corner. The time has > come for us to start knocking off some of the stuff on V2 Roadmap > listhttp://apiwiki.twitter.com/V2-Roadmap. For a while that page has been > the dumping ground for all our lofty dreams. Version 2 probably won't > be so ambitious that it resolves everything on that list. We want, > after all, to get good at managing a multi-version environment before > we get all crazy with the nitrous injections and chrome detailing. But > we're putting the framework in place that will allow us to more > quickly fix the stuff you've struggling with, take chances without > putting your work in jeopardy, and all other things that are good. > > Cheers. > > -- > Marcel Molina > Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] What is included In the "Queries are limited 140 URL encoded characters." restriction?
What us being counted as part of the length of the query - entire query string? What names (of query string name/value pair), values (of query string name/value pair), and delimiters are counted in the Twitter API restriction "Queries are limited 140 URL encoded characters?" I've run the Twitter API Advanced Search Form to generate queries: http://search.twitter.com/advanced At some point it will say the query is too large - should be 140 but is 155 Query example: http://search.twitter.com/search?q=&ands=All+of+these+words&phrase=This+exact+phrase&ors=Any+of+these+words¬s=None+of+these+words&tag=Balloonboy&lang=en&from=leonspencer&to=&ref=&near=&within=15&units=mi&since=2009-10-15&until=2009-10-16&rpp=15 What us being included in this length? The entire query string? (i.e. ? q to the end or just the length of the values? Thank you
