This is an 
image, and this is a link.
+
+ GET /~neale/foo.html + Host: goob.woozle.org ++ +That's helpful, because I have a whole lot of hostnames all going to +216.39.146.229. The web server looks at the host header and pulls up +the appropriate page for that domain. My web server, thttpd, has an +easy go of this: it just goes into a directory called "goob.woozle.org". +Apache and other servers take a little more configuration, but in +practice aren't much more difficult to run. This concept of many names +pointing to the same IP address is called "virtual hosting". diff --git a/papers/digimatrix.mdwn b/papers/digimatrix.mdwn new file mode 100644 index 0000000..5c934ad --- /dev/null +++ b/papers/digimatrix.mdwn @@ -0,0 +1,299 @@ +[[!meta title="Debian on Digimatrix"]] + +
+ Caution: this is what I was running in 2004. Nowadays we just use + MythTV. Some of this stuff (like the X configuration) still applies, + though, which is why I'm leaving the page up. +
+ +Introduction +------------ + +We have a Digimatrix hooked up to our high-definition television. We +use it for a number of things: + +* Watching DVDs +* Playing music from OGG and MP3 files +* Recording and playing back television shows +* Storing pictures and movies from our digital camera +* Hosting our pictures and movies, along with those of our friends, + on a web server +* Playing Super Nintendo video games +* Occasional desktop tasks + +MythTV and Freevo vs. KDE +------------------------- + +This sounds like a MythTV box, right? I tried MythTV, and Freevo, and +while I was impressed with how pretty they were, I just couldn't get +them working quite right. + +[MythTV](http://www.mythtv.org/) gave a blank screen trying to watch or +record TV, with no useful error messages, and try as I might I just +couldn't figure out what the problem was. After spending three days on +it I gave up. + +[Freevo](http://freevo.sourceforge.net/) had its own problems; I don't +remember exactly what they were now. I do remember feeling like Freevo +was held together with bailing wire and chewing gum, while MythTV had a +much more polished and easy-to-use feel to it. + +Neither of them worked well out of the box with the Digimatrix remote +control. + +In the end, I decided it'd be easier for everybody if we just used KDE. +It lets me bind actions to the key sequences the remote control sends +out, and for most TV-type activities the remote does enough to move +around in [Xine](http://xinehq.de/) and +[Konqueror](http://www.konqueror.org/). The +[x2x](http://x2x.dottedmag.net/) program allows us to use our laptops to +control things over the wireless network, when the remote doesn't +suffice. The Unix `at` utility and a little shell script lets us +schedule TV recordings with more ease than a VCR. + +Best of all, there's no meta-information filed away in some obscure +database layout. Everything is a file somewhere and can be manipulated +with Konqueror or the shell. + +This turns out to be a very workable setup. + + +h2. Installing the base system + +I had to install the testing (etch) installation CD for it to have a +driver for the SiS 900 10/100 network card. Installation went smoothly +enough. Everything is detected at boot time except: + +* LED Panel and front panel buttons (including volume) +* Infrared reciever +* 802.11b card ([Ralink rt2400 chipset](http://rt2x00.serialmonkey.com/)). + While I've gotten the rt2400 drivers to work, the card won't seem to + associate with my WAP until some other device does it first. This is + so inconvenient that I've run a long CAT-5 cable under the house so I + can use the 10/100 ethernet port. + + +I installed the following additional packages to help me administer the +machine: + ++# aptitude install less zile screen ssh strace sudo ntp ntpdate ++ + +Web server +-------------- + +Waldorf needed to run a web server to host photo albums. + +
+# aptitude install mathopd stunnel4 php4-cgi rssh +# aptitude install netpbm jhead exiftran libjpeg-mmx-progs libjpeg-progs ++ +I won't detail my web server configuration here, since that's unique to me. + +X +---- + +
+# aptitude install x-window-system ++ +To my surprise this brought in x.org. I run an HDTV over DVI, so to get +full screen, I had to change the configuration as follows: + +
+Section "Device" + Identifier "Generic Video Card" + Driver "sis" + Option "ForceCRT1Type" "DVI-D" +EndSection + +Section "Monitor" + Identifier "Generic Monitor" + Option "DPMS" + HorizSync 30-65 + VertRefresh 30-60 + ModeLine "720p" 74.160 1280 1352 1392 1648 697 725 730 750 +EndSection ++ +I also had to add "720p" to the `Modes` of the `Display` subsection of +`Screen`. + +You may notice I only have 697 pixels vertically. That's because my TV +puts about 23 lines in the "overscan", preventing me from seeing my KDE +toolbar. I haven't yet found a way to recenter the screen, this just +chops off the bottom. As a hack, I put empty KDE toolbars on the top, +left, and right borders. This keeps windows inside the viewable area. + + +h2. KDE + +I like KDE. I've tried MythTV and Freevo and found it's just easier to +run KDE and occasionally use a mouse and keyboard. The only thing we +don't get is a snazzy interface to recording TV shows, but we don't tend +to want to do that very often. I may work on a web interface to XML-TV +listings later on. + +
+# aptitude install kde kdm ++ +I don't know if this is typical or not, but Debian's KDE went on without +asking me a single question. Kudos to the packagers. + + +h2. Sound + +
+# aptitude install alsa-base alsa-utils ++ +We use the Digimatrix's S/PDIF output (isn't it lame that it comes out +the front?). I know from a previous installation that if you just use +the defaults, you need to reboot between playing 2-channel audio and +using Xine's pass-through option to play a 7.1-channel DVD. I'm sure it +has something to do with the sound card resetting something or other. +The solution seems to be having ALSA multiplex audio, and while I don't +get why this works, work it does. + +I put the following into `/etc/asound.conf`: + +
+pcm.asus-hw {
+ type hw
+ card 0
+}
+
+pcm.!default {
+ type plug
+ slave.pcm "asus"
+}
+
+pcm.asus {
+ type dmix
+ ipc_key 1234
+ slave {
+ pcm "hw:0,0"
+ period_time 0
+ period_size 1024
+ buffer_size 4096
+ rate 48000
+ }
+}
+
+ctl.asus-hw {
+ type hw
+ card 0
+}
+
+
+h2. A decent desktop
+
+At this point I was able to browse the web and play music using KDE's
+"JuK":http://developer.kde.org/~wheeler/juk.html, so I took a break to
+dance around the living room with my 1-year-old daughter as ABBA sang to
+us.
+
+
+h2. Playing DVDs
+
+I like kaffeine, mostly because it's part of KDE and I'm a purist. It
+can play all sorts of movies and even has a nice startup screen that
+allows you to type in numbers for various actions (play from playlist,
+play DVD, etc.).
+
++# aptitude install kaffeine ++ + +### DVD's Content Scrambling System ### + +For some reason the DVD guys thought putting an encryption scheme on the +DVD was going to slow down piracy. I don't see any evidence of that +happening, but because of stupid laws in the US, you have to install +illegal software (as in, illegal to own) in order to watch the DVDs +you've bought or rented. To become a criminal, just run the following +commands: + +
+# wget http://www.dtek.chalmers.se/groups/dvd/deb/libdvdcss2_1.2.5-1_i386.deb +# dpkg -i libdvdcss2_1.2.5-1_i386.deb ++ +The version and/or URL may have changed since I wrote this. Apologies +in advance. + + +### DVD drive speed ### + +Linux does not use DMA on IDE devices when it boots up, you have to turn +that on yourself. I'm not sure what the reason is for this, probably +compatibility with some ancient thing that blows up if you attempt DMA. +In any case, turning on DMA will allows your DVD drive to keep up with +the data on the DVD. + +
+# aptitude install hdparm ++ +To turn on DMA, I put the following at the end of `/etc/hdparm.conf`. +While I was at it, I turned ot DMA for the hard drive too. + +
+/dev/dvd {
+ dma = on
+}
+
+/dev/hda {
+ dma = on
+}
+
+
+
+### Try a DVD ###
+
+At this point I was able to watch DVDs, so I did. I watched the first
+DVD of the first season of Buffy, which turned out to be a terrible idea
+since it's pretty dark and not very high quality. I played around with
+the gamma settings in the KDE configuration tool, and set my gamma at
+1.25. Then I adjusted the brightness, contrast, and saturation of
+Kaffeine, and got what I think is a pretty nice-looking configuration.
+
+
+
+h2. The remote control
+
+What good is a home theater system if you have to get up off your butt
+to press buttons? This is America, man! I want to be able to eat
+cheez-doodles and watch porn all night without having my feet hit the
+floor, ever.
+
+### The keyboard thingy ###
+
+My Digimatrix came with this IR receiver thingy that goes in between the
+keyboard and the keyboard port on the Digimatrix. It synthesizes
+keypresses in response to your remote. Pretty slick! This is good
+enough for most things, and for a long time I just bound remote
+keystrokes to do certain things in KDE applications, and to certain
+actions in Xine.
+
+### lirc ###
+
+lirc is the Linux Infra-Red Control system. It provides a standard
+interface to various IR recievers and remote controls, and supplies
+events to whatever wants to listen to it. KDE has a module to listen to
+it, so I figured I'd give it a go.
+
++# aptitude install kdelirc ++ +Unfortunately, lirc 0.7 (the version in debian testing and unstable) +does not compile on Linux 2.6.12 and newer, so I had to install from +source code. + + diff --git a/papers/html-tutorial.html b/papers/html-tutorial.html new file mode 100644 index 0000000..0e84f3d --- /dev/null +++ b/papers/html-tutorial.html @@ -0,0 +1,110 @@ +[[!meta title="The 3-minute HTML tutorial"]] + +
As computer formats go, HTML is really easy and logical. It's all just +text that you can edit with any basic text editor, like gedit nder +Gnome, or notepad in Windows. Let's start out with an example. Say you +have a sentence, and you want one word in it to be bold. That sentence +would look like this:
+ +Guess which word is <b>bold</b>?+ +
As should be obvious, the bold word in that sentence is "word". Just
+kidding, it's the word "bold", in between <b> and </b> tags.
+The sentence will show up like so:
Guess which word is bold?+ +
You now know HTML, the rest is just learning the names of the tags.
+ +Seriously! Here's a slightly larger example:
+ +<title>My first web page</title> +<h1>Welcome</h1> +<p> + Welcome to my <b>first ever</b> web page! + It features: +</p> +<ul> + <li>A title!</li> + <li>A header!</li> + <li>A paragraph!</li> + <li>An unordered list!</li> +</ul> ++ +
So what you end up with in the end is something like this:
+ +++ ++++ My first web page - WoozWeb Browser ++Welcome
++ Welcome to my first ever web page! + It features: +
++
+- A title!
+- A header!
+- A paragraph!
+- An unordered list!
+
The part inside the <title> and the </title> is the title of your
+page; that's what goes in the window frame at the very top of your web
+browser window, above the menus and everything else.
The stuff in between <h1> and </h1> is a "level-1 header". That
+means that it's the biggest header you can get. There are also h2, h3,
+h4, h5, and h6 headers, with h6 being the smallest.
The stuff inside <p> and </p> is a paragraph. Since HTML treats
+spaces the same as line breaks, you need to use paragraph tags around
+each paragraph. Inside the example paragraph is our old friend bold.
Then, there's <ul> and </ul>, an "unordered list" (as opposed to an
+ordered list, which would have a number by each item). Inside the list
+are four "list items", enclosed in <li> and </li>.
Now check this action out:
+ +<p> +This is an +<img src="http://www.woozle.org/images/star.png" + alt="star"></img> image, and +<a href="http://woozle.org/">this</a> is a link. +</p> ++ +
Which will show up like this:
+ +++ +This is an
The example above has an image tag, with two "attributes", "src" and
+"alt". The "src" attribute in an <img> tag gives the
+URL to a picture, and the "alt" attribute is the text that's displayed
+to people who can't see images (blind users, folks without graphics
+capabilities, or if there's a problem on your web server). The "alt"
+attribue is required, but you can set it to "" if there's
+nothing appropriate for alternate text.
Lastly, the infamous link, enclosed inside of <a>
+and </a>. The "href" attribute gives the URL that
+the browser will go to if you click the link.
That's it for basic HTML, and it should be enough to get you started +writing your own pages. So go write something! The best way to learn +it is to try stuff out and see what it does. For more neat HTML tags, +check out HTML 3.2 by +Examples, which is what I used to learn HTML.
diff --git a/papers/reply-to-still-harmful.mdwn b/papers/reply-to-still-harmful.mdwn new file mode 100644 index 0000000..87d153e --- /dev/null +++ b/papers/reply-to-still-harmful.mdwn @@ -0,0 +1,170 @@ +[[!meta title="“Reply-To” Munging Still Considered Harmful. Really."]] + +An Earnest Plea to People Still Having This Debate +-------------------------------------------------- + +A long time ago, Chip Rosenthal wrote a fine document entitled +['Reply-To' Munging Considered +Harmful](http://www.unicom.com/pw/reply-to-harmful.html). It details the +problems caused by `Reply-To` munging. Chip's essay basically points +out that: + +* Munging only helps people with broken mail clients. +* Munging can catch people by surprise, since in every other email + they've gotten with multiple recipients, when they hit "reply" it goes + only to the sender. +* Munging totally breaks things for people who want replies to go to a + different address than the one they sent the mail from. + + +In 2000 (or maybe earlier), Simon Hill wrote a response called [Reply-To +Munging Considered +Useful](http://www.metasystema.net/essays/reply-to.mhtml), which is +frequently offered as a rebuttal to Chip's document in online debates. +Simon's response boils down to the following: + +* Munging encourages list discussion. +* RFC 822 seems to indicate it's okay. +* Munging makes things easier on broken mail clients. + + +People still using these two documents to debate the issue are wasting +everybody's time. The issue was definitively settled in 2001, and Chip +won. + + +The IETF settles things +----------------------- + +The IETF (Internet Engineering Task Force) writes the standards +documents for the Internet. Such a document, called an RFC (Request For +Comments), attempts to unambiguously lay out in English the way things +are supposed to take place. They are deliberated intensely, sometimes +for years, and every paragraph is scrutinized by scores of experts. +Still, problems do crop up with RFCs over time, be they from +ambiguities, new technologies, or flat out mistakes. If problems are +big enough or numerous enough, the IETF will issue a new RFC to correct +the deficiencies of an older one. This new document is said to +_obsolete_ the old one. + +Both Chip's and Simon's documents refer to RFC 822, "Standard For The +Format Of ARPA Internet Text Messages", issued way back in 1982, before +most of us even knew what a computer network was. Indeed, RFC 822 +doesn't say anything about whether or not mailing lists can or should +set the `Reply-To` header field. Chip interpreted it one way, and Simon +another. + +In April of 2001, the IETF issued af new document, [RFC +2822](http://www.ietf.org/rfc/rfc2822.txt), which obsoletes RFC 822. In +this new RFC, the author addresses the `Reply-To` header field in a few +places, but the most relevant to this discussion is the following in +section 3.6.2 "Originator fields": + +> When the "Reply-To:" field is present, it indicates the mailbox(es) to +> which the author of the message suggests that replies be sent. + +Your list software is not "the author of the message", so it must not +set or in any way meddle with the `Reply-To` header field. That field +exists for the author and the author alone. If your list munges it, you +are violating the standard. + +These standards are not written flippantly, they are carefully crafted +in such a way as to ensure everything on the Internet works as smoothly +as possible. So do the Internet a favor and leave `Reply-To` alone. + + +How to specify where to post list messages +------------------------------------------ + +[RFC 2369](http://www.ietf.org/rfc/rfc2369.txt) specifies, in section +3.4, the `List-Post` header field: + +> The List-Post field describes the method for posting to the list. +> This is typically the address of the list, but MAY be a moderator, or +> potentially some other form of submission. For the special case of a +> list that does not allow posting (e.g., an announcements list), the +> List-Post field may contain the special value "NO". + +Modern mail list software sets this header field, or provides some +mechanism for the administrator to set it. + +Mail clients are beginning to act on it too. The KMail program Simon +references uses the presence of this header field to make the "reply" +action send to the list and the list only, and provides a "reply to +author" action that will always send to the message's author whether +it's a list or not. "Reply to author" honors the `Reply-To` field. +This is exactly the convenient behavior Simon claims to want in his +essay, and it can all be done using standard behavior. + + +Getting two copies of the same email +------------------------------------ + +Some people complain that they'll get two copies of the same email. +Since they're on the list, their first copy is the one sent to them by +the list. When the responder hit "reply all", it also put their email +address in the recipient list, so they get a second copy directly. + +Fortunately, there's already a technical solution to this. Since all +mail clients put a unique `Message-ID` header field on their email, a +mail reader has only to compare the `Message-ID` of a message to +previously-recieved messages. If it's the same, then the second message +is a duplicate and can be safely ignored. + +If your mail reader doesn't do this, that's too bad, but it's not an +excuse to violate Internet standards and surprise people with +inconsistent behavior, just to prevent you from having to delete a few +emails. Anyone who gets any spam at all knows how to delete email. + + +It's What People Want +--------------------- + +I can't tell you how many `Reply-To` munging lists I've been on where +someone (or multiple people) send private messages to the list by +accident. "But I hit reply, not reply to all!" I've even been bitten +by this, right after a message to the list chiding people for sending +private messages to the list! + +People want their mail client to be consistent. When they hit "reply" +they want it to go to the person who wrote the message. When they hit +"reply to all", they want it to also go to everyone who received it. +Most people understand this by now, since it's how their mail reader has +worked for every email they've ever gotten. Your list shouldn't be any +different. + +Sure, mistakes are going to happen, maybe on your list, maybe with an +email with multiple recipients. It's not your job as a list owner to +make sure people can't make mistakes with their software. If the job +belongs to anybody other the user, it'd be the author of the mail +client. Your job is to make sure your mail list follows Internet +standards, and as a result works consistently for the user. + + +Summary +------- + +Some people want to munge `Reply-To` header fields. They believe it +makes reply-to-list easier, and it encourages more list traffic. It +really does neither, and not only is it a poor idea but it's forbidden +by Internet standards. + +The IETF has spoken, and if you violate their standard and munge your +`Reply-To` header fields you're just creating problems for everybody. + +----- + +References +---------- + +* ['Reply-To' Munging Considered + Harmful](http://www.unicom.com/pw/reply-to-harmful.html) +* [Reply-To Munging Considered + Useful](http://www.metasystema.net/essays/reply-to.mhtml) +* [RFC 822](http://www.ietf.org/rfc/rfc822.txt): _STANDARD FOR THE FORMAT + OF ARPA INTERNET TEXT MESSAGES_ +* [RFC 2822](http://www.ietf.org/rfc/rfc2822.txt): _Internet Message + Format_ +* [RFC 2369](http://www.ietf.org/rfc/rfc2369.txt): _The Use of URLs as + Meta-Syntax for Core Mail List Commands and their Transport through + Message Header Fields_ diff --git a/papers/sockets.mdwn b/papers/sockets.mdwn new file mode 100644 index 0000000..13b365a --- /dev/null +++ b/papers/sockets.mdwn @@ -0,0 +1,132 @@ +[[!meta title="Introduction To TCP Sockets"]] + +Client Sockets +-------------- + +Sockets are sort of like PBX phone systems, where the IP address is +the phone number, and the port is the extension. Every paired +(connected) socket has a source IP/port and a destination IP/port. + + +When you want to hook up to a listening server, first you have to +request a socket from the kernel. You use the socket() call. In +Python, that'd be: + ++ import socket + s = socket.socket(socket.PF_INET, socket.SOCK_STREAM) ++ +That tells Python that you want a socket in the Internet class (as +opposed to, say Appletalk), and that it should be a streaming +socket (TCP, as opposed to a datagram socket, which would be UDP). + +The next thing you can do is tell the kernel what IP/port you'd like to +use as the source port (think of this as the number that will show +up on caller ID when you make your connection). You can do this +with the bind() call, like this: + +
+ s.bind(("192.168.4.216", 9234))
+
+
+This tells the kernel to use the IP/port of 192.168.4.216 and 9234. When
+you make an outbound connection, it will come from that IP and that
+port. You can use 0 for the IP and 0 for the port, in which case
+the kernel picks one for you. Or you can skip the bind call
+entirely, which is the same as binding to `('', 0)`.
+
+So you've got a socket and it's bound to something, now all you
+have to do is connect it (make your phone call). In Python:
+
+
+ s.connect(("192.168.4.12", 80))
+
+
+That'll hook you up to port 80 (the HTTP port) of 192.168.4.12.
+
+From then on you can use s just like it was a file, with read and
+write replaced with send and recv (I think you can actually use
+read and write on sockets, but traditionally send and recv are used):
+
+
+ s.send("GET / HTTP/1.0\n\n")
+ print s.recv(8192)
+
+
+When you're done, just close it:
+
++ s.close() ++ + +Server Sockets +-------------- + +Since a server operates on a IP/port combination too, you still do the +socket and bind calls (and you can skip the bind if you want any random +port, but I've never heard of a server that doesn't care what port it's +listening to). Then the next thing you have to do for a server, instead +of connecting, is listen. In Python: + +
+ s.listen() ++ +That tells the kernel to start listening for incoming connections +to the IP/Port you got with bind. + +Once you get a connection set up in the kernel, you have to ask the +kernel for that connection. That conenction will be a different file +descriptor than the one you had listening, so that you can have multiple +connections plugged in to the same ip/port and keep them all distinct. +The call you make to the kernel is "accept" and by default it will block +(that is, the kernel won't return control to your program) until there's +a new socket established. So you'll see loops like this: + +
+ while 1:
+ c = s.accept()
+ cli_sock, cli_addr = c
+
+ cli_sock.send("Hello, person from %s" % cli_addr)
+
+
+So there, you are accepting from s, it puts the new socket in c. Python
+does a little trick here, in that it actually returns a tuple (like a
+list) with the first value the actual socket, and the second value the
+address (ip/port) of the incoming connection. So you don't have to ask
+again to find out who just connected to you, get get it with the accept
+call. The C library does this in a slightly different way, but you
+still get the same information. And at that point, you can start
+treating the client socket just like you would any other connected
+socket.
+
+
+Forking for fun and profit
+--------------------------
+
+The code above is the serializing (FIFO) model, but you'd need to
+fork to handle multiple requests simultaneously. In practice,
+hardly anything serializes requests, what's more common is
+something like this:
+
++ while 1: + c = s.accept() + if os.fork(): + c.close() + else: + do_client_stuff(c) + c.close() + exit(0) ++ +If you're just learning sockets, do a serialized socket first. It'll be +easier to understand what's going on that way. But forks are easy too. +You call fork() and then you get a new process that starts with the same +everything (all the variables are the same and it starts running right +after the fork() call). After the fork, both are running as if the fork +has just completed, but the parent's fork returned the PID of the new +process, and the child's fork returned 0. diff --git a/poems.mdwn b/poems.mdwn new file mode 100644 index 0000000..9fdf894 --- /dev/null +++ b/poems.mdwn @@ -0,0 +1,7 @@ +[[!meta title="Poems"]] + +If wishes were horses +And poets were kings +I guess I'd still have my day job. + +[[!map pages="poems/*" show="title"]] diff --git a/poems/bagel-girl.mdwn b/poems/bagel-girl.mdwn new file mode 100644 index 0000000..74d01b5 --- /dev/null +++ b/poems/bagel-girl.mdwn @@ -0,0 +1,25 @@ +[[!meta title="Ode to the Bagel Girl"]] + +We stand waiting for the 253 to Redmond +The fog sits lightly on our tongues +Cigarette smoke blending in + +I walk to catch a glimpse of the bagel girl +(who works the second shift, +from noon to eight on weekdays). + +Oh bagel girl, make me a cappucino. +Brew the espresso dark and heavy +Froth the milk thick and heady. + +Tell me you love me, bagel girl. +Ride away with me +Into a cream cheese sunset. + +---- + +I wrote this on the bus home. There was a young girl with a beautiful +face sitting at the front of the bus, and I kept looking at her before I +started to write. I was laughing so hard as I wrote this, that she +started to get pretty self-conscious. + diff --git a/poems/double-dactyl.mdwn b/poems/double-dactyl.mdwn new file mode 100644 index 0000000..3ba8141 --- /dev/null +++ b/poems/double-dactyl.mdwn @@ -0,0 +1,11 @@ +[[!meta title="Double Dactyls"]] + +Hoobimus Goobimus, +Emad El-Haraty +“Please call me Fishmael” +said to #tron. + +But for the myriad +nicks in the channel list, +characteristically, +they were all gone. diff --git a/poems/ducks.mdwn b/poems/ducks.mdwn new file mode 100644 index 0000000..5243899 --- /dev/null +++ b/poems/ducks.mdwn @@ -0,0 +1,21 @@ +[[!meta title="Ducks"]] + +If ducks ran the country, I'm sure you'll agree +Things sure would be different for you and for me! +For starters, we'd live near a pond or a lake +On your birthday, you'd have to eat fish, and not cake. + +At lunchtime we'd all go eat grass under trees. +For snacks we'd have quackers, without any cheese. +We'd waddle around from point A to point B, +and when going in groups, we would all form a V. + +We wouldn't wear raincoats in winter or fall, +But then, I suppose we'd wear nothing at all. +Every person on earth would be covered with down +And I bet that would make it much harder to drown. + +If ducks ran the country, it sure would be strange. +And everything we find familiar would change. +I don't think I'd like it. No, not in the least. +But it still would be better than if it were geese. diff --git a/poems/goldfish.mdwn b/poems/goldfish.mdwn new file mode 100644 index 0000000..8d749df --- /dev/null +++ b/poems/goldfish.mdwn @@ -0,0 +1,8 @@ +[[!meta title="My Goldfish Wish"]] + +I wish a goldfish were my pet! +I'd make sure he was warm and wet. +I'd keep him in the kitchen sink, +And wash him when he starts to stink. + + diff --git a/poems/lake.mdwn b/poems/lake.mdwn new file mode 100644 index 0000000..5ba90da --- /dev/null +++ b/poems/lake.mdwn @@ -0,0 +1,10 @@ +[[!meta title="Poem For A Moonlit Lake With City Lights Reflecting"]] + +It, +is getting, +dark. + +---- + +Written while leaving dance class at Madrona Park; August 10, 9:07pm + diff --git a/poems/mice.mdwn b/poems/mice.mdwn new file mode 100644 index 0000000..4163c72 --- /dev/null +++ b/poems/mice.mdwn @@ -0,0 +1,31 @@ +[[!meta title="Ode to Mice"]] + +Leave them mice alone +Let them wander through your home +Eat little holes into your walls +Let them scamper up and down the halls + +Leave them mice alone +Let them grow up on their own +Give them places for mousey beds +Protect their little mousey heads + +And sometimes late at night +When you and your boyfriend had a fight +Those little mouseys, they just might +Not give a damn + +But when you curl up in bed by yourself +And you're hoping that somebody else +Can feel your anguish, up there on the shelf +They'll be eating SPAM + +So leave them mice alone +Leave them lots of styrofoam +And sweaters, and pink insulation stuff +Make sure that they have enough + +Leave them mice alone +Don't call the Orkin man on the phone +Those little mouseys +They are your friends diff --git a/poems/optimized.mdwn b/poems/optimized.mdwn new file mode 100644 index 0000000..84c58d5 --- /dev/null +++ b/poems/optimized.mdwn @@ -0,0 +1,26 @@ +[[!meta title="Optimized"]] + +This poem made for Wooz-Web 8 +So please download today. +On my computer, it looks great! +On yours, it might turn gray. + +It uses ActivePoetry +(By WoozleSoft, v4.3) +And fonts from [here](#), and [here](#), and [here](#); +Without those fonts, it sucks, I fear. + +You'll need a 3-D graphics chip +To see the verses do a flip; +A hundred gigabytes of RAM +(unless you want your mouse to jam) + +Get MarcoMuddy SlickWave Bash +If you don't want the rhymes to crash +And please be sure to maximize +So that the meter can resize. + +I'm sorry if you cannot see +This interactive poetry +But I just cannot take the time +To make my poems sound good on every browser! diff --git a/poems/poopy.mdwn b/poems/poopy.mdwn new file mode 100644 index 0000000..b1dd97b --- /dev/null +++ b/poems/poopy.mdwn @@ -0,0 +1,44 @@ +[[!meta title="The Poopy Song"]] + + + +I had a baby Ginnie +She liked to poop a lot +And when it came out of her butt +The temperature was hot + +She liked to poop her diapers +The smell was never strong +And when she pooped them really good +Her dad would sing a song + +### chorus ### +Poopy Poopy Poopy +Poopy all day long +Poopy Poopy Poopy +This is the Poopy song +(repeat) + +This little baby pooper +She liked to bounce and dance +And when you least expected it +She’d up and poop her pants + +She’d poopy in the morning +She’d poopy in the night +If she went long between her poops +You knew things weren’t right + +[chorus] + +Her poop was many colors +Like yellow, brown, and green +Sometimes she made so much of it +It made you want to scream + +She always pooped for pleasure +She never pooped for spite +If poop were good and evil, then +She’d poop for what was right + +[chorus] diff --git a/poems/sap.mdwn b/poems/sap.mdwn new file mode 100644 index 0000000..70646a6 --- /dev/null +++ b/poems/sap.mdwn @@ -0,0 +1,21 @@ +[[!meta title="Sap"]] + +I love you dear, so very much +That I get sappy when we touch +Or even when I think of you +Your eyes so red, your hair so blue + +I see your face, it warms my heart +It makes my colon leap, then fart +There aren't enough words to express how much I am in love with you +Even breaking meter won't do + +The fleshy folds around your teeth +Are red like blood, beyond belief +They make me want to osculate +And doing so is super-great + +In short, my love, you fill my gap +With sticky, drippy, sugary sap +I hope you're with me for all time +And that is why I wrote these lines diff --git a/poems/snark.mdwn b/poems/snark.mdwn new file mode 100644 index 0000000..6431a01 --- /dev/null +++ b/poems/snark.mdwn @@ -0,0 +1,31 @@ +[[!meta title="Snark Hair"]] + +Has anyone ever turned into a snark? +In the sun? In the rain? When it's light? When it's dark? +I'm asking because in the past couple days +Snark features have turned up in frightening ways. + +On Monday the snark hair began to appear +I felt just a tuft of it under my ear. +On Tuesday, my daugter declared with shagrin +It grew to envelop my cheeks and my chin. + +On Wednesday I noted with mounting alarm +that snark hair was starting to grow on my arm. +On Thursday I woke up and got quite distressed: +the thick, furry snark hair had covered my chest! + +This morning, I came in to work and found out +my nose was beginning to look like a snout. +My hands looked like snark claws; my feet did as well, +I carried a pungent, distinct snark-like smell. + +It looks as though snarkdom may be in the works. +I'm still undecided about all the perks: +My hearing and sniffing's improved, and that's cool, +But everything's suddenly slimed with snark drool. + +So if you're aware of a cure for this ill, +be it some kind of tonic, or potion, or pill, +please tell me! Or else when I go to the park, +kids won't call me "Mister", they'll just shout "Hey, Snark!" diff --git a/poems/winders.mdwn b/poems/winders.mdwn new file mode 100644 index 0000000..f8e9eab --- /dev/null +++ b/poems/winders.mdwn @@ -0,0 +1,6 @@ +[[!meta title="Winders"]] + +If I should ever find myself +A-washin' dirty winders, +I think that I'd confine myself +To washin' ol' Max Enders'. diff --git a/poems/woozle-irc.mdwn b/poems/woozle-irc.mdwn new file mode 100644 index 0000000..5996c15 --- /dev/null +++ b/poems/woozle-irc.mdwn @@ -0,0 +1,19 @@ +[[!meta title="32 lines about 16 lusers"]] + +ian is a manager, he also rides a motorbike +hbunny's a boss-man too, and he pumps iron day and night +Meeko is a quasi-furry, lives in Georgia with the fam +Seattle City pays owreee to try and stick it to the man +toast lives on a sailboat with husband, daughters, and some pets +brains take pictures of them all and posts them on the Internets +pinky's in New Jersey, works at linode keeping servers up +crispy's got a dozen kids and writes code for some small start-up +alien's a British guy, his wife is French and they ride bikes +Fub's from Denmark, lives in London, wife and son are Chinese tykes +ameigh is a mommy and she studies speech impediments +nate's a mystery to me, I don't know how he pays his rents +ronin is a Star Wars fan, and coding's something he enjoys +heidi's pinky's wife, she has a business selling bedroom toys +kirk hacks Linux Kernels, and his paycheck comes from Cray Research +nwc's a mystery, he mostly hangs around and lurks +And me, I just sit around writing poems. diff --git a/print.css b/print.css new file mode 100644 index 0000000..cd20bae --- /dev/null +++ b/print.css @@ -0,0 +1,3 @@ +#head, #nav, .actions { + display: none; +} \ No newline at end of file diff --git a/smileys.mdwn b/smileys.mdwn new file mode 100644 index 0000000..02e759c --- /dev/null +++ b/smileys.mdwn @@ -0,0 +1,31 @@ +This page is used to control what smileys are supported by the wiki. +Just write the text of a smiley to display it. + +* \\:) [[smileys/smile.png]] +* \\:-) [[smileys/smile.png]] +* \\:D [[smileys/smile-big.png]] +* \\:-D [[smileys/smile-big.png]] +* \\;) [[smileys/wink.png]] +* \\;-) [[smileys/wink.png]] +* \\:\ [[smileys/thinking.png]] +* \\:-\ [[smileys/thinking.png]] +* \\:/ [[smileys/thinking.png]] +* \\:-/ [[smileys/thinking.png]] +* \\:| [[smileys/neutral.png]] +* \\:-| [[smileys/neutral.png]] +* \\:( [[smileys/sad.png]] +* \\:-( [[smileys/sad.png]] +* \\:-? [[smileys/tongue.png]] +* \\:-P [[smileys/tongue.png]] +* \\:o [[smileys/shock.png]] + +---- + +To change the supported smileys, just edit the lists on this page. +Note that the format is important; each list item should start with the +text that is turned into the smiley, escaped so that users can see what +produces it, followed by a [[ikiwiki/WikiLink]] to the image to display. + +/!\ Bear in mind that the link to the image needs to be written in a way that +will work if it's copied to other pages on the wiki. So be sure to include the +smileys directory in the path to the file. diff --git a/src.mdwn b/src.mdwn new file mode 100644 index 0000000..613d402 --- /dev/null +++ b/src.mdwn @@ -0,0 +1,31 @@ +[[!meta title="Software"]] + +I write software for a living. I like doing it so much that sometimes I +even write software just for fun. Here are some of the better hacks I've +created over the years. + +[Firebot](firebot) is an IRC automaton (bot) that works as an InfoBot, +LinkBot (links multiple channels, even across servers), command bot +(displays the output of programs), web bot (fetches and parses web +pages, returning the results), and more. Everything runs in an +asynchronous select() loop with a very easy-to-use high-level interface. + +[Photobob](photobob) is a web-based photo album. There's nothing to +differentiate this from the myriad other web-based photo albums out +there, except that this one doesn't need a database and doesn't write +any meta-information. You just point it at a directory full of +images/movies and it serves 'em up. + +[eguile](eguile) is a text preprocessor using guile scheme. +[escm](escm) is the same thing for gauche. You could use these to build +a web site with a common theme. I used to use them, but now I use a +very simple m4 template. + +The [Universal Boardgame Kit](ubk/) is a kit you can build for under $5 +to use with a number of boardgames. A few boards are included. I +designed the pieces and most of the boards, and hand-coded them all in +PostScript. That makes me feel manly. + +I also have some little [Python](python/), [PostScript](ps-hacks), and +[other](misc) hacks, which do clever things. + diff --git a/src/eguile.mdwn b/src/eguile.mdwn new file mode 100644 index 0000000..37250d9 --- /dev/null +++ b/src/eguile.mdwn @@ -0,0 +1,65 @@ +[[!meta title="Eguile : a scheme preprocessor"]] + +If you've ever wished your text preprocessor could do symbolic +derivation, eguile is the tool for you! + +eguile is a preprocessor which lets you include Scheme code in your +source files--any source files, not just HTML. With the bundled +ntp-style.scm, you can give web pages a consistent interface with easy +navigation bars, just like this page. Further functionality is limited +only by your imagination and programming ability. + +eguile looks like PHP, but with Scheme instead of Perl. If you're the +sort of person that would enjoy something like this, you probably don't +need any further description. + + +## Downloading it + +[eguile.scm](scheme/eguile.scm). + + +## Reference + +Easy squeezy: + +
: (a colon) is
+ displayed an action. That is, instead of saying "
+#! /usr/bin/env python
+
+import ipqueue
+import iputils
+
+rewrite = 1
+
+q = ipqueue.IPQ(ipqueue.IPQ_COPY_PACKET)
+while 1:
+ p = q.read()
+ tcp = iputils.TCP(p[ipqueue.PAYLOAD])
+ print "Got %s -> %s on hook %d" % (iputils.ntoa(tcp.saddr),
+ iputils.ntoa(tcp.daddr),
+ p[ipqueue.HOOK])
+
+ if rewrite and p[ipqueue.HOOK] == 0:
+ tcp.daddr = iputils.aton("10.1.1.2")
+ tcp.th_dport = 25
+ q.set_verdict(p[0], ipqueue.NF_ACCEPT, tcp.to_str())
+ else:
+ q.set_verdict(p[0], ipqueue.NF_ACCEPT)
+
+
+Help me out
+-----------
+
+If you're using this in a project, let me know and I'll link to it. If
+you find any bugs, or want any features, please let me know about that
+too. If you've got a hankering to write better documentation, that would
+also be welcome :)
diff --git a/src/ipqueue/ipqueue-1.0.tar.gz b/src/ipqueue/ipqueue-1.0.tar.gz
new file mode 100644
index 0000000..c32cf80
Binary files /dev/null and b/src/ipqueue/ipqueue-1.0.tar.gz differ
diff --git a/src/ipqueue/ipqueue-1.1pre1.tar.gz b/src/ipqueue/ipqueue-1.1pre1.tar.gz
new file mode 100644
index 0000000..86abbbf
Binary files /dev/null and b/src/ipqueue/ipqueue-1.1pre1.tar.gz differ
diff --git a/src/ipqueue/ipqueue-1.2.tar.gz b/src/ipqueue/ipqueue-1.2.tar.gz
new file mode 100644
index 0000000..4a5c62e
Binary files /dev/null and b/src/ipqueue/ipqueue-1.2.tar.gz differ
diff --git a/src/ipqueue/ipqueue-1.3.tar.gz b/src/ipqueue/ipqueue-1.3.tar.gz
new file mode 100644
index 0000000..f8b728d
Binary files /dev/null and b/src/ipqueue/ipqueue-1.3.tar.gz differ
diff --git a/src/ipqueue/ipqueue-1.4.0.tar.gz b/src/ipqueue/ipqueue-1.4.0.tar.gz
new file mode 100644
index 0000000..6adc0fb
Binary files /dev/null and b/src/ipqueue/ipqueue-1.4.0.tar.gz differ
diff --git a/src/ipqueue/ipqueue-1.4.1.tar.gz b/src/ipqueue/ipqueue-1.4.1.tar.gz
new file mode 100644
index 0000000..3755e21
Binary files /dev/null and b/src/ipqueue/ipqueue-1.4.1.tar.gz differ
diff --git a/src/ipqueue/ipqueue.tar.gz b/src/ipqueue/ipqueue.tar.gz
new file mode 120000
index 0000000..be60321
--- /dev/null
+++ b/src/ipqueue/ipqueue.tar.gz
@@ -0,0 +1 @@
+ipqueue-1.4.1.tar.gz
\ No newline at end of file
diff --git a/src/ipqueue/nfqueue-0.1.tar.bz2 b/src/ipqueue/nfqueue-0.1.tar.bz2
new file mode 100644
index 0000000..2702426
Binary files /dev/null and b/src/ipqueue/nfqueue-0.1.tar.bz2 differ
diff --git a/src/photobob.mdwn b/src/photobob.mdwn
new file mode 100644
index 0000000..9cb31d1
--- /dev/null
+++ b/src/photobob.mdwn
@@ -0,0 +1,59 @@
+[[!meta title="Photobob"]]
+
+I don't have a lot to say about photobob. It's the 7th or so photo
+album package I've written, and probably the best. You just put
+pictures and movies in a directory, and away you go. This works
+really well with [an automated digicam photo sucking
+thing](/~neale/blog/2006-10-18.The_automatic_camera_suck_script/).
+
+Like all web applications I write, photobob does not use tables for
+layout, and will change layout depending on your browser's width. It
+uses CSS but still looks passable in non-CSS browsers. There is no
+database back-end because it doesn't need one. It's just files in
+directories.
+
+Motivation
+----------
+
+I want my photo albums to survive longer than the software that serves
+them up. My grandparents have shoeboxes full of photos, categorized by
+date and event. This is nice because it doesn't require any additional
+tools to determine the categorization.
+
+All the web-based photo albums I've run across require some way to store
+metadata. In one extreme example (PHP Gallery), all the images are
+stored in one flat directory. Should the metadata ever become corrupted
+or disappear, or should you decide to switch programs, you're left with
+a huge mess and your categorization work is lost.
+
+Photobob uses the file system as its categorization. You put photos in
+directories, and attach comments to the photos themselves (using the
+JFIF comment field). This makes it easy to press CDs or DVDs of your
+photo albums and still preserve the categorization and narration you've
+done. Should you decide to quit using Photobob, your photos will still
+be tucked away in their directories, with no droppings from the album
+software.
+
+Photobob also takes advantage of a special property of JPEG files: size
+reductions by powers of two (½, ¼, 1/8, etc.) are a very inexpensive
+operation when done at decoding time. Additionally, many digital
+cameras write small "thumbnail" images in the JFIF headers. Photobob
+takes advantage of both of these properties to serve up scaled images
+quickly and without needing to write anything to the hard drive.
+
+
+Getting it
+----------
+
+It's not really packaged up for distribution, but that's only because I
+doubt anyone will want it. If you're interested in trying it out on
+your site, email me and I'll be glad to help you set it up.
+
+You can check out the [woozle albums](http://woozle.org/albums)
+for a live demo.
+
+To get your own copy, run
+
+ git clone http://woozle.org/~neale/repos/photobob
+
+Or you can do a [download the latest commit as a tarball](http://woozle.org/~neale/gitweb.cgi?p=photobob;a=snapshot;h=HEAD).
diff --git a/src/pysieved.mdwn b/src/pysieved.mdwn
new file mode 100644
index 0000000..c8dd320
--- /dev/null
+++ b/src/pysieved.mdwn
@@ -0,0 +1,89 @@
+[[!meta title="pysieved: Python Managesieve Server"]]
+
+This is a GPL managesieve server. It uses a plug-in architecture to
+support different authentication, homedir lookup, and storage
+back-ends.
+
+I wrote this so I could use avelsieve (SquirrelMail) with Postfix
+and Dovecot. It should work with other managesieve clients too.
+Please share with me your successes and failures.
+
+
+Plugin architecture
+-------------------
+
+The server ships with the following plug-ins:
+
+Authentication:
+
+* Dovecot
+* PAM
+* SASL
+* MySQL
+
+Homedir lookup & session initiation:
+
+* Dovecot
+* /etc/passwd
+* MySQL
+* simple virtual hosting (eg. /var/lib/virtual/username)
+
+Storage:
+
+* Dovecot
+
+
+Additional back-ends are easy to write, just copy one of the existing
+back-ends and start hacking. No modifications are needed to any
+existing code, so you don't have to worry about things like the
+managesieve protocol or forking.
+
+
+Download
+--------
+
+[Version 1.0](http://woozle.org/~neale/gitweb.cgi?p=pysieved;a=commit;h=1.0)
+was released on May 10, 2008 after release candidate 3 had been out for
+6 weeks with no bug reports.
+
+You can get the latest version [as
+a tarball](http://woozle.org/~neale/gitweb.cgi?p=pysieved;a=snapshot;h=HEAD),
+or with git:
+
+ git clone http://woozle.org/~neale/repos/pysieved
+
+A [web view of revisions](http://woozle.org/~neale/gitweb.cgi?p=pysieved) is
+also available for those without git.
+
+
+Installation
+------------
+
+Put all the files somewhere. I put mine in /usr/local/lib/pysieved.
+Copy pysieved.ini into /usr/local/etc/, and edit to taste. It's
+commented.
+
+To run from inetd, add the following line to /etc/inetd.conf:
+
+ sieve stream tcp nowait root /usr/bin/python python /usr/local/lib/pysieved/pysieved.py --inetd
+
+To run as a daemon, just run
+
+ python pysieved.py
+
+
+
+
+Mail list / IRC channel
+-----------------------
+
+If you use pysieved, please join the pysieved mail list by emailing
+[pysieved-subscribe@woozle.org](mailto:pysieved-subscribe@woozle.org) or
+visiting the [subscription page](http://woozle.org/lists/pysieved).
+
+To talk about pysieved on IRC, join us in
+[#pysieved on irc.oftc.net](irc://irc.oftc.net/pysieved).
+
+--------
+
+Neale Pickett + This is a clever magic trick. This paragraph should be filled with + suspenseful leadup to waste your time and get you TOTALLY PUMPED for + this AWESOME MAGIC TRICK that was created by some famous and/or + mystical person and now it's coming directly to you on the + Internets! Can you believe it! +
+ ++ Pick a card. Stare at it long enough to memorize what card you've + picked, try to burn it into you mind. Don't worry, take your time, + I'll wait. +
+ +
+ 
+ 
+ 
+ 
++ When you've memorized your card, you may proceed to + the next page. +
+ ++ Do you remember your card? I'm going to yak at you for a little while + to make you spend some time doing something other than focusing on + those cards. This is called redirection and it's a + fundamental part of most magic tricks. The fact that it works even in + a web page says more about humanity than you in particular, so don't + feel bad. +
+ ++ Ready to have you mind blown? Let's go! +
+ ++ I have removed your card from the hand! +
+ +
+ 
+ 
+ 
+