Skip to main content

Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, Indieweb, and the entertainment industry including: finance, distribution, representation







@billbennettnz @davewiner I think I mentioned to you that @Chronotope was mulling something over along these lines:

I'm curious if there's a middle ground? The way that @davewiner does his blog with updating hashes throughout the day would be interesting within news distribution, that way the URL changes, but at the same time it doesn't really. Example: (Naturally the ability to update RSS feeds over time would be useful---as he describes in this particular post--, but it would also depend heavily on how users are subscribing to their news.) In his case, the updates are categorized by day/date rather than topic or category which is what an unfolding story would more likely do in a digital news publication.

In some sense, these hashes are related to the IndieWeb concept of fragmentions:, though in their original use case, they're meant to highlight pieces within a whole. This doesn't mean they couldn't be bent sideways a little to serve a more news-specific piece that includes a river of updates as a story unfolds--especially since they're supported by most browsers. It would be much easier to syndicate the updates of the originals out to social media locations like Twitter or Facebook this way too. Readers on Twitter, for example, could see and be directed to the latest, but still have easy access to "the rest of the story" as Paul Harvey would say.

Depending on implementation, news sites could offer a tl;dr toggle button that gives a quick multi-graph synopsis. As I recall USA Today and Digiday used to do something like this on longer pieces:
Here's a version of the functionality via the WayBackMachine that still works:

Imagine how powerful a long running story could be with all of these features? Or even snippets of inter-related stories which could be plugged into larger wholes? Eg: The Trump Administration's handling of North Korea seen in fact snippets over time spanning months while pieces of this could be integrated into a larger Trump Administration mega-story going back to January or even the beginning of his campaign. Someone who hasn't been following along could jump back months or years to catch up relatively quickly, but still have access to more context that is often missing from bigger pieces which need to stand on their own relatively.


@billbennettnz I hope/suspect it will be an on/off option. Changes will also require adoption. It could mean you could fix errors though.


Jeremy, congrats on owning your reading! I'd recently seen your note about using, but I've been on holiday and not had a chance to get back to you.

In general it seems like you've found most of the salient pieces I liked about it. For the record these include:
* I like the idea of "bookmarking" everything I'm reading as I read it. Even for things I don't quite finish, I often will want to know what the thing was or how to easily find it at a later date.
* It has an easy to use desktop bookmarklet that makes the friction of using it negligible. (On mobile I use the ubiquitous sharing icon and use my account's custom email address to email links to my account which is quick enough too.)
* Its RSS feed is useful (as you've discovered), but I've integrated it into my WordPress site using for porting the data I want over. In my case I typically save the post as a draft and don't publicly publish everything that my lesser followed account does. Generally once a day I'll look at drafts to add some notes if necessary, or do some follow up reading/research (especially when I've read something interesting via mobile and didn't have the time), and then publish a subsection of the captured reads as public.

I've filed an issue with the developer to see if he'd include the comment data within into the RSS feed so that it could be included in the passed data, so that when commenting there, the commentary could also be passed across to my site as well.

While I typically prefer to default to POSSE when I can, this PESOS workflow is generally acceptable to me because it required very little effort and I like having the drafts to determine which I should post publicly/privately as well as for a nudge on potential follow up for some of what I've read.

One other small thing I had done was (via plugin) to have any links on my site auto-post to the WayBackMachine on as I read/post them that way there's a back up version of what I'd read so that in the future copies are available even if the site goes down at a future date. I suspect you could do this with a simple POST call, an example of which I think is documented in the wiki.

As a subtle tweak you may wish to take a look at I noticed that you bookmarked something as read a second time having clicked through via a link. This causes to mark the second one as "Jeremy Cherfas is reading this because of Jeremy Cherfas" which means the "because of Jeremy Cherfas" manages to sneak into your RSS feed in the title. I suspect this wouldn't happen often, so you could probably ignore it, but you could throw it into your Regex filter to trim it out when it does happen. (When you click on links, they process to show that you're reading something as a result of someone else having posted it, which could show some interesting network effects though the network is relatively small.)

I know you're always saying that you're not a developer, but you've puzzled out a regex filter, implemented it, and posted it to your site for others to benefit. I would submit that you could now proudly wear the title even if you have no intention to do it professionally. Neither of us may be at the level of people like aaronpk or snarfed, but then, really, who is?

I also love that you've got a Webmention form set up, working, and looking great. Congratulations! If you want a small challenge, perhaps you could massage it to create a Grav plugin so others could easily implement it? If you want less challenge (and obligation for support), perhaps submit what you've got as an issue to the Grav Webemention plugin and see if they'd add it into the bigger plugin where it would also make sense having it. (They may also default to having it use their own webmention implementation instead of the heroku version.) If nothing else, consider linking/documenting it on the wiki page for Grav where others may find it more easily in the future.

Congratulations again Mr. Developer!


@dauwhe On first blush it looks like something superceded by microformats h-cards and other pieces within community for identity.


@susanthesquark This is part of the reason I never really quit and find Extension courses like


I'm curious what, if anything, you all think that the IndieWeb as a community could do or do better to make things easier for Generation 2 users?

Additionally is there something we all (as Gen2 users) could band together to do to make it easier for others like us not to have to "suffer" as we did? Comments back to this are welcome, as is conversation in the channel, or even brainstorming on the wiki (perhaps the generations page:


Sorry to hear that it took so much work, but the end result is pretty cool. I hope it has a useful advertising effect and would be curious to hear the numbers if you track them.


Here's roughly the reason that the "Like" button is being pushed into your syndicated copies:

Ultimately, I decided that very few people were using that like functionality on my site (which is WordPress specific), so I just turned it off in JetPack to "fix" the problem. There are other possible methods to fix it within your theme, but it will ultimately be very hacky based on my past attempts.


John, it was worth writing this just for your response.


@cdevroe @johnjohnston Ideally, it would be best if people were using their own blogs for direct replies. Then *if* they choose to syndicate those responses to, it would be best if were able to parse that reply and see the in-reply-to mf2 class to be able to properly find and thread the conversation on

I tend to treat as a feed reader of sorts, but for those who have their own blogs with webmentions (the case with this post right here), I'll definitely reply to their blog directly, though this can tend to dampen the conversation for those taking part on, but this is the case for the disjointed conversations happening on Facebook, Twitter, etc. Sometimes it's not always easy to keep the conversation on one's own site while simultaneously playing nicely with silos.

While is a great product that supports some interesting pieces, for those with their own sites and webmentions, it's still just another silo. The secret is to treat it the same way one would with Twitter, Facebook, or any other site you'd syndicate out to. Because is a hybrid site sitting between the old world and the new, how you use it and interact will have to change based on whether you're using it for hosting or not and whether you support niceties like Webmentions or not.

For me It's always been easier to post the start of the thread and then go to (or Twitter or Facebook) to continue a discussion with others knowing that I'll get the webmentions back to my site where I'll still manage to own the content. The tougher piece is for others (who also own their sites) to inject their reply via their own site into the original person's blog as well as the siloed conversation at the same time.


@cleverdevil Reminds me of our gardener who went on vacation a month before we put the house up for sale, and didn't manage to come back. Had to rush to get a few gardeners to do a massive clean up and clear back our jungle at the last minute.


@vboykis Wait? A *second* blog I didn't seem to know about?! Are there others I'm missing?


@keithjgrant @SaraSoueidan @snookca @danmall @adactio There are some micropub clients that will do this on mobile


@cleverdevil It's official if you say it is. :) Ought to document it for the history books at least.


@cleverdevil @DreamHost Awesome! Did you get a photo? (or document it at