OK, had to do away with the Twitter gadget already.
Apparently, Twitter places a limit of 350 API calls per hour on a given account. This is a perfectly reasonable number; I don't think I could make 350 queries from my Droid in an hour if I tried.
Yet, after posting once around 10AM and doing nothing more for the next 6 hours, I was still getting an error message from Touiteur saying I'd exceeded my API call rate limit. Turns out the blog gadget is making those calls. That's way too many calls in an hour for a blog gadget. Especially for a blog that no one actually reads (or posts to). :-P Guess I'll have to figure something else out if I want the posts to show up here; I can't have my blog effectively blocking access from my phone, now, can I?
Tuesday, July 6, 2010
Monday, July 5, 2010
Something must be wrong with me. I was sure I'd never have a blog. I made one anyway, and the regular updates didn't last very long, just as I'd suspected. Then I started using Google Buzz here and there, which actually wasn't such a big deal since it's well-organized, and neatly integrated into Gmail. Now I have a fucking Twitter account, too.
I didn't understand Twitter for a long time. OK, I got that you could post to a blog-like thing via text message, which I guess is nifty. But I had a hard time following conversations on it, and thought it counter-intuitive to have something set up to read responses before what prompted them (and my blind [and/or apathetic] ass didn't see the "in reply to" links for a long time, meaning I was sifting through posts to find a corresponding date). Now that I've seriously checked it out, it makes a little more sense.
Noticing that not everyone uses Twitter to try and talk to each other had a lot to do with my coming around. Also, the ability to steer clear of high-schoolers comes easier than I'd expected. That helps even more. The icing on the cake, for me, has been Touiteur, an excellent application for the Android OS for viewing and posting to one's account. The pleasure of using that app alone is almost enough to justify having an account.
Anyway, if you're interested, you can probably see that I already added a gadget to the sidebar here showing recent "tweets" and a link. I'm not going to try harvesting followers since I don't even know what I'll use it for yet, but feel free if you have your own account and want to keep tabs.
I didn't understand Twitter for a long time. OK, I got that you could post to a blog-like thing via text message, which I guess is nifty. But I had a hard time following conversations on it, and thought it counter-intuitive to have something set up to read responses before what prompted them (and my blind [and/or apathetic] ass didn't see the "in reply to" links for a long time, meaning I was sifting through posts to find a corresponding date). Now that I've seriously checked it out, it makes a little more sense.
Noticing that not everyone uses Twitter to try and talk to each other had a lot to do with my coming around. Also, the ability to steer clear of high-schoolers comes easier than I'd expected. That helps even more. The icing on the cake, for me, has been Touiteur, an excellent application for the Android OS for viewing and posting to one's account. The pleasure of using that app alone is almost enough to justify having an account.
Anyway, if you're interested, you can probably see that I already added a gadget to the sidebar here showing recent "tweets" and a link. I'm not going to try harvesting followers since I don't even know what I'll use it for yet, but feel free if you have your own account and want to keep tabs.
Thursday, July 1, 2010
VirtualBox updates
Yeah, I know I'm not posting anything lately. This is totally unrelated to the blog, but I have to put it somewhere. I'll start making real posts again eventually.
I'm running Ubuntu 10.04 on my work laptop, and I need a Windows VM (mostly for IE stuff), so I use VirtualBox.
Problem is, every time I update my Ubuntu kernel, it breaks VirtualBox, and I always have a hell of a time on Google figuring out how to fix it. So by posting it here, hopefully I'll remember, or at least be able to find it again!
At any rate, the problem is that attempting to start a VM produces an error something like:
"Inexistent host networking interface, named 'vboxnet0'"
Ignoring the fact that "inexistent" is not actually a word, what has happened here is a problem. The real problem is not that the network interface has disappeared (although it looks that way), but that the vboxdrv kernel module isn't working properly anymore due to the kernel update. So the kernel module just needs to be recompiled, like so:
sudo /etc/init.d/vboxdrv setup
So all of those people out there opening bug reports and telling people not to upgrade VirtualBox are just plain wrong. This should be fixed by the developer, but what needs to be done is to have some kind of trigger in place that recompiles this module any time the kernel is updated. Hopefully this post makes its way into the Google results for this problem so that it turns up an actual solution for someone.
**EDIT: My mistake: "inexistent" is indeed a word. Apparently it's just so rare that Google wants to auto-correct it every time.
I'm running Ubuntu 10.04 on my work laptop, and I need a Windows VM (mostly for IE stuff), so I use VirtualBox.
Problem is, every time I update my Ubuntu kernel, it breaks VirtualBox, and I always have a hell of a time on Google figuring out how to fix it. So by posting it here, hopefully I'll remember, or at least be able to find it again!
At any rate, the problem is that attempting to start a VM produces an error something like:
"Inexistent host networking interface, named 'vboxnet0'"
Ignoring the fact that "inexistent" is not actually a word, what has happened here is a problem. The real problem is not that the network interface has disappeared (although it looks that way), but that the vboxdrv kernel module isn't working properly anymore due to the kernel update. So the kernel module just needs to be recompiled, like so:
sudo /etc/init.d/vboxdrv setup
So all of those people out there opening bug reports and telling people not to upgrade VirtualBox are just plain wrong. This should be fixed by the developer, but what needs to be done is to have some kind of trigger in place that recompiles this module any time the kernel is updated. Hopefully this post makes its way into the Google results for this problem so that it turns up an actual solution for someone.
**EDIT: My mistake: "inexistent" is indeed a word. Apparently it's just so rare that Google wants to auto-correct it every time.
Subscribe to:
Posts (Atom)
Posts
