• 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • 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.











  • I feel like the microblog feature would be more useful if we could get a separate feed/filter that doesn’t include the tags of magazines that you’re subscribed to. For example, I’m subscribed to /m/fediverse because I want to see the threads that people post here. I don’t necessarily want to see every mastodon post tagged #fediverse, though.

    It also looks like we can’t subscribe to a tag by itself, without subscribing to a magazine that includes that tag. So yeah, some more separation there would be nice.










  • I liked this bit a lot:

    As Robert Caro wrote:

    “We’re taught Lord Acton’s axiom: all power corrupts, absolute power corrupts absolutely. I believed that when I started these books, but I don’t believe it’s always true any more. Power doesn’t always corrupt. Power can cleanse. What I believe is always true about power is that power always reveals. When you have enough power to do what you always wanted to do, then you see what the guy always wanted to do.”