Being a “computer person” these days is a very stressful business. Forget about angry customers, missed deadlines, unreasonable bosses and co-workers, shrinking wages, etc. Those are just things you get used to after a while.

Dspam filters spam with the best. In my installation, it stops over 98% of all spam: I’ve only had one false positive in the last year, and that was a message to the Dspam list that contained a real spam!

Administering Dspam is a breeze. No rules to configure, new users can automatically benefit from a global dictionary and quarantine management is simple. But getting a Dspam quarantine set up the first time, without losing any email, can challenge the most seasoned mail administrators.

If you are responsible for maintaining an internet-connected mail-server, then you have, no doubt, come to hate spam and the waste of resources which comes with it. When I first decided to lock down my own mail-server, I found many resources that helped in dealing with these unwanted messages. Each of them contained a trick or two, however very few of them were presented in the context of running a real server, and none of them demonstrated an entire filtering framework.

SMTP is an abbreviation for “Simple Mail Transfer Protocol”, and is the standard internet protocol for sending email from one system to another. Although the word “simple” belies the inherent complexity of the protocol, SMTP has proved to be a remarkably robust, useful, and successful standard. The design decisions that made it so useful, though, have given spammers and infectious code an easy way to spread their unwanted messages. Its recent evolution reflects the tug-of-war between those unsavory players and the administrators who want to protect their systems and their users.

In the online world, security plays a role in all online activities. Passwords are the most commonly used method to limit access to specific people. In my previous article I discussed assessing the relative value of systems protected by passwords, and grouping passwords across locations with similar trustworthiness.

In a nutshell, don’t bother creating and remembering strong passwords for low value systems, and certainly don’t use the same passwords for low value systems that you use in high value systems.

In his speech at aKademy, Bernhard Reiter of the Free Software Foundation Europe (FSFE) both celebrated Software Freedom Day and reminded the KDE community of what freedom in software means. The FSFE was founded in 2001 to promote and defend free software, and to coordinate national free software organizations, throughout Europe.

There is a company in the UK that provides Unix shells to their users: Mythic Beasts. They offer fantastic service to people who need a shell account on a very fast server, and don’t want to fork out silly amounts of money. Let’s talk to Chris Lightfoot, one of the company’s owners.

TM: Who is behind “Mythic Beasts”? How did everything start?

The $3.6 billion worldwide market for IT management software is ripe for competition from free software. Leading products from HP, CA, BMC and IBM are overkill for the vast majority of the market. Licensing costs can reach seven figures, and deployment and system administration costs are several times that. Not to mention that these products are widely known to be inflexible, monolithic and difficult to use.

One comment: No wireless. Less space than a nomad. Lame.

Rob “CmdrTaco” Malda introduced the iPod to the Slashdot crowd with a statement rivalled only by Bill Gates’ quip “640 KB should be enough for anybody”.

Since that post in 2001, Apple’s iPod quickly became one of the most successful products in consumer electronics history. While its success largely derives from its “hip” factor and stylish design, the iPod’s integration with the iTunes music application and the iTunes Music Store has made the device a favorite among music listeners.

Venezuela (November 15, 2004 to November 22, 2004)

I spent a week in Venezuela, giving a speech and some interviews at an event which invited speakers from all across Latin America. During the event, the state oil company PDVSA announced its decision to switch 100% to free software. Their decision is not based on convenience or cost; it is based on sovereignty.

During the event, the state oil company PDVSA announced its decision to switch 100% to free software. Their decision is not based on convenience or cost; it is based on sovereignty

We have written this manifesto always wishing to unfold the concept and practice of free/libre and open-source. We wanted it to stretch out so that it might take us in new directions. To start off with, we were sure that the practice of non-proprietary software code production was not a narrowly technical or economic affair, but something that was always also socio-political.

Free software, also known as open source, libre software, FOSS, FLOSS and even LOSS, relies on traditional software legal protection, with a twist. Semantics aside (I will describe all the above as “free software”), the tradition at law is that free software is copyrighted, like most other software, and is not released, unbridled, to the public domain. Authorial or ownership rights can be asserted as with any bit of proprietary software.

It is a common assumption that companies who distribute free software will promote it, leaving the community to concentrate on the meat of the project itself (including code, documentation, graphics, and so on). But this is untrue; companies generally devote few resources and little expertise, leaving communities to fend for themselves in the big scary world of media and marketing.

In this article, I respond to Robert McHenry’s anti-Wikipedia piece entitled “The Faith-Based Encyclopedia.” I argue that McHenry’s points are contradictory and incoherent and that his rhetoric is selective, dishonest and misleading. I also consider McHenry’s points in the context of all Commons-Based Peer Production (CBPP), showing how they are part of a Fear, Uncertainty and Doubt (FUD) campaign against CBPP.