Re: uri4uri.net

Hello,

Sarven, I think the website states no data is kept, but we can take the URIs from the log that resolved with 200 status and submit that list of URIs to the ArchiveTeam [1]. They actively crawl sites that may go down and submit archives to the Archive.org. Additionally, the ArchiveTeam may not be experienced with content negotiation, so the use a tool like ldspider may be needed from our side (again, would need to be primed with all the URIs). We should think this through first from the privacy point of view and maybe update the privacy policy to state that the URIs submitted may be used to create an archive of the data on archive.org.

Christopher, I am happy to take over the hosting and the plan would be to put it on the "Level 1" plan at Hetzner [2].

/Andrew

[1]: https://wiki.archiveteam.org/ 
[2]: https://www.hetzner.com/webhosting?country=se


On 2022-01-25, 18:41, "Sarven Capadisli" <info@csarven.ca> wrote:

    On 25/01/2022 18.23, Christopher Gutteridge wrote:
    > Years ago I did http://uri4uri.net/ as a bit of a gag, but it provides a 
    > kinda useful  thing by defining URIs for web components, including  URI 
    > schemes, mime types, suffixes... and URIs themselves.
    > 
    > But the domain is up for renewal and I'm not planning to renew it. If 
    > anybody want to take ownership, please be let me know. It expires on 
    > 2022-03-26.
    > 
    > If it's not valuable to anybody here we can conclude it's not valuable!
    > 
    > The code for it is here: https://github.com/cgutteridge/uri4uri

    > 
    > 


    Before letting it go, it'd be great to create archival snapshots of all 
    of the URLs at the Internet Archive.

    -Sarven
    https://csarven.ca/#i

Received on Wednesday, 26 January 2022 14:11:21 UTC