summaryrefslogtreecommitdiff
path: root/updates
diff options
context:
space:
mode:
Diffstat (limited to 'updates')
-rw-r--r--updates/2019/36c3-in-leipzig.en.md77
1 files changed, 77 insertions, 0 deletions
diff --git a/updates/2019/36c3-in-leipzig.en.md b/updates/2019/36c3-in-leipzig.en.md
new file mode 100644
index 00000000..ab1d3d29
--- /dev/null
+++ b/updates/2019/36c3-in-leipzig.en.md
@@ -0,0 +1,77 @@
1title: 36th Chaos Communication Congress to take place in Leipzig
2date: 2019-10-03 22:43:32
3updated: 2019-10-03 22:43:32
4author: erdgeist
5tags: update, pressemitteilung, congress, 36c3
6
7For the 36th time the Chaos Computer Club (CCC) will host the Chaos Communication Congress between Christmas and New Year’s Eve.
8
9<!-- TEASER_END -->
10
11The 36C3, which will take place at [Messe
12Leipzig](https://en.wikipedia.org/wiki/Leipzig_Trade_Fair), is the
13largest hacker conference in Europe and – like all CCC events – will be
14organised and executed entirely by volunteers. As last year, around
1517,000 participants are expected, including more than 2,000 volunteers.
16
17## Call for Participation
18
19We would like to fill our approximately 120 curated talk slots with
20high-quality content and therefore today solicit your submissions with
21our [Call for
22Participation](https://content.events.ccc.de/cfp/36c3/index.en.html).
23
24On four days, in addition to the curated talks in five large halls,
25there will be a widely varied program of self-organised workshops at the
26stages of our assemblies distributed throughout the event venue. There
27will also be lots of art & beauty with exhibitions, light installations,
28bars and parties.
29
30We want to stress the unusually short submission deadline this year: 26
31October 2019. No excuses, please.
32
33## Call for Angels
34
35In order to build all that – and to tear it down again – we will once
36again need our legendary and untiring Angel power. Angels are our
37volunteer helpers, they are the true backbone of any CCC event. We call
38upon all of you to help at Congress and become part of the event. If
39possible, do plan a longer stay in Leipzig, until January 5th, in order
40to help during teardown.
41
42## Call for Assemblies
43
44During the last two years in Leipzig we learned many lessons and want to
45apply as much of the knowledge as possible. That’s why we intend to
46change as little about the Assemblies process as possible: in order to
47consolidate and exchange the knowledge and experiences we gained.
48
49If you have organised an Assembly last year, please expect the same
50area, requirements, and infrastructure as last year. Even supposedly
51small changes may lead to large planning overhead and excess preparation
52time which we’re not going to have this year.
53
54## 36C3: Resource exhaustion
55
56Resource exhaustion is a [type of attack on computer
57systems](https://en.wikipedia.org/wiki/Resource_exhaustion_attack) that
58is considered rather crude and destructive. Even with two large scale
59events this year we don’t want to execute such an attack against
60ourselves. Instead we want to use our own resources in a measured,
61effective way:
62
63Those who do know the extend of their own resources, can set [limits, to
64prevent their
65exhaustion](http://man7.org/linux/man-pages/man5/limits.conf.5.html).
66
67On an international stage this wisdom appears to be absent. Resources
68are exhausted knowingly and willfully, instead of limiting their use.
69Two years ago, during 34C3, we [dedicated a day of our schedule to the
70topic of global climate
71change](https://fahrplan.events.ccc.de/congress/2017/Fahrplan/schedule/3.html),
72and in the year following that we joined forces with other civil rights
73and environment protection NGOs for the [Bits & Bäume
74conference](https://bits-und-baeume.org/info/de).
75
76It is in this tradition and with this spirit that we see this year's
77congress's motto **36C3: Resource Exhaustion**.****