Conversation

You're playing on the words here - yes, the GPL is applicable at distribution time, but having to distribute essential components of your software separately comes with several restrictions on how you can use it, the first one being that you can't link it statically.
1
Hahaha, thanks for the condescending explanation! You see, the primary consumers of *source code* are... developers! Maybe it wasn't the case originally, but in today's world, the "users" you are talking about use prebuilt software, they almost never build it from source.
2
But if you must insist on that specific definition of "users" that aren't developers - I reject it entirely. Why? Because an open source license should protect the rights of the developers first. You may disagree, but I value my own rights as a developer more than as a user
1
That's not the case at all. I'm not really interested in further engaging with someone being so thoroughly dishonest and manipulative. You're demonstrating what I said earlier when I said that the toxic Free Software cult is the biggest downside to the GPL.
1
It was an unfortunate name collision but it was a bigger problem for them than for us and we didn't have any conflict with them about it. GrapheneOS brand was previously used by one of the companies building on our project. They gave us the name and branding they'd been using.
1
1
grapheneos.com was registered in January 2014 by someone that's now a GrapheneOS user. grapheneos.ca and grapheneos.net were registered maliciously to trick our users and we were concerned they'd escalate and file for the trademark so we filed first.
We've spent tens of thousands of dollars on legal fees dealing with attacks on the project with little happening because of it. It takes literally years for a court case to move ahead. Don't see any point in hoping it can be used to deal with more trivial things like domains.
1
Show replies