I think this will be hard to achieve. There are a lot of reasons for this, including things such as derivatives that might run on other platforms (possibly without a screen).
My advice would be to choose between two options. Either, go closed source (but free to use) if you want to keep control, or go open source (using a traditional license) and give up that control knowing that people might fork your project a lot.
(Of course, unless your project gets really big, the number of forks - and their scope - will probably be limited in practice.)
I am a certified trainer that likes to share my knowledge with the world.
Also, I am an adopter of continuous learning and evolving idea.
https://dev.to/wolfiton/who-am-i-3lj7
I think this will be hard to achieve. There are a lot of reasons for this, including things such as derivatives that might run on other platforms (possibly without a screen).
My advice would be to choose between two options. Either, go closed source (but free to use) if you want to keep control, or go open source (using a traditional license) and give up that control knowing that people might fork your project a lot.
(Of course, unless your project gets really big, the number of forks - and their scope - will probably be limited in practice.)
Thanks @jasperhorn , I will keep your suggestion in my mind