David S.
14p11 comments posted · 2 followers · following 0
14 years ago @ Dave’s Lab | A c... - qHighlight! - The Firs... · 0 replies · +1 points
14 years ago @ CodaMonkey - Syncing a Remote and L... · 1 reply · +1 points
Sorry I couldn't bring better news :(
14 years ago @ CodaMonkey - Syncing a Remote and L... · 3 replies · +1 points
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 :)
14 years ago @ CodaMonkey - Syncing a Remote and L... · 0 replies · +1 points
14 years ago @ CodaMonkey - Syncing a Remote and L... · 1 reply · +1 points
14 years ago @ CodaMonkey - Syncing a Remote and L... · 2 replies · +1 points
14 years ago @ CodaMonkey - Syncing a Remote and L... · 0 replies · +1 points
15 years ago @ Dave’s Lab | A c... - SuperGenPass: Clicking... · 0 replies · +1 points
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 :).
15 years ago @ Dave’s Lab | A c... - Backing Up Any Email A... · 0 replies · +1 points
15 years ago @ IntenseDebate Blog - IntenseDebate Is Getti... · 0 replies · +1 points