[twitter-dev] Re: Problems Connecting to the API
+1 can't connect from slicehost.com (I believe in St. Louis). 2009/10/18 Michael Ivey : > Further info I've collected: > > Can't connect from: > > AT&T DSL in South Alabama > AT&T iPhone network > Northwest Florida, probably Comcast > Other users in Atlanta > Scoble reported various flakiness > Servers at Slicehost in the St Louis datacenter > > Can connect from: > > Blackberry in Atlanta > Seesmic > CoTweet > Facebook > iPhones in CA (@jess updated via Echofon a little while ago) > > -- ivey > > > On Sun, Oct 18, 2009 at 8:40 AM, Dewald Pretorius wrote: >> >> Does anyone else have problems connecting to the API at the moment >> (Sunday morning October 18)? >> >> Dewald > >
[twitter-dev] Re: Is there a way to tell if a tweet has been favorited (regardless of user)?
2009/4/13 Damon Clinkscales > http://twitfave.com/ (and I think they recently said they are offering an > API) > I built and run twitfave - thanks for mentioning it ! We do actually offer an knocked-together API, see http://twitfave.com/home/about/api - I'm very keen to improve that though, as I'm basically serialising the django objects that I'd be sending to views and throwing them straight to the web (hey, this is a one person project in my spare time ;) ). Feedback is very much appreciated. Note especially the section about "Timeliness" - obviously there's only so much information we can crawl from Twitter, and so we prioritise 1) people who score highly in the apps scoring index and 2) followers of people who follow the twitfave user. (As a side note, I'd still love a firehose of all favouriting activity, but I've mentioned that to Doug and Alex, and it's understandably not high on their priority list currently). Mark
[twitter-dev] Re: Freelance Twitter API Dev directory?
Another one for the list, if you don't mind : Mark Ng URL : http://www.markng.co.uk/, http://twitfave.com/ Twitter : @markng Skills: python, django, html, css, js Regards, Mark Ng
Re: Twitter app user poaching
2009/1/27 Chad Etzel : > > Hi all, I actually point my users to the "competing" apps in my about page both of which are more well known than mine ( http://twitfave.com/home/about ). But I'm not currently trying to make money out of my app, so that probably guides my ethics a bit. Mark
Re: a simple workaround for lack of OAuth
2009/1/2 Cameron Kaiser : > So let's say Scoble is right. How, in fact, does OAuth prevent a bad > actor from using credentials to act badly? > > OAuth solves many problems; it doesn't solve this one. There are several problems to be solved, though. The first is a malicious actor with access to a single system (in this case, twitter) spamming. OAuth doesn't solve the problem of someone using an account to spam using messages from that user (unless that app doesn't need to message, and twitters OAuth implementation has granular permissions). The second is a malicious actor with access to a single system gaining control of other systems that user has access to because they've used the same username and/or password. Whilst this is bad practice on the part of the user, we'd be silly to pretend that this isn't a large problem. OAuth *does* solve that problem, which is one of the problems in this scenario. The third is a malicious actor with access to a single system locking the user out of their own account (by changing their password) and claiming the account for themselves (which has been known to happen with gmail accounts, for example). Twitter, so far as I'm aware, doesn't allow changes of passwords via the API, and I would assume that an OAuth implementation would only allow access to the API, and not the web interface. Even were these things not the case, it wouldn't make sense to allow an OAuth client to change the user password. So OAuth does solve this problem, also. Mark
Re: a simple workaround for lack of OAuth
2009/1/2 Ed Finkler : > > I think Scoble likes to hear himself talk, and loves to stir up drama. > It's how he keeps people paying attention to him. > > I'd find more reputable sources for that argument. Whilst there's an element of truth in your statement (just about all of the prominent tech bloggers remain prominent by stirring up drama), lots of people have been saying similar things for a long time. Ad hominem attacks don't change the fact that the message is right. You could start here : http://adactio.com/journal/1357 . I think we all understand, however, that the twitter engineering team first needed to make twitter stable before they could add features like this one. Now that they've largely done that, it appears they're responding to demand for features like this one, which is great news. Mark
Re: problem returning a public status
2008/12/16 Ninjamonk : > > cool thanks, I just had to buy a unique ip address for this. any idea > how long it takes once requested? Mine was pretty quick, a day or two, if I recall, but I'm guessing it'd depend on how busy the twitter people are at the time. Mark
Re: problem returning a public status
2008/12/16 Ninjamonk : > How do I get around this? I am not logged in with an account as it is > not needed to access these files (public users status xml). It works > fine on my local machine and I have done over 100 requests in an hour. You can apply for a whitelisting based on just IP addresses, I do this for twitfave, which doesn't use a logged in account to gather favorites. Mark
