Skip to main content

Home/ Diigo Community/ Nabble 2 embedded content incompatible with Diigo bookmarking
Graham Perrin

Nabble 2 embedded content incompatible with Diigo bookmarking - 118 views

resolved wontfix suggestion gate Unicode 0023 number sign hash

started by Graham Perrin on 06 Oct 08
  • Graham Perrin
    #1 Graham Perrin on 06 Oct 08
     
    I wish to use Diigo to bookmark - and more importantly to me, highlight/annotate key points - in areas of Plone support forums.

    I find that Diigo doesn't work in these contexts.

    Is the problem that forums there are embedded?

    Example: the permalink for a message within a topic there is
    http://n2.nabble.com/Deleted-users-still-listed-in-Plone-tp337260p337268.html
    and that redirects to
    http://plone.org/support/forums/general#nabble-td337260|a337268
    for a representation of the same topic, anchored to the message;
    but then when I attempt to bookmark the message the URL gained is
    http://plone.org/support/forums/general

    - which will take me nowhere near the topic :(

    A message similar to this is cross-posted to
    http://n2.nabble.com/Nabble-2-embedded-content-incompatible-with-Diigo-bookmarking-td1133746.html

    TIA for any advice
    Graham
  • Maggie Tsai
    #2 Maggie Tsai on 13 Oct 08
     
    hm, they have rather strange URL system that "re-directs"??

    Key principle - Diigo's annotation / bookmarking is URL-specific.
  • Graham Perrin
    #3 Graham Perrin on 16 Oct 08
     
    Maggie Tsai wrote:

    > hm, they have rather strange URL system that "re-directs"??

    The embedding (as they call it) is a foremost feature of Nabble 2:



    > Key principle - Diigo's annotation / bookmarking is URL-specific.

    Understood.

    We have for example two different messages within a single thread:



    and a completely separate thread


    but all are presented as anchors based upon a single URL

    and so we have many thousands of threads, probably thousands more messages at that one base URL.

    1) What's desirable - for content that's 'embedded' in this way - is for Diigo to gain the truly unique URL that's offered (albeit not immediately visible).

    Example: for

    within the 'More' menu we find the 'Permalink'


    2) If from the embedded views [ Classic | List | Threaded ] we choose Classic, then we typically find - at each presented thread - multiple 'More' menus, within each one a unique permalink.

    ----

    I imagine that it should be:

    * feasible for Diigo to gain (from the 'More' menu) the first offered permalink for a thread

    * less feasible to gain the permalink that's unique to a second or subsequent message within a thread.

    Thanks for your consideration.

    Kind regards

    Graham Perrin, Project/Media Development Officer
    CENTRIM - the Centre for Research in Innovation Management

    +44-1273-877922
  • Joel Liu
    #4 Joel Liu on 17 Oct 08
     
    We will eliminate the URL restriction on " # " in later version.
  • Graham Perrin
    #5 Graham Perrin on 17 Oct 08
     
    Joel and colleagues, thanks!
  • Graham Perrin
    #6 Graham Perrin on 12 Nov 08
     
    Joel Liu wrote:

    > We will eliminate the URL restriction on " # " in later version.

    With no pressure: please, for this improvement, does Diigo have in mind a timeline?

    Postscript: the context is, for me, http://groups.diigo.com/ploned/forum/topic/why-do-none-of-the-bookmarks-refer-to-plone-support-forums-7416
  • Graham Perrin
    #7 Graham Perrin on 20 Nov 08
     
    As the subject of redirection and anchoring has cropped up in another context, I'm updating my earlier example.

    We have for example two different messages within a single thread:
    * http://n2.nabble.com/multi-platform-WebDAV-problems-for-LDAP-authenticated-users-tp1131666p1131666.html
    * http://n2.nabble.com/multi-platform-WebDAV-problems-for-LDAP-authenticated-users-tp1131666p1514453.html

    and a completely separate thread
    * http://n2.nabble.com/How-to-migrate-_from_-ATBlob-_to_-ATFile-using-plone.app.blob-migrations.py--tp1519710p1519710.html

    but all are ultimately presented as anchors based upon a single URL
    * http://plone.org/support/forums/general

    and so we have many thousands of threads, probably thousands more messages at that one base URL.

    Postscript: http://www.diigo.com/annotated/5739fb316e3a5d13001d771419b2818a for an annotated view of this thread.

To Top

Start a New Topic » « Back to the Diigo Community group