Search Results: "reg"

31 October 2008

John Goerzen: Biking in the dark, 45 degrees F

I've been telling people that I plan to keep bicycling into the winter. I think about half the people I've told to don't really believe it. And the last two weeks, I haven't been able to ride to work due to muddy roads and scheduling conflicts. But today I did.

I left while it was still dark and 45 degrees outside (7C for the Fahrenheit-impaired). I think that's the coldest bike ride for me yet. I wore my regular shorts, shoes, and socks. I had my regular shirt on, plus a long-sleeve thicker shirt on above it.

It was cold the first few minutes, but this was pretty much the right outfit. Once I got going and got some heat built up, I was doing fine. In fact, I had to unzip my outer layer because I was getting hot.

So. I figure that if I can do 45 with shorts, then I ought to be able to take on 20 with proper winter gear.

Either that, or I've now dug myself a nice big hole if I wimp out.

MJ Ray: Recent Events: London LinuxExpo, Toronto Free Software and Open Source Symposium, Public Sector Online, Get Online Day, the Global Financial Crisis, c&binet

Today’s the last day for the Gov.UK Consultation on Forced ISP Snooping: Please Say NO. I didn’t get to LinuxExpo, partly because of Monday Machine-Mangling Madness but I saw LinuxExpo 2008 Robert Castelo from the Drupal point-of-view. I also didn’t get to Public Sector Online (report by Andrew Lewin with links to more) and I definitely didn’t travel to Toronto, so the report on the Free Software and Open Source Symposium from Randy Metcalfe is pretty welcome. I wrote about the Social Enterprise Photography Competition and Cooperatives South-West Trade Fair last Friday - the photography competition deadline has been extended to 7 November. So you’ve still time to capture a vision of a more progressive approach to business that values people and the planet as well as profit. Last Friday was Get Online Day but TTLLP didn’t do anything for it this year - I took one look and reached similar conclusions to Graham Jones: Get online…! Oh - you are…! Related to that: on Tuesday, I got really annoyed about how many branches of government (national, regional, sub-regional and local) are obsessed about the private sector and are paying even less attention to other types of businesses, includingbuying off-the-shelf software which doesn’t conform to their stated policies about accessibility and interoperability. (Sorry if you saw evidence of that outburst… yes, local councillors are pretty powerless and get as annoyed about incompetent government services as everyone else.) It seems I’m not the only one feeling that good cooperative businesses are being overlooked. The ICA have recently sent an open letter to the Governments of the G-8 reminding them that co-operative financial institutions are an alternative secure, stable and sustainable model of business owned and controlled by people. Finally, a bit of advance notice here: “The inaugural Creativity & Business International Network (c&binet) will take place at The Grove in Hertfordshire from 26 28 October 2009” - is this something that free software and free culture supporters should get involved with? (And why did they pick a name that includes an XML special character?)

30 October 2008

Marc 'Zugschlus' Haber: Nagios, Parent Hosts, and traceroute on the Internet

Nagios has the - very useful - feature of “parent hosts”. If it deems a host A being down, it first checks its parent host, B, and reports A only as down if B is up. This goes back recursively until a host with state “up” is found and only the first “down” host is actually reported. This keeps on-call people from being bombed with alerts in case of major network outages and makes sure that the alerts that are actually sent out do reasonably accurately describe the actual outage. As an individual who has some “external” servers in various data centers on the Internet, I would like to not be alerted multiple times that my servers at ISP C, D, and E are down if there is an outage at the ISP F hosting my Nagios installation or at one of the various exchange points temporarily rendering the servers unreachable (without me being able to do anything). The solution sounds easy but is surprisingly hard. How one could solve the issue For each host in the manual nagios configuration, do a traceroute and generate host stanzas for each of the hosts found:
$ sudo traceroute -I icmp -n -A 213.239.240.200
traceroute to 213.239.240.200 (213.239.240.200), 64 hops max, 28 byte packets
 1  <snip>
 2  217.243.221.150 [AS3320]  1 ms  0 ms  0 ms
 3  62.154.10.106 [AS3320]  1 ms  2 ms  2 ms
 4  217.239.40.226 [AS3320]  51 ms 217.239.40.234 [AS3320]  3 ms 217.239.40.226 [AS3320]  60 ms
 5  193.159.226.2 [AS3320]  3 ms  3 ms  3 ms
 6  213.239.240.200 [AS24940]  6 ms  7 ms (TOS=238!)  8 ms
$
This sounds easy and surely can be accomplished in a few hundred lines of perl. However, this makes it necessary to parse Nagios configuration if one wants to obtain the list of configured hosts directly from there. Unfortunately, the syntax of Nagios configuration is “historically grown” which makes it quite illogical and awfully hard to parse - this would easily double the size of the traceroute-based configuration generator. Additionally, the (real) traceroute given above shows three other issues that might arise from such a setup. Dynamic Routing Network paths are not as static as a traceroute suggests. On the Internet, the ISPs use BGP to connect their networks together and to ensure connectivity. In case of network reconfiguration (which may be caused by desired technical or policy changes or actual failures), the traceroute to a given network host may change. Considerable experience is needed to judge whether a change in the traceroute is only short-term while one looks at it, or long term meant to stay. Of course, only long term changes should be reflected to Nagios configuration. The possibility of changes makes it necessary to distinguish between “manually” and “automatically” generated Nagios host entries and to have a mechanism to quickly re-generate the “automatic” entries according to the current situation found on the network. Alternative Network Paths If you look at hop 4 of the traceroute given above, you see two IP addresses. This is a common “one packet left, one packet right” setup where two identical lines are sharing the load and this one sees different interfaces of the next hop router. Which IP address should one put into the parent host declaration then? Later Nagios versions supposedly are able to handle multiple parents to a host, but the docs of course don’t cover this complex configuration and I didn’t yet find the time to find out how this mechanism works and whether it can be used to represent a network layout like that in Nagios. Unpingable Routers For some network operators, ICMP echo request packets (ping) pose a significant load on their network equipment. To remedy that load, they have disabled ICMP echo reply transmission on these machines to keep the load down. This makes the router still show up in a traceroute (as this is done by sending packets with short TTL values and making them expire in transit, resulting in an ICMP TTL exceeded message being sent back), but it cannot be pinged. Hop Number 5 on the traceroute above is such a box: It shows up fine in the traceroute, but pinging it will always return “DOWN”. Currently, I simply omit such hosts from the Nagios configuration, but this may result in extra and inaccurate alerts once the unpingable host itself fails. A different possibility would be to check the host’s availabilty by sending an appropriately TTLed packet either to the host itself or to a host that is “behind” that host. The latter introduces even more complexity since one needs to find out a host “behind” the unpingable box, but this may be necessary since in the case of Hop Number 5 above, the IP address of the hop does not even seem to be in AS3320’s internal routing and tracing to the hop itself stops well before the expected place of the host regardless of from where one traces. Conclusion This is a surprisingly hard issue if one wants to do network monitoring while generating accurate alerts. Surely, it’s a topic that needs to be addressed in network monitoring, so I am quite interested in how other people tackle this. Please comment! Thanks in advance.

Decklin Foster: A long-overdue explanation

Regarding that last post. I received the list via email from Alan Sondheim earlier in the week, and felt like putting up a link to it. No particular reason; it seemed appropriate for one of those sui-generis enigmatic tumblelog things. I was disappointed to find that none of the mailing lists where I might have been able to find it had public archives. (One way of dealing with people who complain about spammers harvesting their address, I suppose...) So, I said to myself, I've got 8+ years of this guy's email work, I'd like to share it with the world, and I have Mnemosyne, which I had always thought, in the back of my mind, would be a neat way to archive email written as email rather than written as a "blog". So, a little hacking later... The Alan Sondheim Mail Archive (Warning: some parts are NSFW). It has already given me some ideas for improving the example templates; I'll release 0.12 soon with the changes I had to make to get this running. (Final tally: 4500 messages, 75 seconds from a clean htdocs, 12 to no-op. On whatever the cheapest Linode [1] [2] is. Eh. I can do better.)
[1]Incidentally: Linode has been great. Highly recommended.
[2]Also: yeah, I know my footnotes are broken. Working on it.

MJ Ray: Dot-coop Domain Renewal Hell

Without emailing us in advance, UK.domains.coop just expired our software.coop domain on 29 October instead of 5 November. When I looked at the renewal option in the control panel, the fees have increased by about 30% since last year. I don’t remember being told that and it’s more than what was authorised at the last TTLLP members’ meeting. If I remember correctly, the old price for the dot-coop domain was already five times the price of our dot-UK - now it’s more like six or seven times. I’m sick of the service from UK.domains.coop. The services are owned and run by cooperatives, but it’s not one we can join, as far as I know. Their control panel is rented uncooperative software which doesn’t meet current accessibility standards - I have to reconfigure my browser each time I use it. The support has been a little slow and it’s apparently easy to configure a domain into a non-working setup that one can’t recover without help from the support staff. When I complained, it was suggested that we should work with them, but when I asked how, I never saw a reply. So, I’m transferring our cooperative domain to a non-cooperative registrar. The DotCooperation LLC is a wholly-owned subsidiary of the US coop federation and not a cooperative itself, so does it really matter? After working through a long list of registrars that claim to offer dot-coop domains and eliminating all those which only offer paper registrations (because I don’t want to wait for air-mail) or don’t appear to accept domain transfers, I was left with two and neither were cooperatives. I’ve picked one and only after ordering, I’m told it will take a week to transfer. Grrr. At least the support staff response was pretty quick. That means that these news pages are at a temporary URL for a while. Email to software.coop addresses and the main information pages are offline. If the registrar we’re using turns out to be any good and responsive to feedback, I’ll see if we can resell their services next year.

MJ Ray: Time to Re-Regulate the UK Mobile Phone Market

One of the things I wished for last month was a decent cooperative pay-as-you-go mobile phone service. About the same time, Ofcom started a social web consultation about mobile phone services. Now there’s an excellent presentation by Vivian Woodall, Chief Executive of The Phone Co-op that was given to FCS’ Comms Provider 08 event. Ofcom’s Mobile citizens, mobile consumers: the importance of mobile suggests the idea of re-regulating is “controversial”. I’ve left a comment there that asks why. It seems obvious to me that UK mobile phone service is currently a market for lemons - useful independent measurements are few and far between, there are no trial periods and it’s often expensive to change provider. Maybe it’s different in the big cities. Meanwhile, real complaints like An Orange-coloured hell, T-Mobile is the new Orange.. and Cancelling a Three mobile contract FAIL keep appearing with depressing frequency. Just how big does the FAIL need to be before Ofcom actually intervene?

MJ Ray: Time to Re-Regulate the UK Mobile Phone Market

One of the things I wished for last month was a decent cooperative pay-as-you-go mobile phone service. About the same time, Ofcom started a social web consultation about mobile phone services. Now there’s an excellent presentation by Vivian Woodall, Chief Executive of The Phone Co-op that was given to FCS’ Comms Provider 08 event. Ofcom’s Mobile citizens, mobile consumers: the importance of mobile suggests the idea of re-regulating is “controversial”. I’ve left a comment there that asks why. It seems obvious to me that UK mobile phone service is currently a market for lemons - useful independent measurements are few and far between, there are no trial periods and it’s often expensive to change provider. Maybe it’s different in the big cities. Meanwhile, real complaints like An Orange-coloured hell, T-Mobile is the new Orange.. and Cancelling a Three mobile contract FAIL keep appearing with depressing frequency. Just how big does the FAIL need to be before Ofcom actually intervene?

29 October 2008

David Welton: Linux in Sardinia

This was a pleasant surprise: La Sardegna adotta il software libero What that means is that the region of Sardinia (Sardegna, in Italian) will be adopting "software libero" for their IT infrastructure.

David Welton: Linux in Sardinia

This was a pleasant surprise: La Sardegna adotta il software libero What that means is that the region of Sardinia (Sardegna, in Italian) will be adopting "software libero" for their IT infrastructure.

David Welton: Sun's Java ME Marketing Blogs Going Off The Rails

Java ME has served me reasonably well as a platform to develop Hecl on over the years. It certainly has some problems, but it has two huge advantages: it's everywhere, and it's reasonably accessible, in that I can develop for it on Linux. Lately, all the buzz has been about the iPhone, and Android, and this seems to be irritating the guys at Sun who are tasked with creating interest around Java ME. Some of what they've been putting out in response is pretty weak. Look at this: http://blogs.sun.com/hinkmond/entry/google_phone_needs_work Don't they have better things to do than sitting around drawing dead Androids? Here are a few things that I can think of for them to be doing: Here's are a couple more "nyah nyah nyah" pieces. In this one he even quotes John "SCO has something on Linux" Dvorak: http://blogs.sun.com/hinkmond/entry/stop_the_gphone_madness_says http://blogs.sun.com/hinkmond/entry/i_love_google_because_google They're catching flack in the comments because of the attitude. The last post above is about how Google released a new Java ME version of their gmail application. Duh, of course they did; they want to make their stuff as widely available as possible, and no one disputes that Java ME is all over the place. But Sun can sit there and pat themselves on the back, or they can concentrate on what their vision of mobile programming for the future is. We know that Java ME is currently what's out there, and widely deployed. Pointing that out with regards to what Google is shipping is pointless. To be fair, there are plenty of posts are about interesting things they have going on, but there have been too many of these "mud slingers" about the competition, and it makes Sun look scared. Take the lead, show the stuff you're working on, tell us when we can expect it, show us the source code, show us the vibrant community, tell us about the events. Also, admit your mistakes. Everyone makes them - the difference is in how you deal with them. Tell us how you're going to improve stuff in the future so they won't happen again. Apple and Google have done some nice stuff with the iPhone and Android. If all Sun does is say nasty things about platforms that a lot of people are clearly interested in and like, it looks like they're out of touch with reality. The reality is that Sun does have good tech and good people, but they need to do a more effective job with what they have, and push a more positive message about what they're doing.

28 October 2008

David Welton: Sun's Java ME Marketing Blogs Going Off The Rails

Java ME has served me reasonably well as a platform to develop Hecl on over the years. It certainly has some problems, but it has two huge advantages: it's everywhere, and it's reasonably accessible, in that I can develop for it on Linux. Lately, all the buzz has been about the iPhone, and Android, and this seems to be irritating the guys at Sun who are tasked with creating interest around Java ME. Some of what they've been putting out in response is pretty weak. Look at this: http://blogs.sun.com/hinkmond/entry/google_phone_needs_work Don't they have better things to do than sitting around drawing dead Androids? Here are a few things that I can think of for them to be doing: Here's are a couple more "nyah nyah nyah" pieces. In this one he even quotes John "SCO has something on Linux" Dvorak: http://blogs.sun.com/hinkmond/entry/stop_the_gphone_madness_says http://blogs.sun.com/hinkmond/entry/i_love_google_because_google They're catching flack in the comments because of the attitude. The last post above is about how Google released a new Java ME version of their gmail application. Duh, of course they did; they want to make their stuff as widely available as possible, and no one disputes that Java ME is all over the place. But Sun can sit there and pat themselves on the back, or they can concentrate on what their vision of mobile programming for the future is. We know that Java ME is currently what's out there, and widely deployed. Pointing that out with regards to what Google is shipping is pointless. To be fair, there are plenty of posts are about interesting things they have going on, but there have been too many of these "mud slingers" about the competition, and it makes Sun look scared. Take the lead, show the stuff you're working on, tell us when we can expect it, show us the source code, show us the vibrant community, tell us about the events. Also, admit your mistakes. Everyone makes them - the difference is in how you deal with them. Tell us how you're going to improve stuff in the future so they won't happen again. Apple and Google have done some nice stuff with the iPhone and Android. If all Sun does is say nasty things about platforms that a lot of people are clearly interested in and like, it looks like they're out of touch with reality. The reality is that Sun does have good tech and good people, but they need to do a more effective job with what they have, and push a more positive message about what they're doing.

David Welton: Sun's Java ME Marketing Blogs Going Off The Rails

Java ME has served me reasonably well as a platform to develop Hecl on over the years. It certainly has some problems, but it has two huge advantages: it's everywhere, and it's reasonably accessible, in that I can develop for it on Linux. Lately, all the buzz has been about the iPhone, and Android, and this seems to be irritating the guys at Sun who are tasked with creating interest around Java ME. Some of what they've been putting out in response is pretty weak. Look at this: http://blogs.sun.com/hinkmond/entry/google_phone_needs_work Don't they have better things to do than sitting around drawing dead Androids? Here are a few things that I can think of for them to be doing: Here's are a couple more "nyah nyah nyah" pieces. In this one he even quotes John "SCO has something on Linux" Dvorak: http://blogs.sun.com/hinkmond/entry/stop_the_gphone_madness_says http://blogs.sun.com/hinkmond/entry/i_love_google_because_google They're catching flack in the comments because of the attitude. The last post above is about how Google released a new Java ME version of their gmail application. Duh, of course they did; they want to make their stuff as widely available as possible, and no one disputes that Java ME is all over the place. But Sun can sit there and pat themselves on the back, or they can concentrate on what their vision of mobile programming for the future is. We know that Java ME is currently what's out there, and widely deployed. Pointing that out with regards to what Google is shipping is pointless. To be fair, there are plenty of posts are about interesting things they have going on, but there have been too many of these "mud slingers" about the competition, and it makes Sun look scared. Take the lead, show the stuff you're working on, tell us when we can expect it, show us the source code, show us the vibrant community, tell us about the events. Also, admit your mistakes. Everyone makes them - the difference is in how you deal with them. Tell us how you're going to improve stuff in the future so they won't happen again. Apple and Google have done some nice stuff with the iPhone and Android. If all Sun does is say nasty things about platforms that a lot of people are clearly interested in and like, it looks like they're out of touch with reality. The reality is that Sun does have good tech and good people, but they need to do a more effective job with what they have, and push a more positive message about what they're doing.

27 October 2008

Decklin Foster: We could customer care less

(And now, a cathartic "I hate this company and I am never patronizing them again, please don't either" post. I should have done ones for at least Speakeasy/Covad and IBM's server division last year. Ah well.) I went to go register a new domain yesterday (announcement soon! Probably this weekend). I've been using Joker for a while, IIRC on the principle that the cooks were using it so it must be decent enough. While registering, I had a bunch of problems with the horrid, useless "Verified by Visa" popup [1] that you see everywhere these days, and eventually this must have looked like suspicious activity to the bank so my card was declined. I only actually found this out when I got mail saying my order was canceled. Okay, sure. I wrote back and explained what I thought was going on and that I'd like to resolve it. Another half hour later, I got this response:
Hello,
please use
   https://joker.com/goto/support/
for all support inquiries.
Regards, your Joker.com team
This is complete and utter bullshit [2]. If a company is going to mail me, I expect to be able to mail them. I have a mail client; it manages communication the way I want it to, and runs my preferred editor to compose messages (which is, in fact, how I am writing this very blog post). I am sick of dicking around on JavaScript-requiring web forms that all work differently and typing in postage-stamp-sized little textareas. Anything I do type in them is lost, because unlike my email client, web forms don't save sent messages unless the authors feel like letting you have a Cc:. When a company forces me to do this, I take it as a sign of disrespect. I tolerate a web browser [3] for reading pages; "applications" are universally painful [4]. One of the things I used to like about Joker was the PGP mail interface. AFAIK, they have not killed it (I didn't bother to check), but with automatic "we don't want to listen to you unless you inconvenience yourself" bounces like this, what's the point? I surmise that there is, or was, some smart person there who understood how (and more to the point, why) to hook a pseudo-mailbox up to a software system, and that they have been overridden by someone in management who realized it's much easier to have dime-a-dozen webmonkeys hook a form up to the same system since 90% of users just don't care (and even people who do notice and dislike this, but are not as inflamed as I, have come to expect it because everyone else refuses mail, so, y'know, pick yr battles son, etc.). Not the sort of culture I put faith my in. The irony of it all was that I was registering this domain to run a service I had decided to create specifically because of another site refusing mail and directing me to an even lamer web form. That would take incoming mail and, you know... process it with software. Suffice it to say, I am no longer going to be their customer. In deciding who to use instead, I figured I'd do a survey of where the domains in that "Subscription" column [5] on Planet Debian were registered, but... WHOIS is basically useless. Every server just returns free text, formatted differently by (apparently) every implementation under the sun. Cheaply parsing something out from .com/.org/.net is possible, but InterNIC kindly blacklists your IP after making more than a few requests in a few minutes. I guess I'm just gonna go with Gandi (but other suggestions would be welcome). In somewhat unrelated developments, I went to nic.at to update my nameservers for Where the Bus At? last week. There was no authentication or anything on the request form, so I just filled it in and sent it off. I got some automatic mail saying I need to print out a PDF, sign it, and fax it internationally. Annoying, and hardly as secure as mailing them with PGP, but whatever. But then, also yesterday, I got another mail saying the update was complete (lo and behold, it was). I am now somewhat concerned about the security of my domain: it seems like anyone can come by and put something in the form and if I'm not around to notice the courtesy mail and ask that they stop the request, it'll eventually go through, no questions asked. I have not yet written them to figure out what the deal is, though. Kinda burned out. I guess I didn't really have high hopes for dealing directly with a ccTLD registrar (this was the first time I've done it... I can't believe I blew 60 on a cutesy domain name) rather than a reseller who competes in a market, but then, I go and google "domain registrar" and look at all the AdWords dollars spent trying to compete with GoDaddy [6] and just kind of want to put my head in my hands. On DJB's DNS pages there's this bit about setting up a domain. It doesn't say "How to (buy register whatever) a domain name". It says, "How to receive a delegation from .com". Which is of course, how it works. And what I want to buy. I don't want "parking" or even gratis nameservers. Just a delegation from .com. Please. No AdWords came up when I googled for that phrase to copy the link. Sometimes I guess markets just sink to the bottom. Anyway. I feel like there's a free-software angle here. My continuing irrational hatred of using other people's forms, web-based mailing-list substitutes, nameservers, etc. stems not so much from their suckage but from the fact that there is no longer any software there, in front of me, for the four freedoms to possibly apply to. Being able to run your mail reader for any purpose doesn't win you much if no one uses mail. I don't really know what to do about this.
[1]It was only twelve dollars! If I go to hipster market or some other place with brand-new POS systems they don't even make me sign a paper slip for less than $20 or so. But this is the sort of thing dreamed up by people who think good security is setting a cookie to denote that I've answered "what was your first dog's name" or whatever. IF YOU WANT TO BREAK INTO MY BANK ACCOUNTS: I've set the answer to every single one of these questions to "security theater". Easy to remember.
[2]Not to mention a glaringly RESTless URI.
[3]Also, as a rule I normally try not to have anything up on my desktop that I can't close and re-open at any time, thanks to screen, MPD, emacsclient, actually using my browser's bookmark function and resisting the lure of tab-bar.js, etc. Web browsers are supposed to suck at preserving state; HTTP is stateless. See also here (and for further reading on that in the Haskell world, check out Yi. I'm hoping to switch to it someday).
[4]Debbugs, for example, may not have the slickest interface, but if I want to do flags, labels, archiving, threading, or whatever, I can; I'm not at the mercy of some front-end web developer. But we've all heard this litany before.
[5]Thanks, Hpricot!
[6]Even if GoDaddy's customer service were completely hacker-friendly, I would not use them, because their president Hates America.

Chris Lawrence: Newspeak, Yglesias style

I think this quote (regarding the California High-Speed Rail Initiative) is far more revealing than Matthew intends it to be:
[I]t seems to me that the sad reality of politics is that it would be irresponsible for advocates of any large-scale infrastructure project to do anything other than present unrealistically optimistic measures.
Translation into English: it would be irresponsible for advocates of at least some policies Matthew Yglesias prefers to tell the truth. Oxford’s New American Dictionary defines “responsibility to” as “a moral obligation to behave correctly toward or in respect of.” So Yglesias believes it would be immoral for advocates of some of Yglesias’ preferred policies to be honest. I’m glad we have that cleared up.

Joey Hess: I voted

I voted early because Sullivan County, TN is phasing in new voting machines this election. On election day, they will use the old touch screen system, while early voters get to test the "new" paper system. The new system is sure to please fans of paper. However, it has two flaws that were obvious to me. I have no way of knowing that my vote will be counted as I filled it out, and I realized half way through that election officials can determine how I voted. Here's why... You have two pieces of paper during the vote. A registration sheet is signed by the voter. A paper ballot has little rectangles that the votor fills in with a ballpoint pen in the privacy of the voting booth. The instructions say to fill in choices completely. Since the voting booths have a hard top, it's difficult to write on them with a ballpoint, let alone fill in little squares completely. The natural thing to do? Slide your second piece of paper under the ballot, so the pen can dig in better. If you don't think about it, you'll probably do this unconciously. Half-way through, I realized that I was leaving imprints on the registration paper, with my name on it, that corresponded to my choices on the ballot. Due to the two-column layout, and the distinctive spacing between different choices, it's possible to look at those imprints and determine exactly how I voted. The registration paper has to be handed in at the end, so the official who sits there all day collecting these has plenty of time to work this out and determine the votes of anyone. (I moved my ballot around and re-filled in squares to try to confuse things.) (Relatedly, one has to carry the paper ballot around the room to take it to the voting machine. It's difficult to keep the ballot obscured while doing this, since you can't fold it, and since they take the registration paper before the ballot, so you can't keep the ballot covered with it either.) The second obvious flaw is that once I fed my ballot into the voting machine, which presumably scanned it and put it in a safe, there was only a confimation that "you've voted!". There was no way to verify that it had counted my vote as I'd marked it.
Most voting system work seems to be in the direction of advocating paper ballots for paper ballots' sake. This doesn't seem like the right approach to me. Is no-one working on writing down the characteristics that an ideal voting system would have, and trying to make them all requirements? My take on requirements of an ideal voting system are:
  1. Only living people in the set of registered voters may vote.
  2. Each votor can only vote once.
  3. The votor should be able to verify that his vote was counted correctly.
  4. There must be a way for the votor to prove if his vote was not counted.
  5. The votor must not be able to prove which way he voted (to avoid payoffs, intimidation, etc).
  6. Others must not be able to determine how a votor voted.
  7. Individual votes must be retained to allow recounts.
  8. The entire vote data should be published so that the results can be verified by third parties.
  9. The system must scale to many millions of voters.
  10. The correctness of the entire voting system should be formally provable.
The paper ballot system I experienced today fails on at least points #2 [A] , #3 (see above), #4 (I walked away with nothing I can use to prove anything), #5 (I can video my vote), #6 (see above), and #8 [B]. At least it scales well though. The old touch screen system failed most of the same points, though it made at least a small attempt to satisfy #3 (by confirming the vote onscreen) -- and it failed #7, and probably scaled worse. Outside of the American election system, I've participated in voting systems that seem able meet requirements #1 [C], #2, #3, #4, #7, #8, and #10. To me, #10 is the most important point, but it seems to be the one that is neglected most. Some of the points may be worth weakening if they block other points. Is it really worth avoiding giving me something to prove how I've voted, and banning taking cameras into the polling place, in order to meet point #5, if this defeats point #4? I'm curious what requirments I may have left out too. My list is just a rough stab at it. The real point is to analyze voting systems, and reject ones that don't provably meet criteria. Until it becomes accepted practice to do that, our voting systems will not get appreciably less flawed.
[A] If you can get two copies of the ballot, you can vote twice ... fairly easy with a friend on the inside to arrange for the two copies to get "stuck together", and another one at the vote scanner to allow you to scan both. [B] The ballots could be published, but there's no way to prove all of them, or the true ballots would be. And in reality, they're either shredded, or locked away, or tossed in a dumpster, or variously all three. [C] Mostly. Perfectly accomplishing #1 is harder than most of the other points, and may be worth leaving out of scope.

Romain Beauxis: About democracy (revisited)

After my last post about the ongoing debate on the new process to accept and handle debian project members, Rapha l Hertzog proposed an alternative organisation which could be a solution, but misses the most important fact: how the people in charge of the process would be chosed and dismissed. Rapha l Hertzog wants that we consider a group of skilled and trustfull people in charge of giving and revoking powers to lower class of developers, on a per-event basis. Their procedure would be an internal vote amongst this group, and they would be called the "Debian Community Managers". Although it could be a good idea, it really misses the MOST IMPORTANT FACT: how they are chosed and to whom are they responsible. As a reply to my comment, Rapha l propose that they would be elected at first, and then nominated/revoked on the basis of the decision procedure mentioned above. Not only is it exactly what have been in place for the last years in the various core teams, but also it is a dangerous naive vision of how powers and regulations must happen. Before the Debian project started to consider these issues, the various ideas to build a system where the majority is ruled by a minority and the means to prevent the most important issues has already been studied, in the field of Law and how to write a Constitution for a democratic system. The goal of a democratic system is to put some higher power in the hand of several, but prevent as much as possible any issue. And preventing means act before shit happens, not after. Furthermore, power has to be divided into several domains, where the people in charge of these domains are strongly seperated and share as less common interest as possible. Hence, the goal of a constitution is to weaken power and put barreers, even if this leads to slow and frustrating reform processes. In the same idea, elections, which redraw the positions, are planed on a regular basis, and if the previously elected people were good, they are relected, not the opposite, in which if they aren't good they are dismissed. Again, we prevent issues, so the requirement to be responsible for what you did is implicit. And, last, it is well known that the less direct a decision process is, the less democratic it is. Hence, one should always prefer direct elections to indirect nominations. Now, coming back to Debian, we can have a very similar distinction in the various powers available: Now, the propositions, and all the various discussions are motivated by either the fact that there are issues with some developper's behaviour, which falls into the justice side and for which we already have a wide history of long debates before we act whatever the act is, or the executive power to give rights and introduce a new member in the project. Yes, we clearly miss a role in the project for applying rules and sanctions and deciding about these issues. However, we really ought to fix it the right way. In particular, never should we, in any way, give any justice power to someone in charge of any of the other power, in particular core teams. And the same for the right to appoint new members. For instance, to name an issue, the Frans vs. Sven issue would have been really different if there wasn't any kind of personal interest and power in the people in charge of the decisions. In real social systems, the right to apply a sanction or give new rights is a very dangerous power. It suppose a high level of separation between your personal interest, and the decision you have to make, as well as a high level of responsability against the people who trust you. We used to claim that Debian was not a democracy, but a meritocracy where technical skills are the ultimate ranking for deciding who's good or bad when giving reponsabilities. I have never been convinced by this approach, which I consider, just as anarchy, as valid for a small group of developers, but completely naive for a big group. Now, it is clear that the issues that we are dealing with in this situation have nothing to do with technical skills. In particular, the original proposition creates a class of non technical contributors, documentation writers, or translators etc... Furthermore, if you look back in the past, there have been a lot of situation where the issue, and its solution had nothing to do at all with technical issues, like issue mentioned above, or the Duck Tank or whatever it was called. We really should drop this naive idea that technicals skills are the only way to put on decision on the project. That is no longer how it works, nor a solution to the human issues that we face now.

26 October 2008

Chris Lawrence: Inside baseball

I’ve been remiss in pointing my readers recently to Zachary Schrag’s Institutional Review Blog, which patiently documents the overreach and misapplication of federal regulations regarding the protection of human subjects to the social and behavioral sciences, including research that by federal regulation is exempt from review by IRBs. While Schrag is cautiously optimistic that the new head of the Office of Human Research Protections will be an improvement, the continued domination of the process at most levels by biomedical researchers—along with the general sense that, as Schrag notes, “researchers cannot be trusted to apply the exemptions themselves”—is still troubling to those of us who want to conduct human subjects research, particularly secondary data analysis. Technically speaking (even though I dare say most social scientists observe this requirement in the breach), even the analysis of secondary data collected by others and fully anonymized before we see it (e.g. use of data such as the General Social Survey, American National Election Studies series, the Eurobarometer series, etc.) requires IRB oversight and approval beforehand.

Russell Coker: Links October 2008

Here’s a blog post suggesting that anti-depressant drugs such as Prozac may have helped the US mortgage crisis [1]. Apparently such drugs cause poor impulse control, so it wouldn’t be a good idea to attend a house auction while using them. Here’s an interesting idea about lecturing, give 20 minute talks with something else (practical work or group discussion) in between [2]. Michael Lee wants to “capture the power of that strict time limit, the intensity of a well-crafted 20 minutes”. While I’m not sure that a strict time limit is such a great idea. Having talks broken up into sections sounds like it has the potential to offer some benefits. A bible from the 4th century has been found and is being digitised [3]. When the digitisation is complete (next year) it will be published on the net so everyone can see how the bible has changed over the years. Interesting interview with Jim Gray (of MS Research) about storage [4]. It was conducted in 2003 so technology has moved on, but the concepts remain. His ideas for sharing two terabytes of data by using a courier to deliver an NFS or CIFS file server are interesting, the same thing could be done today with five terabytes for a lower cost. Techtarget has a white paper sponsored by Intel about the price/performance of data centers in low-density and high-density designs [5]. I don’t think I’ll ever be in a position to design a data center, but the background information in the paper is very useful. Google has an interesting set of pages describing their efforts to save power in their data centers [6]. They claim to have the most efficient server rooms ever built, and describe how it saves them a lot of money. One of the interesting things that they do is to use evaporative cooling as the primary cooling method. They also have a RE<C (Renewable Energy cheaper than Coal) project [7]. Here’s a Youtube video of an interesting presentation by Andy Thomson (a psychiatrist at the University of Virginia) about male-bonded coalitionary violence [8]. He shows the evidence of it in chimpanzees, humans, and evidence for it being in the common ancestry of chimps and humans (5-6 million years ago). He also shows a link to modern suicide bombing. It’s widely regarded that Cyrus is the fastest IMAP server. Linux-Magazin.de published an article last year comparing Cyrus, UW-IMAP, Dovecot, and Courier and the conclusion is that Courier and Dovecot are the winners [9]. I used Google Translation but the results were not particularly good so I think I missed some of the points that they were trying to make.

25 October 2008

Josselin Mouette: 5 days to win cookies

The Debian bug sprint has started! 27 players registered in the hope to win cookies. The list of players and their assignments can be viewed at the usual place. Good luck to everyone. NB: for those who wonder, the assigned bugs were chosen as the 27 oldest RC bugs without a patch and randomized with shuf.

Adrian von Bidder: Trying new technology

Since it's apparently en vogue to change one's way these days, I'm now learning Python (by looking at TurboGears and related technologies), using Emacs as my main editor (so far I was using mostly Perl and vim.) But while indenting with vim was often correct but occasionally annoying, I've found the much-touted autoindenting with Emacs disappointing. Yes, indent-region is cool, and if I hit tab on a line it indents it correctly, and using C-J instead of hitting enter also gives the right result. But why do I have to do all this? When I hit enter I want to have the new line at the correct indenting. When I start a line with “</” in a HTML file I want emacs to automatically run indent-for-tab-command on the closing “>” of this tag (or better yet immediately autocomplete the tag, since in XML there is only one tag to close, right?) (Oh, and btw: I've not found much about Python to dislike to date. So while my Emacs use might be just an episode, I might stick with Python as default scripting language for future projects for a while now. I thought about switching to git from hg as well in this “trying new things” effort but I think I'll leave this for later, since I've not had hg annoy me much so far.)

Next.

Previous.