A protected switch would be to utilise a XMPP based protocol which has hadn’t been neutered of protection or privacy and typically does not carry extended metadata not necessary to really deliver the solution.
Something such as XMPP perhaps? Sustained by numerous customers on numerous platforms if you have no trust when it comes to server’s SSL cert then(aside from keeping your very very own XMPP host) you can easily put conversations customer part with levels of GPG and OTR вЂ“ until you’ve a actually bad client. Once the servers вЂ“ unless set to especially display to theвЂ“ that is contrary cleanly communicate over the interwebs then a person being logged in to a host does not avoid interaction with other users on other servers(unless that host isolates it self), can sustain your very very very own section of effortlessly a distributed meshnet.
It’s(XMPP) reasonably unstoppable, the protocol is completely resilient with regards to information distribution, and shows attack resilience. Used securely it could offer defenses from it’s articles for degree that is feasibly www.hookupdates.net/trueview-review/ impractical to counter.
Being XML based it may carry such a thing in a position to be represented within an XML stanza вЂ“ which will be essentially any such thing.
It is not impossible вЂ“ esp when having fun with the open supply servers вЂ“ to create “bridges” while having cross protocol interactions. State a relationship layer that sets the users’ account(on need) for an IRC host, giving the consumer usage of a protocol that is completely independant.
As things like whatsapp are derived from XMPP I would recommend building a connection amongst the two that provides improved protection as an interior layer for supporting consumers and ‘legacy'(read:neutered) behavior for just about any consumers without sane features.