JK's current peer-to-peer architecture means that an individual musician's internet link is the limiting factor on how many you can effectively use JK with at once - in a group that means the one with the highest latency/least bandwidth connection. I've been using Jamulus for some months - it is a client-server architecture so everyone connects to a central server, and you only ever have one audio channel to/from the server no matter how many people are making music together. It's less feature rich than JK but very easy to set up and use - and arguably scales better for larger groups if the server you're using is up to the job. You can use one of the many public servers, or set up your own private one very easily (I use an Amazon Web Services free tier for this).
I used JK at the start of lockdown but found it too buggy and gave up - I'm now trying again, as the client seems much more stable now.
I used JK at the start of lockdown but found it too buggy and gave up - I'm now trying again, as the client seems much more stable now.