A feedback cancelling solution would probably increase latency however, so it would kill the 'low latency' claim if it was on by default. Definitely something needed to be switched on for problematic setups though, since the disadvantages would be outweighed greatly (not having feedback \ echo is a necessary feature).

It shouldn’t necessarily, you can find out how much of the speaker output ends up in the microphone input and compensate. I’m sure the models are more complicated to deal with echoes and distortion but the same approach should basically work: fit the filter offline, apply it online.

The major gripe here should be with the monkey who was using speakers in voice comms.

People with a speakers setup sound awful on all software. Some kind of headphones or earbuds cost less than 10 quid.

The feedback cancelling wasn't the problem. It's a feature that should scarcely even exist.

The only time it's ever really good is when there is some sort of interactive one to many setup. A hands on demo from a lecturer where for some reason they can't wear some wireless buds.

You can make speakers and mic sound good, but you need solid software support and also a really decent mic. I have a friend who does this with a Blue Yeti mic sometimes. If you put it in cardioid mode, have the speakers not too loud, and position the mic so the speakers are behind it, you can't hear feedback on Discord. But people running mic setups this fancy are definitely the minority.

Sure, but the vast majority of this legwork is being done by a nice mic having directional capability and massive gain control. This is far from a win for discord and audio comp software. This kind of setup can be made to work on mumble too.