WHY2025 wiki - User contributions [en]

Parcel deliveries

2025-07-30T18:02:58Z

Okarin:

search terms: packet delivery, logistics

= Shipping things to WHY2025 =

It is possible to ship parcels to WHY2025. However, it's a lot of work for us and many things can go wrong. Therefore, we'd prefer it if you can find alternatives to shipping things to the site. This way we can avoid a lot of disappointment and effort.

There will be a delay after delivery of your package by the courier, before the package will be available to you. This delay could easily be up to an entire day.

= Alternatives: =

* Please try hard to find someone with a car who is going to the site. If you don't know anyone, ask on the [[IRC]] channel (#why2025 on OFTC).

* Check whether your local hackerspace is organizing bulk transport to the site (many are) and whether you can ship/bring things to said space ahead of the event as well and have it join said transport.

= What can go wrong =

* We have no way of tracking packages beyond this (publicly editable) wiki page. Packages can get lost, misdelivered, or damaged and we are not able to do anything about it.
* The event is at a site that does not usually receive large volumes of mail and is not familiar to courier services. This means delivery services may attempt to deliver to the wrong place, and packages would be very difficult to trace.
* We are not set up for significant logistics and package handling on site. We are all volunteers that have a lot of other tasks to do and package handling is something we do when we can and if we can, but our priority is making a cool hacker camp happen, not running a post office.

If you have no other options, we do offer a best-effort service, but there are no guarantees. Specifically:

= DISCLAIMER =

* WHY2025, Stichting IFCAT Foundation, and Manege Beukers accept no liability for your package.
* Although we will sign for receipt, we are not able to take responsibility of your package. If it happens to be damaged, stolen in transit, has the wrong contents, or it gets delivered to the wrong place, there is nothing we'll be able to do to help you.
* If for any reason your package seems dangerous in any way, we might reject or dispose of it before informing you — and still disclaim any liability.

If your package gets lost, there is nothing we can do about it. Please only use this option as a last resort.

= Howto =

To ship a package to WHY2025, follow the following steps

1. Make sure it's a package, not a letter/envelope. We have limited infrastructure for handling packages but no infrastructure at all for handling envelopes. Sorry!

2. If your package is above 23 kg it **must** be on a pallet. Make sure it is either below that limit, or packaged on a pallet. If a package is on a pallet, make sure it's weatherproof as it may get rained on during transport and storage.

3. Make sure the package does not consist of food or perishable items (see below)

4. Check that the package is able to arrive between **Saturday, August 2nd** and **Monday, August 11th**. We are not able to receive packages at all outside this time window. If a package arrives outside that time window, it will most likely not reach us, and therefore also not reach you. The package will not be returned but discarded in whatever way seems appropriate. Note: in some countries, you can set a specific delivery date in the future. Dutch couriers typically ignore that.

5. Make sure the package is addressed correctly. Please use the following address format if possible, or at least include all the following information:

To: YOUR NAME @ YOUR VILLAGE
WHY2025 Team Warehouse p/a Manege Beukers

Wagenweg 12
1724 PT Oudkarspel
The Netherlands

Note that "PT" is part of the postal code "1724 PT".

<div style="background-color:red; padding: 10px;">
<span style="color:white; font-weight: bold;">''Regardless of your anxiety level, and regardless of how much you believe that you are not a burden, DO NOT CONTACT and DO NOT VISIT the riding hall (manage) yourself. All communication must go through Team:Warehouse, and we will pick up your package. This may take up an entire extra day after it was delivered; please remain calm and patient.''</span>
</div>

'''If the shipping company requires a phone number, put **your own** phone number on the shipping label. That way you can react if the shipping company gets confused about where to deliver. Please do not use our phone numbers, as we can't guarantee reachability at the time the package is due to be delivered.'''

6. Add your package to the list at the end of this page. The list is sorted by projected arrival day. Please keep it this way. We will update this page once we receive the package.

7. Pick it up at the logistics warehouse. The warehouse is the building next to the Heaven tent.

= Perishable or food items =
Perishable or food items include BBQ meat, pizza, drinks, and perishable foods. We cannot handle deliveries of such items on site at all.

We have contractual obligations to our food vendors on site that prevent us from delivering food or accepting food deliveries. We also don't have the capacity for cold storage, rapid delivery, or food-safe logistics. Please understand that we can't offer this kind of service and don't ask us about it. Sorry!

If you want to have food delivered to you on site, you're on your own. You will have to wait for it at the gate until it arrives and intercept them yourself. Delivery trucks are not allowed on the terrain. Be aware that many food suppliers have quite strict policies on deliveries, and will not deliver to a site like ours anyway. If you need large quantities of food, a better choice might be to do a shopping run yourself in a nearby supermarket. A list of supermarkets and their opening hours are on the [[Supermarkets|Supermarkets wiki page]].

= Delivery policy =

== No envelopes! ==

Note: we '''can't''' receive envelopes, so make sure small stuff is in a box even if it would fit in an envelope.

== Not on the wiki ==
If your package is delivered but it's not on the wiki, the package may be discarded in whatever way seems appropriate. You could try a reconciliation gift when picking it up at the Warehouse. Traditionally this is apple pie but we're open for surprises :)

== Small parcels ==

Small parcels (boxes) will be routed to our storage; once it has arrived, infodesk can tell you where to pick it up. The limit for small boxes is 23 kg. We will try to update this page when the shipment arrives.

== Big parcels ==

Any parcel above 23 kg counts as big.

Big parcels **MUST BE ON A PALLET**. They will be delivered to the village directly if the village has a known location (a tent) that is reachable by one of the roads. If not, we'll leave it at a place we can access by road -- possibly in a restricted area from which you cannot pick it up without our help. Packages might get rained on in transit or in storage, so please make sure they are weatherproof.

'''Please do not have anything shipped to the site (by any means) that you are not able to transport back away from the site.'''

= Expected/delivered packages - ADD TO THIS LIST!! =

Please sort by expected arrival date.

{|class=wikitable
! Expected arrival date !! Recipient name !! Village !! How big and heavy is it?<br>''metric please!'' !! Description of contents !! Received? (to be edited by Team:Warehouse)
|- style="background: #faa;"
| Before 2025-08-02
|colspan=5| Absolutely do not have anything delivered before Saturday 2nd of August.<br>We don't have the people or equipment to deal with it.
|-
| 2025-08-02 || Example || Example || small example package (0.5kg) || example contents
|-
| 2025-08-02 - 4 || Okarin || Heaven || 11 boxes by courier || t-shirts
|-
| 2025-08-02 - 4 || Okarin || Heaven || 2 boxes || safety vests
|-
| 2025-08-01 - 4 || Lightning5 || NOC || 1 box (2,5kg) || sleeping mat
|-
| 2025-08-04 || Mitch Altman || Hardware Hacking Area || Euro Pallet with 11 boxes + roller-board (156kg) || soldering irons and other tools, kits
|-
| 2025-08-04 - 8 || Marvin Brandstetter HyperCraft3r || Team Parking || medium package (ca. 3kg) || 3 Workpants
|-
|-|- style="background: #faa"
| After 2025-08-11
|colspan=5| You can't have anything delivered to WHY after day 4!
|-
|}

[[Team:Warehouse]]

Parcel deliveries

2025-07-30T07:35:14Z

Okarin:

search terms: packet delivery, logistics

= Shipping things to WHY2025 =

It is possible to ship parcels to WHY2025. However, it's a lot of work for us and many things can go wrong. Therefore, we'd prefer it if you can find alternatives to shipping things to the site. This way we can avoid a lot of disappointment and effort.

There will be a delay after delivery of your package by the courier, before the package will be available to you. This delay could easily be up to an entire day.

= Alternatives: =

* Please try hard to find someone with a car who is going to the site. If you don't know anyone, ask on the [[IRC]] channel (#why2025 on OFTC).

* Check whether your local hackerspace is organizing bulk transport to the site (many are) and whether you can ship/bring things to said space ahead of the event as well and have it join said transport.

= What can go wrong =

* We have no way of tracking packages beyond this (publicly editable) wiki page. Packages can get lost, misdelivered, or damaged and we are not able to do anything about it.
* The event is at a site that does not usually receive large volumes of mail and is not familiar to courier services. This means delivery services may attempt to deliver to the wrong place, and packages would be very difficult to trace.
* We are not set up for significant logistics and package handling on site. We are all volunteers that have a lot of other tasks to do and package handling is something we do when we can and if we can, but our priority is making a cool hacker camp happen, not running a post office.

If you have no other options, we do offer a best-effort service, but there are no guarantees. Specifically:

= DISCLAIMER =

* WHY2025, Stichting IFCAT Foundation, and Manege Beukers accept no liability for your package.
* Although we will sign for receipt, we are not able to take responsibility of your package. If it happens to be damaged, stolen in transit, has the wrong contents, or it gets delivered to the wrong place, there is nothing we'll be able to do to help you.
* If for any reason your package seems dangerous in any way, we might reject or dispose of it before informing you — and still disclaim any liability.

If your package gets lost, there is nothing we can do about it. Please only use this option as a last resort.

= Howto =

To ship a package to WHY2025, follow the following steps

1. Make sure it's a package, not a letter/envelope. We have limited infrastructure for handling packages but no infrastructure at all for handling envelopes. Sorry!

2. If your package is above 23 kg it **must** be on a pallet. Make sure it is either below that limit, or packaged on a pallet. If a package is on a pallet, make sure it's weatherproof as it may get rained on during transport and storage.

3. Make sure the package does not consist of food or perishable items (see below)

4. Check that the package is able to arrive between **Saturday, August 2nd** and **Monday, August 11th**. We are not able to receive packages at all outside this time window. If a package arrives outside that time window, it will most likely not reach us, and therefore also not reach you. The package will not be returned but discarded in whatever way seems appropriate. Note: in some countries, you can set a specific delivery date in the future. Dutch couriers typically ignore that.

5. Make sure the package is addressed correctly. Please use the following address format if possible, or at least include all the following information:

To: YOUR NAME @ YOUR VILLAGE
WHY2025 Team Warehouse p/a Manege Beukers

Wagenweg 12
1724 PT Oudkarspel
The Netherlands

Note that "PT" is part of the postal code "1724 PT".

<div style="background-color:red; padding: 10px;">
<span style="color:white; font-weight: bold;">''Regardless of your anxiety level, and regardless of how much you believe that you are not a burden, DO NOT CONTACT and DO NOT VISIT the riding hall (manage) yourself. All communication must go through Team:Warehouse, and we will pick up your package. This may take up an entire extra day after it was delivered; please remain calm and patient.''</span>
</div>

'''If the shipping company requires a phone number, put **your own** phone number on the shipping label. That way you can react if the shipping company gets confused about where to deliver. Please do not use our phone numbers, as we can't guarantee reachability at the time the package is due to be delivered.'''

6. Add your package to the list at the end of this page. The list is sorted by projected arrival day. Please keep it this way. We will update this page once we receive the package.

7. Pick it up at the logistics warehouse. The warehouse is the building next to the Heaven tent.

= Perishable or food items =
Perishable or food items include BBQ meat, pizza, drinks, and perishable foods. We cannot handle deliveries of such items on site at all.

We have contractual obligations to our food vendors on site that prevent us from delivering food or accepting food deliveries. We also don't have the capacity for cold storage, rapid delivery, or food-safe logistics. Please understand that we can't offer this kind of service and don't ask us about it. Sorry!

If you want to have food delivered to you on site, you're on your own. You will have to wait for it at the gate until it arrives and intercept them yourself. Delivery trucks are not allowed on the terrain. Be aware that many food suppliers have quite strict policies on deliveries, and will not deliver to a site like ours anyway. If you need large quantities of food, a better choice might be to do a shopping run yourself in a nearby supermarket. A list of supermarkets and their opening hours are on the [[Supermarkets|Supermarkets wiki page]].

= Delivery policy =

== No envelopes! ==

Note: we '''can't''' receive envelopes, so make sure small stuff is in a box even if it would fit in an envelope.

== Not on the wiki ==
If your package is delivered but it's not on the wiki, the package may be discarded in whatever way seems appropriate. You could try a reconciliation gift when picking it up at the Warehouse. Traditionally this is apple pie but we're open for surprises :)

== Small parcels ==

Small parcels (boxes) will be routed to our storage; once it has arrived, infodesk can tell you where to pick it up. The limit for small boxes is 23 kg. We will try to update this page when the shipment arrives.

== Big parcels ==

Any parcel above 23 kg counts as big.

Big parcels **MUST BE ON A PALLET**. They will be delivered to the village directly if the village has a known location (a tent) that is reachable by one of the roads. If not, we'll leave it at a place we can access by road -- possibly in a restricted area from which you cannot pick it up without our help. Packages might get rained on in transit or in storage, so please make sure they are weatherproof.

'''Please do not have anything shipped to the site (by any means) that you are not able to transport back away from the site.'''

= Expected/delivered packages - ADD TO THIS LIST!! =

Please sort by expected arrival date.

{|class=wikitable
! Expected arrival date !! Recipient name !! Village !! How big and heavy is it?<br>''metric please!'' !! Description of contents !! Received? (to be edited by Team:Warehouse)
|- style="background: #faa;"
| Before 2025-08-02
|colspan=5| Absolutely do not have anything delivered before Saturday 2nd of August.<br>We don't have the people or equipment to deal with it.
|-
| 2025-08-02 || Example || Example || small example package (0.5kg) || example contents
|-
| 2025-08-01 - 4 || Okarin || Heaven || 11 boxes by courier || t-shirts
|-
| 2025-08-01 - 4 || Okarin || Heaven || 2 boxes || safety vests
|-
| 2025-08-04 || Mitch Altman || Hardware Hacking Area || Euro Pallet with 11 boxes + roller-board (156kg) || soldering irons and other tools, kits
|-
| 2025-08-04 - 8 || Marvin Brandstetter HyperCraft3r || Team Parking || medium package (ca. 3kg) || 3 Workpants
|-
|-|- style="background: #faa"
| After 2025-08-11
|colspan=5| You can't have anything delivered to WHY after day 4!
|-
|}

[[Team:Warehouse]]

Parcel deliveries

2025-07-30T07:34:04Z

Okarin:

search terms: packet delivery, logistics

= Shipping things to WHY2025 =

It is possible to ship parcels to WHY2025. However, it's a lot of work for us and many things can go wrong. Therefore, we'd prefer it if you can find alternatives to shipping things to the site. This way we can avoid a lot of disappointment and effort.

There will be a delay after delivery of your package by the courier, before the package will be available to you. This delay could easily be up to an entire day.

= Alternatives: =

* Please try hard to find someone with a car who is going to the site. If you don't know anyone, ask on the [[IRC]] channel (#why2025 on OFTC).

* Check whether your local hackerspace is organizing bulk transport to the site (many are) and whether you can ship/bring things to said space ahead of the event as well and have it join said transport.

= What can go wrong =

* We have no way of tracking packages beyond this (publicly editable) wiki page. Packages can get lost, misdelivered, or damaged and we are not able to do anything about it.
* The event is at a site that does not usually receive large volumes of mail and is not familiar to courier services. This means delivery services may attempt to deliver to the wrong place, and packages would be very difficult to trace.
* We are not set up for significant logistics and package handling on site. We are all volunteers that have a lot of other tasks to do and package handling is something we do when we can and if we can, but our priority is making a cool hacker camp happen, not running a post office.

If you have no other options, we do offer a best-effort service, but there are no guarantees. Specifically:

= DISCLAIMER =

* WHY2025, Stichting IFCAT Foundation, and Manege Beukers accept no liability for your package.
* Although we will sign for receipt, we are not able to take responsibility of your package. If it happens to be damaged, stolen in transit, has the wrong contents, or it gets delivered to the wrong place, there is nothing we'll be able to do to help you.
* If for any reason your package seems dangerous in any way, we might reject or dispose of it before informing you — and still disclaim any liability.

If your package gets lost, there is nothing we can do about it. Please only use this option as a last resort.

= Howto =

To ship a package to WHY2025, follow the following steps

1. Make sure it's a package, not a letter/envelope. We have limited infrastructure for handling packages but no infrastructure at all for handling envelopes. Sorry!

2. If your package is above 23 kg it **must** be on a pallet. Make sure it is either below that limit, or packaged on a pallet. If a package is on a pallet, make sure it's weatherproof as it may get rained on during transport and storage.

3. Make sure the package does not consist of food or perishable items (see below)

4. Check that the package is able to arrive between **Saturday, August 2nd** and **Monday, August 11th**. We are not able to receive packages at all outside this time window. If a package arrives outside that time window, it will most likely not reach us, and therefore also not reach you. The package will not be returned but discarded in whatever way seems appropriate. Note: in some countries, you can set a specific delivery date in the future. Dutch couriers typically ignore that.

5. Make sure the package is addressed correctly. Please use the following address format if possible, or at least include all the following information:

To: YOUR NAME @ YOUR VILLAGE
WHY2025 Team Warehouse p/a Manege Beukers

Wagenweg 12
1724 PT Oudkarspel
The Netherlands

Note that "PT" is part of the postal code "1724 PT".

<div style="background-color:red; padding: 10px;">
<span style="color:white; font-weight: bold;">''Regardless of your anxiety level, and regardless of how much you believe that you are not a burden, DO NOT CONTACT and DO NOT VISIT the riding hall (manage) yourself. All communication must go through Team:Warehouse, and we will pick up your package. This may take up an entire extra day after it was delivered; please remain calm and patient.''</span>
</div>

'''If the shipping company requires a phone number, put **your own** phone number on the shipping label. That way you can react if the shipping company gets confused about where to deliver. Please do not use our phone numbers, as we can't guarantee reachability at the time the package is due to be delivered.'''

6. Add your package to the list at the end of this page. The list is sorted by projected arrival day. Please keep it this way. We will update this page once we receive the package.

7. Pick it up at the logistics warehouse. The warehouse is the building next to the Heaven tent.

= Perishable or food items =
Perishable or food items include BBQ meat, pizza, drinks, and perishable foods. We cannot handle deliveries of such items on site at all.

We have contractual obligations to our food vendors on site that prevent us from delivering food or accepting food deliveries. We also don't have the capacity for cold storage, rapid delivery, or food-safe logistics. Please understand that we can't offer this kind of service and don't ask us about it. Sorry!

If you want to have food delivered to you on site, you're on your own. You will have to wait for it at the gate until it arrives and intercept them yourself. Delivery trucks are not allowed on the terrain. Be aware that many food suppliers have quite strict policies on deliveries, and will not deliver to a site like ours anyway. If you need large quantities of food, a better choice might be to do a shopping run yourself in a nearby supermarket. A list of supermarkets and their opening hours are on the [[Supermarkets|Supermarkets wiki page]].

= Delivery policy =

== No envelopes! ==

Note: we '''can't''' receive envelopes, so make sure small stuff is in a box even if it would fit in an envelope.

== Not on the wiki ==
If your package is delivered but it's not on the wiki, the package may be discarded in whatever way seems appropriate. You could try a reconciliation gift when picking it up at the Warehouse. Traditionally this is apple pie but we're open for surprises :)

== Small parcels ==

Small parcels (boxes) will be routed to our storage; once it has arrived, infodesk can tell you where to pick it up. The limit for small boxes is 23 kg. We will try to update this page when the shipment arrives.

== Big parcels ==

Any parcel above 23 kg counts as big.

Big parcels **MUST BE ON A PALLET**. They will be delivered to the village directly if the village has a known location (a tent) that is reachable by one of the roads. If not, we'll leave it at a place we can access by road -- possibly in a restricted area from which you cannot pick it up without our help. Packages might get rained on in transit or in storage, so please make sure they are weatherproof.

'''Please do not have anything shipped to the site (by any means) that you are not able to transport back away from the site.'''

= Expected/delivered packages - ADD TO THIS LIST!! =

Please sort by expected arrival date.

{|class=wikitable
! Expected arrival date !! Recipient name !! Village !! How big and heavy is it?<br>''metric please!'' !! Description of contents !! Received? (to be edited by Team:Warehouse)
|- style="background: #faa;"
| Before 2025-08-02
|colspan=5| Absolutely do not have anything delivered before Saturday 2nd of August.<br>We don't have the people or equipment to deal with it.
|-
| 2025-08-02 || Example || Example || small example package (0.5kg) || example contents
|-
| 2025-08-01 || Okarin || Heaven || 11 boxes by courier || t-shirts
|-
| 2025-08-01 || Okarin || Heaven || 2 boxes || safety vests
|-
| 2025-08-04 || Mitch Altman || Hardware Hacking Area || Euro Pallet with 11 boxes + roller-board (156kg) || soldering irons and other tools, kits
|-
| 2025-08-04 - 8 || Marvin Brandstetter HyperCraft3r || Team Parking || medium package (ca. 3kg) || 3 Workpants
|-
|-|- style="background: #faa"
| After 2025-08-11
|colspan=5| You can't have anything delivered to WHY after day 4!
|-
|}

[[Team:Warehouse]]

Parcel deliveries

2025-07-30T07:32:05Z

Okarin: Updated because red on black is hard to read.

search terms: packet delivery, logistics

= Shipping things to WHY2025 =

It is possible to ship parcels to WHY2025. However, it's a lot of work for us and many things can go wrong. Therefore, we'd prefer it if you can find alternatives to shipping things to the site. This way we can avoid a lot of disappointment and effort.

There will be a delay after delivery of your package by the courier, before the package will be available to you. This delay could easily be up to an entire day.

= Alternatives: =

* Please try hard to find someone with a car who is going to the site. If you don't know anyone, ask on the [[IRC]] channel (#why2025 on OFTC).

* Check whether your local hackerspace is organizing bulk transport to the site (many are) and whether you can ship/bring things to said space ahead of the event as well and have it join said transport.

= What can go wrong =

* We have no way of tracking packages beyond this (publicly editable) wiki page. Packages can get lost, misdelivered, or damaged and we are not able to do anything about it.
* The event is at a site that does not usually receive large volumes of mail and is not familiar to courier services. This means delivery services may attempt to deliver to the wrong place, and packages would be very difficult to trace.
* We are not set up for significant logistics and package handling on site. We are all volunteers that have a lot of other tasks to do and package handling is something we do when we can and if we can, but our priority is making a cool hacker camp happen, not running a post office.

If you have no other options, we do offer a best-effort service, but there are no guarantees. Specifically:

= DISCLAIMER =

* WHY2025, Stichting IFCAT Foundation, and Manege Beukers accept no liability for your package.
* Although we will sign for receipt, we are not able to take responsibility of your package. If it happens to be damaged, stolen in transit, has the wrong contents, or it gets delivered to the wrong place, there is nothing we'll be able to do to help you.
* If for any reason your package seems dangerous in any way, we might reject or dispose of it before informing you — and still disclaim any liability.

If your package gets lost, there is nothing we can do about it. Please only use this option as a last resort.

= Howto =

To ship a package to WHY2025, follow the following steps

1. Make sure it's a package, not a letter/envelope. We have limited infrastructure for handling packages but no infrastructure at all for handling envelopes. Sorry!

2. If your package is above 23 kg it **must** be on a pallet. Make sure it is either below that limit, or packaged on a pallet. If a package is on a pallet, make sure it's weatherproof as it may get rained on during transport and storage.

3. Make sure the package does not consist of food or perishable items (see below)

4. Check that the package is able to arrive between **Saturday, August 2nd** and **Monday, August 11th**. We are not able to receive packages at all outside this time window. If a package arrives outside that time window, it will most likely not reach us, and therefore also not reach you. The package will not be returned but discarded in whatever way seems appropriate. Note: in some countries, you can set a specific delivery date in the future. Dutch couriers typically ignore that.

5. Make sure the package is addressed correctly. Please use the following address format if possible, or at least include all the following information:

To: YOUR NAME @ YOUR VILLAGE
WHY2025 Team Warehouse p/a Manege Beukers

Wagenweg 12
1724 PT Oudkarspel
The Netherlands

Note that "PT" is part of the postal code "1724 PT".

<div style="background-color:red; padding: 10px;">
<span style="color:white; font-weight: bold;">''Regardless of your anxiety level, and regardless of how much you believe that you are not a burden, DO NOT CONTACT and DO NOT VISIT the riding hall (manage) yourself. All communication must go through Team:Warehouse, and we will pick up your package. This may take up an entire extra day after it was delivered; please remain calm and patient.''</span>
</div>

'''If the shipping company requires a phone number, put **your own** phone number on the shipping label. That way you can react if the shipping company gets confused about where to deliver. Please do not use our phone numbers, as we can't guarantee reachability at the time the package is due to be delivered.'''

6. Add your package to the list at the end of this page. The list is sorted by projected arrival day. Please keep it this way. We will update this page once we receive the package.

7. Pick it up at the logistics warehouse. The warehouse is the building next to the Heaven tent.

= Perishable or food items =
Perishable or food items include BBQ meat, pizza, drinks, and perishable foods. We cannot handle deliveries of such items on site at all.

We have contractual obligations to our food vendors on site that prevent us from delivering food or accepting food deliveries. We also don't have the capacity for cold storage, rapid delivery, or food-safe logistics. Please understand that we can't offer this kind of service and don't ask us about it. Sorry!

If you want to have food delivered to you on site, you're on your own. You will have to wait for it at the gate until it arrives and intercept them yourself. Delivery trucks are not allowed on the terrain. Be aware that many food suppliers have quite strict policies on deliveries, and will not deliver to a site like ours anyway. If you need large quantities of food, a better choice might be to do a shopping run yourself in a nearby supermarket. A list of supermarkets and their opening hours are on the [[Supermarkets|Supermarkets wiki page]].

= Delivery policy =

== No envelopes! ==

Note: we '''can't''' receive envelopes, so make sure small stuff is in a box even if it would fit in an envelope.

== Not on the wiki ==
If your package is delivered but it's not on the wiki, the package may be discarded in whatever way seems appropriate. You could try a reconciliation gift when picking it up at the Warehouse. Traditionally this is apple pie but we're open for surprises :)

== Small parcels ==

Small parcels (boxes) will be routed to our storage; once it has arrived, infodesk can tell you where to pick it up. The limit for small boxes is 23 kg. We will try to update this page when the shipment arrives.

== Big parcels ==

Any parcel above 23 kg counts as big.

Big parcels **MUST BE ON A PALLET**. They will be delivered to the village directly if the village has a known location (a tent) that is reachable by one of the roads. If not, we'll leave it at a place we can access by road -- possibly in a restricted area from which you cannot pick it up without our help. Packages might get rained on in transit or in storage, so please make sure they are weatherproof.

'''Please do not have anything shipped to the site (by any means) that you are not able to transport back away from the site.'''

= Expected/delivered packages - ADD TO THIS LIST!! =

Please sort by expected arrival date.

{|class=wikitable
! Expected arrival date !! Recipient name !! Village !! How big and heavy is it?<br>''metric please!'' !! Description of contents !! Received? (to be edited by Team:Warehouse)
|- style="background: #faa;"
| Before 2025-08-02
|colspan=5| Absolutely do not have anything delivered before Saturday 2nd of August.<br>We don't have the people or equipment to deal with it.
|-
| 2025-08-02 || Example || Example || small example package (0.5kg) || example contents
|-
| 2025-08-04 || Mitch Altman || Hardware Hacking Area || Euro Pallet with 11 boxes + roller-board (156kg) || soldering irons and other tools, kits
|-
| 2025-08-04 - 8 || Marvin Brandstetter HyperCraft3r || Team Parking || medium package (ca. 3kg) || 3 Workpants
|-
|-|- style="background: #faa"
| After 2025-08-11
|colspan=5| You can't have anything delivered to WHY after day 4!
|-
|}

[[Team:Warehouse]]

Template:Whybox

2025-07-22T14:02:52Z

Okarin:

{| style="width:100%;" class="whybox" |
|-
| class="whybox-title" style="background: #61F2FF; background: linear-gradient(90deg,rgba(82, 52, 191, 1) 0%, rgba(242, 94, 149, 1) 50%, rgba(82, 52, 191, 1) 100%); text-align: center; font-family:'Beon','Oxanium'; padding:0px; font-size:30px; vertical-align: bottom; display: block; color: white;" data-input="{{{title}}}" |
<span style="position: relative; top: 0px;">{{{title}}}</span>
|-
| style="padding:10px;" |
{{{content}}}
|}

Vacancies

2025-07-20T16:59:29Z

Okarin:

<div style="border: 1ex solid #491d88; background: #fec859; color: #331a38; padding: 1em; width: 60%; font-size: 120%; margin: 1em">
<p>This page describes how to become part of the organization, where you are more than welcome!</p><br>
<p>Want to help out during the event doing one or more things on the field? Check the [[Angel_Guide]]</p>
</div>

All teams are starting up. That means that they are still preparing for showing their vacancies on this page.

In the mean time: is there anything you would like to do that's not listed here yet? Ask at [ircs://irc.oftc.net/why2025 #why2025 on OFTC]. New to IRC? Use the [https://webchat.oftc.net/?randomnick=1&channels=why2025&prompt=1 web client] or send a mail at volunteers@why2025.org

There are two tables here. One with specific vacancies, and one with teams who need general members.

This info is accurate as of 2024-10-06.

== Open Vacancies ==

{| class="wikitable sortable" style="width: 100%" |
|-
! Team, Role
! Description
|-
| [[Team:Volunteers]], Team members
|
What would WHY2025 be without angels, all the volunteers that help make camp perfect?

Help us help them so they can have fun helping at camp :)

Looking for Angel Kitchen Coordinator.

Interested? Need more info? Contact {{UserLink|Okarin}} or sent an email to [mailto:volunteers@why2025.org volunteers@why2025.org]
|-
| [[Team:Parking]], Parking coordinator support, 'evenementenverkeersbegeleiders'
|
Are you the Dutch-/English-speaking hero who can help out everyone with a car? Or are you even an evenementenverkeersbegeleiders and can help out at day -1, 0 or 1?

Do you want to help making parking possible, and look at the local regulations? Or do you have strong oppinions on how cars should be placed?

We are in dire need of supporting people for the parking coordinator. Workload can vary, but we certainly need support on the field during the late build-up and the event itself. Please contact {{UserLink|Konmei}} for more information and if you are interested.
|-

| [[Team:Merch]], administrative coordinator
|
Quality inspector, distribution planner and online shop stockkeeper
We are looking for a Merch coordinator, who keeps an eye on the shop, handles questions, production and delivery of the WHY2025 Merch. First to feel the merch, looking at samples.[https://tickets.why2025.org/media/pub/ifcat/why2025/item-22-6fce47a6-9b15-4fce-b3ee-b065e9067b23.jpeg image of shirt]

Let's dress the hackerscene, contact {{UserLink|Netsmurf}}!
|-
| [[Team:Shuttle]], Team members
|
We're looking for people to help organise the Shuttles.
The shuttle is, for a large amount of visitors, their first encounter with the event. They should enthusiastic and full of good energy. Really rewarding job though! Not only when arriving, but also when you bring them back to the train.
For questions, contact {{UserLink|crablab}}.
|-
| [[Team:Badge]], Team members
|
We can definitely use more software developers that are willing to commit to working with us on this interesting project.

If you have experience with '''embedded C''' programming we'd love for you to join the '''Firmware''' team and if you have experience with '''Web / Application''' development the '''BadgeHub''' team would love to see you help out.

Join our '''Signal''' group for '''Newcomers''' and write us a message if you feel like joining us or just want to explore if you see it fit. https://signal.group/#CjQKICKbwZzlVup_A_smn_rUWrQVTzomGlBZgkP3Txm_P23xEhDzXQr4gvUMxUxivNZKuOEj
|-
| [[Team:Foodcourt]], Team members subteam "Bar"
|
We are looking for team members for the Horeca team, subteam Bar. Do you like to put a smile on people's faces?

The Bar team will organize, build and run the 3 planned Bar areas. Organizing consists of planning, designing bar set-up, ordering supplies to be delivered.
A few days before the event we will receive the ordered stuff and start the build up.
During the event on site the Angels will run the bars.
With a dedicated Bar-team we coordinate, re-supply and take turns solving any problems for the 3 event bars. Do you want to be part of the team closest to the Mate? Then this is the team for you!

For questions, contact {{UserLink|K4T0}}
|-
| [[Team:PartyArea]], Team members
|
The Party Area team will organize, build and run the WHY2025 main stage with Live Music content, DJ's Silent Disco until deep in the Night
We are looking for Team Members that can't sleep anyway and love to organize parties !!!

For questions, contact {{UserLink|Netsmurf}}
|-
| [[Team:Cohesion]], Team member
|
Team Cohesion is looking for extra team members. Both for during the event to coordinate things and in the preparation phase. Take a look at the team page for the things we are working on before the event starts if you want to lend a hand in creating policy or set up the ultimate silent lounge. For during the event we need people who are good listeners and feel up to deescalate wherever necessary.
Get in touch with us so you can help everyone be excellent to each other.

For questions, contact {{UserLink|Dany}}
|-
| [[Team:Parking]], Team Lead
|
The Parking team is a fun vitally important team responsible for making our visitors feel welcome when they arrive for the first time at WHY2025 and making sure traffic flows and parking are done in a safe and orderly way.

For questions, contact {{UserLink|Netsmurf}}
|-
| [[Team:Parking]], Team members
|
The Parking team is a fun vitally important team responsible for making our visitors feel welcome when they arrive for the first time at WHY2025 and making sure traffic flows and parking are done in a safe and orderly way.

For questions, contact {{UserLink|Netsmurf}}
|-
| [[Team:Family]], Project owner
|
Even if you do not have time to be very closely involved with FamilyZone you may want to do something for/with (your?) kids. We are very open to people to run one or two projects at the event. Check out our [[Team:Family#Projects|current project list]] for inspiration.
|-
| [[Team:Content]], Speaker Desk Volunteers
|
Team:Content is in need of volunteers for Speaker Desk (more info soon).

Contact content@why2025.org to get involved!
|-
|}

== Teams who still need members ==



{{#ask: [[Category:Team]] [[Team needs x people::>1]]
|?Team is essential to event=essential to event
|?Team has enough people=enough people
|?Team needs x people = team needs x people
|?E-Mail=Contact
|limit=100
|offset=0
|link=subject
|sort=
|outrotemplate=plteamhealthfooter
|order=asc
|headers=show
|searchlabel=... further results
|class=sortable wikitable smwtable
}}

== I want to do something small ==
Small tasks that need to be done, or large tasks that can be split in small tasks are collected at the [[Tiny_Tasks]] list

Volunteering Guide

2025-07-18T17:42:45Z

Okarin:

[[File:Volunteers needed.png|frameless|right|Volunteers requested :-)]]

<div style="border: 1ex solid #491d88; background: #fec859; color: #331a38; padding: 1em; width: 60%; font-size: 120%; margin: 1em">
<p>This page describes how to become part of the organization, where you are more than welcome!</p><br>
<p>Want to help out during the event doing one or more things on the field? Check the [[Angel_Guide]]</p>
</div>

{{VolunteeringHeader}}

<div style="max-width: 800px">
Welcome to the '''WHY2025''' volunteering page. This page has the goal to make it easy to understand '''WHY2025''' and start contributing to it. You'll find information on why this event exists, how it is organized, how decisions are made, and how you can contribute.

== Why is there an WHY2025? ==
Ultimately '''WHY2025''' wants to share knowledge about hacking with the world. This helps improve the world by making technology accessible, sharable, and understandable. We believe that sharing this knowledge creates a better world: whatever this knowledge entails. From creative use to technology to actual creation and philosophy. Therefore the range of knowledge and programmed content is very broad, but always leans towards technology and systems.

People that subscribe to this goal found that this can be done in various ways, but the ultimate would be to create a temporary outdoor physical utopia. Also known as a "hacker camp". These have been organized '''since 1993'''.

'''WHY2025''' can be described as two things:

# a physical event where people that like hacking / having a deep passion for technology meet and elevate each other.
# a place where knowledge is presented on stages and archived on the internet for anyone to see, use and access.

== How is WHY2025 organized? ==
'''WHY2025''' is organized in various ways. Most importantly it is organized by volunteers who assemble in groups about a specific subject. Legally '''WHY2025''' is organized by the IFCAT foundation: it performs bureaucratic work on request of the organization. The foundation has handed off all operational decisions to volunteers / teams: aka (to be) experts.

=== Organizational Concepts ===

'''WHY2025''' is a fully volunteer-driven event. But where do you start volunteering? Knowing what the structure looks like might help.

A simple view of '''WHY2025''' yields the following six key concepts:

* '''Roles''': description of responsibilities. It is a description of 'what' the team should accomplish, it does not state 'how' something needs to be done. For example: the 'Deco' role states "make the whole event pretty" and "impress visitors with a memorable atmosphere". A decent list of roles can be found here: [[roles]].
* '''Teams''': a group of people that are (or want to become) experts on a certain subject. Some teams are established and also help on other events such as CCC and EMF. Others are new or unique to WHY, such as the Flags or NUTS. In the end, teams make decisions based on expertise and intent to create a great event. A list of teams can be found here: [[teams]]. A team fulfills one or more roles and consists of many team members.
* '''Team member''': Somebody that is actively doing stuff for a team.
* '''First Contacts''': How a team is organized internally, what communication structure they choose, and how they meet is theirs to decide. To lower the barrier for new volunteers, teams share several contact details such as a first-line contact. A team has one or more first-line contacts.
* '''Angel''': Angels are on-event volunteers that perform mostly designed tasks. They do not need to be fully invested in what a team does or how the organization works. An angel usually works in a predefined timeslot (called a shift). A team can have a need for many angels.
* '''Wiki''': The wiki is the central information repository for organizing '''WHY2025'''. The wiki can be reached at '''[http://wiki.why2025.org https://wiki.why2025.org]'''. You'll find a volunteering section as well as many pages aimed at visiting.
* '''Projectleiding''': A team that tracks the health and progress of the entire organization. One team member from the projectleiding (PL) team is connected to every other team to assist the team with navigating the organization, bootstrapping, legal, financial. As the organization matures, the activities of PL dwindle. PL does not determine the color of the bikeshed, '''WHY2025''' is organized team first.
* '''Orga''': a simplification that points to the group of people that organizes this event: all angels and/or team members.

== How to join the crew ==

If you want to join a specific [[teams|team]], you can just talk to the people who are already on the team. For many teams, there will be a listed email address. Just send a mail, it doesn't have to be a very long one, something like "Hi, I'd like to join this team; how can I help?" is enough. Please note that some teams might already be fully staffed, and are not looking for more volunteers.

Some teams haven't really started yet, and as such, their team page is pretty empty. Don't let that stop you, because these are the teams that need your help the most. If there's no team email address, that means we're looking for someone to "bootstrap" the team into existence. The list of [[Vacancies]] is a good starting point for those who want to take the lead in getting a team up and running. If you are not sure how to start your desired team you can always contact the assigned member from the [[Team:Projectleiding]].

If you want to join the crew, and don't know which team would suit you, then you can talk to someone from the future [[Team:Volunteers]] and they can help you with that. You can email '''volunteers@why2025.org'''. If you don't know what you want to do, feel free to describe what you're good at, so we can find a good match. Or you can join our general orga meetings or any of the [[IRC|IRC channels]] and ask around. Another option is to look at the [[Roles]] page to see which of the responsibilities you find attractive, and then figure out which team does that role.

=== General communication channels ===

If you want to say hi and meet us, there are many opportunities:

* [[IRC]], the old and reliable chat protocol
* [[Mailing lists]], for somewhat more structured communication
* [[Meetings]], both physical and [[Jitsi|online]

The wiki itself (that is, the website you're looking at now) is also used for communication. Signing up for teams and meetings is done on the wiki, and sometimes there's a discussion about the contents of pages. Please [[Special:CreateAccount|create an account]] to unlock the page editing feature.

=== Team-specific communication channels ===

Go to the [[Teams]] page, and then the team specific page, to find out where the team members reside.

== How many pieces?  ==

The '''WHY2025''' organization is huge and has numerous moving pieces. It's hard to describe everything in detail, especially because we always fail to come up with good definitions. We're constantly figuring things out and we often find that clear boundaries are impossible in a chaotic organization like ours. When you talk to different people, they'll probably have a different idea of how it works. And they're probably both right, because there are so many valid perspectives. But we can come up with some basic explanations that should give some insight into the "structure" of the organization.

There are two kinds of volunteers, and both are vitally important:

; Angels: visitors who, at the event, sign up to do shifts. This can be anything from bartending to driving a luggage shuttle golf cart, helping with preparing the volunteer food, etcetera. Generally, these tasks are prepared by the orga and come with instructions, so you can just start doing them when you arrive on the job. You can even decide to become an angel at the event itself. More on this at [[Angel]]
; Orga: the term "orga" has become really broad, and now includes anyone who is involved with the preparations of the event. If you join the crew long before the event starts, then you're orga.

Within the orga, some people maintain direct contact with [[Team:Projectleiding]]. These so-called "first-line contacts", or "team leads", are responsible for a team's budget and decision making. Every team does one or multiple [[roles]]. A role is a collection of responsibilities. This allows us to think of the organization in a more abstract manner.

== How we work ==

Teams are very autonomous, and it's up to the team to decide how they organize themselves. Because of that, different teams may have very different ways of reaching decisions.

There's another page that goes into this subject in more detail: [[way of working]].

== What we have to offer ==

Volunteering for '''WHY2025''' is an unpaid job. Because of the way our event is designed, we're counting on everyone to help out, and that's why we can have affordable tickets instead of expensive corporate entrance fees. This does indeed mean that crew members still have to buy a ticket to be part of the event. (If you can't afford a ticket, there are options for that, but that's not related to whether you're a volunteer.) All volunteers are part of the crew because they want to be part of this organization, not for any financial gains.

We do our best to take care of our fellow crew members. When joining the orga community, or when signing up for angel shifts, you become very important to us, and we want you to feel welcome. We have a crew area where you can hang out and get some rest. Good food is served exclusively for crew members, including angels who get food vouchers for doing a certain amount of shifts. And of course, we'll also hand out physical tokens of appreciation, such as crew t-shirts.

For orga, there are orga meetings and field days, where we shape the details of the upcoming event. These meetings are equal parts hard work and socializing/networking/partying.

== Other forms of participation ==

Being part of the crew is great, but there are more different ways to participate! [[Villages]] are sub-events organized by visitors themselves. Just to be clear: when we talk about crew and orga, we're talking about the main event, not the village crews. If you want to learn more about the villages and how they organize themselves, have a look at their respective pages.

=== Wiki gardening ===

Are you good with wikis? We always need help structuring the information, correcting spelling and grammar, and making things look nicer with appropriate images and such. If you want to help out with these things, please [[Special:CreateAccount|create an account]] and edit away :)

For example, this page has a lot of text and just two images. It's amazing you made it this far!

</div>

MediaWiki:Common.css

2025-07-18T09:05:31Z

Okarin:

/* READ ME READ ME READ ME */
/* See https://gitlab.com/why2025/team-sysadmin/mediawiki-themes/-/tree/master/vector/why?ref_type=heads */
/* Prefix temporary bugfixes with either `body.theme-why` or `body.theme-why-light` for the dark and light theme respectively */

/* End of intentional gap */

/* Countdown begin */

/* the countdown clock on the front page of the wiki. See common.js for the script. */
#clockdiv{
font-family: Beon;
display: inline-block;
font-weight: 100;
text-align: center;
font-size: 30px;
}

#clockdiv > div{
padding: 10px;
border-radius: 1px;
display: inline-block;
margin-left: 10px;
color: white;
}

#clockdiv > div:nth-child(1) { background: #5234BF;}
#clockdiv > div:nth-child(2) { background: #B03BBF;}
#clockdiv > div:nth-child(3) { background: #F24535;}
#clockdiv > div:nth-child(4) { background: #FFFB96;}

#clockdiv div > span{
box-sizing: content-box;
padding: 15px;
border-radius: 1px;
background: #00000073;
display: inline-block;
min-width:50px;
height:50px;
}

.clocksmalltext{
padding-top: 5px;
font-size: 20px;
color: #000000;
}
/* Countdown end */

/* helps make the frontpage responsive */
.col-wrap * {
box-sizing: border-box;
}

/* Create two equal columns that floats next to each other */
.col-wrap-col-50 {
float: left;
width: 50%;
padding: 10px;
}

/* Clear floats after the columns */
.col-wrap:after {
content: "";
display: table;
clear: both;
}

/* Responsive layout - makes the two columns stack on top of each other instead of next to each other */
@media screen and (max-width: 1200px) {
.col-wrap-col-50 {
width: 100%;
}
}

/* Background colors for thumbs need to go, given the design generator creates transparent pngs. */
.thumbimage {
background-color: transparent !important;
}

/* Fix Page Forms map / location picker */
.leaflet-container .leaflet-overlay-pane svg,
.leaflet-container .leaflet-marker-pane img,
.leaflet-container .leaflet-shadow-pane img,
.leaflet-container .leaflet-tile-pane img,
.leaflet-container img.leaflet-image-layer {
max-width: none !important;
max-height: none !important;
}

@keyframes vibe{
0%{}
2%{
transform: translateX(5px) rotateZ(1deg);
}
4%{transform: translateX(-5px) rotateZ(-0.1deg);}
6%{transform: translateX(3px) rotateZ(0.2deg);}
8%{transform: translateX(-2px) rotateZ(-0.2deg);}
10%{transform: translateX(1px) rotateZ(0.2deg);}
12%{transform: translateX(-5px) rotateZ(-0.2deg);}
14%{transform: translateX(3px) rotateZ(-0.1deg);}
16%{transform: translateX(-5px) rotateZ(-0.2deg);}
18%{transform: translateX(5px) rotateZ(0.2deg);}
20{transform: translateX(-5px) rotateZ(-0.2deg);}
22%{transform: translateX(5px) rotateZ(0.2deg);}
24%{transform: translateX(-3px) rotateZ(-0.2deg);}
26%{transform: translateX(0px) rotateZ(0.0deg);}
100%{}
}

.page-Village_Øl_Telecom h1 span, a[title="Village:Øl Telecom"]{
animation: vibe 1.5s infinite alternate;
display: inline-block;
}

MediaWiki:Common.css

2025-07-18T09:01:54Z

Okarin:

/* READ ME READ ME READ ME */
/* See https://gitlab.com/why2025/team-sysadmin/mediawiki-themes/-/tree/master/vector/why?ref_type=heads */
/* Prefix temporary bugfixes with either `body.theme-why` or `body.theme-why-light` for the dark and light theme respectively */

/* End of intentional gap */

/* Countdown begin */

/* the countdown clock on the front page of the wiki. See common.js for the script. */
#clockdiv{
font-family: Beon;
display: inline-block;
font-weight: 100;
text-align: center;
font-size: 30px;
}

#clockdiv > div{
padding: 10px;
border-radius: 1px;
display: inline-block;
margin-left: 10px;
color: white;
}

#clockdiv > div:nth-child(1) { background: #5234BF;}
#clockdiv > div:nth-child(2) { background: #B03BBF;}
#clockdiv > div:nth-child(3) { background: #F24535;}
#clockdiv > div:nth-child(4) { background: #FFFB96;}

#clockdiv div > span{
padding: 15px;
border-radius: 1px;
background: #00000073;
display: inline-block;
min-width:50px;
height:50px;
}

.clocksmalltext{
padding-top: 5px;
font-size: 20px;
color: #000000;
}
/* Countdown end */

/* helps make the frontpage responsive */
.col-wrap * {
box-sizing: border-box;
}

/* Create two equal columns that floats next to each other */
.col-wrap-col-50 {
float: left;
width: 50%;
padding: 10px;
}

/* Clear floats after the columns */
.col-wrap:after {
content: "";
display: table;
clear: both;
}

/* Responsive layout - makes the two columns stack on top of each other instead of next to each other */
@media screen and (max-width: 1200px) {
.col-wrap-col-50 {
width: 100%;
}
}

/* Background colors for thumbs need to go, given the design generator creates transparent pngs. */
.thumbimage {
background-color: transparent !important;
}

/* Fix Page Forms map / location picker */
.leaflet-container .leaflet-overlay-pane svg,
.leaflet-container .leaflet-marker-pane img,
.leaflet-container .leaflet-shadow-pane img,
.leaflet-container .leaflet-tile-pane img,
.leaflet-container img.leaflet-image-layer {
max-width: none !important;
max-height: none !important;
}

@keyframes vibe{
0%{}
2%{
transform: translateX(5px) rotateZ(1deg);
}
4%{transform: translateX(-5px) rotateZ(-0.1deg);}
6%{transform: translateX(3px) rotateZ(0.2deg);}
8%{transform: translateX(-2px) rotateZ(-0.2deg);}
10%{transform: translateX(1px) rotateZ(0.2deg);}
12%{transform: translateX(-5px) rotateZ(-0.2deg);}
14%{transform: translateX(3px) rotateZ(-0.1deg);}
16%{transform: translateX(-5px) rotateZ(-0.2deg);}
18%{transform: translateX(5px) rotateZ(0.2deg);}
20{transform: translateX(-5px) rotateZ(-0.2deg);}
22%{transform: translateX(5px) rotateZ(0.2deg);}
24%{transform: translateX(-3px) rotateZ(-0.2deg);}
26%{transform: translateX(0px) rotateZ(0.0deg);}
100%{}
}

.page-Village_Øl_Telecom h1 span, a[title="Village:Øl Telecom"]{
animation: vibe 1.5s infinite alternate;
display: inline-block;
}

Welcome

2025-07-18T09:00:54Z

Okarin:

[[File:Wiki banner.png|center|alt=WHAT HACKERS YEAR FOR

8-12th August 2025, The Netherlands|WHY2025 infobanner]]
<br>

The camp is organized [https://angel.why2025.org/ for and by volunteers] from and around all facets of the international hacker community. Knowledge sharing, technological advancement, experimentation, connecting with your hacker peers, and of course hacking are some of the core values of this event. During the camp there are [https://why2025.org/programme hundreds of talks] and activities to participate in.

== The Last Online Orga Meetings ==
<big>The last online organization meeting before WHY is on [https://wiki.why2025.org/Orga_Jitsi_30_July_2025 Wednesday 30th of July 2025] </big>

== Upcoming Sweatshops ==
Come and help us in a real life sweatshops. So if you want to help us out, and help prepare the welcome package and/or the badge for the visitors. Then please come and help us out. Just put your name on the list, so we know you can come. And just know, you do NOT have to in any team, anyone willing to help us during these sweatshops is welcomed.

<big>The Welcome Package Sweatshop: [https://wiki.why2025.org/Welcome_Package_Sweatshop Saturday 26th of July 2025]</big>
<big>The Badge Assembly Sweatshop: [https://wiki.why2025.org/Badge_Assembly_Sweatshop Saturday 2nd of August 2025]</big>

<div class="col-wrap">
<div class="col-wrap-col-50">
{{whybox|title=How to participate|content=
* [[Volunteering_Guide|Volunteering Guide]] – become an Angel! [https://angel.why2025.org/ Sign up HERE]
* [[Self-organized Sessions]] – host your own talk, workshop, hack session, meeting
* [https://ctf.why2025.org Capture the Flag] - solve all the challenges
* [https://tokens.why2025.org Secret Token Game] - join the scavenger hunt for secret tokens
* [[Villages]] – create your home with like-minded people
* [[Projects]] – do your project at the camp
* [https://design.why2025.org Design] – create WHY2025 designs for your village/project
* [https://gitlab.com/why2025 GitLab] – edit ALL the things
* [[Newcomers_Guide|Newcomers Guide]] – New to the event? Don't know where to start? Begin here!
}}
</div>

<div class="col-wrap-col-50">
{{whybox|title=Countdown|content=
<span style="text-align:center; width:100%">
{{countdown}}
</span>
}}
</div>

<div class="col-wrap-col-50">
{{whybox|title=Angel Counter|content=
<span style="text-align:center; width:100%">
{{AngelCounter}}
</span>
}}
</div>

<div class="col-wrap-col-50">
{{whybox|title=General|content=
* [https://maps.why2025.org/ Map] - The entire field, on your screen. Magic.
* [https://why2025.org/programme Program] - schedule of the conference program
* [[Facilities]] – list of facilities at the camp
* [[Tickets]] – everything about tickets
* [[FAQ]] – many questions answered
* [[Code of Conduct]] - rulez on awesomeness
}}
</div>

<div class="col-wrap-col-50">
{{whybox|title=Camping|content=
* [[Location]] – how to get there
* [[Camping]] – general camping info
* [[Shuttle_Service|Shuttle service]] – from the train to the camp
* [[What to bring]] – this might help you packing
}}
</div>

<div class="col-wrap-col-50">
{{whybox|title=Staying informed|content=
* Visit the [https://why2025.org/ website]
* Join the [https://lists.why2025.org/mailman/listinfo/orga mailing list]
* The main IRC-Channel is [ircs://irc.oftc.net/why2025 #why2025] on oftc.

* Follow us on Social Media:
** [[File:Mastodon.svg|25px|link=https://chaos.social/@why2025camp|Mastodon]] - [[File:Bluesky.svg|25px|alt=Bluesky Logo|link=https://bsky.app/profile/why2025.bsky.social|Bluesky]] - [[File:LinkedIn.png|25px|alt=LinkedIn|LinkedIn|link=https://www.linkedin.com/company/why2025/|LinkedIn]]

More: [[Staying informed]]
}}
</div>

<div class="col-wrap-col-50">
{{whybox|title=Visitor initiatives|content=
* [[Carpooling]] - share your car with others
* [[Ticket_Exchange|Ticket Exchange]] - not coming anymore, sell your tickets here
* [[POIDH|Pics or It Didn't Happen]] - sharing is caring, go here to share pics and video
}}
</div>

<div class="col-wrap-col-50">
{{whybox|title=Wiki stats|content=
* Pages: {{NUMBEROFPAGES}}
* Articles: {{NUMBEROFARTICLES}}
* Files: {{NUMBEROFFILES}}
* Edits: {{NUMBEROFEDITS}}
* Users: {{NUMBEROFUSERS}}
}}
</div>
</div>

== About WHY2025 ==
[[File:Map glow.png|thumb| Go to [http://maps.why2025.org maps.why2025.org] for a online version, or [https://wiki.why2025.org/index.php?title=Team:Terrain#Current_State for technical maps]]]
The camp is built by and for volunteers from across all corners of the international hacker community. Every edition brings together over 3,750 hackers from around the world. At its core, the event thrives on knowledge sharing, technological exploration, hands-on experimentation, and forging connections with fellow hackers. And, of course, hacking in all its glorious forms. Throughout the camp, you'll find hundreds of talks, workshops, and activities—each an opportunity to learn, build, break, and rethink the boundaries of technology.

'''WHY2025''' is an international non-profit outdoor hacker camp/conference taking place in the Netherlands in the summer of 2025.

It is the successor of a string of similar events happening every four years:
[https://en.wikipedia.org/wiki/Galactic_Hacker_Party GHP], [https://nl.wikipedia.org/wiki/Hacking_at_the_End_of_the_Universe HEU], [https://nl.wikipedia.org/wiki/Hacking_in_Progress HIP], [https://en.wikipedia.org/wiki/Hackers_at_Large HAL], [https://en.wikipedia.org/wiki/What_the_Hack WTH], [https://en.wikipedia.org/wiki/Hacking_at_Random HAR], [https://en.wikipedia.org/wiki/Observe._Hack._Make. OHM], [https://en.wikipedia.org/wiki/Still_Hacking_Anyway SHA] and [https://en.wikipedia.org/wiki/May_Contain_Hackers MCH].

Similar events are [https://www.emfcamp.org/ EMF] in the UK and [https://en.wikipedia.org/wiki/Chaos_Communication_Camp CCC Camp] in Germany.

__NOTOC__
__NOEDITSECTION__

MediaWiki:Common.css

2025-07-18T08:53:30Z

Okarin:

/* READ ME READ ME READ ME */
/* See https://gitlab.com/why2025/team-sysadmin/mediawiki-themes/-/tree/master/vector/why?ref_type=heads */
/* Prefix temporary bugfixes with either `body.theme-why` or `body.theme-why-light` for the dark and light theme respectively */

/* End of intentional gap */

/* Countdown begin */

/* the countdown clock on the front page of the wiki. See common.js for the script. */
#clockdiv{
font-family: Beon;
display: inline-block;
font-weight: 100;
text-align: center;
font-size: 30px;
}

#clockdiv > div{
padding: 10px;
border-radius: 1px;
display: inline-block;
margin-left: 10px;
color: white;
}

#clockdiv > div:nth-child(1) { background: #5234BF;}
#clockdiv > div:nth-child(2) { background: #B03BBF;}
#clockdiv > div:nth-child(3) { background: #F24535;}
#clockdiv > div:nth-child(4) { background: #FFFB96;}

#clockdiv div > span{
padding: 15px;
border-radius: 1px;
background: #00000073;
display: inline-block;
min-width:50px;
height:50px;
}

.clocksmalltext{
padding-top: 5px;
font-size: 20px;
color: #000000;
}
/* Countdown end */

/* helps make the frontpage responsive */
.col-wrap * {
box-sizing: border-box;
}

/* Create two equal columns that floats next to each other */
.col-wrap-col-50 {
float: left;
width: 50%;
padding: 10px;
}

/* Clear floats after the columns */
.col-wrap:after {
content: "";
display: table;
clear: both;
}

/* Responsive layout - makes the two columns stack on top of each other instead of next to each other */
@media screen and (max-width: 600px) {
.col-wrap-col-50 {
width: 100%;
}
}

/* Background colors for thumbs need to go, given the design generator creates transparent pngs. */
.thumbimage {
background-color: transparent !important;
}

/* Fix Page Forms map / location picker */
.leaflet-container .leaflet-overlay-pane svg,
.leaflet-container .leaflet-marker-pane img,
.leaflet-container .leaflet-shadow-pane img,
.leaflet-container .leaflet-tile-pane img,
.leaflet-container img.leaflet-image-layer {
max-width: none !important;
max-height: none !important;
}

@keyframes vibe{
0%{}
2%{
transform: translateX(5px) rotateZ(1deg);
}
4%{transform: translateX(-5px) rotateZ(-0.1deg);}
6%{transform: translateX(3px) rotateZ(0.2deg);}
8%{transform: translateX(-2px) rotateZ(-0.2deg);}
10%{transform: translateX(1px) rotateZ(0.2deg);}
12%{transform: translateX(-5px) rotateZ(-0.2deg);}
14%{transform: translateX(3px) rotateZ(-0.1deg);}
16%{transform: translateX(-5px) rotateZ(-0.2deg);}
18%{transform: translateX(5px) rotateZ(0.2deg);}
20{transform: translateX(-5px) rotateZ(-0.2deg);}
22%{transform: translateX(5px) rotateZ(0.2deg);}
24%{transform: translateX(-3px) rotateZ(-0.2deg);}
26%{transform: translateX(0px) rotateZ(0.0deg);}
100%{}
}

.page-Village_Øl_Telecom h1 span, a[title="Village:Øl Telecom"]{
animation: vibe 1.5s infinite alternate;
display: inline-block;
}

User:Okarin

2025-07-18T08:47:47Z

Okarin:

{{UserInfo
|EMail=okarin@why2025.org
|IRC=Okarin
|Mastodon=Okarin@hsnl.social
|DECT=OKAB (probably)
|Languages=NL EN ES
|HackerSpace=Hackalot
|NickName={{PAGENAME}}
|Signal=Okarin.42
|Village=Village:̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝
}}
Tickets sold:
{{MqttFeed|why2025/ticketshop/quotas/Event Visitors/paid_orders}}

<div class="col-wrap">
<div class="col-wrap-col-50">test a</div>
<div class="col-wrap-col-50">test b</div>
</div>

Welcome

2025-07-16T22:07:18Z

Okarin:

[[File:Wiki banner.png|center|alt=WHAT HACKERS YEAR FOR

8-12th August 2025, The Netherlands|WHY2025 infobanner]]
<br>
* This wiki has all relevant information for visitors of WHY2025.
* When: 8th to 12th August 2025
* Where: [https://www.openstreetmap.org/?mlat=52.6873&mlon=4.7521#map=16/52.6925/4.7421&layers=P Geestmerambacht, 42km North of Amsterdam]

The camp is organized [https://angel.why2025.org/ for and by volunteers] from and around all facets of the international hacker community. Knowledge sharing, technological advancement, experimentation, connecting with your hacker peers, and of course hacking are some of the core values of this event. During the camp there are [https://why2025.org/programme hundreds of talks] and activities to participate in.

== The Last Online Orga Meetings ==
<big>The last online organization before WHY is on [https://wiki.why2025.org/Orga_Jitsi_30_July_2025 Wednesday 30th of July 2025] </big>

== Upcoming Sweatshops ==
Come and help us in a real life sweatshops. So if you want to help us out, and help prepare the welcome package and/or the badge for the visitors. Then please come and help us out. Just put your name on the list, so we know you can come. And just know, you do NOT have to in any team, anyone willing to help us during these sweatshops is welcomed.

<big>The Welcome Package Sweatshop: [https://wiki.why2025.org/Welcome_Package_Sweatshop Saturday 26th of July 2025]</big>
<big>The Badge Assembly Sweatshop: [https://wiki.why2025.org/Badge_Assembly_Sweatshop Saturday 2nd of August 2025]</big>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%">
{{whybox|title=How to participate|content=
* [[Volunteering_Guide|Volunteering Guide]] – become an Angel! [https://angel.why2025.org/ Sign up HERE]
* [[Self-organized Sessions]] – host your own talk, workshop, hack session, meeting
* [https://ctf.why2025.org Capture the Flag] - solve all the challenges
* [https://tokens.why2025.org Secret Token Game] - join the scavage hunt for secret tokens
* [[Villages]] – create your home with like-minded people
* [[Projects]] – do your project at the camp
* [https://design.why2025.org Design] – create WHY2025 designs for your village/project
* [https://gitlab.com/why2025 GitLab] – edit ALL the things
* [[Newcomers_Guide|Newcomers Guide]] – New to the event? Don't know where to start? Begin here!
}}
</td>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=Countdown|content=
<span style="text-align:center; width:100%">
{{countdown}}
</span>
}}
</td>
</tr>
<tr>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=General|content=
* [https://maps.why2025.org/ Map] - The entire field, on your screen. Magic.
* [https://why2025.org/programme Program] - schedule of the conference program
* [[Facilities]] – list of facilities at the camp
* [[Tickets]] – everything about tickets
* [[FAQ]] – many questions answered
* [[Code of Conduct]] - rulez on awesomeness

=== Visitor initiatives ===
* [[Carpooling]] - share your car with others
* [[Ticket_Exchange|Ticket Exchange]] - not coming anymore, sell your tickets here
* [[POIDH|Pics or It Didn't Happen]] - sharing is caring, go here to share pics and video
}}

</td>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=Angel Counter|content=
<span style="text-align:center; width:100%">
{{AngelCounter}}
</span>
}}
</td>
</tr>
</table>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%">
{{whybox|title=Camping|content=
* [[Location]] – how to get there
* [[Camping]] – general camping info
* [[Shuttle_Service|Shuttle service]] – from the train to the camp
* [[What to bring]] – this might help you packing
}}

{{whybox|title=Staying informed|content=
* Visit the [https://why2025.org/ website]
* Join the [https://lists.why2025.org/mailman/listinfo/orga mailing list]
* The main IRC-Channel is [ircs://irc.oftc.net/why2025 #why2025] on oftc.

* Follow us on Social Media:
** [[File:Mastodon.svg|25px|link=https://chaos.social/@why2025camp|Mastodon]] - [[File:Bluesky.svg|25px|alt=Bluesky Logo|link=https://bsky.app/profile/why2025.bsky.social|Bluesky]] - [[File:LinkedIn.png|25px|alt=LinkedIn|LinkedIn|link=https://www.linkedin.com/company/why2025/|LinkedIn]]

More: [[Staying informed]]
}}

</td>
</tr>
</table>



<table style="width:100%;">
</table>

== About WHY2025 ==
[[File:Map glow.png|thumb| Go to [http://maps.why2025.org maps.why2025.org] for a online version, or [https://wiki.why2025.org/index.php?title=Team:Terrain#Current_State for technical maps]]]
The camp is built by and for volunteers from across all corners of the international hacker community. Every edition brings together over 3,750 hackers from around the world. At its core, the event thrives on knowledge sharing, technological exploration, hands-on experimentation, and forging connections with fellow hackers. And, of course, hacking in all its glorious forms. Throughout the camp, you'll find hundreds of talks, workshops, and activities—each an opportunity to learn, build, break, and rethink the boundaries of technology.

'''WHY2025''' is an international non-profit outdoor hacker camp/conference taking place in the Netherlands in the summer of 2025.

It is the successor of a string of similar events happening every four years:
[https://en.wikipedia.org/wiki/Galactic_Hacker_Party GHP], [https://nl.wikipedia.org/wiki/Hacking_at_the_End_of_the_Universe HEU], [https://nl.wikipedia.org/wiki/Hacking_in_Progress HIP], [https://en.wikipedia.org/wiki/Hackers_at_Large HAL], [https://en.wikipedia.org/wiki/What_the_Hack WTH], [https://en.wikipedia.org/wiki/Hacking_at_Random HAR], [https://en.wikipedia.org/wiki/Observe._Hack._Make. OHM], [https://en.wikipedia.org/wiki/Still_Hacking_Anyway SHA] and [https://en.wikipedia.org/wiki/May_Contain_Hackers MCH].

Similar events are [https://www.emfcamp.org/ EMF] in the UK and [https://en.wikipedia.org/wiki/Chaos_Communication_Camp CCC Camp] in Germany.

== Wiki stats ==
Pages: {{NUMBEROFPAGES}}, Articles: {{NUMBEROFARTICLES}}, Files: {{NUMBEROFFILES}}, Edits: {{NUMBEROFEDITS}}, Users: {{NUMBEROFUSERS}}

__NOTOC__
__NOEDITSECTION__

Welcome

2025-07-16T22:04:56Z

Okarin:

[[File:Wiki banner.png|center|alt=WHAT HACKERS YEAR FOR

8-12th August 2025, The Netherlands|WHY2025 infobanner]]
<br>
* This wiki has all relevant information for visitors of WHY2025.
* When: 8th to 12th August 2025
* Where: [https://www.openstreetmap.org/?mlat=52.6873&mlon=4.7521#map=16/52.6925/4.7421&layers=P Geestmerambacht, 42km North of Amsterdam]

The camp is organized [https://angel.why2025.org/ for and by volunteers] from and around all facets of the international hacker community. Knowledge sharing, technological advancement, experimentation, connecting with your hacker peers, and of course hacking are some of the core values of this event. During the camp there are [https://why2025.org/programme hundreds of talks] and activities to participate in.

== The Last Online Orga Meetings ==
<big>The last online organization before WHY is on [https://wiki.why2025.org/Orga_Jitsi_30_July_2025 Wednesday 30th of July 2025] </big>

== Upcoming Sweatshops ==
Come and help us in a real life sweatshops. So if you want to help us out, and help prepare the welcome package and/or the badge for the visitors. Then please come and help us out. Just put your name on the list, so we know you can come. And just know, you do NOT have to in any team, anyone willing to help us during these sweatshops is welcomed.

<big>The Welcome Package Sweatshop: [https://wiki.why2025.org/Welcome_Package_Sweatshop Saturday 26th of July 2025]</big>
<big>The Badge Assembly Sweatshop: [https://wiki.why2025.org/Badge_Assembly_Sweatshop Saturday 2nd of August 2025]</big>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%">
{{whybox|title=How to participate|content=
* [[Volunteering_Guide|Volunteering Guide]] – become an Angel! [https://angel.why2025.org/ Sign up HERE]
* [[Self-organized Sessions]] – host your own talk, workshop, hack session, meeting
* [https://ctf.why2025.org Capture the Flag] - solve all the challenges
* [https://tokens.why2025.org Secret Token Game] - join the scavage hunt for secret tokens
* [[Villages]] – create your home with like-minded people
* [[Projects]] – do your project at the camp
* [https://design.why2025.org Design] – create WHY2025 designs for your village/project
* [https://gitlab.com/why2025 GitLab] – edit ALL the things
* [[Newcomers_Guide|Newcomers Guide]] – New to the event? Don't know where to start? Begin here!
}}
</td>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=Countdown|content=
<span style="text-align:center; width:100%">
{{countdown}}
</span>
}}
</td>
</tr>
<tr>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=Angel Counter|content=
<span style="text-align:center; width:100%">
{{AngelCounter}}
</span>
}}
</td>
</td>
</table>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=General|content=
* [https://maps.why2025.org/ Map] - The entire field, on your screen. Magic.
* [https://why2025.org/programme Program] - schedule of the conference program
* [[Facilities]] – list of facilities at the camp
* [[Tickets]] – everything about tickets
* [[FAQ]] – many questions answered
* [[Code of Conduct]] - rulez on awesomeness

=== Visitor initiatives ===
* [[Carpooling]] - share your car with others
* [[Ticket_Exchange|Ticket Exchange]] - not coming anymore, sell your tickets here
* [[POIDH|Pics or It Didn't Happen]] - sharing is caring, go here to share pics and video
}}

</td><td style="vertical-align: top; width:50%">
{{whybox|title=Camping|content=
* [[Location]] – how to get there
* [[Camping]] – general camping info
* [[Shuttle_Service|Shuttle service]] – from the train to the camp
* [[What to bring]] – this might help you packing
}}

{{whybox|title=Staying informed|content=
* Visit the [https://why2025.org/ website]
* Join the [https://lists.why2025.org/mailman/listinfo/orga mailing list]
* The main IRC-Channel is [ircs://irc.oftc.net/why2025 #why2025] on oftc.

* Follow us on Social Media:
** [[File:Mastodon.svg|25px|link=https://chaos.social/@why2025camp|Mastodon]] - [[File:Bluesky.svg|25px|alt=Bluesky Logo|link=https://bsky.app/profile/why2025.bsky.social|Bluesky]] - [[File:LinkedIn.png|25px|alt=LinkedIn|LinkedIn|link=https://www.linkedin.com/company/why2025/|LinkedIn]]

More: [[Staying informed]]
}}

</td>
</tr>
</table>



<table style="width:100%;">
</table>

== About WHY2025 ==
[[File:Map glow.png|thumb| Go to [http://maps.why2025.org maps.why2025.org] for a online version, or [https://wiki.why2025.org/index.php?title=Team:Terrain#Current_State for technical maps]]]
The camp is built by and for volunteers from across all corners of the international hacker community. Every edition brings together over 3,750 hackers from around the world. At its core, the event thrives on knowledge sharing, technological exploration, hands-on experimentation, and forging connections with fellow hackers. And, of course, hacking in all its glorious forms. Throughout the camp, you'll find hundreds of talks, workshops, and activities—each an opportunity to learn, build, break, and rethink the boundaries of technology.

'''WHY2025''' is an international non-profit outdoor hacker camp/conference taking place in the Netherlands in the summer of 2025.

It is the successor of a string of similar events happening every four years:
[https://en.wikipedia.org/wiki/Galactic_Hacker_Party GHP], [https://nl.wikipedia.org/wiki/Hacking_at_the_End_of_the_Universe HEU], [https://nl.wikipedia.org/wiki/Hacking_in_Progress HIP], [https://en.wikipedia.org/wiki/Hackers_at_Large HAL], [https://en.wikipedia.org/wiki/What_the_Hack WTH], [https://en.wikipedia.org/wiki/Hacking_at_Random HAR], [https://en.wikipedia.org/wiki/Observe._Hack._Make. OHM], [https://en.wikipedia.org/wiki/Still_Hacking_Anyway SHA] and [https://en.wikipedia.org/wiki/May_Contain_Hackers MCH].

Similar events are [https://www.emfcamp.org/ EMF] in the UK and [https://en.wikipedia.org/wiki/Chaos_Communication_Camp CCC Camp] in Germany.

== Wiki stats ==
Pages: {{NUMBEROFPAGES}}, Articles: {{NUMBEROFARTICLES}}, Files: {{NUMBEROFFILES}}, Edits: {{NUMBEROFEDITS}}, Users: {{NUMBEROFUSERS}}

__NOTOC__
__NOEDITSECTION__

Welcome

2025-07-16T22:04:06Z

Okarin:

[[File:Wiki banner.png|center|alt=WHAT HACKERS YEAR FOR

8-12th August 2025, The Netherlands|WHY2025 infobanner]]
<br>
* This wiki has all relevant information for visitors of WHY2025.
* When: 8th to 12th August 2025
* Where: [https://www.openstreetmap.org/?mlat=52.6873&mlon=4.7521#map=16/52.6925/4.7421&layers=P Geestmerambacht, 42km North of Amsterdam]

The camp is organized [https://angel.why2025.org/ for and by volunteers] from and around all facets of the international hacker community. Knowledge sharing, technological advancement, experimentation, connecting with your hacker peers, and of course hacking are some of the core values of this event. During the camp there are [https://why2025.org/programme hundreds of talks] and activities to participate in.

== The Last Online Orga Meetings ==
<big>The last online organization before WHY is on [https://wiki.why2025.org/Orga_Jitsi_30_July_2025 Wednesday 30th of July 2025] </big>

== Upcoming Sweatshops ==
Come and help us in a real life sweatshops. So if you want to help us out, and help prepare the welcome package and/or the badge for the visitors. Then please come and help us out. Just put your name on the list, so we know you can come. And just know, you do NOT have to in any team, anyone willing to help us during these sweatshops is welcomed.

<big>The Welcome Package Sweatshop: [https://wiki.why2025.org/Welcome_Package_Sweatshop Saturday 26th of July 2025]</big>
<big>The Badge Assembly Sweatshop: [https://wiki.why2025.org/Badge_Assembly_Sweatshop Saturday 2nd of August 2025]</big>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%">
{{whybox|title=How to participate|content=
* [[Volunteering_Guide|Volunteering Guide]] – become an Angel! [https://angel.why2025.org/ Sign up HERE]
* [[Self-organized Sessions]] – host your own talk, workshop, hack session, meeting
* [https://ctf.why2025.org Capture the Flag] - solve all the challenges
* [https://tokens.why2025.org Secret Token Game] - join the scavage hunt for secret tokens
* [[Villages]] – create your home with like-minded people
* [[Projects]] – do your project at the camp
* [https://design.why2025.org Design] – create WHY2025 designs for your village/project
* [https://gitlab.com/why2025 GitLab] – edit ALL the things
* [[Newcomers_Guide|Newcomers Guide]] – New to the event? Don't know where to start? Begin here!
}}
</td>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=Countdown|content=
<span style="text-align:center; width:100%">
{{countdown}}
</span>
}}
</td>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=Angel Counter|content=
<span style="text-align:center; width:100%">
{{AngelCounter}}
</span>
}}
</td>
</tr>
</table>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=General|content=
* [https://maps.why2025.org/ Map] - The entire field, on your screen. Magic.
* [https://why2025.org/programme Program] - schedule of the conference program
* [[Facilities]] – list of facilities at the camp
* [[Tickets]] – everything about tickets
* [[FAQ]] – many questions answered
* [[Code of Conduct]] - rulez on awesomeness

=== Visitor initiatives ===
* [[Carpooling]] - share your car with others
* [[Ticket_Exchange|Ticket Exchange]] - not coming anymore, sell your tickets here
* [[POIDH|Pics or It Didn't Happen]] - sharing is caring, go here to share pics and video
}}

</td><td style="vertical-align: top; width:50%">
{{whybox|title=Camping|content=
* [[Location]] – how to get there
* [[Camping]] – general camping info
* [[Shuttle_Service|Shuttle service]] – from the train to the camp
* [[What to bring]] – this might help you packing
}}

{{whybox|title=Staying informed|content=
* Visit the [https://why2025.org/ website]
* Join the [https://lists.why2025.org/mailman/listinfo/orga mailing list]
* The main IRC-Channel is [ircs://irc.oftc.net/why2025 #why2025] on oftc.

* Follow us on Social Media:
** [[File:Mastodon.svg|25px|link=https://chaos.social/@why2025camp|Mastodon]] - [[File:Bluesky.svg|25px|alt=Bluesky Logo|link=https://bsky.app/profile/why2025.bsky.social|Bluesky]] - [[File:LinkedIn.png|25px|alt=LinkedIn|LinkedIn|link=https://www.linkedin.com/company/why2025/|LinkedIn]]

More: [[Staying informed]]
}}

</td>
</tr>
</table>



<table style="width:100%;">
</table>

== About WHY2025 ==
[[File:Map glow.png|thumb| Go to [http://maps.why2025.org maps.why2025.org] for a online version, or [https://wiki.why2025.org/index.php?title=Team:Terrain#Current_State for technical maps]]]
The camp is built by and for volunteers from across all corners of the international hacker community. Every edition brings together over 3,750 hackers from around the world. At its core, the event thrives on knowledge sharing, technological exploration, hands-on experimentation, and forging connections with fellow hackers. And, of course, hacking in all its glorious forms. Throughout the camp, you'll find hundreds of talks, workshops, and activities—each an opportunity to learn, build, break, and rethink the boundaries of technology.

'''WHY2025''' is an international non-profit outdoor hacker camp/conference taking place in the Netherlands in the summer of 2025.

It is the successor of a string of similar events happening every four years:
[https://en.wikipedia.org/wiki/Galactic_Hacker_Party GHP], [https://nl.wikipedia.org/wiki/Hacking_at_the_End_of_the_Universe HEU], [https://nl.wikipedia.org/wiki/Hacking_in_Progress HIP], [https://en.wikipedia.org/wiki/Hackers_at_Large HAL], [https://en.wikipedia.org/wiki/What_the_Hack WTH], [https://en.wikipedia.org/wiki/Hacking_at_Random HAR], [https://en.wikipedia.org/wiki/Observe._Hack._Make. OHM], [https://en.wikipedia.org/wiki/Still_Hacking_Anyway SHA] and [https://en.wikipedia.org/wiki/May_Contain_Hackers MCH].

Similar events are [https://www.emfcamp.org/ EMF] in the UK and [https://en.wikipedia.org/wiki/Chaos_Communication_Camp CCC Camp] in Germany.

== Wiki stats ==
Pages: {{NUMBEROFPAGES}}, Articles: {{NUMBEROFARTICLES}}, Files: {{NUMBEROFFILES}}, Edits: {{NUMBEROFEDITS}}, Users: {{NUMBEROFUSERS}}

__NOTOC__
__NOEDITSECTION__

Welcome

2025-07-16T22:02:36Z

Okarin:

[[File:Wiki banner.png|center|alt=WHAT HACKERS YEAR FOR

8-12th August 2025, The Netherlands|WHY2025 infobanner]]
<br>
* This wiki has all relevant information for visitors of WHY2025.
* When: 8th to 12th August 2025
* Where: [https://www.openstreetmap.org/?mlat=52.6873&mlon=4.7521#map=16/52.6925/4.7421&layers=P Geestmerambacht, 42km North of Amsterdam]

The camp is organized [https://angel.why2025.org/ for and by volunteers] from and around all facets of the international hacker community. Knowledge sharing, technological advancement, experimentation, connecting with your hacker peers, and of course hacking are some of the core values of this event. During the camp there are [https://why2025.org/programme hundreds of talks] and activities to participate in.

== The Last Online Orga Meetings ==
<big>The last online organization before WHY is on [https://wiki.why2025.org/Orga_Jitsi_30_July_2025 Wednesday 30th of July 2025] </big>

== Upcoming Sweatshops ==
Come and help us in a real life sweatshops. So if you want to help us out, and help prepare the welcome package and/or the badge for the visitors. Then please come and help us out. Just put your name on the list, so we know you can come. And just know, you do NOT have to in any team, anyone willing to help us during these sweatshops is welcomed.

<big>The Welcome Package Sweatshop: [https://wiki.why2025.org/Welcome_Package_Sweatshop Saturday 26th of July 2025]</big>
<big>The Badge Assembly Sweatshop: [https://wiki.why2025.org/Badge_Assembly_Sweatshop Saturday 2nd of August 2025]</big>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%">
{{whybox|title=How to participate|content=
* [[Volunteering_Guide|Volunteering Guide]] – become an Angel! [https://angel.why2025.org/ Sign up HERE]
* [[Self-organized Sessions]] – host your own talk, workshop, hack session, meeting
* [https://ctf.why2025.org Capture the Flag] - solve all the challenges
* [https://tokens.why2025.org Secret Token Game] - join the scavage hunt for secret tokens
* [[Villages]] – create your home with like-minded people
* [[Projects]] – do your project at the camp
* [https://design.why2025.org Design] – create WHY2025 designs for your village/project
* [https://gitlab.com/why2025 GitLab] – edit ALL the things
* [[Newcomers_Guide|Newcomers Guide]] – New to the event? Don't know where to start? Begin here!
}}
</td>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=Countdown|content=
<span style="text-align:center; width:100%">
{{countdown}}
{{AngelCounter}}
</span>
}}
</td>
</tr>
</table>

<table style="width: 100%">
<tr>
<td style="vertical-align: top; width:50%; padding-right:10px;">
{{whybox|title=General|content=
* [https://maps.why2025.org/ Map] - The entire field, on your screen. Magic.
* [https://why2025.org/programme Program] - schedule of the conference program
* [[Facilities]] – list of facilities at the camp
* [[Tickets]] – everything about tickets
* [[FAQ]] – many questions answered
* [[Code of Conduct]] - rulez on awesomeness

=== Visitor initiatives ===
* [[Carpooling]] - share your car with others
* [[Ticket_Exchange|Ticket Exchange]] - not coming anymore, sell your tickets here
* [[POIDH|Pics or It Didn't Happen]] - sharing is caring, go here to share pics and video
}}

</td><td style="vertical-align: top; width:50%">
{{whybox|title=Camping|content=
* [[Location]] – how to get there
* [[Camping]] – general camping info
* [[Shuttle_Service|Shuttle service]] – from the train to the camp
* [[What to bring]] – this might help you packing
}}

{{whybox|title=Staying informed|content=
* Visit the [https://why2025.org/ website]
* Join the [https://lists.why2025.org/mailman/listinfo/orga mailing list]
* The main IRC-Channel is [ircs://irc.oftc.net/why2025 #why2025] on oftc.

* Follow us on Social Media:
** [[File:Mastodon.svg|25px|link=https://chaos.social/@why2025camp|Mastodon]] - [[File:Bluesky.svg|25px|alt=Bluesky Logo|link=https://bsky.app/profile/why2025.bsky.social|Bluesky]] - [[File:LinkedIn.png|25px|alt=LinkedIn|LinkedIn|link=https://www.linkedin.com/company/why2025/|LinkedIn]]

More: [[Staying informed]]
}}

</td>
</tr>
</table>



<table style="width:100%;">
</table>

== About WHY2025 ==
[[File:Map glow.png|thumb| Go to [http://maps.why2025.org maps.why2025.org] for a online version, or [https://wiki.why2025.org/index.php?title=Team:Terrain#Current_State for technical maps]]]
The camp is built by and for volunteers from across all corners of the international hacker community. Every edition brings together over 3,750 hackers from around the world. At its core, the event thrives on knowledge sharing, technological exploration, hands-on experimentation, and forging connections with fellow hackers. And, of course, hacking in all its glorious forms. Throughout the camp, you'll find hundreds of talks, workshops, and activities—each an opportunity to learn, build, break, and rethink the boundaries of technology.

'''WHY2025''' is an international non-profit outdoor hacker camp/conference taking place in the Netherlands in the summer of 2025.

It is the successor of a string of similar events happening every four years:
[https://en.wikipedia.org/wiki/Galactic_Hacker_Party GHP], [https://nl.wikipedia.org/wiki/Hacking_at_the_End_of_the_Universe HEU], [https://nl.wikipedia.org/wiki/Hacking_in_Progress HIP], [https://en.wikipedia.org/wiki/Hackers_at_Large HAL], [https://en.wikipedia.org/wiki/What_the_Hack WTH], [https://en.wikipedia.org/wiki/Hacking_at_Random HAR], [https://en.wikipedia.org/wiki/Observe._Hack._Make. OHM], [https://en.wikipedia.org/wiki/Still_Hacking_Anyway SHA] and [https://en.wikipedia.org/wiki/May_Contain_Hackers MCH].

Similar events are [https://www.emfcamp.org/ EMF] in the UK and [https://en.wikipedia.org/wiki/Chaos_Communication_Camp CCC Camp] in Germany.

== Wiki stats ==
Pages: {{NUMBEROFPAGES}}, Articles: {{NUMBEROFARTICLES}}, Files: {{NUMBEROFFILES}}, Edits: {{NUMBEROFEDITS}}, Users: {{NUMBEROFUSERS}}

__NOTOC__
__NOEDITSECTION__

Template:AngelCounter

2025-07-16T21:53:42Z

Okarin:

[https://angel.why2025.org/ <div id="clockdiv"><div><span class="sold">{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}</span><div class="clocksmalltext">Registered</div></div><div><span class="available">{{MqttFeed|why2025/angel/users|why2025/angel/users|json|2.value}}</span><div class="clocksmalltext">Arrived</div></div></div>]

Template:AngelCounter

2025-07-16T21:52:59Z

Okarin:

[https://tickets.why2025.org/ <div id="clockdiv"><div><span class="sold">{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}</span><div class="clocksmalltext">Sold</div></div><div><span class="available">{{MqttFeed|why2025/angel/users|why2025/angel/users|json|2.value}}</span><div class="clocksmalltext">Available</div></div></div>]

Template:AngelCounter

2025-07-16T21:51:45Z

Okarin:

[https://wiki.why2025.org/ <div id="clockdiv"> <div>
<span class="registered">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}
</span>
<div class="clocksmalltext">
Registered
</div>
</div>
<div>
<span class="available">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|2.value}}
</span>
<div class="clocksmalltext">
Arrived
</div>
</div>
</div>]

Template:AngelCounter

2025-07-16T21:51:13Z

Okarin:

[https://wiki.why2025.org/ <div id="clockdiv">
<div>
<span class="registered">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}
</span>
<div class="clocksmalltext">
Registered
</div>
</div>
<div>
<span class="available">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|2.value}}
</span>
<div class="clocksmalltext">
Arrived
</div>
</div>
</div>]

Template:AngelCounter

2025-07-16T21:50:48Z

Okarin:

<div id="clockdiv">
<div>
<span class="registered">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}
</span>
<div class="clocksmalltext">
Registered
</div>
</div>
<div>
<span class="available">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|2.value}}
</span>
<div class="clocksmalltext">
Arrived
</div>
</div>
</div>

Template:AngelCounter

2025-07-16T21:48:10Z

Okarin:

<div id="clockdiv">
<div>
<span class="registered">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}
</span>
<div class="clocksmalltext">
Registered
</div>
</div>
<div>
<span class="arrived">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|2.value}}
</span>
<div class="clocksmalltext">
Arrived
</div>
</div>
</div>

Template:AngelCounter

2025-07-16T21:46:11Z

Okarin:

<div id="angeldiv">
<div>
<span class="registered">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}
</span>
<div class="clocksmalltext">
Registered
</div>
</div>
<div>
<span class="arrived">
{{MqttFeed|why2025/angel/users|why2025/angel/users|json|2.value}}
</span>
<div class="clocksmalltext">
Arrived
</div>
</div>
</div>

MediaWiki:Common.js

2025-07-16T21:36:12Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
var elementParamsArr = elementParams.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value']);
console.log(elementParamsArr);

for (elementParam in elementParamsArr) {
console.log(displayObj);
console.log(elementParamsArr[elementParam]);
displayObj = displayObj[elementParamsArr[elementParam]];
}

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:35:25Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
var elementParamsArr = elementParams.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value']);
console.log(elementParamsArr);

for (elementParam in elementParamsArr) {
console.log(displayObj);
console.log(elementParam);
displayObj = displayObj[elementParam];
}

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:33:50Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
var elementParamsArr = elementParams.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value']);

for (elementParam in elementParamsArr) {
console.log(displayObj);
console.log(elementParam);
displayObj = displayObj[elementParam];
}

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

Template:AngelCounter

2025-07-16T21:32:54Z

Okarin:

[https://tickets.why2025.org/ <div id="clockdiv"><div><span class="sold">{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0.value}}</span><div class="clocksmalltext">Sold</div></div><div><span class="available">{{MqttFeed|why2025/ticketshop/quotas/Event Visitors/available_number}}</span><div class="clocksmalltext">Available</div></div></div>]

MediaWiki:Common.js

2025-07-16T21:32:27Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
var elementParamsArr = elementParams.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value']);

for (elementParam in elementParamsArr) {
displayObj = displayObj[elementParam];
}

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:31:45Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:29:44Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
let elementParamsArr = elementParams.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value']);

for (elementParam in elementParamsArr) {
displayObj = displayObj[elementParam];
}
console.log(displayObj);

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:27:28Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
let paramarray = elementParam.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value']);
console.log(displayObj);

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:26:29Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
let paramarray = elementParam.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value']);
for (elementParam in elementParams) {
displayObj = displayObj[elementParam];
}
console.log(displayObj);

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:25:33Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParams = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
let paramarray = elementParam.split(".");
var displayObj = JSON.parse(feedelements[x].attributes['data-value'])
for (elementParam in elementParams) {
displayObj = displayObj[elementParam];
}
console.log(displayObj);

finalValue = displayObj;
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

MediaWiki:Common.js

2025-07-16T21:11:39Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParam = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
console.log(JSON.parse(feedelements[x].attributes['data-value']));
finalValue = JSON.parse(feedelements[x].attributes['data-value'])[elementParam];
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

Template:AngelCounter

2025-07-16T21:10:23Z

Okarin:

[https://tickets.why2025.org/ <div id="clockdiv"><div><span class="sold">{{MqttFeed|why2025/angel/users|why2025/angel/users|json|0}}</span><div class="clocksmalltext">Sold</div></div><div><span class="available">{{MqttFeed|why2025/ticketshop/quotas/Event Visitors/available_number}}</span><div class="clocksmalltext">Available</div></div></div>]

Template:MqttFeed

2025-07-16T21:08:45Z

Okarin:

<span class="mqttfeed" data-topic="{{{1}}}" data-topic2="{{{2|}}}" data-operation="{{{3|}}}" data-param="{{{4|}}}">Loading...</span>

Template:AngelCounter

2025-07-16T21:06:54Z

Okarin:

[https://tickets.why2025.org/ <div id="clockdiv"><div><span class="sold">{{MqttFeed|why2025/angel/users|json|0}}</span><div class="clocksmalltext">Sold</div></div><div><span class="available">{{MqttFeed|why2025/ticketshop/quotas/Event Visitors/available_number}}</span><div class="clocksmalltext">Available</div></div></div>]

MediaWiki:Common.js

2025-07-16T21:04:15Z

Okarin:

/* Any JavaScript here will be loaded for all users on every page load. */
function getTimeRemaining(endtime) {
var t = Date.parse(endtime) - Date.parse(new Date());
var seconds = Math.floor((t / 1000) % 60);
var minutes = Math.floor((t / 1000 / 60) % 60);
var hours = Math.floor((t / (1000 * 60 * 60)) % 24);
var days = Math.floor(t / (1000 * 60 * 60 * 24));
return {
'total': t,
'days': days,
'hours': hours,
'minutes': minutes,
'seconds': seconds
};
}

function initializeClock(id, endtime) {
var clock = document.getElementById(id);
var daysSpan = clock.querySelector('.days');
var hoursSpan = clock.querySelector('.hours');
var minutesSpan = clock.querySelector('.minutes');
var secondsSpan = clock.querySelector('.seconds');

function updateClock() {
var t = getTimeRemaining(endtime);

daysSpan.innerHTML = t.days;
hoursSpan.innerHTML = ('0' + t.hours).slice(-2);
minutesSpan.innerHTML = ('0' + t.minutes).slice(-2);
secondsSpan.innerHTML = ('0' + t.seconds).slice(-2);

if (t.total <= 0) {
clearInterval(timeinterval);
}
}

updateClock();
var timeinterval = setInterval(updateClock, 1000);
}

/* only run this on the page that there is a clock div... */
// Or just a plain access for comparison
// (no need to check exists first, it falls back to null)

$(function () {
if (mw.config.get('wgPageName') === 'Template:Countdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var deadline = new Date(2025, 07, 8, 13, 37, 42, 0); /* base 0 months */
initializeClock('clockdiv', deadline);
}

if (mw.config.get('wgPageName') === 'Template:BuildupCountdown' || mw.config.get('wgPageName') === 'Welcome' ) {
var buildupdeadline = new Date(2025, 07, 1, 0, 0, 0, 0); /* base 0 months */
initializeClock('buildupclockdiv', buildupdeadline);
}
});

var mqttinitstarted = false;
var mqttClient = null;
function initMqtt() {
if(typeof mqtt == "undefined" && !mqttinitstarted) {
mqttinitstarted = true;
(function(d, script) {
script = d.createElement('script');
script.type = 'text/javascript';
script.async = true;
script.onload = initMqttStep2;
script.src = 'https://unpkg.com/mqtt@5.10.3/dist/mqtt.min.js';
d.getElementsByTagName('head')[0].appendChild(script);
}(document));
}
}

function initMqttStep2(callback) {
const url = 'wss://mqtt.why2025.org/'

const options = {
// Clean session
clean: true,
connectTimeout: 4000,
// Authentication
clientId: 'whywiki_' + Math.floor(Math.random() * 9999999),
}

mqttClient = mqtt.connect(url, options);
mqttClient.on('connect', function () {
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
mqttClient.subscribe(elementtopic);
console.log("MQTT sub on:" + elementtopic);
if(feedelements[x].attributes['data-topic2'] && feedelements[x].attributes['data-topic2'].value) {
var elementtopic2 = feedelements[x].attributes['data-topic2'].value;
mqttClient.subscribe(elementtopic2);
console.log("MQTT sub on:" + elementtopic2);
}
}

// Receive messages
mqttClient.on('message', function (topic, message) {
// message is Buffer
console.log("MQTT msg:"+message.toString())
var feedelements = document.getElementsByClassName("mqttfeed");
for(x = 0; x < feedelements.length; x++) {
var elementtopic = feedelements[x].attributes['data-topic'].value;
var elementtopic2 = feedelements[x].attributes['data-topic2'] ? feedelements[x].attributes['data-topic2'].value : "null";
var elementOperation = feedelements[x].attributes['data-operation'] ? feedelements[x].attributes['data-operation'].value : "none";
var elementParam = feedelements[x].attributes['data-param'] ? feedelements[x].attributes['data-param'].value : "none";

if(elementtopic == topic) {
feedelements[x].attributes['data-value'] = message.toString();
}
if(elementtopic2 == topic) {
feedelements[x].attributes['data-value2'] = message.toString();
}
if(elementtopic == topic || elementtopic2 == topic) {
var finalValue = "";
switch(elementOperation) {
case "json":
finalValue = JSON.parse(feedelements[x].attributes['data-value'])[elementParam];
break;
case "sum":
finalValue = feedelements[x].attributes['data-value']*1 + feedelements[x].attributes['data-value2']*1;
break;
case "sub":
finalValue = feedelements[x].attributes['data-value']*1 - feedelements[x].attributes['data-value2']*1;
break;
case "mul":
finalValue = feedelements[x].attributes['data-value']*1 * feedelements[x].attributes['data-value2']*1;
break;
case "div":
finalValue = feedelements[x].attributes['data-value']*1 / feedelements[x].attributes['data-value2']*1;
break;
default:
finalValue = feedelements[x].attributes['data-value'];
}
feedelements[x].innerText = finalValue;
}
}
});
});
}

// Only make a MQTT connection for pages that use it.
if (document.getElementsByClassName("mqttfeed").length > 0) {
initMqtt();
}

Template:AngelCounter

2025-07-16T20:46:37Z

Okarin: Created page with "[https://tickets.why2025.org/ <div id="clockdiv"><div><span class="sold">{{MqttFeed|why2025/angel/users|json}}</span><div class="clocksmalltext">Sold</div></div><div><span class="available">{{MqttFeed|why2025/ticketshop/quotas/Event Visitors/available_number}}</span><div class="clocksmalltext">Available</div></div></div>]"

[https://tickets.why2025.org/ <div id="clockdiv"><div><span class="sold">{{MqttFeed|why2025/angel/users|json}}</span><div class="clocksmalltext">Sold</div></div><div><span class="available">{{MqttFeed|why2025/ticketshop/quotas/Event Visitors/available_number}}</span><div class="clocksmalltext">Available</div></div></div>]

Angel Shirts

2025-07-16T09:27:43Z

Okarin: Created page with "<p style="margin-bottom: 15px;"><span style="border:5px solid #ff9900; padding: 5px;">This page is part of Team:Volunteers</span></p> As a thank you for volunteering we offer a t-shirt after completing a couple of shifts. Team:Volunteers == Size Distribution == File:Size_distribution.png == Design == == Status == Being ordered"

<p style="margin-bottom: 15px;"><span style="border:5px solid #ff9900; padding: 5px;">This page is part of [[Team:Volunteers]]</span></p>

As a thank you for volunteering we offer a t-shirt after completing a couple of shifts.

[[Team:Volunteers]]

== Size Distribution ==
[[File:Size_distribution.png]]

== Design ==

== Status ==
Being ordered

File:Size distribution.png

2025-07-16T09:27:01Z

Okarin: The size distribution for angel shirts

== Summary ==
The size distribution for angel shirts

Safety Vests

2025-07-16T09:25:21Z

Okarin:

<p style="margin-bottom: 15px;"><span style="border:5px solid #ff9900; padding: 5px;">This page is part of [[Team:Volunteers]]</span></p>

We need safety vests for all people on the field during buildup and teardown.

[[Team:Volunteers]]

== Requirements ==
If you bring your own safety clothing please make sure it has the following properties:
* At least 0,14m² of fluorescent material
* At least 1 horizontal retro reflective stripe
* Retro reflective stripes over the shoulders

== Size Distribution ==
[[file:Vest_distribution_why2025_final.png]]

== Design ==
[[File:Safety-vest-why2025.png]]

== Status ==
Vests are currently in transport.

File:Safety-vest-why2025.png

2025-07-16T09:24:33Z

Okarin: A mockup of the safety vest worn at WHY2025 during buildup and teardown.

== Summary ==
A mockup of the safety vest worn at WHY2025 during buildup and teardown.

Angel Guide

2025-07-10T23:24:43Z

Okarin:

[[File:Volunteers needed.png|frameless|right|Volunteers requested :-)]]

[[File:WikiBanner angel guide.png|left]]

<div style="max-width: 800px">
== Introduction ==

Hello angel,

Thank you for being part of the WHY2025 Community and taking the time to read up on how to participate!

This guide tries to convey basic information about volunteering at WHY2025.

If you feel this guide is incomplete, please contact the authors at [mailto:volunteers@why2025.org volunteers@why2025.org].

== Quick start ==

Step 1: Create an [https://angel.why2025.org/ Engelsystem] account

Step 2: Arrive at WHY2025 (in Geestmerambacht)

Step 3: Go to [[Heaven]] and report to the welcome desk

- Get marked as arrived in the Engelsystem

- Get your angel badge

Step 4: Log in to your [https://angel.why2025.org/ Engelsystem] account, read the shift descriptions and register for a shift.

Step 5: Go to the meeting point before the start of your shift, meet your teammates and have fun!

If you have any questions, ask the welcome angels or the shift coordinators behind the front desk in Heaven.

== What is an angel and what do they do? ==

Every visitor that contributes their time to WHY2025 by working one or more shifts is called an angel. During the camp we need hundreds of angels to work thousands of shifts. Angels build up the camp, check tickets, help park cars, pour drinks, organise talks, make video streams and keep us all safe and healthy.

Please join in and make WHY2025 excellent!

=== Perks ===

Being an angel comes with some perks. While we hope that participation is reward enough, here is a list of things that are exclusive to angels:

* Community acknowledgement
* Making it easy to meet fellow hackers
* Hanging out in Heaven
* Fantastic vegan and vegetarian meals
** during your shift you will receive a voucher for a meal
** information on allergens will be made available on the wiki
* A refillable water bottle
* Free coffee, tea and water available in Heaven

If you have contributed a certain amount of time, you may receive access to:

* The famous limited™ angel T-shirt in WHY2025 design

Of course all perks are provided on a “best effort” basis. In particular, the meals are intended for angels who also worked on the day in question and were therefore unable to eat elsewhere.

=== Expectations ===

Volunteering at WHY2025 also comes with some simple, but important expectations of you:

* Be on time for your shift or give Heaven early notice
* Be well rested, sober and not hungry
* Be open-minded and friendly in attitude
* Follow the camps moral values:
** Be excellent to each other
** Check the code of conduct

=== Get Help/Protect Yourself ===

If you don’t feel safe in a shift, please contact Heaven or, if urgent, the security. Your own safety comes before protecting others, especially as an angel.

If you have the feeling that a fellow angel shouldn’t do a shift (e.g. when angel is intoxicated, extremely tired, under the influence of drugs, aggressive or a lone child without a guardian) please contact Heaven and they will have a look and send a replacement if necessary.

== What is Heaven? ==

Heaven is the home of all angels. It is the place where you will always receive help and have your questions answered as you begin your angel career for the current event.

Within Heaven, you will find some of the benefits of being an angel, such as food and drinks. But there is also work to be done in Heaven. There is a helpdesk that manages all active angels. A group of so-called standby angels are waiting for tasks that spontaneously arise. And some angels are working in the kitchen and washing the dishes.

Heaven is also the best place to call, if you have any problems with your shift.

== The Engelsystem ==

The Engelsystem is the central place to distribute the work to all the helping angels. It can be a bit overwhelming at the beginning, but you will get used to it and find your way around.

As you might have seen there are many different shifts and roles for angels — some sounding more appealing than others. There are shifts where you need to have some knowledge before you can take them. This knowledge is transferred in introduction meetings or by taking an unrestricted shift in the team and getting trained on the job. You can read about the requirements in the shift description. Introduction meetings are announced in the Engelsystem under the tab “Meetings”.

Some shifts require angels that have certain certifications, experience or training. Regular angels can’t register for these shifts. Details and contacts are listed in the Engelsystem under each shift.

Also restrictions are in place, when angels get access to certain systems with a huge amount of data (e.g. mail-queues with emails from participants) or handling big piles of money.

If you want to know more about an angel type, the description of the angel type usually includes contact data such as a DECT number or an email-address to ask your questions. Alternatively, you can also ask one of the persons of the respective angel type mentioned under “Supporter”.

We asked teams to provide information about accessibility requirements for the shifts in Engelsystem. You will will find it in the description of the shifts.

== What to bring to shifts ==

Participating as an angel works best if you have some equipment with you. While most of the tools needed to complete a task will be provided to you, some items are personal and are best brought by yourself. Think about these items:

* Your angel badge
* Refillable water bottle
* DECT phone (optional, bring [https://eventphone.de/doku/dect_phone_compatibility_list a qualified model] and register it at the POC desk)
* Solid shoes (we are camping after all)
* Appropriate protection if it’s sunny, cold or raining and your shift is outside

If some special item is required (for instance for some shifts you need to bring a laptop or tablet), you’ll find that info in the description of the shift.

== When to arrive? ==

For visitors of the camp, day 0 (August 7th) is considered a good day to arrive. It is the day before the program starts.

On day 0, build up is nearly completed, most infrastructure is set up and the registration desk will already be open, so you can exchange your ticket QR code for a wristband without having to queue for too long.

In addition, the areas are not yet as crowded as during the event, so day 0 is a good opportunity to familiarise yourself with the camp field and have a look around without the fear of missing any interesting talks.

=== Buildup and teardown ===

The camp needs angels for builup and teardown!

If you want to have a more detailed look behind the scenes and are not afraid of all sorts of manual labour like carrying heavy stuff and setting up chairs and tables, you are welcome to arrive earlier (up to day -6, Friday August 1st) and help with buildup. During early buildup there is little infrastructure available.

Please let us know about your arrival date in your Engelsystem registration, and follow messages about buildup on the [https://why2025.org/Blog WHY2025 blog].

You are also more than welcome to help during teardown. Often teardown is less popular then buildup! We will start August 13th and work for a few days until everything is packed up.

Food and drinks will be provided to volunteers working during buildup and teardown.

== Where to get information ==

This is a short list of information sources to get you started.

* The [https://angel.why2025.org/ Engelsystem], which offers news and scheduled angel meetings
* The [[Welcome|WHY2025 wiki]] for instance the [[Angel|Angel page]].
* More questions? Try the [[FAQ|general FAQ]] or the [https://angel.why2025.org/faq Heaven FAQ]
* Lost? Try the [https://map.why2025.org/ map]!
* Go to the Infodesk in the info tent or the front desk in Heaven

Important DECT numbers:

* 110 Security
* 112 CERT
* 113 Awareness Team
* 1023 Heaven
* 1111 Info Desk
* Find more number in the [https://micropoc.de/phonebook POC Phonebook]

</div>

Angel Guide

2025-07-10T23:12:18Z

Okarin: Reverted edits by Okarin (talk) to last revision by Marjolein

[[File:Volunteers needed.png|frameless|right|Volunteers requested :-)]]

[[File:WikiBanner angel guide.png|left]]

<div style="max-width: 800px">
== Introduction ==

Hello angel,

Thank you for being part of the WHY2025 Community and taking the time to read up on how to participate!

This guide tries to convey basic information about volunteering at WHY2025.

If you feel this guide is incomplete, please contact the authors at [mailto:volunteers@why2025.org volunteers@why2025.org].

== Quick start ==

Step 1: Create an [https://angel.why2025.org/ Engelsystem] account

Step 2: Arrive at WHY2025 (in Geestmerambacht)

Step 3: Go to [[Heaven]] and report to the welcome desk

- Get marked as arrived in the Engelsystem

- Get your angel badge

Step 4: Log in to your [https://angel.why2025.org/ Engelsystem] account, read the shift descriptions and register for a shift.

Step 5: Go to the meeting point before the start of your shift, meet your teammates and have fun!

If you have any questions, ask the welcome angels or the shift coordinators behind the front desk in Heaven.

== Where to get information ==

This is a short list of information sources to get you started.

* The [https://angel.why2025.org/ Engelsystem], which offers news and scheduled angel meetings
* The [[Welcome|WHY2025 wiki]] for instance the [[Angel|Angel page]].
* More questions? Try the [[FAQ|general FAQ]] or the [https://angel.why2025.org/faq Heaven FAQ]
* Lost? Try the [https://map.why2025.org/ map]!
* Go to the Infodesk in the info tent or the front desk in Heaven

Important DECT numbers:

* 110 Security
* 112 CERT
* 113 Awareness Team
* 1023 Heaven
* 1111 Info Desk
* Find more number in the [https://micropoc.de/phonebook POC Phonebook]

== What is an angel and what do they do? ==

Every visitor that contributes their time to WHY2025 by working one or more shifts is called an angel. During the camp we need hundreds of angels to work thousands of shifts. Angels build up the camp, check tickets, help park cars, pour drinks, organise talks, make video streams and keep us all safe and healthy.

Please join in and make WHY2025 excellent!

=== Perks ===

Being an angel comes with some perks. While we hope that participation is reward enough, here is a list of things that are exclusive to angels:

* Community acknowledgement
* Making it easy to meet fellow hackers
* Hanging out in Heaven
* Fantastic vegan and vegetarian meals
** during your shift you will receive a voucher for a meal
** information on allergens will be made available on the wiki
* A refillable water bottle
* Free coffee, tea and water available in Heaven

If you have contributed a certain amount of time, you may receive access to:

* The famous limited™ angel T-shirt in WHY2025 design

Of course all perks are provided on a “best effort” basis. In particular, the meals are intended for angels who also worked on the day in question and were therefore unable to eat elsewhere.

=== Expectations ===

Volunteering at WHY2025 also comes with some simple, but important expectations of you:

* Be on time for your shift or give Heaven early notice
* Be well rested, sober and not hungry
* Be open-minded and friendly in attitude
* Follow the camps moral values:
** Be excellent to each other
** Check the code of conduct

=== Get Help/Protect Yourself ===

If you don’t feel safe in a shift, please contact Heaven or, if urgent, the security. Your own safety comes before protecting others, especially as an angel.

If you have the feeling that a fellow angel shouldn’t do a shift (e.g. when angel is intoxicated, extremely tired, under the influence of drugs, aggressive or a lone child without a guardian) please contact Heaven and they will have a look and send a replacement if necessary.

== What is Heaven? ==

Heaven is the home of all angels. It is the place where you will always receive help and have your questions answered as you begin your angel career for the current event.

Within Heaven, you will find some of the benefits of being an angel, such as food and drinks. But there is also work to be done in Heaven. There is a helpdesk that manages all active angels. A group of so-called standby angels are waiting for tasks that spontaneously arise. And some angels are working in the kitchen and washing the dishes.

Heaven is also the best place to call, if you have any problems with your shift.

== The Engelsystem ==

The Engelsystem is the central place to distribute the work to all the helping angels. It can be a bit overwhelming at the beginning, but you will get used to it and find your way around.

As you might have seen there are many different shifts and roles for angels — some sounding more appealing than others. There are shifts where you need to have some knowledge before you can take them. This knowledge is transferred in introduction meetings or by taking an unrestricted shift in the team and getting trained on the job. You can read about the requirements in the shift description. Introduction meetings are announced in the Engelsystem under the tab “Meetings”.

Some shifts require angels that have certain certifications, skills or knowledge. Regular angels can’t register for these shifts. The description of the restricted angel type explains what is needed. When one of the supporters listed in Engelsystem confirms you meet the requirements, you can register for such a shift.

Also restrictions are in place, when angels get access to certain systems with a huge amount of data (e.g. mail-queues with emails from participants) or handling big piles of money.

If you want to know more about an angel type, the description of the angel type usually includes contact data such as a DECT number or an email-address to ask your questions. Alternatively, you can also ask one of the persons of the respective angel type mentioned under “Supporter”.

We asked teams to provide information about accessibility requirements for the shifts in Engelsystem. You will will find it in the description of the shifts.

== What to bring to shifts ==

Participating as an angel works best if you have some equipment with you. While most of the tools needed to complete a task will be provided to you, some items are personal and are best brought by yourself. Think about these items:

* Your angel badge
* Refillable water bottle
* DECT phone (optional, bring [https://eventphone.de/doku/dect_phone_compatibility_list a qualified model] and register it at the POC desk)
* Solid shoes (we are camping after all)
* Appropriate protection if it’s sunny, cold or raining and your shift is outside

If some special item is required (for instance for some shifts you need to bring a laptop or tablet), you’ll find that info in the description of the shift.

== When to arrive? ==

For visitors of the camp, day 0 (August 7th) is considered a good day to arrive. It is the day before the program starts.

On day 0, build up is nearly completed, most infrastructure is set up and the registration desk will already be open, so you can exchange your ticket QR code for a wristband without having to queue for too long.

In addition, the areas are not yet as crowded as during the event, so day 0 is a good opportunity to familiarise yourself with the camp field and have a look around without the fear of missing any interesting talks.

=== Buildup and teardown ===

The camp needs angels for builup and teardown!

If you want to have a more detailed look behind the scenes and are not afraid of all sorts of manual labour like carrying heavy stuff and setting up chairs and tables, you are welcome to arrive earlier (up to day -6, Friday August 1st) and help with buildup. During early buildup there is little infrastructure available.

Please let us know about your arrival date in your Engelsystem registration, and follow messages about buildup on the [https://why2025.org/Blog WHY2025 blog].

You are also more than welcome to help during teardown. Often teardown is less popular then buildup! We will start August 13th and work for a few days until everything is packed up.

Food and drinks will be provided to volunteers working during buildup and teardown.

</div>

Angel Guide

2025-07-10T23:10:58Z

Okarin: Reverted edits by Marjolein (talk) to last revision by Okarin

[[File:Volunteers needed.png|frameless|right|Volunteers requested :-)]]

[[File:WikiBanner angel guide.png|left]]

<div style="max-width: 800px">
== Introduction ==

Hello angel,

Thank you for being part of the WHY2025 Community and taking the time to read up on how to participate!

This guide tries to convey basic information about volunteering at WHY2025.

If you feel this guide is incomplete, please contact the authors at volunteers@why2025.org.

== Quick start ==

Step 1: Create an Engelsystem account

Step 2: Arrive at WHY2025 (in Geestmerambacht)

Step 3: Go to Heaven and report to the welcome desk

- Get marked as arrived in the Engelsystem

- Get your angel badge

Step 4: Log in to your Engelsystem account, read the shift descriptions and register for a shift.

Step 5: Go to the meeting point before the start of your shift, meet your teammates and have fun!

If you have any questions, ask the welcome angels or the shift coordinators behind the front desk in Heaven.

== Where to get information ==

This is a short list of information sources to get you started.

* The Engelsystem, which offers news and scheduled angel meetings
* The WHY2025 wiki, for instance the Angel page.
* More questions? Try the general FAQ or the Heaven FAQ
* Lost? Try the map!
* Go to the Infodesk in the info tent or the front desk in Heaven

Important DECT numbers:

* 110 Security
* 112 CERT
* 113 Awareness Team
* 1023 Heaven
* 1111 Info Desk
* Find more number in the POC Phonebook

== What is an angel and what do they do? ==

Every visitor that contributes their time to WHY2025 by working one or more shifts is called an angel. During the camp we need hundreds of angels to work thousands of shifts. Angels build up the camp, check tickets, help park cars, pour drinks, organise talks, make video streams and keep us all safe and healthy.

Please join in and make WHY2025 excellent!

=== Perks ===

Being an angel comes with some perks. While we hope that participation is reward enough, here is a list of things that are exclusive to angels:

* Community acknowledgement
* Making it easy to meet fellow hackers
* Hanging out in Heaven
* Fantastic vegan and vegetarian meals
** during your shift you will receive a voucher for a meal
** information on allergens will be made available on the wiki
* A refillable water bottle
* Free coffee, tea and water available in Heaven

If you have contributed a certain amount of time, you may receive access to:

* The famous limited™ angel T-shirt in WHY2025 design

Of course all perks are provided on a “best effort” basis. In particular, the meals are intended for angels who also worked on the day in question and were therefore unable to eat elsewhere.

=== Expectations ===

Volunteering at WHY2025 also comes with some simple, but important expectations of you:

* Be on time for your shift or give Heaven early notice
* Be well rested, sober and not hungry
* Be open-minded and friendly in attitude
* Follow the camps moral values:
** Be excellent to each other
** Check the code of conduct

=== Get Help/Protect Yourself ===

If you don’t feel safe in a shift, please contact Heaven or, if urgent, the security. Your own safety comes before protecting others, especially as an angel.

If you have the feeling that a fellow angel shouldn’t do a shift (e.g. when angel is intoxicated, extremely tired, under the influence of drugs, aggressive or a lone child without a guardian) please contact Heaven and they will have a look and send a replacement if necessary.

== What is Heaven? ==

Heaven is the home of all angels. It is the place where you will always receive help and have your questions answered as you begin your angel career for the current event.

Within Heaven, you will find some of the benefits of being an angel, such as food and drinks. But there is also work to be done in Heaven. There is a helpdesk that manages all active angels. A group of so-called standby angels are waiting for tasks that spontaneously arise. And some angels are working in the kitchen and washing the dishes.

Heaven is also the best place to call, if you have any problems with your shift.

== The Engelsystem ==

The Engelsystem is the central place to distribute the work to all the helping angels. It can be a bit overwhelming at the beginning, but you will get used to it and find your way around.

As you might have seen there are many different shifts and roles for angels — some sounding more appealing than others. There are shifts where you need to have some knowledge before you can take them. This knowledge is transferred in introduction meetings or by taking an unrestricted shift in the team and getting trained on the job. You can read about the requirements in the shift description. Introduction meetings are announced in the Engelsystem under the tab “Meetings”.

Some shifts require angels that have certain certifications, skills or knowledge. Regular angels can’t register for these shifts. The description of the restricted angel type explains what is needed. When one of the supporters listed in Engelsystem confirms you meet the requirements, you can register for such a shift.

Also restrictions are in place, when angels get access to certain systems with a huge amount of data (e.g. mail-queues with emails from participants) or handling big piles of money.

If you want to know more about an angel type, the description of the angel type usually includes contact data such as a DECT number or an email-address to ask your questions. Alternatively, you can also ask one of the persons of the respective angel type mentioned under “Supporter”.

We asked teams to provide information about accessibility requirements for the shifts in Engelsystem. You will will find it in the description of the shifts.

== What to bring to shifts ==

Participating as an angel works best if you have some equipment with you. While most of the tools needed to complete a task will be provided to you, some items are personal and are best brought by yourself. Think about these items:

* Your angel badge
* Refillable water bottle
* DECT phone (optional, bring a qualified model and register it at the POC desk)
* Solid shoes (we are camping after all)
* Appropriate protection if it’s sunny, cold or raining and your shift is outside

If some special item is required (for instance for some shifts you need to bring a laptop or tablet), you’ll find that info in the description of the shift.

== When to arrive? ==

For visitors of the camp, day 0 (August 7th) is considered a good day to arrive. It is the day before the program starts.

On day 0, build up is nearly completed, most infrastructure is set up and the registration desk will already be open, so you can exchange your ticket QR code for a wristband without having to queue for too long.

In addition, the areas are not yet as crowded as during the event, so day 0 is a good opportunity to familiarise yourself with the camp field and have a look around without the fear of missing any interesting talks.

=== Buildup and teardown ===

The camp needs angels for builup and teardown!

If you want to have a more detailed look behind the scenes and are not afraid of all sorts of manual labour like carrying heavy stuff and setting up chairs and tables, you are welcome to arrive earlier (up to day -6, Friday August 1st) and help with buildup. Please let us know about your arrival date in your Engelsystem registration. That helps us coordinating the volunteers.

However, please remember there is NO infrastructure yet. So if you would like to help, please follow messages about buildup on the WHY2025 blog or contact Team:Volunteers for more details.

You are also more than welcome to help during teardown. Often teardown is less popular then buildup! We will start August 13th and work for a few days until everything is packed up.

Food and drinks will be provided to volunteers working during buildup and teardown.

</div>

Angel Guide

2025-07-09T21:14:45Z

Okarin: Removed work limit

[[File:Volunteers needed.png|frameless|right|Volunteers requested :-)]]

[[File:WikiBanner angel guide.png|left]]

<div style="max-width: 800px">
== Introduction ==

Hello angel,

Thank you for being part of the WHY2025 Community and taking the time to read up on how to participate!

This guide tries to convey basic information about volunteering at WHY2025.

If you feel this guide is incomplete, please contact the authors at volunteers@why2025.org.

== Quick start ==

Step 1: Create an Engelsystem account

Step 2: Arrive at WHY2025 (in Geestmerambacht)

Step 3: Go to Heaven and report to the welcome desk

- Get marked as arrived in the Engelsystem

- Get your angel badge

Step 4: Log in to your Engelsystem account, read the shift descriptions and register for a shift.

Step 5: Go to the meeting point before the start of your shift, meet your teammates and have fun!

If you have any questions, ask the welcome angels or the shift coordinators behind the front desk in Heaven.

== Where to get information ==

This is a short list of information sources to get you started.

* The Engelsystem, which offers news and scheduled angel meetings
* The WHY2025 wiki, for instance the Angel page.
* More questions? Try the general FAQ or the Heaven FAQ
* Lost? Try the map!
* Go to the Infodesk in the info tent or the front desk in Heaven

Important DECT numbers:

* 110 Security
* 112 CERT
* 113 Awareness Team
* 1023 Heaven
* 1111 Info Desk
* Find more number in the POC Phonebook

== What is an angel and what do they do? ==

Every visitor that contributes their time to WHY2025 by working one or more shifts is called an angel. During the camp we need hundreds of angels to work thousands of shifts. Angels build up the camp, check tickets, help park cars, pour drinks, organise talks, make video streams and keep us all safe and healthy.

Please join in and make WHY2025 excellent!

=== Perks ===

Being an angel comes with some perks. While we hope that participation is reward enough, here is a list of things that are exclusive to angels:

* Community acknowledgement
* Making it easy to meet fellow hackers
* Hanging out in Heaven
* Fantastic vegan and vegetarian meals
** during your shift you will receive a voucher for a meal
** information on allergens will be made available on the wiki
* A refillable water bottle
* Free coffee, tea and water available in Heaven

If you have contributed a certain amount of time, you may receive access to:

* The famous limited™ angel T-shirt in WHY2025 design

Of course all perks are provided on a “best effort” basis. In particular, the meals are intended for angels who also worked on the day in question and were therefore unable to eat elsewhere.

=== Expectations ===

Volunteering at WHY2025 also comes with some simple, but important expectations of you:

* Be on time for your shift or give Heaven early notice
* Be well rested, sober and not hungry
* Be open-minded and friendly in attitude
* Follow the camps moral values:
** Be excellent to each other
** Check the code of conduct

=== Get Help/Protect Yourself ===

If you don’t feel safe in a shift, please contact Heaven or, if urgent, the security. Your own safety comes before protecting others, especially as an angel.

If you have the feeling that a fellow angel shouldn’t do a shift (e.g. when angel is intoxicated, extremely tired, under the influence of drugs, aggressive or a lone child without a guardian) please contact Heaven and they will have a look and send a replacement if necessary.

== What is Heaven? ==

Heaven is the home of all angels. It is the place where you will always receive help and have your questions answered as you begin your angel career for the current event.

Within Heaven, you will find some of the benefits of being an angel, such as food and drinks. But there is also work to be done in Heaven. There is a helpdesk that manages all active angels. A group of so-called standby angels are waiting for tasks that spontaneously arise. And some angels are working in the kitchen and washing the dishes.

Heaven is also the best place to call, if you have any problems with your shift.

== The Engelsystem ==

The Engelsystem is the central place to distribute the work to all the helping angels. It can be a bit overwhelming at the beginning, but you will get used to it and find your way around.

As you might have seen there are many different shifts and roles for angels — some sounding more appealing than others. There are shifts where you need to have some knowledge before you can take them. This knowledge is transferred in introduction meetings or by taking an unrestricted shift in the team and getting trained on the job. You can read about the requirements in the shift description. Introduction meetings are announced in the Engelsystem under the tab “Meetings”.

Some shifts require angels that have certain certifications, skills or knowledge. Regular angels can’t register for these shifts. The description of the restricted angel type explains what is needed. When one of the supporters listed in Engelsystem confirms you meet the requirements, you can register for such a shift.

Also restrictions are in place, when angels get access to certain systems with a huge amount of data (e.g. mail-queues with emails from participants) or handling big piles of money.

If you want to know more about an angel type, the description of the angel type usually includes contact data such as a DECT number or an email-address to ask your questions. Alternatively, you can also ask one of the persons of the respective angel type mentioned under “Supporter”.

We asked teams to provide information about accessibility requirements for the shifts in Engelsystem. You will will find it in the description of the shifts.

== What to bring to shifts ==

Participating as an angel works best if you have some equipment with you. While most of the tools needed to complete a task will be provided to you, some items are personal and are best brought by yourself. Think about these items:

* Your angel badge
* Refillable water bottle
* DECT phone (optional, bring a qualified model and register it at the POC desk)
* Solid shoes (we are camping after all)
* Appropriate protection if it’s sunny, cold or raining and your shift is outside

If some special item is required (for instance for some shifts you need to bring a laptop or tablet), you’ll find that info in the description of the shift.

== When to arrive? ==

For visitors of the camp, day 0 (August 7th) is considered a good day to arrive. It is the day before the program starts.

On day 0, build up is nearly completed, most infrastructure is set up and the registration desk will already be open, so you can exchange your ticket QR code for a wristband without having to queue for too long.

In addition, the areas are not yet as crowded as during the event, so day 0 is a good opportunity to familiarise yourself with the camp field and have a look around without the fear of missing any interesting talks.

=== Buildup and teardown ===

The camp needs angels for builup and teardown!

If you want to have a more detailed look behind the scenes and are not afraid of all sorts of manual labour like carrying heavy stuff and setting up chairs and tables, you are welcome to arrive earlier (up to day -6, Friday August 1st) and help with buildup. Please let us know about your arrival date in your Engelsystem registration. That helps us coordinating the volunteers.

However, please remember there is NO infrastructure yet. So if you would like to help, please follow messages about buildup on the WHY2025 blog or contact Team:Volunteers for more details.

You are also more than welcome to help during teardown. Often teardown is less popular then buildup! We will start August 13th and work for a few days until everything is packed up.

Food and drinks will be provided to volunteers working during buildup and teardown.

</div>

Team:Volunteers

2025-07-08T17:40:51Z

Okarin:

{{Team
|Lead=User:Okarin
|Description=Team:Volunteers is responsible for managing the angels during the Event.
|Exclusive team=Yes
|Contact=volunteers@why2025.org
|IRC=why2025-volunteers
|team_is_essential_to_event=Important
|team_has_contact_info=Yes
|team_has_info_on_wiki=Yes
|team_has_planned_meetings=Yes
|team_has_enough_people=No
|team_needs_x_people=1
|team_has_drafted_budget=No
|team_has_informed_volunteer_team=Yes
|Projectleiding=User:NancyBeers
}}
==Team Members==

{{TeamMemberEntry|User:Okarin}}
{{TeamMemberEntry|User:Xu}}
{{TeamMemberEntry|User:Igel}}
{{TeamMemberEntry|User:Marjolein}}
{{TeamMemberEntry|User:Jasper}}
[[File:Angel-logo.png|thumb|right]]

'''We have vacancies!'''

What would WHY2025 be without angels, all the volunteers that help make camp perfect?

Help us help them so they can have fun helping at camp :)

To make this happen, we need to set up all kind of things, there is fun stuff for everyone.
For instance, we need coordinators during the event. You can help with setting up Heaven, the place where angels can meet. We arrange food and drinks for angels, so we are setting up a complete kitchen and catering. The Engelsystem needs to be ready and filled with shifts so angels can register and select tasks. And much more.

Most importantly we want angels to have a great time helping out all the other teams during camp.
Interested? Need more info? Contact {{UserLink|Okarin}} or sent an email to [mailto:volunteers@why2025.org volunteers@why2025.org]

== Projects ==
* [[Heaven]]
* [[Safety_Vests]]
* [[Angelsystem]]
* [[Angel_Care]]
* [[Water_Bottles]]
* [[Angel_Badges]]
* [[Angel_Shirts]]
* Recruitment
** Landingpage [[Angel]] (How to become an Angel)
** [[Shifts Guidelines]]
** [[Angel_Guide]]
** [[Volunteering_Guide]]
** [[recruitment poster]]

=== Shared Projects ===
* Accessible volunteer shifts: [[Team:Accessibility]]
* Heaven decoration: [[Team:Deco]]
* Angel shifts for minors: [[Team:Family]]

=== Subproject making shifts for Engelsystem ===
* [[Shifts for teams in Engelsystem]]
* [[Buildup Teardown Volunteer Capacity]]

==Meetings==
https://meet.why2025.org/why-volunteers

* 1st Apr 2025 20:00
* 16th Apr 2025 20:00
* 1st May 2025 20:00
* 16st May 2025 20:00
* 2nd Jun 2025 20:00
* 12nd Jun 2025 20:00

Past dates:
* <s>28th Aug 2024 20:00</s>
* <s>25th Sep 2024 20:00</s>
* <s>29th Oct 2024 20:00</s>
* <s>26th Nov 2024 20:00</s>
* <s>25th Dec 2024</s> (cancelled)
* <s>6th Jan 2025 20:00</s>
* <s>21th Jan 2025 20:00</s>
* <s>5th Feb 2025 20:00</s>
* <s>14th Feb 2025 19:00</s>
* <s>20th Feb 2025 20:00</s>
* <s>7th Mar 2025 19:00 (Brainstorm session tasks)</s>
* <s>17th Mar 2025 20:00</s>

==Roles==

===Before the event===
*Indexing orga vacancies
*On-boarding new organization members
*Planning heaven's amenities
*Planning shifts
*Talk to teams about volunteer needs
**Help teams structure their needs in shifts
*Setting up Engelsystem
*Entering shifts in the Engelsystem

===During the event===
*Recruit volunteers
*Optimize on-boarding experience
*Match volunteers to tasks and shifts:
**Provide teams that have things that need doing with people to do it
**Provide people with spare time with things to do
**Try to optimize fun and efficiency by directing people towards tasks that fit their skills
*Schedule volunteers and inform volunteers about what’s expected from them
*Take care of the volunteers
**Provide basic life necessities to volunteers that help out for more than just a few hours, e.g. food and drinks.
**Express gratitude towards volunteers, e.g. by awarding goodies (t-shirts) and good food
*Manage volunteers on site from early build-up to late tear-down
*Schedule volunteer assignments according to priorities indicated by build-up, tear-down, and PL
*Keep a pool of volunteers available for unplanned ad-hoc tasks.
*Manage the Engelsystem

==Design work==
* A [[recruitment poster]] design to recruit more Orga/volunteers (ASAP)
* An angel safety vest design for the [[Safety_Vests]].
* An angel lanyard design for the [[Angel_Badges]].
* An angel t-shirt design for the [[Angel_Shirts]].
* A design to print on the [[Water_Bottles]].

Vacancies

2025-07-08T17:29:00Z

Okarin:

All teams are starting up. That means that they are still preparing for showing their vacancies on this page.

In the mean time: is there anything you would like to do that's not listed here yet? Ask at [ircs://irc.oftc.net/why2025 #why2025 on OFTC]. New to IRC? Use the [https://webchat.oftc.net/?randomnick=1&channels=why2025&prompt=1 web client] or send a mail at volunteers@why2025.org

There are two tables here. One with specific vacancies, and one with teams who need general members.

This info is accurate as of 2024-10-06.

== Open Vacancies ==

{| class="wikitable sortable" style="width: 100%" |
|-
! Team, Role
! Description
|-
| [[Team:Volunteers]], Team members
|
What would WHY2025 be without angels, all the volunteers that help make camp perfect?

Help us help them so they can have fun helping at camp :)

Looking for Angel Kitchen Coordinator.

Interested? Need more info? Contact {{UserLink|Okarin}} or sent an email to [mailto:volunteers@why2025.org volunteers@why2025.org]
|-
| [[Team:Parking]], Parking coordinator support
|
Are you the Dutch-/English-speaking hero who can help out everyone with a car?

Do you want to help making parking possible, and look at the local regulations? Or do you have strong oppinions on how cars should be placed?

We are in dire need of supporting people for the parking coordinator. Workload can vary, but we certainly need support on the field during the late build-up and the event itself. Please contact {{UserLink|Konmei}} for more information and if you are interested.
|-

| [[Team:Merch]], administrative coordinator
|
Quality inspector, distribution planner and online shop stockkeeper
We are looking for a Merch coordinator, who keeps an eye on the shop, handles questions, production and delivery of the WHY2025 Merch. First to feel the merch, looking at samples.[https://tickets.why2025.org/media/pub/ifcat/why2025/item-22-6fce47a6-9b15-4fce-b3ee-b065e9067b23.jpeg image of shirt]

Let's dress the hackerscene, contact {{UserLink|Netsmurf}}!
|-
| [[Team:Accessibility]], Team members
|
We're looking for people to join the Accessibility team to make this the most accessible event ever!
|-
| [[Team:Shuttle]], Team members
|
We're looking for people to help organise the Shuttles.
The shuttle is, for a large amount of visitors, their first encounter with the event. They should enthusiastic and full of good energy. Really rewarding job though! Not only when arriving, but also when you bring them back to the train.
For questions, contact {{UserLink|crablab}}.
|-
| [[Team:Badge]], Team members
|
We can definitely use more software developers that are willing to commit to working with us on this interesting project.

If you have experience with '''embedded C''' programming we'd love for you to join the '''Firmware''' team and if you have experience with '''Web / Application''' development the '''BadgeHub''' team would love to see you help out.

Join our '''Signal''' group for '''Newcomers''' and write us a message if you feel like joining us or just want to explore if you see it fit. https://signal.group/#CjQKICKbwZzlVup_A_smn_rUWrQVTzomGlBZgkP3Txm_P23xEhDzXQr4gvUMxUxivNZKuOEj
|-
| [[Team:Foodcourt]], Team members subteam "Bar"
|
We are looking for team members for the Horeca team, subteam Bar. Do you like to put a smile on people's faces?

The Bar team will organize, build and run the 3 planned Bar areas. Organizing consists of planning, designing bar set-up, ordering supplies to be delivered.
A few days before the event we will receive the ordered stuff and start the build up.
During the event on site the Angels will run the bars.
With a dedicated Bar-team we coordinate, re-supply and take turns solving any problems for the 3 event bars. Do you want to be part of the team closest to the Mate? Then this is the team for you!

For questions, contact {{UserLink|K4T0}}
|-
| [[Team:PartyArea]], Team members
|
The Party Area team will organize, build and run the WHY2025 main stage with Live Music content, DJ's Silent Disco until deep in the Night
We are looking for Team Members that can't sleep anyway and love to organize parties !!!

For questions, contact {{UserLink|Netsmurf}}
|-
| [[Team:Cohesion]], Team member
|
Team Cohesion is looking for extra team members. Both for during the event to coordinate things and in the preparation phase. Take a look at the team page for the things we are working on before the event starts if you want to lend a hand in creating policy or set up the ultimate silent lounge. For during the event we need people who are good listeners and feel up to deescalate wherever necessary.
Get in touch with us so you can help everyone be excellent to each other.

For questions, contact {{UserLink|Dany}}
|-
| [[Team:Parking]], Team Lead
|
The Parking team is a fun vitally important team responsible for making our visitors feel welcome when they arrive for the first time at WHY2025 and making sure traffic flows and parking are done in a safe and orderly way.

For questions, contact {{UserLink|Netsmurf}}
|-
| [[Team:Parking]], Team members
|
The Parking team is a fun vitally important team responsible for making our visitors feel welcome when they arrive for the first time at WHY2025 and making sure traffic flows and parking are done in a safe and orderly way.

For questions, contact {{UserLink|Netsmurf}}
|-
| [[Team:Family]], Project owner
|
Even if you do not have time to be very closely involved with FamilyZone you may want to do something for/with (your?) kids. We are very open to people to run one or two projects at the event. Check out our [[Team:Family#Projects|current project list]] for inspiration.
|-
| [[Team:Content]], Speaker Desk Volunteers
|
Team:Content is in need of volunteers for Speaker Desk (more info soon).

Contact content@why2025.org to get involved!
|-
|}

== Teams who still need members ==



{{#ask: [[Category:Team]] [[Team needs x people::>1]]
|?Team is essential to event=essential to event
|?Team has enough people=enough people
|?Team needs x people = team needs x people
|?E-Mail=Contact
|limit=100
|offset=0
|link=subject
|sort=
|outrotemplate=plteamhealthfooter
|order=asc
|headers=show
|searchlabel=... further results
|class=sortable wikitable smwtable
}}

== I want to do something small ==
Small tasks that need to be done, or large tasks that can be split in small tasks are collected at the [[Tiny_Tasks]] list

Village:̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝

2025-07-06T18:26:09Z

Okarin:

{{Village
|Has name=ZERO WIDTH NO-BREAK SPACE
|Has website=https://wiki.why2025.org/Village:̸̡̛̯̳͎͔̟̠̪̲͖̦̒̆̀̈̉̒͊̚̕͝
|Has contact=Shiz (5730)
|Has description=No brakes on this unicode
|Part of=Arcade
|Related to village=Village:Tilde.industries and friends, Village:Øl Telecom, Village:Chrząszczyżewoszyce, Village:DIWhy Bar
|Has village tag=arcade, reverse engineering, music, breaking, fixing, text rendering
|Village is open to newcomers=Yes
|Provides session location=No
|Location=52.69289, 4.74508
|Has orga contact=why@shiz.me
|On site orga contact=Shiz
|Village frab=no
|Village content space=no
|Village citizen count=12
|Village Needs power=Other (describe below)
|Village size needed=0
|Village hacktents num=0
|Village brings big stuff=No
|Village Special Vehicle=no
|Village planning notes=Located inside the Arcade 1 tent, no other specific resources needed.
}}
And a dutch hacker named Iron (the real one)
==TL;DR==

A collective of hardware/software/food hackers with a weird habit of finding cursed technology to break. The WHY2025 reincarnation of [https://wiki.mch2022.org/Village:Love_Live_Laugh!_Arcade_Hacking_Festival_~after_camp_ACTIVITY~_Wai-Wai!_Tent_Meeting!! Love Live Laugh! Arcade Hacking Festival ~after camp ACTIVITY~ Wai-Wai! Tent Meeting!!].

Come discover the weird world of modern industrial game systems!

==Equipment==

* Cabinets for [[Project:Arcade]]
* Weird arcade baseboards and systems!
* Test & measurement equipment
** Agilent 54854A oscilloscope (20 GSa/s, 4 GHz)
** Tektronix 222 oscilloscope (small and cute, 10 MHz, portable, floating inputs)
** Tektronix TLA5202 logic analyser (68 channels, 2 GHz)
** Kikusui PWR800M DC power supply (0-320V, 0-12.5A, 800W)
* Train parts
** NS ICMm destination dot-matrix display
** NC ICMm 1st class seats?
* 3D printers
** Voron V2.4 350mm