Chances are you’re familiar with both StumbleUpon and Digg. Have you ever wished it would be as easy to Digg posts as it was to Stumble from site to site? Well, now it can be. Sub Digger Plus wasn’t created by Digg (so it’s uncertain if using it will get your Digg account in trouble), but it’s a great way to make keeping up with your friends’ Digg submissions. Not only is this tool helpful, it’s not difficult to use. In fact, if you know your Digg username, that’s all you need to enter to start using the tool (which works on Internet Explorer, Firefox, and Chrome browsers.)
With no plugins to download or software to install, Sub Digger Plus makes it simple to easily check out Digg submissions from your friends. After entering your Digg username, you’ll go to a screen with a toolbar on the bottom. Your friends’ submissions will load in the top of the screen. All you have to do is click one button to see the next submission. There’s also a handy list view that’s sortable. Depending on your personal preferences, you can choose to sort the list by Date, Diggs, Title, Submitter, Topic or Read (and any of these options can be sorted in ascending or descending order). This makes it super easy to see what your friends are doing at Digg, and provides you with the opportunity to create a really personalized Digg experience.
WordPress is one of the most popular open source blogging platforms. Unfortunately, this also seems to make it a popular target for hackers. While keeping your WordPress installation up to date can prevent a lot of potential security breaches, that’s not a guaranteed way to stay safe. Today, I’m going to cover a few steps you can take to give yourself extra layers of protection against hackers and evil robots.
Although these first steps may seem extremely basic, it’s always good to be reminded of the fundamentals. A great example of this was the Twitter happiness fiasco that occurred a couple of months ago. While it did have some entertainment value, it also served as a reminder that even the most basic security measures can be overlooked if you aren’t proactively taking steps to be more secure. Here are a few lessons that can be learned from that fiasco:
Don’t use words from the dictionary for your password
For example, passwords like password or happiness.
Most brute force attacks attempt to gain access by trying a prearranged list of dictionary words. If you choose a password that is not a word from the dictionary, you won’t leave yourself open to this type of attack.
Don’t use passwords that aren’t strong
For example, all lowers case with no numbers or other characters.
What exactly makes a password strong? Strong passwords have the following characteristics:
- Lengthy: Each time you add a character, your password becomes exponentially more difficult to guess.
- A combination of letters numbers and symbols: The more characters the better
- Uses both upper case and lower case letters
- Use a password that is easy for you to remember but difficult for others to guess
Microsoft has some more detailed tips on how to create strong passwords that are easy to remember but difficult for others to guess.
Whatever you do, don’t allow UNLIMITED login attempts!
In the case of the Twitter fiasco, the hacker actually launched an automated brute force attack which ran overnight while he was sleeping. The WordPress Limit Login Attempts Plugin is an ideal way for WordPress users to protect themselves from such brute force attacks. It works using both IP addresses and cookies. It can be set to notify you via email when someone has been locked out due to four failed login attempts. The first time four failed attempts occur the user or potential hacker is locked out for twenty minutes. After the next four failed attempts, the lockout last for twenty-four hours. These are the default settings, but they are fully customizable.