Hi Joey,

One form of fraud that many people are unaware of and is often possible in paper voting systems is the selling of votes as follows:

1. steal a blank voting form, and fill it in as the vote buyer prefers
2. give that to a prospective vote seller
3. the seller then goes in to vote, and swaps the pre-filled and blank forms in the privacy of the voting booth.
4. the seller then returns to the buyer, and sells them the next blank ballot
5. repeat (in parallel) from step 1.

In the UK, the people running the ballot stamp the voting papers on the back as they hand them out in a way that allows them to recognise how long ago a ballot was handed out, and the folded paper is checked before it's allowed into the ballot box.

It is not clear from your post if this fraud would be viable in the system you just used.

Cheers, Phil.

They did remove a stub from the ballot and attach it to the registration form. I forgot to look at the stub to see what the point was. They may have stamped it that morning, or done so w/o me noticing. It's also possible they're printing the ballots on the fly, if so the stub might always have the current date. They may have checked this, quickly, before waving me on the the voting machine. But, I don't see how that would let them check that the ballot I turned in was the one matching the stub. --Joey

The datetime design pattern the microformats people came up with is similar, but uses ISO 8601 for the timestamp in the title attribute.

Use of an abbr element instead of a span will work, although there are accessability concerns with using abbr in the way the microformat is using it.

My javascript code cannot currently parse 8601 dates. The nice thing about the date format I'm using is it can piggyback on javascript's built-in date parser.

Also, html 5 actually has a time element, although it looks to me like there's no way to specify you want one to be displayed as a relative date. (My javascript could be adapted to handle them though.) --Joey

Umh... Well, I'm currently still using Awesome 2.3.4 - And I do have good system tray support.

From my .xsession:

/usr/bin/trayer --edge bottom --align right --expand true --widthtype request \
    --height 20 --tint 0x000077 --transparent true --SetDockType true &

Of course, it fits quite nicely in the least used portion of my bottom statusbar.

The standard says you are almost 40 foots away (If I remember well, they were 110 meters maximum from jack to jack)

IIRC the mathematics involved give a maximum cable length of ~136 meters (~445ft) based on ethernet timeouts vs propagation time.
Should be interesting to see if it works in practice...
-owen

Owen, perhaps I'll get lucky then, I'm under 445 feet. I figured there was some give in the 100 meter limit that's quoted everwhere. Was thinking about signal attenuation, but propigation time is a harder limit. --Joey

I certainly hated lua with ion, but I haven't invested the time to learn awesome yet. Seems like that might have been the right idea, or I'd have hit the same 2-3 issues you have (I never got as far as ion3, as all my barely-understood lua config files from ion2 failed to work in 3. History repeating?) -- ?JonDowland

---

Add to the list: Can't figure out how to duplicate tag 0 functionality. sigh.

---

The awesome mailing list is a great place to bring stuff like this up. It's a pretty young project still. Julien is pretty open to adding new features if they are good ones...

---

Ok, finally duplicated sending a window to all (numeric) tags:

keybinding({ modkey, "Control", "Shift" }, 0,
       function ()
          if client.focus then
         t = awful.tag.selected(client.focus.screen)
         for i = 1, keynumber do
            st = tags[client.focus.screen][i]
            if st and t ~= st then
               awful.client.toggletag(tags[client.focus.screen][i])
            end
         end
          end
       end):add()

(and wtf? I can't type a tab in FF? augh.)

If you are the original designer of alien, do you think, because of its experimental situation at the moment, alien will once - though perhaps very difficult - have a possibility - and possible with other programs - to convert an exe file into a deb or rpm file?

Ah, the joys of festivals. Can't make every show that's scheduled, and some of the unscheduled shows are even better... Had to miss Doc Watson to catch Otis Taylor's Black Banjo Project. Wish I could be there today to catch Dr. Ralph Stanley, but I have to prep class notes. If you see this in time, Medford's Black Record Collection is good if you like Southern Gothic...

I actually had access to internet over a cat5 ethernet cable a bit longer than 400 ft and it worked all right.

There are two limiting factors for the distance. Signal strength is a soft limit – it is guaranteed at 100 m (333 ft), so there has to be some reserve and as a result the signal is still usable at 150 m (500 ft). The other is collision detection – but that's not a problem if the link is operated full-duplex.

So if you make sure both ends are connected to either computer or proper switch, it should be workable at 400 ft. Also this cable I was using was lying on the roof and even hang from one roof to another and once again over ~20 m gaps (attached to support wire, but that means every meter or so) for at least two years and survived that, so having cable lying outside on the ground should not be a problem either.

–Jan Hudec

---

Both of those have been fixed in Ubuntu for at least a year, IIRC. If you could look at what they have done and adjust it to be done the right way (tm) a lot of people will be grateful, I think.

I've never used Ubuntu, but the fsck on my laptop doesn't run unless on AC power. Dunno. Worst case, just disable fsck altogether and run it by hand every few weeks.

from initscripts/2.86.ds1-21 [September 2006]:

• Add /usr/bin/ to the checkroot and checkfs PATH, to make sure on_ac_power is used if it is available. (Closes: #387308)

on_ac_power is in the powermgmt-base package (optional).

Those of us not well versed in very latest of Debian behind the scenes (but otherwise big fans of your software {etckeeper, ikiwiki to name a few} ) wonder why such a turn of events.

Suffice to say that there's no specific issue going on behind the scenes (or out in the open for that matter) in Debian that led to this decision. --Joey