[twitter-dev] Re: Some thoughts leading up to Chirp
Regardless of the companies position moving forward, there are great people working at Twitter who sincerely care about the developer community, including Ryan. If things are unfair, you can bet they feel it too. They're still figuring it out. I don't see them implementing any of the stuff your software does, so I don't understand the constant negativity. You complained that they weren't communicating, and when they do you call it BS. Life's too short man. The whole situation the last few days reminds me a lot of this clip: http://www.youtube.com/watch?v=KLni3wbndls Justyn On Apr 11, 8:05 pm, Dewald Pretorius dpr...@gmail.com wrote: Ryan, Thanks for attempting to step into an emotionally charged environment and clarifying things. However, to be quite frank, the argument about confusion in the Apple app store gives off a distinct spinning sound. Very loud, in fact. It may be one of the reasons for acquiring Tweetie, but to cite it as the primary and only reason immediately sets of all flavors of BS alarms.
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
The difference (to my understanding) is that Authenticate does not authorize the app. We need to have the app authorized but want to give the user the chance to choose which account to login with (and Authorize). Ideally, twitter state would not be effected, and user could authorize an app with desired account (regardless of session) without clicking sign out. Justyn On Dec 28, 5:36 pm, Abraham Williams 4bra...@gmail.com wrote: That is true. Authenticate currently leaves the user logged in. I would prefer that get fixed rather then adding force_login to authorize as I view leaving users logged in as a security risk. Apparently Twitter does not: http://code.google.com/p/twitter-api/issues/detail?id=1070 On Mon, Dec 28, 2009 at 17:13, Andy Freeman ana...@earthlink.net wrote: Then use authenticate. It accomplishes the same effect of authorize. Does it? My notes say that authenticate leaves the user logged into twitter if they weren't before and that authorize doesn't. For my purposes, I'd like to force the user to specify their twitter account and password even if they're already logged in and not change their login state (as far as twitter is concerned) at all. I can imagine folks who'd like to allow users to quickly authorize the use of the logged in account (if any) I can't imagine anyone who'd want to change the user's logged in state. On Dec 27, 6:08 pm, Abraham Williams 4bra...@gmail.com wrote: Then use authenticate. It accomplishes the same effect of authorize. On Sun, Dec 27, 2009 at 17:42, Justyn justyn.how...@gmail.com wrote: Thanks Abraham - I understand this is the current limitation, however I think there is a need for the foce_login to be available with the authorize function. The authorize landing page is confusing to users who want to sign-in with an account that is different from their latest session. The sign-out option is not obvious to users. This is based on user feedback, and I don't think we're the only ones having this issue. On Dec 27, 3:39 pm, Abraham Williams 4bra...@gmail.com wrote: force_login=true only works onhttps:// twitter.com/oauth/authenticatenot onhttps://twitter.com/oauth/authorize. On Sat, Dec 26, 2009 at 23:23, el moro axel.sachm...@googlemail.com wrote: Hi, i'd like to use force_login too in my new Rails application. This parameter seems to be buggy. For me it' s not working too. On 24 Dez., 05:18, Justyn justyn.how...@gmail.com wrote: Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States- Hide quoted text - - Show quoted text - -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
Thanks Abraham - I understand this is the current limitation, however I think there is a need for the foce_login to be available with the authorize function. The authorize landing page is confusing to users who want to sign-in with an account that is different from their latest session. The sign-out option is not obvious to users. This is based on user feedback, and I don't think we're the only ones having this issue. On Dec 27, 3:39 pm, Abraham Williams 4bra...@gmail.com wrote: force_login=true only works onhttps://twitter.com/oauth/authenticatenot onhttps://twitter.com/oauth/authorize. On Sat, Dec 26, 2009 at 23:23, el moro axel.sachm...@googlemail.com wrote: Hi, i'd like to use force_login too in my new Rails application. This parameter seems to be buggy. For me it' s not working too. On 24 Dez., 05:18, Justyn justyn.how...@gmail.com wrote: Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn
[twitter-dev] oAuth Authenticate vs. Authorize (force_login)
We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn
[twitter-dev] Re: A way to send user to oAuth page with no user defined?
Hoping to get some direction on this issue when possible. If I'm missing something simple, a link would be great. Thanks! Justyn On Dec 14, 10:24 pm, Justyn justyn.how...@gmail.com wrote: We'd like to use oAuth to add authorize additional accounts, but it gets hairy for users when it defaults to last used username. Is there a way to send oAuth users directly to the page that appears when sign out is clicked? So that they are prompted for the username and password for the account they want to authorize? Thanks in advance!
[twitter-dev] Re: A way to send user to oAuth page with no user defined?
Thanks Abraham! On Dec 15, 4:33 pm, Abraham Williams 4bra...@gmail.com wrote: Add force_login=true when you send the user to Twitter. See:http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate On Tue, Dec 15, 2009 at 15:02, Justyn justyn.how...@gmail.com wrote: Hoping to get some direction on this issue when possible. If I'm missing something simple, a link would be great. Thanks! Justyn On Dec 14, 10:24 pm, Justyn justyn.how...@gmail.com wrote: We'd like to use oAuth to add authorize additional accounts, but it gets hairy for users when it defaults to last used username. Is there a way to send oAuth users directly to the page that appears when sign out is clicked? So that they are prompted for the username and password for the account they want to authorize? Thanks in advance! -- Abraham Williams | Awesome Lists |http://bit.ly/sprout608 Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] A way to send user to oAuth page with no user defined?
We'd like to use oAuth to add authorize additional accounts, but it gets hairy for users when it defaults to last used username. Is there a way to send oAuth users directly to the page that appears when sign out is clicked? So that they are prompted for the username and password for the account they want to authorize? Thanks in advance!
[twitter-dev] Re: Developer Preview: Contributor API
Hi Raffi,
Curious how the contributors will be associated? Will it essentially
be linking accounts? Presumably then the user would identify in an app
which account to post an update to based on those accounts they have
been associated as contributors to? So, a contribution would
originate from a separate Twitter account, let's say @Raffi and be
posted to @Twitter. The primary difference from what we're used to
with CoTweet for example, where you may have many authors with no
individual twitter accounts, this would all be based on having two or
more accounts (1 biz account linked to contributor accounts). Does
that make sense?
Justyn
On Dec 14, 6:07 pm, Raffi Krikorian ra...@twitter.com wrote:
As you may have seen on our
bloghttp://blog.twitter.com/2009/12/feature-test-with-businesses.html,
we're starting a very small test of a new feature that will allow a Twitter
account to have multiple contributors. This is the first in a suite of
features that we'll be rolling out specifically targeted to the needs of
businesses, and this particular feature is going to allow a business to
invite employees and representatives to tweet, DM, follow users, etc., on
behalf of the account holder.
While this feature is not ready for prime-time, and while we're not yet
taking requests to be part of an early-access release while we work out the
kinks, we're really committed to keeping our developers in the loop. I want
to give you all a heads up on what is coming on the API side, and, for this
particular feature, I wanted to give you all a look at what we're calling
the Contributor API. The reason I want to really highlight these changes
is because we'll be making an addition to the status objects as this rolls
out.
We'll be introducing a new parameter called contributingto to most API
endpoints -- this parameter must be set to the user ID of the user that the
employee or representative wants to take the action on behalf of. If using
contributingto, then the caller must authenticate when calling and must use
OAuth. For example, if I, @raffi, wanted to tweet on behalf of @twitter (ID
783214), I would call /status/update.xml, I would attach a parameter of
contributingto=783214, and I would authenticate to that endpoint as myself
using OAuth. The API will confirm that @raffi has permission to contribute
to the @twitter account, and will error with a 403 if that account does not.
You can expect to see contributingto show up as an optional parameter to the
following endpoints (and presumably some more) when calling
onhttp://api.twitter.com/1:
/account/rate_limit_status
/account/update_profile
/account/update_profile_background_image
/account/update_profile_colors
/account/update_profile_image
/account/verify_credentials
/blocks/blocking
/blocks/blocking/ids
/blocks/create
/blocks/destroy
/blocks/exists
/direct_messages
/direct_messages/destroy
/direct_messages/new
/direct_messages/sent
/favorites
/favorites/create
/favorites/destroy
/followers/ids
/friends/ids
/friendships/create
/friendships/destroy
/friendships/exists
/report_spam
/saved_searches
/saved_searches/create
/saved_searches/destroy
/saved_searches/show
/statuses/destroy
/statuses/followers
/statuses/friends
/statuses/friends_timeline
/statuses/home_timeline
/statuses/mentions
/statuses/public_timeline
/statuses/retweet
/statuses/retweeted_by_me
/statuses/retweeted_to_me
/statuses/retweets
/statuses/retweets_of_me
/statuses/show
/statuses/update
/statuses/user_timeline
/users/show
Lastly, the status objects will include an additional parameter named
contributors that will have an user_id with the ID of the user who actually
created this status object. An example XML status would have
status
...
contributors
user_idID of the contributor/user_id
/contributors
...
/status
and in JSON
{
...
contributors : [ID of the contributor],
...
}
Due to caching, historical status objects may or may not contain the
contributors, but all status created after launch will.
Like I said, more details to come!
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Developer Preview: Contributor API
That's exactly what I was wondering, helps for planning. Thanks Raffi!
On Dec 14, 11:14 pm, Raffi Krikorian ra...@twitter.com wrote:
what we have not yet exposed is the invitation or linking step - but,
you are mostly correct. to carry on with my example, @twitter would
invite @raffi to contribute on its behalf. now @raffi, has the ability to
call API endpoints with contributingto=783214. �...@raffi and @twitter are
both
twitter accounts, but @twitter has enabled itself for contributors to access
it.
does that help?
On Mon, Dec 14, 2009 at 8:33 PM, Justyn justyn.how...@gmail.com wrote:
Hi Raffi,
Curious how the contributors will be associated? Will it essentially
be linking accounts? Presumably then the user would identify in an app
which account to post an update to based on those accounts they have
been associated as contributors to? So, a contribution would
originate from a separate Twitter account, let's say @Raffi and be
posted to @Twitter. The primary difference from what we're used to
with CoTweet for example, where you may have many authors with no
individual twitter accounts, this would all be based on having two or
more accounts (1 biz account linked to contributor accounts). Does
that make sense?
Justyn
On Dec 14, 6:07 pm, Raffi Krikorian ra...@twitter.com wrote:
As you may have seen on our
bloghttp://blog.twitter.com/2009/12/feature-test-with-businesses.html,
we're starting a very small test of a new feature that will allow a
Twitter
account to have multiple contributors. This is the first in a suite of
features that we'll be rolling out specifically targeted to the needs of
businesses, and this particular feature is going to allow a business to
invite employees and representatives to tweet, DM, follow users, etc., on
behalf of the account holder.
While this feature is not ready for prime-time, and while we're not yet
taking requests to be part of an early-access release while we work out
the
kinks, we're really committed to keeping our developers in the loop. I
want
to give you all a heads up on what is coming on the API side, and, for
this
particular feature, I wanted to give you all a look at what we're calling
the Contributor API. The reason I want to really highlight these
changes
is because we'll be making an addition to the status objects as this
rolls
out.
We'll be introducing a new parameter called contributingto to most API
endpoints -- this parameter must be set to the user ID of the user that
the
employee or representative wants to take the action on behalf of. If
using
contributingto, then the caller must authenticate when calling and must
use
OAuth. For example, if I, @raffi, wanted to tweet on behalf of @twitter
(ID
783214), I would call /status/update.xml, I would attach a parameter of
contributingto=783214, and I would authenticate to that endpoint as
myself
using OAuth. The API will confirm that @raffi has permission to
contribute
to the @twitter account, and will error with a 403 if that account does
not.
You can expect to see contributingto show up as an optional parameter to
the
following endpoints (and presumably some more) when calling onhttp://
api.twitter.com/1:
/account/rate_limit_status
/account/update_profile
/account/update_profile_background_image
/account/update_profile_colors
/account/update_profile_image
/account/verify_credentials
/blocks/blocking
/blocks/blocking/ids
/blocks/create
/blocks/destroy
/blocks/exists
/direct_messages
/direct_messages/destroy
/direct_messages/new
/direct_messages/sent
/favorites
/favorites/create
/favorites/destroy
/followers/ids
/friends/ids
/friendships/create
/friendships/destroy
/friendships/exists
/report_spam
/saved_searches
/saved_searches/create
/saved_searches/destroy
/saved_searches/show
/statuses/destroy
/statuses/followers
/statuses/friends
/statuses/friends_timeline
/statuses/home_timeline
/statuses/mentions
/statuses/public_timeline
/statuses/retweet
/statuses/retweeted_by_me
/statuses/retweeted_to_me
/statuses/retweets
/statuses/retweets_of_me
/statuses/show
/statuses/update
/statuses/user_timeline
/users/show
Lastly, the status objects will include an additional parameter named
contributors that will have an user_id with the ID of the user who
actually
created this status object. An example XML status would have
status
...
contributors
user_idID of the contributor/user_id
/contributors
...
/status
and in JSON
{
...
contributors : [ID of the contributor],
...
}
Due to caching, historical status objects may or may not contain the
contributors, but all status created after launch will.
Like I said, more details to come!
--
Raffi
[twitter-dev] Re: Duplicate Tweets
If duplicate tweets are the concern, then why are RT's on their way to being a feature? Abuse is the concern. Not duplicate content, right? So a local restaurant can't setup a tweet to go out on Wednesdays to remind their followers of 1/2 off appetizers? There's no ill intent here, and they have businesses to run. Doesn't twitter want businesses to foster it's platform? There's valid uses for recurring content within reason. It's not realistic to ask users to come up with 52 unique headlines, hunt down the associated link and fire up the laptop prior to happy to hour every Wednesday at 6:00 in order to get a message out to people who opted to follow them. What's the happy-medium here? On Oct 13, 4:00 pm, JDG ghil...@gmail.com wrote: They already do that ... in SOME cases. Pharmacies are required (or maybe simply strongly encouraged) to sell OTC meds like Sudafed behind the counter because some people use that to make crystal meth. The government requires a waiting period on guns because some people use guns to murder people. Rightly or wrongly -- and I seriously believe you did this with no abusive intent -- you provided a tool that made it very easy for users to post duplicate tweets. They didn't shut you down. They gave you a stern warning. On Tue, Oct 13, 2009 at 14:39, Dewald Pretorius dpr...@gmail.com wrote: Now there is an excellent analogy, which begs the question, Where is the user's responsibility in this? I have very clearly warned my users, every time they enter a tweet, that they must adhere to the Twitter Rules, with hyperlinks to those rules. That was not good enough. So, with your analogy in mind, should the authorities pull over speeders, or should they shut down manufacturers that make vehicles that can exceed the speed limit? Or, in a different analogy, should the government shut down Home Depot because they sell chain saws and box cutters, and some people use chain saws and box cutters to murder other human beings? Dewald On Oct 13, 5:31 pm, JDG ghil...@gmail.com wrote: Yes, and should be treated as such. I personally detest all those stupid twitter-based games. Point is, with Twitter's userbase, some get through the cracks. Don't like it, report it. This is like complaining that cops only pull over SOME speeders. Yeah, some are going to get through the cracks. -- Internets. Serious business.
[twitter-dev] Re: Duplicate Tweets
Thanks for the response Chad. Hoping we can find measures to curb abuse while still allowing responsible use of recurrence as a useful tool for publishers, businesses and their followers who benefit from the consistency/timeliness of the communications. On 10/13/09 8:28 PM, Chad Etzel c...@twitter.com wrote: Believe it or not, I've been reading every post on this thread with great intent. I have been proxying major points to powers that be and started an internal discussion on the topic at hand. The resulting decisions and policies that may be made/enforced from these discussions is, how do you say, above my pay grade. We do listen to these threads as long as the discussion remains constructive, which this one has. -Chad On Tue, Oct 13, 2009 at 9:08 PM, Dewald Pretorius dpr...@gmail.com wrote: The only Twitter participation we've had thus far on this unfortunate matter was Chad aging 10 years in 10 seconds over the idea that someone can write a desktop or browser script that scrapes the login page and then do whatever the hell it pleases (you know, like posting something awful like recurring tweets). The sad thing is this. Selected people at Twitter are very familiar with my level of cooperation with them. Believe it or not, there are people in Twitter who actually view me as one of the good guys. With my users having a recurring tweet feature available to them, and with the cooperation of Twitter and suitable information from Twitter, I could have contained the matter programmatically. But, with what essentially amounts as a flat-out rejection of my offer to cooperate and change my system to prevent duplicate tweets, they have now sent all those users off somewhere else, into the loving arms of people who couldn't give a shit about working with Twitter, and have in essence unleashed recurring tweet hell on themselves. The demand for recurring tweets has not suddenly magically disappeared. Let me repeat that. Hopefully someone in Twitter will take notice. The demand for recurring tweets has not suddenly magically disappeared. Dewald On Oct 13, 9:22 pm, JDG ghil...@gmail.com wrote: I dunno. It'd be nice. I personally like rearranging deck chairs like this. It was civil and, hopefully, productive. On Tue, Oct 13, 2009 at 17:39, Dewald Pretorius dpr...@gmail.com wrote: I often wonder whether our non-API musings here on these forums have any effect on anything, or are we just amusing ourselves by rearranging deck chairs? Dewald On Oct 13, 8:03 pm, Justyn justyn.how...@gmail.com wrote: If duplicate tweets are the concern, then why are RT's on their way to being a feature? Abuse is the concern. Not duplicate content, right? So a local restaurant can't setup a tweet to go out on Wednesdays to remind their followers of 1/2 off appetizers? There's no ill intent here, and they have businesses to run. Doesn't twitter want businesses to foster it's platform? There's valid uses for recurring content within reason. It's not realistic to ask users to come up with 52 unique headlines, hunt down the associated link and fire up the laptop prior to happy to hour every Wednesday at 6:00 in order to get a message out to people who opted to follow them. What's the happy-medium here? On Oct 13, 4:00 pm, JDG ghil...@gmail.com wrote: They already do that ... in SOME cases. Pharmacies are required (or maybe simply strongly encouraged) to sell OTC meds like Sudafed behind the counter because some people use that to make crystal meth. The government requires a waiting period on guns because some people use guns to murder people. Rightly or wrongly -- and I seriously believe you did this with no abusive intent -- you provided a tool that made it very easy for users to post duplicate tweets. They didn't shut you down. They gave you a stern warning. On Tue, Oct 13, 2009 at 14:39, Dewald Pretorius dpr...@gmail.com wrote: Now there is an excellent analogy, which begs the question, Where is the user's responsibility in this? I have very clearly warned my users, every time they enter a tweet, that they must adhere to the Twitter Rules, with hyperlinks to those rules. That was not good enough. So, with your analogy in mind, should the authorities pull over speeders, or should they shut down manufacturers that make vehicles that can exceed the speed limit? Or, in a different analogy, should the government shut down Home Depot because they sell chain saws and box cutters, and some people use chain saws and box cutters to murder other human beings? Dewald On Oct 13, 5:31 pm, JDG ghil...@gmail.com wrote: Yes, and should be treated as such. I personally detest all those stupid twitter-based games. Point is, with Twitter's userbase, some get through the cracks. Don't like it, report it. This is like complaining that cops only pull over SOME speeders. Yeah, some are going to get through the cracks
[twitter-dev] Re: inline popup on twitter links
If you're looking to do this in an external app, it's certainly possible. If you're looking to add this functionality to twitter.com itself, you would need something like Abraham mentioned (a browser plugin). On Jun 17, 4:03 pm, Shift shiftmarket...@gmail.com wrote: Hi Guys Just working on developing an idea/app for twitter and was hoping anyone out there might shed some light on something i am stumpped on. From within twitter i want to be able to post a link (say a shortened URL to an article). which when clicked will span a lightbox (modal/ inline popup) rather than opening a new window/tab with the article, is this possible to do, does anyone know how to do it or direct me to somewhere that i can get more info? Anyones help is really appreciated a lot. Thanks
[twitter-dev] Re: Get last login date
You could use the timestamp of their last update - I imaging this would work for most needs, unless you truly needed to know the last time they accessed Twitter and browsed. On Jun 17, 7:07 pm, Stuart stut...@gmail.com wrote: 2009/6/17 drewcrazy andrewila...@gmail.com: Is there currently a twitter call that can capture the last login date of a user? Nope. -Stuart --http://stut.net/projects/twitter
[twitter-dev] Re: Search API to require HTTP Referrer and/or User Agent
Thanks Doug - Any additional info to help us know if we comply? My dev is out of the country on vacation and want to make sure we don¹t miss anything. On 6/16/09 11:33 AM, Doug Williams d...@twitter.com wrote: Hi all, The Search API will begin to require a valid HTTP Referrer, or at the very least, a meaningful and unique user agent with each request. Any request not including this information will be returned a 403 Forbidden response code by our web server. This change will be effective within the next few days, so please check your applications using the Search API and make any necessary code changes. Thanks, Doug
[twitter-dev] Re: Spinn3r Twitter Social Media Rank
I'd love to be able to pass you a UN and get back your algo results. On 6/15/09 5:42 PM, burton burtona...@gmail.com wrote: That's what we're thinking of experimenting with... perhaps an API where you can give us a handle and we can tell you if it is spam or ham. Also ranking on certain topics (tech, politics, etc) would be pretty hot. If you have any ideas we're all ears On Jun 15, 2:45 pm, Justyn Howard justyn.how...@gmail.com wrote: Well done. Considering an API so we could integrate rank data with other apps? On 6/15/09 3:43 PM, burton burtona...@gmail.com wrote: Hey guys. We just pushed this today: http://spinn3r.com/rank/twitter.php as part of our Spinn3r 3.1 release: http://blog.spinn3r.com/2009/06/spinn3r-31---now-with-twitter-support... al-media-ranking.html Would love feedback. If this is valuable for the community we would be willing to compute deeper rankings (on a deeper crawl) and recompute this more regularly (once every two weeks or so). Kevin
[twitter-dev] Re: Search API to require HTTP Referrer and/or User Agent
Thanks, pretty sure we do both. Will this new (or newly enforced) policy help clean up some garbage? On 6/16/09 11:56 AM, Doug Williams d...@twitter.com wrote: All we ask is that you include a valid HTTP Referrer and/or a User Agent with each request which is easy to do in almost every language. Both would be helpful but we only require one at this time. We simply want to be able to identify apps and have the ability to communicate with the authors. Thanks, Doug On Tue, Jun 16, 2009 at 9:51 AM, Justyn Howard justyn.how...@gmail.com wrote: Thanks Doug - Any additional info to help us know if we comply? My dev is out of the country on vacation and want to make sure we don¹t miss anything. On 6/16/09 11:33 AM, Doug Williams d...@twitter.com http://d...@twitter.com wrote: Hi all, The Search API will begin to require a valid HTTP Referrer, or at the very least, a meaningful and unique user agent with each request. Any request not including this information will be returned a 403 Forbidden response code by our web server. This change will be effective within the next few days, so please check your applications using the Search API and make any necessary code changes. Thanks, Doug
[twitter-dev] Re: Twitter Developer/Founder Community on Ning - Registration Open
So you only use one social networking site? One email account? Of course because information in several places would be fragmentation right? Oh wait, you're on Friendfeed, Twitter, Facebook, LinkedIn, StumbleUpon, etc. Conversations take many forms. We wanted to create closer relationships with other developers, so we created a place to do it. Google Groups is linear. We're not reinventing the framework there, we're sharing ideas and getting to know each other. We have the group feed specifically so people will continue to interact here for technical discussion. Totally OK with you passing, but I'm not sure why you would waste your time putting down others who are trying to connect with the community. Justyn On 6/11/09 2:21 AM, Andrew Badera and...@badera.us wrote: Of course you don't consider it fragmentation, even if that's exactly what you've just described. Can I go to a single, official, original place to get the entire conversation? Nope, you've just created a new place people need to go, a place where new knowledge will inevitably accrete and not propagate. Congratulations on adding to the noise in everyone's life. The only way this doesn't fragment the community and the knowledge and the flow of communication is if an alternative to the official list TOOK OVER official dev communications for Twitter. Otherwise, augmentation like this leads to fragmentation. Again, congratulations. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Wed, Jun 10, 2009 at 9:11 PM, Justynjustyn.how...@gmail.com wrote: I don't consider it fragmentation. We pump this thread into the site w/ links back to discussions and give people another layer of ways to connect and communicate with other dev's. I don't see a downside =) http://twtfnd.ning.com/ On Jun 7, 5:47 pm, Andrew Badera and...@badera.us wrote: fragmentation ... On Sat, Jun 6, 2009 at 9:26 PM, Justynjustyn.how...@gmail.com wrote: We have created a private community on the Ning network for developers and founders of Twitter-related projects. You can connect and communicate with other developers, share ideas, discuss your projects, find contract work and veiw/post events. You can view and join the community here:http://twtfnd.ning.com/ All are welcome and we look forward to seeing you there!
[twitter-dev] Re: Twitter Developer/Founder Community on Ning - Registration Open
Yeah, we should probably shut down everything new and go back to IRC. C'mon man, I wanted to network with other interesting devs, period. If there was a place to easily do that more socially than Groups, I would have happily joined and called it a day. On 6/11/09 2:37 AM, Andrew Badera and...@badera.us wrote: Poor strawmen. And yes, I do use only one email account, thanks. Social networking sites are the epitome of fragmentation, and they don't revolve around my use of official documentation and communication, for many, many reasons -- first and foremost, they're not well suited, they're not easily searched or indexed. You've created fragmentation Suck it up and accept that. I'm not putting you or anyone or anything down, quit being so overly sensitive -- but face the facts. Whether you did it with good intentions, or you did it with the idea of making yourself more visible, you've created fragmentation. Period. Thanks again. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Thu, Jun 11, 2009 at 3:34 AM, Justyn Howardjustyn.how...@gmail.com wrote: So you only use one social networking site? One email account? Of course because information in several places would be fragmentation right? Oh wait, you're on Friendfeed, Twitter, Facebook, LinkedIn, StumbleUpon, etc. Conversations take many forms. We wanted to create closer relationships with other developers, so we created a place to do it. Google Groups is linear. We're not reinventing the framework there, we're sharing ideas and getting to know each other. We have the group feed specifically so people will continue to interact here for technical discussion. Totally OK with you passing, but I'm not sure why you would waste your time putting down others who are trying to connect with the community. Justyn On 6/11/09 2:21 AM, Andrew Badera and...@badera.us wrote: Of course you don't consider it fragmentation, even if that's exactly what you've just described. Can I go to a single, official, original place to get the entire conversation? Nope, you've just created a new place people need to go, a place where new knowledge will inevitably accrete and not propagate. Congratulations on adding to the noise in everyone's life. The only way this doesn't fragment the community and the knowledge and the flow of communication is if an alternative to the official list TOOK OVER official dev communications for Twitter. Otherwise, augmentation like this leads to fragmentation. Again, congratulations. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Wed, Jun 10, 2009 at 9:11 PM, Justynjustyn.how...@gmail.com wrote: I don't consider it fragmentation. We pump this thread into the site w/ links back to discussions and give people another layer of ways to connect and communicate with other dev's. I don't see a downside =) http://twtfnd.ning.com/ On Jun 7, 5:47 pm, Andrew Badera and...@badera.us wrote: fragmentation ... On Sat, Jun 6, 2009 at 9:26 PM, Justynjustyn.how...@gmail.com wrote: We have created a private community on the Ning network for developers and founders of Twitter-related projects. You can connect and communicate with other developers, share ideas, discuss your projects, find contract work and veiw/post events. You can view and join the community here:http://twtfnd.ning.com/ All are welcome and we look forward to seeing you there!
[twitter-dev] Re: Twitter Developer/Founder Community on Ning - Registration Open
Your one-upmanship amuses me. Doesn't your profession involve developing for social networks? In regards to fragmentation, I wanted a place to connect with entrepreneurs who are doing interesting things with Twitter. To talk best-practices (business), network with founders of complimentary tools, connect contractors with jobs etc. That's not really the premise of this group. In any case, please accept my apologies for muddying your stream. I didn't realize your authority on the matter. Let's move on. On 6/11/09 2:54 AM, Andrew Badera and...@badera.us wrote: So now you're reduced to what comes across as whining, but you've stopped denying fragmentation. Well hey, that's a step in the right direction I guess. Because of course what the world needs is ANOTHER social network, or another aspect of an existing social network, to serve the developers of client apps to a social network. Hey, why not have a whole social network talking about social networks discussing development of social networks while you're at it? Nothing like niche. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Thu, Jun 11, 2009 at 3:52 AM, Justyn Howardjustyn.how...@gmail.com wrote: Yeah, we should probably shut down everything new and go back to IRC. C'mon man, I wanted to network with other interesting devs, period. If there was a place to easily do that more socially than Groups, I would have happily joined and called it a day. On 6/11/09 2:37 AM, Andrew Badera and...@badera.us wrote: Poor strawmen. And yes, I do use only one email account, thanks. Social networking sites are the epitome of fragmentation, and they don't revolve around my use of official documentation and communication, for many, many reasons -- first and foremost, they're not well suited, they're not easily searched or indexed. You've created fragmentation Suck it up and accept that. I'm not putting you or anyone or anything down, quit being so overly sensitive -- but face the facts. Whether you did it with good intentions, or you did it with the idea of making yourself more visible, you've created fragmentation. Period. Thanks again. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Thu, Jun 11, 2009 at 3:34 AM, Justyn Howardjustyn.how...@gmail.com wrote: So you only use one social networking site? One email account? Of course because information in several places would be fragmentation right? Oh wait, you're on Friendfeed, Twitter, Facebook, LinkedIn, StumbleUpon, etc. Conversations take many forms. We wanted to create closer relationships with other developers, so we created a place to do it. Google Groups is linear. We're not reinventing the framework there, we're sharing ideas and getting to know each other. We have the group feed specifically so people will continue to interact here for technical discussion. Totally OK with you passing, but I'm not sure why you would waste your time putting down others who are trying to connect with the community. Justyn On 6/11/09 2:21 AM, Andrew Badera and...@badera.us wrote: Of course you don't consider it fragmentation, even if that's exactly what you've just described. Can I go to a single, official, original place to get the entire conversation? Nope, you've just created a new place people need to go, a place where new knowledge will inevitably accrete and not propagate. Congratulations on adding to the noise in everyone's life. The only way this doesn't fragment the community and the knowledge and the flow of communication is if an alternative to the official list TOOK OVER official dev communications for Twitter. Otherwise, augmentation like this leads to fragmentation. Again, congratulations. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Wed, Jun 10, 2009 at 9:11 PM, Justynjustyn.how...@gmail.com wrote: I don't consider it fragmentation. We pump this thread into the site w/ links back to discussions and give people another layer of ways to connect and communicate with other dev's. I don't see a downside =) http://twtfnd.ning.com/ On Jun 7, 5:47 pm, Andrew Badera and...@badera.us wrote: fragmentation ... On Sat, Jun 6, 2009 at 9:26 PM, Justynjustyn.how...@gmail.com wrote: We have created a private community on the Ning network for developers and founders of Twitter-related projects. You can connect and communicate with other developers, share ideas, discuss your projects, find contract work and veiw/post events. You can view and join the community here:http://twtfnd.ning.com/ All are welcome and we look forward to seeing you there!
[twitter-dev] Re: Twitter Developer/Founder Community on Ning - Registration Open
Are you drunk? Your .sig says ask permission to email, so I posted here. There is no personal gain involved and I have given way more than I have received. If you want to judge my character, as I mentioned, email me direct. You have my permission. On 6/11/09 3:13 AM, Andrew Badera and...@badera.us wrote: And yet you keep posting on-list ... amusing, yep. On Thu, Jun 11, 2009 at 4:12 AM, Justyn Howardjustyn.how...@gmail.com wrote: Feel free to email me directly if you want to continue this discussion - I don't think the group cares. On 6/11/09 2:54 AM, Andrew Badera and...@badera.us wrote: So now you're reduced to what comes across as whining, but you've stopped denying fragmentation. Well hey, that's a step in the right direction I guess. Because of course what the world needs is ANOTHER social network, or another aspect of an existing social network, to serve the developers of client apps to a social network. Hey, why not have a whole social network talking about social networks discussing development of social networks while you're at it? Nothing like niche. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Thu, Jun 11, 2009 at 3:52 AM, Justyn Howardjustyn.how...@gmail.com wrote: Yeah, we should probably shut down everything new and go back to IRC. C'mon man, I wanted to network with other interesting devs, period. If there was a place to easily do that more socially than Groups, I would have happily joined and called it a day. On 6/11/09 2:37 AM, Andrew Badera and...@badera.us wrote: Poor strawmen. And yes, I do use only one email account, thanks. Social networking sites are the epitome of fragmentation, and they don't revolve around my use of official documentation and communication, for many, many reasons -- first and foremost, they're not well suited, they're not easily searched or indexed. You've created fragmentation Suck it up and accept that. I'm not putting you or anyone or anything down, quit being so overly sensitive -- but face the facts. Whether you did it with good intentions, or you did it with the idea of making yourself more visible, you've created fragmentation. Period. Thanks again. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Thu, Jun 11, 2009 at 3:34 AM, Justyn Howardjustyn.how...@gmail.com wrote: So you only use one social networking site? One email account? Of course because information in several places would be fragmentation right? Oh wait, you're on Friendfeed, Twitter, Facebook, LinkedIn, StumbleUpon, etc. Conversations take many forms. We wanted to create closer relationships with other developers, so we created a place to do it. Google Groups is linear. We're not reinventing the framework there, we're sharing ideas and getting to know each other. We have the group feed specifically so people will continue to interact here for technical discussion. Totally OK with you passing, but I'm not sure why you would waste your time putting down others who are trying to connect with the community. Justyn On 6/11/09 2:21 AM, Andrew Badera and...@badera.us wrote: Of course you don't consider it fragmentation, even if that's exactly what you've just described. Can I go to a single, official, original place to get the entire conversation? Nope, you've just created a new place people need to go, a place where new knowledge will inevitably accrete and not propagate. Congratulations on adding to the noise in everyone's life. The only way this doesn't fragment the community and the knowledge and the flow of communication is if an alternative to the official list TOOK OVER official dev communications for Twitter. Otherwise, augmentation like this leads to fragmentation. Again, congratulations. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Wed, Jun 10, 2009 at 9:11 PM, Justynjustyn.how...@gmail.com wrote: I don't consider it fragmentation. We pump this thread into the site w/ links back to discussions and give people another layer of ways to connect and communicate with other dev's. I don't see a downside =) http://twtfnd.ning.com/ On Jun 7, 5:47 pm, Andrew Badera and...@badera.us wrote: fragmentation ... On Sat, Jun 6, 2009 at 9:26 PM, Justynjustyn.how...@gmail.com wrote: We have created a private community on the Ning network for developers and founders of Twitter-related projects. You can connect and communicate with other developers, share ideas, discuss your projects, find contract work and veiw/post events. You can view and join the community here:http://twtfnd.ning.com
[twitter-dev] Re: Twitter Developer/Founder Community on Ning - Registration Open
The Moral of this story is that I posted something I thought would be helpful, something that people might find value in. There was no self- interest involved. I took the time to create something for other people to use. But some people would rather criticize, show thier web-flaming skills and wit to make other narrow-minded people chuckle or show thier superiority. I've learned my lesson. Don't try to be helpful, especially not here. Thanks for turning something I was delighted to share into a clear message that some people will always justify their own self-importance by tearing down others. Most of you are awesome. A few of you need a hug. Andrew took offense to the idea that I was creating fragmentation, another place to go for information, that was somehow self purposed. Fragmentation? From a guy who's blog has links to 16 different websites to connect with him. Not once did I remark on your character, yet you continued to insult me and pass judgement on mine. Live and let live, sir. Do your thing and I'll do mine. This will be my last post on the topic, but I wanted to share my dissapointment that people are being discouraged from sharing. I'm a genuine person and I was genuinely trying to be helpful. Justyn P.S. - Andrew - you...complete...me Sent from my iPhone On Jun 11, 2009, at 5:57 PM, Dossy Shiobara do...@panoptic.com wrote: On 6/11/09 4:06 PM, Bradley S. O'Hearne wrote: Hint: why make an enemy out of a complete stranger, when you could instead speak (regardless of agreement / disagreement) with courtesy and make a friend, or a business associate. Just as easy to make a friend than an enemy. Actually, it's a lot easier to make enemies than friends. Plus, enemies are known quantities - you know what the deal is. Friends, especially the fair-weather types (you know, the kind who are your friend when things go their way, but don't know you the minute you need them) aren't worth having in the first place. People who need something from others should be a little more gracious and accomodating of the people they're seeking favor from, not whine when they don't get their way or are mistreated. That's not the short path to getting what they want, anyway. Begging and bribery are both well-tested and proven methods for soliciting help from others. I highly recommend exhausting those two options, first. :-) -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: Twitter Application Usage Guidelines, Please Read
Thank you for the response Doug. I intended the post to be more curious than implicative though it may have sounded more of the latter. In any case, we¹ve all grown to love the openness of the platform, and the platform itself as such a great opportunity to build. I just got nervous when I started thinking about the work we¹ve put in. Thanks for being communicative about this! On 6/9/09 9:10 PM, Doug Williams d...@twitter.com wrote: Obviously I can't address the impact since we don't have a document to deliver. Let me be clear, we are not thinking of taking functionality from the offering, but we are discussing how open we want to be moving forward. Most of the talks are around what we want to offer through the Streaming API and to whom should those privileges be extended. We are not concentrating our efforts on whom can we restrict and why? Remember we built this company on being open and to that we are committed, especially within the API team. We are very conscious that you developers are a little weary of our plans but rest assured we want to augment the ecosystem and its abilities rather than contract our offering. Thanks, Doug On Tue, Jun 9, 2009 at 6:58 PM, Justyn Howard justyn.how...@gmail.com wrote: What are the chances that this new TOS will negate any of the hard work we¹ve done up until this point? Can you give us an idea of what will be protected? It¹s a little alarming to hear that Twitter might decide to reserve functionality that the developer network has built-on and enhanced in favor of internalizing as business assets. As there has been no TOS in place other than the general Twitter TOS, many of us have spent countless hours and $$ trying to build businesses around Twitter. Not trying to be an alarmist, just curious what this will ultimately mean for us? Justyn On 6/9/09 8:51 PM, Doug Williams d...@twitter.com http://d...@twitter.com wrote: The API TOS is currently in development. It is taking longer than hoped as we are still exploring what we want to give to developers and what we want to protect as business assets. For now, make sure that you understand the general TOS we have in place. We do work with developers if they are willing to answer our attempts to reach out before shutting them off due to TOS violations. We also try to understand what developers are doing and how they may be heading against the grain before issuing whitelisting. Most developers are willing to work with us which is great and works out for everyone. Thanks, Doug On Tue, Jun 9, 2009 at 6:26 PM, Jesse Stay jesses...@gmail.com http://jesses...@gmail.com wrote: Doug, where is the developer API TOS? I think that's part of the problem - none of us are being required to enter into an agreement before developing, therefore we have no idea what we can and can't do with it. I also don't think most of us even know where any such TOS is, if there is one. I agree that the OAuth application process should make this a bit eas ier to manage, and help developers know more about what they are getting into before starting their applications. Personally, I want to make sure I'm following the rules of the API. I'd also prefer to know what I'm agreeing to before starting a busine ss on top of it. I feel for the developers of the 2 mentioned apps because, *if* they are violating any TOS, they probably had no idea they were doing so before spending so much time developing it. (even if I disagree with the premise of those apps) @Jesse On Tue, Jun 9, 2009 at 5:31 PM, Doug Williams d...@twitter.com http://d...@twitter.com wrote: Brant, Thank you for your concern. This is something that bothers us as well. Moving applications exclusively to OAuth-based authentication will certainly help in restricting applications that abuse the service. If you find a service that you think is violating our TOS, please email a...@twitter.com http://a...@twitter.com or send a message to @twitterapi and we can take a look. As you mentioned, Del is great but she is but one person. We do have an abuse team forming to help quickly identify which services are violating our TOS. All in all we have a lot of work to do so please do help where you can. Cheers, Doug On Tue, Jun 9, 2009 at 2:43 PM, Brant btedes...@gmail.com http://btedes...@gmail.com wrote: This message will hopefully get back to the people who run Twitter API development and spam prevention. I noticed there are quite a few twitter applications that are developed to abuse the service and violate their TOS. They do not hide what their purpose is, yet these applications remain active. I contacted twitter.com/delbius http://twitter.com/delbius http://twitter.com/delbius who heads Twitter Spam prevention and she said that they do revoke API access to abusive applications. But I don't think they are taking an aggressive stance against them. Abusive
[twitter-dev] Re: Greetings all, New Dev (.net) Here
Start with the API/Wiki stuff. There's an API Status value that gives you the calls/100. Sent from my iPhone On Jun 10, 2009, at 12:31 PM, KrushRadio - Doc drega...@gmail.com wrote: Hey all, thougth i'd pop my head in and say hey. My name is Dan Regalia, and I'm a .net Dev. I'm working on a twitter engine, and a client (names have not been announced yet). I'm really excited about the entire Twitter concept. I have been watching the streams, and I've seen alot of talk about Messaging limits, DM Limits, Follow Limits, etc. While my engine strictly follows and tracks existing streams, and the client is really a souped up version of twirhl in .net form.. Where can i actually find the actual limits at. Are there read limits? I saw on some of the applications, that people are getting counts from somewhere, like they have 5/100 left, etc. Are there dynamics to this, is it tracked in the account stream xml, or something like that? I have about 2 weeks of reading up to do here on the group dev site, and then dig thru the api/wiki stuff... ~Dan 'Doc' Regalia
[twitter-dev] Re: Twitter Developer/Founder Community on Ning - Registration Open
I don't consider it fragmentation. We pump this thread into the site w/ links back to discussions and give people another layer of ways to connect and communicate with other dev's. I don't see a downside =) http://twtfnd.ning.com/ On Jun 7, 5:47 pm, Andrew Badera and...@badera.us wrote: fragmentation ... On Sat, Jun 6, 2009 at 9:26 PM, Justynjustyn.how...@gmail.com wrote: We have created a private community on the Ning network for developers and founders of Twitter-related projects. You can connect and communicate with other developers, share ideas, discuss your projects, find contract work and veiw/post events. You can view and join the community here:http://twtfnd.ning.com/ All are welcome and we look forward to seeing you there!
[twitter-dev] Re: Twitter Application Usage Guidelines, Please Read
I think it depends on what measures the site is taking to promote responsible use of the applications. Both applications could be used for good, or bad. I can think of one fairly popular site that is all but endorses spammy behavior and charges users for access to these spammy tools. I don¹t want to point fingers, but my point is, there are probably more abusive apps out there than these two, and it all comes down to how responsibly the sites are guiding users, and if they have any rules in place to get rid of those who abuse it. On 6/9/09 6:28 PM, Abraham Williams 4bra...@gmail.com wrote: In briefly checking out Mutuality and Twollo I'm not sure what about them is abusive. Mutuality says it lets you rapidly modify who you are following to match who is following you and Twollo auto follows accounts it thinks you might be interested in. Those are both useful tools and if used as intended are just that. I can see Twitter banning an individual user for using the services abusively but not the services themselves. On Tue, Jun 9, 2009 at 16:43, Brant btedes...@gmail.com wrote: This message will hopefully get back to the people who run Twitter API development and spam prevention. I noticed there are quite a few twitter applications that are developed to abuse the service and violate their TOS. They do not hide what their purpose is, yet these applications remain active. I contacted twitter.com/delbius http://twitter.com/delbius who heads Twitter Spam prevention and she said that they do revoke API access to abusive applications. But I don't think they are taking an aggressive stance against them. Abusive Applications: http://www.huitter.com/mutuality/ http://www.twollo.com/ The combination of these two applications is for outright abuse of the service. They have been around for several months and are known applications to abuse the service with. To make matters worse, Twitter suspends accounts of the people who use these applications rather than targeting the root of the problem, the applications themselves. (Sound counterproductive? RIAA uses a similar policy by going after end users.) I propose that applications need to be more closely scrutinized and can even be flagged as abusive by users. Instead of creating algorithms that detect abnormal user behavior, why not detect abnormal application behavior. Taking a stronger stance against gray area applications could reduce server load on Twitter (giving real applications faster response time) and reduce manpower to deal with spam prevention. I strongly encourage anyone who develops Twitter applications to send this link around. Thanks for reading, Brant twitter.com/BrantTedeschi http://twitter.com/BrantTedeschi
[twitter-dev] Re: Twitter Application Usage Guidelines, Please Read
What are the chances that this new TOS will negate any of the hard work we¹ve done up until this point? Can you give us an idea of what will be protected? It¹s a little alarming to hear that Twitter might decide to reserve functionality that the developer network has built-on and enhanced in favor of internalizing as business assets. As there has been no TOS in place other than the general Twitter TOS, many of us have spent countless hours and $$ trying to build businesses around Twitter. Not trying to be an alarmist, just curious what this will ultimately mean for us? Justyn On 6/9/09 8:51 PM, Doug Williams d...@twitter.com wrote: The API TOS is currently in development. It is taking longer than hoped as we are still exploring what we want to give to developers and what we want to protect as business assets. For now, make sure that you understand the general TOS we have in place. We do work with developers if they are willing to answer our attempts to reach out before shutting them off due to TOS violations. We also try to understand what developers are doing and how they may be heading against the grain before issuing whitelisting. Most developers are willing to work with us which is great and works out for everyone. Thanks, Doug On Tue, Jun 9, 2009 at 6:26 PM, Jesse Stay jesses...@gmail.com wrote: Doug, where is the developer API TOS? I think that's part of the problem - none of us are being required to enter into an agreement before developing, therefore we have no idea what we can and can't do with it. I also don't think most of us even know where any such TOS is, if there is one. I agree that the OAuth application process should make this a bit easie r to manage, and help developers know more about what they are getting into before starting their applications. Personally, I want to make sure I'm following the rules of the API. I'd also prefer to know what I'm agreeing to before starting a business on top of it. I feel for the developers of the 2 mentioned apps because, *if* they are violating any TOS, they probably had no idea they were doing so before spending so much time developing it. (even if I disagree with the premise of those apps) @Jesse On Tue, Jun 9, 2009 at 5:31 PM, Doug Williams d...@twitter.com wrote: Brant, Thank you for your concern. This is something that bothers us as well. Moving applications exclusively to OAuth-based authentication will certainly help in restricting applications that abuse the service. If you find a service that you think is violating our TOS, please email a...@twitter.com or send a message to @twitterapi and we can take a look. As you mentioned, Del is great but she is but one person. We do have an abuse team forming to help quickly identify which services are violating our TOS. All in all we have a lot of work to do so please do help where you can. Cheers, Doug On Tue, Jun 9, 2009 at 2:43 PM, Brant btedes...@gmail.com wrote: This message will hopefully get back to the people who run Twitter API development and spam prevention. I noticed there are quite a few twitter applications that are developed to abuse the service and violate their TOS. They do not hide what their purpose is, yet these applications remain active. I contacted twitter.com/delbius http://twitter.com/delbius who heads Twitter Spam prevention and she said that they do revoke API access to abusive applications. But I don't think they are taking an aggressive stance against them. Abusive Applications: http://www.huitter.com/mutuality/ http://www.twollo.com/ The combination of these two applications is for outright abuse of the service. They have been around for several months and are known applications to abuse the service with. To make matters worse, Twitter suspends accounts of the people who use these applications rather than targeting the root of the problem, the applications themselves. (Sound counterproductive? RIAA uses a similar policy by going after end users.) I propose that applications need to be more closely scrutinized and can even be flagged as abusive by users. Instead of creating algorithms that detect abnormal user behavior, why not detect abnormal application behavior. Taking a stronger stance against gray area applications could reduce server load on Twitter (giving real applications faster response time) and reduce manpower to deal with spam prevention. I strongly encourage anyone who develops Twitter applications to send this link around. Thanks for reading, Brant twitter.com/BrantTedeschi http://twitter.com/BrantTedeschi
[twitter-dev] Twitter Developer/Founder Community on Ning - Registration Open
We have created a private community on the Ning network for developers and founders of Twitter-related projects. You can connect and communicate with other developers, share ideas, discuss your projects, find contract work and veiw/post events. You can view and join the community here: http://twtfnd.ning.com/ All are welcome and we look forward to seeing you there!
