Update manifesto.txt

[SkyperTHC]

No description provided.

[stpeter]

Thanks for your interest in improving XMPP security! This manifesto is intended to be signed by developers of XMPP servers, clients, and libraries, and by service providers who deploy XMPP services (i.e.., people who can actually commit to making changes in their software and services). As far as I can determine, you do not develop XMPP software and there is no XMPP service at thc.org. Please correct me if I'm wrong.

[SkyperTHC]

There is at jabber.thc.org but it is private. I do not mind being on the
list. From everyone at THC thanks a lot
for the effort in making XMPP secure.

regards,

skyper

On Fri, Nov 15, 2013 at 6:40 PM, Peter Saint-Andre <notifications@github.com

wrote:

Thanks for your interest in improving XMPP security! This manifesto is
intended to be signed by developers of XMPP servers, clients, and
libraries, and by service providers who deploy XMPP services (i.e.., people
who can actually commit to making changes in their software and services).
As far as I can determine, you do not develop XMPP software and there is no
XMPP service at thc.org. Please correct me if I'm wrong.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/29#issuecomment-28592713
.

[stpeter]

When you say "private", do you mean (a) it is not connected to the public XMPP network via server-to-server connections or (b) open registration is disallowed? Yes, these terms are confusing. :-)

[SkyperTHC]

both. not connected to the XMPP network and open registration is
disallowed. Might change at some point in the future but that's a long way
off.

On Fri, Nov 15, 2013 at 10:06 PM, Peter Saint-Andre <
notifications@github.com> wrote:

When you say "private", do you mean (a) it is not connected to the public
XMPP network via server-to-server connections or (b) open registration is
disallowed? Yes, these terms are confusing. :-)

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/29#issuecomment-28607436
.