WHY2025 wiki - User contributions [en]

Village:Yolocation

2025-08-05T12:22:15Z

Based: /* Contact us */

Village:Yolocation

2025-08-04T05:02:48Z

Based: /* Free VMs and co-location */

Village:Yolocation

2025-08-04T04:53:08Z

Based: /* Free VMs and co-location */

Village:Yolocation

2025-08-04T04:52:21Z

Based: /* Free VMs and co-location */

Village:Yolocation

2025-08-04T04:51:26Z

Based: /* Free VMs and co-location */

Village:Yolocation

2025-08-04T04:46:30Z

Based: /* Free VMs and co-location */

Village:Yolocation

2025-08-04T04:43:34Z

Based:

Village:Yolocation

2025-08-04T04:42:55Z

Based: /* Make Hosting Great Again */

{{Village
|Has name=Yolocation
|Has website=https://yolocation.nl
|Has contact=GraPghaST (IRC)
|Has description=Free VMs, popup datacenter with Yolo Colocation & Retro Hardware
|Has village tag=retro computing, Free VMs, Datacenter Infrastructure
|Provides session location=Maybe
|Location=52.6924, 4.7498
|Has orga contact=grapghast@gmail.com
|On site orga contact=IRC, DECT (tbd), Mail
|Village frab=yes
|Village citizen count=10
|Village Needs power=Large Village (32A CEE 400V)
|Village size needed=250
|Village hacktents num=1
|Village brings big stuff=Yes
|Village planning notes=- Big Tent (10x5m)
- Popup datacenter in heavy trolly with heavy equipment. So we want to be near a road where we can bring the van with stuff (see preferred location)
- 400v32A socket needs to be nearby, we're going to use more than average power
- Datenklo needs to be nearby for fast (redundant) uplink
- We're thinking about using YolocationDC for scheduled workshops: a guided tour about how to run a (popup) datacenter, what is necessary, and what we ran into
}}
= Free VMs and co-location =

If you need a Virtual Machine to host your excellent project, or you want to co-locate your own server, please reach out to us. We offer Free VM's from our pop-up datacenter on the WHY camp terrain. The location can be found on the map.

For Free VM's please read the [https://yolocation.nl/docs/ documentation] on our [https://yolocation.nl website]. It basically boils down to asking our bot for a VM on our IRC or Discord channel. The VM is automatically created.

For co-location it's best to contact us directly to work out the details. You can reach us at:
* IRC: #yolocation, nick GraPghaST
* mail: [mailto:yolocation@gmail.com yolocation@gmail.com]
* DECT: YOLO

Please come and visit us! Bring beer and Mate.

= F.A.Q.: =
About the YOLOhosting part, you might be thinking "WHY the F.A.Q are you doing this?" So here are a bunch of answers:

=== Where is this thing you are talking about actually for? ===
For educational purposes of course. To learn about the wonderful world of colocation and hosting. If you want to learn about this, please visit our village and ask, we are glad to tell you.

=== What is the uptime of your Yolosomethingsomething VM's? ===
Yes we have uptime as an added feature in our Limited Availability package. Please ask our Sales representative.

=== Where do you store the back-ups of the platform? ===
Hey back up there buddy, as we follow the Yolo paradigm we use the perfect amount of back-ups. We use the 3-2-1 paradigm, which means we discuss it first with at least 3 persons, then drink 2 Club Mate's and finally we send the 1 back-up to /dev/null. Please understand we do not have anything in place to recover your precious data on our YOLO if you loose it.

=== How much current can your redundant power supply handle and did YOLO properly calculated the load during failover? ===
This all depends on the quality of the solder and duct tape for our 380V connector. We don't use flux, because we are YOLO.

=== Do you have any proper networking so we can pull some bandwith? ===
You are in luck, as network is arranged by the WHY organization it's the least YOLO part of YOLO. You can pull somez bitz bro, we give you bandwithz.

=== Do you cooperate with law enforcement if they want to investigate? ===
Yes of course, as good citizens we completely cooperate with law enforcement and shall hand over gracefully any log files in existence.

=== What do you log any way and what metadata do you store? ===
We are working on a very intrusive totalitarian monitoring system with dodgy privacy regulation and complete introspection on anything that happens. This will log all actions and tie it to actual persons and other metadata as camera footage and OSINT info. This database is also directly coupled to third party companies, mainly in the markerting sector. We do this all "for your safety and user experience" of course.

However, due to budget constraints, manpower, prioritization and amateuristic project management we had to reschedule this feature to sprint 43 which starts Monday the 18th of August 2025. Before that date we only have Yologging which is a skeleton framework only for some metrics as general network traffic and total disk storage. We can't log anything on an individual level with the Yologging Framework(tm) unfortunately.

=== What happens to the data after WHY? ===
Because most of the hardware is borrowed, we need to wipe and destroy ALL DATA from the pop-up datacenter after WHY. So not a single bit of data survives the camp. Nothing. This is for compliancy reasons. Please store any valuable educational material you learned on this platform yourself in a safe place. We won't. The Data Only Lives Once.

=== Where can we contact you for signing an NDA ===
We use the FrieNDA system, so what happens at YOLO stays at YOLO. This also includes everything what happens inside the physical village tent. Please don't tell my mom anything that happens inside that tent.

=== Can we host a strongly political website which accidentaly also sells drugs? ===
Come on dude, we host an educational platform for a hacker camp. Please be Excellent to each other and the platform.

Network

2025-08-03T10:23:13Z

Based: /* Co-location */

== Rules of Conduct ==

* Be fair. Do not do to others what you do not wish done to yourself. 🌈
* Protect your computer. -> We cannot be held responsible for any damage your computer may face due to attachment to our network. Be reminded that both internet access and the local network are unfirewalled and unfiltered. Even well-maintained systems can be attacked and get hacked, even more so at a hacker event.
* Do not run your own DHCP server. -> Doing so is harmful.
* Do not send IPv6 Router Advertisements.
* Do not ARP spoof or otherwise impede the operation of the network.
* While we are generally quite able to find and disconnect you in case of network misuse if necessary, we still prefer to not have to do so and that everybody respects the other visitors.
* Think twice before you do something that affects others. -> If you hack someone, you might be prosecuted. Be aware that we cannot prevent law enforcement from acting within or related to our network.👮🚨🚔
* Do not connect S/FTP or F/FTP (so called shielded cables) to a Datenklo; this is to prevent ground-loops.
* See also [[Network#Rules|Rules for wireless equipment]].

== Wired ==

There will be wired 100BASE-TX/1000BASE-T/10GBASE-T ethernet on the camping grounds and in the caravan area by means of so-called "Data Toilets" or "Datenklos". Look for construction toilets with tin foil wrapped around them.

You can lay your own cables, but please do so in a tidy manner. You must not cross any roads, paths or borders between camping grounds. Always lay your cable from the Datenklo towards your tent to keep any slack close to your tent. Leave 5m of slack cable at the Datenklo. You can simply leave the end of your cable at the Datenklo, it will be connected by helpers at regular intervals (during reasonable work hours). If you want your cable back, make a proper spool of it and leave that at the Datenklo or mark it accordingly. It will be disconnected for you to pick up.

The maximum line-of-sight distance to the next Datenklo will be approximately 50 meters. Cables will not be provided. A length of 50 meters is recommended. If that is insufficient, you will find someone within this range who has a switch and can plug you in. But bringing 60 or 75 meters won't hurt if you want to be sure. Do not bring SFTP or other shielded cables, this can cause harm you your and our equipment, we will not connect them (this is to prevent ground loops).

Optionally, bring & connect a small ethernet switch when connecting multiple devices. Please disable Spanning-Tree Protocol if you would connect a managed switch.

Wired connections are unfiltered. If you have (older) devices that cannot be trusted with unrestricted incoming connections, bring a router or firewall (and disable the WiFi).

== Wireless ==

You can't live without wireless access, so we've built an awesome wireless network again.

=== WHY2025 SSIDs ===
<dl>
<dt>Network Name (SSID)</dt>
<dd>WHY2025</dd>
<dt>Username</dt>
<dd>why</dd>
<dt>Password</dt>
<dd>why</dd>
</dl>

The following SSIDs are provided:

* WHY2025 (WPA3 802.1X (see below), 2.4GHz+5GHz+6GHz) ✅ noc recommended ✅
* WHY2025-open (open/OWE, 2.4GHz+5GHz+6GHz)
* spacenet (WPA3 802.1X, 2.4GHz+5GHz+6GHz) - you can connect with a valid account if your hackerspace offers it.
* eduroam (WPA3 802.1X, 2.4GHz+5GHz+6GHz) - you can connect with a valid account if your university/college/school is offering eduroam.

=== WPA3 802.1X, encryption ===

Due to popular demand (and with security in mind) we provide WPA3 802.1X. This will encrypt your traffic, preventing attackers from sniffing your data. Keep in mind that this won't protect you from other network attacks and you should still be aware that you are at a hacker conference. Your link layer should be secure if you do certificate checking (see below).

You might think: "WTF? Do I need to register a user and password blah, blah". Fortunately not. You can use any username/password combination using EAP-TTLS with PAP to login (example: "user: fbhfbhiaf pass: bgufwbnkqo" is valid), because we don't care who logs in and who you are. We just want to encrypt your data.

Users which use MSCHAPv2 (like Windows users with default 802.1X supplicant) should use a fixed username and password. You can use "why/why" or "guest/guest" as "username/password".

=== Client Settings ===
Also see [[Network/802.1X client settings]] for a list of OS-specific client settings.

<pre>SSID: WHY2025

EAP-TTLS:

Phase 1: EAP-TTLS
Phase 2: PAP

PEAP:

Phase 1: PEAP
Phase 2: MSCHAPv2 or EAP-MSCHAPv2 or PAP

CN = radius.eventinfra.org
CA = ISRG Root X1

SHA256 Fingerprint = 95:28:B8:D2:4E:F3:66:D6:4F:B9:9F:D1:A4:EC:EE:1D:FE:4A:BA:93:C9:46:7E:D0:43:C9:E9:C2:50:38:8F:4B
</pre>

Make sure you check the certificate in order to know you are connecting to the correct network (you should check on both the CN and the CA). Check [[Network/RADIUS_certificate|here]] for the complete certificate.

=== Services VLANs ===
We're using WPA3 802.1X to push your client in the correct VLAN. The reason we are doing this is to keep the number of SSID's per wireless band to a minimum; this way we are saving airtime by not wasting it too much with 802.11 beacons/mgmt-frames. Use the following user/password combinations:

{| class="wikitable"
! Username
! Password
! Result
|-
| why
| why
| Filtered connection with public IP address. Inbound connections from the rest of the campsite are possible, inbound connections from the Internet are blocked. IPv6-mostly enabled.
|-
| dualstack
| dualstack
| Filtered connection with public IP address. Inbound connections from the rest of the campsite are possible, inbound connections from the Internet are blocked. Dual-stack, no IPv6-mostly enabled.
|-
| allowany
| allowany
| Unfiltered connection with public IP address
|-
| outboundonly
| outboundonly
| Filtered connection with public IP address. Inbound connections from the Internet or camp-site are not possible.
|}

Please note the username AND password are case-sensitive.

=== Rules ===

To keep the wireless working for you, keep a few things in mind:
* We're aware you can break the WiFi infrastructure. We're hoping that you won't and don't want to be chased by 3750 hackers through the Camp.
* If you want to download terabytes of data, you might be better off connecting to the wired network
* Don't set up your own accesspoint. However, if you have no other choice (for running experiments and such), please be nice and consider these rules:
** Please do not operate non-WiFi/analog equipment in these frequencies.
** 2.4GHz: use channels 1, 5, 9 or 13 @ 20MHz. Disable 802.11b.
** 5GHz: use channels 36 or 140 @ 20MHz.
** Minimum data-rate = 12Mbit/s, also for beacon-rate. Beacon interval 100ms or higher.
** Limit the number of broadcasted BSSID's per radio to 1 or 2. No SSID spamming etc is allowed.
** Do not prefix your broadcasted ESSID(s) with "WHY". Do not use "WHY2025" as your ESSID. Do not use other well-known ESSIDs.
** Do not use high-gain antennas.
** Limit your transmit-power for example to 6dBm or 4mW.

== Co-location ==

There will unfortunately be no co-location service at Camp. There are villages like [https://wiki.why2025.org/Village:Yolocation Yolocation] who offer co-location services from their own initiative. Please contact these villages directly if you are interested. You are also welcome to host a server in your tent/village and you can get a 10-gigabit copper uplink from one of the nearby datenklos. If you have any special requests regarding bandwidth please contact the NOC at noc *DOT* WHY2025.org. '''Please send your requests in English.'''

== IXP ==

There will be a IXP at WHY2025. For more info see [[IXP]].

== Supporters ==
We'd like to extend our immense gratitude to the following people and organisations who have been instrumental in making the WHY2025 network and uplink happen through their donations and sponsorship:

Hardware/material sponsors:

* [https://www.juniper.net Juniper] ; core-routers & switches
* [https://www.flexoptix.net FlexOptix] ; optical transceivers
* [https://eventinfra.org/ EventInfra] ; Access network (wired+wireless) and fibers
* [https://www.i3d.net/ i3D.net] ; Equipment and upstream connectivity (IP-transit)
* [https://pfalzkom.de/en/ PFALZKOM] ; DWDM equipment
* [https://www.babiel.com/ Babiel] ; Servers
* [https://www.bit.nl BIT] ; UTP cable

Connectivity sponsors:

* [https://surf.nl/ SURF] ; Alien-Wave and dark-fibre to the field
* [https://solcon.nl/ Solcon] ; Dark-fibre to the field
* [https://inter.link/ Inter.link] ; IP-transit
* [https://www.gin.ntt.net/ NTT Global IP Network] ; IP-transit
* [https://www.a2b-internet.com/ A2B Internet] ; IP-transit
* [https://fusix.nl/ Fusix] ; IP-transit
* [https://www.wobcom.de/ WOBCOM] ; IP-transit
* [https://www.eranium.io/ Eranium] ; IP-transit

Other connected Internet Exchanges are: [https://nl-ix.net/ NL-ix], Asteroid, SPEED-IX, [http://www.frys-ix.net/ Frys-IX], ERA-IX and LS-IX

== Mastodon ==
Follow Team:NOC on their WHY2025 Mastodon account: https://hsnl.social/@why2025noc

== PeeringDB ==
The WHY2025 network is operated under AS64404 (EventInfra): [https://www.peeringdb.com/net/16005 PeeringDB]

Village:Yolocation

2025-06-27T15:32:04Z

Based:

{{Village
|Has name=Yolocation
|Has contact=GraPghaST (IRC)
|Has description=Free VMs, popup datacenter with Yolo Colocation & Retro Hardware
|Has village tag=retro computing, Free VMs, Datacenter Infrastructure
|Provides session location=Maybe
|Location=52.69149, 4.74766
|Has orga contact=grapghast@gmail.com
|On site orga contact=IRC, DECT (tbd), Mail
|Village frab=yes
|Village citizen count=10
|Village Needs power=Large Village (32A CEE 400V)
|Village size needed=250
|Village hacktents num=1
|Village brings big stuff=Yes
|Village planning notes=- Big Tent (10x5m)
- Popup datacenter in heavy trolly with heavy equipment. So we want to be near a road where we can bring the van with stuff (see preferred location)
- 400v32A socket needs to be nearby, we're going to use more than average power
- Datenklo needs to be nearby for fast (redundant) uplink
- We're thinking about using YolocationDC for scheduled workshops: a guided tour about how to run a (popup) datacenter, what is necessary, and what we ran into
}}
= Make Hosting Great Again =

We are some industry veterans who think hosting and colocation is not what it used to be.
You only live once, so WHY host twice? Exactly. To counter the current chicken SRE trend with modernities as redundancy, back-ups, compliancy, "AI networking" and other counterproductive facilities we go back to the core of it all. We do things YOLO.

So in our pop-up datacenter we do hosting and colocation the correct way.
You can get some of the finest quality, handcrafted and Free VM's for you to experience true hosting like it should be.

As we are industry veterans, we are also somewhat Old(tm) so we also have a fair amount of oldsCool hardware from Ye Olde Days. This is not AI generated crap but actual touchable and lickable (please don't) physical hardware for you to admire if you visit our beautiful village. Please drop by and have a look.

= F.A.Q.: =
About the YOLOhosting part, you might be thinking "WHY the F.A.Q are you doing this?" So here are a bunch of answers:

=== Where is this thing you are talking about actually for? ===
For educational purposes of course. To learn about the wonderful world of colocation and hosting. If you want to learn about this, please visit our village and ask, we are glad to tell you.

=== What is the uptime of your Yolosomethingsomething VM's? ===
Yes we have uptime as an added feature in our Limited Availability package. Please ask our Sales representative.

=== Where do you store the back-ups of the platform? ===
Hey back up there buddy, as we follow the Yolo paradigm we use the perfect amount of back-ups. We use the 3-2-1 paradigm, which means we discuss it first with at least 3 persons, then drink 2 Club Mate's and finally we send the 1 back-up to /dev/null. Please understand we do not have anything in place to recover your precious data on our YOLO if you loose it.

=== How much current can your redundant power supply handle and did YOLO properly calculated the load during failover? ===
This all depends on the quality of the solder and duct tape for our 380V connector. We don't use flux, because we are YOLO.

=== Do you have any proper networking so we can pull some bandwith? ===
You are in luck, as network is arranged by the WHY organization it's the least YOLO part of YOLO. You can pull somez bitz bro, we give you bandwithz.

=== Do you cooperate with law enforcement if they want to investigate? ===
Yes of course, as good citizens we completely cooperate with law enforcement and shall hand over gracefully any log files in existence.

=== What do you log any way and what metadata do you store? ===
We are working on a very intrusive totalitarian monitoring system with dodgy privacy regulation and complete introspection on anything that happens. This will log all actions and tie it to actual persons and other metadata as camera footage and OSINT info. This database is also directly coupled to third party companies, mainly in the markerting sector. We do this all "for your safety and user experience" of course.

However, due to budget constraints, manpower, prioritization and amateuristic project management we had to reschedule this feature to sprint 43 which starts Monday the 18th of August 2025. Before that date we only have Yologging which is a skeleton framework only for some metrics as general network traffic and total disk storage. We can't log anything on an individual level with the Yologging Framework(tm) unfortunately.

=== What happens to the data after WHY? ===
Because most of the hardware is borrowed, we need to wipe and destroy ALL DATA from the pop-up datacenter after WHY. So not a single bit of data survives the camp. Nothing. This is for compliancy reasons. Please store any valuable educational material you learned on this platform yourself in a safe place. We won't. The Data Only Lives Once.

=== Where can we contact you for signing an NDA ===
We use the FrieNDA system, so what happens at YOLO stays at YOLO. This also includes everything what happens inside the physical village tent. Please don't tell my mom anything that happens inside that tent.

=== Can we host a strongly political website which accidentaly also sells drugs? ===
Come on dude, we host an educational platform for a hacker camp. Please be Excellent to each other and the platform.

Village:Yolocation

2025-06-27T15:25:54Z

Based:

{{Village
|Has name=Yolocation
|Has contact=GraPghaST (IRC)
|Has description=Free VMs, popup datacenter with Yolo Colocation & Retro Hardware
|Has village tag=retro computing, Free VMs, Datacenter Infrastructure
|Provides session location=Maybe
|Location=52.69149, 4.74766
|Has orga contact=grapghast@gmail.com
|On site orga contact=IRC, DECT (tbd), Mail
|Village frab=yes
|Village citizen count=10
|Village Needs power=Large Village (32A CEE 400V)
|Village size needed=250
|Village hacktents num=1
|Village brings big stuff=Yes
|Village planning notes=- Big Tent (10x5m)
- Popup datacenter in heavy trolly with heavy equipment. So we want to be near a road where we can bring the van with stuff (see preferred location)
- 400v32A socket needs to be nearby, we're going to use more than average power
- Datenklo needs to be nearby for fast (redundant) uplink
- We're thinking about using YolocationDC for scheduled workshops: a guided tour about how to run a (popup) datacenter, what is necessary, and what we ran into
}}
= Make Hosting Great Again =

We are some industry veterans who think hosting and colocation is not what it used to be.
You only live once, so WHY host twice? Exactly. To counter the current chicken SRE trend with modernities as redundancy, back-ups, compliancy, "AI networking" and other counterproductive facilities we go back to the core of it all. We do things YOLO.

So in our pop-up datacenter we do hosting and colocation the correct way.
You can get some of the finest quality, handcrafted and Free VM's for you to experience true hosting like it should be.

As we are industry veterans, we are also somewhat Old(tm) so we also have a fair amount of oldsCool hardware from Ye Olde Days. This is not AI generated crap but actual touchable and lickable (please don't) physical hardware for you to admire if you visit our beautiful village. Please drop by and have a look.

= F.A.Q.: =
About the YOLOhosting part, you might be thinking "WHY the F.A.Q are you doing this?" So here are a bunch of answers:

=== Where is this thing you are talking about actually for? ===
For educational purposes of course. To learn about the wonderful world of colocation and hosting. If you want to learn about this, please visit our village and ask, we are glad to tell you.

=== What is the uptime of your Yolosomethingsomething VM's? ===
Yes we have uptime as an added feature in our Limited Availability package.

=== Where do you store the back-ups of the platform? ===
Hey back up there buddy, as we follow the Yolo paradigm we use the perfect amount of back-ups. We use the 3-2-1 paradigm, which means we discuss it first with at least 3 persons, then drink 2 Club Mate's and finally we send the 1 back-up to /dev/null. Please understand we do not have anything in place to recover your precious data on our YOLO if you loose it.

=== How much current can your redundant power supply handle and did YOLO properly calculated the load during failover? ===
This all depends on the quality of the solder and duct tape for our 380V connector. We don't use flux, because we are YOLO.

=== Do you have any proper networking so we can pull some bandwith? ===
You are in luck, as network is arranged by the WHY organization it's the least YOLO part of YOLO. You can pull somez bitz bro, we give you bandwithz.

=== Do you cooperate with law enforcement if they want to investigate? ===
Yes of course, as good citizens we completely cooperate fully with law enforcement and hand over gracefully any log files in existence.

=== What do you log any way and what metadata do you store? ===
We are working on a very intrusive totalitarian monitoring system with dodgy privacy regulation and complete introspection on anything that happens. This will log all actions and tie it to actual persons and other metadata as camera footage and OSINT info. This database is also directly coupled to third party companies, mainly in the markerting sector. We do this all "for your safety and user experience" of course.

However, due to budget constraints, manpower, prioritization and amateuristic project management we had to reschedule this feature to sprint 43 which starts Monday the 18th of August 2025. Before that date we only have Yologging which is a skeleton framework only for some metrics as general network traffic and total disk storage. We can't log anything on an individual level with the Yologging Framework(tm) unfortunately.

=== What happens to the data after WHY? ===
Because most of the hardware is borrowed, we need to wipe and destroy ALL DATA from the pop-up datacenter after WHY. So not a single bit of data survives the camp. Nothing. This is for compliancy reasons. Please store any valuable educational material you learned on this platform yourself in a safe place. We won't. The Data Only Lives Once.

=== Where can we contact you for signing an NDA ===
We use the FrieNDA system, so what happens at YOLO stays at YOLO. This also includes everything what happens inside the physical village tent. Please don't tell my mom anything that happens inside that tent.

=== Can we host a strongly political website which accidentaly also sells drugs? ===
Come on dude, we host an enducational platform for a hacker camp. Please be Excellent to eachother and the platform.

Village:Yolocation

2025-06-27T15:24:24Z

Based:

{{Village
|Has name=Yolocation
|Has contact=GraPghaST (IRC)
|Has description=Free VMs, popup datacenter with Yolo Colocation & Retro Hardware
|Has village tag=retro computing, Free VMs, Datacenter Infrastructure
|Provides session location=Maybe
|Location=52.69149, 4.74766
|Has orga contact=grapghast@gmail.com
|On site orga contact=IRC, DECT (tbd), Mail
|Village frab=yes
|Village citizen count=10
|Village Needs power=Large Village (32A CEE 400V)
|Village size needed=250
|Village hacktents num=1
|Village brings big stuff=Yes
|Village planning notes=- Big Tent (10x5m)
- Popup datacenter in heavy trolly with heavy equipment. So we want to be near a road where we can bring the van with stuff (see preferred location)
- 400v32A socket needs to be nearby, we're going to use more than average power
- Datenklo needs to be nearby for fast (redundant) uplink
- We're thinking about using YolocationDC for scheduled workshops: a guided tour about how to run a (popup) datacenter, what is necessary, and what we ran into
}}
= Make Hosting Great Again =

We are some industry veterans who think hosting and colocation is not what it used to be.
You only live once, so WHY host twice? Exactly. To counter the current chicken SRE trend with modernities as redundancy, back-ups, compliancy, "AI networking" and other counterproductive facilities we go back to the core of it all. We do things YOLO.

So in our pop-up datacenter we do hosting and colocation the correct way.
You can get some of the finest quality, handcrafted and Free VM's for you to experience true hosting like it should be.

As we are industry veterans, we are also somewhat Old(tm) so we also have a fair amount of oldsCool hardware from Ye Olde Days. This is not AI generated crap but actual touchable and lickable (please don't) physical hardware for you to admire if you visit our beautiful village. Please drop by and have a look.

= F.A.Q.: =
About the YOLOhosting part, you might be thinking "WHY the F.A.Q are you doing this?" So here are a bunch of answers:

=== Where is this thing you are talking about actually for? ===
For educational purposes of course. To learn about the wonderful world of colocation and hosting. If you want to learn about this, please visit our village and ask, we are glad to tell you.

=== What is the uptime of your Yolosomethingsomething VM's? ===
Yes we have uptime as an added feature in our Limited Availability package.

=== Where do you store the back-ups of the platform? ===
Hey back up there buddy, as we follow the Yolo paradigm we use the perfect amount of back-ups. We use the 3-2-1 paradigm, which means we discuss it first with at least 3 persons, then drink 2 Club Mate's and finally we send the 1 back-up to /dev/null. Please understand we do not have anything in place to recover your precious data on our YOLO if you loose it.

== How much current can your redundant power supply handle and did YOLO properly calculated the load during failover? ===
This all depends on the quality of the solder and duct tape for our 380V connector. We don't use flux, because we are YOLO.

=== Do you have any proper networking so we can pull some bandwith? ===
You are in luck, as network is arranged by the WHY organization it's the least YOLO part of YOLO. You can pull somez bitz bro, we give you bandwithz.

=== Do you cooperate with law enforcement if they want to investigate? ===
Yes of course, as good citizens we completely cooperate fully with law enforcement and hand over gracefully any log files in existence.

=== What do you log any way and what metadata do you store? ===
We are working on a very intrusive totalitarian monitoring system with dodgy privacy regulation and complete introspection on anything that happens. This will log all actions and tie it to actual persons and other metadata as camera footage and OSINT info. This database is also directly coupled to third party companies, mainly in the markerting sector. We do this all "for your safety and user experience" of course.

However, due to budget constraints, manpower, prioritization and amateuristic project management we had to reschedule this feature to sprint 43 which starts Monday the 18th of August 2025. Before that date we only have Yologging which is a skeleton framework only for some metrics as general network traffic and total disk storage. We can't log anything on an individual level with the Yologging Framework(tm) unfortunately.

=== What happens to the data after WHY? ===
Because most of the hardware is borrowed, we need to wipe and destroy ALL DATA from the pop-up datacenter after WHY. So not a single bit of data survives the camp. Nothing. This is for compliancy reasons. Please store any valuable educational material you learned on this platform yourself in a safe place. We won't. The Data Only Lives Once.

=== Where can we contact you for signing an NDA ===
We use the FrieNDA system, so what happens at YOLO stays at YOLO. This also includes everything what happens inside the physical village tent. Please don't tell my mom anything that happens inside that tent.

=== Can we host a strongly political website which accidentaly also sells drugs? ===
Come on dude, we host an enducational platform for a hacker camp. Please be Excellent to eachother and the platform.

User:Based

2025-06-26T11:39:07Z

Based:

{{UserInfo
|Bringing=Ye Olde Thinkpads, some IoT.
|Village=Village:Yolocation
|Arrival=2025-08-07
|Departure=2025-08-13
|Languages=EN, NL
|NickName=flag{0x4261736564}
}}

Village:Yolocation

2025-06-26T11:31:19Z

Based: Free VMs, popup datacenter with Yolo Colocation & Retro Hardware

{{Village
|Has name=Yolocation
|Has contact=GraPghaST (IRC)
|Has description=Free VMs, popup datacenter with Yolo Colocation & Retro Hardware
|Has village tag=retro computing, Free VMs, Datacenter Infrastructure
|Provides session location=Maybe
|Location=52.69149, 4.74766
|Has orga contact=grapghast@gmail.com
|On site orga contact=IRC, DECT (tbd), Mail
|Village frab=yes
|Village citizen count=10
|Village Needs power=Large Village (32A CEE 400V)
|Village size needed=250
|Village hacktents num=1
|Village brings big stuff=Yes
|Village planning notes=- Big Tent (10x5m)
- Popup datacenter in heavy trolly with heavy equipment. So we want to be near a road where we can bring the van with stuff (see preferred location)
- 400v32A socket needs to be nearby, we're going to use more than average power
- Datenklo needs to be nearby for fast (redundant) uplink
- We're thinking about using YolocationDC for scheduled workshops: a guided tour about how to run a (popup) datacenter, what is necessary, and what we ran into
}}
Make Hosting Great Again

We are some industry veterans who think hosting and colocation is not what it used to be.
You only live once, so WHY host twice? Exactly. To counter the current chicken SRE trend with modernities as redundancy, back-ups, compliancy, "AI networking" and other counterproductive facilities we go back to the core of it all. We do things YOLO.

So in our pop-up datacenter we do hosting and colocation the correct way.
You can get some of the finest quality, handcrafted and Free VM's for you to experience true hosting like it should be.

As we are industry veterans, we are also somewhat Old(tm) so we also have a fair amount of oldsCool hardware from Ye Olde Days. This is not AI generated crap but actual touchable and lickable (please don't) physical hardware for you to admire if you visit our beautiful village. Please drop by and have a look.

About the YOLOhosting part, you might have a lot of questions, so here are a bunch of answers:

F.A.Q.:

* Where is this thing you are talking about actually for?
For educational purposes of course. To learn about the wonderful world of colocation and hosting. If you want to learn about this, please visit our village and ask, we are glad to tell you.

* What is the uptime of your Yolosomethingsomething VM's?
Yes we have uptime as an extended feature in our Limited Availability package.

* Where do you store the back-ups of the platform?
Hey back up there buddy, as we follow the Yolo paradigm we use the perfect amount of back-ups. We use the 3-2-1 paradigm, which means we discuss it first with at least 3 persons, then drink 2 Club Mate's and finally we send the 1 back-up to /dev/null. Please understand we do not have anything in place to recover your precious data on our YOLO if you loose it.

* How much current can your redundant power supply carry and did YOLO properly calculated the load during failover?
This all depends on the quality of the solder and duct tape for our 380V connector. We don't use flux, because we are YOLO.

* Do you have any proper networking so we can pull some bandwith?
You are in luck, as network is arranged by the WHY organization it's the least YOLO part of YOLO. You can pull somez bitz bro, we give you bandwithz.

* Do you cooperate with law enforcement if they want to investigate?
Yes of course, as good citizens we completely cooperate fully with law enforcement and hand over gracefully any log files in existence.

* What do you log any way and what metadata do you store?
We are working on a very intrusive totalitarian monitoring system with dodgy privacy regulation and complete introspection on anything that happens. This will log all actions and tie it to actual persons and other metadata as camera footage and OSINT info. This database is also directly coupled to third party companies, mainly in the markerting sector. We do this all "for your safety and user experience" of course.

However, due to budget constraints, manpower, prioritization and amateuristic project management we had to reschedule this feature to sprint 43 which starts Monday the 18th of August 2025. Before that date we only have Yologging which is a skeleton framework only for some metrics as general network traffic and total disk storage. We can't log anything on an individual level with the Yologging Framework(tm) unfortunately.

* What happens to the data after WHY?
Because most of the hardware is borrowed, we need to wipe and destroy ALL DATA from the pop-up datacenter after WHY. So not a single bit of data survives the camp. Nothing. This is for compliancy reasons. Please store any valuable educational material you learned on this platform yourself in a safe place. We won't. The Data Only Lives Once.

* Where can we contact you for signing an NDA
We use the FrieNDA system, so what happens at YOLO stays at YOLO. This also includes everything what happens inside the physical village tent. Please don't tell my mom anything that happens inside that tent.

* Can we host a strongly political website which accidentaly also sells drugs?
Come on dude, we host an enducational platform for a hacker camp. Please be Excellent to eachother and the platform.

File:Village-Yolocation.png

2025-05-07T22:19:51Z

Based: Based reverted File:Village-Yolocation.png to an old version

File:Village-Yolocation.png

2025-05-07T22:16:12Z

Based: Based reverted File:Village-Yolocation.png to an old version

File:Village-Yolocation.png

2025-05-07T22:15:54Z

Based: Based reverted File:Village-Yolocation.png to an old version

File:Village-Yolocation.png

2025-05-07T22:04:53Z

Based: Based uploaded a new version of File:Village-Yolocation.png

File:Village-Yolocation.png

2025-04-27T22:20:42Z

Based: Based uploaded a new version of File:Village-Yolocation.png

File:Village-Yolocation.png

2025-04-27T22:16:25Z

Based: Based uploaded a new version of File:Village-Yolocation.png

File:Village-Yolocation.png

2025-04-27T21:58:44Z

Based: Based uploaded a new version of File:Village-Yolocation.png

File:Village-Yolocation.png

2025-04-27T21:52:31Z

Based:

User:Based

2025-04-27T21:15:07Z

Based:

{{UserInfo
|NickName=flag{0x4261736564}
|Village=Village:Yolocation
|Languages=EN, NL
}}

User:Based

2025-03-24T15:18:21Z

Based:

{{UserInfo
|Languages=EN, NL
|NickName={{PAGENAME}}
}}

File:User-Based.png

2025-03-07T12:09:56Z

Based:

User:Based

2025-03-07T12:09:10Z

Based:

{{UserInfo
|NickName={{PAGENAME}}
|Village=Village:Yolocation
|Languages=EN, NL
|HackerSpace=
}}

User:Based

2025-03-07T12:06:23Z

Based:

{{UserInfo
|NickName={{PAGENAME}}
|Village=Village:Yolocation
|Languages=EN
|HackerSpace=
}}

User:Based

2025-03-07T11:46:16Z

Based: create user page

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