Henry Andrews

@m451 yeah that would be great. We're very short on people to add to the actual content of the site- there aren't that many of us actively working on the...

As discussed in #31, the correct solution is to set the content-type, which is a problem because we don't have control of the DNS.

He doesn't have access. https://github.com/kriszyp/json-schema/commit/1c4923479501cdf78c6dab4e9af4bb40dc7992f0#commitcomment-19914120 We don't even know who has access, just that it's not anyone who was willing to answer email the last time anyone tried.

@epicfaace IIRC I think it's a github pages limitation? @Relequestual or @Anthropic might know? I've been focused on the spec rather than the website.

@epicfaace Oh, now I remember- the problem is that the older specs specifically use `http://...` for the meta-schema URIs. We can't just change that. New drafts will use `https://...` I'm...

@epicfaace while *technically* implementations should not automatically retrieve the meta-schemas from the canonical URI, if they do, it should still work and not break by suddenly returning a redirect.

> Where would this potentially cause a problem? I'm sure someone will complain about it but I don't care enough to argue over it.

@philsturgeon @Relequestual as long as y'all deal with the people who complain it's fine with me.

Not sure why this wasn't merged. @gregsdennis you might need to update your most recent PR, but I don't want to ask this person to change theirs a month after...

@Relequestual are we ready to re-link this?