I posted a tweet today that suggest that Social Wok had problems. Social Wok replied to my tweet asking for more information. Now that’s the way to follow up! Take note of that folks. Responding to complaints is a good thing as I went the extra mile to grab some screenshots(see below) and am creating this post. If they hadn’t responded I probably would have removed Social Wok and just moved on.

update: And they wouldn’t have fixed it already making their product better, this user happy with them, and all that before I could even finish this post (granted there’s a lot of fluff in this post).

So Lev Gonick has started an effort to get Google to choose Cleveland and/or Northeast Ohio for its Google Fiber for Communities. I of course followed the twitter account Lev created for this purpose — Google1Gig4CLE. Lev has been very active in bringing broadband and it’s benefits to Cleveland, with OneCommunity and the effort around University Circle and Case University.

My question for Lev is this — what’s the plan?

Beta for Google Chrome is released. Cute little graphical novel-like announcement: http://www.google.com/chrome/intl/en/w00t.html
 w00t indeed.

Of course, I’ve been running the “developer” version for several months.  It’ll be interesting to see what the difference is.  So far the only issue I have really had is no audio on videos, YouTube or otherwise.  Granted there have “blips” of issues, but nothing major.

google, google chrome

Powered by ScribeFire.

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.

Wow. I discovered this morning that I can use my google app private domain account as a google account. Perhaps I am slow, but what I had been doing is associating my gmail google account with my google app account. However, today I received a google wave invite to my private domain. In the process of muddling around I discovered the ability to create a google account using the google app domain. So for example, now that my rbh at neohawk.org account is also a google account, I have a google profile, picasa account, etc. Until today, I need to use my gmail account to login, but now I can use my neohawk.org account. See below:

You can see my profile below:

This is huge. One of may largest complaints with google has been the two different logins I needed. One for my google apps, one for google accounts. Now that they are the same, I’m a happy camper. I did have to remove my neohawk.org account from my gmail google account to make this work.

Did I just not know this or is this new?

google

Powered by ScribeFire.