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