![](https://media.kbin.social/media/e9/15/e91548790805c6c416d8ecab84927481ee82e853b0f5521193abfaf1e337963f.jpg)
![](https://lemmy.world/pictrs/image/4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
Huh, I’m going to have to try that at some point. It’s even got nim support.
Huh, I’m going to have to try that at some point. It’s even got nim support.
Interesting. I was thinking more of gray area stuff than outright lying, like playing up the importance of facts that support one’s position and downplaying those that don’t.
I read somewhere a while back that it’s supposedly an evolutionary thing. In a social competition for resource allocation, confidently arguing your position regardless of its correctness is more beneficial than admitting you may be wrong.
It’s probably exacerbated by the internet, where the relative anonymity and psychological disconnection further reduces any benefits to admitting to an error.
From the PR comments:
Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, © engaging with the Contributor on improving their patch quality.
I asked around and asked in the C4 specification matrix room.
And the reason is actually simple. If you merge bad code, have a record of proof in git (pull requests aren’t forever it’s only a github/gitlab thing).So the idea is if you merge bad code you have proof in the git record that there is a bad actor. You can always revert the commit again or fix it. And the record can act as a proof in case the community want to get rid of bad actors.
Hmm, that seems like not such a good look from Ernest. According to google translate:
I know, honestly it was on purpose. I noticed that forks sync changes immediately with /kbin. I wanted to check how they deal with this much-announced community-based qualitative code review. Answer: they can’t cope. Quite an obvious bug was accepted in PR and domerged into the main branch :P It now works properly on the rifle ;)
Hopefully everyone can play nice and work together productively.
It looks like they’re still working out what they want their process to be:
https://github.com/MbinOrg/mbin/pull/34
Seems like your concern is addressed there:
Pull Requests require at least one (1) other maintainer approval before the PR gets merged (built-in peer review process).
The mbin fork happened when kbin development was looking a lot less active. In any case, it’s not necessarily bad to have a diversity of approaches. Due to their differing organizational structures, mbin will likely tend to have more features and more rapid development, but also potentially more bugs, while kbin remains more stable.
Domain blocking isn’t instance blocking. It’s for if you don’t want to see posts that link to, for example, imgur.com. It’s also broken and will just hide random posts from you.
You’re posting to /c/foss, not /c/freeofchargeandthecodeisavailableforinspection.
You’re mixing up cranks and bigots. Bigots tend to get banned because they’re harmful. Cranks tend to exclude themselves on principle.
The term “crank” is usually used as a pejorative, but cranks can sometimes be beneficial. Richard Stallman is the prototypical example of a Free Software crank. Definitely annoying, but also definitely a net benefit to all of us.
That’d be covered by #4:
The license may require derived works to carry a different name or version number from the original software.
There is a clause about redistribution (1), and it expressly specifies that it applies to “aggregate software distribution containing programs from several different sources”, not single, standalone works.
That is a weird way of wording it. In practice I doubt there are any OSI-approved licenses that prohibit standalone commercial distribution. If there were, you could trivially comply by just including a “hello world” program to make it an aggregate distribution.
Dr. Evil moment
Anti-white
Anti-cis
Oh no! Anyway…
I mean, them dropping a chunk of money for “political” stuff over software development is kind of curious, though maybe there is a good reason for it. In any case, this meme is sus as hell, and posted from a throwaway account. What are you up to, OP?
I really doubt it’s doing much for him. In general it’s better to mock fascists than it is to ignore them.
You’re not wrong, but I think there’s some merit to repurposing bigoted memes to clown on bigots. r/antifastonetoss, for example.
The original was posted here yesterday
I love these memes that turn into threads full of vim tips. You really can do anything within vim. You can even exit vim!:
!killall vim