I think the OWF agreement is an excellent idea - I'd love to see Twitter
join in that agreement with its developers. If Twitter has concerns with it
I'd love to see them get involved in the OWF discussions and perhaps the
agreement could be modified to meet Twitter's needs. Why reinvent the
Ryan,
I realized a few months ago that there were some problems along the lines you have mentioned. I stopped development on my project partially due to these issues and the extremely plastic state of the API. I continue to watch this forum to keep abreast of the state of things but I doubt I
Just an update from our end: I am still working with our General Counsel to
get answers to the questions, but it's going to take a bit. So please bear
with us but we'll get an update to you in the coming weeks after we get back
from LeWeb.
Thanks, Ryan
On Tue, Nov 24, 2009 at 9:12 AM, DeWitt
Hi all,
I recently received a request to implement the retweet api calls in the
python-twitter and java-twitter libraries, but before I proceed I was hoping
for a bit of clarification around the licensing terms for the Twitter API.
My layman's understanding is that without explicit terms there
DeWitt,
Thanks for the email. These are all great questions and I want to make
sure I get all the appropriate answers for you and other people on the
thread so it's clear and transparent. Let me work internally to make
sure we get answers to these and get back to you.
The more general answer is
Great, thank you, Ryan. Looking forward to it.
Please let me know on or off list if there is anything I can do to help.
Cheers,
-DeWitt
On Tue, Nov 24, 2009 at 11:08 AM, Ryan Sarver rsar...@twitter.com wrote:
DeWitt,
Thanks for the email. These are all great questions and I want to make
