skip to issue skip to content

Mysterious Infestation

Cari Harper

I settled in front of my laptop this week refreshed and ready to take on the challenges of school and the newspaper. As per usual, chaos struck shortly after. It has come to my attention that the Rose Thorn is currently suffering from an infestation. I am unsure of the details and can only guess what sort of sinister liason occurred between my unattended laptop and cordless mouse over the break to produce this:

Get a good close look at him. Cute right? Until you try to delete him. The little sucker can run into the network and hide in the system files faster than you can save a JPG. You’d think after the third run-around with him he’d learn to stay off the Thorn pages, but I think he keeps returning simply to spite me. Or maybe it’s part of a sinister plot to duplicate himself into over 1000 copies every week for use in taking over the world. Either way, I am smarter (in other words lazier) than he is, and going to enlist outside help. That help is you, the Thorn reader. I don’t know where he is going to show up next, but I figure that if you can keep track of him over the winter term, I can hunt down his EXE or catch him based on predicting where he is most likely to appear.

Now ‘what is my incentive?’ you may be asking yourself. ‘Why, the satisfaction of knowing you did a good deed and aided an esteemed member of the Thorn staff’ is my reply. However, I’m factoring in the fact that no one reads my section to allow me the ability to offer a small tangible reward if you bring me him circled in the subsequent issues of the paper (because everyone knows that is how you capture a 2D creature). To clarify the requirements for reward: in all issues of the Thorn from this issue to the second to last issue of the term, you will find him, circle him, and hold onto the full page on which you found him to turn in.

I will refrain from mentioning him hence-forth in an effort to avoid arousing his suspicion (and reduce the number of prizes I have to give out). Codename Fuzzy must be stopped.