[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: About the oneforty application directory
Hi Robby, Thanks for the explanation on the read/write access. I hesitated to signon when I saw the access requirement. Many saavy users will hesitate as well. I want to see you get as many users as possible and this will probably come up again when you move to the next phase. It might be worth considering registering two separate applications, one with read access and one with read/write. It wouldn't be quite as seamless because you'd require the user to grant access again for the read/write features, but that approach would result in fewer questions at the initial signon.
[twitter-dev] Re: About the oneforty application directory
On Mon, 28 Sep 2009 16:49:29 -0700 (PDT) Dewald Pretorius dpr...@gmail.com wrote: Then I don't understand. Why would OneForty elect to pay the developer's 70% in the form of a gift or donation to the developer? All hypothetical, no malice imputed... - What if program costs run away and there isn't enough $$$ to cover the obligations? How much can developers legally recover? 30%. - Above a certain $$$ threshold, the accounting requirements change. Reporting 70% of the distribution as a gift effective triples the total payments that can be made to a developer before tax status changes. - 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: About the oneforty application directory
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: 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
I'll vouch for Laura as being an upright person, and all of the other oneforty people I've met are as well. They aren't going to try to screw anyone over and I have faith that whatever they come up with will be fair for developers and the community both. david
[twitter-dev] Re: About the oneforty application directory
Hi folks, This is Robby from oneforty. We wanted to take a moment to address the issues that you all have raised surrounding our use of Twitter OAuth. oneforty requests read/write access to your Twitter account. At present, read access is used to examine the source tag of your tweets, so that we can identify which applications you are using. This allows us to automate filling in the My Apps section of your profile. If your tweets are public, we can do it without read access, but only in limited number because we need to authenticate in order to get past the Twitter API limits. As for write access, we're hoping to add features along the lines of Tweet about this app or DM the app developer. By requesting read/write access, we can provide a much better user experience for handling these features than we could otherwise, as the alternative would be a nonnative mechanism involving popup windows or new browser tabs on twitter.com. We will never, under any circumstances, post to your twitter account without your consent. Any publishing to your tweet stream, sending of DMs, etc. will be the result of an explicit action on your part. It will never be done automatically. It will always be opt-in rather than opt-out. We are in the process of updating our site copy to reflect all of this, but wanted to pass along our intentions to this group sooner rather than later. As always if you have any questions or concerns we are always available at develop...@oneforty.com. Best, Robby (on behalf of @graysky, @macasek and myself)
[twitter-dev] Re: About the oneforty application directory
DM the app developer. Please don't add that as a feature. You are going to enable anybody to DM the developer, whether the developer follows that person or not. Dewald
[twitter-dev] Re: About the oneforty application directory
Let me explain why I said that. There are only two ways you can implement a DM the developer feature. a) Execute a follow API call to make the developer follow the DMer, and then send the DM from the DMer's Twitter account. Presumably you will then also execute a follow API call from DMer to developer, so that the developer can reply to the DM. Bad idea, because the developer loses control over his friends list. b) Act as a DM proxy. The developer gets a DM from @oneforty saying, @user said: bla bla bla... Developer replies to @oneforty and @oneforty DMs the DMer with @developer said: yada yada... Slightly better than a), but it still makes a mockery of Twitter's rule that only your friends can DM you. Dewald On Sep 29, 8:14 pm, Dewald Pretorius dpr...@gmail.com wrote: DM the app developer. Please don't add that as a feature. You are going to enable anybody to DM the developer, whether the developer follows that person or not. Dewald
[twitter-dev] Re: About the oneforty application directory
It would be nice if Twitter was an OpenID end point (hint hint). OpenID could be used all over the place, but at the same time apps like oneforty could use this for allowing a user to login. I know has their own login with twitter thing, but I think it would be nice to have OpenID so my twitter account could be used on sites that are not twitter powered. Brian Atkinson On Mon, Sep 28, 2009 at 5:19 PM, JDG ghil...@gmail.com wrote: Unfortunately, best as I can ascertain, that would violate the OAuth spec (I may, of course, be wrong -- I often am :-) ). There are RW tokens and RO tokens, but no Auth-only tokens. The best you could hope for, given the current state of the spec, would be for an app to simply get, then discard, the Access token. This is a good use case for OAuth, and perhaps should be brought up with them as a scenario for future versions of the spec. On Mon, Sep 28, 2009 at 14:47, Jim Renkel james.ren...@gmail.com wrote: Yes, you can check the Yes, use Twitter for login, or not. I'm not sure what this does, either way. But you have to select one of the Read Write or Read-only radio buttons under the Default Access type: heading. There doesn't appear to be any way to turn them both off. So it seems you have always request (and receive) at least read access to the data of user's that authorize your application to act for them on twitter. This is what I and others were trying to point out, and object to: you can't authorize without granting read access. Why authorize without granting read access? Just to verify that they are the twitter user they claim to be, without reading, or writing, any of their data. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Brian Smith Sent: Monday, September 28, 2009 09:32 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: About the oneforty application directory Dossy Shiobara wrote: It would be nice if Twitter made authentication only as an option for OAuth. Twitter already has this. It is called Sign in with Twitter. - Brian -- Internets. Serious business.
[twitter-dev] Re: About the oneforty application directory
The rev-share doesn't kill the deal for me, although it does feel steep, and just because Apple gets 30% for the app store, not sure that number works in all cases. Also 60 day terms are discouraging. But the killer for me is the support-only clause. If I can't own the relationship, that makes it a total no-go. On Sep 27, 4:14 pm, Jim Renkel james.ren...@gmail.com wrote: I agree! Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dossy Shiobara Sent: Sunday, September 27, 2009 14:08 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: About the oneforty application directory Frankly, I don't even like the idea of read-access for an application like this. It would be nice if Twitter made authentication only as an option for OAuth. Better would be an option on the accept/deny OAuth page where users can select what access to grant to an application - defaulting to perhaps what access the application desires. On 9/25/09 8:04 PM, Jim Renkel wrote: What will you be using my twitter account for, other than authorization? If you reregister the site to only need read access to my twitter account, I would be a lot less reluctant to use it. -- 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: About the oneforty application directory
Dossy Shiobara wrote: It would be nice if Twitter made authentication only as an option for OAuth. Twitter already has this. It is called Sign in with Twitter. - Brian
[twitter-dev] Re: About the oneforty application directory
Yes, you can check the Yes, use Twitter for login, or not. I'm not sure what this does, either way. But you have to select one of the Read Write or Read-only radio buttons under the Default Access type: heading. There doesn't appear to be any way to turn them both off. So it seems you have always request (and receive) at least read access to the data of user's that authorize your application to act for them on twitter. This is what I and others were trying to point out, and object to: you can't authorize without granting read access. Why authorize without granting read access? Just to verify that they are the twitter user they claim to be, without reading, or writing, any of their data. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Brian Smith Sent: Monday, September 28, 2009 09:32 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: About the oneforty application directory Dossy Shiobara wrote: It would be nice if Twitter made authentication only as an option for OAuth. Twitter already has this. It is called Sign in with Twitter. - Brian
[twitter-dev] Re: About the oneforty application directory
+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
Unfortunately, best as I can ascertain, that would violate the OAuth spec (I may, of course, be wrong -- I often am :-) ). There are RW tokens and RO tokens, but no Auth-only tokens. The best you could hope for, given the current state of the spec, would be for an app to simply get, then discard, the Access token. This is a good use case for OAuth, and perhaps should be brought up with them as a scenario for future versions of the spec. On Mon, Sep 28, 2009 at 14:47, Jim Renkel james.ren...@gmail.com wrote: Yes, you can check the Yes, use Twitter for login, or not. I'm not sure what this does, either way. But you have to select one of the Read Write or Read-only radio buttons under the Default Access type: heading. There doesn't appear to be any way to turn them both off. So it seems you have always request (and receive) at least read access to the data of user's that authorize your application to act for them on twitter. This is what I and others were trying to point out, and object to: you can't authorize without granting read access. Why authorize without granting read access? Just to verify that they are the twitter user they claim to be, without reading, or writing, any of their data. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Brian Smith Sent: Monday, September 28, 2009 09:32 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: About the oneforty application directory Dossy Shiobara wrote: It would be nice if Twitter made authentication only as an option for OAuth. Twitter already has this. It is called Sign in with Twitter. - Brian -- Internets. Serious business.
[twitter-dev] Re: About the oneforty application directory
I too could be wrong, and often am, but I don't see anything in the OAuth specification (http://oauth.net/core/1.0a) about what an access token could or does allow access to, i.e., reading resources as opposed to reading and writing resources. The spec seems to be completely silent on the granularity of access that is granted to resources via its mechanisms. So I think twitter would be perfectly legitimate in granting authentication only, authentication and read access, and authentication and read and write access levels of authorization. I have previously proposed that the ability to geocode tweets be an additional level of authorization, and I could also see additional levels, or orthogonal capabilities, for, e.g., enabling geo-coding, access to e-mail addresses and device phone numbers, etc. Comments expected and welcome. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of JDG Sent: Monday, September 28, 2009 17:20 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: About the oneforty application directory Unfortunately, best as I can ascertain, that would violate the OAuth spec (I may, of course, be wrong -- I often am :-) ). There are RW tokens and RO tokens, but no Auth-only tokens. The best you could hope for, given the current state of the spec, would be for an app to simply get, then discard, the Access token. This is a good use case for OAuth, and perhaps should be brought up with them as a scenario for future versions of the spec. On Mon, Sep 28, 2009 at 14:47, Jim Renkel james.ren...@gmail.com wrote: Yes, you can check the Yes, use Twitter for login, or not. I'm not sure what this does, either way. But you have to select one of the Read Write or Read-only radio buttons under the Default Access type: heading. There doesn't appear to be any way to turn them both off. So it seems you have always request (and receive) at least read access to the data of user's that authorize your application to act for them on twitter. This is what I and others were trying to point out, and object to: you can't authorize without granting read access. Why authorize without granting read access? Just to verify that they are the twitter user they claim to be, without reading, or writing, any of their data. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Brian Smith Sent: Monday, September 28, 2009 09:32 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: About the oneforty application directory Dossy Shiobara wrote: It would be nice if Twitter made authentication only as an option for OAuth. Twitter already has this. It is called Sign in with Twitter. - Brian -- Internets. Serious business.
[twitter-dev] Re: About the oneforty application directory
On Mon, Sep 28, 2009 at 3:05 PM, Dewald Pretorius dpr...@gmail.com wrote: 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? Not sure how it works in other countries, but in the U.S. revenue is revenue is revenue; most gifts are income to the person who receives them. Even if you are a non-profit, if you're making a profit from a substantial part of your operations, you can end up owing taxes on it, even if you call the income a gift. Otherwise, everybody would call everything a gift and nobody would pay taxes! The fundamental rule is that when the gift is actually in exchange for something of value, it is income to the receiver and not deductible as a donation to the giver. Nick
[twitter-dev] Re: About the oneforty application directory
Nick, Then I don't understand. Why would OneForty elect to pay the developer's 70% in the form of a gift or donation to the developer? Dewald On Sep 28, 8:34 pm, Nick Arnett nick.arn...@gmail.com wrote: Not sure how it works in other countries, but in the U.S. revenue is revenue is revenue; most gifts are income to the person who receives them. Even if you are a non-profit, if you're making a profit from a substantial part of your operations, you can end up owing taxes on it, even if you call the income a gift. Otherwise, everybody would call everything a gift and nobody would pay taxes! The fundamental rule is that when the gift is actually in exchange for something of value, it is income to the receiver and not deductible as a donation to the giver. Nick
[twitter-dev] Re: About the oneforty application directory
Frankly, I don't even like the idea of read-access for an application like this. It would be nice if Twitter made authentication only as an option for OAuth. Better would be an option on the accept/deny OAuth page where users can select what access to grant to an application - defaulting to perhaps what access the application desires. On 9/25/09 8:04 PM, Jim Renkel wrote: What will you be using my twitter account for, other than authorization? If you reregister the site to only need read access to my twitter account, I would be a lot less reluctant to use it. -- 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: About the oneforty application directory
I agree! Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dossy Shiobara Sent: Sunday, September 27, 2009 14:08 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: About the oneforty application directory Frankly, I don't even like the idea of read-access for an application like this. It would be nice if Twitter made authentication only as an option for OAuth. Better would be an option on the accept/deny OAuth page where users can select what access to grant to an application - defaulting to perhaps what access the application desires. On 9/25/09 8:04 PM, Jim Renkel wrote: What will you be using my twitter account for, other than authorization? If you reregister the site to only need read access to my twitter account, I would be a lot less reluctant to use it. -- 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: 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.
[twitter-dev] Re: About the oneforty application directory
Thanks Nelu! Not sure when, but the chances of Chicago are really good. The next few trips are mid/late October, Mid November and early December. Details will be kept up-to-date at http://bit.ly/tour140. Also? We're working to get this thing out into the sunlight as quickly as possible to that folks can casually browse without signups, etc. Just as you point out, that's important. Thanks all for the feedback and glad to be part of this list. I'll pretty much keep my mouth shut here and leave it to oneforty's developers say intelligent development related stuff, but I'm a lurking fan of the work all you guys are doing. Warmly, Laura Laura Fitton, Founder oneforty inc. la...@oneforty.com http://twitter.com/pistachio http://twitter.com/oneforty On Sep 24, 3:55 pm, Nelu Lazar cont...@nelulazar.com wrote: I have checked thedirectorypast days, and claimed my app. Congrats on a work very well done. A couple of suggestions: - the site doesn't currently allow new lines in the description field; this could be useful for listing features; - although it's understandable why thedirectoryrequires user's authentication, specific pages of the website may be more useful if public, to allow new users to familiarize with Twitter's capabilities and the apps around it. I live near Chicago, any chance you will add it to your tour? Nelu Lazar Founder Tweetvisor.comhttp://twitter.com/nelulazar On Sep 24, 3:24 pm, Alex Payne a...@twitter.com wrote: Just wanted to pass on a note from the team atoneforty.com, who recently launched with over 1300 Twitter applications in their directory. Your app might already be on their site. If it's not yet, you can register as a developer and add it. Once you register and claim your app you can promote it with screenshots, descriptions, tags, and reviews. If you saw the early alpha version ofoneforty, it's much improved - real home page, most popular apps ranking and essentials. New item pages just launched and look much better than the prototype did. Their team working on the ability to sell apps right on the site. They're also definitely looking for your feedback. @freerobby, @graysky, @macasek, and @pistachio are often in the #twitterapi IRC channel. There's more contact info below, too. A note from theonefortyteam and info on how to register, claim, edit add stuff: We builtonefortyto help the best stuff being built on the Twitter API get found and get profitable. Come claim your apps, add content and add new projects in the Twitter appstoreoneforty.com To get started: Sign in via oauth. (We whitelisted as many dev usernames as we could find. If you can't login already use invite code TWAPI and we'll let you right in.) Register as a developer:http://oneforty.com/me/developer_profile Search for and claim your app (Suggest Item if we don't have it yet!) Check out your item's page, make sure it's tagged well, tweet a link to it, etc Once approved, add details, screenshots, media coverage and more In the near future you'll be able to offer things for sale right in oneforty. For now we link to your sites and (optionally) let you collect donations. We want to help you get your app found, rated, reviewed and into the hands of the users who need it the most. We also want to get the Twitter community to do a better job supporting developers and apps so that your innovation can flourish. It's frustrating when great apps go defunct because of server costs, etc. We're anticipating decent blog and press coverage, so we want your to look its best! Please let us know whatever we can do to help you. Thank you. We'd really love to know what you think and what you want: Uservice feedback forum. Any questions at all, develop...@oneforty.com or 617-645-7767, anytime. onefortyFounder Laura (@Pistachio) Fitton will be at events in Fort Worth 9/25, Seattle 9/26-27, SF/bay area 9/27-30 and Boston 10/1 and would love to meet you (seehttp://bit.ly/tour140forTweetup event info). She also wrote Twitter for Dummies. Check 'em out! -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: About the oneforty application directory
oneforty.com seems like a valuable and useful site, one I would definitely take advantage of, but I have a couple of questions and concerns that need to be answered before I do so. 1. I'm not sure why I have to grant the site access to a twitter account to use, and I am REALY concerned about why it needs update access, not just read access. I don't want this site, or any other site like it, to be able to update my twitter account, generating tweets or DMs, etc., until I see what the benefit of it doing so is. What will you be using my twitter account for, other than authorization? If you reregister the site to only need read access to my twitter account, I would be a lot less reluctant to use it. 2. The site seems to be geared toward client applications. My application is, for now, just a web-site (http://twxlate.com) with the possibility of it evolving into desktop and smart phone client applications in the future. Is your intention to be as relevant to web-sites as to client applications? Thanks in advance. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Alex Payne Sent: Thursday, September 24, 2009 14:24 To: Twitter Development Talk Subject: [twitter-dev] About the oneforty application directory Just wanted to pass on a note from the team at oneforty.com, who recently launched with over 1300 Twitter applications in their directory. Your app might already be on their site. If it's not yet, you can register as a developer and add it. Once you register and claim your app you can promote it with screenshots, descriptions, tags, and reviews. If you saw the early alpha version of oneforty, it's much improved - real home page, most popular apps ranking and essentials. New item pages just launched and look much better than the prototype did. Their team working on the ability to sell apps right on the site. They're also definitely looking for your feedback. @freerobby, @graysky, @macasek, and @pistachio are often in the #twitterapi IRC channel. There's more contact info below, too. A note from the oneforty team and info on how to register, claim, edit add stuff: We built oneforty to help the best stuff being built on the Twitter API get found and get profitable. Come claim your apps, add content and add new projects in the Twitter appstore oneforty.com To get started: Sign in via oauth. (We whitelisted as many dev usernames as we could find. If you can't login already use invite code TWAPI and we'll let you right in.) Register as a developer: http://oneforty.com/me/developer_profile Search for and claim your app (Suggest Item if we don't have it yet!) Check out your item's page, make sure it's tagged well, tweet a link to it, etc Once approved, add details, screenshots, media coverage and more In the near future you'll be able to offer things for sale right in oneforty. For now we link to your sites and (optionally) let you collect donations. We want to help you get your app found, rated, reviewed and into the hands of the users who need it the most. We also want to get the Twitter community to do a better job supporting developers and apps so that your innovation can flourish. It's frustrating when great apps go defunct because of server costs, etc. We're anticipating decent blog and press coverage, so we want your to look its best! Please let us know whatever we can do to help you. Thank you. We'd really love to know what you think and what you want: Uservice feedback forum. Any questions at all, develop...@oneforty.com or 617-645-7767, anytime. oneforty Founder Laura (@Pistachio) Fitton will be at events in Fort Worth 9/25, Seattle 9/26-27, SF/bay area 9/27-30 and Boston 10/1 and would love to meet you (see http://bit.ly/tour140 for Tweetup event info). She also wrote Twitter for Dummies. Check 'em out! -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: About the oneforty application directory
Thanks Alex. I work at oneforty, and would be really interested to hear what would be useful for twitter developers. I've written a couple Twitter-based apps, and found it is hard to have them discovered, hear back from users, or even see what else is out there in the space. (And having half of them named Tw-something, doesn't help!) If you're interested in checking it out, I'll make sure anyone who signs up via this link gets in quickly: http://oneforty.com/?code=TWAPI Cheers, -mike -- Mike Champion Engineering Lead, oneforty @graysky On Sep 24, 3:24 pm, Alex Payne a...@twitter.com wrote: Just wanted to pass on a note from the team at oneforty.com, who recently launched with over 1300 Twitter applications in their directory. Your app might already be on their site. If it's not yet, you can register as a developer and add it. Once you register and claim your app you can promote it with screenshots, descriptions, tags, and reviews. If you saw the early alpha version of oneforty, it's much improved - real home page, most popular apps ranking and essentials. New item pages just launched and look much better than the prototype did. Their team working on the ability to sell apps right on the site. They're also definitely looking for your feedback. @freerobby, @graysky, @macasek, and @pistachio are often in the #twitterapi IRC channel. There's more contact info below, too. A note from the oneforty team and info on how to register, claim, edit add stuff: We built oneforty to help the best stuff being built on the Twitter API get found and get profitable. Come claim your apps, add content and add new projects in the Twitter appstore oneforty.com To get started: Sign in via oauth. (We whitelisted as many dev usernames as we could find. If you can't login already use invite code TWAPI and we'll let you right in.) Register as a developer:http://oneforty.com/me/developer_profile Search for and claim your app (Suggest Item if we don't have it yet!) Check out your item's page, make sure it's tagged well, tweet a link to it, etc Once approved, add details, screenshots, media coverage and more In the near future you'll be able to offer things for sale right in oneforty. For now we link to your sites and (optionally) let you collect donations. We want to help you get your app found, rated, reviewed and into the hands of the users who need it the most. We also want to get the Twitter community to do a better job supporting developers and apps so that your innovation can flourish. It's frustrating when great apps go defunct because of server costs, etc. We're anticipating decent blog and press coverage, so we want your to look its best! Please let us know whatever we can do to help you. Thank you. We'd really love to know what you think and what you want: Uservice feedback forum. Any questions at all, develop...@oneforty.com or 617-645-7767, anytime. oneforty Founder Laura (@Pistachio) Fitton will be at events in Fort Worth 9/25, Seattle 9/26-27, SF/bay area 9/27-30 and Boston 10/1 and would love to meet you (seehttp://bit.ly/tour140for Tweetup event info). She also wrote Twitter for Dummies. Check 'em out! -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: About the oneforty application directory
I have checked the directory past days, and claimed my app. Congrats on a work very well done. A couple of suggestions: - the site doesn't currently allow new lines in the description field; this could be useful for listing features; - although it's understandable why the directory requires user's authentication, specific pages of the website may be more useful if public, to allow new users to familiarize with Twitter's capabilities and the apps around it. I live near Chicago, any chance you will add it to your tour? Nelu Lazar Founder Tweetvisor.com http://twitter.com/nelulazar On Sep 24, 3:24 pm, Alex Payne a...@twitter.com wrote: Just wanted to pass on a note from the team at oneforty.com, who recently launched with over 1300 Twitter applications in their directory. Your app might already be on their site. If it's not yet, you can register as a developer and add it. Once you register and claim your app you can promote it with screenshots, descriptions, tags, and reviews. If you saw the early alpha version of oneforty, it's much improved - real home page, most popular apps ranking and essentials. New item pages just launched and look much better than the prototype did. Their team working on the ability to sell apps right on the site. They're also definitely looking for your feedback. @freerobby, @graysky, @macasek, and @pistachio are often in the #twitterapi IRC channel. There's more contact info below, too. A note from the oneforty team and info on how to register, claim, edit add stuff: We built oneforty to help the best stuff being built on the Twitter API get found and get profitable. Come claim your apps, add content and add new projects in the Twitter appstore oneforty.com To get started: Sign in via oauth. (We whitelisted as many dev usernames as we could find. If you can't login already use invite code TWAPI and we'll let you right in.) Register as a developer:http://oneforty.com/me/developer_profile Search for and claim your app (Suggest Item if we don't have it yet!) Check out your item's page, make sure it's tagged well, tweet a link to it, etc Once approved, add details, screenshots, media coverage and more In the near future you'll be able to offer things for sale right in oneforty. For now we link to your sites and (optionally) let you collect donations. We want to help you get your app found, rated, reviewed and into the hands of the users who need it the most. We also want to get the Twitter community to do a better job supporting developers and apps so that your innovation can flourish. It's frustrating when great apps go defunct because of server costs, etc. We're anticipating decent blog and press coverage, so we want your to look its best! Please let us know whatever we can do to help you. Thank you. We'd really love to know what you think and what you want: Uservice feedback forum. Any questions at all, develop...@oneforty.com or 617-645-7767, anytime. oneforty Founder Laura (@Pistachio) Fitton will be at events in Fort Worth 9/25, Seattle 9/26-27, SF/bay area 9/27-30 and Boston 10/1 and would love to meet you (seehttp://bit.ly/tour140for Tweetup event info). She also wrote Twitter for Dummies. Check 'em out! -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: About the oneforty application directory
I wish they would provide more information. You sign in to oneforty by logging in through Twitter and authorizing your Twitter account to talk to oneforty. We'll do the rest. What rest? What is it going to do on my Twitter account? Dewald
[twitter-dev] Re: About the oneforty application directory
Please read the Publishers Contract that you agree to when you register as a publisher and make your application available for sale through OneForty. Here's a bird's eye view of some things you need to determine whether you like them or not: 1) OneForty takes 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 from OneForty (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 from OneForty, you must pay OneForty 30% of that sale. 7) For the first 12 months, you can cancel the agreement with 30 days notice only if OneForty has breached the agreement. 8) After the first 12 months, you can cancel the agreement at will with 60 days notice.
[twitter-dev] Re: About the oneforty application directory
Ha ha - better go remove www.MyPostButler.com from that site - how exactly are they going to track sales from click through links? Cheers, Dean -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dewald Pretorius Sent: Thursday, September 24, 2009 8:25 PM To: Twitter Development Talk Subject: [twitter-dev] Re: About the oneforty application directory Please read the Publishers Contract that you agree to when you register as a publisher and make your application available for sale through OneForty. Here's a bird's eye view of some things you need to determine whether you like them or not: 1) OneForty takes 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 from OneForty (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 from OneForty, you must pay OneForty 30% of that sale. 7) For the first 12 months, you can cancel the agreement with 30 days notice only if OneForty has breached the agreement. 8) After the first 12 months, you can cancel the agreement at will with 60 days notice.
