The iPhone dramarama wheel landed on Tweetie 2 recently, to the tone of much annoyance regarding the fact that the Tweetie 2 upgrade won’t be free to existing iPhone Tweetie users. That is to say, Tweetie 2 is a totally different program than Tweetie, and as such, will require another $3 purchase for those who want to use the latest Tweetie version. That’s not to say that users of Tweetie will be incapable of still using their Twitter client of choice, merely that the developer, atebits, will clearly be focusing on Tweetie 2 users rather than spending most of their time addressing problems with Tweetie “1″. So naturally, buyers of Tweetie may be a little peeved, since they feel neglected and betrayed, particularly when atebits could offer a discount to existing Tweetie users, or even simpler, make Tweetie 2 a free upgrade instead of a new app (albeit at the cost of atebit’s development time).

Perhaps the hoopla is mainly grounded in the naming of Tweetie 2. Clearly, atebits wants to capitalize on the success of Tweetie, though naming Tweetie 2 something different may not have gotten everone as riled up, since a clearer line would be drawn in the sand. After all, it’d be easier to convince people to buy a new Twitter client than a newer version of a client they already paid for. Sure, the argument against a sense-of-entitlement is a simple one to make: atebits clearly spent a lot of time building Tweetie 2 from the ground up, and as a business, they wants to make money where they can (and not where they can’t, thus the continued free-ness of Tweetie for OS X).

And maybe that’s where the second problem lies: blame it on self-entitlement or not, there’s a reason many Tweetie users are upset: the precedent for major upgrades to iPhone apps (as well as software like Tweetie for OS X), at no cost to previous buyers, was set long ago. Developers of apps like Twittelator Pro, for example, have added just as many features as Tweetie 2 will offer, and arguments of Tweetie 2′s superior useability aside, there are many other apps that have offered iterative, substantial updates over time, at an arguable loss to the developers who continue supporting purchases long after they were made. Now that’s no fault of atebits: they’re clearly trying to break free from the way things are generally being done on the AppStore, in such a way that they can afford to work on iPhone apps full-time, whereas many other developers may simply be working on their apps as a side-job. Neither way is inherently right, it’s just that Tweetie users are used to things moving in a direction that favors their AppStore expenditures.

It’s really not a matter of having to shell out a whole $3 more just for the update. We’d argue that if atebits made Tweetie 2 a free upgrade and kept certain features unlockable only through in-app purchases, that they could more easily convince many dissenters to spend that $3 for fancy new features. But instead, they made a new app, which will probably earn atebits a few more bucks in the long-run (since in-app purchases generally make less than stand-alone products), and though that’s certainly a valid move for a business trying to make some extra moolah, it somehow feels wrong, as though atebits is not being honest to consumers. That’s especially true for people who buy Tweetie today, only to find that their purchase will barely be supported once Tweetie 2 comes out.

So the hoopla is an emotional reaction to a problem not with atebits, but the AppStore process, highlighting yet another deficiency with the AppStore’s mechanism for enabling long-term application support by developers who make a living writing, and maintaining, iPhone apps. The only real fault we can find with atebits is not using the in-app purchase mechanism to support the transition from Tweetie to Tweetie 2, but maybe there’s a legitimate reason that atebits couldn’t go that route. (Any developers want to comment on this?)

Ultimately, if Tweetie 2 offers the same features as Twittelator Pro (with TweetPress support for WordPress), we’ll probably drop another $3, knowing full well that that $3 we spent earlier was effectively thrown away (Tweetie offered too little functionality by the time we picked it up). What we don’t want to see is this kind of practice being repeated again and again, however. Rather, if there’s an obstacle to using in-app purchases to charge for major iPhone app revisions, then Apple needs to address this issue pronto, else this won’t be the first time that app buyers get all up-in-arms over the Tweetie 2 upgrade process. As it stands, the process not only angers consumers, but negatively affects app developers also.

09/30/2009 Update: According to atebit’s response to an inquiry by The iPhone Blog, the in-app mechanism wasn’t appropriate.

If all I were adding were features, then the in-app purchase route would have been an option (but then again, if all I were offering were features, I’d probably release it as a free update). Tweetie 2 is a fresh start, 100% rewritten, shares no code with the original . The only thing they have in common is the name.

That doesn’t entirely answer our question though. Does Apple require a minimum amount of code to be the same between app updates? If not, then Tweetie 2 could have new features enabled with an in-app purchase, despite it being rewritten from the ground-up. Aside from the extra development time needed to include the in-app purchase functionality, is there an Apple-imposed obstacle here?Similar Posts:

• Why the 3G iPhone will be “meh” for unlockers. – Some people are wetting their pants over the prospect of a 3G iPhone coming out next month (or this …
• This is why the AppStore will rock the computing world. – Exhibit One: a tilt-shift application built for OS X, which costs $14.99. Purchase from the develope…
• Little reason left for jailbreaking. – When jailbreaking first began on the iPhone, allowing users to install third-party applications, the…
• Turn-by-turn iPhone apps pathetic, so far. – AT&T, known for gouging people due to what we can assume is only pure greed, just released AT&T Navi…
• iTablet AppStore has its downsides. – By now, the rumour-wagon has settled on the idea that Apple’s purported tablet device, to be unveile…

For most web-surfers, one’s inbox is the focal point for spam, but let’s be honest: the internet itself is one giant hodge-podge of spam. The very ease of setting up accounts at most every portal and site out there makes for both convenience and interconnectivity, though it just as easily creates a spawning pool for the unsavory word-vomit that literally covers the cyberspace landscape. This is the very reason that e-mail services have incorporated spam filters, and why notable blogging suites have done same. Arguably, the lack of this feature-set is one more reason that services like Blogspot foster what is now commonly referred to as splogs.

We’ve never used Blogspot as a blogging outlet – we’ve merely experimented with its feature-set. From our understanding, we gauge that for a Google-owned service, Blogspot is rather weak in features compared to its competition, begging the question as to why so many individuals capable of using a hosted-blogging package like WordPress rely on Blogspot instead. This is particularly notable when Blogspot users decide that they cannot keep up with comment spam, which really means that they prefer to delete comments before the comments are posted, instead of afterward. Preferential aside, the real problem with comment moderation is not only that it’s slow (thereby artificially slowing community growth), but because it’s easily abused.

While comment moderation may keep spam out, it’s a tool often used to keep out differences of opinion as well. If blogs are the new journalism (or at least, the new op-ed), then it should follow that comments are ideal for fact-checking, followup, and opposing view-points. If blog authors conveniently abuse a comment moderation mechanism to silence opposing opinions, they’re effectively clumping these view-points into the same category as spam. With that mind-set, why should a commenter (who cares enough about the blog to weigh-in) ever comment again?

Comment moderation is a sinister mistress – it’s significantly subjective when employed against gray-area spam, but moreso when used against non-spam. Sinister is comment moderation’s invisibility – blog authors can simply refuse to publish comments, thereby giving the appearance that no opposing viewpoints among a readership exist. But when this does become apparent, our position is simple: either ignore the author’s inaccuracies or arguments entirely, else comment about them elsewhere. Anything else is simply exposing oneself to an unfair argument: if a blog author can selectively refuse to post a comment, especially in an ongoing discussion, then the author has the advantage of always being heard when the commenter does not.

Not only is comment moderation unfair to the audience, but it’s disrespectful to them as well. This is particularly true in the case of an ongoing discussion thread which, moderation initially appearing objective, suddenly morphs into the opposite, when a commenter is suddenly silenced. If a blog author feels she does not want to invest the time in continuing an argument, she could just as easily bow out of the discussion herself. Silencing the opposition, especially without noting such publicly, is simply poor etiquette, and sends the message that readers should either not comment at all, else stop reading the blog entirely, because their opinions, dare they not agree with the author, will be forcibly unheard.

To bloggers across cyberspace, we ask that comment moderation be deactivated. If no suitable anti-spam mechanism exists to fight comment spam thereafter, then you should move on to a blogging package does. In truth, if you’re capable of setting up a blog on Blogspot, then you’re capable of setting one up at WordPress; comment moderation is not an excuse for Blogspot’s lack of features – better solutions exist. If you believe this transition to be too time-consuming, then we argue that you simply don’t care enough about the quality of your blog, else don’t respect your readers enough to foster a thriving community around them.Similar Posts:

• Blogs and comment solicitation. – I don’t know why it bothers me to so much when I read a blog post that ends in a bunch of questions …
• Unsurprising: Blogger population slows. – Jacqui Cheng posted about the overall blogosphere population slowing its growth, while profit-for-b…
• The online Forum. – When Internet accessibility was widespread enough to drive Bulletin Board Systems underground, Usene…
• Hunter blogs: welcome to 2004. – A few days ago, Xizang became another World of Warcraft (WoW) blogger to point out the proliferation…
• Potential WordPress competitor? – Admittedly, I’m intrigued by the buzzwords used by those describing Chyrp, who claim that it is “lig…

After reading Apple Gazette’s fairly positive overview of Blogo 1.2, we decided to give the stand-alone blogging application a try. (We tried out ecto and MarsEdit in the past, and ecto still stands as our victor.) From Blogo‘s screenshots, we were hopeful that the application could seriously stand against ecto, as it looks quite polished, with a nice feature-set and much better-looking UI than ecto, albeit one that could still use some polish.

One of the first things we noticed when we started Blogo up is that after easily adding mendax.org to our list of blogs, Blogo imported a number of recently published posts. While ecto does this also, the key difference is that Blogo imports saved drafts at the top of the list, whereas ecto drops them to the bottom as if they were posted weeks, months, or years ago. The ecto team claims that this is a WordPress issue, but it’s clearly surmountable.

Blogo also has a nice full-screen editing window that can be toggled. This feature makes Blogo great for authors who post longer entries on their respective blogs, or authors who like to keep their desktop free of distractions while writing. Also, Blogo has a nice preview mode for blog posts, which actually generates a template of your site by connecting to the site in question and grabbing the requisite style-sheets and related documents. All in all, were quite impressed with Blogo up to this point.

Sadly, this is where Blogo’s strengths end, for even with a nicer aesthetic to the interface than ecto, our experiences with Blogo went downhill quickly. Firstly, there’s little image manipulation that can be done. While some may argue that margin sizes should be handled by a blog’s style-sheet, we still like the fact that ecto lets one adjust image margins without hacking up the HTML code for a blog post. We also like that after aligning an image to the left or right in ecto, that text is automatically wrapped around the image. In Blogo, the HTML tags inserted didn’t display the word-wrapping well at all, and we couldn’t find a way to fix it without getting down to the raw HTML.

Blogo also doesn’t show a list of tags previously used. While typing a letter brings up a small window of tags starting with that letter, it’s not as simple as visually check-marking the tags you want assigned to a new post. In this respect, ecto’s implementation is better, though Blogo could run with both ideas and make the tag list an optional, detached window (like the comments window it sports).

Before submitting our first test post, we changed the time-stamp to the following day, so as to queue the post for later publishing. Unfortunately, Blogo ignored our preference and published right away, which is a bug that shouldn’t have made it out of beta testing. A similarly annoying bug was noticed during the editing process itself, in which italicizing or bolding text via command-I and command-B, respectively, did not work unless text was selected.

Finally, after publishing a post, we retrieved it with ecto to make changes. Immediately, ecto complained about HTML syntax errors. After fixing them, we took a look at the image we uploaded, and noticed that Blogo automatically changed the left and bottom margins to 10 (the image was right-aligned). It’s silly that Blogo doesn’t let users change this value easily.

All said and done, Blogo is a stand-alone blogging application with promise, though very simple bugs are making it to release, and that’s really unfortunate. As it stands, the application needs more testing, and more refinement, before it can really stand up to ecto or MarsEdit. For $25, Blogo shouldn’t sport a version number of 1.2 with these kinds of shortcomings.

Similar Posts:

• Learn to write a web page in 24 hours. – To be honest, I don’t recall the exact name of the first book I ever read on learning HTML, but it w…
• Related posts box now sans excerpts. – Another thing that broke after upgrading to the latest version of WordPress is the Related Posts plu…
• mendax.mac – v1.16 We’re not shy about our love for OS X, and don’t hesitate to declare it superior to Windows in…
• The online Forum. – When Internet accessibility was widespread enough to drive Bulletin Board Systems underground, Usene…
• If all your friends jumped off a bridge… – Over ten years ago, when mendax.org first went online, the term “blog” didn’t even exist. Back then,…

We swear we fixed this problem in the past, but apparently we ran into a problem in which we couldn’t leave multiple comments in a given session at mendax.org. The fix we found pretty quickly, but it’s further evidence that Redoable theme is not getting the support it fully needs, and why we desperately need to find a new theme that’s being updated routinely. That is, unless a new version of Redoable is within sight, but we’ve seen few clues about this from the author, Dean Robinson.

Similar Posts:

• Twitter widget removed. – While I played with it here and there, the Twitter widget we’d been using simply wasn’t working, and…
• Messing with themes. – Some have undoubtedly noticed that the layout of this page has been in flux for the past 24 hours or…
• Scheming about WordPress themes. – When Asides/Sidenotes stopped working properly at mendax.org a mere two weeks ago, our troubleshooti…
• Redoable needs some redoing. – After upgrading the theme we’ve been using, a couple things broke, and strangely enough, going back …
• Old posts showing. – I am aware that the front page (at least the main column thereof) is displaying nothing but old post…

Some time back, we stopped paying attention to Bones Wiley’s web site, because he was outta town and knew he wouldn’t be updating it anytime soon. As it happens, his web site broke during that time, and only a few days ago did we manage to pick the old database and put Wiley’s old content back up. All this content was thrown onto a fresh WordPress installation, a new theme was selected as a temporary backdrop, and the song management system used earlier was discarded for something a bit newer thanks to WordPress 2.5.

We expect to see some promising new things from Bones Wiley, so we’re eagerly awaiting his latest creative endeavors.

Similar Posts:

• Turning pages into posts. – Though WordPress is great for dealing with posts, it’s not as good at dealing with pages, in part be…
• More random-frikken-errors. – After getting the Twitter plugin to work earlier today, the site seemed operable, but then spontaneo…
• Twitter widget removed. – While I played with it here and there, the Twitter widget we’d been using simply wasn’t working, and…
• Temporary face-off. – Since WordPress is now level two, the old theme we were using wasn’t entirely compatible, since the …
• The re-emergence of Bones Wiley. – We’ve been urging Bones Wiley to update his website, as we know he’s been hard at work coming up wit…

Apparently, our earlier coverage of Chyrp didn’t push anyone to build any extravagant or even irregular Chyrp themes, and we still haven’t updated our broken theme for WordPress yet either. Yes, we expected to move onto something better by now, but we’ve been holding out for someone talented to bring the Redoable theme up to snuff, else move onto a premium theme.

We’ve strongly considered utilizing one of adii’s Premium News Themes, and an upcoming contest has our interest piqued. Of adii’s themes, we were most enthused by the Kineda Inspiration theme, but as it’s been discontinued, we’ve sort of been holding out on what else adii comes up with. At present, we’d still prefer a grid-based news theme, but with developer support, which the unfinished Kineda theme does not offer.

We do like adii’s Live Wire 2.0, both because of the color scheme and the reliance on smaller graphics for the “main” article. It’s also easy to see various recent articles without scrolling, and overall, the layout puts more emphasis on the textual content of the page versus some other premium themes. Still, we’re not entirely happy with the color scheme (which we could edit ourselves, naturally), and we still prefer the more grid-like layout the Kineda theme offered. Perhaps if the Live Wire 2.0 theme placed the “main” article in the center of the page, with other articles flanking the sides and bottom, we’re be more inclined to give it a go, but then again, this could easily become distracting as well. The lack of ad-space is also a bit disconcerting, and we’d prefer to see more places one could put smaller ads, without requiring to do so.

Nonetheless, adii’s themes have come a long way, and we can see using them both here at mendax.org, as well as on some other sites we administer. Should we not win adii’s latest contest, we may opt to hold out a bit longer for something closer to what we’d like to see in a theme, though we can easily see using something like Live Wire 2.0 and simply having it altered by a professional web developer.

As an aside, what most premium theme designers ought to do is showcase the configuration options of their themes, such that potential buyers can see what options they have for ad-space, feeds, columns, etc.

Anyone have other suggestions as to a theme we should consider?

Similar Posts:

• Riddle me this. – From its birth as the homesite of an underground organization synonymous with the New World Order (N…
• Scheming about WordPress themes. – When Asides/Sidenotes stopped working properly at mendax.org a mere two weeks ago, our troubleshooti…
• Messing with themes. – Some have undoubtedly noticed that the layout of this page has been in flux for the past 24 hours or…
• Downsizing – Tonight I not only fixed some of the staff functionality for the site, allowing us to edit news entr…
• New backend for mendax.org. – You may have noticed that the front page has been acting a little odd over the past couple days, but…

Admittedly, I’m intrigued by the buzzwords used by those describing Chyrp, who claim that it is “lightweight” and “quick” and “uncomplicated”. Chyrp is a cross between a micro-blogging platform and a normal blogging platform, yet the available plugins already offer users a substantial base of features. While Chyrp doesn’t have the large community and extendability that WordPress does, it looks as though it’s off to a good start, and my only reservation on recommending it to someone is the possibility of the author ultimately abandoning it. To curb those thoughts, however, we note that the author has been at the project since 2004, and that the code is open source.

Chyrp is also simpler than WordPress, in that the code behind it appears less complicated, or at least, smaller. Would we ever consider using Chyrp here at mendax.org? The deciding factors would be whether or not available Chyrp plugins can duplicate features we depend on, and whether or not we can find a theme that we’d be willing to go with. As our recent research has been on adapting a magazine-style theme for mendax.org, it’s unlikely that Chyrp would be refined enough before we’re ready to make a decision. Then again, perhaps a talented designer will take a look at Chyrp and decide that it’s something they just must make a refined theme for.

As would-be earlier adopters, we’re also concerned with the fact that Chyrp doesn’t appear to have Feedburner integration possibilities, as the configuration only allows one to point to Chyrp’s own RSS feed. There’s also the fact that Chyrp doesn’t seem to be built to support desktop blogging software because of the way it handles a particular file, but these are all relatively little things that could easily be addressed by Chyrp’s author.

Needless to say, Chyrp looks to have a lot of potential down the road, and we’ll be watching its continued development and community with interest.

Similar Posts:

• Scheming about WordPress themes. – When Asides/Sidenotes stopped working properly at mendax.org a mere two weeks ago, our troubleshooti…
• Welcome to mendax.rss. – Really Simple Syndication (RSS) is nothing new to us at mendax.org. In fact, we incorporated RSS int…
• When others do things for me, I rejoice. – And this post exemplifies such rejoice, for I have learned that Steffen Becker, the author of mendax…
• Turning pages into posts. – Though WordPress is great for dealing with posts, it’s not as good at dealing with pages, in part be…
• Still no new theme? – Apparently, our earlier coverage of Chyrp didn’t push anyone to build any extravagant or even irregu…

When Asides/Sidenotes stopped working properly at mendax.org a mere two weeks ago, our troubleshooting didn’t turn up any solutions, and we ended up getting diverted and began researching new WordPress themes. Finding such themes has always been an annoyance, firstly because finding a good-looking theme that promotes the atmosphere we want is difficult, and secondly, because finding a theme with the options and support we’d like is doubly difficult.

This latter point bears reflection, because themes can be the scourge of users, and the headache of their respective developers. This is because themes come and go; themes are created, and then abandoned. This is a problem because WordPress is ever-evolving thanks to tremendous work on the part of its developers and users. Unfortunately, this evolution breaks many themes and plugins, and since every WordPress user isn’t a PHP/CSS/HTML master, or simply doesn’t have the time to employ such mastery, we are forced to rely on the developers of the troublesome theme or plugin when problems arise.

So it is that as WordPress users who don’t have the time to develop a unique theme ourselves (which is why we switched to WordPress from our homegrown code in the first place), one of our primary needs as a blogger/administrator is to select software with a future. For the foundation (i.e. WordPress), the future’s pretty clear for some distance, but for individual themes, this isn’t the case. In fact, since moving to WordPress, we’ve slept with at least four themes including the current one, and while each lay has been excellent in its own way, we now feel trapped, and so we keep eying the next pretty girl to cross our sites.

Fortunately, we’ve grown as man-whore, and can say that we’re at least picky about who we get drunk next. Part of us still hopes that Dean Robinson will convince Redoable to, well, do us again, by raising Redoable’s version and and somehow making Asides/Sidenotes work again, since we really started to rely on them for output. Since there’s been little word on this front, however, we’ve begun considering paying for our fun, and adopting a premium theme.

I’ve always been somewhat opposed to the idea of paying for a theme, especially when others can still use it. Of course, less people will use it, and there’s a better guarantee of developer support, but then again, we wonder just how long such support will last in the end.

We began using Redoable just under a year ago, and it’s treated us well for most of that time. A year is about what you’d expect to get out of updates, and it’s a miracle that Robinson intends to do something with the theme down the road, instead of outright abandoning yet. Nonetheless, unless such an update hits soon, and the specific problems we’ve encountered are addressed, then that same year of use marks its the expiration date on our end.

Nonetheless, a year is a long time, and premium theme developers haven’t been too upfront about whether or not their direct support will exist for a theme older than that. In fact, no time frame is ever mentioned as far as I can tell, and though we’re still intrigued about magazine/news-style themes (since it fits the e-zine concept we hoped for back in ’96), adopting this format for a price, when the theme will ultimately be disposed of a year later, leaves us with much trepidation.

Chances are, mendax.org will make its move to a new theme sometime in February. What theme we’ll adopt, however, is still up in the air. We’ve looked into Revolution, Premium News Theme, and News, and are still undecided. This morning, we heard that iThemes went live, releasing the Essence series of premium themes, but these too, are underwhelming. The problem we see is that many of these themes are based on visual eye-candy like pictures and movies, and don’t lend themselves to a more newspaper-style, primarily-text interface. We don’t want mendax.org to become some flashy site filled with large media files, partially because that was never what we intended to become, and partly because we don’t have the time and talent at the moment to generate that kind of content anyway. Then, we’d like a theme with the potential for ad placement, and by potential, we mean preset placement of ads paces, should we decide to use them. The ad subject is tangental at the moment, but on the back of our minds anyway, and so it’s a topic of consideration for our theme selection process.

In any case, should any of you fine readers have a suggestion, be that for a premium theme or not, we’d love to hear it. What’s clean, customizable, fairly unique, and backed by a developer who isn’t going to shed their relationship with the theme anytime soon? Are we hoping too much?

Similar Posts:

• Still no new theme? – Apparently, our earlier coverage of Chyrp didn’t push anyone to build any extravagant or even irregu…
• Changing themes. Again. – We’ve switched WordPress themes again, sadly changing the look of the site once more. I wasn’t satis…
• Redoable’s commenting problem. – We swear we fixed this problem in the past, but apparently we ran into a problem in which we couldn’…
• Twitter widget removed. – While I played with it here and there, the Twitter widget we’d been using simply wasn’t working, and…
• Messing with themes. – Some have undoubtedly noticed that the layout of this page has been in flux for the past 24 hours or…

I am aware that the front page (at least the main column thereof) is displaying nothing but old posts. If anyone knows how to resolve this, I would greatly appreciate it. This problem suddenly began yesterday, and I did not change anything to cause this. Since the problem started, I updated the WordPress files to the latest version, but still no luck. The issue does not appear to manifest when I am using the default theme.

Update: The problem appears to be caused by Sidenotes/Asides being enabled. Under the K2 theme, different post categories set as Asides cause different front page posts to show up, while Sidenote categories aren’t even selectable for me anymore after copying Redoable over from scratch. Interestingly, Sidenotes/Asides always display from newest to oldest, whereas the front page itself displays older posts. Sidenotes/Asides are currently disabled so readers can view the latest posts. Any ideas what’s going on and/or how I can fix it?

Update 2: It’s been two days now since the problem appeared, and we’re strongly considering changing themes until the problem is resolved, or potentially for good. Things may be rickety during this time until we settle into something that looks good.Similar Posts:

• Scheming about WordPress themes. – When Asides/Sidenotes stopped working properly at mendax.org a mere two weeks ago, our troubleshooti…
• Related posts box now sans excerpts. – Another thing that broke after upgrading to the latest version of WordPress is the Related Posts plu…
• Redoable needs some redoing. – After upgrading the theme we’ve been using, a couple things broke, and strangely enough, going back …
• Messing with themes. – Some have undoubtedly noticed that the layout of this page has been in flux for the past 24 hours or…
• Redoable’s commenting problem. – We swear we fixed this problem in the past, but apparently we ran into a problem in which we couldn’…

While I played with it here and there, the Twitter widget we’d been using simply wasn’t working, and so I took it down for the time being. Dean J. Robinson, the creator of Redoable (the theme currently powering mendax.org) recently stated that a new version of the theme would be out by year’s end to support the latest version of WordPress. Since we recently upgraded to said WordPress version, the tagging system we were using also broke (as tagging is now native to WordPress).

Hopefully when Redoable 2.0 comes out, both our Twitter status and the tag display (and maybe even the category cloud widget) will all be working again. In the meantime, at least the core of the site (content!) is fully functional.Similar Posts:

• Twitt-Two working again. – http://www.deanjrobinson.com/wordpress/twitt-twoo Some readers may have noticed that the Twitt-Two p…
• Bringing back the bones. – Some time back, we stopped paying attention to Bones Wiley’s web site, because he was outta town and…
• More random-frikken-errors. – After getting the Twitter plugin to work earlier today, the site seemed operable, but then spontaneo…
• Messing with themes. – Some have undoubtedly noticed that the layout of this page has been in flux for the past 24 hours or…
• Redoable’s commenting problem. – We swear we fixed this problem in the past, but apparently we ran into a problem in which we couldn’…