That's not quite how it works, you can relicense stuff under GPL and your distribution and any changes you made are GPL'd but the original remains MIT.
It's just such a pointless distraction. Don't make it about you? It reminds me of men who hear that women get paid less and start complaining about their own salary.
"Hey, we have this problem." "To each their own but it doesn't affect me!"
Really done with this take. Show some solidarity for your peers. So you like working from the office -- good for you! Do that! But also stand up for your colleagues who don't want that. When your colleagues have fewer choices, when things like this are imposed on them, well, your preferences are not far behind from being managed themselves.
Not sure that "copyleft" is confusing or falling into disuse, I hear people talking about it without confusion pretty often. First time I've heard "reciprocal licensing".
I dunno, it's just a place to store the code, and SourceHut is itself free software. I could put it on Codeberg or something, I guess, but it doesn't really seem like a big deal. Never heard anyone criticize the FSF or GNU for their use of savannah.gnu.org.
tl;dr: access to the source code will help people develop cheats but it's not really required, your game's gonna have cheaters unless you do server side cheat mitigations.
Not sure how this comes across as self-serving or what the nature of this protest is, but if you explain it in more detail perhaps I can make a correction.
I had the opposite issue -- something like 90% of genuine payments on my account are rejected by the fraud detector on the first try and have to be retried daily for several days before going through. I exchanged over a hundred emails with support in which they read the card testing script to me, tried to upsell me on "better" fraud management tools, disregarded any details I provided to show that the activity was non-fraudulent, gave me no insights into how the fraud detector worked or why it might be giving false positives, and refused to escalate my ticket anywhere. I had to beg to be put through to an engineer who knew anything about it, and still I couldn't get past front line support. Long gone are the days where you can talk to a Stripe engineer on IRC. Really badly soured me on Stripe and I started working on plans to move away from the platform entirely.
I take pride in making my websites accessible for everyone regardless of the monetary incentive to do so, and to make inaccessible websites simply because you don't think there's money in it is very shameful.
Not saying that hamburger menus can or cannot be accessible; just saying that, as an engineer, you really have an obligation to make something that is accessible. This is a basic, non-negotiable requirement for all software.
It would range from unfortunate to a non-issue. The entire flight is not expected to be successful, the purpose is data gathering. The worst case scenario is that it fails on the pad and damages the launch infrastructure, which would be a huge setback to the project. If it fails anywhere else it's probably fine.