CY-X FORUM

i will achieve the 15th standard GET as prophesied by xkcd

One thing that I have thought of is "abandon XMPP, Mumble, and IRC, and create a God protocol that takes the best elements from all three of those protocols and implement what they are all collectively missing"
I could perhaps easily establish bridges to other protocols and create compatibility layers that would allow clients designed for the other protocols to connect to the God protocol simply through network layer shims, meaning no transition costs for users. es, but it will be designed at core to be a cleanly unified, yet modular thing

The God protocol would have all of the features of IRC/XMPP/Mumble and yet include features that don't exist in either one. Maybe I could even directly market it as a competitor to Matrix, Discord, and old pre-Microsoft encrypted Skype if I were to also target home casual networking with friends and family through video calling and screensharing.
I imagine that if I were to advertise that to the more "normal" parts of the Internet they would accept it. Most Discord alternatives strive to be just like Discord along with Discord's flaws and heavily centralized nature. Matrix is suspicious and bloated (so is Discord) and still doesn't have core features years later and is also indirectly centralized. I think Skype pre-6 would be a great reference. A decentralized and encrypted Skype-like protocol and official client would be awesome.
People who are inherently interested in alternatives but think the current players are too extreme or foreign will come. Because I am a user of my own software and projects. I know UX.

Maybe I'd approach it like XMPP where there's a centralized federated server. Skype worked that way, but it also worked kind of like Simplex if you told it to, IIRC. The most privacy schizo Skype would have settings that made Skype act only as a relay server/login gate.
So, lets say my idea is to have a decentralized ecosystem like XMPP, but with the relay P2P nature of Skype. Would that just be redundant, compared to the pure XMPP approach, since it still requires creating an account?
What about users who don't want to make an account of any kind at all? That would deter those kinds of folk who want to remain purely anonymous. In that case, maybe the protocol could allow for single-node deployments, where users can use the protocol to join a single centralized chatroom hosted by the server owner, just like IRC and Mumble.

I have already come up with a proper for this new protocol, but I will not reveal it until I have started the programming process. I am still working on my Trinity Protocol chat client that unifies IRC/XMPP/Mumble together in an effort to obsolete all other clients, but my next step beyond this is to completely negate the need to use those protocols by creating the God protocol where all of these features are implemented by default and in a clean manner.

let me know your thoughts, do know i'm going to make it anyway regardless of whether or not people say they fucking hate it unless they're able to actually give me a reason as to why and how i can improve upon this concept
i already have a partial plan for propagating it throughout the broader internet including advertising it to normgroid spaces and shilling the fuck out of it at organizations and small independent groups, most likely foss projects especially because "hey this thing does everything you want but better & regular irc clients can still use it normally by default"

Finish trichat first.

I saw this on 4chan /g
Is this reposted from 4chan
Or did 4chan repost this?

Anyway cool website I just found it
Also sorry if of topic, feel free to delete if you want

>>18895
>Is this reposted from 4chan
No. Trichat and the God Protocol are projects that are currently being developed here on Cyberix.

Can you come to mumble pub-private

Anything that isn't ncat -l --chat is bloat.

>>4167
just found this. i've had the same exact thought over the years.
it seems like the biggest issue that xmpp has is implementing. each client supports a different set of XEPs so that they rarely have even a similar experience. to my knowledge, there isn't even a single released xmpp client on desktop that supports voice calls. dino and kaidan, i recently discovered, do now support it but they're both in alpha.
MUC kind of sucks for the persistent environment that people expect out of it nowadays. MIX tried to fix that but failed due to a lack of implementation interest. it was too hard to shift away when so few servers and clients support it.
if there is to be a 15th standard, it should be laser focused. learn from xmpp's mistakes, cut out cruft, and harmonize the features. xmpp fought hard to figure out how to handle chat history (MAM), rooms (MIX), and presence (too many XEPs). it makes no sense to let that experience go to waste. i suspect extensibility shouldn't be the goal. focusing on anything but chat will lead to unnecessary compromises.