Comment on This is another implementation of what's possible inside of termux for all you self hosters.
darkan15@lemmy.world 3 weeks ago
Just wondering, as this is the second post I see you do like this, why not use git and a forge (codeberg, gitlab, github), to publish these projects, with proper file separation, a nice README with descriptions and instructions and a proper OSS license?
hereforawhile@lemmy.ml 3 weeks ago
I thought about it but it’s not worth tieing accounts together to me and I don’t wanna make throwaway accounts just to share.
To small of scale I’m just messing around is the short answer.
Usage is commented at the start of the script. Just save it, chmod, run it and it spins it self right up.
What are the downsides of sharing code with no license?
darkan15@lemmy.world 3 weeks ago
The TL, DR version of sharing with of No License, is that technically speaking you are not explicitly permitting others to use your code in any way, just allowing them to look, a license is a formal way to give permissions to others to copy, modify, or use your code.
You don’t need an extra file for the license, you can embed it on a section at the top of your file, as you did with the description, just add a
# Licensesection at the very top, if you want the most permissive one you can just use MIT, just need to replace the year of publication of the code and a username or email that can identify you as the authorhereforawhile@lemmy.ml 3 weeks ago
Thankyou that’s really helpful 👍
ki9@lemmy.gf4.pw 3 weeks ago
It didn’t used to be this way. You used to apply for copyright like a patent. Rich people stole content from poor artists that didn’t have the lawyers to file copyright. This broken system has been reformed. Nowadays, if you create something, you automatically own the copyright. You now have to “opt out” of copyright with an explicit license to “release” the rights. Much better system.
possiblylinux127@lemmy.zip 3 weeks ago
I think you are legally liable for damages