![]() |
Our Home is Our Castle |
- Electrical (done today)
- Plumbing
- Furnace and AC Check
- Masonry (tuckpoint work)
- Chimney Sweep (probably not this year)
- Minimal Roofing Repair (not this year)
Welcome to Robataka's blog. I used to blog alot more, not so much these days. Particularly since google plus, facebook, twitter, etc., have taken over I just don't find myself blogging as much. But every now and again I do and that's what this place is for
![]() |
Our Home is Our Castle |
As I mentioned in my New Year's post, last year I was able to successfully quit smoking. However, it did come at a price - I gained 30 pounds. Since coming back from Japan and prior to quitting smoking I had already put on 20-30 pounds. So that's about 60 pounds in 5 or 6 years. That's pretty bad.
Now, the reality of it is that the last 30 pounds is what really made it bad. That gain in weight was a direct result of quitting something that is even more dangerous and damaging to my health - smoking. Last year, I knew I was gaining weight and eating more "snacks". I made a conscious decision to not worry about it until this year, or rather after a full year of not smoking. I completed that full year so it is time for this year's challenge.
www.neohawk.org is currently down.
@grokthis: The SAN filer crash appears to be non-trivial. Recovery efforts are underway. Service is not expected to be restored in fewer than 12 hrs
It'll be up when it's up. That was from 5-6 hours ago.
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!
I am trying out Disqus for comments on the blog.
Disqus Comments is a comment system and moderation tool for your site. This service lets you add next-gen community management and social web integrations to any site on any platform. Hundreds of thousands of sites, from small blogs to large publications, rely on Disqus Comments for their discussion communities.
Perhaps this is easier than the built in one. We'll see...or maybe not since nobody comments on my blog anyway...
If I decide I like it, I'll clean up the template to remove the default comment stuff.
For the time being, nevermind. It didn't work like I thought it would.
I am trying something new on this blog. I am giving Google Connect a go for commenting. I have also added a "social bar" on the right side of the blog, but that was really part of my testing to make sure that Google Connect was working.
This site is powered mostly by Byteflow with some minor code added by me (news and links), and a couple other pieces of Django code/modules. But I wanted to give Google connect a try. With Byteflow, in order to comment you need to register with this site either with an OpenID account or a email address and password. I'm pleased with the OpenID support, but not many people actually know what it is. They do know their google, aim, or yahoo accounts and can use those to register and then comment.
Of course, there actually needs to be somebody reading this blog before any comments are going to happen. But I know I'm talking to myself here in the ether. But I think this may be easier in the long run.
I'll need to tidy up my templates since there is still some stuff left over from the byteflow templates. I'll need to nix those when I get around to it.
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.