mehdim

I love the comparison between web ecosytem and biological ecosystem

True, IFTTT recipes are often too limited, because targeting non developers, they limit a lot inputs and ouputs of APIs. But all these APIs can do lot more. The reason why there we made webshell.io , "IFTTT for developers", enabling developers to script APIs in Javascript, with the whole expressivity of a a scripting language for more advanced APIs scripts(recipes) :)

We made it for helping people in big organizations and in startups to better understand ROI of APIficiation of a business. New distribution models, scalability and architecture, open innovation

The "building bricks company" or the "API driven company"

My IT infrastructure is Amazon

My CRM is Salesforce

My Storage is Box.net etc...

Lots of players in API economy

You have API managements solution : Layer7, SOAsoftware, APIgee, Mashery, 3scale and plenty of new ones.

Then you have API distribution channels with market place and automation platforms : Mashape, Zapier, Apiary Temboo, elastic, IFTTT, Webshell

To my mind, this is all API economy which is addressing this point.

What you are talking is a part of the Steve Klabnik presentation yesterday at APIdays event "Why Open?" in Paris.

He talked about exactly what you're saying, look a this photo of its slide about "organisation of organs" with APIs http://twitter.com/Anton_in/status/275614644557717504/photo/...

We will release soon his slides...

Is it a kind of change.org?

developer version of qsview.com :) http://webshell.io/prototype/OWFiO/2 and don't forget to run it!

Nice slidedeck for good APIs principles evangelisation But nothing on Policy and Terms of Use which become the main issue for developers , before good design.

Some thoughts between facts, compilation and original work of authorship

http://en.wikibooks.org/wiki/US_Copyright_Law/Copyrightable_...

Does a orignal list of URLs is copyrightable? If you follow the copyritht , yes. But an other URL compilation of the same API which would be a kind of "list" (alphabetical for example) would not...

In all cases, if original URLs lists are copyrightable, Google results too are under copyright, because they are sorted by pagerank, which is an orginal way to sort links...

Any creative content or writing can be copyrightable. But in the case of Oracle vs Google, the end of the case was that an API is just no more than a list of rules and URLs, nothing "creative".

And a list is not copyrightable.

Think to the Yellow Pages for examples. No Copyright on name, address and numbers (hopefully) , because no specific form or shape to these writings.

The case is to define if design an API is more than listing URLs. I don't think so, and the Judge Alsup of Oracle vs Google who was developer too, said the same thing.

But API providers will try to not accept this. Do you remeber Twitter's message to developers

http://apijoy.tumblr.com/post/34350096121/twitter-api-teams-...

?

IFTTT, Zapier, Webshell.io, Webscript.io, Elasctic.io, Apiary.io, Opalang.org, Rules.io etc...we have something to bring to api@eff.org

Mistakes between french and english. We fix it.

We are working on it. We gived some explanations because each people wasn't not understanding the same value, we are in a step by step explanation of what we've done.

You're definitively right.

Follow us, more examples soon.

Thank you for your advise.

We want to be an API of APIs, so we are an API for using and combining others ! api.webshell.io

In our doc , you can read how to already use it on webshell.io/docs/reference

  "In the programmable web where APIs lie,
  One shell to rule them all, one shell to find them,
  One shell to bring them all and in the cloud bind them"

;)

You can use it as an IDE but it’s not the Webshell’s job ! Our job is to make an “API mashup factory” for people which want to make fast applications based on APIs.

It would be impossible to make a lib which maintain all third party APIs (arround 8000 today), it’s for that we made it as a platform where everything is always working.

Please note that Webshell is an API too, and you can call scripts as a REST/JSON API.

“Sandbox API workflow” : we have a REPL prototyping part for helping you to see very fast a result of API scripting results, as for server side API (Facebook, Spotify...) as for Client side (GoogleMaps, Youtube player etc...)

After you have two choices.

- Make it again by yourself, with the different API protocols, Oauth1.0 or Oauth2.0 , manage rate limits and keep an eye for maintenance on all your APIs in your application.

- Or push the “create API” button on top right of the Webshell prototyping REPL, so generating a new API of your mashup, use it in production and share it with other developers which would like to use it too.

Our job is to keep an eye for you on API maintenance, easy Oauth integration, APIkeys and rate limit management, analytics. We will be implement each feature step by step during the public beta.

Dependancy? We are an API like other APIs. We behave like Back-end-as-as Service as Parse for example. You could do it yourself to not be dependant, but if you implement it fast for your application, with lot of integrated tools, you will keep it in production.

You can see us as a kind of API-as-a-service backend... ;)

done. :)

To put in a nutshell "the idea is more to be an IFTTT/Zapier for developers but without limited inputs and outputs by Graphical User Interface" ;)

Thanks. We will use it to explain better the value next time. ;)

Nice to meet you ;)

We would be glad to talk with you.

Contact us team[at]webshell.io if you are interested :)

Yes you're right, we are already working on this platform for easy API integration to Webshell. News about it soon.

But for the moment you can share with us your API by sharing a WADL of it and make a pull-request on our Github http://github.com/webshell

The idea is more to be an IFTTT/Zapier for developers but without limited inputs and outputs by Graphical User Interface.

With the expressiviy of an all language as Javascript and a console interface to explore API and check easilty data response, developers may not be limited when combining APIs and make exactly what they wanted to do.

But Webscript.io is nice too, some similarities but not the same usefulness, not the same paradigm and not the same language : Javascript ;)

Our idea is to help web and mobile developers

- to sandbox API workflow (server-side APIs and/or client-side APIs) into the REPL interface "prototype"

- and then create a new API based on this API workflow(or "prototype")

- use this new API in production into their own application and share it with other developers

we want to bring fast API discovery and exploration, easy multiple API mashups or scripting, then new API creation for use in production. We make for them maintenance, and one-line-of-code authentication and some cool builtins.

This with server side APIs as Client side APIs, in the same shell interface, Javascript, Coffeescript, or even Typescript.

But is seems not obvious apparently... ;)

Can you share with us what and why you did'nt understand it when testing the tour?

PS: Everybody can also brings to Webshell API explorer its own API (you can read the doc on how to add your own API to be scripted and used by developers)

You've sent the first signal that we are evolving from a facebook generation to a github generation, so from a numerical social generation to a programmable generation.

Thank you !

Thanks for what you've down, I'll play a little with it. :)

It is a fantasctic exercise for game theory ! If you have success with your post with lot of forks on github and upvotes, we may expect that a lot of people will follow it and the success of HN posts will be not following your script. I go now make an anti-script ;)

swagger.wordnik.com, apiary.io, turnapi.com Enjoy!

Instead of whining, use your valuable time to make start-ups that solves big pains, bring value to users and customers, with a good UX, which will then make $millions revenues and valuated $billions. Then your voice will have power and audience to make things change if you want so, and you'll become politician from the do-ers side. I'll even vote for you, but lot of work before... I'm a french startup entrepreneur and I approve this message. :)

Net Neutrality is the reason the Internet has driven online economic innovation. It protects our right to use any equipment, content, application or service without interference from the network provider. With Net Neutrality, the network’s only job is to move data — not choose which data to privilege with higher-quality service and which to demote to a slower lane.

This would be the same for APIs, which are too often driven only by business when investors strategies come in the place. Stay open for an API without discrimination and tiering on data access and re-use is giving trust to all your ecosystem for building future business on it. Don't respect it is enfrenging the API neutrality concept.

More on what would be API neutrality here : http://api500.com/post/31465739810/what-is-api-neutrality

This why this is important to put the basis theory of API neutrality http://api500.com/post/31465739810/what-is-api-neutrality

This is why we need API neutrality http://api500.com/

it works anyway...;)

Yahoo pipes is great. And new automation platforms are fun and useful for non developers. But if you want to be completely freewhen programming the web, let APIs to developers.

http://api500.tumblr.com/post/28165124923/your-mashup-is-so-...