You do not have permission to edit this page, for the following reasons:
Please read before you start to fill in the form!
Please enter a basic description for the planned Self-Organized Session. For more information about Self-Organized Sessions head to Self-Organized Sessions.
Add times where you like to run your activities here by just pressing "Add another". You can add multiple times if you like to split your event over multiple timeslots. A Self-Organized Session should have at least one timeslot though ;)
Enter a full description of the event here. The field allows using the full mediawiki syntax for text formating.
The Signal messenger is generally considered as the most secure
encrypted messaging application available today. Signal's code is
licensed under the GPL 3 and thus free software. But in many ways
Signal goes against the values of the free software community. It
depends on proprietary Google services, it requires Google libraries to
run and it depends centralized servers which should not be used by
In justification of these decisions Signal lead developer has written a
provocative blog post in which he basically claims that federated
services are unable to deliver innovations.
For Signal's critics there is one problem: Moxie is right. Everyone
with an unbiased look at XMPP or E-Mail or any other federated service
should clearly be able to see this. While Signal provides secure
end-to-end encryption for all its users XMPP has 5 different end-to-end
encryption methods - and none of them is enabled by default.
What can decentralized services do to break out of this cycle? And what
other problems are there around abuse handling (xmpp is seeing a major
spam flood these days)? And does the ability to self-host mean that
everyone should host their own infrastructure?
This is a minor edit
Watch this page