Bye bye LTSP and KMail

I upgraded my LTSP installation and it stopped working again. After fixing some problems I got stuck with another one. Googling didn’t help and LTSP documentation seems to be reducing rather than expanding through the time. I’m no longer going to waste my time to get running underdocumented software with tricky dependencies so I’ve abandoned the LTSP model. Fortunately hardware didn’t make that much progress during last ten years so the old computer can still run current software directly.

When reinstalling the old computer I abandoned KDE desktop on my users’ accounts and replaced it with Xfce. Xfce is likely to be less resource demanding and easier to use. The replacement wasn’t without problems as KMail stopped working on the new installation. There were some Akonadi crashes and other problems and KMail refused to run completely on one of the user accounts. Again, Googling didn’t help, so I made another step in abandoning KDE applications. KDE is infamous for becoming quite complex without being appropriately robust and for becoming more complicated for its users. Although I still like and use some of its applications (KDM, digiKam, Okular) it’s better to avoid the rest.

However it wasn’t easy to replace KMail with another client. Such trivial features like reading incoming mail from mailbox or handling maildir format are not properly supported in some popular clients. I personally use Gnus which is an excellent client for an advanced user but it’s not suitable for my users. I ended up installing Balsa which seems to work acceptably so far. My users have just lost their contacts as KAddressBook couldn’t start as well and I haven’t found the data anywhere (was it lost?) — another reason to avoid KDE.

W3C and DRM

Yes, DRM technologies are defective by design. They make problems to legal customers, preventing them to use the content they paid for in normal ways like viewing or playing it on any device they own or using their favorite and trusted software. They are also exposed to privacy issues. On the other hand those who use illegal copies probably don’t care much about DRM, they can find ways how to break it or how to get a DRM-free copy and using it in any way they like. That encourages usage of illegal copies.

The only way I could use DRM content on my devices, if it is possible at all, is to install and run untrusted proprietary code on the devices. I usually refuse to do such things so I don’t buy anything with DRM. Still, there is sometimes DRM content I’d like to buy and use if I could.

So the purpose of DRM is questionable and DRM makes problems to fair users (unlike unfair users). Still some circles insist on using it and other ones profit from it by delivering DRM technologies. There is an argument that those circles need to handle DRM content on the Web anyway and thus it is better to do it in a standardized way. W3C encourages such a standardization by working on the Encrypted Media Extensions (EME) proposal.

The problem is that by mandating a defective and harmful technology as a Web standard the technology gets officially promoted and encouraged. That shouldn’t happen. If someone wants to push a defective technology which can’t be run universally on Web enabled devices, let he promotes it on his own, without an official mandate from W3C. W3C should propose universal standards accessible to all Web users instead of inviting the use of defective and harmful technologies.

Things seem becoming worse now. Despite the opposition to the EME proposal, its first public draft has been published recently and the work on it continues. Technical work on the standard and discussions about its sanity are kept separate which makes some sense but on the other hand I suspect the DRM proponents are simply not going to get disturbed by the opposition. They could maintain their pace and make the proposal ready for approval.

If you haven’t already done so, please consider taking some action about the issue. The FSF‘s campaign Defective by Design may be a good starting point, including signing the petition. You can also look at W3C EME specification and restricted media mailing lists. By ignoring the problem we will continue to face all the problems with viewing and playing crippled content on the Web, but this time mandated by an official policy.