I've got episode 2 of my new podcast Sound of History online. It's been really interesting to find these old recordings. For this episode, I found Kennedy's famous 1963 speech in West Berlin. I keep being struck with what an amazing orator Kennedy was. It is quite the captivating and amazing speech. Reagan's speech to West Berlin in 1987 is also in this episode. It's three times longer than Kennedy's, and probably less inspirational, but still an interesting listen. Next week I'm going to have one of the forgotten opposition speeches, trying to argue against Reagan. Also some good material out there from that perspective. In other news, ourmedia.org is being terribly annoying. It's much easier to upload to archive.org directly. I don't know why I ever bothered with ourmedia.org (or why anyone does, really).

Today I've rewritten most of my "laySVN" layered subversion tool. Tests had shown that most of the time was spent calling the "status" command of the underlying subversion client. This is probably due to locking, and the workaround is pretty simple: avoid calling it on single files, instead run it on the whole repository at once. This of course requires major changes to the code, so I've started a rewrite. I've already applied for a alioth project for it, I'll make the source available via svn.debian.org soon. "Layered subversion" means that you basically checkout multiple subversion repositories on top of each other. A file found or ignored in an "upper" layer will not be checked out in lower layers; ignoring a file in a layer will effectively "hide" it if it were in lower layers. This is an interesting alternative to branching. In branches, you have to "carry forward" changes from one branch to other branches. The base case - merging changes from a "lower" layer into an "upper" layer is usually quite easy. The other direction can get quite messy however. Assuming that multiple files were modified in the checkout, how are you going to commit these changes to the correct branches? Basically you'll have to commit the files to the correct branches, then do the merging magic. Along comes laySVN, where this common usage pattern is much easier. Changes will automatically be committed to the highest "layer" the file is in. A checkout will update the file to the version of the "highest" layer. The only case which is a bit more complex is when you want to make changes to a file on a different layer. Then you actually have to "add" the file to the appropriate layer. Not really difficult either, is it? A different name for "layered subversion" would probably be "difference branches", which are very similar.

Warning: Very long post ahead. You have been warned! What? Tor is a Free Software project (revised BSD license), developed by Roger Dingledine and Nick Mathewson, which creates an infrastructure for anonymous TCP communication. From the project website:

Tor is a toolset for a wide range of organizations and people that want to improve their safety and security on the Internet. Using Tor can help you anonymize web browsing and publishing, instant messaging, IRC, SSH, and other applications that use the TCP protocol. Tor also provides a platform on which software developers can build new applications with built-in anonymity, safety, and privacy features. Tor aims to defend against traffic analysis, a form of network surveillance that threatens personal anonymity and privacy, confidential business activities and relationships, and state security. Communications are bounced around a distributed network of servers called onion routers, protecting you from websites that build profiles of your interests, local eavesdroppers that read your data or learn what sites you visit, and even the onion routers themselves.

Tor also allows you to set up and/or use a so-called Tor hidden service, i.e., a server which offers some service (a website, ssh access, or similar) without revealing its IP to its users. Why? Why would you want to use Tor? Well, because you probably don't want anybody (neither state agencies, nor companies, nor "hackers", nor any other individuals or groups) to be able to record, analyze, and (ab)use information about your web browsing habits, or any other communication habits. For instance, you don't want Google to have a complete search-profile of you, which — even worse — might some day get in the hands of other parties. In the days of massive data retention you don't want all your electronic traces to be recorded, stored for ages, analyzed, and data-mined for dubious reasons and with even more dubious results and false conclusions drawn which might negatively affect you. If you're a human rights activist in China, you want anonymous communication. If you're a whistleblower, you want anonymous communication. The list is endless. For securing your communications, so that nobody is able to sniff your emails, your chat messages, your passwords, your private documents and conversations, you use encryption. For communicating anonymously you can use Tor. Combine both, and you have secure and anonymous communication. In case you're wondering whether criminals might abuse Tor, read the Tor Abuse FAQ. Short answer: yes, but if you're willing to break the law, you already have anonymity (open access points, stolen/prepaid mobile phones, etc.). You don't need Tor to do bad things if you're a criminal. If you're one of those horrible "oh, but I don't have anything to hide" guys, consider this: Say you have a drug/alcohol problem and want to visit an anti-drugs/anti-alcohol website or forum for help. Would you want the whole world, your neighbors, your co-workers, your boss, to know that, or would you rather want to keep that a secret? Say you have AIDS and want to get information on the web? Or, to make the example even more dramatic: Would you want some random guys to be able to watch you while you fuck your wife? No? So you have something to hide after all, right? My point is: Everyone has something to hide, even more, it is a basic human right to have the ability to hide something. It's called privacy. How? Tor implements a form of onion routing to, basically, push encrypted data through multiple Tor nodes (servers), before it reaches the final destination (e.g. a website). The result is that neither the website owner, nor a local eavesdropper, nor any single Tor server knows who requested that specific website, hence you are communicating anonymously. For more technical details, read the Tor overview and the Tor documentation pages. In order to use Tor, you have to install and run a local Tor client/daemon (this is not necessarily a Tor server!). On Debian, type apt-get install tor, on other systems you can get the respective binary packages or download the sources and compile Tor yourself. Usually Tor is used together with Privoxy, a configurable HTTP proxy which sanitizes your web-browsing experience by removing nasty banner ads, pop-ups, JavaScript, webbugs, cookies etc. etc. So: apt-get install privoxy. After installing and starting Tor and Privoxy, you can now configure your webbrowser to use Privoxy as an HTTP proxy (see below), and Privoxy will in turn use Tor to anonymize your communication if you add "forward-socks4a / localhost:9050 ." to your /etc/privoxy/config. Anonymizing various applications Most (but not all) of the following information is also covered in the very useful Torify HOWTO in the Tor wiki (I will add the missing information there, ASAP). As I'm pretty paranoid, I have checked every single of these configurations with Ethereal to ensure that the traffic is really anonymized. However, if you are paranoid, you shouldn't trust me, but rather test this stuff for yourself! Warning: DNS Leaks:
The biggest problem with many applications is that they leak DNS requests. That is, although they use Tor to anonymize the traffic, they first send a DNS request untorified in order to get the IP address of the target system. Then they communicate "anonymously" with that target. The problem: any eavesdropper with more than three brain cells can conclude what website you visited, if they see that you send a DNS request for rsf.org, followed by some "anonymous" Tor traffic. The solution: use Tor together with Privoxy, that prevents DNS leaks. Many non-HTTP-based applications are usually torified using a small tool called torify (e.g. by typing torify fetchmail), but often this approach has DNS leaking problems, see below.

• Webbrowser: Firefox, Mozilla, Galeon, Konqueror, ...:
  Most browsers can be torified by using Privoxy as an HTTP(S) proxy, i.e. using 127.0.0.1 as proxy host and 8118 as proxy port.
  For example, to torify Firefox go to Edit -> Preferences -> General -> Connection Settings -> Manual proxy configuration and configure:
  HTTP Proxy: 127.0.0.1 port 8118
SSL Proxy: 127.0.0.1 port 8118
FTP Proxy: 127.0.0.1 port 8118
SOCKS v5

  For Konqueror, go to Settings -> Configure Konqueror -> Proxy -> Manually Specify the proxy settings -> Setup and configure:
  HTTP Proxy: 127.0.0.1 port 8118
HTTPS Proxy: 127.0.0.1 port 8118
FTP Proxy: 127.0.0.1 port 8118

  Warning: Although Privoxy doesn't support FTP, you should configure the browser to use Tor + Privoxy for FTP. By doing that, you get an error message when you try to access ftp:// URLs, but at least you don't send untorified traffic without noticing.
  Warning: Firefox's "Live Bookmarks" (RSS feeds) are a problem if you switch from a torified to an untorified state sometimes (by switching or enabling/disabling the proxy). Firefox periodically requests all the feeds you're subscribed to. If you turn off Tor + Privoxy usage, they will be requested non-anonymously, and you won't even notice it! Solution: remove all "Live Bookmarks", or never switch to untorified browsing.
• HTTP-based tools: lynx, links, w3m, wget, curl, ...:
  Most other HTTP tools, such as wget, can be torified by setting the respective values for the http_proxy and HTTP_PROXY environment variables. Applications which don't honor http_proxy probably have a configuration option to set the HTTP proxy.
  Add this to your ~/.bashrc or similar config-file:
  http_proxy=http://127.0.0.1:8118/
HTTP_PROXY=$http_proxy
export http_proxy HTTP_PROXY

  Warning: links is a notable exception here. It does not honor the http_proxy environment variable! However, you can add http_proxy 127.0.0.1:8118 to your /etc/links.cfg and/or to your ~/.links/links.cfg. Or go to Setup -> Network Options and do the same there. Or use the -http-proxy 127.0.0.1:8118 command line option.
• Instant Messaging: Gaim:
  Go to Preferences -> Network -> Proxy and configure this:
  Proxy type: Socks 5
Host: 127.0.0.1
Port: 9050

  Gaim doesn't seem to leak DNS requests.
• Debian: Apt:
  Setting http_proxy is enough, as apt-get honors the http_proxy environment variable. But you can also add this line to your /etc/apt/apt-conf:
  Acquire::http::Proxy "http://127.0.0.1:8118/";

  apt-get doesn't seem to leak DNS requests.
  Warning: This will only work for deb/deb-src lines in /etc/apt/sources.list which use HTTP, because Privoxy does not support FTP.
• RSS-Reader: Akregator:
  Which RSS feeds you are reading tells quite a lot about you, and it's probably an information some people or organizations would be very interested in, I imagine. So anonymizing your feed-reader is quite important, IMHO. Akregator (a KDE RSS-reader application) uses Konqueror internally, so if you have set Konqueror to use Tor + Privoxy as HTTP-proxy, Akregator is safe, too.
  Akregator doesn't seem to leak DNS requests.
• Podcast Client: iPodder/Juice:
  Got to File -> Preferences -> Network settings and configure this:
  Use a proxy server: enable
Address: http://127.0.0.1
Port: 8118

  iPodder/Juice doesn't seem to leak DNS requests.
• Secure login: ssh:
  In order to torify all your ssh communications (ssh, slogin, sftp, etc.), edit your /etc/ssh/ssh_config and/or ~/.ssh/config and add:
  Host *
ProxyCommand socat STDIO SOCKS4A:127.0.0.1:%h:%p,socksport=9050

  This requires socat, so: apt-get install socat.
  ssh doesn't seem to leak DNS requests.
  Warning: Simply using torify ssh does not suffice, it leaks DNS requests!
• Email: fetchmail:
  Properly torifying fetchmail is pretty ugly. Basically, torify fetchmail should be enough (one would think), but that leaks DNS requests! All tips offered in the Torify HOWTO suffer from this problem. The ideal solution would be to use tor-resolve (a small utility which resolves DNS requests via the Tor network, and hence anonymously) before fetching the emails, but I haven't found a good and simple solution for that. What I do right now is to hardcode IP addresses in my ~/.fetchmailrc config-file and then use torify fetchmail, which doesn't leak DNS requests. However, it leads to some ugly "fetchmail: Server CommonName mismatch: foo.bar.com != xxx.xxx.xxx.xxx" warnings.
  I always start fetchmail manually, often by clicking an icon in my IceWM toolbar. So I use the following line in my ~/.icewm/toolbar config-file:
  prog Fetchmail fetchmail xterm -e torify fetchmail

  Sometimes I invoke fetchmail from the command-line, too, so I have this alias in my ~/.bashrc:
  alias fetchmail='torify fetchmail'
Warning: Just for the record: torify fetchmail alone (i.e. used with hostnames in ~/.fetchmailrc) does not suffice, it leaks DNS requests!
• IRC: XChat:
  Go to Settings-> Preferences -> Network -> Network setup -> Proxy server and configure:
  Hostname: 127.0.0.1
Port: 9050
Type: Socks5

  Then make sure you check the "Use a proxy server" checkbox in the preferences dialog of the IRC server you want to use.
  XChat doesn't leak DNS requests.

You might also want to check out toraliases, a small shell script you can source from your ~/.bashrc file. It defines some functions and aliases which transparently direct the traffic of some (but not all!) programs through Tor. Applications which cannot easily be torified Anything not using TCP usually cannot be torified, as Tor only works for TCP.

• Non-TCP traffic from tools like ping, host, dig, nslookup, nmap, traceroute and lots more: as Tor only supports TCP, you're out of luck. However, you can safely use web-frontends such as dnsstuff.com over Tor + Privoxy (if they don't block Tor users, that is).
• whois: Although torify whois google.com leaks the DNS request for the whois-server (in this case whois.crsnic.net), it doesn't seem to leak the host you wanted to lookup. Can somebody confirm this? The safer method is to use a web-frontend, though.
• FTP: Although torify ncftp works, it leaks DNS requests! I haven't yet found a way to fix this (help is appreciated!). I also tried a few other FTP clients, without luck.
• GnuPG: Using gpg anonymously should work by using a proper http_proxy environment variable and by using a hidden Tor server as keyserver.
  Add this to your ~/.gnupg/gpg.conf:
  keyserver x-hkp://yod73zr3y6wnm2sw.onion
keyserver-options honor-http-proxy broken-http-proxy

  This works in theory. However, I noticed a problem: while gpg --recv-keys seems to work fine, gpg --refresh-keys leaks DNS requests! It seems GnuPG hard-codes the keyserver to keyserver.pgp.com in that case and leaks the DNS request for this domain name.
• Sending email (SMTP): Not sure how to do this with Tor. Many Tor nodes block SMTP per default. A better solution is probably Mixmaster/Mixminion.
• CVS, svn, Bittorrent/Azureus (untested HOWTO), usenet clients (pan, slrn), xmms: TODO. Haven't checked, yet.

Pitfalls to be aware of

• Rule #1: Don't spoil your anonymity by being stupid!
• IRC: Don't use nicks which hint at you, such as your real name, real-life nickname, acronyms which are known to "belong" to you or identify you. Don't use things like DCC which might reveal your real IP or real information about you. Disable all possibly "leaky" features/commands such as CTCP, VERSION requests, automatically accepting files from other IRC users, etc. etc.
• Don't accidentally access Tor hidden server URLs in an untorified browser. For example, if you would try to access the fictitious hidden server abc1234.onion, this request would travel over the net unencrypted and untorified. An eavesdropper could sniff that, enable Tor on his computer, go to abc1234.onion, and would know what you wanted to look at.
• Double-check that all applications you use don't leak DNS requests.
• Do not only configure your ~/.foobarrc config-files but also the config-files in /etc. Otherwise you might eventually use wget, ssh, lynx or other tools as root (instead of your normal, non-privileged user account) resulting in untorified traffic!
• Disable all "check for updates automatically", "notify upon new release" and similar "phoning home" features in all your applications. Most such features are probably not Tor-safe, i.e. will send/receive untorified traffic. Some candidates are Firefox, Adobe Acrobat reader, Gaim, and others.
• Never, never, think that Tor encrypts your traffic! It does not! The person who runs a Tor exit node can easily sniff all plain-text traffic! Tor only anonymizes your traffic, but it can still be sniffed plain-text at the beginning and at the end of the onion route! So don't do any HTTP-auth, or plain-text password sending for e.g. POP3, telnet, and so on. Always use encryption in addition to Tor!
• In general, spread only a minimum of information. Disable referrer sending (e.g. using Privoxy), disable cookies, kill webbugs (Privoxy), and so on.
• Watch your language, especially in public forums or IRC. A linguist can probably easily figure out which country/region you're from if you speak/write broken English or use certain idioms or false friends. This might or might not be a problem for you, but it's something you should bear in mind.
• If you're extra paranoid, you could set up your firewall to block all outgoing DNS traffic and force all applications to use Tor to resolve names. You could probably also block all outgoing non-Tor traffic...
• Another good idea is probably carrying an Anonym.OS LiveCD with you, so you can have a (more) anonymous communication wherever you go.

More information More information is available in the Tor documentation, the Tor wiki, and especially in the Tor FAQ. In addition, there's an IRC channel on Freenode (#tor), some slides and a video (torrent) about Tor you might find interesting. If you would like to help, you can run a Tor server, donate some money, or volunteer to do other things (code, debug, document, translate, and more). That's it for now. I'm very grateful for comments and suggestions, especially for hints on how to anonymize more applications. Also, if you notice any dumb mistakes I made, please leave a comment. Update 2006-03-07: Fixed typos, added link to the toraliases project (thanks Benjamin Schieder).

Today I've rewritten most of my "laySVN" layered subversion tool. Tests had shown that most of the time was spent calling the "status" command of the underlying subversion client. This is probably due to locking, and the workaround is pretty simple: avoid calling it on single files, instead run it on the whole repository at once. This of course requires major changes to the code, so I've started a rewrite. I've already applied for a alioth project for it, I'll make the source available via svn.debian.org soon. "Layered subversion" means that you basically checkout multiple subversion repositories on top of each other. A file found or ignored in an "upper" layer will not be checked out in lower layers; ignoring a file in a layer will effectively "hide" it if it were in lower layers. This is an interesting alternative to branching. In branches, you have to "carry forward" changes from one branch to other branches. The base case - merging changes from a "lower" layer into an "upper" layer is usually quite easy. The other direction can get quite messy however. Assuming that multiple files were modified in the checkout, how are you going to commit these changes to the correct branches? Basically you'll have to commit the files to the correct branches, then do the merging magic. Along comes laySVN, where this common usage pattern is much easier. Changes will automatically be committed to the highest "layer" the file is in. A checkout will update the file to the version of the "highest" layer. The only case which is a bit more complex is when you want to make changes to a file on a different layer. Then you actually have to "add" the file to the appropriate layer. Not really difficult either, is it? A different name for "layered subversion" would probably be "difference branches", which are very similar.

David writes that, while momentum is a very good way to keep flames away, it's really solidified by proper code of conduct. I don't disagree with either of these positions, but they're both characteristics of a good culture that enables things to get done in a productive atmosphere, rather than the causes themselves.

One of the problems is that you can't enshrine, 'don't be a tool' in a code of conduct. Yes, you can legislate away personal attacks, so there's no more Serious problems with Mr. Troup, but it's still entirely possible to completely subvert the development process while still remaining within the bounds of any particular code of conduct. The key here is that the code of conduct is just a rough guide to, and a method of enforcement of, any given culture that you wish to enforce.

If you want to change Debian's current developmental culture, you'll need more than just a document: you'll need a landslide mindshift within the entire developer base, which will be extremely difficult to achieve, given that some particular developers seem to champion their lack of social skills, delight in annoying others, and glorify petty arguments on mailing lists as being superior to actually achieving anything. When you get this, the code of conduct is really just fluff, because it becomes almost entirely self-enforcing. The general tone of the list and attitude of the developers discourages people from being idiots, and you don't have to point to the code of conduct except in serious cases.

So that's the really hard part. Debian has a destructive culture that has led to debian-devel and debian-private becoming the pointless landfill it is today. Which is no slight on Debian developers as a group, or any particular developers; it's just the way it is today. How it got that way is entirely unclear, but how it's going to move on from there is an equally perplexing question.

And, in response to Joss, the two go hand in hand. Once you've stopped arguing for the sake of it, you're infinitely more productive as a result. So I don't think calling people advocating change in Debian's social norms 'teletubbies' is at all useful: these people aren't advocating turning Debian into a sewing club where we all turn up and talk about how much we love each particular developer. What they're advocating is change of the current Debian social culture such that trainwreck threads full of personal attacks, mindless bitching, and argument for the sake of it, don't exist anymore. You can have robust debate within that framework, and you don't have to completely vet every statement you make so it's a glowing reflection on everyone and everything mentioned. If you have the right culture, you can simply tell trolls once to go away, and they get utterly ignored, instead of having their threads blown up into huge all-consuming flamewars by people who seem to love seeing their name in the mailing list index. I don't see how you conclude that any hypothetical code of conduct exists purely to facilitate trolling either, but maybe I'm missing something.

The current problems in Debian with people being unable to relate to fellow developers, so instead getting bored and flaming them into the ground instead, isn't a techincal problem in the least. It's a social problem. The entire point of this debate isn't, 'which MTA should we install by default, if any', but 'how do we fix Debian's current culture?'. I don't see how this is a technical problem, but it does have technical ramifications (e.g. releases take years of banging our collective head against a very large wall).

Yesterday I have setup a kfreebsd-amd64 (ie GNU/kFreeBSD on an amd64 CPU) build daemon. Its name is shockley.aurel32.net (all my machines are named related to electronics), and it has Sempron 2600+ CPU. As you can see on the photo, it is still missing a decent case. There are actually two machines on the the photo, the motherboard in the case is maxwell’s one (one of the kfreebsd-i386 build daemon), while the one on the top front is shockley’s one. That’s a bit strange, but the amd64 motherboard needs a power supply with a P4 connector, while the other one only needs a small power supply. Thanks to Ingo Juergensmann, the kfreebsd-amd64 architecture is now listed on http://buildd.net. As you can see on the graph, this machine is very fast (it only runs for 24 hours!).

Several weeks ago, Wolfgang asked after a rename command for Hecl. Pretty simple to do in terms of the Hashtable that maps strings to commands, so I added it. However, there was a problem: in order to save space, I'd been grouping commands together in one class, and dispatching on "argv[0]". A nearly empty class in Java compiles to something like 500 bytes, so mapping one command to one class is not an acceptable practice when you are working, in some cases, with an upper limit of 64K. Dispatching on argv[0] meant treating it as a string, and doing a compare against the command name, which meant hard coding the command names into the classes implementing commands. Try renaming one of those commands and...oops! I struggled for a bit trying to find an answer I was happy with, and after talking it over on the mailing list, arrived at doing things like this: A big class that implements a number of commands, with a dispatch method:

static void dispatch(int cmd, Interp interp, Thing[] argv) throws HeclException  

That method then does a plain old 'switch' on the cmd int to go to the correct block of code. The code that calls this is simple, and it has to be, because one gets instantiated for every command, and so it's imperitive that it doesn't take up much memory:

class MathCmdFacade implements Command  
    private int cmdtype;
    public MathCmdFacade(int cmd)  
        cmdtype = cmd;
     
    public void cmdCode(Interp interp, Thing[] argv) throws HeclException  
        MathCmds.dispatch(cmdtype, interp, argv);
     
 

So far, I'm pretty happy with the results. By making the 'facade' (I'm not sure it's really the facade pattern, but... oh well, the name works for me) small, I don't waste memory. Plopping all the code in the switch statements is probably loathsome to purists, but it makes the code smaller, something that's never far from mind when working on Hecl. Things are also a bit faster, because we don't do the string comparisons to dispatch commands either. All things considered, the code isn't illegible by any means, either. Furthermore, because the new 'facade' commands still just implement the regular old Command interface, which means that Proc still works, and that you can still associate a class implementing Command with a string, so that it remains very easy to implement new Hecl commands in Java, and the interface hasn't changed. Faster, smaller, backwards compatible, and 'rename' works too... life is good!

[ 2 ] GFDL-licensed works are unsuitable for main in all cases
[ 1 ] GFDL-licensed works without unmodifiable sections are free
[   ] GFDL-licensed works are compatible with the DFSG [needs 3:1]
[   ] Further discussion

I dropped my cell phone a few months ago, and it ended up with a large crack across the LCD, which to me became the perfect excuse to finally get that Blackberry I’ve always wanted. However, given the uncertainty about the outcome of NTP v. RIM, I decided to hold off on my purchase till after the hearing last week, which was widely expected to provide some closure one way or the other as to whether RIM would be allowed to continue its service in the U.S. Unfortunately, there was no such closure to be found. So, I have a quick question to those more in the know than I: When the media talks of a “Blackberry shutdown”, I assume they’re just talking about a shutdown of the push email service, not a shutdown of all access to the Blackberry network? In other words, if Blackberry is shutdown, I presume I’d still be able to access the web etc.? Or would my brand new Blackberry become little more than an expensive paperweight?

I'm angry with Kanaal 2. They've broadcasted Star Trek series since they were founded approximately a decade ago, which was nice; not that I'm a fanatic who would never miss an episode, but I do appreciate a bit of science fiction now and then—and in my opinion, Star Trek is some nice SF. Well—most of it, anyway. This year, they've started the first season of Star Trek: Enterprise as well... at 8 AM, on saturday morning. Morons.

I just managed around to learn the very basics of autotools, and as a first execrise, used them on my "SSDDiff" xmldiff application. So you can now build it with the usual "./configure && make" command (if you have C++ STL and libxml2, that is, but these have been really standard for years now) So there is a new tarball on the Alioth project page which should be a lot easier to install. Get it while it's hot. ;-) A few words about ssddiff: SSDDiff is an "diff" application for XML files, which can output into a "merged" format, "xupdate" diffs or "marked" versions of the source files. The algorithm used is very good at dealing with structural changes, but it uses rather much memory and is not the fastest. So it's a good choice when you have a difficult case (one could say it tries to do a "semantic diff"). If you have CVS files or database tables dumped to XML, use other tools.

Well, the title might be a little too optimistic, s/victory/battle/ if you prefer. Surely the next battle against software patents (not only) in Europe is coming up.

In case you haven't heard about it yet, visit the nosoftwarepatents-awards. Each month five (software) patents will be presented, which were issued despite the law prohibiting software patents and despite (formal) protests against them.

This month features such highlights as a "centralized database" and a "context menu".

The idea is to show, that a.) software patents exists (despite patent advocators claiming they don't) and b.) what a sheer nonsense such are.

BTW, your webshop is also patented, in case you didn't know. Selling over the network, paying with credit cards, sending offers after requests ? All patented. Shut down your business now ;-)

It looks like I’ve earnt another ID: CVE-2005-4720 - Firefox 1.0.6 segfaults on this malformed .html page. Still no news about the security bounty though. I’m tempted to prod people .. but I haven’t managed to get round to it yet. On the one hand it’s bad to push for things like that. On the other hand there is no way I’d cash the cheque, and it would look lovely hanging on my wall…. Nothing much to say about the Debian Project Leader election yet. I think it is pretty clear to me that the idea of a “team DPL” was a failure. (At least I saw nothing happen any different.) I hoped the current/previous DPL would do great things, but to be honest didn’t see much evidence of it. (I know that personal issues came up, which is understandable, but it was disappointing to see the lack of promised status reports.) I also utterly refuse to vote for anybody who mentions in their platforms “we’re all social disfunctional”. I’m not. I’m good with people, animals, and myself. I don’t need somebody reinforcing geek stereotypes in even the smallest way. I did have the vague hope we’d have a female DPL, but alas that doesn’t look like it will happen for a while longer. Something to think about for the next year perhaps? Ummm .. I’m not sure how valid people would consider my opinions given that I’ve been mostly driven away from Debian mailing lists, and have never been a big IRC users .. so I will stop commenting now!