{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibyfzsx4l6z56iyt6fku7wavmkqxlvachtlkeul2ivs2fhml36q3e",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mn7oxtve3ei2"
  },
  "path": "/viewtopic.php?t=33488&p=275043#p275043",
  "publishedAt": "2026-06-01T07:16:29.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> This place could really use a couple of active moderators. There used to be one guy that would show up occasionally, is he still around? You've been filling that role for a long time, but basic moderation shouldn't be taking up your time.\n\nIt's not really taking up much of my time, but it's a good point.\nThe thing with assigning moderators is: I've seen _way_ too often that people who become community moderators actually don't know how to handle the responsibility or aren't actually suited for that role (and actually cause more harm than good in the long run), so I'm very apprehensive about assigning moderators and careful whom I want to give that kind of influence. It takes a shepherd to herd the sheep and not many people are actually shepherds, able to handle both the stray bucking individual sheep and being able to guide larger herd movements in a gentle way. Especially these days when everyone has their opinion on their sleeves ready to shove into your face, it takes a lot of balancing between restraint and action to do it well.\n\nIf you're volunteering, though, I'll be happy to make you a global mod here.\n\n\n> To be honest, I kind of suspected you were overwhelmed by security bugs...\n\nIt's just been insanity. Even Dan Veditz of Mozilla called the inrush of sec bugs in the past months a \"hellscape\" in our communications. Not because sec was bad, but because so much was dumped on them (and by proxy, us), no doubt to cash in on those sweet bounties (often in the couple grand range per incident, if I understood correctly, at Mozilla) by letting an LLM comb through the code and find deviations from what it thinks are the \"right\" coding patterns to use.\n\n\n> I noticed you pulling in a lot of stuff seemingly in a rush related to those, and also merging a lot of stuff in a rush from that eUXP fork...\n\nThe sec bug code changes weren't rushed. That's just me working full steam for full days on end. I can't do that too often or for too much time without burnout, of course, but it's not overly hurried. The eUXP stuff was indeed rushed and I hated having to do that but I felt severely pressured in that case. Some things weren't exactly ready there and we'll just have to work on ironing out some creases over time.\n\n\n> Out of the two things you won't be focusing on anymore, the two that are potentially the most worrying are web compatibility and new code\n\nWeb Compatibility is more stepping back from the first line of support/analysis/mitigation. I need to just step back and have a more filtered view on what is an actual compat problem in the platform and not just one-offs or corner cases. I'd love to be able to fix everything but that just isn't realistic.\nThe new code works is indeed the major change; and I don't like to do it but I am just no longer capable of doing high level project administration and low-level code dives in tandem. It takes a lot of effort to switch between those two very different mindsets multiple times a day.\n\n\n> Overall, it does seem like you and Basilisk-Dev are both setting boundaries when it comes to this project and circumscribing responsibilities, pulling back, etc, at basically the same time.\n\nThe timing isn't intentional. I don't know what Basilisk-dev's reasoning is but he did hint at things _outside_ of coding and the project/his browser pulling him away (including personal matters). For me it's very much a re-evaluation _within_ the bounds of the project and what I can or should be doing within my resource and mental energy bounds.\n\n* * *",
  "title": "Platform Development • Re: Stepping back from new code tasks...",
  "updatedAt": "2026-06-01T07:16:29.000Z"
}