3 ms·
Honestly, rather than building it from scratch on socket.io, use any existing chat infrastructure - be that Matrix, XMPP or IRC. My bias would be for Matrix (b
by Arathorn 5y ago
Honestly, rather than building it from scratch on socket.io, use any existing chat infrastructure - be that Matrix, XMPP or IRC.
My bias would be for Matrix (being project lead thereof); there is a whole new generation of client sdks (eg matrix-rust-sdk) on the horizon which are transformative - likewise massive serverside improvements like v3 sync which will provide instant login & sync (somewhat inspired by Discord). You also get e2ee, decentralisation and bridges to a bazillion other systems too.
- zaik 5y agoXMPP has the additional benefit of being the IETF Internet Standard for instant messaging.
- dinkleberg 5y agoI’ll have to take a deeper look at how matrix works and dig through some of those client and server implementations. My initial concern was that the architecture seemed at odds with what my service needs. While I whole heartedly approve with the decentralization and E2EE approach for a general chat solution people would use like element, mine is much more niche and I need tighter control. That being said, I haven’t dug into it enough to see how flexible it is. It would certainly save tons of effort if I could take advantage of the hard work that people no doubt smarter than me have put into this project.
- Arathorn 5y agowould be interested to know what tighter control you are after :) there is a huge range of matrix clients these days, so you can get an idea of how much flexibility there is to build the app you need.
- hammyhavoc 5y agoI love Matrix so much. It makes my heart sing.