You may have heard of the Web of Trust plugin for browsers. This product is marketed as a "Safe Browsing Tool", and supposedly improves the security of the web by allowing users to view the rating of a site before even clicking on it (as it places an icon next to all links), as well as other measures such as an icon next to the address bar, and a popup warning you if you try to visit a site that does not have a good rating.
Archive for Abridged
It's been a long time since I've posted anything here. We've been busy - and perhaps I've been playing a bit too much Guild Wars 2. ;)
Recently I added a third screen to my system, and this only made the existing multi-screen issues I had with KDE even worse. Finally, I decided to do something about it, hunting down each issue one by one and fixing it. This post is just to serve as a guide to fixing these problems.
Whenever you work with other people long enough, you'll no doubt encounter elitism. This is a given since it is a part of Human nature. However, not all elitism is bad, and its important to be able to recognise the difference.
Error handling is serious business. Or at least, this is how a lot of programmers see it. For decades, programmers have handled program errors in a wide variety of ways, from error levels, to error codes, macros, exceptions and beyond, all based upon the core concept of detecting an error and then handling it. But this process may be inherently flawed, because it is a reactive, not proactive formula that ultimately places a huge burden on software design.
I'm not usually the type of person to plug something. I tend to let everything just go its own way without interfering, if that makes sense at all. Because of that, I'm usually at the sidelines just watching things happen. But lately I've begun to realize that if I'm passionate about something it might do others some good to fill them in on it as well. Because if I enjoy it, someone else might too.