dokieli is a clientside editor for decentralised article publishing, annotations and social interactions https://dokie.li/
I'd to move away from GitHub and Gitter.
Happy Birthday @timbl !
What does everyone think about the idea to remove 'Source' (which essentially lets you update the HTML in DOM) from the dokieli menu. The features will still be available by calling it directly or via as part of extensions/configuration (later on). Some discussion here linkeddata/dokieli#284
Has some rough edges but will sort that out as we go.
It detects
<cite><a>s as potential candidates to robustify. Creates archive snapshots on selected links, updates the citation anchors with the versioned URL along with the version datetime stamp... then shows a clickable Link Decoration besides the anchor.
w3.org anchors are acting a bit weird because Content-Location on some stuff points to Overview.html .. not sure if it is the Internet Archive messing with me or what..
dokieli software or dokie.li site management?
@michielbdejong BTW, how did you try to create a new doc?
on my pod I went to https://michielbdejong.inrupt.net/public/, made sure I was logged in, clicked ‘+’ then ‘d'
It did create https://michielbdejong.inrupt.net/public/some-dokieli-doc but then that shows just [object Object]
Can you try saving to /foo.html and see?
Cool
let me know if there’s more i can do to help!
Actually, dokie.li's inbox already uses NSS v5.1.6
I use NSS4 on my local machine.
I don't keep dokie.li's notifications around long though. People experiment all the time on the homepage.
showing all annotations gets a bit out of hand at the moment.. need to improve the UI
a lot of the annotations require authentication so the app ends up fetching the notifications on the homepage but then hits a 401 on the annotation. no point in keeping the tests around..
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?
@rubensworks https://github.com/rubensworks/rdfa-streaming-parser.js great! How do we get it on dokieli? :)
@csarven I haven't used simplerdf myself, but it should be just a matter of plugging it in here: https://github.com/linkeddata/dokieli/blob/master/src/simplerdf.js
The parser is based on RDFJS, so it should be compatible with RDF-ext
@rubensworks Yes, hopefully. I think SimpleRDF's parse is a bit buggy though. I had to patch it up the go because we couldn't get to an upstream package.. IIRC something DOM related. So, maybe if we change all of the parsers/serialisers in SimpleRDF to use whatever RDFJS is available, that'll work.
@csarven This may also be relevant for you then: https://www.npmjs.com/package/rdf-parse (the RDFa parser will be added to that soon)
It's basically a convenience package that exposes the same functionality that Comunica uses to parse RDF files.
Not sure if it will work well in your pipeline though.
It's basically a convenience package that exposes the same functionality that Comunica uses to parse RDF files.
Not sure if it will work well in your pipeline though.
We also need Turtle and JSON-LD serialisers.
@csarven I'm not really familiar with the internals of Dokieli, but LDflex, Clownface or rdf-object may be good alternatives for SimpleRDF.
Serializers for Turtle and JSON-LD exist that are based on RDFJS exist as well :-)
Serializers for Turtle and JSON-LD exist that are based on RDFJS exist as well :-)
- https://www.npmjs.com/package/n3
- https://www.npmjs.com/package/jsonld-streaming-serializer
(no convenience package for these exist yet though, but I intend to make a similarrdf-serializepackage some time in the future)
But if you need JSON-LD framing, then you'll probably have to use this one: https://www.npmjs.com/package/jsonld
Do one of those helper packages let you set the subject URI so that you can grab its p,o?