Allow users to host things (web hosting?) (http?) on domains

[m@…]

Probably not *.devhack.net because of cookie reasons :(

​https://publicsuffix.org/

but there are vague amounts of domain names that ppl want to donate to the space to be able to host things on subdomains. *.wizard.gay, etc, etc.

[m@…]

Putting things on a tilde subpath under a pub.devhack.net or smthn would be able to avoid issues?

[m@…]

A combination of a collection of fun TLDs either managed by the space or donated by members + an html only ​https://devhack.net/«username» should work, as long as we control the web server to disable javascript or at least cookies.

[m@…]

we also need a DNS record for folks to CNAME point at that will always end up resolving through our load balancer.

[m@…]

One thing I haven't seen a good consensus about is how we specify [domain / subpath] mappings to both user AND user hosted content.

For example, devhack.fun is easy enough. permanently specifying within git / kubernetes CRDs because it's very dynamic at all. only letting users claim subdomains. user claimed subdomains restrict further subdomains to that specific user. for example, if I get m.devhack.fun, another user can't get test.m.devhack.fun. We'de probably want to park something on the top level devhack.fun. Maybe a redirect to devhack.net, maybe a page explaining what it is. Maybe tilde directories at the top level devhack.fun as well.

The complicated part is how users "claim" subdomains, or other domains that are user-specific. for example, nel has endofthe.world that she wants to be hosted at devhack but doesn't want to give other users access to. Do we specify this in the same place as our more permanent domain mappings?? or my claim of m.devhack.fun.

Obviously these mappings need to be specified somewhere. whether kubernetes CRDs, zone files / nameservers, a database / key value store like postgres or redis, or merely unix directory perms. Subdomain wildcard dynamic routing could exist, as could a fallback routing. And then wherever it gets specified it gets translated to traefik routing (but traefik assumes a total list of all domains being served (for https at least)). Caddy allows doing wildcard https routing, it requests certificates as soon as the domain name is hit.

[m@…]

apiVersion: "v1"
kind: HostingResource
domain: "dev.hack.seattle.wa.us"
subdomains: true
tildepaths: true
protocols:
    - https
    - http
users:
  - *
----
apiVersion: "v1"
kind: HostingResource
domain: "devhack.net"
subdomains: false
tildepaths: true
protocols:
    - https
    - http
users:
  - *
----
apiVersion: "v1"
kind: HostingResource
domain: "devhack.fun"
subdomains: true
protocols:
    - https
    - http
users:
  - *
----
apiVersion: "v1"
kind: HostingResource
domain: "attheendof.world"
subdomains: true
protocols: 
    - https
    - http
users:
  - nel
----
apiVersion: "v1"
kind: HostingResource
domain: "wizard.gay"
subdomains: true
protocols:
    - https
    - http
    - http-dialup
    - gopher
users:
  - *
----

[m@…]

Oh yeah the fact that hostnames are now being used as identifiers on varying services (cough bluesky cough) or did stuff lends credence to letting users have full nameserver access to their subdomains

[m@…]

recurse center uses: ​https://github.com/recursecenter/proxy