3 ms·
I've been killed kicking around the idea of doing something similar, in go, with the domain I own ChatFor.Us JavaScript encryption, as others have mentioned is
by jrussbowman 11y ago
I've been killed kicking around the idea of doing something similar, in go, with the domain I own ChatFor.Us
JavaScript encryption, as others have mentioned is the thing I see I was planning that's missing from yours.
I'm planning on going a different direction with the domain, this functionality for private messaging for a platform set up for chat rooms as well.
Right now though I'm investigating a node.js and rethinkdb infrastructure, but that's also because I will need to persist data somehow.
Thanks for building this, at least validates that someone else has similar ideas.
- jrussbowman 11y agoNot sure how the word killed got in there. Typing on phone
- knadh 11y agoNice. From my crude and unscientific benchmarks, I've found that Go is able to handle a lot more concurrent WebSocket connections than Node.
- jrussbowman 11y agoI assumed it would. But I'm thinking socket.io would provide better client support and have been looking at meteor as a way to get something built fast. Going Roth a prototype first as I have a lot less time to do this stuff these days. I'm about equally proficient in both go and node which is to say I can stumble my way to a solution with both.