DITCHWALK

A Road Less Traveled

Topics / Books / Docs

About / Archive / Contact

Copyright © 2002-2020 Mark Barrett 

Home > Archives for Publishing > Ditchwalk.com

Email Subscription Conundrum Update

July 30, 2015 By Mark 2 Comments

Faced recently with the choice between yet more proofreading and advancing my feeble knowledge, I spent the better part of a whole day digging into the Feedburner issues mentioned in the previous post. The good news is that I learned a lot. The bad news is that none of what I learned has solved the problem, or is likely to do so.

As was to be expected, Feedburner is now toying with me by sending emails to at least some of the addresses in its subscription list. I can confirm that because I registered a couple of test-addresses, and a few days later a message got through on one account notifying me of a recent post. Unfortunately, that same message did not arrive at two other accounts, so I now have to figure out if the issue is with Feedburner itself (impossible to determine) or with the site hosting those addresses (possible but not likely given their disinterest).

As for fixing potential issues with Feedburner, in fits and starts I managed to work through all of the steps that I later found helpfully enumerated here. If you’re having Feedburner issues yourself, that’s where I’d start. (None of that troubleshooting did anything for me.)

On the subject of whether I’m using Feedburner for my RSS feed, by chance I stumbled across confirmation (now lost) that the only thing Feedburner does with regard to feeds is give you visibility to stats associated with their use. And as far as I can tell, it even does a miserable job of that. Then again I am terminally naive about how to exploit the data habits of people who come to Ditchwalk, so I’m probably missing something. In any case, Feedburner seems to be non-essential for feeds unless you’re an analytics junkie.

The ENews Extended plugin, which was closely associated with StudioPress/Genesis themes for several years, now seems to be deprecated, moribund and — while still working — non-viable if you want to use a solution derived from Cpanel or your own ISP/mail package. I asked a couple of people if they’d ever even seen that plugin configured to use something like Mailman, and they said they had not.  [ Read more ]

Filed Under: Ditchwalk.com

The Email Subscription Conundrum

July 24, 2015 By Mark 1 Comment

For at least six years I’ve been using Feedburner to send a single email to registered subscribers after each new post is published. A few weeks ago Feedburner stopped working for reasons I cannot ascertain. I’ve tried everything possible to get it to work, but even though all systems appear go the emails are not being sent.

I know this is not a new complaint, and that Google (which owns Feedburner) has allowed the site/service to languish. It is, technologically, adrift, and has been for a long time. I used it because it works, it no longer works, so it’s time to do something else.

One complicating factor is that Feedbuner handles both emails subscriptions and RSS feeds, and I think I’ve been using Feedburner for both. I say ‘I think’ because no matter how much I learn about RSS feeds I’m never quite sure what they are. They seem to be a kind of parallel channel to my published site — like a radio version, or maybe a telex or telegraph. If you don’t want to click on my site you can point your browser or feed-reader to the Ditchwalk feed and get my content that way.

What’s never clear to me is what Feedburner is actually doing to make that feed happen, because I think it’s actually doing nothing. Rather, it takes my feed — which WordPress creates — and then redirects it, or repurposes it, or maybe even reporpoises it, or something. Which means not only that Feedburner isn’t doing anything for me in terms of email subscriptions, it’s doing nothing for me in terms of RSS. Or at least nothing I need to care about if the rest of Feedburner’s functionality is on the fritz.  [ Read more ]

Filed Under: Ditchwalk.com

Graphics and Interactive Storytelling

April 30, 2015 By Mark 3 Comments

In the mid-nineties I became fascinated by the storytelling potential of interactive entertainment. My interest peaked in the early aughts, during what I now think of as the second great wave of interactive storytelling mania. While the potential of interactive storytelling seems obvious to everyone, the mechanisms — the actual techniques — by which interactive stories might be told are complex and at times counterintuitive.

After finding my way into the interactive industry and meeting with some professional success, I was asked in 2000 to write an article for SIGGRAPH’s Computer Graphics magazine about the future of interactive storytelling. While great effort was being put into replicating techniques from passive mediums, including, particularly, film, it seemed to me that such an imitative approach had everything exactly backwards.

Recently, while conducting periodic maintenance on my computer and sprucing up Ditchwalk, I ran across that article, which for some reason I had never gotten around to adding to the Docs page on this site. That omission now stands corrected.

The title of the article is Graphics — the Language of Interactive Storytelling. Coming from someone who primarily made a living with words that may seem odd, but it and the accompanying text goes to the heart of the interactive storytelling problem, and why so little progress has been made. In fact, the only thing that’s changed is that we no longer worry about having enough processing power to do what we want — yet today’s enviably high hardware ceiling is still rarely used to facilitate aspects of interaction that might truly drive emotional involvement.

Fifteen years on, during the fourth great wave of interactive storytelling mania now taking place in the industry, little has changed. Another generation of eager developers is grappling with the same questions, reaching the same inherently limiting conclusions, attempting to once again adapt non-interactive techniques from passive mediums, and confusing the revelation of pre-designed outcomes with choices that determine outcomes.

— Mark Barrett

Filed Under: Ditchwalk.com, Interactive Tagged With: interactive storytelling

Link Rot Postmortem

April 15, 2015 By Mark 3 Comments

Ugh. So here’s what I learned while banishing broken links…

* Broken Link Checker isn’t completely intuitive, but as of this date it’s current and supported. If you have a question you may not get the answer you’re looking for, but you’ll get an answer, and you’ll profit from it.

* Over the past year the BLC plugin reported (via email) in fits and starts for reasons I did not understand. In reading up and poking around, however, I discovered a ‘server load’ setting which seems to act like a throttle. If you set it very low — meaning lower than the reported server load — you effectively idle BLC until the server load drops. Or at least I think that’s what happens. In any case, when I raised the number above the reported load, BLC sprang into action, so if you’re not getting activity when you expect it I would check that setting. (Also, if you’re on shared hosting, consider changing that setting at night when the server load is low. BLC may run much faster.)

* When you’re working on each individual broken link, going slowly and searching for missing pages on the web can be surprisingly fruitful. I fixed quite a few dead links where the missing page’s URL had been altered without a redirect. Once located, copying and pasting the current active link in place of the broken link solved the problem.

* I initially decided to deal with a minimum of twenty-five links each day, but the first day was tough. As it turned out, however, much of the struggle was due to the fact that I had no process or workflow to follow, so what I was really fighting was the learning curve, not the task. On the second day I probably fixed or killed fifty or so links, then the following day I finished off the remaining sixty or so, meaning it took me three days to get through my backlog. (If you’re in the weeds like I was, or worse, just make link-fixing a chore that you come back to again and again until it’s done.)  [ Read more ]

Filed Under: Ditchwalk.com Tagged With: blogs, links

Link Rot

April 12, 2015 By Mark 1 Comment

Whatever my favorite blog post title used to be, it is now a distant second to this one.

So what is link rot? It’s decay that happens to a linked document over time as links become unresponsive. You add links to pages on other sites, some of those pages disappear or are moved, and suddenly your links don’t work any more.

On a case-by-case basis it’s a nuisance. Over time, and over an entire website, it’s a horror. Across an entire discipline, like law, it’s potentially crippling. Speaking of which….

More than a year ago now I found a couple of dead links in an old post, which made me realize I had no way to find such links on a proactive basis. After using a few web-based spiders to search my site and report on dead links, and finding them wanting, I came across a WordPress plugin called — appropriately — Broken Link Checker.

Installing and running BLC was easy, but the results were frightening. At the time I had over 150 reported broken links, although on closer inspection some of those proved to be links that timed out. Still, 150+ bad links was plenty, yet when I earnestly set about trying to solve the problem I realized I didn’t know how.

Yes, I could see that a link pointed to a page that was no longer available, but how to note that in context so the reader would understand? Worse, what if a whole paragraph was written around the presumption of a link?

Just knowing about the problem has allowed me to be a little smarter about writing link text. For example, in the paragraph above, where I mentioned law, the article I linked to is on Gigaom.com, which went belly-up only a few weeks back. At some point that link will probably be reported dead because the content on Gigaom will no longer be available, but that sentence will still be intelligible without it. It won’t be substantiated, but it will still make sense.

Maddeningly, however, as simple as the problem seems — fix dead links — in practice it has repeatedly proved insurmountable. I psych myself up, I dig into BLC, I fix one or two broken links — usually the easiest ones — then flop back, mentally exhausted.

Searching for sage advice on the interweb reveals fraught awareness of the problem, but few good solutions I can put into practice. Or solutions that are overkill. (Oops — that sentence won’t make much sense when that link dies.)

Since I first installed BLC days have turned into weeks, weeks into months, months into a year, and…well, here I am. Still with 150+ dead links reported.

So it’s time to do something about the problem. I don’t know what that’s going to be, and I suspect it’s going to be a fight all the way, but I’ve got a little time now and nothing better to do. And believe me, I tried to find something better to do.

They say the first step in solving a problem is admitting you have a problem. I have a problem. I have link rot.

— Mark Barrett

Filed Under: Ditchwalk.com Tagged With: blogs, links

Site Seeing: Jane Friedman

April 2, 2015 By Mark 2 Comments

First things first. Because nothing is ever easy in life, there are (at least) two Jane Friedman’s in the publishing world. One Jane is the CEO of Open Road. This post concerns the other Jane, who is the CEO of herself, and formidably so.

Back about five or six years ago, when the self-publishing craze blew up and all the hand-wringing inside publishing turned into shrieking and wailing in the streets, one of the people I ran across on the interweb was Jane Friedman, then at Writer’s Digest. While ably fulfilling her contractual duties Jane struck me as someone who didn’t just have a job, but genuinely enjoyed — and more importantly, was interested in — her line of work. When she later departed WD I was glad to see her hang out her own shingle and keep moving with the times, because I thought she had a lot to offer both new and veteran writers who were struggling to understand the rapidly shifting publiscape.

Flash forward half a decade and I just ran across the most recent iteration of Jane’s site, and I think you should stop by yourself. I don’t know Jane personally and I can’t vouch for her in any professional context, but one of the things I’ve learned over the years is that there’s a lot to be said for people who stick with their interests no matter what else might be happening. In a world — and particularly a disingenuous online universe — where everyone is always racing off to the next shiny object or embracing the latest transactional fad (or fraud), I think it’s worth paying attention to people who seem immune to such influences.

Jane’s blog is here, and if you’re interested in publishing, self-publishing, and how authors are transitioning between and navigating the two, you won’t be disappointed. Having been in a cave since 2010 I’m happy to have years of back posts to read through, and I’ve already found one or two that were genuinely informative.

Too, not only does Jane post regularly, but she maintains a presence on her site, which is also quite rare given the usual online advice about branding, social networking and becoming a micro-celebrity. For example, not only do I agree with just about everything she had to say in this recent post — yet another rarity, albeit largely because I’m a crank — but one of the few concerns I did have was mentioned in the comments, to which Jane herself replied. The only point I might add is to make your website mobile-responsive, as Jane’s site already is. Not only are most people using smartphones these days, meaning they’re looking at your content in a very small window, but in a few weeks Google is going to start factoring mobile-responsive web design into its page rankings.

(Don’t have a mobile-responsive site? Don’t panic. Anyone searching for your name or the title of one of your books will still have little or no trouble finding you on the first page of search hits. It’s just something to keep in mind when you’re putting up a site or doing a refresh.)

— Mark Barrett

Filed Under: Ditchwalk.com, Publishing Tagged With: jane friedman, site seeing

The Ditchwalk Indignation Scale

March 19, 2015 By Mark 3 Comments

Following up on the previous post, about how 90% of the internet is righteous indignation and ridicule, I thought it might be useful to provide some context. While ridicule is of course childish in all instances, there are times when righteous indignation is warranted. Unfortunately, those times are few and far between when compared with the perpetual tide of indignation surging across the internet.

Not everything is worthy of true indignation, though it is admittedly easy to get lost in an argument and forget that what you’re talking about is meaningless. So next time you think you may have lost your bearings, or you’re not sure if flaming someone for their opinion about an espresso machine is appropriate, take a deep breath and consult the Ditchwalk Indignation Scale:

Practically speaking, the benefit of the Ditchwalk Indignation Scale is to remind us all that when we’re arguing about a 1 — which is pretty much all we ever argue about — we’re arguing about a 1. In fact, you can even use that point to express your righteous indignation. For example: “I’m sorry, but I have more important things to do with my time than argue about a 1.” At which point the other person may slug, you, allowing you to continue your discussion on a more substantive basis.

— Mark Barrett

Filed Under: Ditchwalk.com, Non Sequiturs Tagged With: scale, social networks

Making the Move to Mobile Web Design

July 16, 2014 By Mark 1 Comment

After taking eight of the previous twelve months off from the haphazard blogging I do here on Ditchwalk, I knew when I picked up the mouse again that I needed to redesign the site to reflect a broader but also more personal focus. Less platform and profession, more craft and art. Less business and commerce, more being and seeing.

What I did not fully comprehend until I took up that task in February was that a sea change had taken place in computing over the previous two years, and that I would need to factor that change into the redesign of Ditchwalk. (I had noticed aspects of the change, but because I can be fairly slow on the uptake I didn’t perceive those dissonant experiences as part of a fundamental metamorphosis in computing.)

In retrospect, the loudest and most prominent signal came from Microsoft with it’s release of Windows 8. Unlike previous versions, Windows 8 came with a default desktop environment that emulated the screen of a mobile device, including touch-sensitive tabs perfect for use on tablet displays — then an exploding technology. As someone who has never owned a smartphone or tablet I reacted with a practiced and oblivious roll of the eyes because Microsoft is always trying to drive computing in directions that favor its various monopolies, often with disastrous results. What I did not realize was that the decision to try to kill off the desktop PC was not a sign of active corporate idiocy, it was a sign of reactive corporate idiocy.

During the two years following the release of Windows 8 Microsoft first denied it had made a mistake, then belatedly began trying to undo the damage it had done to its own brand by once again attempting to force everyone that used its products to adopt another self-serving interface metaphor. Watching this ritual inanity play out further convinced me that Microsoft’s initial decision was just another blind lurch by a company that cannot perceive its own meaning in the marketplace, but that was a mistake on my part.  [ Read more ]

Filed Under: Ditchwalk.com

The Best Blog Post Ever

July 6, 2014 By Mark Leave a Comment

This is the best blog post ever. Now you know.

You now also know how keywords work. And don’t work.

— Mark Barrett

Filed Under: Ditchwalk.com, Non Sequiturs Tagged With: blogs

Five (More) CSS Tips for Beginners

February 19, 2014 By Mark Leave a Comment

Even if you’re an absolute beginner, making changes to an existing CSS style sheet is not complicated. Yes, there are things you need to learn, and computer code is often unforgiving, but as I hope I explained in the previous post the basics are easy to grasp. Fuel your own initiative with a reference site like W3Schools, where you can pick up tips and information as needed, or even try out techniques before implementing them, and the only thing standing between you and success will be the bitter realization that an innocent misstep may lead to hours of hysteria because you don’t know how to protect yourself from your own ignorance. So let’s solve that problem.

Whatever goals you have for learning or even just tinkering with CSS, the first thing you need to do is see those goals in context. Yes, finding the exact right shade of green for your hyperlinks is important, but so is ensuring the stability and functionality of your site. There’s nothing inherently dangerous about making changes or even making mistakes when you’re working with computer code as long as you know how to protect yourself from inevitable errors. That protection begins with making sure you can always get back to the most recent stable build, even after you’ve made (and forgotten about) multiple changes.

1. CTRL-Z IS YOUR FRIEND. CTRL-Y IS YOUR OTHER FRIEND.
If you’ve been using a computer for any length of time you probably know that pressing and holding the Control (Ctrl) key, then simultaneously pressing the Z key will undo the most recent action in many applications. Most word-processing and image-editing software uses this convention, and the same holds true for many of the applications used to edit CSS style sheets.

If you make a change to the CSS in your style sheet, then upload the change and get results you’re not expecting, you can usually press Ctrl-Z to undo your mistake. Since mistakes are quite often unintentional you may not even be sure what you did to cause the problem, so Ctrl-Z can be a real lifesaver. Even better, many applications allow for multiple undos, so you can go back through five, twenty or even fifty edits. (Check the documentation to determine the exact number.) Since some mistakes become apparent only after multiple changes, Ctrl-Z may be the only way to step back through the sequence that triggered the problem.

What many people don’t know is that holding the Control key down and pressing the Y key will often redo an action, meaning between Ctrl-Z and Ctrl-Y it’s possible to go backwards and forwards through your most recent changes. For example, maybe you made a change but forgot what the original value was and suddenly realize it’s important. With Ctrl-Z and Ctrl-Y you can cycle back and read the value, write it down on a piece of paper or copy it to a separate document for reference, then cycle back to where you were. (What you must not do is cycle backwards with Ctrl-Z and make a change unless you’re sure you won’t need to press Ctrl-Y again. Any change you make when you go backwards with Ctrl-Z necessarily starts a new Ctrl-Y sequence in the application’s memory at that point.)  [ Read more ]

Filed Under: Ditchwalk.com Tagged With: CSS

  • 1
  • 2
  • 3
  • 4
  • Next Page »