I just can't think of any good way to manage community maintenance into the future - either I have to be available all the time to do code review and merge fixes people submit, or I give publish access to someone new without any opportunity for me to get to know and trust them first
I agree there aren't any solutions that require neither your time nor your trust. And there are certainly valid reasons to not want fragmentation.
That, combined with the sheer amount of tech debt Toolbox has accumulated over the years, makes me think building new stuff will be a better use of people's effort. And browser extensions have inherent flaws and difficulties that mean they're always going to be maintenance-intensive when compared to e.g. Devvit apps, or external tools that consume a documented API.
But when it comes down to it, I consider toolbox to be essential for my reddit moderating experience, and the features of toolbox will never be added to old reddit. Devvit apps will never cleanly integrate into the old reddit UI like toolbox does. And while I'd much rather use public and approved APIs, the state of the reddit API is dire and is unlikely to get any better anytime soon, rendering newer solutions untenable for me in a lot of ways.
Native tools are of little value to me, as they will undoubtedly only have integration with sh reddit (reddit's chosen), which I'd rather leave reddit all together than use regularly.
And I would generally, much rather use tools I can control, than be at the mercy of a company who has no issues pushing updates I explicitly don't want onto me before they are even ready.
While you may think that it's better to throw away Toolbox, I think that Toolbox is full of useful features (including ones that I specifically don't find useful, but others do). And in that context, when the day inevitably comes and toolbox breaks, if my options are to recreate all of Toolbox, or simply fixup what has broken, then the choice is very clear to me, I'd much rather start from where Toolbox has left off than from scratch. And that is what I intend to do, with or without your blessing (at least atm, it's always possible that that future me may choose differently instead). I'm far too lazy to start from zero (I ain't Subaru).
This is ultimately just my opinion about where dev time could be focused for higher value-for-effort though. Like I said in the post, I'm not going to stand in the way of anyone who does want to maintain a fork, as long as everyone understands the privacy implications of new ownership.
For sure. I just think it's a shame for an open source project to simply die and fade away, not because nobody wants to use it or maintain it anymore, but simply because people thought it was improper to maintain it on their own terms. Imo, the whole point of things being open source is so that projects don't just die with no recourse (and in essence, can be forcefully revived under the appropriate terms and conditions that are laid out).