(#7nq3eda) The _problem_ of course is that @dbohdan _was_ and **is** right about something he said to him about building Private Messaging into this platform, it would overtake the project, its complex and getting security/privacy right is hard™. The advice given was to find something that we could integrate with so we don't have to do all the _hard word_ -- Problem is I've not really found anything quite suitable...

(#7nq3eda) It's hard to describe in words, but it basically quite simple: > If you follow a project's README or software's Documentation and **cannot** get it up and running within a few mins (_with a little tiny perseverance, because we're all human and make small mistakes_), then the project or software is basically quite garbage at that point "operationally". It _might_ be a fantastic piece of software or project, but if its that hard to "operationalize" you may as well forget it. That's how I feel about a lot of software and project. A lot you come across just suck. cc @markwylde

@prologic (#7nq3eda) sometimes I think it would be nice to have a XMPP instance. then I remember it's all XML and I think "nah." I am constantly in awe that IRC remains the only realtime chat that isn't unnecessarily complex. name another that can run chatops bot with just nc and sh?

@xuu (#7nq3eda) I can’t! but in so saying I brought this up with @asi Who helped me come up with the final proof of concept implementation of the private messages you see here today. But I do wonder what if instead we actually used the IRC protocol and baked in a built-in IRC server between pods?

@prologic (#7nq3eda) that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM. but having a federation of IRC servers would be interesting for realtime twt propagation.