search

stpeter / manifesto

A public statement about ubiquitous encryption on the federated XMPP network.
98 stars 58 forks source link

Added myself to manifesto #45

Closed dbrgn closed 10 years ago

dbrgn commented 10 years ago

I run a private XMPP server (=no public registration, but connected to XMPP network).

I think "regular" server operators should also have a way to show their commitment to a more secure network. Ubiquitous S2S encryption won't work if not all servers support it. Therefore it is important that not only the public service providers adhere to these guidelines/goals, but also people that just run XMPP servers for themselves & friends.

If you want to differentiate between public service providers and "private or unimportant service providers", why not create two different sections for the signatures? :)

Thanks for creating this manifesto, it's an important step towards more secure communication online!

stpeter commented 10 years ago

I'll add your signature manually (not via pull request).

We need clearer terminology for servers. To me, "private" means "not connected to the network" (e.g., behind a company firewall), "public" means "connected to the network" (i.e., federated), "open" means "accepting registration from anyone", and "closed" means "registration is restricted". Your suggestions are welcome. :-)

dbrgn commented 10 years ago

Ah, alright. In that case I run a public closed server :)

stpeter commented 10 years ago

Yeah that sounds strange, doesn't it? :-) "Private, federated server" sounds more correct.

dbrgn commented 10 years ago

Yeah, doesn't sound bad.

stpeter commented 10 years ago

Another recent signer used that term, and it sounded right. But on the other hand we also talk about the "public network", and can you connect a private server to the public network? Maybe we're just confused... ;-)