Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 24 02:51
    merryjane742 starred linkeddata/dokieli
  • Aug 23 11:25

    csarven on master

    Rea^Cgn RL Link Decorations (compare)

  • Aug 22 20:52
    osharper starred linkeddata/dokieli
  • Aug 21 12:02
    csarven commented #137
  • Aug 20 09:20
    dragonman225 starred linkeddata/dokieli
  • Aug 19 21:15

    csarven on master

    Minor Refactor citations and note pos… (compare)

  • Aug 18 22:30

    csarven on master

    Add MotivationSigns to Config (compare)

  • Aug 18 21:06

    csarven on master

    Add cito:cites* to Vocab, docum… Minor selectArticleNode fallbacks to … and 1 more (compare)

  • Aug 18 11:59
    davidcorbly starred linkeddata/dokieli
  • Aug 16 20:40

    csarven on master

    Add C.Delete button (compare)

  • Aug 16 09:25
    csarven commented #259
  • Aug 15 15:36
    timbl commented #259
  • Aug 14 16:46

    csarven on master

    Bump (compare)

  • Aug 13 11:27

    csarven on master

    Minor (compare)

  • Aug 13 11:25

    csarven on master

    Move buildReferences updateRefe… Show inline citations and jumpl… (compare)

  • Aug 12 15:36
    infredulous starred linkeddata/dokieli
  • Aug 12 11:25

    csarven on master

    Add targetInSameAs check for an… (compare)

  • Aug 12 10:41

    csarven on master

    Use margin instead of padding o… (compare)

  • Aug 11 22:46

    csarven on master

    Minor (compare)

  • Aug 11 11:53

    csarven on master

    Minor (compare)

Sarven Capadisli
@csarven
This is something that both server and client can improve somehow. Server has to do its thing any way, and the client can play along nicer by discovering and at least deciding whether to comply or not.
I can see dokieli UI saying sometihng like: this inbox prefers to have all of the resources mentioned in the notification to be public-read, do you want to make it so (annotation public-read) and then send a notification"?
if user says nopes, then it can proceed with the annotation but won't sent a notification.
server or some inbox agent or whatever.. needs to keep an eye on what's coming in any way.
That's only for the initial entry. Of course the annotation can be private at any time. So, I suppose seomthing like an inbox agent can do its management at its leisure.
Sarven Capadisli
@csarven
Not straight forward to compare with Hypothesis because they have a custom API working against a central server.
@bencomp Do you mean that their UI lets you know that some annotations are marked as private and that you can't actually read the annotation?
We could do that now.. but I don't see the point. Unless we add stuff like 'Ask Alice if you can read this resource'
Sarven Capadisli
@csarven
(and that's a different hting altogether.. which was discussed and will probably get implemented on Solid servers I think)
bencomp
@bencomp
@csarven I believe a long time ago I saw somewhere on their website Hypothesis say they support Web Annotations, but I haven't discovered yet how. The UI indeed lets me select access levels for each of my annotations. Other users won't even know that I created a private annotation. It would be nice if dokieli also allowed me to adjust access permissions, so that I don't need to either think of setting them on the container beforehand or realising afterwards.
Sarven Capadisli
@csarven
@bencomp I've documented the architecture of Hypothes.is at: https://csarven.ca/linked-research-decentralised-web#hypothes.is , and an overview of interop alongside dokieli: https://csarven.ca/linked-research-decentralised-web#dokieli-hypothes.is
@bencomp Setting access permissions is a non-issue. Planned todo. I agree, nice to have.
What I was saying earlier about H's case was that, because the client application works with a preconfigured H server, it already knows which annotations to show or not for the user.
Dmitri Zagidulin
@dmitrizagidulin
@csarven oh, VERY cool, re hypothes.is article
Sarven Capadisli
@csarven
@dmitrizagidulin in what why?
Dmitri Zagidulin
@dmitrizagidulin
@csarven just in that, I was wondering what the interop with dokieli & hypothes.is was.
Sarven Capadisli
@csarven
@dmitrizagidulin Not sure what your takeaway was, but practically there is not much to go with. They're doing their own thing.. different identifiers for humans and machines, hardcoded URI templates, each client instance is wired up to only speak with a particular server.. Sounds awfully familiar? no WAP, LDP, AP.. So, dokieli can't talk to their stuff. There is one area of interop (IIRC have mentioned): if annotations that dokieli created somehow gets migrated to H's server, their client could potentially reuse it.. but since they have all data coming from elsewhere and their client is mostly depended on it, who knows what'd happen. dokieli can't reuse their stuff because it can't discover it.. and there is no way in hell dokieli will hardcode an arbitrary URI Template =)
Dmitri Zagidulin
@dmitrizagidulin
@csarven I see :(
bencomp
@bencomp
Somewhere on my list of IMHO Great Ideas is a service that creates a bridge from Hypothesis to Web Annotations. I only need to find time.
gpbak
@gpbak
When I try to save a new document or publish using dokie.li I get an error message "you are not authorized". What's going on with that if someone can help please? Thanks!
Sarven Capadisli
@csarven
@gpbak Where are you trying to create a new doc? What's your WebID? Did you sign in using 'OpenID Connect'?
Adrian Gschwend
@ktk
@csarven if I get that correctly https://www.w3.org/TR/ldn/ is using Dokieli?
Sarven Capadisli
@csarven
@ktk Do you mean the HTML pattern?
If so, yes. Recent W3C spec's HTML and dokieli's is quite similar, so it was straightforward. The CSS worked mostly out of the box.
See also https://linkedresearch.org/ldn/ for the ED. That has a few other things like inbox/annotationService.. and loads dokieli - showcases LDN as well.
Adrian Gschwend
@ktk
very cool
I only used ReSpec so far but not super convinced by it
Sarven Capadisli
@csarven
I'd like dokieli to be "mature" enough for spec editors to use it. Right now people are compiling Markdown mixed with JSON(-LD), magic.. to generate the HTML output htat we see.
There is also Bikeshed
Adrian Gschwend
@ktk
yeah didn't get much further with that either ;)
Sarven Capadisli
@csarven
Ok, did a tonne of code reshuffling.. also got AutoSave working for both localStorage and HTTP writes. Triggered by going into Edit mode and selecting the type of autosave. Autosave timer uses 1m.
I will remove the checkbox for localStorage because that's clutter. It autosaves to localStorage but there is no way to recall. Basically what needs to happen is if dokieli detects that you were in offline mode and have changes that's "ahead" (just document modified timestamp for now probably) it will prompt the user about that situation and ask them if they want to update the HTTP resource
I suppose that will happen automatically right now any way.
So, maybe we just need to remove the checkbox for localStorage. Hmm.
Sarven Capadisli
@csarven
but what if the resource has changed since your local (while offline) updates. How do we resolve that? Simplest to ask which version the user wants to use.. diff/merge type of thing would be complicated right now.
^ @timbl Re AutoSave
Sarven Capadisli
@csarven
The checkbox for HTTP autosave should be removed as well.. eventualyl when I feel this is stable.
Need to track the hash of last save's content.. and only save if different hash
Sarven Capadisli
@csarven
Should HTTP autosave be on by default when in Edit mode? My initial thought was that it should be off in case the user wants to make edits privately (in their browser) and decides to save it somewhere else (via Save As).
I realise the convenience and less clutter of not showing the autosave checkbox (although many software do).
GoogleDocs doesn't have it IIRC
Sarven Capadisli
@csarven
Added message digest to determine whether doc was modified, and if so, updates localStorage or saves to HTTP
Adrian Gschwend
@ktk
btw the web-write is only to LDP endpoint right?
Sarven Capadisli
@csarven
@ktk No, plain ol' HTTP PUT (in the case of autosave). It will include ldp:Resource in Link header... so that LDP servers are happy too.
PUT text/html
Sarven Capadisli
@csarven
I suppose in this case dokieli can be a bit gentler by sending OPTIONS first... in case the server prefers or only llows POST or PATCH or something.. and in a different mediatype. However, alternatives routes complicates the overall system IMO.
dokieli uses OPTIONS heavily for notifications and annotations.
Sarven Capadisli
@csarven

Any opinions on whether autosave to localStorage at 1m interval should always be on? And also remove the checkbox option to enable/disable that?
Dmitri Zagidulin
@dmitrizagidulin
yeah, that seems reasonable. (possibly even shorten to 30 seconds)