So for some strange reason, CoverItLive will initialize on my Windows machine using FF 2.0, but not my Mac. Seeing as if my Windows machine is acting wonky right now, this isn’t good. I’m still going to try it though.
Hmmm. Maybe I should backtrack a bit. I’m not a big fan of liveblogging. Either I take part in something (and enjoy it) or I liveblog: I can’t do both. Via The Next Web, I learned about CIL, which may make liveblogging a tad bit easier for me. I decided to try it out today.
One uh-oh about the service is that, at least according to CIL’s website, the iframes in the code don’t play nice with WP. Actually, that should be reversed: WP doesn’t play nice with iframes. CIL recommends giving your users the actual link to the code instead of the embed. Users paste the link in the browser and the liveblogging session pops up in a window. Not really keen on that.
In any case, I’ll try to test this thing out some more.
I’m still having a hellified time with del.icio.us’ daily blog posts. I have no idea why I keep getting the error message I described in this post. In any case, yet another mystery to solve.
On another note, I lemminged (is that a word?) and splurged on Moo cards. It was time for me to re-order personal business/calling cards and I couldn’t fathom shelling out my life savings over CHF200 yet again for plain white ones. My flickr photos are on one side, my contact info on the other. Very, very attention getting. Depending on the type of business you’re in (I wouldn’t recommend these for in “serious” trades such as banking or insurance) you may want to take a chance on Moo cards: they stand out, especially during conferences when folks are swapping contact info like mad.
Yet another note: I’m investigating the option of using Wordpress as a CMS for a couple of projects. There are some kick-$$ templates out there, but they’re pricey. Mimbo is an option though. I know it’s a lot to ask, but WP is such a wonderful product that it’s almost a shame that it hasn’t been CMSed already (perhaps it has and I just haven’t found the package). I’d thought about attempting to tweak it myself, that that would require time and patience…neither is in great supply for me right now.
By the way, I got a hold of danah boyd’s “Facebook’s Privacy Trainwreck: Exposure, Invasion, and Social Convergence.” Getting into it tonight.
I played with Yahoo Live for a bit tonight. Don’t know about this. Reminds me a tad bit too much of JennyCam or JustinTV. But, it is gosh-darned fun if you’re in the mood. Yahoo Live could probably be used for video conferencing (tried with Skype but the echoes drove me batty) or just keeping in touch with family members. But since none of my family members would probably dare step in front of a web cam, the latter is probably a lost cause.
Discovered via George and Liz. Sorry I missed the karaoke session.:-)
On another note, for some strange reason this message shows up in the output results of my del.icio.us daily blog post settings:
Allowed memory size of 8388608 bytes exhausted (tried to allocate 233472 bytes) in (yadda…yadda)
I googled for a solution and found one that required me to edit my htaccess file, which promptly took my entire site down. Now I’m trying this. The funny thing is that this only started happening with WP 2.3.2. I don’t have *that* many plugins, so they shouldn’t be the problem, should they?
Grrr.
…please do so. Now. You have been warned.
By default, the WP meta widget shows the login link for site admin and a link to WP.org. This bugged the heck out of me so I dug around (and Googled) to try and figure out what to do. I found out the solution and wanted to put it in this post, but for some strange reason WP is recognizing the code even when I use code tags. I guess there’s just too much code in there. The only thing I could think to do was to make a gif. The thumbnail is to the left. Dear lord. There has to be an easier way of doing this.
In any case, you’d like to get rid of the links in your meta widget here’s what to do:
- Navigate to wp_includes on your server
- Find widget.php
- Save a backup copy of widget.php to your computer (name it something like widget_org.php)
- Take out what I have starred in the gif (click on the thumbnail)
- If you use line numbers, I believe the ones you need to take out are 476, 477 and 480
You should be good to go after that. If not, upload the backup file to wp_includes and change the name back to the original one (widgets.php).
