Supporting Twofish is really bizarre. It's basically dead and would be slow compared to AES or ChaCha unless someone rolled their own SIMD implementation (why?). AES128 is weird too since 128-bit key ciphers are kind of deprecated unless your target is a fridge magnet.
AES256 or ChaCha20 would be sane as they are both roughly equivalent security-wise (in practice, people will debate theory) and both still recommended for use in new stuff, but most cryptographers would recommend that you pick one and only one of these two for a new system unless something forces you to support both.
So yeah, weirdness abounds here.
Why is AES128 preferred over AES256 by browsers then?
https://www.ssllabs.com/ssltest/viewClient.html?name=Chrome&... https://www.ssllabs.com/ssltest/viewClient.html?name=Firefox...
> Traffic over OmniEdge is end-to-end encrypted by Twofish/AES128/ChaCha20 cipers' P2P MESH network.
I'm grasping at straws to find a single thing which looks legitimate about it. You'd have to be completely nuts to even begin looking into this as a solution for anything.
If you're interested in what the technology behind this is, it's just a thin veneer of https://github.com/ntop/n2n.