I miss those early days of blogging, when you didn’t need perfect pictures and a post didn’t require a vigorous social media campaign in order to find some readers.
Those days aren’t over Marisa! We’re still here. Still posting imperfect pictures!
Evergreen content. It’s what many bloggers crave. Posts that keep people coming back. Passive traffic that you don’t have to do anything more to receive.
Back-in-the-day we called this the longtail. Publish enough posts on a given niche and generate tons of traffic over the longterm due to people searching for those topics and your blog becoming a valued resource.
The problem is that it is crap traffic for a personal blogger. It is someone in a moment of need of a piece of information and they are looking for it via your site. It isn’t reflective of your audience size, it isn’t someone that is interested in your opinion or perspective, it is just someone that jammed their fingers in the right order on Google and found your site.
I have a post here on my blog that generates ridiculous amounts of traffic. It skews every number in my analytics. None of those thousands and thousands of people ever come back to my site. Very few even click around. I’m glad people are finding my solution to that particular issue but other than that it provides me no value at all.
That being said, if I was a professional blogger that wanted to make a living at writing I’d be all over it as it is the best traffic for generating money via advertising.
Yet there is still a problem, and that is the apparent insistence on the implementation of specific technologies as implied by the guides and documentation.
Go read his entire post. There are all sorts of “problems” with the IndieWeb and Walker lays some of them out nicely. (Remember, I told you to subscribe to his site.) He mentions that the entire thing can be confusing to non-developers. Well, I am a developer and while the protocols themselves aren’t impossible to grok if you spend some time reading or visiting the IndieWeb IRC chat, I have completely given up trying to support it because it is far too time consuming and nothing ever seems to work for every long.
I’m writing that out of frustration. Sorry. I know it can work. Look at Jeremy Keith’s site. I’m so jealous. He’s put tons of time into making so many of these things work. I want what he has. I simply have chosen not to spend nearly as much time as Jeremy has to get all of this stuff to stick together.
Here is just one example. I have webmention turned on for my site via the “official” WordPress plugin. It doesn’t work. Colin Walker has linked to my site several times. And I to his. His webmentions have yet to show up on my site. Mine have yet to show up on his. And his site isn’t the only site that has linked to me and the only way I’ve found out is via my Jetpack Stats (which I dislike having on but I keep it on for this very purpose). I’m certain that there is a logical reason webmentions aren’t working but I don’t feel like looking under the hood again (and again and again) to figure it out.
I’m not the type of person that needs everything to be easy. I don’t mind some configuration here and there from time-to-time and if something is really worth the effort I’ll even write the code myself. But supporting the IndieWeb (even just a single piece of it like Webmention) has exhausted this developer to the point of giving up.
Part of the problem with people based following models on social networks is that you follow the whole person so see everything they post whether it is relevant to you or not. There is no filtering system.
He goes on to mention that blogrolls that also supply an OPML file make it quick to subscribe via RSS to all of the blogs in the roll. Then, that person can determine whether or not to keep each subscription based on the value they get from them.
I can see that. But, I still go back to my original thought on this. If I subscribe to a bunch of blogs (and I do) and then I link to individual posts that I think are interesting, then I’m acting as a curator for my subscribers. This is why Kottke, Daring Fireball, and Waxy are so popular. They highlight some of the most interesting content, discussions, or resources they’ve found on the web. I do not intend to try to be as focused as Daring Fireball or as prolific as Kottke, but if I find something interesting I enjoy linking to them and giving my thoughts. If I really think something is worth discussing then I will link to it in an individual post.
If you subscribe to my blog and notice I’m routinely linking to a particular source (like Colin Walker) you may consider hopping over to your nearest feed reader and subscribing to his site as well.
Walker also mentions that anecdotal evidence suggests that people using RSS or JSON Feed to subscribe to blogs is on the rise. I’m seeing that too. And I’m very happy about it.
I’m thinking of restarting my blogroll. Remember those!
I’ve been thinking about that too.
I have a list already created of what blogs I would add to it. But I find linking to individual posts with some context provides more value than just a list of URLs.
Me, in 2011:
I believe the blog format is ready for disruption. Perhaps there doesn’t need to be “the next” WordPress, Tumblr, or Blogger for this to happen. Maybe all we really need is a few pioneers to spearhead an effort to change the way blogs are laid-out on the screen.
I still feel that way over six years later.
Colin Walker has a personal blog he calls Social Thoughts. If you read his most recent few weeks of posts you’ll see that he is toying with several subtleties to how his blog looks and works. Of course he has microblog posts, similar to my statuses, but he also has longer form posts. And he’s struggling with how to show them, how to segregate them into feeds (or not), etc.
Like him I too play around with how my blog looks and works. You can see that in my commit history since my WordPress theme is open source.
Looking at his blog’s front page, however, I think he’s onto some interesting ideas. One example is how each day’s content is separated (like blogs used to be). Another being that he has a small indicator for when there are comments on a post. But my favorite thing is that he’s sharing these little experiments out in the open. I’m looking forward to seeing more.
Micro.blog is a social timeline, similar to Twitter, where you can post short snippets of text with links and photos, and converse with others. The biggest difference from most other social networks is where these short posts come from. They come from people’s own websites, where they control the content and can do whatever they like. Micro.blog aggregates its feeds from each member’s personal site and gives people chances to reply and favorite content on the the service.
“people’s own websites” can be their own site powered by whatever they want (WordPress, Squarespace, etc.) But, they can be powered by Micro.blog too as Micro.blog has a blog hosting option built-in.
Scheduling posts to my blog has a few drawbacks but I think the most annoying one is that the topics I write about could be out-of-date pretty quickly or the topic could be covered by someone else.
I have a personal publishing goal to publish an image and blog post per weekday. Sometimes I go for long stretches making that goal and other times I go stretches without. To do so I schedule a bunch of posts in advance.
I wrote about this process in October of 2016 when I wrote a custom WordPress plugin to make it easier (for me) to schedule image posts.
I don’t just schedule image posts but also links, regular posts, and audio bits. For example, I’m writing this post on Tuesday and I’m going to schedule it to be posted on Thursday (the next available slot that I have open in my personal publishing calendar). This particular post contains nothing that needs to be published on a specific day so it doesn’t matter when I decide to publish it. However, earlier today (Tuesday) I wrote a quick post regarding JSON Feed, a topic I’ve been writing about a bit lately, and scheduled it for tomorrow morning. Then, not a few hours later, I noticed the same topic written about by someone else and mainly covered my point. So now I’m faced with allowing that post to publish as is, editing it, or deleting it.
Or, maybe I shouldn’t care at all?
This is one of those posts that I’m glad I wrote because by the time I distilled my thoughts on the matter, edited this post, and re-edited it, I’ve come to a conclusion. Starting June 1 (today) I’m going to continue scheduling posts that do not contain any timely subject matter (like image posts) and set aside some time each morning to write posts for the day. So I’ll be switching my strategy from publishing each day to writing each day. It should be fun.
Manton Reece and Brent Simmons have created a new specification for creating feeds using JSON. They write:
We — Manton Reece and Brent Simmons — have noticed that JSON has become the developers’ choice for APIs, and that developers will often go out of their way to avoid XML. JSON is simpler to read and write, and it’s less prone to bugs.
JSON Feed has been implemented on a few platforms already and it was talked about a lot since its debut. I’m glad someone has created a spec around this so that the developers that would like to use this can now rally behind a unified specification. However, JSON Feed won’t be replacing RSS any time very soon.
RSS is something you could call a “good enough” solution. It is already in place, tons of stuff supports it, and works fine. And while the developers of all of the apps and services that use RSS could update their software to create and parse JSON Feed it is doubtful they will very quickly as the benefits aren’t all that great. The advantage of JSON Feed mostly comes when creating new services not replacing old ones.
I don’t think Manton and Brent believe JSON Feed will replace RSS. I don’t think that is why they created the spec. I believe they feel this is a good alternative for the developers that would like to use it and that they wrote the spec out of a need that they had. Which is good.
I’ve discussed the benefits of replacing RSS with JSON in the past. Me, in June 2015 on one of the benefits of replacing RSS with JSON:
RSS is a fairly bloated specification. It is a bit verbose and the file sizes for even a small blog can get relatively large quickly. JSON is, by its very nature, a bit more succinct. This would result in faster load times, easier caching, etc.
So while there are definite benefits, it is doubtful that RSS is going anywhere for a long time. There have been a few attempts to replace RSS with something that is smaller and easier to parse over the years and they simply didn’t catch on. This weekend Dave Winer (the inventor of RSS) chimed in on JSON Feed and he has a similar reaction to it as I have had; it is great that the specification exists but it will not be replacing RSS for news or blogs any time soon.
I’ve added a JSON feed to this blog because Manton created the WordPress plugin already.
Side note: How did I not see this one coming?
Not exactly sure what Colin Devroe means when he says he’s “just going to publish her on my blog”. I guess that means he’s not interested in people, like me, publishing our comments on our blogs. Of course there’s no compulsion to POSSE to be part of the #indieweb, and if you don’t want to, you shouldn’t. But I hope he’ll still accept webmentions.
On the contrary, I’d much prefer people publish on their blogs in response to my posts rather than on social media. Which is why I do not plan to continue to POSSE. If people find my posts or subscribe to my blog great. If they don’t, that’s ok with me too.
I’ll agree with Jeremy that you don’t need to syndicate content or even backfeed to be a part of the Indieweb. Particularly when you’re already doing the primary tenets: own your domain, own your data, publish on your own site. (Ideally this is what everyone should be doing in conjunction with webmentions and then all the social networks would be superfluous.
Exactly. If I publish here and people link to it in response, I don’t need any social networks.
So, I’m going to support webmention. Not just accepting them and sending them (as I do now), but displaying them also. I need to find a little time to do that since web mentions generally look terrible by default but when I do I’ll report back.
Thanks to Jeremy and Chris for chiming in.
You may have noticed a slight uptick in my publishing. That’s because I am, once again, coming back to my blog as the central place that I publish. Except this time I care far less about any of the content getting to any social networks.
It is simply too exhausting to get working correctly. And once you have everything sort of working right, something about these networks change or a new one arises (like Mastodon). So rather than stifle my publishing based on getting each gear properly greased I’m giving up. Sorry indiewebbers. I’m just going to publish here on my blog.
I don’t care if anyone on Twitter or Facebook or Instagram sees or reads any of this. I just want my blog back.
So does Dave Winer:
Before 2010, on my blog, I could have long and short items. I could use HTML. Link to as many places I wanted, where ever I wanted. There was no character limit, so the short items could grow if they needed to. The same format could accommodate post-length bits with titles that were archived on their own pages. Every item appeared in the feed, regardless of length, regardless of whether it had a title.
I plan on turning off a bunch of the code I have running here on my blog to support these networks too. I’m going old school.
If you like my blog subscribe. If not, that’s OK too.
I love that blogs can scale from the trivial to the important. The microblog post about what you had for breakfast. The half-baked rant about something you’re passionate about. And sometimes, the rare essay that really hits the mark and makes people think.
Publishing most of my “tweets” here first has led to some frivolous posts. But, I wouldn’t have it any other way. Takes the pressure off of me to have every post be significant before hitting publish.
Next Wednesday I’ll be hosting the first Scranton-based Homebrew Website Club at Condron Media‘s headquarters on Penn Avenue. There are other locations HWC will be happening on that day too. If you have your own site and I you care to work on it in anyway at all please do stop by.
Homebrew Website Club is not a typical meetup, like say a WordPress meetup, in that you stop by to learn a particular topic (although I have no doubt you will learn if you attend one). It is more a reoccurring time that is set aside to allow you to work on your personal web site. Perhaps you’ve been meaning to finish up a blog post that has been in draft for weeks, or you need to fix a theme issue, or you want to do something more complex – whatever it is, HWC is your opportunity to do that while sitting next to other people that are trying to do the same.
I’ll be using the this time, each meeting, to fit more Indieweb building blocks into my personal site. I’ve recently added Backfeed, POSSE, Webmention, and others. And I plan on continuing to tweak them to get them just the way I’d prefer. Also, I plan on pushing my code and work back out into the world through this blog, my Github account, and #indieweb on IRC.
So, if this is something you’re into. Drop by.
With my What I saw this week series of posts hitting #29 this week I thought I’d take a second to share how these posts do on my site, how I create them, how I choose what I will link to outside of these posts.
These posts are some of my most popular week-to-week. My active subscriber numbers aren’t that high – I’d say less than 1,000 people subscribe to my site in some way or another – but the traffic to these posts are as high as any other popular post on my site. I believe there are two reasons for this; consistency and because I share them on Facebook. I try to share these posts every single Friday at 10:30am and I think that helps a lot. Facebook is starting to push a lot more traffic to my blog than Twitter. It used to be the other way around. For years. But I honestly believe Twitter is losing ground on this front (more on this at a later date when my thoughts have had more time to simmer).
How do I create them? As I mentioned in a previous post, I keep a note open to throw URLs in during the week. On average I’d say I put 2 to 3 URLs in that note before the week is out. Mainly because I haven’t stored them in some other way. On Thursday or Friday I take the URLs from this note, and also look through my Twitter favorites, my YouTube history (if you’re logged into YouTube on all devices it stores a history of all videos you’ve watched), my Unmark archive, and lastly I comb through Chrome’s browser history (I keep my history for years). This takes me about 25 minutes a week.
Then comes the choice about what to include in these posts and what to link to separately. You’ll probably notice that the bulk of my publishing comes on Fridays and the weekends lately. That is because I’ve gotten out of the habit of scheduling my posts for the week on Sundays. I think I’ll get back to this soon. But also it is because many of my posts are simply links to other things I find interesting and so at the end of each week I do a dump onto my blog.
I choose what to link to separately mainly based on category or thread. My interests are myriad but overall I like to cover specific trends here on my blog such as the indie web, blogging, photography, social networking, hiking, flying my drone, kayaking, etc. If a link falls into one of these categories, or is a continuation of a discussion I started here on my blog, I generally separate those posts out into their own.