Zach knows the wind now. I saw him look at the window and see the leaves rustle. He then started making blowing noises. We blow the mobile over his crib whenever we change his diaper, so he knows the blowing noises move objects. But he's translated that to leaves hundreds of feet away through a window. Now I'm not saying he's a genius, but he's pretty awesome.

I noticed a while ago that my spam filter was 100% accurate on all plain-text emails. Spammers are now forced to use obfuscation techniques like embedded images and HTML. It seems to me that this provides an easy way of totally eliminating spam:

1. Bounce anything that is not from a whitelisted sender and contains an non-plain-text MIME section.
2. Auto-whitelist anyone I send a mail to.

This means that anyone I email is free to send me whatever they want. Anyone can still contact me, but they are restricted to sending me plain text for the first email, until I reply to them.

Of course, spammers could start sending out messages saying 'I tried to send you some spam but your filter blocked it, please email me.' These will be caught in grey-traps for 8 hours, and by the end of the 8 hours there's a very good chance that the email will have been caught and the sender added to an RBL.

I'll probably try implementing this when I have time, but if anyone has time before me then please do and let me know how well it works.

This won't significantly affect most of you, but we have been working on some meta mod changes. The most user visible change is that the UI we used to use was thrown out, and instead we are using one based on the firehose. Subscribers will see it when they go to the old metamod link although users can see it by going to this version of those hose

The first real change is that we've changed the meanings of the UI around. The old system is 'Fair' and 'Unfair' and the new system is '+' and '-'. The meanings are subtly different. You are no longer rating individual 'Insightful' or 'Troll' or whatever... you are now stating basically "Is this comment good or bad for you". Personally, since I find very few Score:5 funny comments to be actually really funny (and not just cliche memes) I '-' most of them. You are encouraged to be harsh if you don't actually think something is insightful or funny, call it such. The system encourages more of what you + and less of what you -.

You are also welcome now to do more than 10 m2 per day... however we internally have diminishing returns after 10, so you can do more, but they start to matter less and less.

There will undoubtedly be bugs so feel free to email me or vroom at slashdot if you find them. Probably next week or so we'll move this out to everyone, so your assistance is appreciated.

My current contract at the university expires a week on Monday. It's been fun. I've been employed to set up a History of Computing Collection - a chance to indulge one of my hobbies for a bit after finishing my PhD and relaxing after the immense stress of writing a book and a thesis (in more or less unrelated areas) at the same time.

Now I'm back to freelance writing and spare-time hacking. If anyone wants to employ me for a bit, let me know...

A couple of weeks ago, one of the hard drives in a FreeBSD box of mine died. This was mildly inconvenient, but since it was one of a RAID-1 array, not totally catastrophic. It seems to be the season for drives dying, because the disk in my MacBook Pro just died this evening.

The machine had been being a bit slow and randomly pausing for a while for no apparent reason. I now realise that the random pauses were caused by I/O errors causing userspace processes to block waiting for kernel locks to be released. Ho hum.

Over the last month, I've been becoming progressively more concerned about how long it had been since my last backup (October 2007!) and last weekend I finally got around to running a full backup of my home directory. As such, I haven't lost very much. Most of the work I did in the last week is in svn and the grant proposal I've been working on was rescued just before the drive died completely. I lost a paper I was working on and some emails and chat logs, but nothing particularly important.

I think my next laptop is going to be solid state. Mechanical storage is more trouble than it's worth.

Well, for subscribers only this week at least. We have a half dozen minor bugs left in the TODO list, but if you are a paying subscriber you can test it out. It works best if you are using the keybindings to navigate. Pressing 'f' takes you to the next unread comment respecting thread order... so you can press that over and over again.

We also added a thing to 'collapse comments after reading' which I think I might turn of as a default setting soon. This is only usable for subscribers atm as well. But basically, as you navigate through a discussion, it collapses the comments you've read after you move on. This makes it really easy to navigate large discussions without having to scroll over 150 comments you've already read.

we're aware of a number of annoying bugs, but hopefully most of them will be squashed by Pudge for this weeks code refresh. If things are stable, we hope to roll this out for everyone rsn.

also my baby cut his first tooth yesterday. My furniture will never be ungnawed upon again.

I'm not a huge fan of the GPL. While I agree with the FSF on most things, I can't help feeling that the GPL shows a certain lack of faith in the whole idea - if the open source development model is so much more efficient, and Free Software is so much more valuable, then why do they need such a mass of legalese to protect them?

From a more pragmatic standpoint, the GPL is about the most incompatible Free Software license around. If you write GPL code, you can't use it in a BSD, Apache, X11, MIT, or Mozilla licensed project.

I was fairly happy with the LGPL until recently, however. It is a bit more restrictive than I'd have liked, but as long as you dynamically link to it it doesn't taint your own code. This is a story about the pain caused when lawyers get in the way of writing code.

It turns out that the LGPL, as it stood, wasn't restrictive enough for the FSF's ideology. You can't have freedom without a lot of restrictions (apparently) and so they added a load more to the venerable LGPL 2.1, and created the new, improved, twice as restrictive, LGPL 3.0, and encouraged all GNU projects to upgrade.

One such project, which I'm directly involved with, GNUstep, did so. Then we started having problems. It turns out there's this other license that has a clause stating that it may not be used with any conditions that are not in the license itself. This is the (GNU) GPL. Version 2 of the GNU GPL is incompatible with version 3 of the GNU LGPL, and since it's viral you can't even link code under the two licenses.

That's okay though, right? The FSF has been telling everyone that they should use the 'or later versions' clause when they use the GPL, just in case they want to make it more restrictive in the future. And everyone's done that, right? Well, it turns out, xpdf didn't. And the xpdf code was extracted to form the Poppler library. And the Poppler library, in turn, was wrapped in PopplerKit, an Objective-C framework for rendering PDFs. And so, by the transitive property, all of these GNUstep apps were GPL 2. Which is incompatible with LGPL 3. Which meant that suddenly they couldn't use the latest GNUstep. By the way, PopplerKit isn't the only GPL2-only library used by GNUstep apps.

This is a bit of a problem. So big, in fact, that Debian decided not to carry the latest GNUstep, because it would have meant dropping a load of GNUstep applications from the next release. The eventual outcome? GNUstep has reverted to LGPL2.

This isn't an unusual situation, by the way. A number of big libraries, such as GNU libc (an abomination that needs to die, but for technical, not legal reasons) is having the same problem - the FSF wants to 'upgrade' it to LGPL version 3, but that will mean any Linux distro that ships the new glibc will not be able to ship any GPL 2 apps.

And people wonder why I prefer the BSD license family.

So as we've been migrating the system from the tired old D1 to the exciting and awesome new D2 a number of complaints have come up. I'm going to talk about a couple of them here because I'm really looking for feedback on THESE issues. Please only talk about these points or I will mod you offtopic or troll or something.

The issue is about the use of Flat/Threaded/Nested modes. D2 cleanly replaces both threaded and nested modes- you effectively get nested mode by bringing the 2 sliders together. And threaded mode is vastly more flexible because you can choose the level at which comments are abbreviated or displayed in full text. So users of those modes should be set (obviously there are other reasons not to use D2, I'm just talking about the layouts here tho)

What's left is flat mode, which has a number of sort options. Now flat mode is used by roughly 4% of our active population. When i think about flat mode, I think about 2 reasons you would have to use it:

1. I hate indenting and whitespace. I want a big vertical column now this isn't my bag, but I can understand it and even consider supporting it in D2. I think you sacrifice legibility, but this is a personal preference. It also would be easy to support in D2. Hell, you could probably do it in a greasemonkey script no problem.
2. It's easier to remember your place in flat mode This to me is the only reason to use flat mode- you can reload your page an hour later, find the last comment you read, and pick up where you left off.

Now I Would think that the only reason to use flat mode is #2... except that only a couple hundred Slashdot readers have the 'ignore threads' sort order enabled. So either they don't understand what they are doing, or #1 above is the real reason that they use flat mode.

So in a nutshell, the question I am asking in this journal is 'Why do you use flatmode?' Is it cosmetic? To more easily keep your place in a discussion? Something I'm just missing? We have plans to implement a read/unread state retention for discussions, so maybe would you migrate to a threaded view if that function exists? Or is it purely aesthetic... an irrational hatred of scrollbars and whitespace? :)

The reason this matters is that simply formatting the page flatly is easy. Probably a simple greasemonkey hack or maybe a few lines of CSS. But re-implementing the alternate sort is gonna take some work. And I'm ok with that... except that the logs say that nobody actually USES that sort... they ONLY are using flat mode for the cosmetic reasons.

Speak out! Stay on-topic or you WILL be moderated down.

In-Place Posting is now live for all logged in users. Hopefully there are no surprises. We've found a number of very tiny bugs, but nothing show stopping. We'll leave the link up to the 'classic' reply form for a few weeks. Next week anonymous coward will get the new posting form... hopefully there are no surprises with that.

A few new keybindings aren't documented yet... v (end) t (top) [] change upper threshold and ,. change bottom threshold. Also 'r' opens the new reply box, m opens the mod total thingee.

The only major complaint so far is that the design changes consume a lot more whitespace. I have mixed feelings on the subject, but am aiming to strike a balance. We noticed 2 very clear places where the whitespace is excessive and hopefully that will be fixed RSN. But on the other hand, making deep threads visually clear, and drawing some attention to the 'reply' buttons is beneficial to everyone, so bare with us as we work to strike some sort of balance.

Discussion2 rolls on... the most recent addition to the system is in-place comment posting. Essentially, little dynamic ajaxy slideout boxes to post directly within the thread, without going to a stand-alone page. This is great because you don't have to lose your place within the thread to post.

this functionality is currently only available to paid subscribers, and several hundred of them have tested it out already. We still need to make it look pretty and add a few minor things (like the CAPTCHA for anonymous posting) but it's almost done.

Also worth noting is that logged in users can click on the 'Score' field of comments to view the moderation information on the comment. This information was previously not visible within D2, unless you navigated outside the d2 system (opening a comment in a new window did it). I doubt most people really care about this info, but it's available.

We also have one (perhaps minor) thing to get in... right now if you visit a comment directly via a CID link you can navigate within that thread, but navigating 'up' the comment hierarchy results in a new page, and a new discussion... this makes context a pain to maintain. So pudge is going to change that page to display the parent posts in an abbreviated format. This will mean that you can climb back up the thread easily, even if you entered the forum via a link deep into a thread.

A few minor items left on the todo list (keybindings for threshold changes... maybe press 'r' to open the reply slideout from the current comment, and a bunch of small design issues to make the threads a little more visually clear and easily navigatable) and we're ready to call D2 finished.

We have no plans to remove D1, so those of you who hate D2 are welcome to stay on the old system, but obviously new moderation tools and whatever else we think of will be attached to D2, not D1, so you've been warned ;)

In the last few weeks, we've switched most users over to the new 'D2' discussion system- a fully ajaxified discussion system. There are a number of minor bugs, but I figured I'd toss up a few quick notes to address the biggest user complaints.

1. you can turn it off if you log in. Some people get stuck in there ways, and no matter what we build it will never make you happy. So you can have the old lame system and we'll all enjoy the new cool system without you.
2. you can get 'nested' mode back by dragging the 2 thresholds together in the floating slider. they connect and become a single thing. it's quite nifty, and if you are logged in the setting is remembered so you don't have to click to navigate deep threads.
3. you can get more comments at once from the 'prefs' link. the default is currently 50, but choosing 'many' changes that (currently) to 250, which means you will get roughly the average number of comments in a typical slashdot story. Yes you will need to click 'more' on a huge discussion, but at that point we're talking about very large pages and slower computers like to choke on huge pages anyway so we have to balance size and performance.

there are 2 huge wins here for everyone... the first is retention of context. You can wade into a thread, retrieve more comments, change your threshold, all without losing your place like you did in the old system. And using the WASD keys to navigate makes it very easy to peruse discussions in a number of interesting ways. mouseover the help text in the floater for more information about how they work. We're open to suggestions on how this should work- i'm not totally happy with it yet... but it *is* possible to mash a single key and go from start to end of a discussion, which pleases me.

the second is that the default users see the highest score comments first. You can change this by logging in and toggling the retrievable order to oldest first, but for most people this means that the first comments they see will be the best. There are so many great comments on Slashdot, but most users don't see them because they are buried within the discussion. I think this goes a long ways towards helping.

A final word about the ads in there- unfortunately there are ads in the new system. Changing from a static page-page-page system to a dynamic ajax system with a single 'page load' causes us to serve hundreds of thousands of fewer ads. We worked out roughly how long people read discussions and are trying to strike a balance so that you see roughly the same number of ads under this system as you would have under the old one. We'll tweak it of course, but we gotta pay the bills here people!

And obviously all of this is a work in progress. Pudge is leading development work on this. The next project is to make it possible to post without losing your place in the discussion, and then to refine navigation keybindings and thread expansion/contraction controls to make the whole UI clean. We appreciate constructive criticisim. There are bugs (especially in IE, but almost no slashdot user runs IE) but we're mashing them out- thanks for your feedback on them. As we sand off the rough edges I think you'll all find the new system a vast improvement if you just play with it for a bit and give it a fair chance. Not all change is bad ;)

It's that time of year again, where I realise I'm paying more than I need to for my phone and think about switching providers. Currently I'm paying abut £14 a month, for 100 minutes of calls and 40MB of data. I rarely make more than 60 minutes of calls in a month (I hate telephones), but I'd like more data so I can use my 770 as intended.

For the last four years, I have been looking for a service like this, where it provides calls but is mainly focussed on data. I am looking (somewhat half-heatedly, I admit) for jobs and the moment and so I don't know how long I will be staying in the UK for, making any contract with a minimum period unacceptable. This shouldn't be a problem, since I already own a phone so no network needs to make and recoup any investment (and yet most of them still require a minimum period of a year for a contract, and Three don't even offer SIM-only contracts).

Does anyone know of a UK operator which doesn't suck, and does provide intermittent data use for a reasonable rate? I am starting to think I should invest in WiMAX companies; at this rate they're going to make a killing when they start deploying over here...

There is no way I could feel more disdain for Apple's QA department than I do right now. It seems that, in spite of the fact Leopard was in development for over two years, no one bothered to test what happened when you updated an account using FileVault from Tiger. My experience was:

1. The installer worked fine.
2. I logged in, and used the OS for a day.
3. The kernel paniced.
4. On rebooting, my home directory was inaccessible, and Disk Utility was unable to repair the disk image.

Oh well, I thought. It's an occupational hazard when using an encrypted disk image for your home directory; if you don't get a clean shutdown then you can lose data. So, mindful of this, I restored from a recent backup and rebooted. Sure enough, there I was logged in again. Then, a few weeks later, I upgraded to 10.5.1, shut down cleanly, rebooted, and... couldn't log in. Apparently the disk image was corrupted. Worse, it turns out this is a known fault: Leopard always leaves FileVault home directories created with Tiger in an unmountable state when you log out.

I'm going to say that again:

Leopard always leaves FileVault home directories created with Tiger in an unmountable state when you log out.

What kind of monumentally incompetent design is this? I have no idea. Anyway, enough of the ranting. I'm sure what people really want to know is 'what do I do when my shiny new OS has just eaten 30GB of personal data.' Step one is to swear at Apple. A lot. Step two is to realise that this 'corrupt' disk image, with a 'bad superblock' actually mounts fine in Tiger still. Fortunately, I haven't 'up'graded my Powerbook to Leopard. I booted the MBP in target mode, mounted it on the PowerBook, mounted the disk image and copied all of the files out.

I now had /Users/theraven/theraven.sparseimage containing the disk image that Leopard was too inept to use and /Users/tr containing my files. After swapping these over, I rebooted. Could I log in? No. Now it didn't think that the disk image was corrupt, it just couldn't find it. A problem.

This lead to the question of how to tell OS X that I was no longer using FileVault. Apparently this isn't documented anywhere I could find via Google and so I had to spend a long time hunting through the filesystem. Thanks again Apple.

It turns out that the relevant file is /var/db/dslocal/nodes/Default/users/theraven.plist (where theraven is my username). To edit this, you have to log in as root. I did this by booting to single user mode (hold command-s on boot). Inside this file, you will find a key-value pair where the key is home_loc and the value is an array. If you delete this key, then it will fall back to using the home directory as a directory, rather than a mount point. You can then reboot (or just exit from single user mode) and log in. You can probably then reenable file vault and have it re-encrypt your data, but I think I want some confirmation from Apple that they are only mostly incompetent, rather than completely inept before doing this.

Once upon a time, Apple was known for attention to detail and thorough testing. I suppose their current activities are good news for Étoilé, but I'd rather we competed by raising our standards than by Apple lowering theirs.

Someone just sent me the best link I've seen in a long time: http://freerice.com/index.php.

It's a simple vocabulary game which asks you to pick the closest synonym for a word from four options. It shows you adverts, and for every word you get right they donate 10 grains of rice to the UN World Food Program. It adjusts the difficulty based on how many you've got right so far, up to a maximum of 50. I seem to be hovering around he 40±2 mark at the moment.

EDIT: I got to 47 for a bit, but then dropped down again. Still haven't made it to 48, which they claim few people beat.

Since this is not yet documented, I figured I would mention this here now... we are experimenting with some very rudimentary keystroke navigation in the discussion2 system. We support both FPS style WASD keybindings, as well as the standard vi layout of HJKL. Down/Up will cycle you through next/previous comment chronologically... left/right will cycle you through next/previous in thread order. Holding SHIFT down while you press the navigation key will collapse the previous comment. And when you get to the end, pressing down or right will attempt to retrieve more comments if you want them.

What this means is that you can now use D2 to simulate most of the most popular viewing modes of the original discussion system. By dragging both the abbreviate & display sliders right next to each other you effectively remove abbreviated comments which simulates nested mode. By toggling comment retrieval order to 'Oldest First' and using up down, you can effectivel read the discussion from oldest to newest. And of course the default settings gives you the best comments first, providing a nice default view of discussions for most anonymous users (who rarely participate and we want to really show only the best comments).

You can also disable D2 in the comment prefs (the word 'prefs' in the floating dialog box) if you are logged in. Right now we're testing D2 for a large percentage of anonymous readers. As soon as we finish IE7 support we'll roll out D2 for the rest of the ACs.