This is an experiment, an alternative way to represent blog posts, as a graph. Click this if you want to get back to the plain list.
The idea is that if you encounter a blog, it's often unclear how to start reading it: typically it's an overwhelming linear list of posts, ordered by date. (thanks Jonathan for bringing my attention to it!)
Representing as a graph allows to relax this linear structure by introducing a partial order (shown by edges). You can start reading from a title that seems most interesting to you, and keep exploring the related posts.
- clicking on a post title brings you to the post
- clicking on a tag will bring you to the description of the tag
- clicking on a date will highlight all connections to the corresponding post, to make the navigation easier
- clusters correspond to 'themes' (although it's pretty fuzzy)
If you have any ideas on improving this page, or notice any problems, please let me know! You can find the source here.
This is the sort of thing that Maggie Appleton and the digital gardens gang would appreciate.
Quite a while I wrote about building a social reader[^ Then called IndieWeb reader, but social reader is the better term.], but these days I have to admit it went nowhere. The biggest problem with it being that I myself don’t really use any reader to consume stuff: I was not used to keeping up wit...
I’m brainstorming ways of describing art museum guards. Art museum security guardArt protectorGallery attendantLaw enforcementMuseum access controlMuseum patrolMuseum protectorObserver of visitorsParcel inspectorPolicy enforcerPreventer of suspicious actionsPreventer of touchingProper propriety maintainerProperty guardProtection services officerSecuritySecurity officerVandalism deterrent My favorite might be the last one, Vandalism deterrent. It’s so true, but also feels so odd to describe that …
A few weeks ago, I made a post about how I got PESOS working for Facebook and Instagram using IFTTT. Now, I’ve gone ahead and done something similar with Pocket and IFTTT!
The code is similar to my linked post. As always, you’ll want to customize everything for your own needs, as well as add your own auth token.
This makes me wonder what web designers and developers would put on their own personal jealousy lists for 2020. What types of features and functionality have you seen this year that you’d love to have on your own website or in your own projects?
I love how Sia has implemented it on her static Eleventy site where she’s kept the UI nice and clean. I particularly like the way she’s done the design and layout and made it more like a call to action.
To take the Twitter actions a half-step further, she could URL wrap the word “liked” with the like action on Twitter.
In general, this reminds me a lot of the idea of webactions, though I don’t think that many have been experimenting with them as of late. Perhaps it’s because of the growth of Microsub-based feed readers that have built-in Micropub support?
— Sia Karamalegos (@TheGreenGreek) November 26, 2019
I’ve spent most of my time in the IndieWeb on backfeed: sending interactions from social networks back to your web site. Bridgy, the service we built, has served that need wel...
Yesterday I was catching up on chat logs and ran across a stub for lurking on the IndieWeb wiki. I cleaned up the formatting a bit and added some additional material. Later Ton Zĳlstra dropped a link to his excellent article from 2004 on the topic: Lurking and Social Networks (though honestly, I first came by the link courtesy of our good friend Jeremy Cherfas who added it to the wiki page).
Lurking is the quiet watching/listening that what many people of the web do in chat rooms in order to begin gauging culture, learning jargon or lingo, and other community norms or unspoken principles before diving in to interact on a more direct level with other participants.
While the word lurking can have a very negative connotation, online it often has a much more positive one, especially in regard to the health and civility of the commons. Rather than rehash what Ton has done an excellent job of doing, I won’t go into the heavy details and history of online lurking, but instead, let’s take a look at where it isn’t in today’s social media landscape.
Since 2004, Twitter and a slew of other social media has popped up on the scene and changed many of our prior behaviors concerning lurking. In particular, Twitter’s interface has made it far easier to either like/favorite a post or retweet it.
In comparison the the preceding era of the blogosphere represented by Tons’ post, Twitter has allowed people to send simple notifications back and forth about each others’ posts indicating a lower bar of interaction than writing a thoughtful and measured comment. Now instead of not knowing about dozens, hundreds, or thousands of lurkers, a (micro)blogger would more quickly know who many more of their readers were because they were liking or resharing their content. Naturally there are still many more potential lurkers who don’t interact with one’s posts this way, but these interactions in some way are like adding fuel to the fire and prompt the writer to continue posting because they’re getting some feedback that indicates they’ve got an audience. Twitter has dramatically lowered the bar for lurkers and made it more socially acceptable for them to make themselves known.
Of course, not all is rosy and happy in Twitterland as a result of this lowering the social bar. Because it’s so easy to follow almost anyone and interact with them, naturally everyone does. This means that while before one may have lurked a blog for weeks or months before posting a response of any sort, people are now regularly replying to complete strangers without an resistance whatsoever. While this can be valuable and helpful in many instances, oftentimes it comes off as rudely as if one butted into the private conversation of strangers at a public gathering. At the farther end of the spectrum, it’s also much easier for trolls to tag and target unsuspecting victims. As a result, we have the dumpster fire that Twitter has become in the past several years for many of its users.
The problem for the continued health of the commons is how can we maintain a bar for online lurking, but still provide some feedback? How can we keep people from shouting and yelling at passer-by from their proverbial front porches or vice-versa? How might we encourage more positive lurking online before directly jumping into a conversation?
Read Posts and Private Posts
For several years now, as a part of the IndieWeb movement, I’ve been more directly controlling my online identity and owning my content by using my own domain name and my own website (boffosocko.com). While I still use Twitter, I’m generally only reading content from it via a feed reader. When I post to or interact with it, I’m always publishing my content on my own website first and syndicating a copy to Twitter for those who don’t own their online identities or content and (sadly) rely on Twitter to do that for them.
Within this setting, since roughly late 2016, I’ve been posting almost all of what I read online or in books, magazines, or newspapers on my own website. These read posts include some context and are often simply composed of the title of the article, the author, the outlet, a summary/synopsis/or first paragraph or two to remind me what the piece was about, and occasionally a comment or two or ten I had on the piece.
In tandem with these posts, I’m also sending webmentions to the websites of those pieces. These (experimental) read webmentions are simply notifications to the originating site that I’ve read their piece. In our prior framing of lurking or Twitter, I’m sending them the simplest notification I can think of to say, “I’m here lurking. I’m reading or looking at your work.”
I’m not saying that I liked it, favorited it, disliked it, bookmarked it, commented on it, or anything else, but simply that I read it, I consumed it, I spent the time to interact with it. But in contrast with Ton’s older method of looking at server logs to see what kind of traffic his posts are getting, he can see exactly who I am and visit my website in return if he chooses. (Ton’s old method of sifting through those logs was certainly not a fun experience and the data was usually relatively anonymous and useless.) These newer read notifications could potentially give him a much richer idea of who his (lurking) audience actually is. Then when someone shows up with a comment or reply, it’s not completely from out of the dark: they’ve previously indicated that they’re at least somewhat aware of the context of a potentially broader conversation on his site.
These read notifications are semantically different from likes, favorites, or even bookmarks on other platforms. In fact many platforms like Twitter, which has moved from “stars” (with the semantic idea of a favorite) to “hearts” (with the semantic idea of a like), have so few indicators of reaction to a post that the actual meaning of them has been desperately blurred. Personally I’ll use Twitter’s like functionality variously to mean: “I’m bookmarking this (or the linked article within it) for reading later”, “I like this post”, “I’ve read this post”, or even “I’m acknowledging receipt of your reply to me”. That’s just too much meaning to pack into a silly little heart icon.
Because I’m using my own website over which I have complete control, I can make it do a better job of unpacking some of this semantic tom-foolery. I’ve written about it a bit in the past if you care to see some of the details: Thoughts on linkblogs, bookmarks, reads, likes, favorites, follows, and related links. See also: the read-posts tag on this site.
If they choose, some website owners display these read post notifications in one or more ways. Some sites like Aaron Parecki’s or Jeremy Keith’s will show my interactions as bookmarks. Others, primarily WordPress-based websites that support Webmention (via plugin), will actually show these interactions in their comment sections under the heading “Read” and display my photo/avatar as an indicator that I’ve interacted with that post. In the case of read posts on which I’ve written one or more comments, the receiving site also has the option of showing my interaction not as a read/bookmark intent, but could also show my comments as a reply to their post. I’ve written a bit about this and its potential for large news outlets before in Webmentions: Enabling Better Communication on the Internet for A List Apart. There are also some older legacy sites that might show my interactions as a trackback or pingback, but these seem few and far between these days, particularly as those systems are major targets for spam and the Webmention protocol has a richer interaction/display model.
A new itch
But as I think about these read posts, lurking, and being more civil on the internet, I have a new itch for some functionality I’d like to add to my website. I very frequently use my website as a digital commonplace book to collect links of things I’ve read, watched, and listened to. I’ll collect quotes, highlights, and even my own marginalia. As I mentioned above, my read posts sometimes have comments, and quite often those comments are really meant just for me and not for the author of the original post. In many cases, when my comments may be too egregious, sensitive, or perhaps even insulting to the original author, I’ll make these posts private so that only I can see them on my site. Of course when they’re private, no notifications are sent to the site at the other end of the line.
Sometimes I would like to be able to send a read notification to the site, but also keep my commentary privately to myself. This allows me to have my notes on the piece and be highly critical without dragging down the original author or piece who I may not know well or the audience of that same piece which I haven’t properly lurked (in the positive community-based sense indicated above) to be as intelligently and sensitively commenting as I would otherwise like. Thus I’d like to build in some functionality so that I can publicly indicate I’ve read a piece (and send a notification), but also so that I can keep the commentary on my read private to either myself or a smaller audience.
I suspect that I can do this in a variety of meta-fields on my website which aren’t shown to the public, but which might be shown to either myself or logged in users. In some sense, this is a subset of functionality which many in the IndieWeb have been exploring recently around the ideas of private posts or by limiting the audience of a post. In my case, I’m actually looking at making a post public, but making smaller sub-portions of it private.
To begin with, I’ll most likely be looking at doing this at a small scale just for myself and my commonplace book, as I can definitely see second and third-order effects and a variety of context collapse issues when portions of posts are private, but others who may be privy to them are commenting on those pieces from the perspective of their public spheres which may not be as private or closed off as mine. i.e.: While I may have something marked as private, privy readers will always have the option of copy/pasting it and dragging it out into the public.
For those interested, I’ll briefly note that Sebastiaan Andeweg just wrote Private posts: the move of the checkins which has some useful and related background to private posts. (Of course I remember exactly when I read it.) I also highly suspect there will be a private posts related session(s) at the upcoming IndieWeb Summit in Portland in June (tickets are still available). I’m interested to see what others come up with on this front.
The Weekly Top 30 (WT30) is the weekly ranking of the thirty most streamed tracks of the week by Michael L. Douglas, MD, MBA. It represents an active hobby by its creator and is subject to augmentation, suspension, or cancelation at any time.
I like the lab book metaphor! That’s probably why a notebook-note analogy appeals to me for my productivity tools. Paul Jacobson on .
I’m honestly a bit surprised that no one has created a bullet journal plugin for WordPress yet. Or maybe someone comes up with a bullet journal stand alone product a bit like Autommatic’s Simple Note? Last week after a talk I attended, someone came up to me who had self-published 400+ copies of a custom made bullet journal that they wanted to sell/market. I’ve also been looking at some bullet journal apps, but my very first thoughts were “Who owns this data? What will they do with it? What happens if the company goes out of business? Is there a useful data export functionality?” For one of the ones I looked at my immediate impression was “This is a really painful and unintuitive UI.”
Naturally my next thought was “how would the IndieWeb build such a thing?”
Perhaps there’s a lot of code to write, though I can imagine that simply creating Archive views of pre-existing data may be a good first start. In fact some good archive views would be particularly helpful if one is using a plugin like David Shanske’s Post Kinds which dramatically extends the idea behind Post Formats. This would make tracking things like eating, drinking, reading, etc. a lot easier to present visually as well as to track/journal. One could easily extend the functionality of Post Kinds to create “to do” items and then have archive views that could be sorted by date, date due, tags/categories for easier daily use. Since it’s all web-based, it’s backed up and available almost everywhere including desktop and mobile.
I know a few people like Jonathan LaCour and Eddie Hinkle have been tinkering around with monthly, weekly, or annual recaps on their websites (see also: https://indieweb.org/monthly_recap). Isn’t this what a lot of bullet journals are doing, but in reverse order? You put in data quickly so you can have an overview to better plan and live in the future? If you’re already using Micropub tools like teacup (for food/drink), OwnYourSwarm (for location), or a variety of others for bookmarking things (which could be added to one’s to-do list), then creating a handful of bullet journal-type views on that data should be fairly easy. I also remember that Beau Lebens had his Keyring project for WordPress that was pulling in a lot of data from various places that could be leveraged in much the same way.
In some sense I’m already using my own WP-based website as a commonplace book (or as Jamie Todd Rubin mentions on Paul’s post a (lab) notebook), so how much nicer/easier would it be if I could (privately) track to do lists as well?
Of course the hard part now is building it all…
Additional notes and ideas
I started thinking about some of this ages ago when I prototyped making “itches” for my own website. And isn’t this just a public-facing to-do list? I don’t immediately see a to-do list entry on the IndieWeb wiki though I know that people have talked about it in the past. There’s also definitely no bullet journal or productivity entries, but that doesn’t mean we couldn’t build them.
There are a lot of preexisting silos on the web that do to-do lists or which have productivity related personal data (Google notes, Evernote, Microsoft OneNote, etc.), so there are definitely many UI examples of good and bad display. For distributed group task management I could easily see things being marked done or undone and webmentions handling notifications for these. I suspect for this to take off on a wide, distributed scale for company-wide project management however, more work would need to exist on the ideas of audience and private or semi-private posts. The smaller personal side is certainly much more easily handled.
As another useful sub-case for study, I’ll note that several within the IndieWeb are able to post issues on their own websites, syndicate to GitHub’s issue queue, and get replies back, and isn’t this just a simple example workflow of a to-do list as well?
Greg McVerry has also mentioned he’s tinkered around in this area before primarily using pre-existing functionality in WithKnown. In his case, he’s been utilizing the related idea of the Pomodoro Technique which is widely known in productivity circles.
I’d be thrilled to hear ideas, thoughts, additional brainstorming, or even prior art examples of this sort of stuff. Feel free to add your thoughts below.
Over the past year, I've been working on the side on a WordPress plugin that implements an idea that has been growing in me over the last couple of years. Decentralized Social Networking. The plugin that does it is called Friends. Starting with the frustration that there are few alternatives for pe...