Search Results: "ag"

15 April 2008

Theodore Ts'o: AT&T: Customer support horrors

This morning, I just wasted two hours of my life trying to deal with a bill with AT&T. I am a work-at-home employee, and my company has a contract with AT&T so that when I deal 1-700-xxx-xxxx, I can reach the internal corporate phone network. In addition, long distance calls on my home office line are billed to the company at the pre-negotiated corporate rates. I also had a (long-dormant) AT&T long distance account, dating from before I started working at this company. Starting at the beginning of the year, that account grew a $18 monthly fee. When I tried to make it go away, the AT&T consumer side of the house said that according to Verizon, that was because I had my long distance service through AT&T. Which was true, in a sense — AT&T was providing my service, but through a corporate account. But the consumer side of AT&T didn’t understand that, and were in my opinion, willfully ignorant. Several phone calls later, I got the 1-800 number for the AT&T corporate side of the house, and those folks said they couldn’t look at consumer/personal AT&T accounts, and implied it was my fault that I had both accounts on the line. (This took over an hour while the support person tried multiple things, all of which was not helpful at all.) I finally googled for AT&T CEO’s office, and found a number on the consumerist.com web site that claimed to be the AT&T CEO’s office. It had long since been directed to a help center, but after I told my tale, I was quickly transferred to an executive customer support person, who was able to fix the problem in ten minutes. The only questions remaining are: 1) Why can’t the different parts of AT&T talk to one another?
2) Will this problem really be solved, or will I see another bill in a month or two and have to spend more time dealing with this mess all over again?
3) When will VOIP services put AT&T long distance out of its misery? (Given the absolute frustration of this morning, this can’t happen soon enough.)
4) Will AT&T compensate me for two hours of frustration and of my life that I will never get back. (Not bloody likely.) One thing is for certain, it will be a long, long, LONG time before I will ever voluntarily choose AT&T to provide service for just about anything. Even an iPhone wouldn’t be enough inducement….

MJ Ray: Talk with People who want to Discuss

I spend too much of my time trying to talk with people who don't want to discuss, yet somehow I won't stop. I keep hoping that things like suggesting good advice on meeting scheduling will avoid them repeating old mistakes. The most extreme life-and-death example is probably trying to help with Kewstoke Toll Road, where people still speed and someone crashed off again last night (although I don't know what caused last night's crash - could have been a simple accident). Of course, it's better to talk with people who have asked questions and want to hear the answer. I'm currently involved in several groups like that and it makes me much happier [4HWW]. I've even made a confidentiality agreement [Network Blogging article] about one group because I really like the organiser and want to help them, but I've yet to see changes happen because of it and that's probably about all I can write here, which does rather suck. But talking of changes that make me happy, I spotted that Bristol Wireless has now gone further than TTLLP by deciding to change people away from Microsoft Windows when they find it:-
"all Windows stuff must be gone from the premises [...] no longer help do callers favours with broken Windows machines, apart from fixing them properly and permanently by installing Debian"
at their March meeting. Well done, BW! After a request, I finally put four photos from Social Source South West (which was hosted by BW) online, which reminded me to subscribe to watfordgap's travels. Disappointingly, on my first read, it promotes the Suppliers Directory developed by Lasa. That directory is a big problem because it creates a silly barrier to entry which hinders new social enterprises and cooperatives. At a time where most non-profit software is unsustainable and needs to change, requiring three referees is a way to obstruct change. Also, persuading three people to support their work is no substitute for supplier evaluation. Any non-profits who want to lead their sector should approach ICT suppliers directly. The article also mentions Experts Online which is even more short-sighted about computing: "both PC and Mac" indeed! What about GNU/Linux, thin clients, and other changes which are already making a big difference to some non-profits...? But here I go again, talking to a brick wall. I expressed these concerns when that Directory started and it didn't do any good then, so I doubt they'll change it now, near the end of its life. So I'm going to move on. There are lots of people emailing who want to hear from me, so it's time to concentrate on talking with people who do want to listen. If you want to discuss this with me, visit my website for the comments form (click the title or look for a "view original post" link, depending what site you're reading).

Anthony Towns: Jigdo Downloads

Last month we had a brief discussion on debian-devel about what images would be good to have for lenny – we’re apparently up to about 30 CDs or 4 DVDs per architecture, which over 12 architectures adds to about 430GB in total. That’s a lot, given it’s only one release, and meanwhile the entire Debian archive is only 324GB. The obvious way to avoid that is to make use of jigdo – which lets you recreate an iso from a small template and the existing Debian mirror network. I’ve personally never used jigdo much, half because I don’t usually use isos anyway, but also because the few times I have tried jigdo it always seemed really unnecessarily slow. So the other day I tried writing my own jigdo download tool focussed on making sure it was as fast as possible. The official jigdo download tool, ttbomk, is jigdo-lite – which you give a .jigdo file, and the url of a local mirror. It then downloads the first ten files using wget, and once they’re all downloaded, it calls jigdo-file to get them merged into the output image. This gets repeated until all the files have been downloaded. By doing the download in sequence like this, you miss out on using your full network connection in two ways: one during the connection setup latency when starting to download the next package, and also while jigdo-lite stops downloading to run jigdo-file. And if you’ve got a fast download link, but a slower CPU or disk, you can also find yourself constrained in that you’re maxing those out while running jigdo-file, but leaving them more or less idle while downloading. To avoid this, you want to do multiple things at once: most importantly, to be writing data to the image at the same time as you’re downloading more data. With jigdodl (the name I’ve given to my little program), I went a little bit overboard, and made it not only do that, but also manage four downloads and the decompression of the raw data from the template. That’s partly due to not being entirely sure what needed to be done to get a speedy jigdo program, and partly because the communicate module I’d just written to deal with this sort of parallelism making that somewhat natural. In the end, it works: from wireless over ADSL to my ISP’s Debian mirror, I get the following output:
Jigsaw download:
  Filename: debian-40r3-amd64-CD-1.iso
  Length:   675477504
  MD5sum:   d3924cdaceeb6a3706a6e2136e5cfab2
Total: 679 s; d/l: 586 MB at 883 kB/s; dump: 57 MB at 57 MB/s          
Finished!
which is only slightly short of maxing out my downstream bandwidth, taking a total of about 11m20s. Running jigdodl with a closer mirror works pretty well too, though evidently some of my more recent changes weren’t so great, because I’ve gone from 9153 kB/s on a 100 Mbps link down to 7131 kB/s or lower. The CPU usage also seems a bit high, hovering at between five to ten percent at 900 kB/s. For comparison, running jigdo-lite on the same file took 17m41s, which is about 566 kB/s, with the overhead being about 6m20s. What that means is if I doubled my bandwidth to about 20Mbps, jigdodl would halve its time for the download to about 5m50s, while jigdo-lite would still have about the same non-download overhead, and thus take 12m10, which is still 69% of its original speed. Going from 10Mbps ADSL speed to 100Mbps LAN gets jigdodl down to 1m31s (13% of the time, with optimal being 10%), while jigdo-lite would be expected to still be about 7m51s (43% of its original time). I suspect the next thing to do is to rewrite the downloading code to use python-curl instead of running curl, and thus downloading multiple files with a single connection, and tweaking the code so that it writes the file in order, rather than updating whichever parts are ready first. Anyway, debs are available for anyone who wants to try it out, along with source in the new git source package format.

Sylvain Le Gall: Debian accounts and keyring

Even if i don't like talking about this in public, Lucas Nussbaum blog entry decides me to write this, because I, too, agree that the Debian accounts and keyring situation is severely hurting Debian, and that a solution needs to be found RSN. I wish to be more clear on some of my positions concerning this. First of all, I am actually being hit by a "GPG key expired" status that prevents me to vote and upload packages. It is a little bit my fault because 1) i set an expiration date on my GPG and 2) i only update this expiration date in keyring.debian.org less than 1 month before it expires -- but it was more than 3 months ago... I have pinged different people since then to get the keyring updated without success. I have reuploaded my key without expiration date, and now i know that things can take a long time inside Debian (2nd rank after waiting for my own Debian account creation). Another point is concerning DM (Debian Maintainer). I was against the proposal when it was voted, because i was thinking it will create a "sub" status of Debian Developper (i.e people which are in between debian users and debian developers). I have changed my mind concerning this point the DM process is lightweight and everything seems to be faster with it. This is a really good points for DM (and jetring). I am also considering to sponsor myself to apply to DM, in order to have a non-expired GPG key somewhere. Last but not least, i met several French NM at DebConf 7 (Kibi, Goneri...). At that time, i didn't know them. Since DC7, I have seen them working on different parts of Debian. I think it is a shame to make them wait so long. It is really the best way to make their motivations disappear. Looking back at my own situation, i realize that i was more active before my account creation. This is probably because it takes a long time to process, and i loose hope in a possible account creation. I am now more active in Debian, but still not doing as much as i want to. I don't know the best solution to solve this problem. I tend to think that some key people should delegate their work to other DD (within a team ?). Last year at DC7, Sam Hocevar was already discussing this problem with the people involved in Account Creation. I don't know what was the result of this discussion... Hope, this post will help to show that this problem is important.

Matthew Palmer: Blahsagne

Blahsagne, n.: A tasteless pile of pasta sheets and nominally tomato-based sauce, usually found in the cold store section of supermarkets.

Holger Levsen: sick

It seems spring has finally arrived in northern Germany and I'm laying in bed, trying to get rid of a flu. So in case you are waiting for something from me, you will have to wait a bit longer :-(

Plans for today: stay in bed most of the time, eat properly, walk the dog twice more and do the monthly upload of debian-edu-doc.

/me sadly waves to KiBi - do what is good for you & have some fun!

Lucas Nussbaum: 4 months and 10 days without any new Debian developer. Is Debian dying?

It has now been more than 4 months since the last Debian developer account was created. 18 contributors have been through all steps, and are simply waiting for this simple administrative task to be done. We are sending a terrible message to potential contributors. We have strong requirements on the technical level of our developers. During the new maintainer process, we ask them to answer about 80 questions about Debian. We ask them to do grunt work. We review their reports twice (New Maintainers’ Front Desk, then Debian Account Manager). But even after we are totally satisfied about what they did, even after they became more qualified than many of our current DDs, we ask them to wait for months, so that the only person allowed to create accounts can finally do his “job”. It discourages the contributors currently in the NM process. I’ve seen several signs of frustration, or even depression. Some of them reduce their involvement in Debian, so we lose them before they even became Debian developers. Some of them consider resigning from the NM process. We should all feel guilty about that. But it also discourages people from joining Debian. Instead, they go to other more welcoming projects, which is totally understandable. Debian isn’t the only distribution with developers from the community those days. There’s Gentoo, Ubuntu, Fedora, openSUSE. Some of those have nice programs for new contributors, like “school” sessions. Sure, Debian is the “biggest” distribution without a company behind it. But is independance worth all the trouble? Of course, we have Debian Maintainers. DM is great for people who want to work on their packages. But, when we are trying to release lenny, we need more: people who are going to go through RC bugs, submitting patches. Who are going to do QA work. In short: people who care more about the whole distribution. Can we afford not recruiting anybody? Can we run Debian with the current manpower? I don’t think so. There are more than 550 RC bugs in lenny, many packages are currently blocked from migrating to lenny because they are RC-buggy, and many packages are orphaned or neglected. There are also a lot of bugs which haven’t been filed yet (I asked for help with running piuparts, which would probably result in 100-200 new RC bugs, but nobody had time to help). Most of the work that needs to be done is not rocket science. We could use a lot more manpower. Currently, the same small set of developers is doing most of the grunt work. They will get tired too. So, what can we do, as simple developers? There’s no magic solution, but we can try a few things.
  1. It seems that some people disagree that there’s a problem. Let’s prove them wrong: we could start a blog meme with “I, too, agree that the Debian accounts and keyring situation is severely hurting Debian, and that a solution needs to be found RSN.” It’s not going to solve the problem by itself, but it will at least show that we consider it very important. Pressure could help.
  2. We could start discussing solutions together. Our newly elected DPL said that he would talk with the problematic teams to determine how the situation could be improved. Unfortunately, this has been tried in the past (and failed). It might work this time, of course, but we could prepare a backup plan. So let’s find one or two good plans, and vote on them. (I liked the idea of giving accounts creation/management to DSA. After all, it’s only an sysadmin task once the report has been approved by FD and DAM.)
  3. We could push forward Josip Rodin’s proposal about infrastructure teams. It might not solve the DAM problem immediately, but would probably help avoid similar problems in the future.
Notes:
1. Maybe the 18 waiting accounts will be created today or tomorrow. Even if that happens, it won’t solve anything. Waiting 4 months for a simple administrative task is not acceptable, and we need to fix that problem anyway.
2. Account creation is not the only problem. Some people have been unable to upload packages or to vote for the DPL election, because their PGP key expired, and nobody updated it even if they have been asking for more than 4 months.

Stefano Zacchiroli: not my president

he is not my president I hereby declare that he is not my president, no matter of what (country, largest television group, football team, ...). While I'm at it, I also declare myself SABDPTIC (Self Appointed Benevolent Dictator Pro Tempore of the (Debian) Italian Cabal). Empowered by this charge I also declare that he is not the president of the various members of the (Debian) Italian Cabal either. I will not accept any counter statement, as I'm now the dictator. Now that I've declared this, I can happily resign from my role of dictator. Thanks for all the support messages I've received today by fellows around the world. Saddened. PS (ikiwiki permitting) the hyperlinks to my new non-president in this post are a good example of the usage of the rel="nofollow" microformat.

Lars Wirzenius: Stolen laptop, call home!

The Finnish computer magazine Tietokone has an article on stolen laptops calling home and the police using this to track down thieves. The article reads like a press release from the proprietary software company mentioned in the article, although perhaps that's just because it only mentions that one company. However, the main point is that by having the stolen laptop report its IP number, police can trace it and recover it. In the interest of helping Unix users have similar protection, I provide you with the following crontab snippet:
*/15 * * * * wget -q -O /dev/null http://your.home.page/call-home; true
That page does not need to exist, you just need to be able to access the httpd logs for the web server it accesses to be able to find out the IP number. By using a distinctive URL, you make it easier to grep. Perhaps someone would like to turn that into a Debian package? Add some debconf magic to specify the URL to access, and it should be easily usable. For all the people without a web site of their own, perhaps there would be people interested in operating a server people could use for that. (There's some privacy issues involved, but it's an opt-in thing, obviously, so that lessens them.) Now, to be fair, the proprietary software package mentioned does more than my cron job. For example, they can take control of the system remotely, and wipe it out and make it inoperable. Personally, I don't want that, since it's a huge security risk, but if that kind of thing interests you, you could enhance the cron job a bit. For example, it could download the file and verify that it's GnuPG signed with your key, and if so, execute it as a shell script. One of the risks with this is that if anyone ever happens to get a copy of a file you've made like that, say, your web hosting provider, they can put it there whenever they want to, and boom goes your laptop. I'm sure there are ways around that, but if you want the system, you'll have to solve that yourself.

Alexis Sukrieh: Backup Manager 0.7.7 is released

Yes I know, it’s like a year since the last development release of Backup Manager has been published, I should be ashamed of such a huge idleness. But actually, If you ask me, I’m not. Instead of writing long lines of haiku to apologize for being so late at releasing, here is an illustrated reason why it was so loooong. Good things come to those who wait

14 April 2008

Anthony Towns: A New DPL...

In a couple of days, DPL-elect Steve McIntyre takes over as DPL, after being elected by around four hundred of his peers… Because I can’t help myself, I thought I might poke at election numbers and see if anything interesting fell out. First the basics: I get the same results as the official ones when recounting the vote. Using first-past-the-post, Steve wins with 147 first preference votes against Raphael’s 124, Marc’s 90 and NOTA’s 19 (with votes that specify a tie for first dropped). Using instant-runoff / single transferable vote, the winner is also Steve, with NOTA elimited first and Marc collecting collecting 5 votes, Steve 4 and Raphael 2, followed by Marc getting eliminated with Steve collecting 50 votes, against Raphael’s 26. So, as usual, different voting systems would have given the same result, presuming people voted in basically the same way. NOTA really didn’t fare well at all in this election, with a majority of voters ranking it beneath all candidates (268 of 401, 53.5%). For comparison, only 18 voters ranked all candidates beneath NOTA, with 9 of those voters then ranking all candidates equally. (For comparison, in 2007, 312 of 482 voters (about 65%) ranked some candidate below NOTA, though that drops to 225 voters (47%) if you ignore voters that just left some candidates unranked. Only 98 voters (20%) voted every candidate above NOTA) With NOTA excluded from consideration, things simplify considerably, with only 13 possible different votes remaining. Those come in four categories: ranking everyone equal (17 votes, 9 below NOTA as mentioned above, and 8 above NOTA), ranking one candidate below the others (13 votes total, 7 ranking Raphael last, 3 each for Steve and Marc), ranking one candidate above the others (66 votes; 30 ranking Steve first, 18 each ranking Raphael and Marc first), and the remainder with full preferences between the candidates:
     70 V: 213
     63 V: 123
     56 V: 132
     52 V: 231
     38 V: 312
     26 V: 321
The most interesting aspect of that I can see is that of the people who ranked Raphael first, there was a 1.8:1 split in preferring Steve to Marc, and for those who preferred Marc first, there was a 2:1 split preferring Steve to Raphael. For those who preferred Steve, there was only a 1.1:1 split favouring Raphael over Marc. I think it’s fair to infer from that that not only was Steve the preferred candidate overall, but that he’s considered a good compromise canidate for supporters of both the alternative candidates (though if all the people who ended up supporting Steve hadn’t been voting, Raphael would have won by something like 26 votes (129:103) with a 1.25:1 majority; if they had been voting, but Steve hadn’t been a candidate, Raphael’s margin would’ve increased absolutely to 33 votes (192:159) but decreased in ratio to a 1:1.2 majority.

James Morrison: Niti days

I don't think any of these are mine, but this needs to be published to the general public (at least until it rests on AlumNit).

Poo Alliterations
- The Earl of Excrement
- The Duke of Dung
- The Prince of Poop
- The Sultan of Shit
- The Father of Feces
- The Matriarch of Merde
- The Steward of Stink
- The Dignitary of Dangleberries
- The Grand Poohbah of Grand Poo
- The Tyrant of Turd
- The Shogun of Scheisse
- The Baron of Bowels
- The Cardinal of Crap
- The Director of Dump
- The Surveyor of Stool
- The Lord of the Log
- The Crown Prince of Cow Patties
- The Royal Archbishop of Road Apples
- The Duchess of Droppings
- The Princess of Poodie
- The Legionnaire of Loaf
- The Supervisor of Stinkers
- The Pharaoh of Floaters
- The Magnate of Manure
- The Tycoon of TCPDumps
- The Czar of Czesspools
- The Mogul of Bowel Movements
- The Ruler of the Runs
- The Dean of Diarrhea
- The Royal Ringleader of Rump Raisins
- The Denizen of Doo-doo
- The Emperor of Evacuations
- The Headmaster of Horrible Odors
- The Titan of the Trots
- The King of Klingons
- The Big Boss of Bum Beans
- The Taskmaster of Turtleheads
- The Supervising Sovereign of Sewer Serpents
- The Colonel of Colon Cobras
- The Nobleman of Number Two
- The Top Dog of Toilet Twinkies
- The Kingpin of Keester Cakes
- The Shepherd of Sea Pickles
- The Head Navigator of Heinie Nuggets
- Rectal Representative
- The Commander of Cow Pie
- The First Mate of Fecal Matter
- The Creator of Cloth Touchers
- The Protector of Porcelan
- The Theologian of the Throne
- The God of Grunts
- The Small Insignificant Yodeling President of Shit in your Pants
- The Diaper Destroyer
- The Loader of Loincloths
- The Pontiff of Plum Pudding
- The Daiymo of Dysentery
- The Master of Montezuma's revenge
- The Squire of Squirts
- The [Weaver] of [WvLog]s
- The Primary Contact of Pudding Cookies
- The Best Producer of Brown Puddles
- The Senior Partner of Steaming Piles
- The Fine Baker of Fudge Brownies
- The Sheriff of Stench
- The Don of the Deuce
- The Torrid Putrid Tainted Pervert of Two-Ply Toilet Paper
- The Sacred Monarch of Skid Marks
- The Main Scientist of Microfeceological Studies
- The G.I. Joe of Gastro Intestinal Journeys
- The Premier of Polyps
- The Brigadier General of Bedpan Gold
- The Plunger Pilot
- The Specialist of Splashers
- The Foreman of Fake Farts
- The Ambassador's Under-Secretary of Astounding Unearthly Scents
- The Old Man and the Sea of Odiferous Monsters in the Sink
- The Bafflingly Blunt and Blasphemous Bearer of Big Bad Beastly Booty Burdens
- The Crisp Pungence of Chain Pooping
- The Goddess of Groundhogging
- The Burly Bobby's Brief Battle with Brim Blasting Bowel Bombs
- The Nasty Neighbour's Noisy and Nefarious Neglect of Normal Nasal Niceties
- The Judge Jury and Executor of Jolly Jumper Excrement
- The Forwarder of the Forwarded
- The Wizard of the Water-closet
- The Grunting Lobber of Great Logs
- The Annoyingly Arrogant Architect of Awful and Abhorrent yet Amazingly Aerodynamic Anal Atrocities
- The Dark, Dangerous and Delusional Dealer of Death-Defying Doses of Disturbingly Decadent Dung
- The Shakespeare of Sinfully Smelly and Supremely Scary Scripture with Soggy Stains and Screaming Splashes
- The Wise but Weakened Warlord Whose Willful Wrath Was Wholly Wrought With Wicked and Wretched Winds from Within
- The Languid and Lackluster Legend of the Little Log from the Loo and its Lavish Life of Luxury in a Lasagna
- The Kahuna of Kaka
- The Emergency Evacuator of Enraged Entrails
- The Squire of Sultry Stinknuggets
- The Deadening Discomfort of a Dearth of Dumps
- The Far From Favourable Fragrance of Four Fragments of Fantastically Fresh Feces
- The Principal of Prodigiously Putrid Pellets
- The Markedly Morose Maintenance of Maniacally Mounded Midden Movements and Mostly Meaty Meals Mysteriously Made Mushy
- The Crass and Cranky Coroner Connecting Clues Concerning a Cornucopia of Casualties Caused by a Crude Cluster of Completely Contemptible Colon Concoctions
- The Thinking Thoughts of a Thinker
- The Horrible, Hubristic Heathen Hoarding Hoary Humps of Hideousness Hailing from His Huge Hairy Heinie in His Harmfully Heady Hovel
- Inane Writings on Irritated Wreathing of the Incubator of Wrath
- That Special Numbness from Sniffing Noodled Stink Nougat
- The Moral Sanctity of the Mystery Shit
- The Ornery Opressor's Opulent Outpost Overseeing the Ordinary Occupants' Outrageous and Ongoing Observance Of an Occasional but Offensive Orgy Of Offal
- The Rector of Relief
- The Rectal Regurgitator
- The Shit Squat
- The Smelly Surprise
- The World Wide Wisdom
- The Slayer Supreme of System Shock

Alexis Sukrieh: Backup Manager 0.7.7 is released

Yes I know, it’s like a year since the last development release of Backup Manager has been published, I should be ashamed of such a huge idleness. But actually, If you ask me, I’m not. Instead of writing long lines of haiku to apologize for being so late at releasing, here is an illustrated reason why it was so loooong. Good things come to those who wait

Russell Coker: Fried Food

I’ve just been reading about oil deterioration when deep frying [1]. Apparently frying food can cause the production of Acrylamide [2] which causes cancer, is a neurotoxin, and does other bad things to your body. Deep frying in a vacuum [3] is a solution to this problem as the lower temperatures reduce the formation of the bad chemicals (and also increase the life of the oil thus making for cheaper fried products). Of course this means that deep frying in a pressure cooker as KFC does probably gives a result that is a lot worse for your health [4]. For some time I’ve been avoiding KFC due to concerns about the treatment of the chickens. I have been regularly eating fried chicken from a local store which looks and tastes very similar to KFC so presumably is cooked in the same way. I guess I’ll have to stop eating that now. I wonder if toast is also bad in this regard. I expect that sausages would be a problem when cooked on a BBQ. In other health news I’ve been reducing my meat consumption and I’m considering trying to entirely avoid farm raised animals to restrict my meat consumption to game meat, this should be good for my health and is also a lot better for the animals and the environment.

Kartik Mistry: Custom Keywords


* Accidently, I found this ‘Mozilla Custom Keywords‘ and tried with Debian BTS. It works. 1. Bookmark: http://bugs.debian.org/%s 2. Give it keyword: bugs (or whatever you want, like if you hate bugs, you can give it, ‘hate’ also…) 3. Type: bugs nnnnnn (where nnnnnn is bug number). Done. No need to type entire url or use broken search engines. Btw, this is really cheap hack, I need to really something cool that will bring some excitement in current boring life :P

Steve Kemp: So helpless against what is coming.

I've made a new release of the chronicle blog compiler. There are a couple of minor changes to the variables exported to the theme templates, as contributed by MJ Ray, and a new spooling system. This works in a simple fashion, and allows you to queue up posts. For example If you write a new entry containing the psuedo-header "Publish: 20th April 2008" and you have a crontab entry containing this:
  chronicle-spooler
    --spool-dir=~/blog/spool/  \
    --live-dir=~/blog/data/  \
    --post-move='cd ~/blog && make upload'
It works as expected. When you call this on the 20th April the file will be moved from ~/blog/spool into ~/blog/data, and your blog will be rebuilt & uploaded. The implementation was different than the original suggestion, but is nice and clean, and can be used to do other things with a little bit of effort. Anyway if you see this entry the spooling system is working! ObQuote: 30 Days of Night.

Lars Wirzenius: Linux-tekij 2008

I'm on the jury for the "Linux-tekij 2008" award. Roughly translated that means "Linux maker 2008". It's an award for a person or organization who has significantly advanced Linux development or improvided the conditions for Linux users in Finland. I'm on the jury as a Debian person, since the Finnish Debian community received an honorary mention two years ago. The nomination form is open, so anyone who has any a suggestion, send it in.

David Welton: Hecl Jacta Est

I don't know if androids dream of electric sheep, but I've certainly been losing a lot of sleep over Google's Android, and am glad that the Android Developer Challenge is winding up, as I've been doing all Android, all the time for the past month or so. I have greatly enjoyed working with Android, as it's much more capable than Java ME. It's still very much a work in progress, and only time will tell if Google and their partners are able to best current mobile programming systems... or if the web will simply obviate the whole thing, as it's doing in many other areas. Win or lose, I will continue to support Android as a platform that Hecl runs on, but in the meantime, I hope to go back and look at some less future-oriented code and get back to some Java ME work. More on that soon... In any case, here's hoping that the contest judges see the value in bringing a scripting language to mobile phones! I also hope to see actual hardware soon, as I'm really looking forward to getting my own Android phone.

Evan Prodromou: 25 Germinal CCXVI

I got my FON router delivered to my house about 2-3 months ago, but I didn't realize what it was until I was cleaning up my office to leave for Buenos Aires. Glad to have a project, I set it up on my home network while I was waiting for the taxi to the airport. I've only really started playing with it since we got back. FON is an international effort, originally based in Spain, to share extra network capacity with roaming wireless users. You set up a router in your home (or wherever), and any other FON user can connect to the Internet through your network. Conversely, you can connect on any other FON network. There is a lot of grass-rootsiness to FON, but it's a commercial project, which turns some people off. I originally heard of FON at Wikimania 2007, where FON provided wireless routers for each attendee's room. It was a nice service, although the doubled-up ESSIDs were kind of confusing at the time. They make a lot more sense for home use. I was impressed by how many FON spots there are on the Montreal/Plateau (see http://maps.fon.com/ for details); about one ever 2-6 blocks in any direction. I think there's an opportunity here to see a higher concentration, though. I'd love to see co peration between FON and, say, le Sans Fil, possibly involving the Ville de Montr al. Apparently there are already FON cities in different parts of Europe, so it's not impossible. I think FON is an interested development for WiFi -- a hybrid between community-based initiatives and a commercial venture. I'm not sure if it will be successful, but I think it's a step in the right direction. tags:

MJ Ray: I Can't Dance

My legs hurt. It hurts to sit. It hurts to stand. It hurts to walk. $DEITY knows what it will feel like to ride my bike. How did I do this? It wasn't some bizarre biking accident. I was laying cables under the floor between the two offices at the opposite corners of my building yesterday. I lifted three floorboards and four carpets and drilled one hole. Afterwards, I rebuilt some shelves. How did that hurt my legs??? Today is Blogger Appreciation Day [UNOFFICIAL] so I'd like to thank Steve for Chronicle which is now powering this blog instead of the old homebrew. Meanwhile, messages that came in while I was AFK included a strange one from Paul, Steve being elected as Debian Project Leader (well done!), 'Free Software in Ethics and Practice' - Richard Stallman, Thursday 1st May, Interview: How a hacker became a freedom fighter From New Scientist Print Edition, Understanding Design & Computers: Notes from an Introduction to OpenMoko, by Ole Tange for UKUUG Finally, in a cycling and cooperatives cross-over, this article on Hammond's crash also mentions the other two Brits, who ride for cooperative teams. I watched the race, but didn't see much of them.

Next.

Previous.