Yes.
Well.
I must admit trying to make something with a feature superset to discord in a week, while having a level of implementation knowledge that led to me struggling to create an echo server in 4 days, while most importantly not grasping the core concept of the jam, was perhaps a result of my hubris getting the better of me. I concede knowing it was a fool's errand anyway. Making an everything app, frontend, backend, protocols and all from scratch is lunacy given the circumstances. My second choice, IRC, although easy to extend, also probably shouldn't be used for it. Due to being a lightweight text messaging solution and little else.
Although...
If one did want to create a forum like experience using a modern ircv3 protocol, the capabilities already exist in the BATCH extension. Using basic tagging to separate threads and forums from each other, as well as potentially attachment links, and all you need is some client-side niceties to have the beginnings of a forum. It should be stated XMPP provides a much more solid foundation for forums/wikis/oekaki-boards/etc due to it's existing extensions already providing feature parity with current forum software (with a little finagling).
What did we learn?
Programming and talking at the same time is surprisingly hard! Not everyone can be tsoding.
Having an idea for how one part of your code will be done (using a bit set to describe client ids for status) does not mean that every other part of your code will be that easy.
That Casey guy codes pretty good (realization after watching the first 7 or so handmade hero's in a row).
I will be making a library free x11 window w/ backbuffer later as a means of penance.