It's pretty awesome, and the issue currently with the IndieWeb is that at least for some things, only certain themes work with it. Wordpress is particularly suffering from that at the moment.
— Faeborn Networks (@FaebornNetworks) June 23, 2020
A lot of the changes seem to be related to people who are shifting from one shiny toy or project to another. They all seem to say something like:
Hey Mom! Look at my fancy new static site that builds in 0.001 seconds!
Can you believe what Drupal supports in the IndieWeb now? See ya!
I’ve moved back to good ol’ WordPress. Ahhh…
Micro.blog is awesome and requires such little maintenance. I migrated… while on vacation… in the wilderness… from my cell phone!!!
Wheee!
They’re often redirecting all their old URLs to the new site, but the one URL they commonly neglect is to create a redirect for their primary RSS, Atom, JSON or other feeds to their new feed structure. This means that the feed goes dead, and I (and others) have to notice it, then revive it. For some who simply have h-feed structures on their home page things may continue apace, particularly for the Microsub readers out there, though I haven’t been using those for as long to see as many issues.
Why are you doing all that work and making your followers do the extra manual work to go back and resubscribe?! Over the past four or five years there have been fifty or more people I’ve seen do this dance (some multiple times and even a few every 4 months or so). I totally get why they do it (because why not?!) But there should be a better way of keeping track of our major URLs and redirecting them properly.
From a continuity or even business perspective, this could be an even bigger thing as sites will likely spend a lot of time building an audience and could potentially throw it all away with the flip of a switch. I’ll be the first to admit that most of these people may not have a lot of people following them via RSS or similar means, but still?! It seems like at least once a week there’s some big newspaper, magazine, or corporate site I want to follow and I have to complain about finding their feeds. Why would you want to start all over again?
If a social media framing is easier for some, it’s the equivalent of changing your Twitter handle for your account with a hundred thousand followers to something new with no followers instead of creating a dummy account and swapping the usernames so you can have the new name, but keep all your followers.
There are also a few serial bloggers/writers who will start up a project for 3-6 months and build a following only to shut things down though they’ll keep the domain name. Why not redirect that primary domain to one of their other or newer projects and redirect those feeds as well? You’ve spent the time building an audience, why wouldn’t you want to keep it? Am I missing something fundamental here?
We often say, own your online identity, own your domain, and own your data. Perhaps we need to remember to also “own” our friends, family, followers, our community, or more broadly our audience?
Until then, I’m still flailing away out here. Manually changing your feeds in my reader…
What was designed to reduce harassment could be a perfect recipe for the spread of unchallenged fake news and echo chambers.
Manton mentioned the much-anticipated ability to show replies on your blog posts, so of course I peeked at how it worked and at least for the moment have it running here, too. I do wonder how, or I guess if, this might affect how people reply to things in Timeline, since those replies no longer are restricted to appearing in Timeline? I haven’t decided yet what my decision will be here, because I have moderation questions, but for the time being I’ll leave it active.
They’re inspired by Twitter’s beta app.
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 Zijlstra 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?
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.
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.
Sebastiaan Andeweg (seblog.nl)I’ve attended both IndieWebCamp Düsseldorf and Utrecht last month. At the first one, we had a very good session about the UI side of private posts. The blogpost I wrote about it unfortunately stayed in draft. The summary: I used to denote private posts by adding the word ‘privé’ in bold below the post, next to the timestamp. Since the hackday I now show a sort-of header with a lock icon, and a text telling you that only you can see the post, or you and others, if that’s the case.
A big takeaway from Düsseldorf was that I don’t need to do it all at once. To me, the first step to private posts is letting people login to your site. This can be done with IndieAuth, or by using IndieAuth.com (which will move to IndieLogin.com at some point). The second step is to mark a post as private in your storage, and only serve it to people who are logged in. The third step is to add a list of people who can see the post, and only show it to those people. This is the place where I was at.
Private Posts UI was a session at IndieWebCamp Düsseldorf 2019.
Jacky Alciné (v2.jacky.wtf)I’m working on improving my content processing for my site. The focus is around making more “magic” happen on the fly for me. I should have mentions, auto tagging and emoji to HTML entity conversion ready soon. The one thing that I am sorely missing is the ability to address a group. And the more I think on it, the more I realize that intrinsically this might be something that requires a bit of coordination. My current plan of attack is to define a page that tags a bunch of people (or entities) and use that in a similar fashion to a person-tag. This would require that when a group page receives a reply from someone in that (public) group, they would get Webmentions as well. The page would serve as a pass through. This works for private messages cleanly. However, if you wanted to have a private group, the request to said group would have to be authenticated somehow. That part I haven’t figured out as of yet.
For now, my person tags and what not will be just fine!
Chris Krycho (chriskrycho.com)“The Internet” is far too broad an audience for, well, basically any post I write. My current best solution: “Assumed Audience” headings on posts.
Book publishing is a business and increasingly a technical one, but at its heart it is an art, writes Peter J. Dougherty in this opinion piece. He is the editor-at-large at Princeton University Press,
More meme accounts are going private. Their owners say it’s a new way to gain followers on a crowded platform.
Similar to several other mantras I’ve seen recently by various bloggers. Most of them have essentially said that they write to test out ideas, to stretch their thinking, to try to find additional clarity in what they’re contemplating. This takes a slightly different tack, but is roughly the same thesis.
For quite a while now, I’ve been publishing most of my content to my personal website first and syndicating copies of it to social media silos like Twitter, Instagram, Google+, and Facebook. Within the Indieweb community this process is known as POSSE an acronym for Post on your Own Site, Syndicate Elsewhere.
Anecdotally most in social media have long known that doing this type of workflow causes your content to be treated like a second class citizen, particularly on Facebook which greatly prefers that users post to it manually or using one of its own apps rather than via API. [1][2][3][4] This means that the Facebook algorithm that decides how big an audience a piece of content receives, dings posts which aren’t posted manually within their system. Simply put, if you don’t post it manually within Facebook, not as many people are going to see it.
Generally I don’t care too much about this posting “tax” and happily use a plugin called Social Media Network Auto Poster (aka SNAP) to syndicate my content from my WordPress site to up to half a dozen social silos.
What I have been noticing over the past six or more months is an even more insidious tax being paid for posting to Facebook. I call it “The Facebook Algorithm Mom Problem”.
I write my content on my own personal site. I automatically syndicate it to Facebook. My mom, who seems to be on Facebook 24/7, immediately clicks “like” on the post. The Facebook algorithm immediately thinks that because my mom liked it, it must be a family related piece of content–even if it’s obviously about theoretical math, a subject in which my mom has no interest or knowledge. (My mom has about 180 friends on Facebook; 45 of them overlap with mine and the vast majority of those are close family members).
The algorithm narrows the presentation of the content down to very close family. Then my mom’s sister sees it and clicks “like” moments later. Now Facebook’s algorithm has created a self-fulfilling prophesy and further narrows the audience of my post. As a result, my post gets no further exposure on Facebook other than perhaps five people–the circle of family that overlaps in all three of our social graphs. Naturally, none of these people love me enough to click “like” on random technical things I think are cool. I certainly couldn’t blame them for not liking these arcane topics, but shame on Facebook for torturing them for the exposure when I was originally targeting maybe 10 other colleagues to begin with.
This would all be okay if the actual content was what Facebook was predicting it was, but 99% of the time, it’s not the case. In general I tend to post about math, science, and other random technical subjects. I rarely post about closely personal things which are of great interest to my close family members. These kinds of things are ones which I would relay to them via phone or in person and not post about publicly.
I can post about arcane areas like Lie algebras or statistical thermodynamics, and my mom, because she’s my mom, will like all of it–whether or not she understands what I’m talking about or not. And isn’t this what moms do?! What they’re supposed to do? Of course it is!
mom-autolike (n.)–When a mother automatically clicks “like” on a piece of content posted to social media by one of their children, not because it has any inherent value, but simply because the content came from their child.
She’s my mom, she’s supposed to love me unconditionally this way!
The problem is: Facebook, despite the fact that they know she’s my mom, doesn’t take this fact into account in their algorithm.
What does this mean? It means either I quit posting to Facebook, or I game the system to prevent these mom-autolikes.
I’ve been experimenting. But how?
Facebook allows users to specifically target their audience in a highly granular fashion from the entire public to one’s circle of “friends” all the way down to even one or two specific people. Even better, they’ll let you target pre-defined circles of friends and even exclude specific people. So this is typically what I’ve been doing to end-around my Facebook Algorithm Mom problem. I have my site up set to post to either “Friends except mom” or “Public except mom”. (Sometimes I exclude my aunt just for good measure.) This means that my mom now can’t see my posts when I publish them!
Don’t jump the gun too quickly there Bubbe! I come back at the end of the day after the algorithm has run its course and my post has foreseeably reached all of the audience it’s likely to get. At that point, I change the audience of the post to completely “Public”.
Yup. My mom “likes” it!
I love you mom. Thanks for all your unconditional love and support!!
Even better, I’m happy to report that generally the intended audience which I wanted to see the post actually sees it. Mom just gets to see it a bit later.
Could you fix this algorithm problem please? I’m sure I’m not the only son or daughter to suffer from it.
Have you noticed this problem yourself? I’d love to hear from others who’ve seen a similar effect and love their mothers (or other close loved ones) enough to not cut them out of their Facebook lives.
I suspect that a lot of the value of the IndieWeb philosophy is that it encompasses how many people inherently wish the internet worked. As a result I’ve seen a growing number of people discovering the concept de novo either on their own or by borrowing bits and pieces from their friends and colleagues who are practicing parts of it as well. This harkens back to the early days of the web when bloggers incrementally improved their websites based on what they saw others doing and sharing ideas more directly and immediately with their audiences.
Recently I came across the personal website of journalist Marina Gerner which is one of the few, but growing number, I’ve come across that is unknowingly practicing some of the primary tenets of the IndieWeb movement that I suspect more journalists will eventually come to embrace to better reach and engage with their audiences.
Another brief example I’ll mention having seen recently that almost explicitly rewrote the IndieWeb philosophy verbatim was on the the website redesign launch of PressThink, the blog of Jay Rosen, a journalism professor at NYU. It’s a great read individually as is the majority of what Mr. Rosen writes.
Though I read many of the publications for which Ms. Gerner is writing and might see most of what she’s writing organically, having all of her work in one primary location is a spectacular convenience! I can quickly and easily subscribe to all her work by email or RSS. For a working journalist, this is a boon, because like musicians in the evolving music business a lot of the value that they bring to the table (and to the venues in which they play) is a result of their individual fan bases.
While her personal website probably doesn’t drive even a tiny fraction of exposure for her work as when it appears in The Economist or the Financial Times, for example, it does allow her fans to easily keep up with what she’s writing and thinking about. Ideally in the future, outlets will make links to writer’s bylines direct to the writer’s own website rather than to archive pages within their own publications (or perhaps both if necessary).
Here I’m reminded of the seemingly sad case of Leon Wieseltier, the long time literary editor of The New Republic, who was ousted by its editor-in-chief and publisher Chris Hughes, a former Facebook executive. Wieseltier’s brand was almost all-too-wrapped up in The New Republic, where he had worked for decades, and when he was pushed out (ostensibly for the puerile desire to get more clicks and eyeballs), his output and influence seemingly disappeared overnight. Suddenly there just wasn’t as much of him to read. While he still has some output, as a fan who enjoyed reading his work, the problematic hurdles of finding his new work were the equivalent of using a cheese grater to file down one’s knee cap. I suspect that if he had his own website or even a semblance of a Twitter presence, he could easily have taken a huge portion of his fans and readership built up over decades along with him almost anywhere.
While there are some major brand names in journalism (examples like James Fallows, Walt Mossberg, or Steven Levy spring to mind), who are either so wrapped up in their outlet’s identities or who can leave major outlets and take massive readerships with them, this isn’t the case for the majority of writers in the game. Slowly building one’s own personal journalistic brand isn’t easy, but having a central repository that also doubles as additional distribution can certainly be beneficial. It can also be an even bigger help when one decides to move from one outlet to another, bridge the gap between outlets, or even strike out entirely on one’s own.
From a work/business perspective, Ms. Gerner’s site naturally acts as a portfolio of her work for perspective editors or outlets who may want to see samples of what she’s written.
Sadly, however, she doesn’t seem to be utilizing the WordPress category or tag functions which she could use to help delineate her work by broad categories or tags to help find specific types of her writing. She appears to have a “featured” category/tag for some of her bigger pieces to appear at the top of her front page, but I can see the benefit of having a “portfolio” or similar tag to give to prospective outlets to encourage them to read her “best of” work. This would also be helpful to new readers and future fans of her work.
Categories/tags could also be beneficial to readers who may want to follow only her book reviews and not her economics related work, or vice-versa. With a bit of massaging, she could easily have an economics-only RSS feed for those who wanted such a thing. I spent a bit of time in December writing about how I customized my own RSS feeds and helping to make them more discoverable.
Because it might take some a bit of time to delve into and uncover a lot of the spectacular and inherent value in the the massive and growing wiki behind IndieWeb.org, I thought I’d take a minute or two to point out some of the subtle IndieWeb-esque things that Ms. Gerner’s site does well and point out a few places she (or others) could quickly and easily add a lot of additional value.
If you’re looking for all things Marina Gerner on the web, where better to start than http://www.marinagerner.com?
Technically, it looks like her site is hosted on WordPress.com, so they own, backup, and maintain it for her, but there is a very robust export path, so she can easily export it, back it up, or move it if she chooses.
I’m not sure if she’s posting on her site first using the concept of Post on your Own Site, Syndicate Elsewhere (POSSE), but even if she’s posting it secondarily (known as PESOS), she’s still managing to capture it on her site and thereby own a full copy of her output. If any of the publications for which she’s published should go out of business or disappear from the internet, she will still own a copy of her work. (See and compare also the commentary at Anywhere but Medium.)
She’s even got a syndication link (or attribution) at the bottom of each article to indicate alternate locations where the content lives on the internet. Since she’s not using Webmentions to back-port the resulting commentary (see below for more), this is highly useful for finding/reading the potential ensuing commentary on her posts or interacting with it in the communities in which it was originally intended.
There are no syndication links to where her content may be living on Twitter, Facebook, LinkedIn, or other social media spaces to give an idea of the conversations that are taking place around her work. In addition to the value that these conversations add to her work, they also give an idea of the breadth of the reach of her work, which could be useful not only to her, but to future outlets/employers.
She’s clearly not using Webmention (now a W3C Recommendation) or services like Brid.gy which would allow her to have the comments and conversation about her articles from other sites or social media silos come back to live with the original articles on her own site. Given the quality of what she’s writing, I’m sure there are some interesting threads of thought stemming from her work which she’s not capturing back on her own site, but certainly could. As it stands, it’s highly unlikely (and perhaps nearly impossible) that I would go trolling around the thousands or hundreds of thousands of links to try to uncover even a fraction of it myself, but it wouldn’t take much for her to be able to capture all that data and make it easy to consume.
Webmention is a simple protocol that allows one website to indicate to another that it has been mentioned elsewhere on the web–it’s akin to Twitter @mentions, but is something that works internet-wide and not just within Twitter. Brid.gy is a service that bootstraps services like Facebook, Twitter, Instagram, Google+, and Flickr via API to make them support webmention until they choose to implement it directly themselves.
Given the schedules of many journalists, they may not always have time to pay attention to the commentary on past articles, but if she were aggregating them back to her own site, she could occasionally check back in on them and interact as necessary or appropriate. Even better she could do this herself without necessarily needing to spend the additional time and energy to go to multiple other social websites to do so. I suspect that a lot of the value that journalists get out of Twitter could be better had by aggregating some of it within their own websites instead.
As an example, the reader will note that I also have syndication links (by means of icons) at the bottom of this post, but I’ve enabled Webmentions and have most of the replies and commentary from these social silos coming back to this original post to aggregate as much of the conversation back to this original post. In the event that any of these social media sites are acquired or go out of business for any reason, all of this commentary will be archived here on the site. As an experiment, if you’d like, click on the Twitter icon at the bottom of this post and reply to that post on Twitter, your reply will be sent to me via webmention through Brid.gy and I can choose to display it as a comment under this post.
Naturally if she does interact with her pieces via other social channels (Twitter, for example), she could post those replies on her own site and automatically syndicate them to Twitter. This would also allow her to own all of that subsidiary content and conversation as well.
Once she owns all of her own writing and subsidiary data, her platform of choice (WordPress along with many others) also provides her with some good internal search tools (for both public-facing and private posts), so that her online hub becomes an online commonplace book of sorts for not only searching her past work, but potentially for creating future work. Naturally this search also extends to the broader web as her online presence gives her some reasonable search engine optimization for making it more discoverable to future fans/followers.
Naturally the IndieWeb encompasses far more than what I’ve written above, but for journalists, some of these highlighted pieces are likely the most immediately valuable.
I’ll refer those interested in learning more to browse the wiki available at IndieWeb or join the incredibly helpful community of developers who are almost always in the online chatroom which is accessible via multiple methods (online chat, Slack, IRC, etc.) Major portions of the IndieWeb have become easily attainable to the average person, particularly on ubiquitous platforms like WordPress which have simple configurable plugins to add a lot of this simple functionality quickly and easily.
While I was writing this piece, I heard Mathew Ingram, who currently writes for Fortune, say on This Week in Google that he’s been posting his work to his own website for several years and “syndicating” copies to his employers’ sites. This means he’s got a great archive of all of his own work, though I suspect, based on his website, that much of is posted privately, which is also an option, though it doesn’t help me much as a fan.
I’d love to hear thoughts, comments, or questions journalists have about any of the above. Are there other online tools or features journalists would like to see on their own websites for improved workflow?
Please post them below, on your own website along with a permalink back to the original article (see “Ping Me” below), via webmention, or even by responding/replying on/to one of the social media silos listed just below in the syndication links, or natively on the social platform on which you’re currently reading.