Tag Archives: Akismet

Blog Advisory – Feedburner and Akismet

Time for a bit of blog administrative business, which I suppose I could spin as a Blaugust post, it being related to the issues that come with a blog.  Or not.  Either way though, it is a post in Blaugust.  We’re about half way through the month.

Feedburner Email

I have been advised by Marina at Follow.it that Feedburner is discontinuing its email syndication program.  Her company apparently has a substitute service they would like to offer me.

And apparently at some point in the distant past I did post a link for people to get my posts via email.  I don’t remember encouraging it at any point after that, but there it is.  I have long since swapped over to recommending the WordPress.com integrated email delivery.

So, if you are subscribed through Feedburner and wish to continue getting my blog posts in you inbox, you will need to switch over to the WordPress.com service.  It is available in the side bar near the top.  Just enter your email address and it will send you a confirmation email that will let you select your preferred deliver method from “immediately on post” (not recommended unless you want to see all my typos), to “daily summary” (I’ve usually fixed a lot of typos by then), to “weekly summary” (which might be a bit too much of me in a single dose).

Feedburner RSS

There was a time when I used to do blog posts about RSS feed.  I think RSS is dying interface from a more civilized age now.

While we’re on the topic of Feedburner, I pretty sure I mentioned at some point that the Google had removed email account recovery as an option from the service (and from Blogger).  I missed the window for recovering my account and have no clue what the password might be, so I couldn’t migrate their email option over to another service even if I had the inclination to do so.

While Google said that they won’t be shutting down feeds of purging accounts Google, as my wife puts it, “Says a lot of things.”  Whether they mean it in the moment is debatable, but we have all learned that promises from companies have an unlisted expiration date.

So I think I am going to recommend that if you’re using a read to read TAGN, that you go with the default WordPress URL, which i:

https://tagn.wordpress.com/feed

I realize that about seven years back I asked everybody to go the other direction, so all I can do is reinforce my change of heart in meme form.

Use your best judgement

Everything will probably be fine for now if you don’t, but if I suddenly disappear from your feed, that might be the immediate cause.

Akismet

Some of you will recognize the name Akismet as the spam comment protection package that comes with… or at least used to come with… WP.com hosted blogs.  I reference it in my blog anniversary posts most years to indicate how many spam comments end up here.  I even have the counter widget down at the bottom of the side bar.

Well, Akismet was broken on WP.com for a stretch, at least for some sites.  That meant rather than about 200 spam comments landing in my spam folder every day I was getting at least 2,000 spam comments to go through, and usually more.

Which means that if you left a comment and it landed in the spam folder this month, I probably didn’t see it.  I am pretty good about going through and fishing out such comments, but when the number gets into the thousands, I just don’t have the will.

WP.com took their time getting to things.  I sent them a note a couple weeks ago, got a response back about ten days later that referred me to a bug they had opened on the issue, and then they closed the support ticket.  The bug got fixed about a week later, which isn’t bad I guess.

But if you leave a comment and it disappears you can always use the contact form on the About page to ask about it.  If I know the name on the comment I can almost always find it.

6,000

Also, after writing this I was looking at the stats and realized that yesterday was post 5,999, which means that this is my 6,000th post.  Another meaningless milestone achieved.