Dann Frazier: svn-load now in unstable
svn-load, a DFSG-free replacement for svn_load_dirs, is now in unstable.
John Wright has been working on adding support for doing preset pattern-based
moves, which I hope will be ready in the next upload.
svn-load, a DFSG-free replacement for svn_load_dirs, is now in unstable.
John Wright has been working on adding support for doing preset pattern-based
moves, which I hope will be ready in the next upload.
I am, at best, a vim dilettante, preferring joe for most of my day-to-day
text-editing needs. However, I do like using vimoutliner for notes, plans,
todo lists, and calendaring (more on that some other time).
However, the Debian vimoutliner package (in combination with the awesomely
undocumented vim-addons mess) is an absolute pain to get going, requiring
far more swearing and prodding than seems necessary. Since I don't do it
often enough, too, I keep forgetting how, and today things came to an
absolute head when I very nearly flung my netbook across the room as it
singularly refused to do my outliner bidding.
Finally, however, after much swearing (and even installing vimoutliner's
upstream package to see if it worked -- it did -- and what it was doing
differently -- just a small, crucial addition to .vimrc), I got
the magical recipe. No doubt someone with an acheing need to make sure
that vim stays as user-hostile as possible will immediately spring into
action to
make sure this doesn't work for squeeze, but at least for the life of
lenny, here's how to get vimoutliner working:
# apt-get install vim-vimoutliner vim-addon-manager vim $ vim-addons install vimoutliner $ echo "filetype plugin indent on" >> ~/.vimrcMay it help someone avoid putting their laptop through a wall.
Once again, the monthly board meeting of Software in the Public Interest will take place on irc.oftc.net #spi tonight (Wed 16 Sep) at 20:00 UTC. The meeting announcement was posted and there s a proposal for an extra bank account and two projects up for association: Path64 and OSUNIX.
The big change for current members is the proposal for contributing membership expiry:
Any contributing member who does not cast a ballot in an annual Board member election shall be considered to be inactive and downgraded to a non-contributing member.Yet another demonstration of how member ballots are not secret yet. Even if they re not secret like they should be, is it a good idea to feed the ballot data to the membership process? Should Further Discussion be added to the SPI board election, to give members a way to abstain? Should this dramatic change proposal be considered this meeting when it wasn t mentioned in the meeting announcement?
The Debian Installer has a USB boot image that is supposed to
be written raw to the USB stick. Problem is that means
the image has a fixed size, 256 MB, and all the other gigabytes
on your typical USB stick are unusable after writing this image
to it. It's a bit of a cheat for me to blog about this, since I'm
slighly responsible for the thing that I'm working around. But still.
The real problem is not the fixed size of the image, but that it is written
to the USB stick as a "super floppy", without any partition table. If there
were a partition table, you could make a second partition in the rest of
the space of the USB stick, and use it to store files, etc. So, let's set
that up. It's not really hard:
zcat boot.img >/dev/sda1mbr package, and running
install-mbr /dev/sda
I released a new 0.9.7.2 version of DAViCal yesterday. This reflects quite a lot of stability and small fixes for some subtle problems, and quite a lot of work with the iPhone, adding the possibility of a simpler configuration experience for iPhone users.
One long-standing, but less obvious problem (well, less obvious to me) was the handling of usernames with odd characters in them. In the round-trip these needed to be urlencoded, and that wasn't happening correctly in all places, but it hopefully is now. People who want to use e-mail addresses in usernames, or spaces in calendar names, or both, etc., should all work now.
One newer problem I've been seeing the effects of a little recently is that PHP 5.3 deprecates call-time pass by reference, which I had used in a few places. That's fixed now, so it should be OK to upgrade to PHP 5.3 without breaking DAViCal or having to explicitly turn those warnings off.
The iPhone is a curious beast. Lots of people love them, and it is about the only mobile device that supports CalDAV (though I'm hoping the Nokia N900 also will), so it's important to support it as transparently as possible regardless of my personal loathing for it's horribly locked down state. It was pointed out to me that it is possible for it to be configured by entering three pieces of data (domain name, username, password) so I decided to make DAViCal support that process. In order for it to work for you you will need to have DAViCal running on an SSL server on port 8443, which isn't too big a deal. You can also plain http on 8008 which it will also attempt after prompting when the SSL connection fails. You'll also have to enable mod_rewrite and use some rewriting rules like the example on the wiki.
For myself, I use the free SSL certificates from CACert.Org so I had to browse to their root certificate page and load the class 1 and class 3 certs into the iPhone before it would talk happily to my DAViCal server.
I'm hoping to continue with reasonably frequent incremental releases of DAViCal for the rest of the year, hopefully with 0.9.7.4 sometime in late October. What will be included there might also depend on how productive my visit to CalConnect XVI is in three weeks too, and I'm looking forward to that.




I'm moving to the US on Thursday, so I will be here on Wednesday evening from about 7. If your presence is unlikely to make me stupifyingly angry, feel free to join me.

A quick reminder about the meeting about forming a Koha foundation in a few hours. The agenda and information links are on the wiki. I d really like to see everyone invoved in koha development there, or you could leave comments here for me to take to the meeting.
Someone will link a summary and the transcript from the wiki after the meeting.
For those who aren t clinically dead, you may have heard of the BBC . The BBC are the state-ish-funded TV network in the UK, and the country s biggest broadcaster, alongside three other major terrestrial broadcasters who make their content widely available without payment ITV, Channel 4, and Five. These broadcasters also make some or all of their programming available for streaming over the Internets usually their home-grown programming only, not licensed stuff from America.
Now, once upon a time, the online functionality was mostly offered via a proprietary P2P-and-DRM-based system called Kontiki. Kontiki was unpopular for various reasons for example, it was Windows-only, and banned by several Internet providers due to the use of P2P (e.g. I know such technology is still banned on the University of Oxford network). As a result, this lead to the introduction and eventual replacement of browser-based streaming solutions, starting with the changes made to BBC s iPlayer. iPlayer is nowadays a combination of an Adobe Flash service for web surfers, an unencrypted MP4 streaming service for users of mobile devices such as iPhones, and as of a couple of weeks ago, has streaming support built directly into the PlayStation 3 s user interface too. Oh, and on the PC, it supports DRM-based downloading courtesy of the Adobe Air platform, on Windows, Mac, and Air-capable (x86) Linux. Channel 4 s service 4od, and Five s Demand Five, are also based on Adobe Flash, and streaming-only. They re basic and functional.
The final interesting one here is ITV s ITV Player. ITV Player was, until about a week ago, the only non-Flash service, instead making use of Microsoft Silverlight. They have now changed to be Flash-based, like their peers, meaning the entire market mandates use of the Adobe Flash plugin or, at a push, command-line utilities or browser plugins which grab the raw video files from the broadcasters servers, in violation of their licenses. Why is this interesting? Well, when ITV Player used Silverlight, we could watch TV using Free Software: Novell Moonlight 2.0 Beta 1.1 and above worked fine with it, on i386 and AMD64 (and other architectures with a recompile). Now that it s using Flash rather than Silverlight, where do we stand for watching streaming TV legitimately with Free Software? Let s take a peek!
Firstly, some preamble. I m running Ubuntu Jaunty, and I hand-compiled a SVN (I think SVN? Maybe Bzr) snapshot of Gnash revision 11485 to ensure I had an up-to-date view of proceedings. It definitely seems to be working, as I m introduced to the world of Flash advertising via Gnash, and Youtube.com also works, more or less. And I m not discussing Adobe s Flash plugin here, for various reasons:
If you want to play a trick on a colleague who is writing a LaTeX document: Open the file, copy the entire contents of the file and paste it at the very end. LaTeX will happily process the file and render the first part. But your colleague will likely try to edit the end of the file and soon feel haunted because his changes to the file have no effect no matter how often he deletes the resulting PDF file or any intermediate file, how often he renames the original file or moves it somewhere else...(Just happened to me, but not due to a mean colleague, but due to some accidential vim commands.)
There will be an EU crackdown on websites selling consumer electronic goods which is entirely understandable when 203 out of 369 sites appeared to break the law. (first seen on BBC News)
If you re a shop owner, the good site and bad site examples are pretty good, while local trading standards offices advise on selling online.
If you re a buyer, see my guide on How to Check Web Shops for Basic Security.
Why is it so bad? Do companies not understand the law? Do they not bother to check the law? Do they deliberately decide to ignore it? Don t customers prefer law-abiding web shops, or are low prices attractive enough to overcome that?
Today it was once again time for the
Chicago Half Marathon
(which I have now been running in
2003,
2004,
2005,
2006,
2007
and
2008).
Conditions were much much better than last year's very heavy rainfall---we were once
again treated to a sunny and clear Chicago sky. It was however a little on
the humid side and got somewhat warm; a few friends I talked to suffered on
the second half of the race and I also slowed down.
As for the race itself, I didn't run it quite as evenly as I had hoped, faded
a little around mile ten and eleven and came in at 1:34:54, or just under
7:15 min/mile. Not a bad time---I have done better (e.g.
last year)
but also worse. All in all still one my very favourite races, and this year
with a once-again improved course that featured even more running along the
lake. I will probably be back next year.
Next.