Thanks :)

edit: I know perfectly what is DDG and I really love this search engine, but still.. don't get me wrong, I'm just asking for answers there, not being rude

I think that perhaps, like me, they were hoping that you would be interested in sharing a couple of use cases for XMPP with us ...?

Where's the technology for linking an XMPP conference to an IRC channel? I lurk in some IRC channels that would love to migrate to a more modern protocol, and that seems a good way to bridge the gap.

If you are interested, just join us on IRC and we talk about it :)

And to answer your question, taka a look at

http://xmpppy.sourceforge.net/irc/

Will you be following the same principals in regard to privacy as the DDG search engine follows? Personally, I would love to see the following:

1.) No connection logging. Ie, don't log when people log in and from which IPs

2.) No chat logs

3.) High profile information and instructions on how people can use OTR (Off the Record) for end to end chat encryption

4.) A Tor hidden service gateway to the XMPP server

Regarding 1 and 2, the least that is required IMO is a privacy policy detailing which information is stored and for how long.

So the messages are kept (in case you want to refresh your memory, but don't have locally-stored history), but are unaccessible by third parties.

That wouldn't fulfil 90% of the purpose of keeping logs, for me at least. Not everyone has the same requirements as you - I for one very rarely bother with OTR, but I have to search my chat logs for something on an almost daily basis. I use XMPP on my work PC, on my laptop and desktop at home, and on my phone. Splitting the logs across all those devices would make them literally useless.

Besides, anyone who is tech savvy enough to mess with public key encryption is going to be using OTR anyway, making server side logs useless.

But having the history is still useful ("remember that article I've sent you yesterday").

Some examples of comments in a private chat that might at first appear like they don't need encrypting, but might come back and bite you in the arse if they ever get published:

"God work is boring today. Need to update my CV/Resume"

"Bob was a bit of an idiot last night wasn't he"

"Thinking of skiving off work tomorrow."

"The wife has been nagging at me all afternoon. Fancy a pint later?"

http://duck.co/topic/duckduckgo-s-new-public-xmpp-jabber-ser...

See down under the comments, i explained there what is so far logged, but we will tune this now over the next days.

EDIT

See this post by yegg, the duck duck go founder

http://www.reddit.com/r/technology/comments/epd59/google_poi...

Note the #. Now, remove it and everything after it and reload the page.

Why am I being downvoted? Didn't we all just throw shit at gawker for doing the same thing?

EDIT: This fundamentally breaks the web. The # and everything after it are _not_ sent to the server. It relies on javascript and extra-protocol information to get the document, which breaks the idea of a resource having its own name. The # was suppose to denote a section of a resource, not a resource in-and-of itself. I'm sure everyone here knows this, but I had to get it off my chest.

Even "DuckDuckGo Jabber Service" is better, XMPP just sounds so unfriendly.