License? about fastflicker HOT 9 CLOSED

What file are you interested in?

from fastflicker.

well, the web socker server and it JS client...

from fastflicker.

I mean no license means the code can be looked at but never used ;)

from fastflicker.

And FWIW, this would apply to https://github.com/Paraintom/FastFlickerChatBookmarklet and https://github.com/Paraintom/FastFlickerChatComponent

from fastflicker.

Pombredanne, I would like to be clear on what is going on.
First of all, I always wanted personally to make this code fully Open Source (seems to be MIT License).

I have the following problem :
This projects is using modified and/or unmodified part of other software.
It would be time consuming for me to find how I have to legally handle this.
I would eventually expose myself to claims that I opensourced ideas that wasn't mine.
(something like this : http://www.thepatentscam.com/ , yes life is crazy).

To sum up, it would take me some time and some risks and I will no gain anything from it.
I am a developer and all this legal darkness is far out from my comfort zone.
From my point of view, I will not sue you for using FastFlicker code.

from fastflicker.

To give you an example, FastFlicker use this websocket librairy : https://github.com/dpallot/simple-websocket-server (MIT License)

from fastflicker.

Another example for https://github.com/Paraintom/FastFlickerChatBookmarklet/blob/master/bookmarklet.html :
It is using a piece of code from http://ted.mielczarek.org/code/mozilla/bookmarklet.html .

The terms of use is here : http://www.brainjar.com/terms.asp

Can he sue me already? Perhaps, I don't know.

from fastflicker.

@Paraintom I am not a lawyer ... that said: if you are not clear about the license terms of your code, then you should not make it public IMHO. I am somewhat cognizant of open source software licensing ( see https://github.com/nexb/ ;) ).
Now if you want to publish it as you did today and want eventually others to be able to reuse it things are rather simple. You need to pick a license for your own code. For code you reuse from others (I mean reuse as opposed to use as a tool such as a bookmarklet compiler) you need to give credits and comply with their license terms. There is not much risks in there and this is rather simple.

Actually as you seem worried by risks of being sued ( a very rare occurrence in the FLOSS space) if you cannot meet these simple licensing terms, you are eventually exposing yourself by publishing this code and more than by not publishing it. So, relax, things are not hard and not that bad ;)

from fastflicker.

Quoted from https://news.ycombinator.com/item?id=16955013 :

What many posters here miss is that there is a big group of tech people that have no interest in dealing with legal matters more than the bare minimum, and overall deem them risky. I am one of them. People like me are well-aware of the fact that if we are not experts then we're absolutely gonna lose because a dedicated lawyer can and will dig up material you couldn't prepare yourself to defend from.Thus, complying with something somewhat ambiguous like the GDPR is still an expense -- of time, money and risk -- that many small website owners won't be willing to spare.

from fastflicker.