DiigoAnnotation

This page happily erupted out of the WikiMail section of FridemarPache ‘s Homepage, of course with the consent of all its participants. ;-)


Welcome, Fridemar! Thank you for your contributions!

  • Hi Lion, great to see you here; thank you for help to make me aware of your feelings and arguments. – fp

Diigo is interesting, but I (and I suspect several others in the CommunityWiki) am not using it for a few reasons.

    • That’s good to know. – fp
  • We are basically a CommunityTiedToOneTechnology. If we move to interact by another interface, it must be a shared interface. To split the interface into users and non-users, especially as a means of interacting with our core content, is to split the community.
    • God beware! We are here to unite and not to separate. – fp
  • Public Visibility: We can just leave our comments here, and then everybody, regardless of whether they use Diigo or not, can see our conversation.
    • Yes, everybody in the sense of as many people as possible, I understand and agree. This is especially true now, where Diigo is in Beta and sometimes it works and sometimes not. But please, don’t take it as offence (yes, I feel similar, when I oppose and won’t lose dear people), when I see in Diigo annotations a great potential to reach a lot more of additional community minds. Before I used Diigo annotations massively, (two weeks ago or so), Google:fridemar had ca 600 hits, (My username is fridemar there.) Now the number of page references are incredible. I even didn’t know, what on earth, the Google brought up, even my oldest insignificant postings, I ever made. This proves to me: PublicVisibility? gets a boost, when working with Diigo annotations. Imagine the order of visibility, when wikis discover this marble. – fp
  • Diigo is not OpenSource. We are quite adament, with only a very tiny handful of exceptions, (namely, Skype, and, for a brief time, MoonEdit, until we discovered [[gobby?]], which became our OpenSource replacement,) about the use of OpenSource, whenever possible. Baring OpenSource, open standards, and when I next get into Internet Telephony again, I’ll be using Gizmo. If we are to get into annotation, it is most likely (I believe) that we would decide to go with one of many OpenSource platforms for doing it.
    • Yes, and that’s why I point to CritLinkMediator the great first web annotation engine, invented by KaPingYee. BayleShanks had started to modify a bit the Perl script for being used on wikis. This software is free, in the sense, that the author of it, KaPingYee gave us permission to adapt it to wiki. This fine guy (I am just a guy) offers the source code on his homepage, even without losing a word, of asking him permission to use it. With CritLinkMediator each webpage can annotate each other webpage, especially each wiki page can annotate each other wiki page. To modify the Perl script, I suppose only less than hundred lines need to be modified, if we can hook it up on an appropriate WikiEngine in Perl. This wikiengine would replace the rudimentary Editmodule of CritLinkMediator. On the other hand we should restrict the different annotation options to those of its underlying WikiEngine (not using arbitrary connections). If you know a wikifriendly perl programmer, let him/her know it. Using another language is coupled with more effort. You have to tranlate it into, say Python, and add some GNU WikiEngine in Python. As KaPingYee is fond of Python (http://barcamp.pbwiki.com/KaPingYee), I strongly suppose, he would love to give support. (I bet, he would support other variants too, if time allows him to do so.) – fp
  • No Way Out: I do not believe we can export our content automatically from Diigo, should we decide to migrate from it. (Can we automate migration out of CommunityWiki, which is an OddMuse? Absolutely.)
    • I am a friend of freely relocatable content (with leaving a backlink (and notifying the authors of it, if possible)). In this way content has better chances to move to places, where it is mostly welcome and useful. – fp

Please do not take offence, but I would like to ask you: Do you have any agreements with the corporation that licenses Diigo, any of its affiliates, or any of it’s members, outside of the standard license agreement to use Diigo?

    • Thank you Lion, for asking that. My answer to this is: “No.” I am neither an agent of Diigo nor one its affiliates. Nevertheless I have been giving the Diigo people ample feedback in their/our (hey, I am a Diigo community member, too) forums and annotations. – fp

I think Lion’s comments re DiiGo are quite interesting and that they are worth preserving on a dedicated page. (I would do this, but this is a HomePage and I’m loathe to just move Lion’s comments into a new context unilaterally.)

Thank you dear Hans, dear Lion : if you both are ready and happy with Refactoring the discussion onto a new page, I am in emotional and cognitive resonance with you ;-). It goes without saying, that I leave an explicit BackLink to the new page and continue to discuss and collaborate with you there. Both pages are then FriendPages, to each other, humans included :-) Thank you./ Sometimes later: Now, we are here, can delete transitory procedere stuff and continue our conversation. – FridemarPache

Define external redirect: gobby PublicVisibility

EditNearLinks: FriendPage WikiEngine OpenSource KaPingYee HomePage DiiGo CritLinkMediator

Languages: