There's a bunch of good tutorials out there on [dumb] fuzzing (presumably where you'll start). One starting point I'd recommend is taking a binary that accepts input from stdin and making some proof-of-concepts with AFL (https://lcamtuf.coredump.cx/afl/).
There's a lot of other fuzzers, techniques, and depth to the field, but I'd recommend inch worming through (speed up as you gain more comfort). The Fuzzing Book is good to help you understand the logic behind techniques and strategies (https://www.fuzzingbook.org/)
As for some management, there's a few decent "monitoring" systems out there; personally I just SSH in and check the fuzzer manually (I leave it running in a tmux pane), but if that's not your cup of tea I've heard good things about OneFuzz (https://github.com/microsoft/onefuzz) and LuckyCat (https://github.com/fkie-cad/LuckyCAT).
Anecdotal: I've seen a lot of people migrate to substack (not how much better it is, but I dont dislike visiting it like I dislike visiting a medium blog)
I originally built my home server for academic use (computational physics), but after changing in security I've come to use it as a fuzzing playground.
Oftentimes I kick off a fuzzer on some OSS, e.g., GCC, v8, standard *nix binaries, and let it run for days/weeks/months. If I find anything I submit it to the appropriate people or make a PR, if Im motivated enough that week
Originally we were on IRC. As the team grew, more CTFs were being played - often concurrently - so having dedicated (private) channels for a given CTF and "sub" channels for its challenges gave us a lot more flexibility.
That being said, we've considered migrating to Discord, Zulip, or Matrix - just haven't gotten around to it yet.
I help run the OpenToAll CTF team - while the primary focus for most are CTFs, the community (>500) has really expanded, e.g., (in the slack workspace) we have active channels for N-day repros, bug bounties with internal competitions, financial trading shop talk, and hardware hacking. You wont find much OTR or blackhat stuff ( due to slack ToS), but Ive found the community loves learning and discussing all things sec.
It doesnt hit your mark completely, but hopefully its somewhat helpful