3 ms·
If you publish something, you have responsibility over it.
by gregoriol 5y ago
If you publish something, you have responsibility over it.
- seba_dos1 5y agoNo, I don't. You may want to read the licenses of the code you're using, by the way.
- dvhh 5y agoImagine the liability of publishing any code if you are "responsible" for it. Meaning that you would be responsible for its improper use, or even use for illegal purpose.
- salawat 5y agoYou are though. Forget the legalese for a second. You wrote the code and put it out there. If you didn't, none of the uses of it would ever have come to fruition. A court of law may let you duck out for the time being, but when you trace the chain of effective physical causality backwards, at the end of the day, you write it, you're responsible for making possible it's applications. There is value to the code unwritten. That value is a clean conscience and true abscence of guilt or remorse for having enabled someone to do something monstrous. I laugh at people who think a legal disclaimer absolves one of moral culpability. If only it were that easy.
- seba_dos1 5y agoI wonder how do the makers of kitchen knives sleep at night.
- johnisgood 5y agoWhat kind of responsibility? In what sense? Could you give me an example? By the way, this is a part of my license (a pretty common one): THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.