Entries for April, 2008

things demanding my attention

South Dakota decided to celebrate April Fool's a little early by dumping some heavy, slushy snow on its inhabitants. I would rather have shoveled rocks than that. At least rocks would have gaps between them to lighten the load, instead of scoops full of melting mush.

Something is wrong with my Tabulas style. I had no idea you could generate a regex error with a CSS file, but that seems to be what's happening. I'm afraid to edit the stylesheets for fear of permanently corrupting them. At least it's not the crazy "Access Denied" error that cropped up when I tried to upload some FeedFlares; that terrified me. I thought maybe some inner working of the server had wrongly flagged me as an intruder trying to hack the site. I'm still not sure what that message actually meant.

Tabulas apparently supports the MetaWeblog API now. That was cool to learn. It was less cool to reinstall ScribeFire and DeepestSender to test the new API, only to find that neither worked. (Why did I only try Firefox add-ons? Because I know I can install them without needing to reboot, and I was in the middle of a couple things that precluded rebooting.) One persistently claims my username and password are wrong, even after I have just used them to login on the site. The other returns an error implying that the MetaWeblog API endpoint does not have Blogger API functions implented, even though it's my understand that MetaWeblog is designed to run on top of the Blogger API; it appears normal for MetaWeblog clients to use Blogger API methods as well as methods of MetaWeblog. I haven't tried other clients because I can't be arsed to dig out the computer I've installed them on, not when I've already tried the FF add-ons and nothing works there.

The closest thing Tabulas has to documention has been altered to only list MetaWeblog, barring a few places the editor's find-replace must have missed. I have no idea if Tabulas still supports the Blogger API or not. I hope it does — as I said above, MetaWeblog expects to have the Blogger API beneath it.

That page will need rewriting. If the MetaWeblog API works for others and it's just my computer being inexplicably retarded, it will change the list of which clients do and don't work with Tabulas. If the Blogger API is no longer supported, that needs to be noted; if it is still supported, its information needs to be added back to the page. No matter what has changed, the page has some slightly slipshod grammar in spots and needs a touch-up. I imagine that task falls to me as payback for creating the page in the first place.

There is not enough caffeine in the world to help me figure out what to do about all these things. One foot at a time, I suppose.

testing old Semagic

I can successfully sign in with an old version of Semagic (1.5.8.3U) once I changed the default port number to 80 in the server settings (and the API to MetaWeblog, of course). No category list shows - trying to refresh the list pops up "Error parsing response XML".

EDIT: Posting goes fine, but can't edit old entries - the titles listed are correct but the entry bodies are all blank. May be a bug in Semagic; if so, may be fixed in less ridiculously antiquated versions. Must upgrade to determine cause of bug.

Son of Edit: Current version (1.7.0.9U) also has blank entry bodies when attempting to edit existing posts. Suspect Tabulas' implementation of API not quite matching what Semagic expects. Will test more clients; if most-to-all have same bugs, will make list of copy-pasted error messages received and ask Roy to puzzle over that.

My trial of BlogJet expired so cannot try it on new API. Not particularly bothered by that.

testing Zoundry Blog Writer

Testing Zoundry Blog Writer. Cannot set categories; based on Semagic being unable to set categories, this may be an anamoly in Tabulas' implementation of the MetaWeblog API. Possibly Tabulas is following the spec but the blog clients are not - would not surprise me.

When trying to edit existing entries, entry bodies are blank but titles and dates appear correct. Again, since Semagic had the same problem, may be due to differences in interpreting (or "working around") the API spec.

WB Editor correctly picks up my list of blog categories (that might be a plus for the program or it might be a recent change in Tabulas' implementation of the MetaWeblog API; I'd have to retest clients from earlier today to determine that). I'm not keen on the interface but that's personal opinion.

WB Editor displays the same oddly empty bodies on existing entries that all other clients have shown today - that's WB Editor, Zoundry Blog Writer, Semagic, and DeepestSender (so far). Either they all have the same bug or the bug is on Tabulas' end, or maybe it's not a bug but a difference of opinion between developers that just so happens to leave me grinding my teeth in unmitigated frustration.

EDIT: Posting through WB Editor works but causes an error to pop up: "Object reference not set to an instance of an object." That's useless for my purposes but thanks for playing.

DeepestSender let me login but my post hung without going through. I find DS generally more reliable than its direct competitor, ScribeFire (which is absolutely pants), but there's a distinct possiblity that DS is merely the less bugridden of the two rather than bona fide good software.

Qumana has a slightly different problem when trying to edit existing entries: instead of blank entry bodies, the entry bodies all contain only the text "null" - probably an error in the way Qumana handles content that isn't what it expects.

Qumana does not let my choose a category for my new post. I've realised the categories issue across various clients may be partially due to my category names, some of which include ampersands. It's possible there are encoding or escaping issues with those amperands that are borking something that would otherwise work. Unfortunately, I don't know better, ampersand-free names for those categories, and a bug is still a bug even if some people never experience it. If I'm right that the ampersands are an issue, hopefully at least some blog clients are capable of handling it anyway.

Qumana consistently wants to timestamp my new post an hour in the past and I don't know why. My computer clock has the correct time, so that's not the problem. For testing purposes, it's simple enough to manually correct the timestamp; for everyday use, it would drive me crazy to fix every single time.

Upon pressing "Publish Post", Qumana displays "Publishing [post title]" but never finishes. This is the same behaviour I noticed with DeepestSender, and something that did not occur when I previously tested Qumana using the Blogger API.

I wasn't able to test BlogJet because I previously tried it, and my trial period had expired. I didn't want to pay $30 when I'm not sure the program will even work with Tabulas. Likewise, I'm holding off on installing Ecto for Windows, in part because I heard the Windows port is buggy and unstable (as opposed to the Mac original, which I've heard only good things about). I may come back to them when Tabulas' MetaWeblog API gets some kinks worked out.

testing Windows Live Writer

I caved and installed Windows Live Writer. Bleh, MicroSoftware, right? But it actually seems pretty nice.

I wish I could access previous posts (those not made through WLW), but it's not a dealbreaker. At least it's intended to be this way instead of being bugridden. The categories list isn't populated though and that one is vexing.

EDIT: Trying to edit a post made via WLW earns a popup error: "Unable To Retrieve Post From Server". Botheration. I was liking the program otherwise.

testing w.bloggar

I know Roy's already tried out w.bloggar on the MetaWeblog API, but I am sick of installing software and figured I'd take what I already have for a whirl. So far it's looking good. It reads my categories and lets me set more than one (assuming this post goes through). I can access previous posts to edit them offline! Yay! Either that's a recent improvement in the Tabulas implementation of MetaWeblog or w.bloggar is my new (and old) best friend. w.bloggar doesn't seem to locally cache posts at all; if I ever want to edit an entry and have already lost Internet connection, I'm out of luck. Still, it's much better than no way to edit old posts.

EDIT: I forgot to markup my post. Gotta get the hang of that.

testing w.bloggar

I already wrote this post once but it vanished into the ether when I tried to edit it. Crazy. So here's the upshot: w.bloggar works, categories work, editing posts works BUT there's at least a chance of the entry disappearing entirely from your blog, hard drive, and the universe as we know it.

The unfortunate part is that a chance of completely losing a post is still the most functional arrangement of Tabulas' MetaWeblog API + a blog client that I've found.

DeepestSender and Tabulas

Trying to edit old entries via DeepestSender sometimes brings up a window with blank title and blank body, while other entries appear correctly in the edit window. I haven't the guts to try editing and saving a post through DS in light of that apparent bug. No category support even though DeepestSender has it and it's checked in account options. And last time I tried to post through DS, the posting window hung until I closed it myself; the post never went through. Too bad, because if DeepestSender could work, that's a cross-platform client right there: Windows, Mac, Linux — anything that can run Firefox, Seamonkey, or XULrunner can run DeepestSender. Eh, even if all else should fail, I'll still have w.bloggar and Blogger API support. Aw hell, I should've figured. Checked the Firefox error console:

Error: cats has no properties Source File: chrome://deepestsender/content/protocols/blogger/metaweblog.js Line: 40

Followed by a bevy of:

Error: catsnode.firstChild has no properties Source File: chrome://deepestsender/content/protocols/blogger/editing.js Line: 25

Looks like DS is hanging because it doesn't handle the error from the categories problem. Botheration. Oh well, at least now I know that. Didn't some other client also hang when trying to post? That's right, it was Qumana. Aha. Maybe Qumana hangs for the same reason DS does. Woohoo, knowledge!

 

DS doesn't support standalone Blogger API; it uses some of it in conjunction with the MetaWeblog API, but there's no way to use only the Blogger API methods. Qumana claims to support the Blogger API but actually appears to only support blogger2 methods, which Tabulas doesn't seem to use. I can test DS with category support turned off, though!

EDIT: Unchecking category support for the Tabulas account (done when logged out of any DS account) lets it work. I'm still wary of the seemingly random and totally blank entries when I go to edit them via DS, though. That's just eerie.

free antivirus for Ree

Cherished readers, I have a little favour to ask of you: recommend me a free (or budget-priced) antivirus program for Windows XP, please?

I'm familiar with Bitdefender and AVG Free.  I'm leery of using either again, Bitdefender because it forces me to re-register on a regular basis, AVG because I'm pretty sure its TOS only allows me to use it on one computer at a time and I'd rather not violate that.  (I know I could and I'd get away with it, but I hate to rulebreak when Grisoft is willing to let me use their software for free.  Otherwise I would run AVG on all my PCs — it's served me quite well.)

I've also heard vague positivity about F-Prot, ClamWin, and Avast! but I'd like to hear user experiences before I install something.

my grandpa or my neck

My throat is driving me crazy.

I am insanely over-sensitive to tobacco smoke. Meanwhile, my grandfather is of a generation that got packed off to war with boxes of cigarettes and came back with an addiction. Houston, we have a problem.

I love my grandpa to itty bits pieces and I don't turn down a chance to hug him. But. I spent several hours yesterday at my aunt's birthday party, with Grandpa. And then headed home, in the same direction as Grandpa, and ended up meeting him again at a restaurant. In the smoking section, since that is where a smoker will naturally sit, and he got there before I did.

I'm not the least bit sorry, but my throat sure is. This particular body part seems certain that I deliberately arrange my life to achieve maximum respiratory inflammation. Accordingly, it has decided that I must be punished. Again.

Unfortunately, I've looked time and again for something to help me be less sensitive to smoke, but nothing works. Symptoms are similar to allergies but the immune response isn't the same as an allergy would cause, so allergy medications have no effect.

If my choices are angry throat or sad Grandpa, I'm quite satisfied with my decision – but if there's a third option where I can enjoy my grandfather's company while maintaining healthy airflow, then want!