Might also end up being devhack.network or devhack2.network to take advantage of SSL certs, as .internal isn't a valid TLD to request certs on.

internal-only network that you have to on our [network](:network) (the hackable one) or connect to via a [vpn](:vpn)


managed via [pdns](:pdns), see: [dns](:dns)

## "but why not just put all web services behind an oauth wall"

To nudge people to use the [hackable wifi](:hackable-wifi) over the [stable wifi](:stable-wifi), there need to be some incentives to want to be on the hackable wifi, by default. that don't threaten the the stable wifi's stability, obviously

For that reason we're putting some amount of less-important-to-be-accessed-from-the-outside services internally. Ideally, these things are still important as to give some pull to the hacker-side.