As a response to the russian unprovoked war in ukraine I am announcing that i will take steps to reduce the rights to use, study, improve and distribute for all software and hardware that i've released and will release in order to actively prevent it being used in russia's wars to hurt innocent civilians and democratic nations.

I am prepared to violate GPLv3 and take legal action if it means that i won't have blood on my hands.

The current projected solution is a restricted access to content manager and putting in place requirements for identity verification.

Despite this I remain dedicated to the values of Free Software Movement and i will do everything in my power to make sure that everyone outside of russia has access to these projects.

Just change the license of your projects to proprietary, if you don't believe in the foundations of Free Software, it's better not to use them at all.

It's your projects and you have the rights to do whatever you want.

If your really don't want "blood on your hands", just distribute the software with the people you trust and that's sure you don't everyone in this world.

@colinsmatt11 i want to maintain the principles of Free Software, but i don't want it to be used by russians

That's not maintain the principles of Free Software at all.

Freedom 0: freedom to USE the software FOR ANY REASON, that includes helping people AND hurting people.

@colinsmatt11 i don't mind them using the precompiled binaries i want to restrict the right to study and improve mainly

So removing freedom 1 and freedom 3.
It would be easier for you to remove all them than cherry pick.

@colinsmatt11 i want to maintain these rights for everyone else but russians or do you have a better solution?

Change your licenses to proprietary and include that people from Russia, etc can't use it. In your EULA.

@colinsmatt11 They will still be able to download it and use it without problem that way.. legal route is not sufficient

Yeah, and how are you going to stop them from downloading the source and study then redistribute it?

They can just use VPNs you know.

@colinsmatt11 One way is to maintain a git forge restricted to those who are able to verify themselves as non-russian citizens and vetted

And what if someone verified redistribute it the Russians?

@colinsmatt11 thus the vetting to make sure that this won't happen..

I do plan on keeping some of my project under GPLv3-complying that can't be used to do harm, but i can't in clear contiousness release the aircraft that i am working on

> can't be used to do harm
Anything can do harm if used in that manner.
Follow

@colinsmatt11 how can you do harm with a hello world program?

Depends upon how it's written, if it's not using const strings it can possibly create a memory leak.

@colinsmatt11 i program in rust and GNU Guix in majority which doesn't have this problem

Every language has it because memory works like that, rust uses OBRM by default which makes memory management optional but you need to disable it for certain things that's where unsafe code block comes in.

You can't everything with constant strings.

@colinsmatt11 i do QA for all of my software including checks for memory safety

That's a good practice, thus your programs are safe but that's not true for everyone else.

@colinsmatt11 how can a leaky hello world be used to cause harm

Best it could fill up your memory and crashed the system.

Worse case : https://youtu.be/EJtUW2AklVs
That's understandable.

I point was it can do harm, and not all harms are equal.

@colinsmatt11 i am only concerned about major harm in russian military

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.