As many of you know, I’ve been using Byteflow for this site and blog. Byteflow is a blog system built in Django. The glorious design(sarcasm) is mine. I should also add that the News and Links are little modules that I created. Which I’m pretty proud of as I’m not a programmer/coder, and even though they are real simple and pretty featureless (no RSS for example).

That’s one of the things I like Byteflow, which is really a blog system, is that I can build other “apps” and include it into the blog to make it a “cms“. And Django is fairly easy to get your head around to do so, at least for the easy stuff.

Anyway, as I posted in “New URL“, I was planning to move everything over to Google, particularly the blog over to blogger — this one in particular: robataka.neohawk.org. For one reason, it’s free. Free as in no charge, not the FLOSS free. It was a cost saving measure as I run this site one a vps, from VPS Village. Now it’s not terribly expensive, in fact it’s inexpensive. I’m sure I might find even cheaper ones. But if I’m going to move my site for cost reasons, it’ll be to free rather than for just less money.

More importantly though, I was going to switch simply because it was easier to post to blogger than it was to a Byteflow blog. My number one “complaint” or dissatisfaction with Byteflow was simply the inability to post to my blog via ScribeFire (what I’m using now) or other blog editor/tool. I always had to go in via the web admin interface. Where as with Google’s blogger, I could use a blog tool like ScribeFire to post to it. It just makes it easier to post which means I’ll post more often. Or that’s the idea anyway.

So here I was getting ready to move. I updated my dns so that you could see robataka.neohawk.org, and I posted all of the entries from here to my blogger blog. I was playing around with Google Sites (useless for my current needs), App Engine Site Creator (cool, and usable, but just not quite right for this — I do use it elsewhere). But I was going to bite the bullet since every decision involves trade offs. I’d be getting a blog that’s easier to post to, but a weaker solution for non-blog stuff. And less control, or more work really, to control the look and feel of the site.

So what do the developers of Byteflow do? They fix Byteflow so it now can handle the MetaWeblog API, and therefore using blog editing tools like ScribeFire(apparently Echto works too). Damn you! Stop making Byteflow so usable!

So now I’m back to using Byteflow at least for the foreseeable future. I may end up posting in both blogs until I finally make up my mind. But for now, Byteflow wins again.

Damn you Byteflow!

django, byteflow, google, google sites, google app engine, blog,

Powered by ScribeFire.

So I’ve been thinking about what to do with this site. Simply put, I’m thinking of moving it to google in some form or fashion. The main motivation is money. I don’t get enough access to warrant paying any money for “hosting”. I currently pay a small fee to GrokThis, VPS Village actually, for a xen virtual host. But anything at this point is too much.

I have had a test blog up on Blogger for quite a while now. It’s been mostly for testing things like email posting, blog editors, gadgets, etc. So last night I finally broke down and tried to see if I could get blogger to look something like this site. While not exact, I’m close enough. Check it out.

Actually it was fairly easy to modify to make it look like this site. It’s not done, nor perfect but was close enough for me to figure out what else was necessary. It also helped me figure out what I did and did not like about blogger. At least partially anyway.

What’s to Like

1. It’s free
2. It’s linked to my google account
3. You can easily add gadgets
4. It’s fairly easy to customize design
5. You can email posts to the blog
6. You can use blog editors, like ecto, scribefire, or google’s Sidewiki
7. I can use my neohawk.org domain if I wish
8. Blogger itself generates traffic to my site
9. I can create a multi-author blog (me and arisa, if arisa ever posts
10. Posting in Japanese is no problem
11. Can use feedburner
12. Easy to implement Google Analytics

So that’s a fairly good list of things it does for you. Here’s the list of things I don’t like about it

What’s Not to Like

1. Miserable on html validation: the template I used had 636 errors on it. That’s not even close.
2. I can not use my google apps account to use it
3. To really customize it, you have to be very careful with the built in widgets and code built in or I’ll probably break the site
4. No concept of “static” pages, so it is only a blog
5. Fairly convoluted process to add Disqus which I like as a commenting system
6. CSS and some javascript is in the template -> I’d prefer them separate
7. Does not provide a way to show posts for a given author(that I can find

Based on that, you would think it’s a no brainer to move to blogger. Actually thought, I’m not feeling the love for blogger. The fact that I cannot use my google apps domain (neohawk.org) to login to the site is huge, as is the effort to customize it to the point where the html, etc., is valid — and I’m still not sure I could get there because of code that Blogger needs.

In general, I’m quite annoyed with the shortcomings of google apps and it’s integration with other google products and services. Picasa, blogger, google reader, openid provider, friend connect, google analytics, etc., require use of a google account. I don’t want to use a google account, I want to use my google apps domain.

Granted, I can not complain too much since it is all for free. No, that’s not right. I can complain because it’s not “free”. I’m providing information to Google as their stated goal is to index everything, I’m making it easy for them. So I may not be paying money, but I’m paying.

One of these days I’ll do a serious post about Google’s ineffectiveness. But for now, I’ve checked out using blogger. I now need to check out Nick’s posts on creating a blog with google app engine.

One down, one to go.

Yesterday, I posted about City Websites. Today, it’s about this website. As some of you have noticed, I brought down my Planets, Planet NEO and Neohawk IT. I did this mostly for time and money reasons. The server they are running on is memory challenged and Planet NEO in particular was getting very large, memory consumption wise. It had over 50,000 posts archived. So it kept crashing, and I was spending more time trying to keep it up than I want.