Oauthd: OAuth.io open sourced | Hacker News Reader

Oauthd: OAuth.io open sourced

github.com

59 pointsnickcolley15 comments

This looks sick, and easy to deploy just redis and node. Will give it try for https://commando.io and a GitHub integration.

[[ Tried getting it running, but ran into an issue. ]]

https://github.com/oauth-io/oauthd/issues/5

Would be better if you could raise a bug on the github page...

just did. :)

AGPLv3. Technically open source, but not what most have in mind.

may be to your mind GNU/GPL is also "technically open source, but not what most have in mind." Licenses that enforce open source to spread are to my mind more in the open source spirit than MIT or Apache2.0

You think that people understand open source as free (as free to re-use)? I don't believe so, there are many open source licences for these reasons, depending on the willingness of the authors. Linux is open source or not? ;)

Nope. AGPLv3 is very different from GPLv2. Also the wishes of the creators of Linux and git make the GPLv2 more comfortable to me. Companies that have a dual-licensing model with GPLv2 and a paid proprietary license may try to stretch the meaning of the GPLv2 to make it more restrictive.

The problem with oauth.io is I could spend time learning it to use it on a personal project and then not be able to apply the same knowldege on a client project where the client doesn't find the copyleft situation acceptable.

May be they will go like MongoDB, RethinkDB, OpenERP, SugarCRM as well as WURFL, they all now utilize the AGPLv3 as a vehicle for dual commercial licensing.

Doing what SugarCRM is doing would be better than what they're doing right now. Many companies would find both AGPL and SaaS against their policies but would be OK with paying for non-copyleft software that they can install on their own server.

You like to get to use some software for free, but you also want to use it so others might not see your modifications.

How exactly is this different from GPLv2, if the web service you were writing was going to be shipped on a router? and why should you be allowed to use someone else code but then prevent others to see your modifications?

Oversimplified refresher for anyone wanting to know what we're talking about:

Least restrictive

  * MIT/2,3,4-clause BSD/Apache (pretty much anything, the terms are clear (except Apache))
  * LGPL (usually for libraries that can link to non GPL stuff)
  * GPLv2 (if you change the source and ship product, you must reveal the source. can't link with other licenses) 
  * GPLv3 (closed the Tivo loophole)
  * Affero GPL (no services)

Most restrictive

Without a license being specified, it's difficult/impossible to include a project in anything commercial.

from http://www.tldrlegal.com/

GPLv2 : You may copy, distribute and modify the software but you must relicense any changes and your entire project under GPLv2 and disclose all the source code

GPLv3 : You may copy, distribute and modify the software as long as you track changes/dates of in source files and keep modifications under GPL. You can distribute your application using a GPL library commercially, but you must also provide the source code

AGPL : The AGPL license differs from the other GNU licenses in that it was built for network software. You can distribute modified versions if you keep track of the changes and the date you made them. As per usual with GNU licenses, you must license derivatives under AGPL. It provides the same restrictions and freedoms as the GPLv3 but with an additional clause which makes it so that source code must be distributed along with web publication

The most restrictive for me for commercial use is GPLv2, because you have to open source ALL the project, not only the modified part. With GPLv3 and AGPL, just the modifications of the source code , not all the project. It is a question of point of view about "restrictions".

Will be quite interesting when the emperor discovers he cannot go outside with his new clothes.

The concern with AGPL is philosophical dissonance of allowing positive rights of freedom while simultaneously enforcing negative rights, e.g., restrictions on use. I see limitations as failure and route through them (ZoL awesome CDDL hack with DKMS).

Zealous enmity accomplishes less than frenemies, and tips your hand besides.

Well, you can't fork, slap different logo, put lower price and compete with oauth.io. So yeah, not what you have in mind.

But on the other hand, this license is no different than GPLv3 except being made for SaaS-type of projects.

Of course you can. But if you do, you have to make your changes available to your users. As oauth.io is already giving away the source code, you'd even be competing on equal(ish) terms.

If you are looking for software which you can hide modification of the software by ripping out any feature that self-print the source code to the user, then yes, this is not the open source licensed software for you.

However, if your not trying to hide modifications by ripping out features, then hey, this might be useful software someone is offering you for free.

Reply on news.ycombinator.com