👓 Just do it — by hand | Jeremy Cherfas

Read Just do it -- by hand by Jeremy Cherfas (Jeremy Cherfas)
So when I do syndicate out to a silo, I do it by hand. Sure it would be tedious if I wanted to do that for every little thing, but I don't. I share the things I want to share, in the way I want to share them.

I’ve noticed that I typically syndicate almost everything manually despite the fact that I’ve got the ability to do it automatically. Doing it manually actually gives me a greater feeling of ownership somehow.

I do miss the ability to have public comments coming back however…

Syndicated copies to:

Reply to Brad Enslen about The Future of Blog Snoop

Replied to Memo: Announcement: The Future of Blog Snoop Blog Directory by Brad EnslenBrad Enslen (Brad Enslen)
I’m hitting a fork in the road with this site and the experiment of using a blog as a directory of blogs.  The problem here is me: I’m running out of time.  I’m duplicating a lot … Source: Announcement: The Future of Blog Snoop – Blog Snoop Weblog Directory We’ll see what happens.  It...

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:

👓 Paving the cowpaths: using architecture concepts to improve online user experience | Elezea

Read Paving the cowpaths: using architecture concepts to improve online user experience by Rian Van Der MerweRian Van Der Merwe (Elezea)
In architecture desire lines or cowpaths describe well-worn paths that appear in a landscape over time. I discuss how this relates to web design.

This is interesting/relevant to the idea of “manual until it hurts”. I particularly like the twist idea at the end of looking at activity after-the-fact and then paving over those methods rather than starting at free range and then paving.

Syndicated copies to:

Some thoughts on highlights and marginalia with examples

Earlier today I created a read post with some highlights and marginalia related to a post by Ian O’Bryne. In addition to posting it and the data for my own purposes, I’m also did it as a manual test of sorts, particularly since it seemed apropos in reply to Ian’s particular post. I thought I’d take a stab at continuing to refine my work at owning and controlling my own highlights, notes, and annotations on the web. I suspect that being able to better support this will also help to bring more self-publishing and its benefits to the halls of academe.

At present I’m relying on a PESOS solution to post on another site and syndicate a copy back to my own site. I’ve used Hypothesis, in large part for their fantastic UI and as well for the data transfer portion (via RSS and even API options), to own the highlights and marginalia I’ve made on the original on Ian’s site. Since he’s syndicated a copy of his original to Medium.com, I suppose I could syndicate copies of my data there as well, but I’m saving myself the additional manual pain for the moment.

Rather than send a dozen+ webmentions to Ian, I’ve bundling everything up in one post. He’ll receive it and it would default to display as a read post though I suspect he may switch it to a reply post for display on his own site. For his own use case, as inferred from his discussion about self-publishing and peer-review within the academy, it might be more useful for him to have received the dozen webmentions. I’m half tempted to have done all the annotations as stand alone posts (much the way they were done within Hypothesis as I read) and use some sort of custom microformats mark up for the highlights and annotations (something along the lines of u-highlight-of and u-annotation-of). At present however, I’ve got some UI concerns about doing so.

One problem is that, on my site, I’d be adding 14 different individual posts, which are all related to one particular piece of external content. Some would be standard replies while others would be highlights and the remainder annotations. Unless there’s some particular reason to do so, compiling them into one post on my site seems to be the most logical thing to do from my perspective and that of my potential readers. I’ll note that I would distinguish annotations as being similar to comments/replies, but semantically they’re meant more for my sake than for the receiving site’s sake. It might be beneficial for the receiving site to accept and display them (preferably in-line) though I could see sites defaulting to considering them vanilla mentions as a fallback.  Perhaps there’s a better way of marking everything up so that my site can bundle the related details into a single post, but still allow the receiving site to log the 14 different reactions and display them appropriately? One needs to not only think about how one’s own site looks, but potentially how others might like to receive the data to display it appropriately on their sites if they’d like as well. As an example, I hope Ian edits out my annotations of his typos if he chooses to display my read post as a comment.

One might take some clues from Hypothesis which has multiple views for their highlights and marginalia. They have a standalone view for each individual highlight/annotation with its own tag structure. They’ve also got views that target highlights/annotation in situ. While looking at an original document, one can easily scroll up and down through the entire page’s highlights and annotations. One piece of functionality I do wish they would make easier is to filter out a view of just my annotations on the particular page (and give it a URL), or provide an easier way to conglomerate just my annotations. To accomplish a bit of this I’ll typically create a custom tag for a particular page so that I can use Hypothesis’ search functionality to display them all on one page with a single URL. Sadly this isn’t perfect because it could be gamed from the outside–something which might be done in a classroom setting using open annotations rather than having a particular group for annotating. I’ll also note in passing that Hypothesis provides RSS and Atom feeds in a variety of ways so that one could quickly utilize services like IFTTT.com or Zapier to save all of their personal highlights and annotations to their website. I suspect I’ll get around to documenting this in the near future for those interested in the specifics.

Another reservation is that there currently isn’t yet a simple or standard way of marking up highlights or marginalia, much less displaying them specifically within the WordPress ecosystem. As I don’t believe Ian’s site is currently as fragmentions friendly as mine, I’m using links on the date/time stamp for each highlight/annotation which uses Hypothesis’ internal functionality to open a copy of the annotated page and automatically scroll down to the fragment as mentioned before. I could potentially see people choosing to either facepile highlights and/or marginalia, wanting to display them in-line within their text, or possibly display them as standalone comments in their comments section. I could also see people wanting to be able to choose between these options based on the particular portions or potentially senders. Some of my own notes are really set up as replies, but the CSS I’m using physically adds the word “Annotation”–I’ll have to remedy this in a future version.

The other benefit of these date/time stamped Hypothesis links is that I can mark them up with the microformat u-syndication class for the future as well. Perhaps someone might implement backfeed of comments until and unless Hypothesis implements webmentions? For fun, some of my annotations on Hypothesis also have links back to my copy as well. In any case, there are links on both copies pointing at each other, so one can switch from one to the other.

I could imagine a world in which it would be nice if I could use a service like Hypothesis as a micropub client and compose my highlights/marginalia there and micropub it to my own site, which then in turn sends webmentions to the marked up site. This could be a potential godsend to researchers/academics using Hypothesis to aggregate their research into their own personal online (potentially open) notebooks. In addition to adding bookmark functionality, I could see some of these be killer features in the Omnibear browser extension, Quill, or similar micropub clients.

I could also see a use-case for adding highlight and annotation kinds to the Post Kinds plugin for accomplishing some of this. In particular it would be nice to have a quick and easy user interface for creating these types of content (especially via bookmarklet), though again this path also relies on doing individual posts instead of a single post or potentially a collection of posts. A side benefit would be in having individual tags for each highlight or marginal note, which is something Hypothesis provides. Of course let’s not forget the quote post kind already exists, though I’ll have to think through the implications of that versus a slightly different semantic version of the two, at least in the ways I would potentially use them. I’ll note that some blogs (Colin Walker and Eddie Hinkle come to mind) have a front page that display today’s posts (or the n-most recent); perhaps I could leverage this to create a collection post of highlights and marginalia (keyed off of the original URL) to make collection posts that fit into my various streams of content. I’m also aware of a series plugin that David Shanske is using which aggregates content like this, though I’m not quite sure this is the right solution for the problem.

Eventually with some additional manual experimentation and though in doing this, I’ll get around to adding some pieces and additional functionality to the site. I’m still also interested in adding in some of the receipt/display functionalities I’ve seen from Kartik Prabhu which are also related to some of this discussion.

Is anyone else contemplating this sort of use case? I’m curious what your thoughts are. What other UI examples exist in the space? How would you like these kinds of reactions to look on your site?

Syndicated copies to:

Group Photo at IndieWebCamp Austin 2017

Friends who attended IndieWebCamp Austin today.
Photo of 14 of the IndieWebCamp Austin attendees
Friends who attended IndieWebCamp Austin today.

👤 Tom Brown (); Aaron Parecki (); David Shanske (); Tantek Çelik (); Marty McGuire (); Manton Reece ()

I wish I could have attended IndieWebCamp Austin in person today, but had a good time attending remotely! Thanks to everyone who made the remote experience so usable.

I’m also posting this in part to take a half-stab at person tagging people using homepage webmentions after the last session on post types in which Tantek mentioned tagging specifically. I can already tell this is something I wouldn’t do often without a much more automated system. #manualuntilithurts indeed!

I’ve also found a bug in Twitter in the process! Apparently I can tag people in photos there except for Tantek, who’s username is so short, it won’t populate their pull-down menu to let me add him.

Syndicated copies to: