Social Bookmarking to Wiki is about making it easy to send links to wiki.

The idea is that people in the wiki can organize, share links, and integrate them with the wiki content.


We imagine that a bookmark has a “lifecycle.”

It may look something like this:

  1. When people see memorable links, they save them to a SocialBookmarking service, UsingTags to index.
  2. If they find it very useful, they work it into their core bookmark hierarchy, carefully placed.
  3. Finally, if they continue to find use for it, they work it into an OpenContent wiki, canonical for the bookmark’s topic. For instance, a link about a Python tool would be worked into the Pythoninfo wiki. (…which is not OpenContent, but rather, a CopyrightTarPit.)
  4. Links of general go to WikiPedia.

This is based on the theory that:

CommunityWiki experiment

Our SocialBookmarkingToWiki rides atop SocialBookmarking service UnaLog.

Here’s how to use it!

  1. Get a unalog account.
  2. Install the bookmarklets it offers. (for more info on “bookmarklets,” read: Wiki:BookMarklets)
  3. Browse the web! When you see a page you want to note on CW, post it to unalog.
  4. In the description field, write:
 blah blah blah blah CW:[[PageName]] blah blah blah blah blah

Then, post it, and go back to whatever you were doing.

Within an hour, a TaoRiver script will note the link, and post it to the appropriate page on this wiki!

If it doesn’t work, that probably means Wiki or Blog (cats) have nudged the power cord, and the power has gone out to the hub connected to TaoRiver. When LionKimbro notices that he has no Internet, the script will kick in again, and pick up your link.

The source code can be found at SocialBookmarkingToWikiCode.


I’m going to try SocialBookmarking with Unalog. I chose Unalog since I want to use an open-source server, and I’d prefer to use a Python one since I think Python rocks so much that a Python-based server may evolve faster than a Perl-based one. I hacked the Foxylicious browser plugin to work with Unalog.

Since I’ve barely started, I don’t really know anything about it, but nevertheless I’ve been sort of thinking of the potential role of social bookmarking in organizing the web for people. Here’s my proposal for the future lifecycle of a bookmark (although it’s not a serious proposal yet, until I get more experience with social bookmarking). You could also think of this as a proposed process for collaborativly organizing links on the web:

  1. When a user first comes across a link that they want to remember, they save it to their social bookmarking service, using a few tags to index it so that they can find it later.
  2. Later, if s/he finds it very useful, s/he works it into their core bookmark hierarchy. Today, that means downloading it to their browser and adding it to their local bookmark hierarchy, but someday perhaps there will be a standard way to do this within the social bookmarking service. Until then, individuals can continue to share their core hierarchies by putting them on their websites.
  3. Finally, if s/he continues to find it useful and want to help others find the same link, s/he adds the link to an OpenContent wiki whose purpose is to serve as a canonical reference for the topical area of the bookmark. For instance, a link about a Python tool would be worked into the Pythoninfo wiki1.
  4. Links of use to a relatively broad segment of humanity are also added to general-use wikis like WikiPedia.

This is based on my theory that:

  • Adding a link to a social bookmarking service is fast, and a social bookmarking service can handle an unlimited number of links, so there’s not a concern about adding “bad links”. So this is a good place to put links when you see them.
  • Adding a link to your core local bookmark hierarchy is relatively fast, however, you don’t want to add every link you ever see into your core hierarchy; that would make it too big. This is a good place to put links that you really like and want to keep “near at hand”.
  • Adding a link to a wiki is slow, but is the most useful for others, because:
    • Tag-based social bookmark services are good but there can be tons of links with a given tag, making it hard to find interesting links just by browsing tags. In addition, different people have different ideas as to what the tags mean to them.
    • Local bookmark hierarchies are great but they are created by and for a single person.
    • Wikis can have hierarchies like local bookmark hierarchies but they can also support more general graph structures. Wikis deal with both of the problems with social bookmarking services. Wikis deal with the problem of “too many links filed under this topic” by allowing the community to refactor. Wikis encourage a community to come to consensus about which topics go where.
    • Wikis have the additional advantage of allowing bookmarks to be surrounded by a narrative of explanatory text, which allows a community to organize bookmarks in ways more efficient to navigate than either a flat tag structure or a tree.

See also

Oh, wow! Wow-wow-wow!

Whatever general interface exist for positing websites to social bookmark sites- they should be reusable with respect to wiki communities.

This might help us find better references and supporting evidence (and counter-evidence) for our ideas: If we can collectively manage links on the wiki, and combine our organization of links with our organization of wiki pages, then I would suspect we would have an easier time putting good links into our pages.

We could organize our links first through our categories, and then through our pages themselves.

BTW, BrianTempleton? made a thing for extracting LocalNames from a feed.

Also, I just want to make sure you know about it: Though, I have to admit: I much prefer Python to Perl. ;)

Yeah, I saw that in the D-lib article (I added the other open source ones mentioned in that article above). Also, I saw that is OpenContent, too, which is big. But I figure I can always export from Unalog and import into later if need be.

I agree that it would be neat to have a combined wiki/social bookmarking interface. I’m thinking this should be a part of the WikiRefactoringBrowser? (btw, I’m hoping that with Mozilla extensions on the frontend and WikiGateway on the backend, we have all the pieces needed to build a refactoring browser).

Bayle and I talked on Skype (during WikiWoodstock) about having something that reads a SocialBookmarking feed, and automatically appends new links to wiki pages.

So like: You’d be looking at a page, and you think, “Oh! This should be attached to ContentAndCommunity!” And so you would tag it with something like _communityWikiAutoFeed, and somehow suggest the page name as well.

Then this special script reads the feed once a day, and places all the links to the appropriate pages. It’d look for = Discussion = most likely, then go backwards looking for = Links =, and then if there wasn’t one, it’d add one just before discussion, and if there’s no discussion, it would just put = Links = at the bottom and start tacking on the list items there.

I really want to see this, and it shouldn’t be too hard to do.

Bonus points: Make it work with BayleShanks’ InterWikiGateway?.

Just add two (or more) tags - the script downloading bookmarks would check if any tag is a category at the wiki and add it there.


1. if it were OpenContent

Define external redirect: BrianTempleton InterWikiGateway

EditNearLinks: WikiRefactoringBrowser TaoRiver