The Camp Dearborn Book



General Information

This web archive was created to fix two simple problems:

1. The book is not available to just anyone who wants to see it year round. Only the "keeper of the book" may view it at any time other than at Camp Dearborn.
2. The book is well...a book. It's not immortal. If something were to happen......well...let's not go there...

The point of this archive it to both back the book up to a digital platform, and to provide anyone access to it year round even if you aren't at Camp. Heck, even if you aren't in Michigan!
The archive is the culmination of about 4 months of work, scanning images, testing server platforms, and creating HTML code.
Even though I don't consider this the final product, I think it's time to release it into the open so that we can at least get some input.
So please, enjoy!

- Tyler

Things to know

If you notice any issues with the website, (discrepancies, discontinuities, or general concerns) please don't hesitate to message me.
Facebook is probably the best way, but you may also email me at too.
It would be good if you could note the web address somewhere in the message for the page it occurs on. That way I can find out pretty quickly exactly which page you're talking about.

Additionally it would be beneficial to read the FAQ below before messaging. Perhaps the problem is explained there.

Frequently Asked Questions (FAQ)

  1. I noticed in the index that some of the pages overlap between years. Why is that?
    The reason for this is because those pages span over two years. An example would be page 38 between 2002 and 2003. That page contains writing from both of those years, which is noted at
    the top of the page when you click on it as "Year: 2002/2003"
    Rather than deal with the mess of creating a separate index section for combination years, I simply made those pages "straddle" the two sections.

  2. Some of the content on the pages is dated incorrectly. For example, on page 112, the pictures there are clearly dated 2008, but the year on the page is listed as 2012.
    This is correct. However, the date during which those pictures were put in is 2012. The year at the top denotes the time during which the pictures were put in the book, not the time
    during which they were created. It was done this way to make the years more contiguous.

  3. Why is that sometimes the year at the top is listed as "Ambiguous?"
    This is because based on the information I have, I cannot discern which year the pages were written. An example would be page 72. We know that page 71 is dated 2005, because a
    date is listed at the top of the entry, and it's the only entry on that page. However, the next dated entry is on page 73 as August 8th, 2006. This is no "divider in between, and
    therefore, we cannot discern whether or not page 72 is from 2005, 2006, or both. Thus, it is "Ambiguous."

  4. Wouldn't it be great if instead of clicking on links in the index, we could just click on thumbnails of the pictures themselves? That way, we could get a preview of the page we're trying to look at.
    I completely agree. It would be great, wouldn't it? In fact, I actually considered implementing it. Too bad it's not presently practical.
    The problem is that the server that runs this website is not very powerful on both the processing and bandwidth end of things. If you were to make the request to view such a page,
    the server would not only have to send you the html document to view in your browser, but EVERY SINGLE IMAGE FILE AS WELL.
    This isn't a problem if the internet that the server is connected to is fast and the server has lots of power to spare, but it doesn't. This website runs on a very old
    server computer sitting in the basement connected to a 10 Mbps ethernet switch. To make matters worse, the images are in a fairly high resolution in order to get as much clarity from the
    pictures as possible. This however equates to a large size for the images. (each one averaging 4 MB) In fact, the total size of all the images is around half a gigabyte, which is a
    large request for such a small server.
    Long story short, it's possible, but it's not practical unless you'd like to wait several minutes for the index page to load.

  5. Is this page viewable by anyone?
    It is technically possible for anyone to view this page who has an unrestricted internet connection. However, there is one small stipulation:
    They need to be able to find it. The thing is, unless someone knows the address, this page would be hard to find. Because this page isn't exactly popular, it would be lowered in priority on search engines like google. (Although if you know the address, it is possible to find it on google) Even if you were to search for something like Camp Dearborn, this page probably wouldn't come up because in google's eyes there are a million more important pages which would be displayed first. But yes, it is possible for anyone with the address to see

  6. Why can't the address be something nice like or something like that? Why is it a bunch of numbers?
    It could be. However, in order to do that, we'd need to use a DNS server.
    A DNS Server (Domain Name System Server) is a special type of server which takes requests sent to a domain name, (like and and translates and redirects them to the IP
    address of the corresponding server. Computers communicate with special addresses called IP addresses. They're a bit like house addresses in that everyone's is unique.
    In order to send something to a computer then, you need to know the IP address in the same way that in order to send someone a letter, you'd need to know their house address. DNS Servers let us remember names instead of numbers, a bit like how you can remember famous buildings by their names.
    The issue is that you can't just set up a DNS Server. In order to get a domain name, you usually have to go through your internet service provider, and they usually charge you a recurring fee.
    I don't want to do this, and am perfectly content with memorizing a number. However, if someone would like to fork over the money for a domain name, by all means, be my guest.

    Done! The address is!

Technical Details

  1. What type of server software does this website run?
    - It runs an HTTP Server client called Apache 2.
    - It also runs PHP Version 5.5, but this is not for this section of the server and is only used for my Minecraft webpage to check server status. - Additionally, the search engine which currently powers the minecraft half of the website (and will soon power this half too...) is called Sphider.

  2. What are the specs on the machine/network?
    - Processor: Intel Core 2 Duo E8400 @ 3.00 GHz
    - RAM: 4 GB DDR2
    - GPU: Dedicated ATI Radeon graphics card with 256 MB of graphics memory
    - Hard drives: Seagate 7200 RPM 250 GB HDD
    - Operating System: Ubuntu 15 64-bit
    - Network: 15 Mbps Down, 2.5 Mbps Up, Asynchronous.

  3. How large is the server?
    - The server program itself is only 38 MB, however the data it manages is about 1.9 GB, give or take a few KB. This is counting not only the Camp Dearborn books (which take up the vast majority) but also all of the html documents and pictures for my minecraft server, as well as a few maps for my TF2 server.

    ...Or did you mean the physical size? It's just your typical computer. Non-small form factor.

  4. What type of code does the server run?
    - The server program was written in C, Forth, and XML. The search engine was coded in PHP. I didn't make either of them though.
    The webpages are coded entirely in HTML and CSS (with some PHP for Minecraft stuff, and Python for a few of the more specialized pages). There are probably around 135 total HTML documents for the first volume, and each one was coded by hand, without assistance from a script.
    In volume II I got wise and used a python script I wrote to assist in writing the pages. The front and back cover and cover pages were made by hand from a template, however the rest of volume II was made entirely by a computer.
    The CSS was also written by hand, using a simple template. I changed some colors here, repositioned some things there, and hey presto, a CSS file.
    There is one for the main directory, and one for each subdirectory as well, (so, 4) and each one is just a duplicate of each other. However that only counts the ones in the directories for the Camp Dearborn books. My minecraft server's webpages have countless directories and thus countless CSS documents, and I don't really have an interest in figuring out exactly how many.