Launched: Hyperlink Node Directory

This started out as a thinking out loud type post a few weeks ago.  At that time I couldn’t really think of a straight forward use for it but my instincts told me it could be useful or somebody would figure out a use for it eventually.  Anyway I spent the week before Christmas 2018 getting things set up.


Okay, a hyperlink node and “clump of links” are synonymous. If I call your link page a hyperlink node it suddenly sounds legit. 🙂

The Hyperlinks node directory is an index of individual collections of web links, by type.  Therefore it indexes: blogrolls and following pages, directories, search engines, linkblogs, link pages, niche directories, webrings and other significant collections.  Comments are enabled for each listing, if you have a thought on a listing, please share it.  These collections often map out odd little corners of the web.


Thinking on it some more, I think it has value for: 1. discovery, finding new sites and blogs to follow by seeing what other people have taken the time to link to, 2. eventually I think it might be useful for indexing communities, 3. establishing, at least one, central index of decentralized search and the hyperlinking guerrilla war against the search monopoly silos, 4. an aid to reestablishing “surfing the web”.  There may be more that I have not thought of.

The big utility for me is having a place to list these when I stumble across them, so they can be shared, rather than just bookmarking them (or worse forgetting to bookmark them).

Challenge #1: Build Your Own

My first challenge to you is build your own node: Easiest would be an old fashion link page or a blogroll/following page; or maybe a linkblog or a linkblog-directory hybrid; or even a directory.  Whatever you feel like, build it and show people websites you like.  Examples and ideas are in the directory.  You can do this.

Challenge #2: List It Here

You might already have a linkblog, link page or big blogroll, if so you can either add the URL to the directory or you can send me the URL via the contact form (hopefully it works) at the bottom of this post and I will review it for inclusion.  It dose not even have to be your own, if you run across something drop me the URL and I’ll look at it.

Or if you build something for Challenge 1, come back and list it.

The idea is to have a lot more of these all across the indieweb so web surfers can find human reviewed recommendations. Like Word of Mouth recommendations from people you trust.

I hope this is in some way useful.  Thanks!

Be sure to include the URL to your node in the form below:


Liked this post? Follow this blog to get more. Follow

Replied to

In reply to: Federated Wiki and Directories by Kicks Condor



Federated Wiki


I like the idea, but like the author says, it’s best for working on one narrow subject for each instance which would mean I, being a generalist, would end up with 20 or 30 Fed wiki’s. Gah!

I think we start talking about federating our directories


This could help spread the net wider plus leverage two indexes for more depth.  Sounds like a portal page, and the public might find that more useful.


central search engine


There are a couple of good off the shelf, open source search engines that can crawl across multiple domains.  My suggestion would be to try those first, see what the bugs, limitations are before spending the time coding something new.  This might be the easiest thing to execute.

Another option might be a metasearch script.  It the old days there were several types: 1. Parallel search: this was the easiest, a search would simply return the top X number of results from engine1 then engine2 then engine3 etc.  No attempt to blend the results or change the ranking so it was a easier scrape to code.  2. returned results and simply showed you a list of engines that had that same site in the first X results.  Again these were scrapes.  I don’t think these early meta search engines had any algo, you just looked at the result and if 2 or 3 engines all had that site on the first page it was probably decent.  3. The most sophisticated meta search engines use API’s and there really isn’t much we can do with that.

My point is #1 Parallel search might be doable.  There may be some open source metasearch scripts around that could be adapted.

Portal: I think I will throw around portal ideas in another post rather than clutter up this one too much.


categorization systems


This could be as simple as a spread sheet like table cross reference: this category on KicksSearch corresponds most closely with this category on Indieseek.  And a reverse one.  Each cat. name being a link to that category. Might encourage deeper browsing.  Also simple HTML.

Or it could be a flow chart but in any event keep it simple and clicky. (Portal)


collecting submissions


I’m getting a brain flood of proto-ideas:

  1. Something like
  2. Twitter submit:  Put out a Tweet (these could be themed) asking for submissions all they have to do is retweet with a URL they want to submit.  Cherry pick the best.  (Heck we could do this right now since both blogs and Twitter support webmentions.)

These could be important, because there seems to be some sort of resistance to submitting URL’s right now.

syndicate entries

This may not be exactly what you are thinking of but:

  1. RSS feed: the directory already makes this of the 5 newest sites added.
  2. Toplist Generation: I know I can generate just about any type of top list available (ie. Top 10 Categories, Top 5 links by Clicks, Top Rated, Newest Comments, etc.)  There is also a way to export these top lists via JavaScript.  I have no idea how this all works but it’s there.

Directory of Directories?

This may be only useful in the future.  I know we have slightly different definitions of directories, but we could easily make a directory of directories if there are enough quality sites worth indexing.  I just mention this because my license for WSNLinks lets me use as many copies as I want, with full support, so long as they are on the domain or a subdomain of it.  Just FYI.

Liked this post? Follow this blog to get more. Follow