Been thinking a lot about how to make my #software corporate-unfriendly. If Facebook steals blog/reblog I want them to have no choice but to federate by the very nature of the design. But I also want a license that forces your source code to be published -- no logins, no paywalls, no EULAs, no NDAs -- under the same or stricter license for as long as your derivative is distributed, anywhere, to anyone, even employees. Even if you only want to make an internal fork with tiny changes, too bad, publish it or write your own. I don't care if it's an abandoned Gitlab repo that sees one commit in its lifetime for the one change you want made; it just better be public.
Current FOSS licenses just don't really do that. I can't think of a legal reason why, though I'm by no means a lawyer. Anyone got any ideas?
There are no "legitimate concerns" about trans people.
Trans people in sport are not significantly out performing their cis counterparts.
Trans people have been using public toilets for years without incident.
Detransition is extremely rare & the most common reason for it is because of societal transphobia. Hip replacements have a greater rate of regret than trans supportive healthcare.
Puberty blockers carry no more significant risk of side effects than plenty of other medications given to children. We still give them those medications because we recognise their benefits & potential to save lives.
You don't have "legitimate concerns", you're looking for excuses to perpetuate your bias against trans people.
playing deltarune chapter 2 and holy fucking shit noelle is intensely homosexual
i hope someone finds a way to remotely brick teslas while they’re driving and uses it in the wild