<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi everyone,<br>
<br>
It's recently been noticed that I've made some changes to the
Cryptoparty.org website, including the addition of a new SSL
certificate and a one-line relaunch statement. Some may be curious
about this, and Malte has asked me to join the mailing list to
discuss.<br>
<br>
Last year I was too embroiled in my work and other projects to work
at all on Cryptoparty. I would like this year to be different, by
rejuvenating the site, making the work already done by many others
more accessible, and additionally adding some features.<br>
<br>
As a breakdown, some of my thoughts are:<br>
<br>
* An anonymous meetup.com-like system for creating, requesting, and
marking attendance to Cryptoparties. I do not believe the use of
Wikis for this is accessible or the most efficient means of creating
gatherings for a primary audience of non-technical people.<br>
<br>
* Comprehensive list of resources<br>
<br>
* Creation of a full suite of learning materials, in an Open Tech
School like manner <br>
<br>
* Forums<br>
<br>
* Possible future services such as free Riseup like email services
hosted outside of US datacentres<br>
<br>
* TOR exit node(s)<br>
<br>
From my perspective if Cryptoparties are about teaching, creating
dialogue, pooling resources, learning, etc, perhaps we can also use
the medium to also contribute network services (email, TOR, etc) to
the community in some manner. <br>
<br>
Malte suggested wildcard domains, ie. pl.cryptoparty.org,
de.cryptoparty.org etc to provide different countries with their own
Wikis. I'm not opposed to this idea, but my only thoughts are about
fragmentation and confusion for end users - if we were to assume a
global Cryptoparty 'management' system existed (to
create/attend/request parties), what kind of information would be on
a country-specific site that should not be in a global unified place
(assuming multi-lingual capabilities were part of development from
the beginning)? Again I'm not opposed to the idea, I'm just
interested in understanding the use-case/benefit.<br>
<br>
I understand the decentralised ideology and the danger of a
completely centralised 'portal' if you like, but, I'm also wary of
the Cryptoparty message being confined to a primarily technical
audience. <br>
<br>
I don't mean to barge in on everyone, I do know considerable work
has been going on. I do feel as though the climate is right to
re-arm Cryptoparty, and I'd like to add some energy.<br>
<br>
Thoughts?<br>
<br>
<i>-sloop</i><br>
<br>
<br>
<br>
<br>
</body>
</html>