Reply to Ryan Boren et al on the WordPress Link Manager, Calypso, and Indie Blogging

Replied to a tweet by Ryan BorenRyan Boren (Twitter)

Oh there’s just so much to say about the start of this thread, and it gives me so much hope for the open web as well as potential growth for WordPress.

Link Manager Update

The Link Manager still seems relatively solid and much of the infrastructure still works well, despite the warnings and lack of updates over the past several years. It would be nice to see it make a comeback and I can personally see many ways it could come back as a means of allowing people to better own their personal social graph as well as dovetail with readers. (This could also be the cornerstone of helping to make WordPress it’s own decentralized social network so that those who want to leave Facebook, Twitter, et al. could more easily do so and maintain their own data and infrastructure.)

If it were being updated, here are a few things that I might suggest as being imminently useful:

  • Update to the latest version of OPML; While the old version still works, there are some new toys that folks like Dave Winer have been iterating on including OPML subscription1,2 as well as some discovery tools.
  • Add in additional microformats support, particularly for display. Things like h-card, u-url, u-photo, etc. could make displaying these more useful for the growing number of microformats parsers. I also suspect that having OPML subscription support could be a major boon to the feed reader resurgence that is happening with the split of the server side/display side split occurring with the improving Microsub spec which now has one server implementation with several more coming and at least three front end implementations. I know of one person building a Microsub server for WordPress already.
  • It’s non-obvious where one’s OPML file lives within the plugin or that one can have or target OPML files by category. Making this more apparent from a UI perspective would be both useful and help adoption.
  • Provide a bookmarklet or browser extension to make it easier to scrape data off of someone’s homepage (or any page for that matter) and put it into the Links Manager data fields. This would allow people to do a one (or two click) solution for quickly and immediately following someone, saving their data into their site, and then via OPML subscription, they’ll automatically be following that feed in their reader of choice.
    • For doing the parsing portion of this, I might recommend the parsing algorithm being used by the Post Kinds Plugin, which parses a web page and searches for microformats, open graph protocol, and one or two other standards to return all or most all of the data that would be needed to fill out the data Links Manager can take. As I recall, this parser was being discussed by Kraft for potential inclusion into the Press This bookmarklet functionality to expand on what it had already provided.
    • From a UI perspective this would allow people to follow friends or others via a WordPress workflow almost as easily as any of the social media silos.
    • Another UI approach for comparison can be found by looking at the SubToMe universal follow button which was developed by Julien Genestoux (also of PubSub/WebSub fame). This version also uses some of the standard feed discovery mechanisms which a bookmarklet would want to be able to do as well.
  • As I’d written, following/subscribing has become more central to the social space, so upgrading the humble blogroll from a widget to a full page would certainly be in order. Having the infrastructure (short link perhaps?) to easily create a WordPress page out of the data would be quite helpful.

As Ryan indicates, the planet-like features that OPML subscriptions provide are immensely valuable in general, but also solves a tough problem that some of the best minds in the educational tech space have found perennially problematic.3

As for the title-less post types that are proliferating by the independent microblogging community (including the recent micro.blog as well as post types in the vein of likes, favorites, reads, replies, etc. which mimic functionality within the broader social space), the so-called (no title) problem can be  somewhat difficult since so many things are built to expect a title. Many feed readers don’t know how to react to them as a result. The Post Kinds Plugin faced a similar issue and recently pushed an update so that within the admin UI at /wp-admin/edit.php the title field would still indicate (no title) but it would also include a 28 character synopsis from the_body or the_excerpt to provide at least some indication of what the post was about. This also seems to be a potential issue in other areas of WordPress including widgets like “Recent Posts” which want to display a title where none exists. As the aside post format can attest, not all themes deal with this well, though there are other alternate methods for displaying some useful data.

 

References

1.
OPML subscriptions. Inoreader blog. https://blog.inoreader.com/2014/05/opml-subscriptions.html. Published May 26, 2014. Accessed July 18, 2018.
2.
RSS Reader InoReader to Support Dynamic OPML Subscriptions. CleverClogs. http://cleverclogs.org/category/opml-subscriptions. Published May 26, 2014. Accessed July 18, 2018.
3.
Groom J. Will Work for Feed Syndication Framework. bavatuesdays. https://bavatuesdays.com/ds106-will-work-for-feed-syndication-framework/. Published August 5, 2013. Accessed July 18, 2018.
Syndicated copies to:

Reply to Tony Zijlstra on Mapping the IndieWeb

Replied to Mapping the IndieWeb a Webmention at a Time by Ton ZijlstraTon Zijlstra (Interdependent Thoughts)

When I link to another blog or site that has enabled webmention, my server log should record that it received a 20* response when trying to reach a webmention end point.

Assuming this is indeed in my server log, then it should be possible to have a script that pulls the successful webmentions from the server log. From that a growing list of IndieWeb sites can grow. Especially if you’d share that list, and others do too, so you can compare and detect new additions to the list. An incremental way of mapping the IndieWeb. Might even become a new, indie Technorati of sorts. At the very least it’s a discovery vehicle to find others interested in the distributed web and outside the silos and media sites.

Or does something like that already exist?

I like this idea…

Somewhat in the same vein, Colin Walker has built a Webmention Directory on his site that lists all the people (selectively) who have mentioned him in the past. It’s not too different from the purpose of a blogroll.

Similarly Ryan Barrett has built the IndieMap which has a much larger data sample behind it. He unveiled it almost a year ago at IndieWeb Summit 2017.

Maybe we could get the old Technorati alumni in IndieWeb to build something out of this?

Reply to UnixSysAdmin about integrating with Twitter

Replied to a tweet by Unix Sys AdminUnix Sys Admin (Twitter)

Articles 1, 5, and 6 in this highlighted series for Twitter will get you most of the functionality (and then some). However once you’ve enabled some of these related plugins, you can also do so much more than just use your site to interact with Twitter.

Syndicated copies to:
Replied to a tweet by ds106 Daily Createds106 Daily Create (Twitter)

I’ve built my own digital (non-)Facebook Wall so that people can write on it. #tdc2380
https://boffosocko.com/mentions/#If%20you%20like,%20you%20can%20also%20think%20of%20this%20as%20my%20personal%20(non-)Facebook%20Wall.

Syndicated copies to:

Reply to This Indispensable Digital Research Tool, We can Say, Without Lying, Saves Time

Replied to This Indispensable Digital Research Tool, We can Say, Without Lying, Saves Time by Alan Levine (@cogdog) (Extend Activity Bank)

People will claim they can replace RSS Readers with social media streams like twitter. While we do get many key resources and news stories via social media, let’s dispute that claim:

  • Clutter, noise, distraction. What you get is interspersed with many things that are outside your interests, rants, yelling, silly gifs. That’s a lot of filtering.
  • You Miss It, You Lose it. Social media is focused at the head of the stream. While you sleep or actually do something productive away from social media, it all flows away. Yes, maybe your network can signal with repeating important things, but its spotty.
  • Duplication You have no means to quickly know what you have already looked at, and you see may the same story multiple times.
  • You Are Subject to Algorithms Especially on facebook, what you see is determined by the mysteries of an algorithm. Sure you choose sources by followers, but the means by which information is presented is determined by some outside automated entity.

This activity brings you an exception to the technology as time-saving lie; it’s old tool that many people have abandoned. I will wade carefully through the acronym jargon jungle, but we are talking about using an RSS Feed Reader to monitor the most recent news, blog posts, data from sources you choose to follow, not ones dished out by some company’s algorithm.

RSS is incredibly valuable as is OPML.

I had used Feedly for several years, but made the switch to Inoreader last year, in part because it has one additional useful feature that Feedly doesn’t: OPML subscription. While it’s nice to be able to import and export OPML files, needing to remember to update them can be an unnecessary step, particularly if 20+ people need to do the update to capture all the new RSS feeds added. (As an example, say one or two students join a class late and everyone has already got the original OPML export and now needs to update to add a few more feeds to keep track of classroom activity.)  OPML subscription improves this by allowing the subscription to an OPML link with multiple feeds in it. If the original OPML file updates with new feeds, then the reader automatically updates them and pushes them out to everyone subscribed to that OPML file!

Think of an OPML subscription as an updating subscription to a bundle of RSS feeds which all also provide their own individual updates. Instead of subscribing to a bunch of individual feeds, you can subscribe to whole bundles of feeds.

For those looking for some sample OPML links to subscribe to, try some of mine which are listed at the bottom of the linked page. For some ideas about building your own data stores with OPML links for WordPress, try my Following Page solution. WordPress’s old Link Manager described on that page will provide the ability to store the data and provide the OPML links, the rest of the page discusses publishing it on one’s site so that it’s publicly available if you wish. URL schemes for sub-categories are discussed separately.

Syndicated copies to:

Reply to Photo Kind not Displaying Information from Response Properties Box

Replied to Photo Kind not Displaying Information from Response Properties Box · Issue #184 · dshanske/indieweb-post-kinds (GitHub)
I am adding in information associated with author and source, however this is not being displayed when published.

@mrkrndvs This is because the photo template doesn’t call these particular details even though they may be provided. I could see an occasional use for including them, particularly to give credit to a photo that was taken by someone else, while in practice most may not use this because they’re posting their own photos.

In the meanwhile, it may not be too tough to cut/paste bits of appropriate code from other templates to get these to display the way you want them when they exist. You can create a custom photo template named kind-photo.php and put it in a folder entitled kind_views in either your theme or (preferably) in your child theme so it isn’t overwritten on plugin update.

I do still wish there were a master template in the set (heavily commented and unused) that used every variation of data that could be displayed (or perhaps even calculated for display) so that non-programmers could attempt to more easily cut/paste templates to get them to do what they wanted.

Syndicated copies to:

A reply to Kathleen Fitzpatrick’s Why Not Blog?

Replied to Why Not Blog? by Kathleen FitzpatrickKathleen Fitzpatrick (Kathleen Fitzpatrick)

My friend Alan Jacobs, a key inspiration in my return (such as it is, so far) to blogging and RSS and a generally pre-Twitter/Facebook outlook on the scholarly internet, is pondering the relationship between blogging and other forms of academic writing in thinking about his next project. Perhaps needless to say, this is something I’m considering as well, and I’m right there with him in most regards.

But there are a few spots where I’m not, entirely, and I’m not sure whether it’s a different perspective or a different set of experiences, or perhaps the latter having led to the former.

I really like where you’re coming from on so many fronts here (and on your site in general). Thanks for such a great post on a Friday afternoon. A lot of what you’re saying echos the ideas of many old school bloggers who use their blogs as “thought spaces“. They write, take comments, iterate, hone, and eventually come up with stronger thoughts and theses. Because of the place in which they’re writing, the ideas slowly percolate and grow over a continuum of time rather than spring full-formed seemingly from the head of Zeus the way many books would typically appear to the untrained eye. I’ve not quite seen a finely coalesced version of this idea though I’ve seen many dance around it obliquely. The most common name I’ve seen is that of a “thought space” or sometimes the phrase “thinking out loud”, which I notice you’ve done at least once. In some sense, due to its public nature, it seems like an ever-evolving conversation in a public commons. Your broader idea and blogging experience really make a natural progression for using a website to slowly brew a book.

My favorite incarnation of the idea is that blogs or personal websites are a digital and public shared commonplace book. Commonplaces go back to the 15th century and even certainly earlier, but I like to think of websites as very tech-forward versions of the commonplaces kept by our forebears.

I’ve seen a few educators like Aaron Davis and Ian O’Byrne take to the concept of a commonplace, though both have primary websites for writing and broader synthesis and secondary sites for collecting and annotating the web. I tend to aggregate everything (though not always published publicly) on my primary site after having spent some time trying not to inundate email subscribers as you’ve done.

There’s also a growing movement, primarily in higher education, known as A Domain of One’s Own or in shortened versions as either “Domains” or even #DoOO which is a digital take on the Virgina Woolf quote “Give her a room of her own and five hundred a year, let her speak her mind and leave out half that she now puts in, and she will write a better book one of these days.”

There are a growing number of educators, researchers, and technologists reshaping how the web is used which makes keeping an online commonplace much easier. In particular, we’re all chasing a lot of what you’re after as well:

Part of what I’m after is consolidating my presence online as much as possible, especially onto platforms that I can control.

To me, this sounds like one of the major pillars of the IndieWeb movement which is taking control of the web back from corporate social media giants like Facebook, Twitter, Instagram, et. al. Through odd serendipity, I came across your micro.blog account this morning which led me to your website. A lot of the underpinnings of micro.blog are informed by the IndieWeb movement. In many subtle ways, I might suspect the two had a lot of influence on your particular choice of WordPress theme.

Tonight I’ve also seen your reply to Dan Cohen’s question:

I had previously replied to Dan’s original question, but somehow missed your side thread at the time. I suspect you didn’t see our branch of the conversation either.

Interestingly, your presumption that the replies/notifications stay within their own domains isn’t necessarily fait accompli, at least not any more. There’s a new web specification in the past few years called Webmention that allows notifications and replies to cross website boundaries unlike Twitter @mentions which are permanently stuck within Twitter. Interestingly, because of the way you’ve set up your WordPress website to dovetail with micro.blog you’re almost 90 percent of the way to supporting it easily. If you add and slightly configure the Webmention and Semantic Linkbacks plugins, the asides and other content you’re syndicating into micro.blog will automatically collect the related conversation around them back to your own posts thus allowing you to have a copy of your content on your own website as well as the surrounding conversation, which is no longer as diffuse as you imagined it needed to be. Here’s an example from earlier this evening where I posted to my site and your response (and another) on micro.blog came back to me. (Sadly there’s a Gravatar glitch preventing the avatars from displaying properly, but hopefully I’ll solve that shortly.)

This same sort of thing can be done with Twitter including native threading and @mentions, if done properly, by leveraging the free Brid.gy service to force Twitter to send your site webmentions on your behalf. (Of course this means you might need to syndicate your content to Twitter in a slightly different manner than having micro.blog do on your behalf, but there are multiple ways of doing this.)

I also notice that you’ve taken to posting copies of your tweeted versions at the top of your comments sections. There’s a related IndieWeb plugin called Syndication Links that is made specifically to keep a running list of the places to which you’ve syndicated your content. This plugin may solve a specific need for you in addition to the fact that it dovetails well with Brid.gy to make sure your posts get the appropriate comments back via webmention.

I’m happy to help walk you through setting up some of the additional IndieWeb tech for your WordPress website if you’re interested. I suspect that having the ability to use your website as a true online hub in addition to doing cross website conversations is what you’ve been dreaming about, possibly without knowing it. Pretty soon you’ll be aggregating and owning all of your digital breadcrumbs to compile at a later date into posts and eventually articles, monographs, and books.

Perhaps more importantly, there’s a growing group of us in the education/research fields that are continually experimenting and building new functionalities for online (and specifically academic) communication. I and a plethora of others would welcome you to join us on the wiki, in chat, or even at upcoming online or in-person events.

In any case, thanks for sharing your work and your thoughts with the world. I wish more academics were doing what you are doing online–we’d all be so much richer for it. I know this has been long and is a potential rabbithole you may disappear into, so thank you for the generosity of your attention.

Syndicated copies to:

Reply to Brad Enslen about Blogrolls in WordPress

Replied to No Good WordPress Blogroll Plugins by Brad EnslenBrad Enslen (Brad Enslen)

Feh. Apparently there are no good blogroll plugins for WordPress.   I did look extensively through the WP plugins directory but didn’t find anything interesting. Most plugins were way out of date for my version of WP.

Might be an opportunity there for the Indieweb movement to aid discovery.

Apologies Brad. I just saw your follow up post and had meant to reply to your earlier one when I saw it last week, I just didn’t have the time to write a quick response. I had hoped you might have found something even better than what I’ve put together previously or perhaps started building a newer and shinier edifice.

There is actually an excellent and solid “plugin” for creating a blogroll, but it’s actually been hiding in WordPress core for ages: the original Link Manager. Use of it declined so much it was programatically “removed”, but all the code is still in core, it still works wonderfully, and it only requires a single line of code (or the simplest plugin ever written) to re-enable it.

It was very solid and didn’t need much iteration, so it should work fine with current versions of WordPress–it certainly does on mine.

I’ve written up a bunch of details on how and what I did (as well as why), so hopefully it’ll give you a solid start including some custom code snippets and reasonably explicit directions to make some small improvements for those that may be a bit code-averse. Hint: I changed it from being a sidebar widget to making it a full page. Let us know if you need help making some of the small code related changes to get yourself sorted.

Even if you just want a plug and play plugin, there are details for that in the post as well, you’ll just be stuck with putting the blogroll into a traditional sidebar position. (With conditional statements in the sidebar widget, you  could restrict the blogroll widget to only displaying on a “Following” page, for example.)

I do think there is still a more IndieWeb way of doing this, potentially by making follow posts with mark up that could be parsed by microsub readers perhaps? Certainly dovetailing something with microsub seems to be a laudable goal. I would like to eventually dive into the Link Manager code and add some additional microformats as well as update the OPML to v2, but there’s enough back compatibility that the older version is fine for most use cases I’ve run across. I know David Shanske has some ideas about some changes he’d like to see in the future as well. You could always also go super low tech the way Greg did and have a blogroll post that you update over time, though perhaps a page is a better way to go? Updating things to be more automated is certainly a reasonable goal though.

Give it a spin and see what you think. Here’s my Following page (aka blogroll) with details at the very bottom for subcategories of OPML subscription. I’ll try to update the IndieWeb blogroll page with some of these details to make them more imminently findable as well.

Reply to Flogging the Dead Horse of RSS by Dean Shareski

Replied to Flogging the Dead Horse of RSS by Dean ShareskiDean Shareski (Ideas and Thoughts)
And I think it’s true. I don’t use RSS the way I did in 2004. That said, I remember reading that blogging was dead ten years ago. And while it’s maybe not trendy, many educators have seen its value and maintained a presence. Apparently, RSS has some valid uses as well but like most everyone, I tend to use social as a place to find new and emerging ideas. But I also think using Twitter and Facebook to haphazardly find content lacks intention and depth. I also value reading a person’s blog over time to understand better their voice and context. So I’m asking for some advice on how to update my module on finding research. What replaces RSS feeds? What works for you that goes beyond “someone on Twitter/Facebook shared….” to something that is more focused and intentional?

Dean, I can completely appreciate where you’re coming from. I too am still addicted to RSS (as well as a plethora of other feed types including Atom, JSON, and h-feeds). I didn’t come across your article by feed however, but instead by Aaron Davis’ response to your post which he posted on his own website and then pinged my site with his repsonse using a web specification called Webmention. We’re both members of a growing group of researchers, educators, and others who are using our own websites to act as our social media presences and using new technologies like Webmention to send notifications from website to website to carry on conversations.

While many of us are also relying on RSS, there are a variety of new emerging technologies that are making consuming and replying to content online easier while also allowing people to own all of their associated data. In addition to my article about The Feed Reader Revolution which Aaron mentioned in his reply, Aaron Pareck has recently written about Building an IndieWeb Reader. I suspect that some of these ideas encapsulate a lot of what you’d like to see on the web.

Most of us are doing this work and experimentation under the banner known as the IndieWeb. Since you know some of the web’s prior history, you might appreciate this table that will give you some idea of what the group has been working on. In particular I suspect you may appreciate some of the resources we’re compiling for IndieWeb for Education. If it’s something you find interest in, I hope you might join in our experimentations. You can find many of us in the group’s online chat.

I would have replied in your comments section, but unfortunately through a variety of quirks Disqus marks everything I publish to it immediately as spam. Thus my commentary is invariably lost. Instead, I’m posting it to a location I do have stricter control over–my own website. I’ll send you a tweet to provide you the notification of the post. I will cross-post my reply to Disqus if you want to dig into your spam folder to unspam it for display. In the meanwhile, I’m following you and subscribing to your RSS feed.

Syndicated copies to:

Reply to Tom Critchlow on feeds

Replied to a post by Tom CritchlowTom Critchlow (tomcritchlow.com)
This is a list of the feeds I'm reading. The page auto-updates every 10 minutes or so. Why? Because we need to resist the hyperfeeds and build our own small feeds in the open

I’m curious how you’re generating your particular feeds. For over a year now I’ve been using a simple bookmarklet system to post what I’m reading, listening to, and watching to my own website and providing it as various feeds (RSS, JSON, and a microformats-based hfeed/h-feed) for others as well as syndicating some of these to other sources. (For the RSS feeds just add /feed/ to the end of the links above. You can also chain them like so http://boffosocko.com/kind/read,listen,watch/ to get multiple feeds at once.)

I wish others were providing this type of data outside of the big silos as well, but it obviously needs to be much simpler.

Syndicated copies to:

Reply to Ian O’Bryne on annotations

Replied to a tweet by William Ian O'ByrneWilliam Ian O'Byrne (Twitter)

Ian, thanks for putting together all of these examples. I think my preference is for option three which provides the most context and seems easiest to read and understand. I like the way you’ve incorporated the blue arrow, which makes semantic sense as well.

I’m sure I’ve seen other versions, but Jon Udell has at least one example of some annotations on his own website like yours too.

When it comes to the “conversation” side of what you’re looking for, I think the biggest piece you’re really missing and which some on the Hypothes.is side (except perhaps for Nate who may have a stronger grasp of their value after the recent IndiewWeb Summit) are apt to miss is that Hypothes.is doesn’t support sending webmentions. Presently you’re putting your data out there in a one-sided manner and Hypothes.is isn’t pushing the other side or any of the follow up back to you. As a result it’s operating as a social silo the same way that sites like Facebook and Twitter do. Based on their GitHub repository, I know that they’ve considered webmentions in the past, but apparently it got put on a back burner and hasn’t been revisited.

Ideally they’d want to have webmentions work in two places. It would be great if they could send webmentions of annotations/highlights to the original page itself, so that the site owner is aware that their content is being marked up or used in this manner. This also means that Hypothes.is could be used as a full-blown and simple commenting system as well so that those who aren’t using their own sites to write replies could use Hypothes.is as an alternative. The second thing it might want to do is to send webmentions, particularly for replies, to the original page as well as to any URLs that are mentioned in the comment thread which appears on Hypothes.is. This would mean that you’d want to add the permalink to your post back to the copy you put on Hypothes.is so that you and your website stay in the loop on the entirety of the conversation. In many senses, this is just mirroring what is going on in threaded Twitter conversations that get mirrored back to your WordPress website. [I’ll note that I think I’ve got the last of the moving pieces for this Twitter/WordPress workflow properly linked up in the past week.] Since Twitter doesn’t support webmentions itself, Brid.gy is handling that part for you, but in Hypothes.is’ case you don’t have any of the details coming back for allowing you to display the discussion on your site except by doing so manually. Doing it manually for extended conversations is going to become painful over time.

From an IndieWeb perspective, you’re primarily implementing a PESOS workflow in which you post first on Hypothes.is and then send a copy of it to your own website. Naturally it would be better if you were posting all the details on your own website and using the Hypothes.is API to syndicate your copy there for additional public conversation outside of the readership of your website. Unfortunately building the infrastructure to do this is obviously quite daunting. Since they’ve got an API, you might be able to bootstrap something webmention-like onto it, but for your purposes it would obviously be easier if they had direct webmention support.

It would also be wonderful if Hypothes.is supported the micropub specification as well. Then you could ideally log into the system as your website and any annotations you made could be automatically be published to your website for later storage, display, or other use. In some sense, this is what I’m anticipating by making  explicit standalone annotation and highlight post kinds on my website. In practice, however, like you, I’d prefer to have a read, like, or bookmark-type of post that aggregates all of my highlights, annotations, and marginalia of a particular piece for easier future use as well as the additional context this provides. I suspect that if I had the additional tag within the Hypothesis Aggregator plugin for WordPress that would let me specify the particular URL of an individual article, I would have most of the front side PESOS functionality we’re all looking for. The rest will require either webmention or a lot more work.

I may have mentioned it before, but in case you hadn’t found it I’ve got a handful of posts on annotations, many of which include some Hypothes.is functionality.

Not itemized in that list (yet?) are some experiments I’d done with the Rory Rosenzweig Center’s PressForward plugin for WordPress. It allowed me to use a simple browser bookmarklet to save a webpage’s content to my personal website with a rel=”canonical” tag for the page pointing at the original page. (Here’s a good example.) Because of the way the canonical set up works within Hypothes.is, I noticed that annotations I (and others) made on the original were also mirrored and available on my website as well. In my case, because PressForward was copying the entirety of the article for me, I used the <mark> HTML tag to make the highlights on my page, but with Hypothes.is enabled, it also shows the other public annotations as well. (Use of the title attribute adds some additional functionality when the mark tagged text is hovered over in most browsers.)

In another example, I annotated a copy of one of Audrey Watters’ articles (after she’d disabled the ability for Hypothesis to work on her site, but before she changed the Creative Commons licensing on her website). But here I added my annotations essentially as pull-quotes off to the side and syndicated copies to Hypothes.is by annotating the copy on my website. If you visit Audrey’s original, you’ll see that you cannot enable Hypothesis on it, but if you’re using the Chrome extension it will correctly indicate that there are five annotations on the page (from my alternate copy which indicates hers is the rel=”canonical”).

In any case, thanks again for your examples and documenting your explorations. I suspect as time goes by we’ll find a more IndieWeb-centric method for doing exactly what you’ve got in mind in an even easier fashion. Often doing things manually for a while will help you better define what you want and that will also make automating it later a lot easier.

 

 

Syndicated copies to:

Reply to a post by Ton Zijlstra

Replied to a post by Ton ZijlstraTon Zijlstra (Interdependent Thoughts)
Hey Brad, discovery is why I started publishing the feeds I read as opml for others to explore, and some I read do so too. In 2005 I used to have photos of blog authors I read. Do you publish your feed list somewhere? Tom Critchlow also shows all the content of the feeds he follows on his site. Works well as a discovery mechanism too I found. Maybe I’ll start doing that as well from my TinyTinyRSS instance I installed earlier this week.

Yes, discovery can be an issue, but if one is providing various feeds (RSS, Atom, JSON, or h-feed) of various post types, then it becomes easier to slice and dice the content coming out of particular websites. I’ve got my website set up so that nearly every post format, post kind, category, and tag has its own feed. Ideally, you should be able to extract almost anything you’d want from my site via a custom feed if necessary.

As an example if you want to follow what I’m reading, there’s a feed for that. Or you can listen to the things I’m listening to by subscribing to my fauxcast.

Separately, I maintain a following page which, similar to a blogroll, is a list of sites I’m following along with OPML of the full list or subcategories. Thus if you want to subscribe to the IndieWeb OPML list, it’s there for you. (Even more fun if you’re using functionality like OPML subscriptions as they’re done in Inoreader, so that when I update my list, yours automatically does too.)

If you’re interested in recreating portions of some of this I’ve tried to document a lot of it (for WordPress at least) at https://boffosocko.com/research/indieweb/.

Syndicated copies to:

Reply to Jaredewy

Replied to a tweet by Jared EwyJared Ewy (Twitter)

@Jaredewy With your domain name, I think that you automatically win the #IndieWeb.

Syndicated copies to:

Reply to I attended IndieWeb Summit 2018 | Fogknife

Replied to I attended IndieWeb Summit 2018 by Jason McIntosh (Fogknife)
Notes and thoughts from the eighth annual IndieWeb conference, held in Portland, Oregon.

My heart forever broken by social-media silos, I’m not really interested in using Micro.blog as yet another “Okay, I’m over here now” social network. I get the impression that it has potential for much deeper use than that, if I can only get my head around it.

Micro.blog can be many things to many people which can be confusing, particularly when you’re a very tech savvy person and can see all the options at once. I’d recommend looking at it like a custom feed reader for a community of people you’d like to follow and interact with. Spend some time in the reader and just interact with those you’re following and they’ll do likewise in return.

It’s purposely missing some of the dopamine triggers other social silos have, so you may need to retrain your brain to use it appropriately, but I think it’s worthwhile if you do.


I really need to hash out my domain situation! IndieWeb encourages its memership to claim a single domain and use it as their personal stamp for everything they do on the internet. I, though, have two domains: my long-held personal catch-all domain of jmac.org, and fogknife.com, which I use exclusively for blogging. My use of both predates my involvement with IndieWeb.

Don’t fret too much over having multiple websites. As you continue on the answer to what you want to do with them will eventually emerge more organically than if you force it to. For some thoughts and inspiration, check out https://indieweb.org/multi-site_indieweb.

Syndicated copies to: