dokieli is a clientside editor for decentralised article publishing, annotations and social interactions https://dokie.li/
csarven on main
Minor (compare)
csarven on main
Add ACL terms to Vocab Add access request with notific… (compare)
timbl acl:delegates bot
schema:SoftwareAgent
and range: schema/foaf:Person
curl -I https://www.w3.org/TR/webarch/
content-location: Overview.html
in comparison to the ones that don't:
curl -I http://csarven.ca/
So, when I do something like:
curl -ki 'https://web.archive.org/save/https://www.w3.org/TR/webarch/'
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101
Firefox/69.0' -H 'Accept: */*' -H 'Accept-Language:
en-CA,en;q=0.7,en-US;q=0.3' --compressed -H 'Referer:
https://localhost:8443/' -H 'Origin: https://localhost:8443' -H
'Connection: keep-alive' -H 'DNT: 1' -H 'Pragma: no-cache' -H
'Cache-Control: no-cache'
I get:
content-location: Overview.html
And that kind of screws up things for me because I can't figure out the
actual snapshot location from the headers. Okay if JS-enabled agent is
making the request because it eventually redirects.. but that's not what
I want because I'm making this call from dokieli and only want to work
with headers (or whatever is proper structured data is available.. as
opposed to scraping stuff).
This is in comparison to say:
curl -ki 'https://web.archive.org/save/http://csarven.ca/' -H
'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101
Firefox/69.0' -H 'Accept: */*' -H 'Accept-Language:
en-CA,en;q=0.7,en-US;q=0.3' --compressed -H 'Referer:
https://localhost:8443/' -H 'Origin: https://localhost:8443' -H
'Connection: keep-alive' -H 'DNT: 1' -H 'Pragma: no-cache' -H
'Cache-Control: no-cache'
which gives a nice workable:
content-location: /web/20190708123256/http://csarven.ca/
Have I missed something obvious that I can use?