• 1 Post
  • 21 Comments
Joined 3 days ago
cake
Cake day: November 13th, 2026

help-circle
  • Meanwhile, I was the giddiest I’ve been in a while, because I thought we’d never fix that bug. It just sounded like one of those ugly bugs, where we might have to patch the auth library again and where it’s almost impossible to know what else is broken afterwards. But with a single-line-change, it’s immediately obvious that it won’t break anything else. I could just immediately merge that to be shipped with the next release. Which is just excellent.

    Did you tell her that? :D













  • There are 3 possibilities:

    1. By accident. That would mean Rimu didn’t know about the existence of Pylova’s blocklist feature. Lets not go down there.
    2. Forced / without choice. Because he wasn’t capable of doing it, or somebody held a gun to his head.
    3. Deliberate. He made a conscious choice to do so. Whether because he felt another approach was preferable, easier, w/e.

    You seem to be conflating ‘deliberate’ with ‘malicious’. Those are 2 separate things. Read my original statement again without projecting any of your assumptions onto it.


  • {
      "@context": "...",
      "id": "https://example.org/blocklist/general",
      "type": "OrderedCollection",
      "name": "General Blocklist",
      "summary": "Description of the list",
      "attributedTo": "https://example.org/u/admin",
      "published": "...",
      "updated": "...",
      "totalItems": 2,
      "first": "https://example.org/blocklist/general/entries?page=1",
      "inbox": "https://example.org/inbox",
      "visibility": "public",
      "subscriberCount": 10
    }
    

    The feature is nothing more than shared basic JSON data. If your thrust is that Rimu is too incompetent to handle that, I don’t really think so, but I can accept that too.