Changing how we live by deep convergence of telephony, video, messaging, collaborative services, geospatial awareness, accessibility, smart agents, and facility automation.
When I was doing wickr we used php for the backend and long poll, which we later supllimented with websocket for eventing, though websockets were never stable. Simple messaging does not care about multi-second delay, but notification for telephony and live calling does. I actually brought in people with experience in trading systems in NYC to fix those problems. But it was still like building backends with stone axes and bearskin rugs.
Most of the backend needs for secure messaging and secure calling are not complex, especially once you avoid things like sip. Much of the magic is really client side instead. If I wanted to go back to doing secure collaboration again, I know where I can find an experienced team to do that with, and I would prefer to focus mostly on the front-end side.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When I was doing wickr we used php for the backend and long poll, which we later supllimented with websocket for eventing, though websockets were never stable. Simple messaging does not care about multi-second delay, but notification for telephony and live calling does. I actually brought in people with experience in trading systems in NYC to fix those problems. But it was still like building backends with stone axes and bearskin rugs.
Most of the backend needs for secure messaging and secure calling are not complex, especially once you avoid things like sip. Much of the magic is really client side instead. If I wanted to go back to doing secure collaboration again, I know where I can find an experienced team to do that with, and I would prefer to focus mostly on the front-end side.