Skip to main content

Home/ Diigo Community/ Diigo API - Seeking advice on how to reach out to developer community
Maggie Tsai

Diigo API - Seeking advice on how to reach out to developer community - 361 views

api developer suggestion 4.0 application programming interface

started by Maggie Tsai on 09 May 08
Graham Perrin liked it
  • Daniel Andrlik
     
    The API appears to be down. :-(
  • Maggie Tsai
     
    Sorry, doing an update. Should be up. Please advise. Thanks
  • Daniel Andrlik
     
    So it is. Rocking.
    Maggie Tsai wrote:
    > Sorry, doing an update. Should be up. Please advise. Thanks
  • Pierre-Yves Gillier
     
    IMHO, before advertising, you should finish main features of this API. Getting bookmarks is great, but a lots of devs will try to use tags and/or lists.

    To be honest, I'm writing a plugin for my weblog system (habari) which will integrate Diigo links as a silo. But now, I can't give it to users as "bookmarks" is the only feature available.
  • Graham Perrin
     
    On 12th May 2008, Pierre-Yves Gillier suggested:

    > finish main features of this API.

    > a lots of devs will try to use tags and/or lists.

    > I can't give it to users as "bookmarks" is the only feature available.

    +1
    to extending and improving the APIs.

    Historically:

    * a plan to publicise the API was announced in April 2008 http://groups.diigo.com/Diigo_HQ/forum/topic/3049

    * alpha of the API was publicised in May http://groups.diigo.com/Diigo_HQ/forum/topic/3776

    * http://www.diigo.com/tools/api currently comes under the banner of Diigo V3 beta

    * and Diigo recently have a mass of suggestions to consider ;)
  • Graham Perrin
     
    Subject: thanks to Diigo (for improvements to groups-related behaviours) and patience (concerning APIs)

    > +1
    > to extending and improving the APIs

    After weeks/months of ridiculous busi-ness with bug reporting, suggestions, general chit-chat and occasional misunderstandings:

    Now is a VERY good time for me to say a HUGE thank you to Diigo for recent improvements to groups-related behaviours.

    Flow
    ====

    The ways in which sticky notes, underlying highlights and page comments are flowed - to multiple groups - feels REALLY GOOD.

    Previously I might have rated the experience 3/10.

    Now, I rate the experience:

    * 9/10
    * intuitive.

    (From me, an unusually short list of points, which reflects the fact that I generally use Diigo with ease, without being upset by the UI.)

    ----

    @ developers beyond Diigo who may be waiting patiently for appearance of the Diigo Groups API

    Whilst I am not a developer: I do have keen interest in related developments.

    From what I can tell (guesswork, no insider knowledge) the many open discussions in this forum do subtly, but SIGNIFICANTLY steer the UIs and presumably the related APIs.

    Best,
    Graham
  • Graham Perrin
     
    In May 2008, Maggie Tsai wrote:

    > Hi everyone,
    >
    > If you have a chance to try out diigo API, love to get more
    > feedback before we "formally" announce it to the public.
    >
    > Also, like to seek out your advice - what may be the best ways to
    > reach out to the developer community about diigo and its new API?
    > We'd love to spread the news and have much wider diigo adoption
    > within the developer community. Their participation and knowledge
    > sharing could greatly benefit the Diigo community.
    >
    > Thanks!

    @ Diigo

    Please: is it too early to ask whether forthcoming Diigo 4 (alpha, beta or release) will precede, coincide with or follow development/announcements relating to APIs?

    http://groups.diigo.com/Diigo_HQ/forum/tag/api
  • Graham Perrin
     
    Google Wave, which will be open source, is one to watch.

    http://groups.diigo.com/Web2/bookmark/tag/wave

    Google's presentation, of the early developer preview, is worth watching if you have an hour and a half to spare.

    1. IMO Diigo services should fit somewhere, probably in more than one place, very neatly.

    2. The three Ps (product, platform, protocol) may provide much of the interop stuff (required by some users of Diigo) without devaluing the core features of Diigo.

    I'm only around twenty minutes through the video, but I'm tempted to view this as an opportunity for developers to:

    * focus more on what they know and love

    * focus less on maintaining knowledge of, and compatibility with, external systems/services/APIs.
  • Graham Perrin
     
    Maggie Tsai wrote:

    > We'd love to … have much wider diigo adoption within the developer
    > community. Their participation and knowledge sharing could greatly
    > benefit the Diigo community.
    >
    > Thanks!

    Recent requests:

    Please add a JSON callback parameter on the API (2009-04)

    API: POST and PUT: parameter for read, unread or readitlater (2009-06)
  • Graham Perrin
     
    Cross reference
    Diigo API (2009-11-10)
  • Graham Perrin
     
    soulgrind r wrote:

    > very few diigo apps, extensions or mashups out there

    Amongst the bookmarks tagged http://groups.diigo.com/group/Web2/content/tag/PubSubHubbub Salmon Protocol could be extremely relevant to Diigo.
  • Soul Book
     
    Diigo API group would be very nice. It might actually get some action going, and i doubt most of the community would be interested in the posts.. so it'd make sense to separate them out.
  • Graham Perrin
     
    > Google Wave…  one to watch … Diigo services should
    > fit somewhere, probably in more than one place, very neatly.

    For what I imagined, Google Wave is not proving so friendly.
    There's a public wave permalink to a blip, wavelet or wave
    (short URL: http://ur1.ca/fv8l)
    that highlights the lack of permalinks. In brief:

    * multiple ways to refer to a wave (no single definitive URL)
    * no way to refer to a wavelet
    * no way to refer to a blip
    * no way to refer to a point in playback.
  • Graham Perrin

To Top

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