A pretty dumb UI decision on my part, but now we've got the problem of legacy URLs existing out there in the wild.
Best solution would be to try and detect if the request is coming from a browser vs coming from a calendar client, and serve up the correct file, but that's not possible right now because the website is hosted on GH pages.
Second best solution is to use a new URL format, and that might be for the best because query params aren't that good for SEO (or so I've heard)
A pretty dumb UI decision on my part, but now we've got the problem of legacy URLs existing out there in the wild.
Best solution would be to try and detect if the request is coming from a browser vs coming from a calendar client, and serve up the correct file, but that's not possible right now because the website is hosted on GH pages.
Second best solution is to use a new URL format, and that might be for the best because query params aren't that good for SEO (or so I've heard)