On 2016-12-29 23:32, Tobias Markmann wrote:
> After
> registration, they need to easily/secure/privacy-enforcing fill up their
> roster with contacts based on known contact information like phone number
> or e-mail address.
I suggest to popularise the idea of identical email and XMPP
address. Whil
On 12/29/16 4:12 PM, Kim Alvefur wrote:
On Thu, Dec 29, 2016 at 11:32:18PM +0100, Tobias Markmann wrote:
Conclusions from the talk and possible actions to address them are:
* The XMPP manifesto from 2014 was a nice start and had very visible and
noticeable effects, >95% of public XMPP services
On Thu, Dec 29, 2016 at 11:32:18PM +0100, Tobias Markmann wrote:
> Conclusions from the talk and possible actions to address them are:
>
> * The XMPP manifesto from 2014 was a nice start and had very visible and
> noticeable effects, >95% of public XMPP services require TLS for C2S
> connections.
On Thu, Dec 29, 2016 at 11:32 PM, Tobias Markmann
wrote:
> * A lot clients are missing modern features and support for modern XEPs.
> We need to provide more incentive for client developers implementing these
> newer XEPs. Maybe we should sort the client list on xmpp.org based on
> support of the
Hi all,
So @hanno ( https://twitter.com/hanno/ ) did a presentation followed by a
short discussion on Signal and how XMPP and other federated systems fail to
provide a similar secure and usable system over federated architecture. The
slides can be found at https://www.int21.de/slides/33c3-decentra
