WHY2025 wiki - User contributions [en]

Project:Meshtastic on the WHY2025 badge

2025-12-23T11:23:24Z

Xylitol: /* Patryk's port */

{{Projects
|Name=Mesthastic on WHY badge
|Has project tag=meshtastic, badge
|Has description=A WiP port for the WHY badge
}}
* [[Badge/LoRa-Antenna|LoRa antenna is not fully optimized for EU usage]] (But works perfectly well with a little tuning at 1.7 SWR @868. If worried you can pick up a better tuned antenna for under €10).

I am porting a meshtastic version that should work on the WHY badge. Currently it works and you can interact with it using the USB serial port.
Feel free to edit this page to add your developments and point to your own github repo with your progress.

The code is [https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge here] (note it is not the main git branch) and it is based on the c6 port [https://github.com/alexbegoon/firmware/tree/add%20seeed%20xiao%20esp32c6%20variant here] - Or better, see in this same page, Patryk's port with UI.

Further instructions on compiling and flashing meshtastic can be found [https://meshtastic.org/docs/development/firmware/build/ here], be sure to use the correct git branch and use the "why2025-badge" variant (it should be the default one on my fork) - the USBC port for the ESP32C6 is the bottom one.

Be aware: '''It requires soldering two GPIOs on the LoRa radio to the ESP32C6'''. Additionally, '''the firmware overwrites the ESPHosted firmware, so the badges loses all WiFi and Bluetooth functionality''' while this firmware is loaded. You can restore the original firmware to re-gain WiFi and Bluetooth (but lose LoRa). It is likely possible to have a firmware that supports all, but this has not been done yet.
Also, the screen and keyboard backlight PWM is wired to the C6, so meshtastic should be modified or configured to enable this outputs.

Also, be aware, the LoRa radio [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/7169/RA-01SH.pdf datasheet] shows different pinout from the KiCad schematics:

[[File:Captura de pantalla 20250811 155120.png]]

So, meshtastic requires the CAD (channel activity detection) and busy pins to be soldered between the LoRa radio and the ESP32, this is documented in [https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h this file], but you can edit at your pleasure.

You can see a modified badge here:

[[File:Badge-lora-solder.jpg]]

Next step when the radio is working should be porting this to have a fully functioning independent device:

[https://github.com/meshtastic/device-ui/tree/master Meshstastic Device UI]

=== Patryk's port ===

Updated 2025-09-22:
Now with better instructions, prebuilt images, web installer and automatic C6 flashing, like BadgeVMS.

https://github.com/pkoryzna/meshtastic-ui-why-m2

See the README for current status. Testing needed and appreciated :)

For French speaking people a build guide of Patryk's port from source is available here: https://hackgyver.fr/pages/writeups/why2025-meshtastic

[[File:Meshtastic UI running on badge.jpg]]

==== Meshcore on the WHY2025 badge ====

(Meshcore is not Meshtastic (nor are they compatible), but opening a new page does not seem to make much sense to me.)

WHY2025 badge support (which was mainly redefining pins) is now on upstream meshcore \o/ You may need to use dev branch for it.

Same as others, you'll need to solder those 2 pins as described. No screen usage yet, sensors are not used, bluetooth works.

See instructions on [https://github.com/meshcore-dev/MeshCore/pull/671 the PR] for building and flashing.

Project:Meshtastic on the WHY2025 badge

2025-12-20T13:55:43Z

Xylitol: /* Patryk's port */

{{Projects
|Name=Mesthastic on WHY badge
|Has project tag=meshtastic, badge
|Has description=A WiP port for the WHY badge
}}
* [[Badge/LoRa-Antenna|LoRa antenna is not fully optimized for EU usage]] (But works perfectly well with a little tuning at 1.7 SWR @868. If worried you can pick up a better tuned antenna for under €10).

I am porting a meshtastic version that should work on the WHY badge. Currently it works and you can interact with it using the USB serial port.
Feel free to edit this page to add your developments and point to your own github repo with your progress.

The code is [https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge here] (note it is not the main git branch) and it is based on the c6 port [https://github.com/alexbegoon/firmware/tree/add%20seeed%20xiao%20esp32c6%20variant here] - Or better, see in this same page, Patryk's port with UI.

Further instructions on compiling and flashing meshtastic can be found [https://meshtastic.org/docs/development/firmware/build/ here], be sure to use the correct git branch and use the "why2025-badge" variant (it should be the default one on my fork) - the USBC port for the ESP32C6 is the bottom one.

Be aware: '''It requires soldering two GPIOs on the LoRa radio to the ESP32C6'''. Additionally, '''the firmware overwrites the ESPHosted firmware, so the badges loses all WiFi and Bluetooth functionality''' while this firmware is loaded. You can restore the original firmware to re-gain WiFi and Bluetooth (but lose LoRa). It is likely possible to have a firmware that supports all, but this has not been done yet.
Also, the screen and keyboard backlight PWM is wired to the C6, so meshtastic should be modified or configured to enable this outputs.

Also, be aware, the LoRa radio [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/7169/RA-01SH.pdf datasheet] shows different pinout from the KiCad schematics:

[[File:Captura de pantalla 20250811 155120.png]]

So, meshtastic requires the CAD (channel activity detection) and busy pins to be soldered between the LoRa radio and the ESP32, this is documented in [https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h this file], but you can edit at your pleasure.

You can see a modified badge here:

[[File:Badge-lora-solder.jpg]]

Next step when the radio is working should be porting this to have a fully functioning independent device:

[https://github.com/meshtastic/device-ui/tree/master Meshstastic Device UI]

=== Patryk's port ===

Updated 2025-09-22:
Now with better instructions, prebuilt images, web installer and automatic C6 flashing, like BadgeVMS.

https://github.com/pkoryzna/meshtastic-ui-why-m2

See the README for current status. Testing needed and appreciated :)

For French speaking people a build guide of Patryk's port from source is available here: https://hackgyver.fr/pages/projets/why2025-meshtastic

[[File:Meshtastic UI running on badge.jpg]]

==== Meshcore on the WHY2025 badge ====

(Meshcore is not Meshtastic (nor are they compatible), but opening a new page does not seem to make much sense to me.)

WHY2025 badge support (which was mainly redefining pins) is now on upstream meshcore \o/ You may need to use dev branch for it.

Same as others, you'll need to solder those 2 pins as described. No screen usage yet, sensors are not used, bluetooth works.

See instructions on [https://github.com/meshcore-dev/MeshCore/pull/671 the PR] for building and flashing.

Project:Meshtastic on the WHY2025 badge

2025-12-01T10:32:54Z

Xylitol: /* Patryk's port */

{{Projects
|Name=Mesthastic on WHY badge
|Has project tag=meshtastic, badge
|Has description=A WiP port for the WHY badge
}}
* [[Badge/LoRa-Antenna|LoRa antenna is not fully optimized for EU usage]] (But works perfectly well with a little tuning at 1.7 SWR @868. If worried you can pick up a better tuned antenna for under €10).

I am porting a meshtastic version that should work on the WHY badge. Currently it works and you can interact with it using the USB serial port.
Feel free to edit this page to add your developments and point to your own github repo with your progress.

The code is [https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge here] (note it is not the main git branch) and it is based on the c6 port [https://github.com/alexbegoon/firmware/tree/add%20seeed%20xiao%20esp32c6%20variant here] - Or better, see in this same page, Patryk's port with UI.

Further instructions on compiling and flashing meshtastic can be found [https://meshtastic.org/docs/development/firmware/build/ here], be sure to use the correct git branch and use the "why2025-badge" variant (it should be the default one on my fork) - the USBC port for the ESP32C6 is the bottom one.

Be aware: '''It requires soldering two GPIOs on the LoRa radio to the ESP32C6'''. Additionally, '''the firmware overwrites the ESPHosted firmware, so the badges loses all WiFi and Bluetooth functionality''' while this firmware is loaded. You can restore the original firmware to re-gain WiFi and Bluetooth (but lose LoRa). It is likely possible to have a firmware that supports all, but this has not been done yet.
Also, the screen and keyboard backlight PWM is wired to the C6, so meshtastic should be modified or configured to enable this outputs.

Also, be aware, the LoRa radio [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/7169/RA-01SH.pdf datasheet] shows different pinout from the KiCad schematics:

[[File:Captura de pantalla 20250811 155120.png]]

So, meshtastic requires the CAD (channel activity detection) and busy pins to be soldered between the LoRa radio and the ESP32, this is documented in [https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h this file], but you can edit at your pleasure.

You can see a modified badge here:

[[File:Badge-lora-solder.jpg]]

Next step when the radio is working should be porting this to have a fully functioning independent device:

[https://github.com/meshtastic/device-ui/tree/master Meshstastic Device UI]

=== Patryk's port ===

Updated 2025-09-22:
Now with better instructions, prebuilt images, web installer and automatic C6 flashing, like BadgeVMS.

https://github.com/pkoryzna/meshtastic-ui-why-m2

See the README for current status. Testing needed and appreciated :)

For French speaking people a build guide of Patryk's port from source is available here: https://hackgyver.fr/pages/projets/Meshtasticwhy2025

[[File:Meshtastic UI running on badge.jpg]]

==== Meshcore on the WHY2025 badge ====

(Meshcore is not Meshtastic (nor are they compatible), but opening a new page does not seem to make much sense to me.)

WHY2025 badge support (which was mainly redefining pins) is now on upstream meshcore \o/ You may need to use dev branch for it.

Same as others, you'll need to solder those 2 pins as described. No screen usage yet, sensors are not used, bluetooth works.

See instructions on [https://github.com/meshcore-dev/MeshCore/pull/671 the PR] for building and flashing.

Feedback

2025-08-18T19:15:48Z

Xylitol: /* Volunteering / angels / heaven */

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback. Positive feedback, on things we should definitely do again next time is also appreciated and helpful.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1
* "Communication" in general seems to be the theme of this camp. It was extremely difficult to find reliable information about anything as a visitor/angel, and often you only had the grapevine to go off, and you just had to hope that the necessary information somehow reached you at some point. From what I've heard it wasn't much better between teams either. Documenting things is really important and saves everyone a lot of work having to repeat and figure out the same things over and over again!
* Don’t use generative “AI” or large language models in official communication. Have seen lots of stuff on this wiki that has that classic LLM stink on it.
* Officially discourage/disallow people from using LLM or GenAI in talks. Have seen quite a few images in slide decks that are absolutely generated by GenAI (including grave misunderstandings of human anatomy lol)
* The site was not suitable for this kind of event. There was essentially no tree cover and no shade anywhere, no swimming water to cool off in, and the long-and-narrow shape made it difficult for far-away social groups to mix due to the long walks involved. The SHA/MCH site was much better on all of these points.
** In my experience Zeewolde (SHA/MCH-terrain) was far more long-and-narrow, but more tree cover would have definitely been welcome.
* Intra-team communication proved difficult during planning and buildup; big orga meetings of multiple hours causes people to tune out fast and not really lead to meaningful discussions but just quick updates.
* Would like to see a more clear split between teams and projects; teams being what is necessary for the event to happen at all, and projects being nice-to-haves that make the camp the place we want it to be. This way if there's less (core) teams, orga meetings could also be slimmed down and communication possibly more efficient.
* While it was good to see signal being used a lot, using it for a large number official announcements was not very effective. Signal does not share message history when members join a group so previous announcements are not viable to new members.
* Signal announcement groups were only used partially and did not link to services with official communication channels (such as sign posting people to angel.why2025.org for Heaven updates). Some announcements posted on the Angel system were also posted on the signal group, but it wasn't consistent so announcements were missed.
* These points were compounded when large announcements on the angel system were pinned to the top. Considering many users primary accessed the angel system via mobile phone, they would need to scroll multiple times to know if there were new announcements. In many cases, I had individuals complaining about lacking information and I had to teach them what was wrong so they could stay updated. This added frustration to people wanting to volunteer.
* a great amount of assumptions and unwritten rules are present that a new-comer might not be aware of. Quite often, weird situations got brushed off as "tradition" including taking flags from Deco home because apparently that was OK last camp.
* My experience of WHY2025 as an immunocompromised person: https://fedi.slightly.tech/@joepie91/statuses/01K2YJ7RTEBF9ZZRWG5ASBPJ90 (compiles various different issues and places them in context)

=== Arcade ===

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!
* Overly-strict parking angels were a returning issue. To name two incidents:
** Parking bike angel halting a huge Boels truck driving out of the terrain during teardown telling him he needed a bike angel (it had been a multi-hour pickup from LSD including the truck in question breaking down, large suppliers typically don't have bike angels as they are dealt with by on-site or productiehuis), and telling him to turn the huge truck around on the main road as it was going against the one-way direction. The zeal is necessary at times, but having turned around a huge truck full of rental stuff on de Wagenweg would have caused significantly more issues and delays than it was immediately solving.
** Parking bike angel telling a car to continue driving in the one-way-direction despite being repeatedly told and shown that the upcoming cable cover bump would ruin his bumper and he can not drive over it. Car driver got told it was his problem and to solve it himself.
* Parking felt like a premium experience! being greeted by a friendly and energetic angel and guided to my parking spot with no issues.
* tear-down chaos with everyone requesting field access was handled quite well considering the workload!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.
* Stop giving out badges by default that’ll end up collecting dust or become e-waste shortly after the event. Would much rather have paid 30 EUR (or however much they cost) then pay for a crap badge I wasn’t even able to get. Also makes the event more accessible to financially unprivileged people.
** +1 to this, my badge has now been stowed away in a drawer and I will most likely never use it again.

* This year I made my first pcb: a SAO. I was really looking forward to handing them out to people. But there is no easy way to add SAO to the badge except to buy the extension. So in the end I didn't hand out any. Next time it would be great to have a badge with a build in SAO connector, because I'll be making more SAOs for sure!

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
** +1, this was really demotivating
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.
* Queues at the bar were sometimes very long and slow. Bottleneck during peak times seemed to be the payment terminals, having two or more instead of one terminal would already speed everything up.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help +1
* Near constant drone flyovers at times and nothing happened to curb it, or even announce it is violating policy (to be fair, I do not know if anyone complained - I did not either, but was severely bothered by the sound alone; like a giant privacy violating mosquito).
* It would be nice if new organizers who joined the field build up for the first time get more included / accepted when they have free time to help out, and NOT to get rejected from tasks. Some of us felt very left out and sad :( (Remember, we're all volunteers and not paid workers, so keep the elitist behavior out of orga please).

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.
-> Apart from that hardcore talk, some hacker disconnected the subwoofers, hence why the lack bass during the hardcore talk which kinda sucked but additional security was added after.
* Speakerdesk was very nice! Having a good place to prepare slides and practice a bit was great.
* A better handover process needs to be established from A/V tech + heralds + speakers. Who is putting on microphones, who is checking them.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +2
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this. +1
* New signs popped up at various places during the event when necessary, very nice to have the Deco team able to accomodate needs last minute and on site.

=== Family / kids ===

- Family field offered lots of entertainment for our kids. Location was perfect, with a direct path to the arcade and silent lounge. You could hear the noise from other fields but it was never overwhelming. Daycare was a blessing.

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
** +1, this was set up well! My only feedback would be to maybe have something that you can tap your card against to see the remaining balance (or otherwise instruct angels to communicate the balance upon payment)
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage
* Card payment everywhere is amazing!
* On a few of my shifts (WOC, main bar), the WHY payment card failed to scan on the POS (it popped up a toast message saying no application is registered for this NFC card) and i received conflicting/no information about what to do about it or how to properly use it. Rebooting the POS seemed to help, but i'm more concerned with the conflicting/no training on what to do with it. The card looks great and worked a dream whenever the POS wasn't having trouble scanning it!

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later. +1
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +4

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo +1
* Wireless kept disconnecting every few minutes for the entire event

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns. If not possible, less hot is preferred. My partner could not use the shower due to the heat
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +3
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks! +1
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +3
* furthermore, the toilets seemed to be cleaned often which is good. +3
* There always was toilet paper available in the stalls, greatly lessens anxiety. +4
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +3
* There always was plenty of soap available at the sinks, during peak time and at night. +3
* Dedicated dishwashing location. +4
* More drinking water fountains across the terrain
* Hoses to fill canisters at drinking water locations - did not find any other location than heaven where it was possible +1
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized
* Communication to other teams with regards to their planning would have been heavily appreciated and could have prevented some minor crises (like the logistics traffic jam during buildup)

=== Off-site logistics ===
* Very clear upfront, yet flexible during the event when needed and did a great job transporting and thinking along. Kudos!

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.
* The desk phone, DECTs and the ability to make outside calls were incredibly useful for our team.
* SIP worked great once the wiki instructions were followed. A bit unclear from what date the SIP server was exactly available!

=== Productiehuis / C3VOC ===

* Camera Angels had little to nothing to do, all they did was standing still, because of static shots. It would be more efficient to just leave CAM 1 as a Medium close up shot of the lectern and CAM 2 as a wide shot. Also there's really no need for an intercom system at the FOH which was next to useless.
* A lot of the angel positions could be automated and doesn't really require much hands on work. Apart from Signal Angel, which seems to be the most busy angel type.
* Stagehand Angeltype to be added instead per track instead of A/V Technician per track. Better to use an A/V Technician for purely troubleshooting when needed, those should be on-call instead.
* A use of Dante audio routing + a centralized mixer (with separate mixing matrixes per track would be a more efficient setup) at the VOC tent. (would also cut costs to renting 4x Digital mixers)
* Spykersound's low budget equipment didn't seem too reliable, especially the EV mics and some of the TVs, they also provided the wrong Power supplies to things, there was also lack backup equipment which the supplier packed away too early. (IMHO, I would never hire Spykersound, they seem rather incompetent and annoying to deal with).
* Time management of build up tasks needs to be improved, leaving all remaining tasks to a few hours before opening was not really ideal, there needs to be better planning from the start of build up, some of the organizers arrived early and had little to no tasks to do other than doing other unrelated build up tasks. Also it would be great next time to know when it's the recommended day to join the build up of Productiehuis beforehand, so that people don't use up their energy on other tasks.
* C3VOC is a very efficient team but it would be nice if they could delegate interesting tasks to the rest of the team as well and not hog all the interesting tasks to themselves.
* The placement of the screen on the Andromeda stage was bad. Audience members could only see the top 60% and only the left side, because the rest was obscured by the audience, the speaker lectern or the speaker. When sitting on either the left or right side of the chairs, the screen was obscured by the metal pillars on stage. Please consider the viewing angles from the audience because it was hard to follow talks that relied on their slides for explanation, when those slides cannot be properly seen.

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.
* ROC did a stellar job in running the radio network which saw a lot of action during the various crises and power cuts. Battery life was amazing and I never had issues making a call

=== Safety / security / first aid / fire ===
* Having yellow as the allocated first-aid safety vest color during the event was not the best choice, as it's one of the two most generic safety vest colors people are likely to already have/bring.

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves +1
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot. +1
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)
* Very resilient, apparently; throughout just about every logistical and infrastructure problem at camp, they seemed to keep operating. Would like to see them back! +1
* Would have liked to see tofu in the assortment; a few vegan proteins were available but none were quite as versatile.
* Instead of installing white tarps on the sides of the supermarket tent, black tarps were installed, making the supermarket uncomfortably warm inside!
* This was a fantastic addition, the supermarket had a good selection and fresh bread every morning.

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff. +1
** -1 agreed. "distant" location is not really possible on-site
** +2 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
** +1, At Lambda village we choose to be behind the party stage to be loud and partying, but the permit said no amplified noise after 23:00, which made most of the camp dead after this time.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, and designated smoking areas away from event spaces would be appreciated. Quite a few people smoking in busy areas without much attention about people around them, not to mention throwing cigarette butts on the grounds. A blanket ban on smoking and vaping for the entire event is probably to draconian (unfortunately).
* All the big track tents and workshop tents that had black tarps installed instead of white was a really bad idea, it made the interior more like a sauna. Down right unbearable to visit.

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.
* Was very happy with the village planning this time around, we had a very cozy cluster. Thanks a lot!
* Loved that it was possible to rent tents and bedding! (though they got very uncomfortably cold and damp at night, maybe consider waterproof sleeping bags next event)

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''". +1
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* +1 about the leak problem, i put water everywhere when doing my shifts, finally i stopped to use it and took my own bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.
* Loved the DasBrot
* Didn't love the utter lack of social hygene during breakfast, lunch and dinner. The proper tools were lacking. Get a cooling gastronorm tray thing for all your meats and cheeses, get the (wasteful) small cups of smears. And have people service it. Dinner handout got fixed with angels doing plating, but was still very haphazard on several days.
* You need more people on the team. You worked your butts off and did not get to enjoy camp enough. I wish better for you all.
* Also get teardown safety vests (or use generic ones for buildup and give a cool one to those tearing down).
* Water-as-a-service trucks were organized well and at a very good frequency during my shifts; however prolonged storing of jerrycans of drinking water unprotected in full sun is not safe.
* Was very happy with the available food during all portions of the event, great job.
* Some more organisation in allocating tasks would probably be helpful. There were numerous cases of people not knowing what to do, and vice-versa teams recruiting angels themselves by approaching them in heaven.
* When calling for standby angels, it's probably better to immediately mention the task instead of just "I need two angels"; that way you can select for people already familiar with the task. Now I often had to ask myself and then someone else would pipe up once they recognized the task.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!
* Purchase generic safety vests for use during shifts. All safety vests with branding were taken by people having done buildup.
* Have radio battery charging and exchange either handled by ROC or extend opening hours. I know you guys also need rest, so perhaps have an exchange option that does not require warehouse

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
''-> The rules for plastic and metal recycling vary per local municipality, let alone per country. So we decided to not do a plastic/metal sorting bin as it would probably only cause headaches. ''

''-> Paper and food remains were collected seperately at heaven, foodcourt. Agree on extending that to villages.''

''-> Pfand was handled by team bar. Full agree. We saved a trailer full of big bags of bottles and cans.''

* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)
* The bins near the villages I was at were always emptied before overflowing, which was nice. On teardown day I saw a big pile of bottles around one of the bins: can't say if glass or deposit ones. Generally the field seemed rather clean.

''-> See above, glass deposit should have been collected. Unclear why it wasn't.''

* Thanks for the motivating music! It was always a pleasure to see you guys roll by.

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.
* The to-do whiteboard on the last few days helped a lot with clarity, highly appreciated!

Feedback

2025-08-18T19:06:36Z

Xylitol:

'''What Hackers Yearn''' for is to '''Improve'''. This page is dedicated to collecting user feedback related to the execution of WHY2025 as a whole. Constructive feedback is invaluable to the continuous improvement of the project and is welcomed from all participants. Please share your observations and suggestions in a '''clear and respectful manner'''. Your input will help guide enhancements for future generations of the event.

It is also possible to send feedback to [http://mailto:2029@why2025.org 2029@why2025.org]

== IMPORTANT ==

Do '''NOT''' review '''people'''. Any individual interaction you had with a human does not belong here, but should be taken up with [[Team:Cohesion]].

This page is strictly for addressing improvements for the next event. We encourage contributors to maintain a neutral, factual, and calm tone in their feedback. Positive feedback, on things we should definitely do again next time is also appreciated and helpful.

* GOOD EXAMPLES: "Excessive mud at showers", "Food vendors often refused to accept WHY-voucher", or "Limited drop-off points for luggage shuttle".

* BAD EXAMPLES: "Person XXX was insulting me", "Helpdesk XOC was too busy to help", "frickin hot", "So the story begins on Saturday night at 23:04 when..."

== Feedback List ==

=== General / overall ===

* There should be a clear single method/channel of communication from orga, using the Heaven signal chat or social media for this is not ideal
** +1
* "Communication" in general seems to be the theme of this camp. It was extremely difficult to find reliable information about anything as a visitor/angel, and often you only had the grapevine to go off, and you just had to hope that the necessary information somehow reached you at some point. From what I've heard it wasn't much better between teams either. Documenting things is really important and saves everyone a lot of work having to repeat and figure out the same things over and over again!
* Don’t use generative “AI” or large language models in official communication. Have seen lots of stuff on this wiki that has that classic LLM stink on it.
* Officially discourage/disallow people from using LLM or GenAI in talks. Have seen quite a few images in slide decks that are absolutely generated by GenAI (including grave misunderstandings of human anatomy lol)
* The site was not suitable for this kind of event. There was essentially no tree cover and no shade anywhere, no swimming water to cool off in, and the long-and-narrow shape made it difficult for far-away social groups to mix due to the long walks involved. The SHA/MCH site was much better on all of these points.
** In my experience Zeewolde (SHA/MCH-terrain) was far more long-and-narrow, but more tree cover would have definitely been welcome.
* Intra-team communication proved difficult during planning and buildup; big orga meetings of multiple hours causes people to tune out fast and not really lead to meaningful discussions but just quick updates.
* Would like to see a more clear split between teams and projects; teams being what is necessary for the event to happen at all, and projects being nice-to-haves that make the camp the place we want it to be. This way if there's less (core) teams, orga meetings could also be slimmed down and communication possibly more efficient.
* While it was good to see signal being used a lot, using it for a large number official announcements was not very effective. Signal does not share message history when members join a group so previous announcements are not viable to new members.
* Signal announcement groups were only used partially and did not link to services with official communication channels (such as sign posting people to angel.why2025.org for Heaven updates). Some announcements posted on the Angel system were also posted on the signal group, but it wasn't consistent so announcements were missed.
* These points were compounded when large announcements on the angel system were pinned to the top. Considering many users primary accessed the angel system via mobile phone, they would need to scroll multiple times to know if there were new announcements. In many cases, I had individuals complaining about lacking information and I had to teach them what was wrong so they could stay updated. This added frustration to people wanting to volunteer.
* a great amount of assumptions and unwritten rules are present that a new-comer might not be aware of. Quite often, weird situations got brushed off as "tradition" including taking flags from Deco home because apparently that was OK last camp.
* My experience of WHY2025 as an immunocompromised person: https://fedi.slightly.tech/@joepie91/statuses/01K2YJ7RTEBF9ZZRWG5ASBPJ90 (compiles various different issues and places them in context)

=== Arcade ===

=== Arrival / departure / parking / train shuttle / luggage shuttle ===

* On day 0 we queued to drive onto the field. We said said we had stuff for two different villages at opposite ends of the site, named the villages and showed them on map print outs. This information was accepted by a dispatcher. However, the bicycle guide refused to guide us to the second location, claiming it was impossible to get there. This is somewhat surprising, since others had been able to drive to that location before. It seemed there was a informational mismatch between dispatch and bicyle guide. (Both locations were accessible by asphalt roads.)
* train shuttle worked well, good job!
* Overly-strict parking angels were a returning issue. To name two incidents:
** Parking bike angel halting a huge Boels truck driving out of the terrain during teardown telling him he needed a bike angel (it had been a multi-hour pickup from LSD including the truck in question breaking down, large suppliers typically don't have bike angels as they are dealt with by on-site or productiehuis), and telling him to turn the huge truck around on the main road as it was going against the one-way direction. The zeal is necessary at times, but having turned around a huge truck full of rental stuff on de Wagenweg would have caused significantly more issues and delays than it was immediately solving.
** Parking bike angel telling a car to continue driving in the one-way-direction despite being repeatedly told and shown that the upcoming cable cover bump would ruin his bumper and he can not drive over it. Car driver got told it was his problem and to solve it himself.
* Parking felt like a premium experience! being greeted by a friendly and energetic angel and guided to my parking spot with no issues.
* tear-down chaos with everyone requesting field access was handled quite well considering the workload!

=== Badge ===

* Badge handouts were announced right before they happened which didn't allow people to plan their angel shifts and disrupted talks / workshops. A virtual queue would have fixed this and required less total manhours to organize / manage. +1

* There was an expectation that the badge was and I quote from what I have overheard "included in the price". This is not the case and has never been the case but it’s not clearly communicated. To my understanding there was a surplus at SHA2017 and MCH2022 so there never was a shortage of badges before which may have contributed.
** The above is misinformation: It was in fact communicated in written form that every attendee with a ticket receives a badge. The badge could not be ordered separately and was included in the ticket price.

* During the event (AFAIK) there were no badge angel shifts outside of queue angel. This is a chance from prior events and didn't allow people who normally would have helped to help in the same way.

* Due to the badges not being self-powered nor being distributed at the entrance they failed to function as badges. The SHA2017 badge was designed with having no power yet still being a nametag in mind. The WHY2025 badge did not seem to function as a nametag which should have been its intended design goal.

* At MCH and SHA you had people using the badges at the event itself to make games / hack / learn / teach. It was something which brought people together. There was very little being done / to do with the badge during the camp, not just because of the late arrival and limited distribution but rather because there is no way to get apps on the badge outside of the SD card... or if there is a way of doing so then its not documented on the wiki page as of writing. There was no app store app, no way to use the LORA hardware, and outside the event its impossible to use the badge without reflashing a new wifi SSID.

* You could not sit at the badge tent and solder on your antenna onto the badge or work on projects. At SHA and MCH you could just approach the badge people / angels and even get help with projects.

* Badge still has way too limited documentation to even work on it after the event.

* Team Badge have overworked themselves to get a badge available. Team over Badge next time. Which is also a Team:Cohesion issue.

* Would have been great to have a separate queue for villages that collected tickets and pick up 15+ badges at the same time. This would also have greatly reduced waiting times for individuals picking up badges and sped-up the whole process.

* Not enough badges for all visitors (not even close apparently).

* Badge queues were very long and poorly managed. This made it impossible for some people to collected a badge (for example because they cannot stand that long, require shade, have to take care of children, need to go to their next angel shift, etc.)

* The communication about the badge status was very sparse and lacking. If there is a problem, '''communicate''' about it and tell participants what to expect.

** +1. I am sympathetic to the team scrambling to get stuff done under difficult constraints, but especially in such cases good communication is important. Things like randomly posting a link to a page about the keyboard hardware felt frustrating when we were just waiting for more info about future handouts. In addition, a Signal group was a poor choice of channel for announcements for many reasons - no public access, no history for new joiners, redundant join/leave messages, etc. Keeping updates to a section on the wiki and/or a mailing list would've worked much better.

* During build-up, almost all other teams were scrambling to find a pair of hands to get essential stuff done, while watching lots of people pouring epoxy in the badge tent. Which was, lemme me blunt here, one of the lowest priority of all the things that have been done during build-up.
* Stop giving out badges by default that’ll end up collecting dust or become e-waste shortly after the event. Would much rather have paid 30 EUR (or however much they cost) then pay for a crap badge I wasn’t even able to get. Also makes the event more accessible to financially unprivileged people.
** +1 to this, my badge has now been stowed away in a drawer and I will most likely never use it again.

* This year I made my first pcb: a SAO. I was really looking forward to handing them out to people. But there is no easy way to add SAO to the badge except to buy the extension. So in the end I didn't hand out any. Next time it would be great to have a badge with a build in SAO connector, because I'll be making more SAOs for sure!

=== Bars and food court ===

* Menu was much longer and more complex compared to MCH. A lot of items were almost never sold, like nachos and chips.
* Slight differences in the menu between the bars caused customers to ask "Do you have ...?". Also complicates restocking logistics.
* The amount of Rum in the "Tschunk" was '''halved''' without updating the price. They decided it was better to modify the recipe to make it almost non-alcoholic, rather than say "Sorry, we're out."
** +1, the Tschunk contained barely any Rum.
* Bar is not a Merch Store, "Special/Ceremonial Cup" should be sold in Infodesk. It was also badly advertised, only people who "knew" of its existence could buy it. +1
* How was the cup not a deposit... I didn't even realize you wouldn't get any money back. Made it extremely bothersome to buy drinks for other people. +1
* Why wasn't statiegeld/pfand collected? Many glass bins full of mate-bottles. I don't want to know how many plastic bottles and aluminium cans were thrown out. This could have been prevented.
* No Club Mate Beere?
* No normal (0.5L) bottles available on the last day?
* Do we get mate from the source, or a Dutch overprices company?
* No mate during buildup again?
** +1, this was really demotivating
* Not written instructions for angels. The “game of telephone” style handing of incorrect instructions down from one angel to the next caused food to be prepared incorrectly. Written instructions should be posted right at the frier and microwave.
** +1
* Handling of vegan food was bad. Burger stall incorrectly advertised vegetarian burger as "vegan" originally, and could not provide any vegan burger at all because the buns contained milk(!). Fries/snacks stall staff did not know what they were selling or what it contained, and communication was difficult. Only positive note goes to the pasta stall where the food was good, and the operator was highly competent and knew exactly what they were selling (I would like to see them at a next event).
* Bottle collection procedure was very unclear.
* To add to the above: between bar and foodcourt no crates in sight on several days. No crates at any of the waste collection points. No instructions or procedure arranged. So people grabbed the glass-waste bin from the showers and put it in the middle. End result: 24x 240L glass trash bin completely filled to the brim. Assuming roughly around 5000 pfand-bottles (Mate, beer etc) were trashed. And team Waste had a ton of heavy lifting to get all these bins off the field and back to the recycling company. This could have been prevented.
* The same with plastic bottles and cans. Team Waste managed to save a *trailer* full of cans and bottles. About 24 big bags (240L). That could easily have been double. And if people actually organized it, it would have been less work.
* Queues at the bar were sometimes very long and slow. Bottleneck during peak times seemed to be the payment terminals, having two or more instead of one terminal would already speed everything up.

=== Cohesion ===
* I like the idea, but not the implementation: Geraffel was put at the arse end of the field (OK fine, epicenter of noise gradient and all that), then got told off for playing music during the day.
* Very little communication/information. People barely knew the team existed and could be contacted, social rules like the Photo Policy were not communicated and very widely ignored. Other events signpost these things all over the site and it does help +1
* Near constant drone flyovers at times and nothing happened to curb it, or even announce it is violating policy (to be fair, I do not know if anyone complained - I did not either, but was severely bothered by the sound alone; like a giant privacy violating mosquito).
* It would be nice if new organizers who joined the field build up for the first time get more included / accepted when they have free time to help out, and NOT to get rejected from tasks. Some of us felt very left out and sad :( (Remember, we're all volunteers and not paid workers, so keep the elitist behavior out of orga please).

=== Content / talks / heralds / speakerdesk / AV / recordings ===

* Party Stage was the perfect location for the "History of Hardcore" talk. More 'serious' talks could be held on the music stages at events going forward.
-> Apart from that hardcore talk, some hacker disconnected the subwoofers, hence why the lack bass during the hardcore talk which kinda sucked but additional security was added after.
* Speakerdesk was very nice! Having a good place to prepare slides and practice a bit was great.
* A better handover process needs to be established from A/V tech + heralds + speakers. Who is putting on microphones, who is checking them.

=== CTF / token game ===

=== Decoration / design ===

* Team did an amazing job. The field felt welcoming and interesting. Thank you so much for all the effort that went in. +2
* Next time we need to find a sponsor to print flags for all visitors, and have it available as merch for purchase. It was sad to see so much deco being liberated too early in the event. We need to also work on the communication around this. +1
* New signs popped up at various places during the event when necessary, very nice to have the Deco team able to accomodate needs last minute and on site.

=== Family / kids ===

- Family field offered lots of entertainment for our kids. Location was perfect, with a direct path to the arcade and silent lounge. You could hear the noise from other fields but it was never overwhelming. Daycare was a blessing.

=== Finance / coins / payments ===

* Like the concept of an anonymous payment card that '''just works'''. Absolutely love the design of the WHY2025 card. And very happy to play with a blank Ultralight AES card afterwards.
** +1, this was set up well! My only feedback would be to maybe have something that you can tap your card against to see the remaining balance (or otherwise instruct angels to communicate the balance upon payment)
* option for payout of remaining funds wasn't communicated properly (even the website claimed it wasn't possible at all). Cash payout would be nice, but would understandably be a big extra thing to manage
* Card payment everywhere is amazing!
* On a few of my shifts (WOC, main bar), the WHY payment card failed to scan on the POS (it popped up a toast message saying no application is registered for this NFC card) and i received conflicting/no information about what to do about it or how to properly use it. Rebooting the POS seemed to help, but i'm more concerned with the conflicting/no training on what to do with it. The card looks great and worked a dream whenever the POS wasn't having trouble scanning it!

=== Information / infodesk / wiki ===

* The wiki seems to have never been updated after the event started. I have attempted to find information about something several times and ''none'' of those times was it on the wiki. Instead everything seemed to be in random Signal groups and wherever else, that I didn't even know about until much later. +1
* It was very hard to find information on anything (like infrastructure, badge handouts, etc.) in general, and even infodesk angels often didn't have the answers.

=== Merchandise ===
* It would have been nice if the merch that was ordered months ago would have actually been available at the field.
* Flags as preordered merchandise. Would create the possibility for hackerspaces and individuals to bring back home some of them. +4

=== NOC / Network ===
* From buildup, through the event, through teardown: the networks worked!
* It was a pleasure to work together, to deduplicate work and equipment.
* In our location, Wifi coverage was poor although we were next to a Datenklo +1
* Wireless kept disconnecting every few minutes for the entire event

=== NUTS / power / water ===

* Showers with adjustable heat (showerheads which mix cold and hot water) to avoid burns. If not possible, less hot is preferred. My partner could not use the shower due to the heat
* Wood pallets outside both showers and toilets to reduce mud. (+1, from day zero would have been helpful)
* Even if not in all bathroom points, more drinking water points other than the one in heaven should have been available from the beginning. +3
* Disable the watertaps at the same time as all the other bathroom facilities. Or communicate when the water is going out. Now villages were only able to fill small containers at the toilets. Or needed to walk all the way to Heaven.
* Slightly more cleaning would have been great. The showers were extremely full of mud even inside at times. Given they only used a hose as far as I saw, should have been possible to also have some angels do this in addition to the cleaning crew.
* Adding hooks to the showers was a very welcome addition, thanks! +1
* It wasn't clear where to get drinking water during the first few days. This should be communicated better, e.g. with signs and on the map. +1
* I liked the number of toilets: never had to wait +3
* furthermore, the toilets seemed to be cleaned often which is good. +3
* There always was toilet paper available in the stalls, greatly lessens anxiety. +4
* water pressure and temperature in the showers was great! Also: never had to wait, which is great! +3
* There always was plenty of soap available at the sinks, during peak time and at night. +3
* Dedicated dishwashing location. +4
* More drinking water fountains across the terrain
* Hoses to fill canisters at drinking water locations - did not find any other location than heaven where it was possible +1
* "upgrading" facilities to "drinking water" is questionable. What of all the potential risks was actually tested and could be guaranteed? Separate 100% clear drinking water spots would be better -1
* Shower temperature constantly fluctuated and never stabilized
* Communication to other teams with regards to their planning would have been heavily appreciated and could have prevented some minor crises (like the logistics traffic jam during buildup)

=== Off-site logistics ===
* Very clear upfront, yet flexible during the event when needed and did a great job transporting and thinking along. Kudos!

=== On-site logistics ===

=== POC / DECT / Fieldphones ===
* micropoc worked just fine: I could easily and quickly register the DECT phones for my village and the network worked whenever I wanted to use it.
* Having the DECT so people can reach my team was as always: amazing. Thank you. Feature request: have a phone number only operational during business hours (and redirect to a prerecorded thing other times). Fixed that ourselves by switching the dect to silent. But would be a cool feature.
* The desk phone, DECTs and the ability to make outside calls were incredibly useful for our team.
* SIP worked great once the wiki instructions were followed. A bit unclear from what date the SIP server was exactly available!

=== Productiehuis / C3VOC ===

* Camera Angels had little to nothing to do, all they did was standing still, because of static shots. It would be more efficient to just leave CAM 1 as a Medium close up shot of the lectern and CAM 2 as a wide shot. Also there's really no need for an intercom system at the FOH which was next to useless.
* A lot of the angel positions could be automated and doesn't really require much hands on work. Apart from Signal Angel, which seems to be the most busy angel type.
* Stagehand Angeltype to be added instead per track instead of A/V Technician per track. Better to use an A/V Technician for purely troubleshooting when needed, those should be on-call instead.
* A use of Dante audio routing + a centralized mixer (with separate mixing matrixes per track would be a more efficient setup) at the VOC tent. (would also cut costs to renting 4x Digital mixers)
* Spykersound's low budget equipment didn't seem too reliable, especially the EV mics and some of the TVs, they also provided the wrong Power supplies to things, there was also lack backup equipment which the supplier packed away too early. (IMHO, I would never hire Spykersound, they seem rather incompetent and annoying to deal with).
* Time management of build up tasks needs to be improved, leaving all remaining tasks to a few hours before opening was not really ideal, there needs to be better planning from the start of build up, some of the organizers arrived early and had little to no tasks to do other than doing other unrelated build up tasks. Also it would be great next time to know when it's the recommended day to join the build up of Productiehuis beforehand, so that people don't use up their energy on other tasks.
* C3VOC is a very efficient team but it would be nice if they could delegate interesting tasks to the rest of the team as well and not hog all the interesting tasks to themselves.
* The placement of the screen on the Andromeda stage was bad. Audience members could only see the top 60% and only the left side, because the rest was obscured by the audience, the speaker lectern or the speaker. When sitting on either the left or right side of the chairs, the screen was obscured by the metal pillars on stage. Please consider the viewing angles from the audience because it was hard to follow talks that relied on their slides for explanation, when those slides cannot be properly seen.

=== Projectleiding ===

=== ROC ===
* Very clear audio and reception
* Was very happy with radio when the relay was up. During the end of teardown the signal degraded to unintelligible gibberish when going across field.
* Next time, don't do a split service desk in warehouse/ROC.
* ROC did a stellar job in running the radio network which saw a lot of action during the various crises and power cuts. Battery life was amazing and I never had issues making a call

=== Safety / security / first aid / fire ===
* Having yellow as the allocated first-aid safety vest color during the event was not the best choice, as it's one of the two most generic safety vest colors people are likely to already have/bring.

=== Supermarket ===
* Happy friendly people who had the correct stuff on the shelves +1
* Pricing was for a campsite supermarket 'okay'. Having stuff available on field makes up for a lot. +1
* Would have loved to be able to purchase anything after 8PM, but i understand that they also need to sleep ;)
* Very resilient, apparently; throughout just about every logistical and infrastructure problem at camp, they seemed to keep operating. Would like to see them back! +1
* Would have liked to see tofu in the assortment; a few vegan proteins were available but none were quite as versatile.
* Instead of installing white tarps on the sides of the supermarket tent, black tarps were installed, making the supermarket uncomfortably warm inside!
* This was a fantastic addition, the supermarket had a good selection and fresh bread every morning.

=== Sysadmin ===

* Setup "live.why2025.org" as an alias for people to easier find the livestreams next time. Right now you needed to go to "streaming.media.ccc.de/why2025".
* IRC is less popular in new generations of hackers and at least Mastodon+Matrix integrations would have made Signal angel role useful.
* Would like a clear messaging channel from Orga/teams to visitors. live.why2025.org would be good. Better than signal. But have no idea what tool to use.

=== Terrain ===

* Noise gradient should be evaluated better: the main party stage was more audible from the family village than from the Belgian cluster, which was way closer.
* Fridge container orientation: the compressor should point away from campers, it was the single most noisy item from Batavus On tour village point of view.
* Infodesk not located at the entrance like at MCH, causing it to be less visible.
* 4000 people but only a single "Hardware Hacking Tent". It was constantly full, and no other places to sit and solder.
** Plenty villages that'll happily let you use their spaces. It makes sense for this kind of thing to be community-provided (the Hardware Hacking Tent was too - while a official workshop spot, it only exists because of of the HHA team willing to equip and run it)
* "Hackcenter" only had space for 20 people, tiny tent, zero cooling, and no advertisement. Not even a sign... We thought it was someone's Village until day 4.
* No place to party/music all night. It would be cool to have a distant (from tents) area where we're allowed to have music going all night long.
** -1, loud music anywhere on the field travels far and I appreciate being able to sleep. I liked the 23:00 cutoff. +1
** -1 agreed. "distant" location is not really possible on-site
** +2 AGREE, the noise cutoff was really annoying, other events the music continues until 2am atleast, I don't see why we can't have somewhere on site where we can play music at a reasonable volume. 23:00 is too early for a festival.
** +1, made the event substancially worse, if we have color-coded fields to match volume levels why do we still have to shut the music down completely at 23:00 in the red area?
** -1, i was very happy to have a camp where i could sleep without earplugs. Also it would be impossible due to very strict permits this time around.
** +1, At Lambda village we choose to be behind the party stage to be loud and partying, but the permit said no amplified noise after 23:00, which made most of the camp dead after this time.
*** also this was not followed on the last night after closing in which the angel party continued in the main bar until very late???? have some consistency please. it just feels mean otherwise.

* it was nice that noise rules were followed quite well this time (unlike e.g. MCH where main stages switched to silent disco while sponsors kept blaring music into the silent areas)

* I missed routing signs for bikes coming in. Google Maps got me to the wooden bridge which was fenced off, and nobody there to either let me in or give me a hint. I may have let myself in at that fence, because it was very unclear which detour to take. The climb was only moderately scary.
* Seperate smoking and non-smoking fields, and designated smoking areas away from event spaces would be appreciated. Quite a few people smoking in busy areas without much attention about people around them, not to mention throwing cigarette butts on the grounds. A blanket ban on smoking and vaping for the entire event is probably to draconian (unfortunately).
* All the big track tents and workshop tents that had black tarps installed instead of white was a really bad idea, it made the interior more like a sauna. Down right unbearable to visit.

=== Tickets / entrance ===
* Putting the desks on the other side might have looked more welcoming, but all was fine for my check-in.
* Camper tickets were not scanned?

=== Villages ===
* Well done! And it was fun to help out villages doing extra luggage shuttles after we were done doing Waste stuff.
* Was very happy with the village planning this time around, we had a very cozy cluster. Thanks a lot!
* Loved that it was possible to rent tents and bedding! (though they got very uncomfortably cold and damp at night, maybe consider waterproof sleeping bags next event)

=== Volunteering / angels / heaven===

* Food tickets given to volunteers expiring, without any communication of them doing so.

[[File:Angel Waterbottle Comparison WHY vs MCH.jpg|thumb|Angle Waterbottle Comparison WHY vs MCH]]

* Waterbottle had boring text "'''Thanks For Volunteering'''", instead of WHY wordplay like "'''We Hydrate You'''", "'''Why Hydrate Yourself?'''" or "'''Wet Hackers, Yay!'''". +1
* Clip/Hook on the waterbootle was 3x smaller, making it unwieldy and difficult to connect. The MCH hook was bigger and easier to quick-connect.
* Drinking part had leak problems, which was not present on the previous bottle.
* The clip caused burn/melt-damage on the waterbottle, as can be seen when zooming in where the clip touches the orange waterbottle.
* No mate during buildup.
* No safe food, or unclear about the contents.
* Severe food safety issues in heaven. Bread toppings (including cheese and meat!) left open on a table outside of a fridge for hours, even overnight, with insects roaming around. No proper cleaning agents or supplies available for cleaning surfaces like tables, only some random supermarket cleaning sprays (this is not good enough for a central eating area!).
* Vegan food availability was unclear and could not be relied on. At times, the "vegan options" were completely inadequate for actually keeping people fed while doing potentially physically intensive volunteer work, with lacking nutritional value. Problem persisted during teardown. "We can't predict what the caterer will deliver" is not good enough for people with dietary restrictions.
* Heaven was too loud. It was almost impossible to communicate with people at the angel desk when there was a meal going on, and you had to practically yell to hear each other. Ideally sound dampening would be installed, but at least the eating area should be separated/insulated from the heaven desk and standby angel area in some way.
* Loved the DasBrot
* Didn't love the utter lack of social hygene during breakfast, lunch and dinner. The proper tools were lacking. Get a cooling gastronorm tray thing for all your meats and cheeses, get the (wasteful) small cups of smears. And have people service it. Dinner handout got fixed with angels doing plating, but was still very haphazard on several days.
* You need more people on the team. You worked your butts off and did not get to enjoy camp enough. I wish better for you all.
* Also get teardown safety vests (or use generic ones for buildup and give a cool one to those tearing down).
* Water-as-a-service trucks were organized well and at a very good frequency during my shifts; however prolonged storing of jerrycans of drinking water unprotected in full sun is not safe.
* Was very happy with the available food during all portions of the event, great job.
* Some more organisation in allocating tasks would probably be helpful. There were numerous cases of people not knowing what to do, and vice-versa teams recruiting angels themselves by approaching them in heaven.
* When calling for standby angels, it's probably better to immediately mention the task instead of just "I need two angels"; that way you can select for people already familiar with the task. Now I often had to ask myself and then someone else would pipe up once they recognized the task.

=== Warehouse ===
* When Boels screwed up, warehouse delivered us a replacement the same day.
- what did boels screw up?
* I appreciate being able to discuss the underlying requirements instead of automatically being handed a solution. When I asked for a bunch of extension cords, it turned out there was a better solution.
* Delivery service made camp a lot better for me as teamlead. I fixed several problems with one phone call and a happy angel heading out on a bike or gator!
* Purchase generic safety vests for use during shifts. All safety vests with branding were taken by people having done buildup.
* Have radio battery charging and exchange either handled by ROC or extend opening hours. I know you guys also need rest, so perhaps have an exchange option that does not require warehouse

=== Waste / garbage collection ===

* I have no knowledge about the state of recycling in NL, but having only separate bins for glass and then ones for everything else felt quite bad. At least separation of paper/carton would have made sense I guess. Also having separate containers where people could "donate" plastic bottles / metal cans which have deposit would have made sense and also could have brought a nice sum of money for the event.
''-> The rules for plastic and metal recycling vary per local municipality, let alone per country. So we decided to not do a plastic/metal sorting bin as it would probably only cause headaches. ''

''-> Paper and food remains were collected seperately at heaven, foodcourt. Agree on extending that to villages.''

''-> Pfand was handled by team bar. Full agree. We saved a trailer full of big bags of bottles and cans.''

* Field was nice and clean until teardown with enough containers to get rid of waste. (+1 for adding at least a paper and deposit container)
* The bins near the villages I was at were always emptied before overflowing, which was nice. On teardown day I saw a big pile of bottles around one of the bins: can't say if glass or deposit ones. Generally the field seemed rather clean.

''-> See above, glass deposit should have been collected. Unclear why it wasn't.''

* Thanks for the motivating music! It was always a pleasure to see you guys roll by.

=== Teardown ===

* "No cars on the gras" policy: Villages that respected the rule of not driving on the grass were effectively disadvantaged. On Wednesday, many cars ignored the rule and drove onto the grass, which meant those villages didn’t have to carry their equipment over long distances. Meanwhile, villages that followed the rule had to transport their gear much farther, which was exhausting given the hot weather. Suggestion: Instead of creating a situation where following the rules feels like a disadvantage, we could reward compliance. For example, check which villages adhere to the rule, and if they do, give them vouchers for a priority ticket queue for the next event.
* Toilets were shut down too early making getting water during the warm teardown harder
* Transporting crates with empty bottles in hand trucks is also very unsafe. If they fall over it would be a mess for barefooted people. Bringing them in and out with cars is much safer.
* Way too many people left a day early. That was a bit sad. For everyone reading this: stay the entire camp ;)
* We should communicate better that flags and other deco is there for the event and should not disappear during the event. Previous events and other events by other parties may have 'trained' our visitors to think they are helping out by removing such decoration early. It was a bit sad to see people rip things of the waste gator. They got told off. But the flags on the main road disappeared on day 2 of camp, and that was entirely unwarranted.
* Remove toilet accessories (paper/soap/brushes) beofore toilets are removed, otherwise they get dumped out on the field.
* Remove zipties of the main tents before tearing the tents down, the tent guys just cut them and leave them on the field.
* Not enough hi-vis vests available, which is especially unsafe when heavy machinery is roaming the site.
* There didn't seem to be any documentation of the teardown procedure for angels, which made it difficult to plan things like food and sleep.
* The to-do whiteboard on the last few days helped a lot with clarity, highly appreciated!

Village:Lambda

2025-08-17T18:55:16Z

Xylitol:

{{Village
|Has name=Lambda
|Has description=French Village with Crepe & DJ
|Related to village=Village:Brittany Fairies
|Has village tag=Free Beer/Cofee, InfoSec, Cyber Circus, Whiskyleaks, electronics, retro computing
|Provides session location=No
|Location=52.68989, 4.74299
|Has orga contact=lambda_why@proton.me
|On site orga contact=vertrex
|Village citizen count=12
|Village Needs power=Smaller Village (up to 2x 230V/Schuko)
|Village size needed=50
|Village hacktents num=0
|Village brings big stuff=No
}}

== Arrival on site / Buildup ==

{| class='h wikitable smwtable table sortable'
! Villagers !! Location (From) !! How !! Arrival-departure
|-
| [[User:Xylitol|Xylitol]], Lucie || France || plane, train || 07/08/2025 - 13/08/2025
|-
| [[User:Thanat0s|Thanat0s]], Xanax || France || car || 07/08/2025 - 13/08/2025
|-
| [[User:Vertrex|Vertrex]], || France || train,car ? || 07/08/2025 : ~18h00 - 12/08/2025 : ~14h00
|-
| [[User:Miizix|Miizix]] || France || car || 07/08/2025 - 13/08/2025 ||
|-
| [[User:Saturne|Saturne]], Frédéric || Paris, France || bus+train+bus || 06/08/2025 - 13/08/2025
|-
| [[User:Maxou56800|Maxou56800]]|| France (Brittany) || car || 07/08/2025 - 13/08/2025
|-
| [[User:Rbnctl|rbnctl]]|| France (Brittany) || car || 07/08/2025 - 13/08/2025
|-
| [[User:Tweety|tweety]]|| France || train || 07/08/2025 - 12/08/2025
|}

== Village Infra ==

{| class='h wikitable smwtable table sortable'
! What !! Location (From) !! Who !! Comment
|-
| 1x Tent 5 m x 5 m || Team Moebelhaus || Solal ||
|-
| 1x Tent Sahara 400 || own stuff || Thanat0s/Xanax || Probably not sleeping here :)
|-
| 1x 3-Person Tent || own stuff || Benoit ||
|-
| 1x 3-Person Tent || own stuff || Maxou56800 ||
|-
| 1x 2-Person Tent || own stuff || rbnctl ||
|-
| 1x 1-Person Tent || Why's stuff || Miizix ||
|-
| 1x MH100 XL || own stuff || Xyl2k || …
|-
| 1x MH100 || own stuff || Solal ||
|-
| 8x chairs || own stuff || Thanat0s || …
|-
| 6x chairs || own stuff || rbnctl ||
|-
| 1x table 4 places || own stuff || rbnctl ||
|-
| DJ Set || own stuff || Benoit ||
|-
| Fire extinguisher (CO2) || own stuff || Maxou56800 ||
|-
| Looooonng Power cords || own stuff || Thanat0s || 1x25m IP52
|-
| Power cords || own stuff || Miizix || 1x15m IP52
|-
| Table Treteaux || own stuff || Thanat0s || 170x90
|-
| Goban || own stuff || tweety || 19x19
|}

== Lambda ==

[[File:Lambda_village.jpg|700px|thumb|left|The village]]

<pre>
let main = (a => (b => (c => (d => (e => (f => (g => (h => (i => (j => (k => (l => (m => (
n => (o => (p => (q => (r => (s => (t => (u => (v => (w => (x => (Y => (y=>(z=>dl=>dv=>dl(
z(dv)(x)))(Y(y)))(z => f => l => l(x => xs => w(f(x))(z(f)(xs)))(v)))(f => (x => f(z => x(
x)(z))) (x => f(z => x(x)(z)))))( w(o)(w(p)(w(q)(w(q)(w(r)(w(s)(w(t)(w(o)(w(u)(v))))))))))
)(a => l => c => n => c(a)(l)))( c => n => n))(f(c)(t)))(f(o)(g(d)(j))))(h(c)(j)))(g(d)(e(
g(i)(l)))))(g(i)(h(d)(d))))(e(n)))(g(l)(k)))(g(h(c)(c))(h(j)(c))))(e(e(l))))(h(d)(c)))(h(c
)(d)))(f(c)(d)))(e(d)))(x => y => y(x)))(x => y => f => x(y(f))))(x => y => x(e)(y)))(x =>
f => s => f(x(f)(s))))(f => x => f(f(f(x)))))(f => x => f(f(x))))(f => x =>f(x)))(f=>x=>x)
//
// main is pure lambda calculus, created using only:
// - `x`: Variable
// - `λx.x`: Abstraction
// - `x x`: Application
//
// Helpers to interpret the lambda code:
let decode_list = a => l => l(x => xs => decode_list(a.concat([x]))(xs))(a)
let decode_number = n => n(x => x + 1)(0)
console.log(String.fromCharCode(...main(decode_list([]))(decode_number)))
</pre>

File:Lambda village.jpg

2025-08-17T18:52:43Z

Xylitol: lambda village

== Summary ==
lambda village

User:Xylitol

2025-08-17T18:46:46Z

Xylitol:

{{UserInfo
|Bringing=Gameboy camera, stickers
|Village=Village:Lambda
|Working on=Project:Game Boy camera trip report, Project:Mario Kart 64 why edition
|IRC=Xylitol
|DECT=2077
|Callsign=14 FRS 1749
|Languages=EN,FR
|HackerSpace=Hackgyver
}}
== 👤 Xylitol ==

Hello! I'm '''Xylitol''', a hacker and tinkerer from '''France'''.
I'll be with [[Village:Lambda]].

I'm passionate about:
* The demoscene ([https://www.pouet.net/user.php?who=55526 My Pouët ID])
* '''Hacking''' and '''reverse engineering'''
* '''Electronics''', especially '''high-voltage''' experiments

I'm a member of the [https://hackaday.io/hackerspace/1374-hackgyver-20 HackGyver hackerspace] in '''Belfort'''.

I've attended '''CCCamp''', but '''Why2025''' is my first time at a '''Dutch hacker camp''', and I’m excited to be here!

Since I’m coming by plane with my girlfriend, I won’t bring too much gear, but still:

'''I’ll be bringing:'''
* A few '''stickers''' (grab one!)
* My '''hackerspace passport''' (looking for stamps!)
* '''Flipper Zero'''
* '''Baofeng GT3/UV5R'''
* My custom board for '''Craft''' and '''Phasor''' by [https://www.linusakesson.net/ lft]
* A '''Game Boy Camera setup''' for our Wild Demo: [[Project:Game_Boy_camera_trip_report]]

'''📞 DECT at camp:''' 2077

* 📷 My photos of the camp: https://www.flickr.com/groups/why2025/pool/203273471@N08/
* 🎥 My video report of the camp: https://files.scene.org/view/parties/2025/why25/misc/hg-why2025-trip-report.zip

Project:Game Boy camera trip report

2025-08-17T18:04:19Z

Xylitol:

{{Projects
|Name=Game Boy Camera Trip Report
|Has project tag=Art, Demoscene
|Has description=We plan to film around the campsite and create a Wild Demo to be submitted to the Field-FX demoparty. The project aims to capture the spirit of the event and its creative atmosphere.
|Located at village=Village:Lambda
}}
For the hypothetical demoparty with Wild entries organized by the [https://wiki.why2025.org/Village:Demoscene Village Demoscene]

We ([[User:Xylitol|Xylitol]], [[User:Miizix|Miizix]]) plan to walk around the campsite with a Game Boy Camera to capture the spirit of the event and create a demo from it.

We’re aware of the camp rules regarding photo and video, so the first days of the project will be spent asking villages for permission to film.

Since we don’t have a direct mailing list for communication, we’ll reach out in person to see which villages would like to participate.

== Be part of the project ==

If your village has something interesting to showcase and you'd like to be featured in the demo, feel free to contact us or edit this page to add your village.

You can contact Xylitol by calling 2077, visiting Village Lambda, or spotting the nerd with short hair and a Game Boy T-shirt wandering around.

Filming will most likely take place in the afternoons, since the Game Boy Camera requires good lighting and doesn't perform well in low-light conditions.

The exact filming schedule will depend on the submission deadline for the FieldFX demoparty, as we aim to complete the demo in time for the event.

'''Musician Wanted!'''

We're looking for a musician to contribute an original track to our demoscene project.

We already have a reference track in mind that we will use, but if we receive something original, preferably in a calm, lo-fi guitar style we’d be happy to feature your track instead!

Please note: the music must comply with the rules of the FieldFX demoparty. That likely means it must be entirely your own creation, no remixes, no covers, no unauthorized vocals samples.

=== Village list, eager to be visited ===
You can add your village here, and we will happily come to you.
** [[Village:Lambda]]
** [[Village:Britanny_Fairies]]
** [[Village:CTF]] - Specifically the CTF Tent (marked on the field) - We got a Gameboy challenge in the CTF! ;-)

== Hardware/setup ==

Because the Game Boy Camera wasn’t originally intended for video capture, we’ve built a custom recording setup, packed into a backpack.
'''Main setup include:'''
** Dell XPS 17 9720 laptop
** Elgato HD60 X capture card
** Analogue Pocket (docked).
** Modified Game Boy Camera with a homemade extension cable separating the camera head from the cartridge
** OBS Studio (running on the Dell XPS for recording)

'''Additional gear:'''
** One GB Camera PicNRec AIO with "Photo! v1.10" firmware by untoxa
** One Analogue Super Nt with a Super Game Boy 2 cartridge
** One unmodified Game Boy Camera (for backup)
** A 20,000mAh power bank to power the Pocket dock
** Possibly an external screen + additional power bank to monitor the feed, as the laptop lid will remain closed inside the backpack

[[File:Hardware_backpack.jpg|alt=setup used in the backpack for the project]]

Let us know if you're interested, and we look forward to documenting the camp’s creative energy through pixelated Game Boy magic!

== Final result ==

We didn’t have the time to submit our entry in time for the Why25 demoparty, but instead we released it afterwards.

This practice was quite common in the late 90s and 2000s, when demoparties often had video reports released shortly after the event.

This report is not part of the competition, but it still remains associated with the event.

You can download it from scene.org (52.15Mb): [https://files.scene.org/view/parties/2025/why25/misc/hg-why2025-trip-report.zip files.scene.org/view/parties/2025/why25/misc/hg-why2025-trip-report.zip]

Thanks also to Pastagang for the teamup and friendship on the camp.

[[File:Hg-report-why2025.mp4.jpg|1000px|thumb|left|Caption]]

File:Hg-report-why2025.mp4.jpg

2025-08-17T18:00:39Z

Xylitol: thumbnail of the vid

== Summary ==
thumbnail of the vid

Badge

2025-08-05T22:01:39Z

Xylitol: /* 3mm Full-frame Spacer Status */

<div class="col-wrap-col-50">
{{whybox|title=WHY2025 Badge|content=
* [https://why2025.org/post/494 Blogpost 01]
* [https://why2025.org/post/697 Blogpost 02]
* [https://www.youtube.com/watch?v=-uMUSUYVGkU WHYCast Episode41]
* [https://tweakers.net/geek/237414/dit-is-de-why2025-badge-met-twee-esp32s-en-een-loramodule.html Tweakers article]
* [https://gitlab.com/why2025/team-badge Team:Badge GitLab repo] (files + documentation)
* [https://badge.why2025.org/ BadgeHub]
* WHY2025 Badge comes with two 18650 round battery cells, you don't need to buy cells before the event.
* ⚠️ [[Badge/Fire hazard]]
}}
</div>
 

Yes, we have a dedicated '''WHY2025 Badge Updates''' Signal group.

-> Feel free to share this new - '''WHY2025 Badge Updates''' - Signal group link with everyone at WHY2025.

https://signal.group/#CjQKINdiQ_2mg4ZIZ9AbjD5UHq8gnIgRojSTnOb6lbx-Tvh_EhDHBzcPicIer3NabcN0fuR9

yes, we're expecting this to become a big one :)

Thank you.

== We could use your help. ==

We need your support for printing the 3mm Full-frame Spacer.

If you want to help out then join the Signal group.

[https://signal.group/#CjQKIBzawhrMtrLuA-5d-J9omT2VW5gqnvtaXRbojytjGzoeEhAzItv1WoFWVkqlxx3GTaZc 3D printed spacer - Signal group]

Do you have a 3D printer and want to help print badge cases or spacers? Great.

=== 3mm Full-frame Spacers ===

We still need many more of these 3mm Full-frame spacers, any contributions are much appreciated.

Get the STL from [https://gitlab.com/why2025/team-badge/Hardware/-/blob/main/Spacer/3d_print/Full_Spacer_with_LoRa_Antenna_WHY2025.stl?ref_type=heads our Gitlab].

A few notes on printing:
* Most prints will be in PLA, so use that if possible.
* Avoid stack prints or anything that might create uneven surfaces on the prints.
* Color doesn't matter - use whatever you'd like.

* There are two options for the spacer thickness endresult:
* Option 1. A spacer thickness of 3mm everywhere. This is great.
* Option 2. A spacer thickness of 3mm in the top part. That is the display area.
* and 2.9 mm in the lower part. That is the keyboard area.

* There will be some 3D printers available at camp, so printing will continue during the event, but the more units we can make before then, the better.

== 3mm Full-frame Spacer Status ==

=== Current Contributors ===
{| class="wikitable"
|+ Full-frame Spacer Contributors
|-
! Number
! Credits to
! Printer
! Layer
|-
| 660 || [[Village:Geraffel]] [[File:Geraffel 3D black.jpg|80px|thumb]] || YES, MANY ||
|-
| 250 || Sander || BambuLab H2D & X1C ||
|-
| 42 || {{UserLink|Jelmo2}} || ||
|-
| 34 || Rens Verhoeven || ||
|-
| 63 || {{UserLink|Edwinm}} || Prusa MK3 || 0.20mm
|-
| 12 || Gregor || ||
|-
| 30 || Fabian || ||
|-
| 28 || NinjaLikesCheeze || ||
|-
| >125 || Klaas ({{UserLink|KlaasYK}}) || Prusa Mk4 & Mk3S with emotional support from Ender 5 Pro and Friend <3 ||
|-
| 3 || Wouter || ||
|-
| 19 || Saskia ({{UserLink|Sassy}}) || Prusa MK4S || 0.20mm
|-
| 80 || {{UserLink|rick}} || Prusa MK4S|| 0.20mm
|-
| 58 || Wouter ({{UserLink|Pa3weg}}) || Bambu LAN P1S || 0.20mm
|-
| >45 || Alex ({{UserLink|Tinyledmatrix}}) || Prusa MK2, Bambulab A1 Mini, Qidi X-Smart3 ||
|-
| 50 || Jan-Willem ({{UserLink|jwrm22}}) || Bambu Lab P1S || 0.20mm, suport material stacks
|-
| 96 || Michael ({{UserLink|MikeS}}) || Prusa MK3.9 and two dusted off MK2.5's ||
|-
| >50 || Henri ({{UserLink|Fashice}}) || ||
|-
| >20 || {{UserLink|Dude77}} || Bambu Lab P1S || 0.20mm
|-
| 4 || {{UserLink|Luxim}} || Ender 3 v3 KE || 0.20mm
|-
|11 || {{UserLink|Galactum}} || Bambu Lab A1 || 0.20mm
|-
|20 || {{UserLink|MagicalDuck}} || Ender 3 || 0.24mm
|-
|>10 || {{UserLink|Willow}} || Bambu Lab P1S || 0.20mm
|-
|15 || {{UserLink|Jap}} || Bambu Lab P1S || 0.20mm
|-
|>10 || {{UserLink|Habbie}} || Bambu Lab A1 || 0.20mm
|-
|>10 || {{UserLink|Sndrsmnk}} || Bambu Lab P1S || 0.20mm
|-
|4 || {{UserLink|LordGaav}} || Voron V2.4 (V2.4523) || 0.20mm
|-
|4 || {{UserLink|Xylitol}} || CR-10S Pro || 0.20mm
|-
| ??? || You? || ||
|}

Current total: '''>1753''' units printed / 3500 needed (50%)

Add your amount and name to this list. Thank you.

== Badge Case Info ==

Currently cases are designed around the prototype PCBs. The final boards might be slightly different, so best advise is currently to wait until (after) the camp with printing one - the badges will be usable without a case. Instead, maybe help with printing the 3mm full-frame spaces (see above).

• Designing your own case? Use the existing screw holes on the badge.
• Bring M2 screws, up to 15 mm in length depending on your case design.
• Badges function fully without a case.
• Note: Cases take much longer to print than spacers.

Case Examples by the community:
https://www.printables.com/model/1372316-why2025-badge-case

== Badge Assembly at BadgeTent ==

We aim to conduct the full-scale assembly during the whole day of Friday, which will involve a maximum of 30 volunteers working in the 15*15 meters BadgeTent.

Assembly involves screwing everything together.

Assembling your first '''WHY2025''' badge might feel overwhelming, that’s okay.

Take your time, explore the parts, and build confidence.

With repetition:
* 1st time = You're learning. -> Instructions on how to handle the components will be provided.
* 5th time = You gain confidence by knowing your tools and how to grab them the best way.
* 500th time = Congratulations, you have accomplished the assembly and will have a Foxconn recruiter on the line.

Parts to assemble:
* CarrierBoard
* Keyboard Dome Layer
* Keyboard Silicon Layer
* 3mm Spacers
* 4x M2 Screws
* Front Panel PCB

If you want to help out in the Badge Assembly on Friday during the day -> then join this Signal group.

[https://signal.group/#CjQKIIORCgY9yjX3a834iz-RQeOQu80fIZtg-i3G56EYqnaQEhBaRn9aHmtLggM6oH7dWXC5 Badge Assembly - Signal group].

== Badge handout at BadgeTent ==

Starting: Friday 19:00 at BadgeTent

== LoRa Details ==

• The LoRa connector will not be pre-soldered but will be handed out as a compontent separately.

• You’ll also receive a screw-on LoRa antenna.

== Photo Sections ==

Pictures of 3D printed Full-frame Spacers:

[[File:Signal-2025-08-04-11-10-44-889.jpg|300px]]

[[File:Geraffel printed.jpg|300px]]

Pictures of WHY2025 Badge Cases:

[[File:Signal-2025-08-03-15-22-08-679.jpg|300px]]

[[File:Signal-2025-08-03-15-22-15-031.jpg|300px]]

[[File:20250804_140303.jpg|300px]]

Pictures of Final WHY2025 Badges with LoRa Antenna:

Project:Mario Kart 64 why edition

2025-08-05T13:43:01Z

Xylitol: Created page with "{{Projects |Name=Mario Kart 64 WHY edition |Has project tag=video games |Has description=A chaotic, high-speed ROM hack of Mario Kart 64 designed for hardcore races and meme-fueled madness. }} == Mario Kart 64: WHY2025 Edition == The ROM hack nobody asked for, and everyone deserves. Buckle up, because hardcore mode just got a political upgrade. In this chaotic high-speed remix of the N64 classic. == Notable Features == * '''Everything is faster.''' You, the CPU-cont..."

{{Projects
|Name=Mario Kart 64 WHY edition
|Has project tag=video games
|Has description=A chaotic, high-speed ROM hack of Mario Kart 64 designed for hardcore races and meme-fueled madness.
}}
== Mario Kart 64: WHY2025 Edition ==
The ROM hack nobody asked for, and everyone deserves. Buckle up, because hardcore mode just got a political upgrade. In this chaotic high-speed remix of the N64 classic.

== Notable Features ==
* '''Everything is faster.''' You, the CPU-controlled opponents, the chaos. Blink and you're off Rainbow Road.
* '''All character textures are hacked.''' Battle against Zuck’s pixelated surveillance kart while Luigi’s face melts in 12-bit agony.

== Character Roster ==

* '''Danny (Tourette Guy)''' – Yells at invisible furniture and spins out for no reason. May randomly win the race or forget he's in one.
* '''Slavik (Zeus Gameover)''' – Siphons your kart’s coins into an offshore wallet. No one’s ever seen him finish last.
* '''Hayden''' – Ex-NSA/CIA director. Knows your driving habits before you start, Might use an EternalBlue spike shell who can crash the karts and phones home.
* '''Kim''' – Dictator Kim joins the roster. Try not to get nuked.
* '''Mark ("Zuck")''' – Shows no emotion, never blinks, and legally owns your kart data the moment the race begins.
* '''Trump''' – Trump is here. But wait, he only speaks in Harambe noises. Why? We don't know either.
* '''Krebs''' – The journalist-turned-juggernaut who reports cybercrime while drifting at 150 MPH. Mention his name and half the track mysteriously loses connection.
* '''Mikko''' – The legendary infosec expert trades malware reports for banana peels and he’s out for blood.

''Sorry, no Musk and Cybertruck.''

Whether you're drifting through meme history or just trying to survive a 1000cc Mushroom Cup, this edition of Mario Kart 64 is pure, glorious nonsense.

== Looking 4 Hardware ==
This ROM hack has been tested on a '''real Nintendo 64 hardware''' using a flash cartridge. While mostly stable, players should expect occasional crashes or glitches due to the extreme speed modifications.

It has also been tested on several emulators. Ironically, the hack is '''more stable on real hardware''' than on emulators, where performance can vary.

'''We are currently looking for a village or someone who can supply a Nintendo 64 console''' and host a community racing event. Please reach out to '''village Lambda''' if you can help!
We’ll bring the flash cartridge. You bring the chaos.

== Download ==
You can download the ROM (16mb, .Z64) [http://temari.fr/temp/MK64_WHY2025.zip here] If you want to train, put it on your emulator or flashcart for the event.

== Screenshot ==

[[File:Mariokartwhy.jpg|alt=The ROM running on a N64 Console]]

File:Mariokartwhy.jpg

2025-08-05T13:39:21Z

Xylitol: Mario Kart 64, why2025 version

== Summary ==
Mario Kart 64, why2025 version

Project:Game Boy camera trip report

2025-08-02T12:07:31Z

Xylitol:

{{Projects
|Name=Game Boy Camera Trip Report
|Has project tag=Art, Demoscene
|Has description=We plan to film around the campsite and create a Wild Demo to be submitted to the Field-FX demoparty. The project aims to capture the spirit of the event and its creative atmosphere.
|Located at village=Village:Lambda
}}
For the hypothetical demoparty with Wild entries organized by the [https://wiki.why2025.org/Village:Demoscene Village Demoscene]

We ([[User:Xylitol|Xylitol]], [[User:Gadget_MCS|Gadget_MCS]], Lou) plan to walk around the campsite with a Game Boy Camera to capture the spirit of the event and create a demo from it.

We’re aware of the camp rules regarding photo and video, so the first days of the project will be spent asking villages for permission to film.

Since we don’t have a direct mailing list for communication, we’ll reach out in person to see which villages would like to participate.

== Be part of the project ==

If your village has something interesting to showcase and you'd like to be featured in the demo, feel free to contact us or edit this page to add your village.

You can contact Xylitol by calling 2077, visiting Village Lambda, or spotting the nerd with short hair and a Game Boy T-shirt wandering around.

Filming will most likely take place in the afternoons, since the Game Boy Camera requires good lighting and doesn't perform well in low-light conditions.

The exact filming schedule will depend on the submission deadline for the FieldFX demoparty, as we aim to complete the demo in time for the event.

'''Musician Wanted!'''

We're looking for a musician to contribute an original track to our demoscene project.

We already have a reference track in mind that we will use, but if we receive something original, preferably in a calm, lo-fi guitar style we’d be happy to feature your track instead!

Please note: the music must comply with the rules of the FieldFX demoparty. That likely means it must be entirely your own creation, no remixes, no covers, no unauthorized vocals samples.

=== Village list, eager to be visited ===
You can add your village here, and we will happily come to you.
** [[Village:Lambda]]

== Hardware/setup ==

Because the Game Boy Camera wasn’t originally intended for video capture, we’ve built a custom recording setup, packed into a backpack.
'''Main setup include:'''
** Dell XPS 17 9720 laptop
** Elgato HD60 X capture card
** Analogue Pocket (docked).
** Modified Game Boy Camera with a homemade extension cable separating the camera head from the cartridge
** OBS Studio (running on the Dell XPS for recording)

'''Additional gear:'''
** One GB Camera PicNRec AIO with "Photo! v1.10" firmware by untoxa
** One Analogue Super Nt with a Super Game Boy 2 cartridge
** One unmodified Game Boy Camera (for backup)
** A 20,000mAh power bank to power the Pocket dock
** Possibly an external screen + additional power bank to monitor the feed, as the laptop lid will remain closed inside the backpack

[[File:Hardware_backpack.jpg|alt=setup used in the backpack for the project]]

Let us know if you're interested, and we look forward to documenting the camp’s creative energy through pixelated Game Boy magic!

User:Xylitol

2025-08-02T11:48:01Z

Xylitol:

{{UserInfo
|Bringing=Gameboy camera, stickers
|Village=Village:Lambda
|Working on=Project:Game Boy camera trip report
|IRC=Xylitol
|DECT=2077
|Callsign=14 FRS 1749
|Languages=EN,FR
|HackerSpace=Hackgyver
}}
== 👤 Xylitol ==

Hello! I'm '''Xylitol''', a hacker and tinkerer from '''France'''.
I'll be with [[Village:Lambda]].

I'm passionate about:
* The demoscene ([https://www.pouet.net/user.php?who=55526 My Pouët ID])
* '''Hacking''' and '''reverse engineering'''
* '''Electronics''', especially '''high-voltage''' experiments

I'm a member of the [https://hackaday.io/hackerspace/1374-hackgyver-20 HackGyver hackerspace] in '''Belfort'''.

I've attended '''CCCamp''', but '''Why2025''' is my first time at a '''Dutch hacker camp''', and I’m excited to be here!

Since I’m coming by plane with my girlfriend, I won’t bring too much gear, but still:

'''I’ll be bringing:'''
* A few '''stickers''' (grab one!)
* My '''hackerspace passport''' (looking for stamps!)
* '''Flipper Zero'''
* '''Baofeng GT3/UV5R'''
* My custom board for '''Craft''' and '''Phasor''' by [https://www.linusakesson.net/ lft]
* A '''Game Boy Camera setup''' for our Wild Demo: [[Project:Game_Boy_camera_trip_report]]

'''📞 DECT at camp:''' 2077

User:Xylitol

2025-08-02T11:44:39Z

Xylitol:

{{UserInfo
|Bringing=Gameboy camera, stickers
|Village=Village:Lambda
|Working on=Project:Game Boy camera trip report
|IRC=Xylitol
|DECT=2077
|Callsign=14 FRS 1749
|Languages=EN,FR
|HackerSpace=Hackgyver
}}
== 👤 Xylitol ==

Hello! I'm '''Xylitol''', a hacker and tinkerer from '''France'''.
I'll be with [[Village:Lambda]].

I'm passionate about:
* The demoscene ([https://www.pouet.net/user.php?who=55526 My Pouët ID])
* '''Hacking''' and '''reverse engineering'''
* '''Electronics''', especially '''high-voltage''' experiments

I'm a member of the [https://hackaday.io/hackerspace/1374-hackgyver-20 HackGyver hackerspace] in '''Belfort'''.

I've attended '''CCCamp''', but '''Why2025''' is my first time at a '''Dutch hacker camp''', and I’m excited to be here!

Since I’m coming by plane with my girlfriend, I won’t bring too much gear, but still:

'''I’ll be bringing:'''
* A few '''stickers''' (grab one!)
* My '''hackerspace passport''' (looking for stamps!)
* '''Flipper Zero'''
* My custom board for '''Craft''' and '''Phasor''' by [https://www.linusakesson.net/ lft]
* A '''Game Boy Camera setup''' for our Wild Demo: [[Project:Game_Boy_camera_trip_report]]

'''📞 DECT at camp:''' 2077

User:Xylitol

2025-08-02T11:31:31Z

Xylitol:

{{UserInfo
|Bringing=Gameboy camera, stickers
|Village=Village:Lambda
|Working on=Project:Game Boy camera trip report
|DECT=2077
|Languages=EN,FR
|HackerSpace=Hackgyver
}}
== 👤 Xylitol ==

Hello! I'm '''Xylitol''', a hacker and tinkerer from '''France'''.
I'll be with [[Village:Lambda]].

I'm passionate about:
* The demoscene ([https://www.pouet.net/user.php?who=55526 My Pouët ID])
* '''Hacking''' and '''reverse engineering'''
* '''Electronics''', especially '''high-voltage''' experiments

I'm a member of the [https://hackaday.io/hackerspace/1374-hackgyver-20 HackGyver hackerspace] in '''Belfort'''.

I've attended '''CCCamp''', but '''Why2025''' is my first time at a '''Dutch hacker camp''', and I’m excited to be here!

Since I’m coming by plane with my girlfriend, I won’t bring too much gear, but still:

'''I’ll be bringing:'''
* A few '''stickers''' (grab one!)
* My '''hackerspace passport''' (looking for stamps!)
* My custom board for '''Craft''' and '''Phasor''' by [https://www.linusakesson.net/ lft]
* A '''Game Boy Camera setup''' for our Wild Demo: [[Project:Game_Boy_camera_trip_report]]

'''📞 DECT at camp:''' 2077

Project:Game Boy camera trip report

2025-08-02T10:39:44Z

Xylitol:

{{Projects
|Name=Game Boy Camera Trip Report
|Has project tag=Art, Demoscene
|Has description=We plan to film around the campsite and create a Wild Demo to be submitted to the Field-FX demoparty. The project aims to capture the spirit of the event and its creative atmosphere.
|Located at village=Village:Lambda
}}
For the hypothetical demoparty with Wild entries organized by the [https://wiki.why2025.org/Village:Demoscene Village Demoscene]

We ([[User:Xylitol|Xylitol]], [[User:Gadget_MCS|Gadget_MCS]], Lou) plan to walk around the campsite with a Game Boy Camera to capture the spirit of the event and create a demo from it.

We’re aware of the camp rules regarding photo and video, so the first days of the project will be spent asking villages for permission to film.

Since we don’t have a direct mailing list for communication, we’ll reach out in person to see which villages would like to participate.

== Be part of the project ==

If your village has something interesting to showcase and you'd like to be featured in the demo, feel free to contact us or edit this page to add your village.

You can contact Xylitol by calling 2077, visiting Village Lambda, or spotting the nerd with short hair and a Game Boy T-shirt wandering around.

Filming will most likely take place in the afternoons, since the Game Boy Camera requires good lighting and doesn't perform well in low-light conditions.

The exact filming schedule will depend on the submission deadline for the FieldFX demoparty, as we aim to complete the demo in time for the event.

'''Musician Wanted!'''

We're looking for a musician to contribute an original track to our demoscene project.

We already have a reference track in mind that we will use, but if we receive something original, preferably in a calm, lo-fi guitar style we’d be happy to feature your track instead!

Please note: the music must comply with the rules of the FieldFX demoparty. That likely means it must be entirely your own creation, no remixes, no covers, no unauthorized vocals samples.

== Hardware/setup ==

Because the Game Boy Camera wasn’t originally intended for video capture, we’ve built a custom recording setup, packed into a backpack.
'''Main setup include:'''
** Dell XPS 17 9720 laptop
** Elgato HD60 X capture card
** Analogue Pocket (docked).
** Modified Game Boy Camera with a homemade extension cable separating the camera head from the cartridge
** OBS Studio (running on the Dell XPS for recording)

'''Additional gear:'''
** One GB Camera PicNRec AIO with "Photo! v1.10" firmware by untoxa
** One Analogue Super Nt with a Super Game Boy 2 cartridge
** One unmodified Game Boy Camera (for backup)
** A 20,000mAh power bank to power the Pocket dock
** Possibly an external screen + additional power bank to monitor the feed, as the laptop lid will remain closed inside the backpack

[[File:Hardware_backpack.jpg|alt=setup used in the backpack for the project]]

Let us know if you're interested, and we look forward to documenting the camp’s creative energy through pixelated Game Boy magic!

Project:Game Boy camera trip report

2025-08-02T10:29:32Z

Xylitol:

{{Projects
|Name=Game Boy Camera Trip Report
|Has project tag=Art, Demoscene
|Has description=We plan to film around the campsite and create a Wild Demo to be submitted to the Field-FX demoparty. The project aims to capture the spirit of the event and its creative atmosphere.
|Located at village=Village:Lambda
}}
For the hypothetical demoparty with Wild entries organized by the [https://wiki.why2025.org/Village:Demoscene Village Demoscene]

We ([[User:Xylitol|Xylitol]], [[User:Gadget_MCS|Gadget_MCS]], Lou) plan to walk around the campsite with a Game Boy Camera to capture the spirit of the event and create a demo from it.

We’re aware of the camp rules regarding photo and video, so the first days of the project will be spent asking villages for permission to film.

Since we don’t have a direct mailing list for communication, we’ll reach out in person to see which villages would like to participate.

== Be part of the project ==

If your village has something interesting to showcase and you'd like to be featured in the demo, feel free to contact us or edit this page to add your village.

You can contact Xylitol by calling 2077, visiting Village Lambda, or spotting the nerd with short hair and a Game Boy T-shirt wandering around.

Filming will most likely take place in the afternoons, since the Game Boy Camera requires good lighting and doesn't perform well in low-light conditions.

The exact filming schedule will depend on the submission deadline for the FieldFX demoparty, as we aim to complete the demo in time for the event.

'''Musician Wanted!'''

We're looking for a musician to contribute an original track to our demoscene project.

We already have a reference track in mind that we will use, but if we receive something original, preferably in a calm, lo-fi guitar style we’d be happy to feature your track instead!

Please note: the music must comply with the rules of the FieldFX demoparty. That likely means it must be entirely your own creation, no remixes, no covers, no unauthorized vocals samples.

== Hardware/setup ==

Because the Game Boy Camera wasn’t originally intended for video capture, we’ve built a custom recording setup, packed into a backpack.
'''Main setup include:'''
** a Dell XPS 17 9720 laptop
** Elgato HD60 X capture card
** Analogue Pocket (docked).
** Modified Game Boy Camera with a homemade extension cable separating the camera head from the cartridge
** OBS Studio (running on the Dell XPS for recording)

'''Additional gear:'''
** One GB Camera PicNRec AIO with "Photo! v1.10" firmware by untoxa
** One Analogue Super Nt with a Super Game Boy 2 cartridge
** One unmodified Game Boy Camera (for backup or comparison)
** A 20,000mAh power bank to power the Pocket dock
** Possibly an external screen + additional power bank to monitor the feed, as the laptop lid will remain closed inside the backpack

[[File:Hardware_backpack.jpg|alt=setup used in the backpack for the project]]

Let us know if you're interested, and we look forward to documenting the camp’s creative energy through pixelated Game Boy magic!

File:Hardware backpack.jpg

2025-08-02T10:26:14Z

Xylitol: Setup used for the Game Boy camera trip report project

== Summary ==
Setup used for the Game Boy camera trip report project

User:Xylitol

2025-08-02T10:04:02Z

Xylitol:

{{UserInfo
|Bringing=Gameboy camera, stickers
|Village=Village:Lambda
|Working on=Project:Game Boy camera trip report
|Languages=EN,FR
|HackerSpace=Hackgyver
|NickName={{PAGENAME}}
}}

Project:Game Boy camera trip report

2025-08-02T09:59:29Z

Xylitol: A lo-fi documentary of Why2025

{{Projects
|Name=Game Boy Camera Trip Report
|Has project tag=Art, Demoscene
|Has description=We plan to film around the campsite and create a Wild Demo to be submitted to the Field-FX demoparty. The project aims to capture the spirit of the event and its creative atmosphere.
|Located at village=Village:Lambda
}}
For the hypothetical demoparty with Wild entries organized by the [https://wiki.why2025.org/Village:Demoscene Village Demoscene]

We ([[User:Xylitol|Xylitol]], [[User:Gadget_MCS|Gadget_MCS]], Lou) plan to walk around the campsite with a Game Boy Camera to capture the spirit of the event and create a demo from it.

We’re aware of the camp rules regarding photo and video, so the first days of the project will be spent asking villages for permission to film.

Since we don’t have a direct mailing list for communication, we’ll reach out in person to see which villages would like to participate.

== Be part of the project ==

If your village has something interesting to showcase and you'd like to be featured in the demo, feel free to contact us or edit this page to add your village.

You can contact Xylitol by calling 2077, visiting Village Lambda, or spotting the nerd with short hair and a Game Boy T-shirt wandering around.

Filming will most likely take place in the afternoons, since the Game Boy Camera requires good lighting and doesn't perform well in low-light conditions.

The exact filming schedule will depend on the submission deadline for the FieldFX demoparty, as we aim to complete the demo in time for the event.

'''Musician Wanted!'''

We're looking for a musician to contribute an original track to our demoscene project.

We already have a reference track in mind that we will use, but if we receive something original, preferably in a calm, lo-fi guitar style we’d be happy to feature your track instead!

Please note: the music must comply with the rules of the FieldFX demoparty. That likely means it must be entirely your own creation, no remixes, no covers, no unauthorized vocals samples.

== Hardware/setup ==

Because the Game Boy Camera wasn’t originally intended for video capture, we’ve built a custom recording setup, packed into a backpack.
'''Main setup include:'''
** a Dell XPS 17 9720 laptop
** Elgato HD60 X capture card
** Analogue Pocket (docked).
** Modified Game Boy Camera with a homemade extension cable separating the camera head from the cartridge
** OBS Studio (running on the Dell XPS for recording)

'''Additional gear:'''
** One GB Camera PicNRec AIO with "Photo! v1.10" firmware by untoxa
** One Analogue Super Nt with a Super Game Boy 2 cartridge
** One unmodified Game Boy Camera (for backup or comparison)
** A 20,000mAh power bank to power the Pocket dock
** Possibly an external screen + additional power bank to monitor the feed, as the laptop lid will remain closed inside the backpack

Let us know if you're interested, and we look forward to documenting the camp’s creative energy through pixelated Game Boy magic!

User:Xylitol

2025-04-28T13:11:08Z

Xylitol:

{{UserInfo
|NickName={{PAGENAME}}
|Bringing=Gameboy camera, stickers
|Village=Village:Lambda
|Languages=EN,FR
|HackerSpace=Hackgyver
}}

Village:Lambda

2025-04-28T13:01:40Z

Xylitol:

{{Village
|Has name=Lambda
|Has description=French Village with Crepe & DJ
|Has village tag=Free Beer, InfoSec, Cyber Circus, Whiskyleaks, electronics, retro computing
|Provides session location=No
|Has orga contact=lambda_why@proton.me
|On site orga contact=vertrex
|Village citizen count=10
|Village Needs power=Smaller Village (up to 2x 230V/Schuko)
|Village size needed=50
|Village hacktents num=0
|Village brings big stuff=No
}}

== Arrival on site / Buildup ==

{| class='h wikitable smwtable table sortable'
! Villagers !! Location (From) !! How !! Arrival-departure
|-
| Gadget,Cheyenne, plus one cat || Switzerland || Camper van (California Coast) ||
|-
| [[User:Xylitol|Xylitol]], Lucie || France || plane, train || 07/08/2025 - 13/08/2025
|-
|}

== Village Infra ==

{| class='h wikitable smwtable table sortable'
! What !! Location (From) !! Who !! Comment
|-
| 1x Tent 5 m x 5 m || Team Moebelhaus || Solal ||
|-
| 1x Tent Sahara 400 || own stuff || Thanat0s ||
|-
| 1x 3-Person Tent || own stuff || Benoit ||
|-
| 1x MH100 XL || own stuff || Xyl2k || …
|-
| 7x chairs || own stuff || Thanat0s || …
|-
| 1x oscilloscope || own stuff || Gadget || not sure yet
|-
| DJ Set || own stuff || Benoit ||
|}

User:Xylitol

2025-03-25T20:51:50Z

Xylitol:

{{UserInfo
|NickName={{PAGENAME}}
|Village=Village:Lambda
|Languages=EN,FR
|HackerSpace=Hackgyver
}}

User:Xylitol

2025-03-25T20:50:25Z

Xylitol:

{{UserInfo
|NickName={{PAGENAME}}
|Village=Village:Lambda
|Languages=EN
}}

User:Xylitol

2025-03-25T20:39:14Z

Xylitol: create user page

{{UserInfo
|NickName={{PAGENAME}}
|Languages=EN
|HackerSpace=
}}