-
Notifications
You must be signed in to change notification settings - Fork 24
Deprecate archives.ipfs.io? #179
Comments
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 |
|
@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:
in |
@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. |
Changed Public Archives link to https://awesome.ipfs.io/datasets/ per work done in ipfs-inactive/archives#179 Closes #237
Changed Public Archives link to https://awesome.ipfs.io/datasets/ per work done in ipfs-inactive/archives#179 Closes #237
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.
The text was updated successfully, but these errors were encountered: