The only screencasting software that doesn’t crash in Ubuntu Hardy

I’ve spent a lot of time trying to record some screencasts for GLM, but every screencasting software I tried crashed under Ubuntu Hardy (and Gutsy too):

  • XVidCap: The workaround is supposed to be disabling sound, but didn’t work.
  • RecordMyDesktop (plus its two front-ends): Crashes with no error message. From time to time I was able to record videos.
  • Istanbul: Crashes if you select a window to be recorded.

So, the only solution is to install a newer version of Istanbul for Debian:
http://ftp.fr.debian.org/debian/pool/main/i/istanbul/istanbul_0.2.2-4_i386.deb
or, if you have a 64-bit box, http://ftp.fr.debian.org/debian/pool/main/i/istanbul/istanbul_0.2.2-4_amd64.deb

After making the appropriate bug reports, I can finally start recording the screencasts with Istanbul!

PS: Forget about the above. That Debian package doesn’t work either. I’m installing KDE4 to check whether I can record the screencast with it; I think I saw such an option when I tried it out.

PPS: The KDE4 built-in screencasting component uses a weird format (cps?) which cannot be opened with VLC, Mplayer nor Kaffeine (but there’s a dirty workaround). Anyways, it records the whole screen and I just want to record a single window.

PPPS: I’m not alone.

I’ve seen the light: GNU/Linux Does Not Matter That Much

We freedomware advocates think that switching to a Freedom-respectful operating system (usually GNU/Linux) is the most important step when switching to freedomware, and therefore we focus on promoting these systems (myself included). However, I’ve found out that it does not matter that much.

The first and most important step when switching to Freedomware is using formats and protocols defined as Open Standards, even under a Freedom-trampling system like Windows: Vendor lock-in is only possible by means of closed standards. They are the stone corner of the non-free software industry.

Why those who know about Freedomware, and support the idea, don’t make the switch? Aside their inability to follow their thoughts (the games excuse is included here), because switching from Windows+Office+MSNMessenger/Etc to GNU/Linux+OpenOffice.org+Pidgin+Etc seems like a huge step, only made by adventurous souls.

The most important things for them, their information and communications, are already locked-in, tied to a single vendor. Encouraging them to switch to a freedom-respectful operating system is an unwise recommendation, if you know they still rely on closed standards:

  1. If you say that they won’t be able to use the programs they were used to, but their free alternatives, you will fright them. Not to mention what they’ll think when they know that their MP3s, WMVs and .doc documents won’t play nice, and that their MSN Messenger sucks under GNU/Linux.
  2. If you help them to keep their files under closed formats and communicate through closed protocols, then, why on the earth do you want them to use a free operating system? Using a free operating system simply means that most of your software is free. It seldom means that the user is reluctant to use Freedom-trampling software, closed formats and/or closed protocols, again. Quick demonstration: Take a look at any community of the easy-to-use distros and you will find that these standards are widely used among the majority of these users (although this doesn’t mean that Gentoo users, for example, are all disciples of the Church of Emacs).

The only way to make safely the switch to a Freedom-respectful computing environment, with no turning back, is by getting rid of closed formats and protocols, before switching to a free operating system. Windows-GNU/Linux dual boots wouldn’t be necessary anymore.

These closed standards have always been a top-priority for non-free software vendors, unlike for us. Closed standards represent the Achilles’ heel of the non-free software industry. We must hit them there! Pay attention to this excerpt from a memo sent by Aaron Contorer, Microsoft general manager for C++ development, to Bill Gates:

“The Windows API is so broad, so deep, and so functional that most ISVs would be crazy not to use it. And it is so deeply embedded in the source code of many Windows apps that there is a huge switching cost to using a different operating system instead…
“It is this switching cost that has given the customers the patience to stick with Windows through all our mistakes, our buggy drivers, our high TCO, our lack of a sexy vision at times, and many other difficulties […] Customers constantly evaluate other desktop platforms, [but] it would be so much work to move over that they hope we just improve Windows rather than force them to move.
“In short, without this exclusive franchise called the Windows API, we would have been dead a long time ago.”

OK, that’s the root problem, but what’s the solution!?

We must put more effort into making people switch to open formats and open protocols, than the effort we put into encouraging them to switch to a freedom-respectful operating system like GNU/Linux. This is, our goal should be that people will get rid of closed formats and protocols before switching to a free operating system. Don’t expect them to make the switch after installing the free system! Or at least don’t get your hopes up if you ignore this (take the longer yet save path!).

The above might seem obvious to you at this point, and you might wonder, how are we supposed to do so effectively?

My proposal

We have to carry out three tasks to reach our goal:

  1. First and foremost, make people worry about the formats and protocols they rely on;
  2. Make it really easy for people to switch to unconstrained formats and protocols, under the current operating system, but also warn them that everything won’t be completely solved until they throw the non-free system away;
  3. And finally, make people switch to a freedom-respectful operating system, like GNU/Linux.

(Notice that nowadays most of us start with task #3, then some of us go further and make #1, but nearly we all forget about task #2)

These tasks should be performed separately and harmoniously, with one project for each of them. The good news is that we won’t have to start from scratch, as there are some existing efforts: GNU/Linux Matters is going to develop Unconstrained.info, a project that would meet the requirements of task #1, and it also maintains GetGNULinux.org, the project that already meets the requirements of task #3.

The second task is by far the hardest one. The solution, in my opinion, is a software suite made up of the following well-integrated modules:

  1. A package manager, like those for GNU/Linux: It will make it easy for people to get started with Freedomware applications that support unconstrained formats and protocols. These programs must be stored on special repositories, so that we could disable support for constrained standards by default. This manager would only install Freedomware required to make the switch, excluding useful free add-ons for the operating system: Our goal is not to make people feel comfortable with their freedom-trampling operating system. Only the best Freedomware packages will be available, with no alternatives: It would make no sense to include both OpenOffice.org and Koffice (for example), we don’t want people to experiment with the free alternatives, just that they make the switch.
  2. A file format converter: An extremely easy to use Freedomware application to convert any file stored with a closed format into one stored with the best-suitable open format, preferably/optionally deleting the former file after the conversion. When the suite is being installed, it must configure the system to open those constrained-formats-based files with this converter.
  3. A Instant Messaging Migrator: The hardest to make module. It will help people migrate to open protocols such as Jabber or SIP. It would create a gratis Jabber account with any provider. Then, if allowed, it would let people’s contacts know that they are making the switch to an unconstrained and better messaging network (encouraging them to make the switch too). Finally, it would configure the pre-selected free IM client accordingly, making it ready to use.
  4. A tutor: A program, similar to a Help Center, that would advice people on unconstrained formats and protocols. It would provide guidance throughout the migration process. It would make sure that people keep in mind that they should switch to a free operating system once they get used to the new standards.

This suite must meet these requirements:

  • Be multi-platform: It must run on all the mainstream operating systems, including GNU/Linux (yes, haven’t you noticed the amount of GNU/Linux users tied to constrained formats and protocols?).
  • Be multilingual.
  • Be extremely easy to use.

Once Unconstrained.info and the liberation suite are ready, together with GetGNULinux.org, the final touch for us to be effective will be Animador.

In an ideal world…

… Organizations such as Mozilla, the FSF and the FFII will support GNU/Linux Matters with tasks #1 and #3, and the GNU project will take over task #2, with the support of all of us.

If everything fails, I’ll try my best to take over task #2 on behalf of GNU/Linux Matters.

On my part…

… I’ll try to make GNU/Linux Matters change its vision, according to this blog post.

On your part…

… This all sounds so beautiful, right? Well, we need you! And please don’t forget to comment on this blog post and spread the word about it if you find it useful.

PS: Got something to say? Talk about it on NXFD!

The Big Failure of the FSF

Explaining what freedom in computing is about, is also talk about the FSF and/or the GNU project; they’re nothing less than the flagship of the free software movement and they’ve made huge steps toward freedom in computing, but they have missed a key point: If the average computer user is not on our side, we’ll get nowhere.

Ours is a wonderful, well-founded philosophy, just like many others. So why would a friend of mine try to find out what yet another philosophy is all about? After all, there are many things that hurt societies and everyone doesn’t have enough time to support/learn about everything that’s going wrong nor how to solve it. Therefore, our most important concern must be how to approach people.

Getting people’s attention is even more important than trying to develop a free BIOS or a free flash player. The industry offers technology and people accept/reject it, this is how things work and this is why having people on our side is the way to go (instead of begging the industry for mercy). There would be no need to develop a free alternative to the Google Earth client in a Free Software-aware society, for example.

What’s worst, the Free Software Foundation doesn’t even seem to have a plan to solve this situation, after 23 years spreading the word about Freedom-respectful software: GNU.org is supposed to be the main resource on Free Software, but it is not aimed at everyday computer users. Let’s have a look at GNU.org:

  • A nerdy introduction:

    What is the GNU project? The GNU Project was launched in 1984 to develop a complete Unix-like operating system which is free software: the GNU system. Variants of the GNU operating system, which use the kernel called Linux, are now widely used; though these systems are often referred to as “Linux”, they are more accurately called GNU/Linux systems. GNU is a recursive acronym for “GNU’s Not Unix”; it is pronounced guh-noo, approximately like canoe.

  • It’s overloaded: It’s full of links everywhere and they mix resources for people to know what Free Software is all about and those for potential volunteers.
  • It provides no guidance on how to make the switch to a free computing environment.

It’s definitely not the place I’d recommend my friends to learn about Free Software, as you only get one chance to make a first impression and I wouldn’t waste it that way.

I’ve talked with Stallman about this and he knows they haven’t been approaching everyday computer users the right way (he told me many people say that it’s not easy to know how to make the switch by following GNU.org and they wanted to change that). Anyways, redesigning the whole GNU.org website wouldn’t be enough, as there are other features of the FSF that make it harder to have the average computer user on our side:

  • Their strictness: On one hand, they expect people to make the switch to a fully free computing environment in one go by only recommending fully free distributions, but we all know that people fear unknown things, so if you spread the word about the wonderful Free Software philosophy and the only option you give to make the switch is using a fully free operating system, you are making it harder for people to take Free Software seriously because there must be a trasition period. On the other hand, they put much effort into making people understand that “GNU/Linux” is the right name of the operating system.
  • Lack of interest in the average computer user: The FSF has only been focused on two important, but not-so-useful target audiences: Techies and politicians. Techies are definitely useful to make software, but how could you rely on techies to do marketing? Politicians, on the other hand, rule a nation/state/whatever, but they go and come, so you shouldn’t rely on a given politician/party; focusing on the population is a safe bet, though.

However, it’s very unlikely that the FSF is going to change and I understand their position and their crucial role in the free software movement, so I’ll keep supporting them. But then, a fork organization is urgently required to meet the need for an effective advocacy for Freedom-respectful software among everyday computing users and this is why GNU/Linux Matters exists.

PS: This blog post’s aim is not to blame the FSF and promote GLM, but to express how disappointed I’m in the poor effort to spread the word about free software on behalf of the Free Software Foundation.

PPS: This blog post does not represent the position of GNU/Linux Matters, just like the rest of the website.