Bookmarks as a part of serendipity

A reflection on using my own blog to reclaim my bookmarks and then syndicate them to other sites, such as Twitter and Diigo.


My one word this year is intent. For me this means many things, one of which is to consider my digital presence. In a post reflecting on Mark Zuckerberg’s attempts to fix Facebook, Doc Searls says that one of the lessons learnt is that we all live digital lives now:

So let’s at least try to look below what big companies, Trump and other dancing figures in the digital world are doing, and try to look at the floor they’re dancing on—and the ground under it. That ground is new and unlike anything that precedes it in human experience. Nothing matters more than at least trying to understand it.

For me, a part of ‘understanding it’ is in reclaiming some of the processes that have been outsourced to third-party platforms. This does not always mean leaving silos completely, but rather not being dependent on them so that if the door shuts or the terms of use change, there is no concern in having to leave. See for example the recent announcement that Storify is shutting down. One recent attempt I have been tinkering with is an effort to reclaim my bookmarks.


Capturing the Web with Radio3

I have been using Diigo for quite a few years. My workflow has gone through a number of iterations, such as emailing links to batch processing favourited sites. This has largely been dependent on my mobile operating system. For example, I have found the Android Diigo app a lot easier to share to than iOS. (Things may have since changed though). My frustration though was that I was completing a number of steps separately.

After exploring the features and affordances of Google+, I came upon Dave Winer’s Radio3 Linkblog, which allows you to push links out to various platforms, whilst also maintaining your own RSS. It involves selecting a site or quote and clicking on the bookmarklet to generate the short post. The creation of a separate feed provides the means to automate processes with IFTTT. This includes saving links to Diigo.

The problem I have with this process is that although I have an archive of my tweets and links via Diigo, I am dependent on these platforms for maintaining an archive of my linkblog. I trialed using an IFTTT recipe to create a weekly digest as well as the built in option to Diigo, however I was not satisfied with any of these solutions. One problem I faced was the inconsistency of the RSS feed produced by Radio3.

I have found that if I save a link with the bookmarklet without selecting any text, there would be no title included in the feed, even if I added or adjusted the description included in the textbox. Whereas, if I highlighted a chunk of text, the title is added. I guess the workaround would be to select the heading if there is nothing specific I wish to highlight? This seems a strange thing to complain about in regards to one of the forefathers to RSS and probably shows a lack of awareness on my behalf for how Radio3 works.

Another frustration with using Radio3 to send links to Diigo is that I really like capturing quotes when I save links. This is something that I have done for a while and one of the reasons that I like Radio3. I could not figure out how to bring these into the description in Diigo consistently, let alone as annotations. I even took to annotating the quotes with the Diigo browser extension. I wonder if Zapier would do a better job, but until I fork out the money for a paid subscription I am not going to know.

In the end, I could probably make Radio3 work for me. Probably deploying a script to collect everything, as Tom Woodward does with Pinboard, but I feel that I am almost doing that manually with the creation of my newsletter. I just feel apprehensive moving forward depending upon something held together by Dave Winer’s very good will. If it were open sourced, this may be different, but it is not.


Collecting Bookmarks

The next step then in my bookmarking journey has been to test out the idea of saving links on my own site and then syndicating them elsewhere. I have been exploring various post kinds lately, however yet to tinker with bookmarks.

One of the inital challenges was how to syndicate. Like most, I had installed –Jetpack and used that to publicise to various social media sites. This is a relatively easy process where you activate the various connections by giving permissions. However, Jetpack is limited in what sites it supports. There is no option to connect with Diigo.

I therefore installed the Social Network Austo-Poster (SNAP) plugin. Although I could generate a custom feed based on my bookmarks and use this with IFTTT, I would prefer to do something within my own site. One of the differences between SNAP and Jetpack is that rather than just give access you need to go through the process of generating API keys. This to me is closer to Searls’ call to understand our digital reality. Although this might seem daunting for some, the plugin provides thorough documentation to support users.

What I like about SNAP is that you can set a default structure for auto-posts, combining a number of predefined ingredients, but you can also quickly customise these when needs be. So if you want to share with a specific user or hashtag on Twitter, but not on Diigo, then you can adjust the Twitter description.

The last thing to consider with using my own site is developing a clear process for saving bookmarks. My first step was to create a bookmarklet using Chris Aldrich’s Post Kinds template. Also, I setup a process for sharing via Mobile using URL Forwarder app. This was a part of the puzzle missing with Radio3.


What Next?

I like the idea of collecting my bookmarks on my site. However, it has forced me to reflect on a number of things. One is the ability to properly syndicate to Diigo and Twitter. With Radio3, the publicised links connect to the corresponding site, whereas when I bookmark using my site, it shares the link to my post rather than the original site. This has me rethinking why I bookmark and POSSE. Maybe I do not need to share links to the original source, especially when my bookmarks have secondary information.

Another interesting feature to using my blog has been the ability to link to other sources within my descriptions. This is something that I do with my newsletter. On the other hand, I wonder if every link needs this level of detail. An answer to this maybe to utilise some other response post kinds, such as Likes and/or Favourite to support my blog as a resource.

This also leads me to wonder about the place of my Wikity blog. I really like the concept of constructing knowledge and ideas over time, however, I do not connect with other Wikity sites, one of the features Mike Caulfield built into the theme. I therefore wonder if these posts could be added as Notes or Articles, as I like having a title and in some themes the title of notes is chopped off.

Maybe rather than using Likes or combining my Wikity posts I maintain these other spaces, such as Radio3 and use them for specific purposes. Or maybe I need to dive into Known again, even if it seems that people are leaving? I think for now I might continue bookmarking with my site and see where it all goes.


So what about you? What process do you use to bookmark links for later? Has it changed over time? As always, comments welcome, especially if you have any tips or tricks that might help me on my way.



Also posted on IndieNews


If you enjoy what you read here, feel free to sign up for my monthly newsletter to catch up on all things learning, edtech and storytelling.

Reclaiming My Bookmarks by Aaron Davis is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

33 thoughts on “Reclaiming My Bookmarks

  1. Chris, I have since worked out that with the SNAP plugin that you can change the URL when sharing out to different spaces. I make this choice on a case by case basis, as there are sometimes when I feel that it is worth sharing my notes, while other times I am more interested in paying the original post/resource forward. I guess what you highlight Chris is that there are always options and as with all workflows, they are never complete.

    via Hypothesis

  2. Thank you Wouter for the read. I accept your criticism of my practice. To explain my personal intent, I used to use Diigo to capture such links. However, I turned to using my own sites as I wanted to own the data. I am not worried about whether it is ‘blogging’ or a ‘weblog’, my focus is on collecting the dots to develop longer form reflections upon. I felt awkward when I clicked on Dave Cormier’s site and found it was full of my pingbacks. My site therefore acts as something of a canonical link in-lieu of the actual link.
    In regards to following the firehose, I have discussed was of adjusting the feed before. However, I am yet to set up a page like Chris Aldrich. From your points, I guess I should.
    I did think that maybe my monthly newsletter sufficed, obvious not.
    As a side note to all this, I also wondered about what it might mean to capture absolutely everything to form a deeper appreciate my presence on the web, but I long gave up that hope. I read way more than I respond to.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.
https://readwriterespond.com/2018/01/reclaiming-my-bookmarks/
readwriterespond.com
CC-MAIN-2024-10
123778
application/http; msgtype=response
sha1:PJQZ6IEN7QUK3FP5VTZ5DELNRPQETLIG
<urn:uuid:396782c4-64ec-4cdb-9cc7-a17f55a4cf93>
2024-03-03T12:40:04Z
143.110.208.221
text/html
sha1:UCJY5IO3AE2SABQJZXN5FABWLZSCRCNG
<urn:uuid:6f5ebec3-61d4-43f7-8ca4-8b8ea123c723>
https://readwriterespond.com/2018/01/reclaiming-my-bookmarks/
response
<urn:uuid:8582b656-45f2-40b4-8c7d-e6fb90ab7bc7>
isPartOf: CC-MAIN-2024-10
publisher: Common Crawl
description: Wide crawl of the web for February/March 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-126
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/