I'm moving back to @firstname.lastname@example.org. I don't know what happened in the current debate, but regardless, I do not wish to have an instance dictate me what parts of the Fediverse I am allowed to see. We do not accept ISPs filtering the web, and I think this is no different. If *users* want to block someone or an entire instance, that is fine. But that should be a *user's* choice, not the choice of the service provider. I think there is value in seeing what people you disagree with write.
#m68k backend for LLVM is now upstream (in the LLVM github repo)
@tuxedocomputers Wie ist das bei euch mit Versand in die Schweiz? Kriegt ihr das hin, ohne dass man deutsche MwSt zahlen muss und but Schweizer Import?
s/limera1n/checkra1n/, of course.
But that is how a probably <50 line patch to Emacs nearly derailed a $117m tech acquisition.
This eventually reaches the CEO of the startup bank, my boss' boss' boss, who has to repeatedly assuage them that it is not material or risky in any way.
Whatever persuasion he deployed is successful, because the deal closes, making me an internet thousandaire.
Do these FSF dorks have some claim to the technology they're about to drop $100m+ on? Anything could be possible. They start escalating to figure out what is going on.
And out of whatever drawer it was shoved into years before, out pops this hippie neckbeard free software thing. The high-caliber lawyers have NO FUCKING IDEA what this is about, but "copyright assignment" starts setting off major red lights.
2-3 years after that, the tech bank startup has launched, grown, and is being bought by a major international bank, one of the largest in the world.
They need to do due diligence. Part of this is reviewing employment contracts and related things.
I mailed the paper and sent in my patch, which I think was something to do with the stored list of preset SQL connections or something adjacent to that, then went on with my life.
Because so many tech employment contracts assert claims over work done by their employees, part of this process involves obtaining a release so the FSF knows they won't get sued over your code.
I worked at what was then a small tech company, we were building a bank. There were probably 20 or less employees in the whole place at this time, so getting sign-off for this was no problem.
Here is a small, true story from my life:
Sometime in the 2011-2012 timeframe, I went through the FSF copyright assignment rigamarole so I could contribute a patch to Emacs. This requires you to send a physical piece of paper to the FSF. Nobody can contribute patches to any GNU project without doing this.