Deprecate archives.ipfs.io?
victorb opened this issue · comments
Since we now lists datasets on awesome.ipfs.io, maybe we should just deprecate the archives.ipfs.io website and add a link to the category on awesome.ipfs.io instead? We should still have isolated discussions here but the results published on awesome.ipfs.io.
Sounds like a good idea.
Right now there are only 8 datasets on https://awesome.ipfs.io/categories/datasets/ but 15 on https://archives.ipfs.io/. They should get migrated first.
Then a 301 redirect from https://archives.ipfs.io/ to https://awesome.ipfs.io/categories/datasets/ would be good.
Should there be any hint to the archiving efforts in this repo?
@Stebalien what about this?
Sounds like a great idea, are you volunteering?
If it's something to do, I can move the missing datasets to awesome.ipfs.io, yes, and make a PR here to remove the unnecessary files.
- Move the missing datasets.
- Setup the redirect (or make sure infra does it).
- Update the README on this repo with instructions on how to get datasets added (PR the awesome IPFS repo?).
@Stebalien can you handle the redirect or should we ping someone from Infra?
I can't. @ipfs/wg-infrastructure?
I have redirected the domain
My browsers try to open archives.ipfs.io on HTTPs which breaks the redirection though, I´m not sure why.
JUst tested and the same is happening here
might have to do with:
< strict-transport-security: max-age=31536000; includeSubDomains; preload
in ipfs.io and gateway.ipfs.io... which means we'll need to setup a special redirect rule on nginx
@Stebalien since the redirect isn't working as expected, could you change the URL of the repository description to awesome.ipfs.io/datasets?
Sure. But we also need to fix the redirect.