Thanks! Can’t believe I somehow missed it, I’ve visited that page quite a lot and it’s right between the two sections I frequent most! ![]()
Have considered this, though since I want to both chat and do chat commands (mute, ban, etc) I’ve not yet taken the effort to separate them or test that I don’t need both to e.g. mute an user.
Haha, that’s actually already my plan! Would probably go serverless and nosql too, to cut down on cost / handle spikes. It’s a monolith atm, but it shouldn’t need much refactoring esp since I use Spring Integration and there’s good adapter support there for different event/pub-sub tech stacks.
But for now not sure if folks will want it since most of the actions are desktop-side (esp communicating with OBS).
Anyway, thanks a lot! Hopefully other folks also find this discussion helpful thinking through these things, too.