I feel like there are some people who don’t like their creations getting copied, so maybe you can make forking an option.
1 Like
They could always just copy the code, also anything you write on replit is pretty much open-source, so as long as they provide credits they can use it.
3 Likes
Hmm, this is a good idea!
1 Like
Welcome to the community, @YeetusMcMuffin! The problem, like @7heMech said, is that they can still see the code anyway, and to get rid of that, just means a private repl which already exists.
1 Like
Disabling forking would be pointless, because if people can see your files, they can copy them. Allowing forking discourages people from making copies without giving credit. Also, disabling forking would be like building a building, but only allowing people who purchase licenses to photograph it. People would photograph it anyways, regardless of whether they are allowed to.
4 Likes
lol to run a console repl, replit just ghost temp forks it and deletes it afterwards while storing important things like db URLs in local storage for later use XD so no there is no way in console repls
4 Likes
Can’t ephemeral forks be created for any public repl?
3 Likes
I mean that’s what it … does it literally forks it temporarily and then deletes it after your done running
6 Likes
You can add a license to your code to prevent people from stealing it if you want, here’s a github article on some license stuff The Legal Side of Open Source | Open Source Guides
2 Likes