Glad you liked it! Yes, it's very helpful when people post code files online and then you click on them to open in another tab, but the browser renders it as plain text. That's what I use it for especially. Also, if you ever need advice, hit me up on Wave and I'll be glad to help in any way.

Yeah, so I hear what you're saying. Unfortunately, syncing the actual publishing of posts between two Wordpress installations is NOT easy. I've done this myself and I've never gotten it to work. WP has some funky magic going on in its database where if you make an exact copy on two machines, one doesn't run correctly. I have no idea why this is, not being familiar with the internal architecture of Wordpress. I know this doesn't exactly answer your question or solve your problem, but just know that you shouldn't expect it to just work without a little bit of work. I'll try to do some Googling myself and I encourage you to do the same, but basically syncing the content of two WP installations is no trivial matter.

Sorry I couldn't bring better news :(

Hi Justina! Well, just in case it wasn't completely clear (though I see you seemed to figure it out), here's the deal. The database information on MAMP on the local machine and the db info on the remote host share nothing in common (by default). There is *no* reason that they be similar in the slightest. I'm just a coincidence much of the time :). As you probably know, 'localhost' is usually the default connection address for many web hosts, though not all. This means that PHP, the language that powers Wordpress, will connect to a MySQL database on the local machine, not one remotely. Many web hosts, in fact, ask you to enter a separate URL for the address of the DB server, like MediaTemple for example. This is actually good practice, because any real web application has the DB and the code running on two separate servers.

Anyway, for the particular web host I used, 'localhost' was where the database resided. Also, as you would expect, the address for the database running MAMP was also localhost. However, the difference was because MAMP requires you to (by default) access MySQL on a non-standard port, which means you need to type in localhost:8889 to get to it. Also notice that the same is true to access the local sites because you have to go to localhost:8888 in your browser to get to them. It could've been completely possible that the MAMP database info could've been 'localhost:9341' and the remote one '19.2.121.239:3231', i.e. the IP address 19.2.121.239 over port 3231 (note: I just made those numbers up :)). So, really, their difference is a neccessity and their similarity is only happenstance.

PS Hopefully, I don't sound patronizing. I just wanna make sure you get the whole picture and those who read these comments later do as well :)

You mean like SSH to the web server and then use command line stuff to copy over files? I could surely show you that, but I must admit it kind of sucks, having done it for months for some research I did in college :). GUI Clients are always better for that, but I'd be happy to give it a go.

Glad to hear you liked it! I used iShowU for this screencast, cause it was pretty simple though I also own iShowU HD Pro. Other great screencast software includes Jing Pro (although only 5 minute at max) and Screenium. However, the king of all of them is ScreenFlow on the Mac, but it's like $100, so unless this project starts making me money someday, that's not gonna happen :)

Glad to help, Jeremy. I enjoy making screencasts when I can and I really wanna launch this site fully when I get the chance. Best of luck!

Thanks so much Adam! Glad you enjoyed it. I'll look into it

Well, the first thing is that a key logger is a whole different kind of scenario, because they can grab anything you input. So it's not really a failing of SuperGenPass. However, the good thing about SGP is that after you enter the password into the popup, you then double click on the password entry field. That password is never typed, unless you actually type it out manually, so keyloggers don't get it. Now, a very sophisticated malware program would detect that you're using SGP and then be able to guess, so you're correct in that sense. It does rely a tiny bit on security through obscurity.

The easiest way around this whole fiasco, quite frankly, is just to do what most of us do, which is just use the same few passwords and swap them between sites. However, if you do this, but use those same passwords which SuperGenPass as the generator, then you're guaranteed a least a little more security. Also, you could change up the default length of the password depending on which site you use, just so that people can't gain more insight into your passwords from length. If you're really cautious, you could always use a couple of super securely generated passwords from maximum entropy such as those found here: https://www.grc.com/passwords.htm.

To be honest, this solution is imperfect and I would not use this to generate a password for my bank account or PayPal or anything really serious. But for most things, I think this is a great solution. So many password attempts are brute force and brute forcing a password like the ones SuperGenPass does is nuts. In a few years it'll be obsolete for sure, as processors get faster, but till then I think it's great.

PS Sorry about not getting back to you sooner, when you're used to no one reading your blog, you tend to forget about it :).

Hi, thanks for the reply! Yeah, that is a good way to do it as well. The only problem is that if your ISP doesn't allow you to forward only copies of incoming email, then you are forced to move completely to Gmail. This is great for me (and frankly what I do with my other non-Gmail emails) but if I wanted to continue using my ISP's email with Outlook, for example, then I couldn't because I'd be forced to use Gmail. I love Gmail and its interface but I know many folks who don't. Still thanks for the great suggestion!

Cool, just heard you guys on net@nite and installed it on my blog. I really like it so far.