Vouch is an extension to the webmention protocol. Webmentions usually have two parameters…source and target. Target is the URL on your website that the Source URL is linking to. The vouch parameter is a third URL to help the target determine whether or not they should accept the webmention. This...
I’ve got a somewhat reasonable bookmarklet for quickly following people, though it’s not marked up with XFN data (yet) — perhaps another data field for Post Kinds? I do wish that there was either a mechanism for adding those to my Following page via the WordPress Link Manager or someone had a means of parsing lots of follow posts so I could quickly have data for both Vouch as well as for microsub readers either via my follow feed list or via OPML export and/or OPML subscription. WordPress obviously has some of the infrastructure built already, but there’s certainly a more IndieWeb way of doing it that wouldn’t require side-files like OPML.
When I read Shanske’s post, I really liked the idea, but was concerned about having an old-school blogroll. Of course this may have been misreading it.
A few years back I had a go at organising my blogroll using Sheets and representing it dynamically. The problem with this is that there is not much I can do with it and it is tedious to maintain, especially as my current workflow involves updating two spaces.
I really like your idea about having a ‘directory’. This reminds me of Chris Aldrich’s following lists. Like Aldrich, I just wish there was an easier way of adding a link/site and having this automagically added to the page. I assume that in part that is what you have?
Replied to Memo: Announcement: The Future of Blog Snoop Blog Directory by Brad Enslen (Brad Enslen)
Brad, much like Kicks Condor, I think you’re making a laudable effort, and one of the ways our work grows is to both keep up with it and experiment around.
If I recall, programming wasn’t necessarily your strong suit, but like many in the IndieWeb will say: “Manual until it hurts!” By doing things manually, you’ll more easily figure out what might work and what might not, and then when you’ve found the thing that does, then you spend some time programming it to automate the whole thing to make it easier. It’s quite similar to designing a college campus: let the students walk around naturally for a bit then pave the natural walkways that they’ve created. This means you won’t have both the nicely grided and unused sidewalks in addition to the ugly grass-less beaten paths. It’s also the broader generalization of paving the cow paths.
In addition to my Following page I’ve also been doing some experimenting with following posts using the Post Kinds Plugin. It is definitely a lot more manual than I’d like it to be. It does help to have made a bookmarklet to more quickly create follow posts, but until I’ve got it to a place that I really want it, it’s not (yet) worth automating taking the data from those follow posts to dump them into my Follow page for output there as well. Of course the fact that my follow posts have h-entry and h-feed mark up means that someone might also decide to build a parser that will extract my posts into a feed which could then be plugged into something else like a microsub-based reader so that I could make a follow post on my own site and the source is automatically added to my subscription list in my reader automatically.
In addition to Kicks Condor, I’me seeing others start to kick the tires of these things as well. David Shanske recently wrote Brainstorming on Implementing Vouch, Following, and Blogrolls, but I think he’s got a lot more going on in his thinking than he’s indicated in his post which barely scratches the surface.
I also still often think back to a post from Dave Winer in 2016: Are you ready to share your OPML? This too has some experimental discovery features that only scratch the surface of the adjacent possible.
And of course just yesterday, Kevin Marks (previously of Technorati) reminded us about rel=”directory” which could have some interesting implications for discovery and following. Think for a bit of how one might build a decentralized Technorati or something along the lines of Ryan Barrett’s indie map.
As things continue to grow, I’m seeing some of all of our decisions and experiments begin to effect others as these are all functionality and discovery mechanisms that we’ll all need in the very near future. I hope you’ll continue to experiment and make cow paths that can eventually be paved.
Featured Image: Cows on the path flickr photo by Reading Tom shared under a Creative Commons (BY) license
Syndicated copies to:
Syndicated copies: