5 ms·
Copyright Bouke van der Bijl I do not give anyone permissions to use this tool for any purpose. Don't use it. I’m not interested in changing this license. Ple
by wejick 5y ago
Copyright Bouke van der Bijl
I do not give anyone permissions to use this tool for any purpose. Don't use it.
I’m not interested in changing this license. Please don’t ask.
- Groxx 5y agoIf it keeps this out of production in even a handful of companies, that's probably a good thing in aggregate. It's a neat blog post, shows interesting internals, and no - you should not do it.
- BiteCode_dev 5y agoSomebody with codepilot to check it out?
- DangitBobby 5y agohttps://github.com/bouk/monkey/blob/master/LICENSE.md https://github.com/bouk/monkey/blob/master/LICENSE.md Then why publish the blog post and put it into a package??
- deleted 5y ago[deleted]
- WesolyKubeczek 5y agoLook, don’t touch.
- whateveracct 5y agoclearly satire
- DangitBobby 5y agoWhich part and in what way? Clearly the blog post is not satire, since the method works, and the license cannot be satire as it seems like it would be legally sufficient to prevent people from using it, which is exactly the stated purpose of the license. It's also implied that the author has received requests to change the license so others can use the package, which have been denied. The author even went so far as to remind people in this comment thread that they don't want it to be used! The license is serious on its face and in practice. Where is the joke?
- bouk 5y agoYour reaction is the joke
- zodiakzz 5y agoSure. It is a "joke" until you're tempted to sue a big enough fish that falls for it and get some people fired. Pathetic.
- DangitBobby 5y agoHilarious.
- mxmilkiib 5y agoYou're a joke.
- deleted 5y ago[deleted]
- _t4sy 5y agoYou have the right to use this project via git submodules. The GitHub terms of service requires code owners to allow forking and linking to their public repositories, regardless of license.
- DangitBobby 5y agoIt does not appear to grant (or attempt to grant) use of the software. So sharing and forking are fine, but not necessarily anything else. > 5. License Grant to Other Users > Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). > If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you adopt a license. If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users
- _t4sy 5y ago> So sharing and forking are fine, but not necessarily anything else. Did I imply otherwise? Git submodules are just links. Please explain how linking to a submodule is not allowed.
- DangitBobby 5y agoWell, I thought the purpose of linking in git submodules was to compile the source code and then use it. The "using it" is not granted by the GitHub license. Did I misunderstand your original point? If not, the verbiage "use this project via git submodules" which uses the word "use" was the source of my confusion. Was someone disputing the right of OP to share a link to the blog post or the repository?