Mon, Jun 7
I'm not opposed to this, but this does seem like a significant expansion of the MirahezeBot project's scope. Additionally, as we'll now be hosting wikis using the "Miraheze" name, consultation with the Miraheze Limited Board of Directors should be done, and the full Bots project team should need to approve this
Sun, Jun 6
May 4 2021
Per conversation with @RhinosF1 on IRC, I'd recommend @MacFan4000 be nominated as, and confirmed subject to @RhinosF1's and the team's approval, the "designated survivor" with all powers to act for RhinosF1 where RhinosF1 has either:
- Formally designated himself on a leave of absence; or,
- Not been around for more than 72 hours without prior notice as to where he is
I think any changes to MirahezeBot plugins should be able to be approved by any Operations-level team member (i.e., you, MacFan4000, Reception123, or Voidwalker). Likewise, changes to MirahezeBot trusted and admin level of access should require the approval of a majority of the team, at least three of which of which must be Operations-level team members.
Apr 25 2021
Apr 20 2021
Not sure how to tick the box, but this seems fine.
Apr 17 2021
Mar 6 2021
I might tackle this page in a few weeks, but why on the static website? Wouldn't this make more sense on-wiki?
Mar 5 2021
Feb 26 2021
Feb 24 2021
Is this our first Phame post? And yes, it would make sense for the Community Relations Specialist to write these.
Feb 22 2021
Feb 15 2021
Though not an official member of the MirahezeBots development team, I was encouraged by @RhinosF1 to comment on this request. It saddens me greatly to see Zppix' access removed, but ultimately, MirahezeBots is a team-based project. It may have been founded by Zppix, but there's nothing in MirahezeBots' policies that give him carte blanche authority to unilaterally make major decisions affecting the entire project. I can say that I strongly encouraged him not to shutdown the Discord/IRC relay bots just because of a dispute over the Discord server moderation hierarchy. It was quite silly, really. It's the equivalent of taking one's sandbox of toys away when you disagreed with something either unrelated or barely related. When the other team members joined the MirahezeBots project, it was de facto agreed, at minimum, that the team would make major decisions collectively.
Feb 3 2021
👍 This will be good to do for the future, I think. +1 to all of those suggestions, and we can retain the existing subdomains as CNAME redirects or web forwarding pointers, as applicable, to the new addresses
Jan 9 2021
Sep 12 2020
Aug 16 2020
@RhinosF1 Wow, from my including the word "block" or "blocked" on a talk page/noticeboard page? Agree with you completely when you say, "This is just abhorrent detection of blocks. I assume a broken regex."
Aug 6 2020
Jul 20 2020
I'd be happy to take/claim this task. I assume I'd just initiate a pull request for security.md, propose the changes, and then propose it for merging, at which point anyone would just (a) make further changes (more likely) or (b) approve it without further amendment (less likely)?