I made some decisions on conversions for Galaxycow (as you’ll see if you visited /blogs or some of the other blogs that haven’t reimported yet).
The biggest decision was changing from multiple disparate WordPress installs to a single WordPressMU install.
HOWEVER, I have discovered that my old permalinks used the screwy /index.php/ workaround to get you to a page. Looking over at Aqua’s blog, I discovered the old permalinks were that way… and this blog wanted to get rid of that. I’ve put the /index.php/ silliness back in to avoid breaking links to this site. Oh well.
So, I’ve decided Drupal just isn’t the way to go on the home page of Galaxycow.
I’m considering a “backpedal” of sorts and going with just something like RapidWeaver to create the website and maintain the podcasts, but it presents a bit of a problem. If I choose to open a forum or whatnot later on down the line, then that’s Yet Another Disparate Database. The WordPress blogs linked in from here are on their own separate databases and so would the forum. You’d be registering multiple times for this website.
Some of you who may be hitting the front page of Galaxycow (www.galaxycow.com) may have noticed that there’s a basic site up there with the ability to register. This shouldn’t surprise you.
I’ve been wanting to grow Galaxycow for some time, but I didn’t have a focus. I’m starting to develop one based around the ideas of several podcasts and a blogging/forum community for just about anything and everything. However, one thing that is set up right now that I do not like is the separate blogs.
So this morning, I decided to try to get to the bottom of what causes iChat AV to fail with my router. I was testing with my stepfather who also has a WRT54GS router (by Linksys).
I read on the Apple site that some routers break when using UPnP, but in general, they have a list of ports to forward. Since I’m planning on multiple Macs in the house, forwarding ports to a single system isn’t going to work for me. I disabled UPnP, then used a remote assistance session on my PC to do the same on my stepfather’s router. Then I returned to the Mac, fired up iChat, and bang, what do you know… that resolved it… without forwarding any ports. I can now have an iChat session with my Mac to my stepfather’s PC without issue.
I was pretty depressed to hear that Apple went ahead and proclaimed October as the month of Leopard. I was really hoping for June, but alas… I can understand if they need time.
I was listening to Macbreak Weekly tonight while exercising and I listened to the panel bring up the merits of the 8-core Mac Pro and… well, it just seems like for me, that’s just money not very well spent. I should set my sights back down to the 4-core level because I just won’t be pushing the machine that hard. With that in mind, I could do two Macs like we wished for $6,400. That’s probably way more reasonable in this day and age.
I’m just now starting to get into the powerful hacks that OS X offers via Automator and Applescript, but I just ran across this one that is just so sexy it’s not even funny.
There’s plenty of positive Apple spin to go around these days. It seems like every day that I look, there are prominent Windows journalists making the switch to Mac and encouraging others to do so. There’s a “vibe” in the air of change. Windows news sites that I frequent daily have not been the source of much excitement since Vista’s release. There is a very positive stock market buzz about Apple as well. There is so much that bodes well for Apple right now that it seems dreadfully easy for them to capitalize.
So, in the last entry I mentioned that a lot of people use the delegation feature in Exchange when their workflow and business processes could benefit from the use of sharing permissions instead. Why would it be useful for you to implement this workaround? Let’s clarify a little bit.
Many companies today are finding the RPC over HTTPs (a.k.a. Outlook Anywhere in 2007) scenario to be quite an interesting deployment method. I’m here to tell you, battle scarred and worn… I’ve deployed RPC over HTTPs as the primary topology for an Exchange environment. We’re talking 80% of the population. It presents some unique challenges, but we won’t go into all of those here and now. Ask me later sometime about non-paged pool memory and I’ll share horror stories with you.
There’s a monster post on the Exchange blog about problems with assigning delegates and/or updating distribution list memberships from the Outlook client.
I can say that we’ve definitely suffered from some of the goofy issues in this article. One item they do not cover is that as a general rule, you should not be assigning more than 4 delegates to your mailbox if you can help it. All too often, people use the delegation feature to work through a business process that can be solved with simple sharing permissions.
Not too very long ago I came to the realization that in the past, I didn’t use computers to do much. It could be that I didn’t really have much to do aside from playing games and writing the occasional resume’, but as far as productivity goes, I’d never quite been in a job that required me to use the computer to be productive, in a way of speaking. I was never required to pump out much in the way of Excel spreadsheets, or Access databases. I was never required to do much more than the occasional Word document.
