[twitter-dev] Re: Attending Chirp? Let's get to know each other better, Before the Conference!
Hope you'll all join the very large developer gathering the evening of 4/13 that emerged out of our hey let's get beer pizza before the conf starts: http://tweetvite.com/event/prechirp ALL are welcome. There will be beer, wine, pizza, photobooth, etc. See you in SF Warmly, Laura Fitton (@pistachio/@oneforty)
[twitter-dev] Twitter Developers at SXSW? Beer O'Clock party Friday 4-6
We're throwing a Beer O'Clock tweetup for Developers Friday (tomorrow) 4-6 pm right across from badge pickup: http://tweetvite.com/event/beeroclock Expect to meet LOTS of other Twitter developers and several angel investors too. Plus, free beer! Anyone else know of developer meetups going on during the event? The entire www.oneforty.com team will be at SXSW starting tomorrow midday. If you're going to be in Austin, we'd REALLY love to meet you. We'll also definitely all be at the Indispensable Twitter Tools panel on Monday at 3:30 in Ballroom D. I'm speaking on the panel and would love your feedback about what you want me to talk about. Drop me a line: la...@oneforty.com. If you are around, definitely PLEASE @us, dm us, say hello, etc. we'd love to meet and hear about your experiences working on the TwitterAPI, and what we can do better to help more of the oneforty.com community find YOUR app. Laura Fitton @pistachio 617-838-2456 Mike Champion @graysky Michael Macasek @macasek Robby Grossman @freerobby Sachin Agarwal @sachinag www.oneforty.com @oneforty Warmly, Laura Laura Fitton CEO/Founder, oneforty inc. la...@oneforty.com 617-838-2456
[twitter-dev] Re: Introduce yourself!
OK awesome x3 - 1) GREAT about the funding!! 2) i didn't know you were working on a Twitter app and 3) i'll see you at Chirp!! When you get a chance, please definitely pop the deets about ThinkTank into http://oneforty.com so we can help it get found - this is *my* startup that i was just teensy tiny embryo incubating when I met you last spring at FOO. We'd also love to collect Abraham's any other libraries you've found useful (just use Suggest App). Last I checked there were only 4 things tagged API Library, Net::Twitter among them, even though we're tracking more than 2500 apps. (Boy have I gotten to learn a LOT about software since I saw you last. :-) ) We're hosting Twitter API developer parties at SXSW (tweetvite.com/ event/beeroclock) the night before Chirp (TBD) Hope you are well hope I see you soon Warmly, Laura Fitton (aka @Pistachio) (who really needs to update her list membership to be from la...@oneforty.com!!!) Laura Fitton CEO/Founder, oneforty inc. la...@oneforty.com 617-838-2456 On Feb 22, 6:40 pm, Gina Trapani ginatrap...@gmail.com wrote: Hi list, I'm @ginatrapani, and I'm working on ThinkTank (http:// thinktankapp.com), an install-it-yourself webapp that archives your tweets, friends, followers, and mentions and makes curating/filtering tweet replies easier. (It also makes use of Abraham's TwitterOAuth library, so THANK YOU kind sir.) It started as a weekend project, but I just got funding by Expert Labs, a non-profit that makes tech for helping government use social media more effectively--so now it's my full-time job. In April, the White House will use ThinkTank for their Grand Challenges project. In short, they'll use Twitter and other services + ThinkTank to gather and curate public feedback about what should be our top-priority scientific and technology challenges. Exciting stuff. ThinkTank's source code is here:http://github.com/ginatrapani/thinktank Here's more about ThinkTank and Expert Labs:http://smarterware.org/5187/thinktank-is-now-at-expert-labs My top API wishlist item is retrieving all the replies to a given tweet. I'm also planning to come to Chirp, and hope to meet you all there. Best, Gina On Feb 19, 12:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1]http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3]https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Very well framed, Dewald. Why a contract for claiming the listing? We provide two ways to associate the developer with the item: Credit vs. Claiming. CREDIT: Providing the rightful developer with credit is no problem and attaches no contractual obligation. A listing on the site with the name of the developer (which we will add on request if the page does not already have it listed) is an editorial listing compiled from publicly available information. CLAIMING: The moment we hand over the keys to edit, that page is now (potentially) a promotional tool. It's now a business service being provided and the contract is to protect both parties. We fully expect many apps will never be sold on the site since that's always going to be the developer's choice. Regardless of what they do we're still offering a free (it will always be free) promotional platform that can be used to promote whatever business the item may be doing elsewhere. All we ask in return is a contract to protect both parties. Make sense? Warmly, Laura On Oct 9, 9:24 pm, Dewald Pretorius dpr...@gmail.com wrote: Maybe, at a more basic level my question is this: Why do I need to enter into a contract with oneforty at all, when all I want to do is say, I am Joe, WonderSocialWidget is my app, and here is more information about it. Isn't this part of oneforty nothing more than a free application directory, where the developer can identify him/herself and provide more information if he/she chooses to do so? Dewald On Oct 9, 9:34 pm, Dewald Pretorius dpr...@gmail.com wrote: Laura, If my understanding is correct, this new contract is applicable when I want to claim my app in oneforty. With that in mind: a) Why do I need to license to oneforty and your sublicensees (whomever that may be) all my trademarks, trade names, service marks, logos or other identifying or distinctive marks. Let's say wondersocialwidget is my trademark. By licensing it to oneforty and your sublicensees, I enable you (collective) to create sites called buywondersocialwidget.com, getsocialwidgethere.com, therealsocialwidget.com, etc., and there is nothing I can do to stop that because I have licensed you to do that. Just for the ability to claim my app in your service? That does not make sense. What then about the unclaimed apps? Will you be violating their trademarks by virtue of the fact that their developers have not agreed to this contract? b) Why is 3.2 necessary at all? In other words, why do I need to license my app to oneforty in order for me to claim it? Shouldn't all this licensing stuff be in the Reseller Agreement? Dewald On Oct 9, 8:14 pm, Pistachio pistachioconsult...@gmail.com wrote: Cross-posting this comment just posted to @BradleyJoyce's blog:http://bit.ly/2RqnU9 Hi folks, We're doing our best to hear and respond to developer feedback and better serve the community. Our approach to the developer contract was wrong. We're working to make it right. Here's how: Revised Publisher Registration Contract * Effective immediately, the old Reseller Agreement is replaced with a Publisher Registration Contract. (View it here:http://oneforty.com/terms/publisher_contract) * This lets you register as a developer and claim your apps. * We're still working on needed improvements to this contract to create productive terms of service that cover registration, claiming and optional donations Two separate agreements: * Publisher Registration Contract (applies if you wish to register for developer privileges to claim and edit your app) * Reseller Agreement (future: will only apply if you wish to offer items for sale at oneforty.com when that functionality is rolled out). This contract will be developed as part of our ecommerce pilot program. Interested in being part of the pilot testing? Ping us at develop...@oneforty.com. Donations * To revise the contract today, we had to temporarily disable the donation service. * We have refunded all donations that were made under the terms of the old contract. * We're revising the Publisher Registration Contract to allow us to turn donations back on for those who opt-in. Reseller Agreement * As part of our ecommerce pilot, we'll create a second contract for developers who wish to sell products on our site. * Its terms will be more developer friendly and created together with your feedback. Thank you for bearing with us while we work out these early kinks. We value your feedback, and we're anxious to make the Twitter community an even better place. As always, you can reach us at develop...@oneforty.com. Warmly, the oneforty team Laura, Mike, Michael and Robby ***NOTE: You do not have to claim your apps to get credit as the developer. Prefer no contract at all? We can add your name as the developer
[twitter-dev] Re: About the oneforty application directory
In reviewing this thread for work on our FAQs, I realized that this aspect of the previous contract never got addressed here on this list. We're not entirely sure where the impression that revenue would be paid out as donations or gifts came from, but it was DEFINITELY never the plan. All revenue terms will be dealt with as revenue. Any words in the (now defunct) contract mentioning gifts and donations were referring explicitly to the actual gifts and donations that developers can elect to receive at the site. Warmly, Laura Laura Fitton, Founder oneforty.com On Sep 29, 4:31 am, Andrew Badera and...@badera.us wrote: As CTO of a startup involved with 501c3s for over two years now, I'm pretty confident in stating that development cannot be donated, period. Services cannot be donated for tax purposes. Only goods can be donated for tax deductions. Services are always taxable, period. No tax benefit for donated services. ∞ 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 Tue, Sep 29, 2009 at 2:47 AM, Chris Babcock cbabc...@kolonelpanic.org wrote: - Some development *is* done by non-profit organizations or could possibly be donated to a non-profit. If the structure of the developer agreement was conduscive to it, as this is, then non-profit work and code donations to non-profit orgs would be encouraged and there could be tax benefits. Chris Babcock
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Cross-posting this comment just posted to @BradleyJoyce's blog: http://bit.ly/2RqnU9 Hi folks, We're doing our best to hear and respond to developer feedback and better serve the community. Our approach to the developer contract was wrong. We're working to make it right. Here's how: Revised Publisher Registration Contract * Effective immediately, the old Reseller Agreement is replaced with a Publisher Registration Contract. (View it here: http://oneforty.com/terms/publisher_contract) * This lets you register as a developer and claim your apps. * We're still working on needed improvements to this contract to create productive terms of service that cover registration, claiming and optional donations Two separate agreements: * Publisher Registration Contract (applies if you wish to register for developer privileges to claim and edit your app) * Reseller Agreement (future: will only apply if you wish to offer items for sale at oneforty.com when that functionality is rolled out). This contract will be developed as part of our ecommerce pilot program. Interested in being part of the pilot testing? Ping us at develop...@oneforty.com. Donations * To revise the contract today, we had to temporarily disable the donation service. * We have refunded all donations that were made under the terms of the old contract. * We're revising the Publisher Registration Contract to allow us to turn donations back on for those who opt-in. Reseller Agreement * As part of our ecommerce pilot, we'll create a second contract for developers who wish to sell products on our site. * Its terms will be more developer friendly and created together with your feedback. Thank you for bearing with us while we work out these early kinks. We value your feedback, and we're anxious to make the Twitter community an even better place. As always, you can reach us at develop...@oneforty.com. Warmly, the oneforty team Laura, Mike, Michael and Robby ***NOTE: You do not have to claim your apps to get credit as the developer. Prefer no contract at all? We can add your name as the developer on a listing without you having to agree to anything beyond the site's general TOS.*** On Oct 9, 5:20 am, Andrew Badera and...@badera.us wrote: Laura, Sounds like you're taking some of the right steps to make your offering better for everyone concerned. I look forward to seeing the results of your efforts. ∞ 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 Fri, Oct 9, 2009 at 1:05 AM, Pistachio pistachioconsult...@gmail.com wrote: Andrew us absolutely correct. I personally bear full responsibility for letting that flawed contract get into production, even on a beta. It was likewise my error of judgment to assume that the alpha testers had been fine with the proposed contract merely because we had not received adverse feedback. We're listening. We're learning. Our comment on Bradley's post (http://bit.ly/DgM40) summarizes some of the contentious points we're revising, but there are others. To make this right, we'd like to better engage the TwitterAPI community in reviewing our next version. We are also separating the claiming terms from the resale terms. One more thing worth mentioning, we held off on building features that will allow developers to offer items for sale because we want to work that - and the related contract issues - out in close cooperation with developers. We'd love to hear from you if you want to have a voice on that. I've been sending out my cell # on all emails bound for developers because we want to be extremely accessible to developers. on email, Twitter, IRC... We will be working hard to earn your trust and to discover how we can better serve. Warmly, Laura Fitton la...@oneforty.com (sent from @pistachio: RT @dwroelands @oneforty needs to change their developer contract #onefortycontracthttp://bit.ly/DgM40//we're seeking feedback) On Oct 8, 10:21 pm, Andrew Badera and...@badera.us wrote: All else aside ... lawyers complicate things? Maybe, but you don't launch a product/platform and expect commitment from outside parties until YOU are happy with what YOUR lawyers have produced and thus YOU are offering to the outside world. There's no defense for a questionable contract. You stand behind your contract, or you don't publish it. Period. ∞ 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 Thu, Oct 8, 2009 at 10:16 PM, Michael Ivey michael.i...@gmail.com wrote: OneForty is not a developer-friendly platform. I think this is a demonstrably false statement. All of my interactions with Laura and the 140 team have been very positive, and she's made it clear that they're working
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Andrew us absolutely correct. I personally bear full responsibility for letting that flawed contract get into production, even on a beta. It was likewise my error of judgment to assume that the alpha testers had been fine with the proposed contract merely because we had not received adverse feedback. We're listening. We're learning. Our comment on Bradley's post (http://bit.ly/DgM40) summarizes some of the contentious points we're revising, but there are others. To make this right, we'd like to better engage the TwitterAPI community in reviewing our next version. We are also separating the claiming terms from the resale terms. One more thing worth mentioning, we held off on building features that will allow developers to offer items for sale because we want to work that - and the related contract issues - out in close cooperation with developers. We'd love to hear from you if you want to have a voice on that. I've been sending out my cell # on all emails bound for developers because we want to be extremely accessible to developers. on email, Twitter, IRC... We will be working hard to earn your trust and to discover how we can better serve. Warmly, Laura Fitton la...@oneforty.com (sent from @pistachio: RT @dwroelands @oneforty needs to change their developer contract #onefortycontract http://bit.ly/DgM40 //we're seeking feedback) On Oct 8, 10:21 pm, Andrew Badera and...@badera.us wrote: All else aside ... lawyers complicate things? Maybe, but you don't launch a product/platform and expect commitment from outside parties until YOU are happy with what YOUR lawyers have produced and thus YOU are offering to the outside world. There's no defense for a questionable contract. You stand behind your contract, or you don't publish it. Period. ∞ 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 Thu, Oct 8, 2009 at 10:16 PM, Michael Ivey michael.i...@gmail.com wrote: OneForty is not a developer-friendly platform. I think this is a demonstrably false statement. All of my interactions with Laura and the 140 team have been very positive, and she's made it clear that they're working on the contract. Sometimes lawyers overcomplicate things, and it takes time to dial it back. And yes, when I claimed Twitpay I balked at the contract initially. We don't have an app to sell, so none of it applied to us, and I knew Laura was working on it, so I went ahead with the registration. Whether you sign it or not, I hope people will give Laura and her team time to sort this out. She's a good person, and has shown a real desire to make something good here. -- ivey On Thu, Oct 8, 2009 at 8:24 PM, Duane Roelands duane.roela...@gmail.com wrote: I read it, and I was horrified. So, I logged into IRC and found two members of the OneForty development team. I asked them to remove my application from the directory. They refused. OneForty is not a developer-friendly platform. On Oct 8, 7:44 pm, brad...@squeejee.com brad...@praexis.com wrote: wow, somehow managed to totally miss that thread... thanks! On Oct 8, 6:07 pm, Dewald Pretorius dpr...@gmail.com wrote: There's another thread herehttp://bit.ly/Owfvdwherethedeveloper contract also raised some eyebrows. Dewald On Oct 8, 7:25 pm, brad...@squeejee.com brad...@praexis.com wrote: There has been a lot of buzz around OneForty.com and what it will mean for all of us Twitter app developers. However, some of the things in their developer contract (that you have to agree to in order to claim your application on their side) gave us (Squeejee) pause after we decided to read the fine print. Please see read the contract for yourself (http://oneforty.com/terms/ publisher_contract), see our blog post with our concerns (http:// squeejee.com/blog/2009/10/08/questions-for-oneforty) and leave your comments! Laura Fitton, the founder of oneforty.com, has been very receptive and wants to engage in open dialogue about the contract. Please add to the discussion!
[twitter-dev] Re: About the oneforty application directory
Hi folks, Laura again. We hear you loud and clear that the contract needs to change - and we agree. We are working on that! Definitely under review = payment minimum threshold and lag time; how the customer relationship is fairly shared if you sell through us, contract cancellation policy and other points. Re: payments to resellers are donations that is not our understanding and I have asked our atty to clarify. We definitely expect developers to need to function as businesses for everyone to succeed. We aim to support that, not complicate your tax dealings! :) can you LMK the specific clause #/s that make it sound like that? The guys are going to weigh in today re: oauth. I know like many of you, figuring out how to imlement it just right has taken time, learning and iteration. Thanks for your patience while we continue to figure out how best to be of service. Dewald you are sweet to think of the risk we face by being as open as we can be and by not being monopolistic like Apple. We're idealist enough to believe that if we make it easier for others to build their businesses we all win together. As always, thanks for all feedback - pro or con - this is what we are in Beta mode to learn. We appreciate your time and insights. Warmly, Laura Laura Fitton, Founder oneforty inc. la...@oneforty.com On Sep 28, 3:05 pm, Dewald Pretorius dpr...@gmail.com wrote: +1. Agree. It is my product that is purchased. No more should OneForty own the customer relationship than an affiliate of mine should own the relationship for having referred a sale to me. The other thing that really bugs is me the payment of the 70% in the form of a gift or donation. I cannot show that in the Sales Revenue of my business. If the amount becomes substantial, how do I explain to the tax man why my for-profit incorporated company is getting all these gifts and donations? And how do I do the accounting for my product units that were sold, but did not generate any top-line revenue? The idea behind OneForty is novel, but I think they face an uphill battle, because they do not have the monopoly on app distribution that the Apple App Store has. Hence, it will not work to try and apply the same business rules as the Apple App Store. Dewald On Sep 28, 11:10 am, Waldron Faulkner waldronfaulk...@gmail.com wrote: But the killer for me is the support-only clause. If I can't own the relationship, that makes it a total no-go.
[twitter-dev] Re: About the oneforty application directory
Hi folks, Really sorry this reply didn't get out sooner; I was on a plane last night when Dewald raised these issues. I regret any concern or alarm caused by our developer contract. We're now reviewing a number of the issues that Dewald brought up because frankly, we don't like them either. The off-site revenue share clause was an outright error that has already been removed from the contract effective today. I'm sorry for the confusion this caused and we will be making further revisions to the contract and clarifying its terms promptly. Please be assured that listings on oneforty.com will always be free -- and free of obligations to the developer. We will never demand a cut in exchange for being listed because we would fail the Twitter Community if our lists of applications left any out. Having a good relationship with the developer community is very important to us. This kind of issue is precisely why we're in private beta -- to work out the kinks and to find out what developers want and need. I'm available at la...@oneforty.com to discuss any concerns or further feedback at any time. Warmly, Laura Laura Fitton, Founder oneforty inc. la...@oneforty.com On Sep 24, 8:25 pm, Dewald Pretorius dpr...@gmail.com wrote: Please read the Publishers Contract that you agree to when you register as a publisher and make yourapplicationavailable for sale throughOneForty. Here's a bird's eye view of some things you need to determine whether you like them or not: 1)OneFortytakes 30% of nett revenue on the sales of your product as royalties. 2) They pay your money (the 70%) within 2 months after the calendar month in which the sale occurred, and only when the amount owed exceeds $250.00. 3) You receive your money as a gift or donation fromOneForty(that may or may not have tax implications). 4) You can only contact customers for support, meaning you are not allowed to contact them for any marketing or upsells. Violations can cause agreement termination, or financial penalties. 5) You must price your item no higher than the lowest price available to other distributors. 6) If customers purchase your item directly from your web site and they came via a link fromOneForty, you must payOneForty30% of that sale. 7) For the first 12 months, you can cancel the agreement with 30 days notice only ifOneFortyhas breached the agreement. 8) After the first 12 months, you can cancel the agreement at will with 60 days notice.
