My Name Is Me

My Name Is Me. I choose to participate on much of the Internet by my full name. I say “full name”, rather than “real name”, because the term “real name” is full of loaded connotations. For example, I (still) periodically have people insist that Dan Q isn’t my real name, because it’s not the name I was born with. It doesn’t matter to them that it’s the name I’m known by to pretty much everybody (except my mother, who still calls me Daniel). It doesn’t matter that it’s the name on my passport or driving license. To them, it’s not “real” because to them, real names are either those acquired by birth or marriage, and somehow nothing else is valid. And that’s without even looking at the number of times I’ve been discriminated against because my name is “too short” for ill-designed computer systems.

That doesn’t bother me. What does bother me is that sites like Facebook and – in the news recently on this very topic – Google+ demand that full “real” names are used on the profiles of their site users. If you don’t use the name that appears on your government-issued documentation (if you have such a thing), then your accounts on these sites are liable to be closed. By the way: the same is theoretically true of your Google Profile, too, so even if you’re not on the Google+ bandwagon and you, say, use a nickname in your Google Profile, your account is still at risk.

Now, I can see the point that these policies are trying to make.  In fact, there was a time that I’d have naively agreed with them. They’re trying to make the Internet a safer, more-accountable place. But in actual fact, there’s a real risk that they’ll make the Internet a lot more-treacherous for some people. I shan’t bother listing folks who are affected, because others have done it far more-thoroughly than I ever could.

But I shall point you in the direction of my.nameis.me, where you can read a little more about these issues. Thanks.

How Can You Have Any Pudding If You Don’t Eat Your Meat?

To those of you that don’t know already, I have a confession to make. After years of picking holes in and finding flaws in their various ethical or other arguments and of mocking their dietary choices, I’ve become… a vegetarian.

This cow, which was not harmed in the making of this blog post, was just as shocked as you are by the news of my vegetarianism.

Okay, this probably wasn’t actually a shock to anybody. Between the observations of the barbeque food I’ve been enjoying recently and the fact that I willingly chose falafel over hog roast a month or so ago, it’s quite possible that you’re saying “well, duh” at this so-called revelation. That’s why I thought it’d be far more-interesting for me to talk about the principal reason for this change.

You don’t eat what, now?

For some, however, this change has been a gradual one, beginning with dropping beef from my diet in January, and other red meats in March (making me, technically-speaking, a lactoovomelopollopescetarian, which is quite a mouthful). Poultry and fish disappeared from my diet in April and May.

For a brief stint, I tried to remove milk, too, aiming for ovo-vegetarianism, but it turns out that – while oatmilk is a perfectly reasonable alternative to the white stuff, and there are some great soya-based dairy-free deserts – there really are no adequate vegan substitutes for cheese… and I’m just not quite capable of coping without it.

Things Dan eats.

Why, Dan? WHY?

My decision to adopt a vegetarian diet is based on a few different influences, but the principal one amongst these is one of environmentalism and sustainability. Over the last few years it’s become increasingly apparent to me that the Western Pattern Diet has a hugely damaging effect in the following areas:

  • Water usage sustainability – studies consistently show[1][2] that it takes an order of magnitude more water to produce beef than wheat, rice, or maize, by weight of food produced. Other meats fare somewhat better, being only three or four times less water-efficient per unit of weight of food, but are still unacceptably water-expensive, to me. Milk and eggs are really quite water-efficient, being (respectively) about as efficient as soybeans/rice (depending on the region they’re grown in) and maize (note, of course, that beef and dairy cattle are almost always separate breeds[3], so the counter-argument that beef is a by-product of milk production or vice-versa is not valid).
  • Climatic impact – intensive modern livestock farming has an appreciable negative impact on global climate, contributing over a third of the world’s methane[4], probably the most-significant of the greenhouse gases[5].
  • Food scarcity – despite worldwide crop yields increasing faster than population growth[6], year on year, food security is becoming a growing issue owing to desertification of equatorial regions, increased uptake of the wasteful Western Pattern Diet, and an increase in the production of biofuels. A still-growing population, the depletion of fish stocks, and a rapid increase by developed nations in biofuel demands as oil supplies dwindle will only aggravate these issues. While a widely-adopted vegetarian/vegan diet would not in itself alleviate these problems (many of which are caused by political and economic constraints), it would help to ensure that it is possible to feed our booming population in the decades to come.
  • Overfishing – most of those reasons, of course, are only applicable to the farming of mammals and birds, but it’s hard to deny that there are huge problems with our consumption of fish, too[7]. We’re already reaching the point where the consumption of many species of fish is ethically very dubious, and an increasing number of species are threatened with extinction. To ensure that fish stocks remain available for future generations, we need either extremely restrictive multinational agreements on fishing quotas (unlikely), or dramatic reductions in the demand for fish.

In short, I could probably best be described as an economic environmentalist vegetarian: I’m concerned primarily with making sure that our agricultural practices are sustainable for the benefit of humans, whether currently existing or future. More on that, little doubt, in the Frequently Anticipated Questions, below.

So… how’re you finding it?

Man, I miss bacon.

A BLT; one of many culinary delights that I’m now denied. /sob/

Giving up beef, it turned out, was reasonably easy. Ditto lamb. But bacon: that’s something I miss. When my co-worker Liz had a bacon, mushroom and cheese jacket potato at an office lunch the other week, I could have almost drowned in my own drool. I find myself envying those vegetarians I know who don’t eat meat because they don’t like it: those guys have it so easy…

Chicken’s been challenging, too, because it’s always been a go-to base ingredient for me, and I’ve had to learn to substitute other sources of protein into my diet. Thankfully, I’ve been in a strong position: many years of cooking for vegetarians, at one point or another, has given me a pretty good understanding of what’s good for what and a decent repertoire of already-vegetarian dishes.

I tried to give up milk and milk products after realising that the ecological impact of milk production – while significantly less than beef, for a variety reasons – is still higher than I’d like. Sadly, it turns out that milk turns up in just about everything, and cheese and cream are remarkably hard to do without. Maybe some day I’ll give that another go.

On the up-side, though, I’ve discovered a reasonable number of things that I didn’t think I liked, that actually I do… or at least, that are perfectly adequate substitutes for meat products.

But man, I miss bacon. Pigs may be clever, but they’re not smart enough to not be delicious.

I also routinely slip up on the likes of isinglass (used in the production of many of my favourite beers), and gelatine (which appears in a surprising number of things), and I try not to kick up a fuss where food is being prepared for several people, of which I’m only one, in a non-compatible way. For example, I tolerate the addition of Worcester sauce (containing anchovies) as an ingredient where a meal is being prepared for several people – it’d be incredibly inconvenient to require a separation of the food at this point during cooking, and I’m happy to compromise a little where the chef’s convenience collides with my ethics.

Frequently Anticipated Questions

In order that I jump the gun and answer you before you ask:

You consume products made using isinglass, gelatine, and occasional small quantities of fish sauce… you’re not a vegetarian at all!

I guess not. But the label’s for my convenience, not yours. I use the word vegetarian because it’s the simplest-common-denominator. If I ask in a restaurant “what have you got that’s vegetarian, or would be but that it contains trace amounts of isinglass, is made using gelatine, has Worcester sauce in, etc.” I’d never get my meal. Plus, the staff would be confused. To take a mathematical model: the set of things that better-vegetarians-than-I eat is completely contained within the set of things that I eat, and the two are very nearly the same, so to call myself a vegetarian is closer to a convenient rounding error than a lie.

Also; that wasn’t a question.

Do you expect to make a significant difference?

No. But, like many moral decisions, this isn’t about making a significant difference but about doing the right thing.

If there’s a riot in your town and an out-of-control crowd begins damaging and looting the shops in the high street, you might be tempted to go out and steal a nice laptop or television yourself, too. Regardless of whether or not you do so, you won’t make a significant difference – Currys will be just as empty in the morning whether you partake of a little ransacking or not. But that doesn’t change the fact that it would be wrong of you to rob them.

On the other hand, over the course of the rest of my life I’m liable, under ideal circumstances, to make a miniscule but measurable net decrease in the demand for meat products, which might, under ideal circumstances, have an impact on meat production, thereby coming some way to achieving my ideals. Moreover, I’d like to think that my dietary choices go some way to making those dietary choices more palatable (hah!) for others, which may influence others to reduce their meat consumption too.

If the aim is to reduce meat consumption, why not simply eat less meat?

Because I can’t trust everybody else to play along.

My gut feeling is that this would work (although I haven’t read any research to either confirm or deny that suspicion): that if we all just cut down our meat consumption so that we were eating meat only once every few weeks, that we’d have a huge impact on sustainability for the future. But I can’t make everybody do this. The best I can do is to do so myself.

However, if I go just a little bit further and stop eating meat altogether, then I also help to “make up” for other people’s meat-heavy diets.

For every animal you don’t eat, I’m going to eat two!

Well, I hope you enjoy it, because you’ll probably not live too long after consuming all the saturated fats of all of the animals I don’t eat.

In any case: I’m not responsible for how you choose to live your life, even if you are threatening to push Comic Book Guy off a railway overpass.

You mentioned that the economic/ecological reasons were the principal cause for your vegetarianism. Are there other reasons, too, like the health and longevity benefits or the cost saving?

Yes. But they’re not the principal reasons.

Incidentally, removing meat from my diet made it far easier for me to lose the second of my three 10kg weight loss goals (as part of my ongoing effort to get down from 110kg to 80kg; I’m currently at about 89kg), because it’s far easier to avoid fats when you’re already avoiding meat.

How does JTA feel, being the only non-vegetarian in the house?

He’s not… so much. These days, Ruth eats a reasonable amount of a select few different varieties of meat, and Paul… well, I’m not sure I can keep up with our favourite pepperoni-eating vegetarian, but I think that right now he’s abstaining from meat entirely, but I’m not sure.

I have a hypothesis that perhaps the world can only tolerate a certain number of vegetarians at once, so as I became one, Ruth had to stop.

What about sustainably-farmed fish/synthetic meat/a survival situation/some other hypothetical situation?

I’m pragmatic, first and foremost, so if somebody wants to demonstrate that a particular farmed fish is environmentally sound, to my satisfaction, then great: it’s back on the menu! I’m not going out of my way to look for any, though, because I was never a big seafood fan to begin with! It’s not a high priority for me to make my life more complicated by coming up with some kind of complex list of what’s okay and what’s not, when the simple rule “no meat” seems to be perfectly workable.

Survival situation: sure, I’d chow down on whatever was available to stay alive. I’m not stupid!

And synthetic meat? If it was economically-sound, environmentally-friendly, safe, and tasty… sounds like a win to me. Fetch me a plate!

Isn’t this quite a turnaround for somebody who was once quoted on the BBC as describing vegetarianism as an “eating disorder”?

Yes, I suppose it is. I’ve always prided myself, though, on what I call “correctness over consistency”: that is, I’d like to think that I’m able to do the right thing, even where it means contradicting my previous attitudes or behaviour. I believe that we’d all do a lot better if people were less attached than they are, on average, to appearing consistent, especially when they’re faced with new information. There’s no shame in saying “I was wrong then,” so long as you can show that you’re learning.

But yes, I’ve been quite mean to many vegetarians for many years, as if I needed reminding. And so yes, this really is quite a turnaround. And I’m proud to be capable of that.

References

× × ×

A New Sensation

I’ve recently gotten a new phone – a HTC Sensation running Android 2.3, and I thought I’d offer up a few thoughts on it. But first…

Hang on: what was wrong with your old phone?

Well-remembered! You’re right, of course, that last year I got a Nokia N900, and that it was the best mobile communications device I’d ever owned. I don’t care so much about a slim profile or an “app store”, but I do care about raw power and geeky hardware features, and the N900 delivers both of those in spades. I’ve had several phones that have, at the time, been the “best phone I’ve ever owned” – my 7110 and my N96 both also earned that distinction, whereas my 7610 and my C550 – the latter of which had only one redeeming feature – fell far short.

Nokia N900 with keyboard extended

Awesome though it is,  with it’s beautiful hardware keyboard, mighty processor, FM receiver and transmitter, Bluetooth and IR, etc., and completely unlocked, tamper-friendly architecture, the N900 suffers from one terrible, terrible flaw: for some reason, the engineers who built it decided to mount the Micro-B USB port (used for charging, tethering, mounting etc. the phone) not to the hard plastic case, but to the fragile inner circuit board. Allow me to illustrate:

A cross-section of a Nokia N900, showing how the USB port is mounted directly to the circuit board, and doesn't touch the hard plastic case.

Why is this a problem? Well, as Katie explained to me at the New Earth housewarming party, most of her other friends who’d had N900s had encountered a problem by now, whereby the USB cable used to charge the device eventually puts a strain on the connection between the port and the board, tearing them apart. “Nope,” I told her, “I’ve never had any such problem with mine.”

A cross-section of a Nokia N900, showing the USB port snapped off by the USB cable.

Looks like I spoke too soon, because that very week, I managed to break my N900 in exactly this way. My theory: that girl is cursed. I shall be attempting to exorcise the anti-technology demons in her the very next time I see her, possibly in some kind of ceremony involving high-voltage direct current. In any case, I found myself with a phone that I couldn’t charge.

So you replaced it?

No, of course not. My N900 remains a fantastic palmtop and a great device. It’s just got a minor problem in that it’s no longer possible to charge or “hard”-tether it to anything any more. The latter problem was an easy one to fix: a separate battery charger (I already carry a spare battery for it, so this was no hardship), bought for about £4 on eBay, made it easy to keep the device rolling. The second problem’s not so much of an issue, because I tend to do all of my synchronisation by Bluetooth and WiFi anyway. But even if these were an issue, it looks like a pretty simple job to re-solder the USB port (and epoxy it to the case, as it should have been to begin with!). I might give it a go, some day, but my current soldering iron is a little big and chunky for such fine and delicate work, and I’m a little out of practice, so I’ll save that project for another day.

The repairing of a Nokia N900 USB port

However, I’m a big believer in the idea that when the Universe wants you to have a new phone, it finds a fault with your current phone. Perhaps this is the geek equivalent of thinking that “When God closes a door, He opens a window”.

So: I’ve got myself a HTC Sensation, which narrowly beat the Sony Ericsson Xperia Arc after carefully weighing up the reviews. I’d always planned that I’d try an Android device next, but I’d originally not expected to do so until Ice Cream Sandwich, later this year. But… when the Universe closes your USB Port, it opens a Gingerbread shop… right?

The New Sensation

After a few difficulties relating to my name – it turns out that my mobile phone network has recorded my name correctly in their database, and I can’t change it, but whenever I use their web-based checkout it asks me to enter a longer surname even though I don’t have a surname field to change – I finally received my new phone.

HTC Sensation seen from the back, front, and side.

The first thing one notices about this phone is that it’s fast. Blindingly fast. I’ve used a variety of Android-powered HTC devices before, as well as other modern touchscreen smartphones like the iPhone, and I’m yet to use anything that consistently ramps up high-end graphics and remains slick and responsive like this does. Its mighty dual-core 1.2GHz processor’s the cause of this, little doubt. I originally worried that battery life might be limited as a result – I don’t mind charging my phone every night, but I don’t want to have to charge it during the day too! – but it’s actually been really good. Using WiFi, GPRS, GPS, playing videos, surfing the web, and other “everyday” tasks don’t put a dent in the battery: I’ve only once seen it dip to under 10% battery remaining, and that was after 40 hours of typical use during a recent camping weekend (with no access to electricity).

It’s also been really well-designed from a usability perspective, too. Those familiar with Android would probably just start using it, but I’ve not had so much exposure to the platform and was able to come to it with completely fresh eyes. Between Android 2.3 and HTC Sense 3, there’s a nice suite of “obvious” apps, and I didn’t have any difficulty synchronising my contacts, hooking up my various email accounts, and so on. There are some really nice “smart” touches, like that the phone rings loudly if it thinks it’s in a bag or pocket, more quietly after you pick it up, and silences the ringer completely if you pick it up from a table and flip it from face-up to face-down. These simple gestural touches are a really nice bit of user interface design, and I appreciate the thought that’s gone into them.

Browsing movies for HD streaming on the HTC Sensation.

The Android Marketplace is reasonable, although I feel as though I’ve been spoiled. On the N900, if there was an application I needed, I usually already knew what it was and where I’d find it: then I’d either apt-get it, or download the source and compile it, right there on the device. For somebody who’s already perfectly confident at a *nix command-line, the N900 is fab, and it feels a little restrictive to have to find equivalent apps in a closed-source environment. It’s not that the pricing is unreasonable – most of the applications I’ve wanted have been under a quid, and all have been under £4 – it’s just that I know that there are FOSS alternatives that would have been easy to compile on my old device: I guess it’s just a transition.

On the other hand, the sheer volume of applications so-easily available as the Android Market is staggering. I’ve been filled with app ideas, but every idea I’ve had but one or two already exist and are just waiting to be installed. It’s a little like being a kid in a candy store.

It’s also taking me quite some time to get used to the way that process management works on an Android device. On Android devices, like the iPhone/iPad, returning to the home screen doesn’t (necessarily) close the application, but it might – that’s up to the developer. If it doesn’t, the application will probably be “paused” (unless it’s a media player or it’s downloading or something, then it’ll likely keep going in the background). And when you re-launch the same application, it could be simply unpausing, or perhaps it’s relaunching (in which case it may or may not restore its previous state, depending on the whim of the developer)… You see all of the keywords there: mightprobablylikelycouldperhaps. Great for most users, who don’t want to have to think about what their phone is doing in the background, but it feels like a step backwards to me: I’m used to being able to ALT-TAB between my currently-running applications, to know what’s running, when (and I can always use top and find out exactly what resources a process is eating). Putting all of this process management into the hands of developers feels to me like giving up control of my device, and it’s a challenging change to undergo. Yes: despite the openness of the platform, Android feels just a little out of my control compared to what I’m used to.

Hacker's Keyboard, my preferred keyboard layout for SSH, etc.

Switching from a physical to a virtual keyboard for the first time is a significant change, too, and it’s slowed me down quite a lot, although applications like SwiftKey X – with its incredibly intelligent personalised predictions – and Hacker’s Keyboard – which gives me back some of the keys I was “missing” – have helped to ease the transition a lot.

In summary: the HTC Sensation seems to be a fantastic device, and I’m really enjoying using it. I’ve got a few niggles to contend with, but these are all things that were destined to catch me out upon switching away from a platform as open as the N900, and they’re not severe enough to make me give up and get an N950 instead: I’m reasonably confident that I’ll come to love the Sensation and we’ll go on to be very happy together.

But will it become my latest “best phone ever”? Time will tell, I guess.

× × × × ×

Instead Of Blogging…

Things I’ve been doing instead of blogging, this last month, include:

  • Code Week: hacking Three Rings code in a converted hay loft of a Derbyshire farm, as mentioned on the Three Rings blog.
  • Hoghton Tower: as is traditional at this time of year (see blog posts from 2010, 2009, 2005, 2003, for example), went to Preston for the Hoghton Tower concert and fireworks display, accompanied by Ruth, and my sister’s 22nd birthday. My other sister has more to say about it.
  • Family Picnic: Joining Ruth and JTA at Ruth’s annual family picnic, among her billions of second-cousins and third-aunts.
  • New Earthwarming: Having a mini housewarming on New Earth, where I live with Ruth, JTA, and Paul. A surprising number of people came from surprisingly far away, and it was fascinating to see some really interesting networking being done by a mixture of local people (from our various different “circles” down here) and distant guests.
  • Bodleian Staff Summer Party: Yet another reason to love my new employer! The drinks and the hog roast (well, roast vegetable sandwiches and falafel wraps for me, but still delicious) would have won me over by themselves. The band was just a bonus. The ice cream van that turned up and started dispensing free 99s: that was all just icing on the already-fabulous cake.
  • TeachMeet: Giving a 2-minute nanopresentation at the first Oxford Libraries TeachMeet, entitled Your Password Sucks. A copy of my presentation (now with annotations to make up for the fact that you can’t hear me talking over it) has been uploaded to the website.
  • New Earth Games Night: Like Geek Night, but with folks local to us, here, some of whom might have been put off by being called “Geeks”, in that strange way that people sometimes do. Also, hanging out with the Oxford On Board folks, who do similar things on Monday nights in the pub nearest my office.
  • Meeting Oxford Nightline: Oxford University’s Nightline is just about the only Nightline in the British Isles to not be using Three Rings, and they’re right on my doorstep, so I’ve been meeting up with some of their folks in order to try to work out why. Maybe, some day, I’ll actually understand the answer to that question.
  • Alton Towers & Camping: Ruth and I decided to celebrate the 4th anniversary of us getting together with a trip to Alton Towers, where their new ride, Thirteen, is really quite good (but don’t read up on it: it’s best enjoyed spoiler-free!), and a camping trip in the Lake District, with an exhausting but fulfilling trek to the summit of Glaramara.
Setting up camp at Stonethwaite.

That’s quite a lot of stuff, even aside from the usual work/volunteering/etc. stuff that goes on in my life, so it’s little wonder that I’ve neglected to blog about it all. Of course, there’s a guilt-inspired downside to this approach, and that’s that one feels compelled to not blog about anything else until finishing writing about the first neglected thing, and so the problem snowballs.

So this quick summary, above? That’s sort-of a declaration of blogger-bankruptcy on these topics, so I can finally stop thinking “Hmm, can’t blog about X until I’ve written about Code Week!”

×

On This Day In 2003

Looking Back

On this day in 2003 I first juggled with flaming clubs! But first, let’s back up to when I very first learned to juggle. One night, back in about 1998, I had a dream. And in that dream, I could juggle.

I’d always been a big believer in following my dreams, sometimes in a quite literal sense: once I dreamed that I’d been writing a Perl computer program to calculate the frequency pattern of consecutive months which both have a Friday 13th in them. Upon waking, I quickly typed out what I could remember of the code, and it worked, so it turns out that I really can claim to be able to program in my sleep.

In this case, though, I got up and tried to juggle… and couldn’t! So, in order that nobody could ever accuse me of not “following my dreams,” I opted to learn!

About three hours later, my mother received a phone call from me.

“Help!” I said, “I think I’m going to die of vitamin C poisoning! How much do I have to have before it becomes fatal?”

“What?” she asked, “What’s happened?”

“Well: you know how I’m a big believer in following my dreams.”

“Yeah,” she said, sighing.

“Well… I dreamed that I could juggle, so I’ve spent all morning trying to learn how to. But I’m not very good at it.”

“Okay… but what’s that got to do with vitamin C?”

“Well: I don’t own any juggling balls, so I tried to find something to use as a substitute. The only thing I could find was this sack of oranges.”

“I think I can see where you’re going wrong,” she said, sarcastically, “You’re supposed to juggle with your hands, Dan… not with your mouth.”

“I am juggling with my hands! Well; trying to, anyway. But I’m not very good. So I keep dropping the oranges. And after a few drops they start to rupture and burst, and I can’t stand to waste them, so I eat them. I’ve eaten quite a lot of oranges, now, and I’m starting to feel sick.”

I wasn’t  overdosing on vitamin C, it turns out – that takes a quite monumental dose; perhaps more than can be orally ingested in naturally-occuring forms – but was simply suffering from indigestion brought on as a result of eating lots and lots of oranges, and bending over repeatedly to pick up dropped balls. My mother, who had herself learned to juggle when she was young, was able to give me two valuable tips to get me started:

  1. Balled-up thick socks make for great getting-started juggling balls.  They bounce, don’t leak juice, and are of a sensible size (if a little light) for a beginning juggler.
  2. Standing with your knees against the side of a bed means that you don’t have to bend over so far to pick up your balls when you inevitably drop them.

I became a perfectly competent juggler quite quickly, and made a pest of myself in many a supermarket, juggling the produce.

So: fast forward five years to 2003, when Kit, Claire, Paul, Bryn and I decided to have a fire on the beach, at Aberystwyth. We’d… acquired… a large solid wooden desk and some pallets, and we set them up and ignited them and lounged around drinking beer. After a little while, a young couple came along: she was swinging flaming poi around, and he was juggling flaming clubs!

Fire poi! They look fantastic when they're flying around you; scary when they're flying towards you.

I asked if I could have a go with his flaming clubs. “Have you ever juggled flaming clubs before?” he asked. “I’ve never even juggled clubs before,” I replied. He offered to extinguish them for me, first, but I insisted on the “full experience.” I’d learn faster if there existed the threat of excruciating pain every time I fucked up, surely. Right?

Juggling clubs, it turns out, is a little harder than juggling balls. Flaming clubs, even more so, because you really can’t get away with touching the “wrong” end. Flaming clubs at night, after a few drinks, is particularly foolhardy, because all you can see is the flaming end, and you have to work backwards in your mind to interpret where the “catching end” of the stick must be, based on the movement of the burning bit. In short: I got a few minor singes.

But I went home that night with the fire still burning in my eyes, like a spark in my mind. I couldn’t stop talking about it: I’d been bitten by the flaming-clubs-bug.

Looking Forward

I ordered myself a set of flaming clubs as soon as I could justify the cost, and, after a couple of unlit attempts in the street outside my house, took them to our next beach party a few days later. That’s when I learned what really makes flaming clubs dangerous: it’s not the bit that’s on fire, but the aluminium rod that connects the wick to the handle. Touching the flaming wick; well – that’ll singe a little, but it won’t leave a burn so long as you pull away quickly. But after they’ve been lit for a while – even if they’ve since been put out – touching the alumium pole will easily leave a nasty blister.

Me juggling flaming clubs at the barbecue I mentioned, in 2007. I almost look like I know what I'm doing. And more importantly, I feel like a badass.

Still: I learned quickly, and was still regularly flinging them around (and teaching others) at barbecues many years later.

Once, a Nightline training ended up being held at an unusual location, and the other trainers and I were concerned that the trainees might not be able to find it. So we advertised on the email with the directions to the training room that trainees who can’t find it should “introduce themselves to the man juggling fire outside the students union”, who would point them in the right direction: and so I stood there, throwing clubs around, looking for lost people all morning. Which would have worked fine if it weren’t for the fact that I got an audience, and it became quite hard to discreetly pick out the Nightline trainees from the students who were just being amused by my juggling antics.

Nowadays, I don’t find much time for juggling. I keep my balls to-hand (so to speak) and sometimes toss them about while I’m waiting for my computer to catch up with me, but it’s been a long while since I got my clubs out and lit them up. Maybe I’ll find an excuse sometime soon.

This blog post is part of the On This Day series, in which Dan periodically looks back on years gone by.

× ×

Halloumi & Mushroom Skewers

Last week, I was invited to a barbeque with Oxford’s Young Friends. Despite being neither a Friend (in their “capital-F” meaning of the word: a Quaker) nor young (at least; not so young as I was, whatever that means), I went along and showed off my barbecue skills. It also gave me an excuse to make use of my Firestick – a contemporary tinderbox – to generally feel butch and manly, perhaps in an effort to compensate for the other week.

Anyway: this is how I discovered halloumi and mushroom skewers. Which may now have become my favourite barbeque foodstuff. Wow. Maybe it’s just the lack of mushrooms in my diet (we operate a cooking rota on Earth, but Paul doesn’t like mushrooms so I usually only get them when he or I happen to be eating elsewhere), but these things are just about the most delicious thing that you can pull off hot coals.

Aside from meat, of course.

Update: we just had some at the Three Rings Code Week, and they were almost as delicious once again, despite being hampered by a biting wind, frozen mushrooms, and a dodgy barbeque.

×

First Class Film

Last week, I saw X-Men: First Class at the cinema with Ruth. The film was… pretty mediocre, I’m afraid… but another part of the cinemagoing experience was quite remarkable:

There’s a bit in the film where Xavier, then writing his thesis at Oxford University, and a CIA agent are talking. As they talk, they walk right through the middle of the Bodleian Library, right past my office. It’s not just Morse and Lewis and the Harry Potter films that make use of the Library (at great expense, I gather) for filming purposes! “That’s my office!” I squee’d, pointing excitedly at the screen.

Needless to say, the student-heavy audience cheered loudly at the presence of parts of Oxford that they recognised, too. It’s been a while since I was in a cinema where people actually cheered at what was going on. In fact, the last time will have been in the Commodore Cinema in Aberystwyth. But cinema-culture in Aberystwyth’s strange anyway.

Spirit of the Century

A couple of weeks ago, the other Earthlings and I played our very first game of Spirit of the Century. Spirit of the Century is a tabletop roleplaying game based on the FATE system (which in turn draws elements from the FUDGE system, and in particular, the FUDGE dice). Are you following me so far?

Four sets of FUDGE/FATE dice. Each die is labelled with 2 “blank”, 2 “minus” and 2 “plus” sides, and all four are rolled to obtain a result between -4 and +4, on a probability bell-curve trending towards 0. Neat.

Spirit of the Century is set in the “pulp novel” era of the 1920s, in the optimistic period between the two world wars. The player characters play pulp-style heroes: the learned professor, the adventurous archaeologist, the daring pilot, all of those tropes of the era. Science, or – as it should be put – Science! is king, and there’s no telling what fantastic and terrifying secrets are about to be unleashed upon the world. Tell you what… let me just show you the cover for the sourcebook:

Yes; that’s a gorilla flying a biplane away from a stricken zeppelin, fighting a masked hero. Meanwhile, a female mechanic clambers under the fuselage and man wearing a jetpack pulls alongside, guns blazing.

Everything you need to know about the game is right in that picture, right there.

The character generation mechanism is different from most RPGs; even other fluffy, anti-min/max-ey ones. All player characters (for reasons relevant to the mythos) were born on 1st January 1901, so the first part of character creation is explaining what they did during their childhood. The second part is about explaining what they did during the Great War. During each of these (and every subsequent step), the character will gain two “aspects”, which they’ll later use for or against their feats in a way not-too-dissimilar from the PDQ System (which may be familiar to those of you who’ve played Ninja Burger 2nd Edition).

The third chapter of character generation involves telling your character’s own story – their first adventure – in the style of a pulp novel. The back of the character sheet will actually end up with a “blurb” on it, summarising the plot of their novel. Then things get complicated. In the fourth and fifth chapters, each character will co-star in the novels of randomly-selected other player characters. This can involve a little bit of re-writing, as stories are bent in order to fit around the ideas of the players, but it serves an important purpose: it gives groups of player characters a collaborative backstory. “Remember the time that we fought off Professor Mechk’s evil robot army?”

Johnny Sparks is a character of my creation.

That’s exactly what Johnny Sparks did in “Johnny Sparks and the Robot Army”. When Professor Mechk released his evil robot army on the streets of New York City, Johnny Sparks – government-sponsored whizkid – knew he had to act. With his old friend Jack Brewood (and Jack’s network of black market contacts), he acquired the parts to build a weapon powered by lightning itself. Then, alongside Mafia child and expert pugilist Michael Leone, he fought his way up the Empire State Building to Mechk’s control centre. While Michael duelled with Mechk, Johnny channeled the powers of the heavens into the gigantic robot brainwave transmitter at the top of the tower, sending it into overload. As the tower-top base melted down and exploded, Michael and Johnny abseiled rapidly down the side to safety.

And so they have a history, you see! And some “aspects” for it: Johnny got “Master of Storms” from his lightning-based research and “With thanks to Jack” for his friend’s support. Meanwhile Jack got “On Johnny’s wavelength” to represent the fact that he’s one of the few people who can follow Johnny’s strange and aspie-ish thought patterns.

Beer, crisps, and roleplaying. What more does an Earthling need?

In our first play session, Michael Leone (Paul), Jack Brewood (JTA), and Anna Midnight (Ruth) found themselves in a race to rescue aviator Charles Lindbergh from the evil Captain Hookshot and his blimp-riding pirates. Hookshot hoped to use the kidnap of Lindbergh as leverage to get his hands on some of Thomas Edison‘s secret research, which he hoped would allow him to gain a stranglehold on the world’s aluminium supply, which was only just beginning to be produced in meaningful quantities. So began an epic boat (and seaplane) chase across the Atlantic to mysterious Barnett Island, a fight through the pirates’ slave camp and bauxite mines, a Mexican-stand-off aboard a zeppelin full of explosives, and a high-speed escape from an erupting volcanic island.

Highlights included:

  • Jack’s afraid of flying, so while the others arrived for the first scenes of the adventure by seaplane, Jack trundled well behind in a cruiser. As a result, he completely missed the kidnapping.
  • When Hookshot was first kidnapping Edison, his attempt was foiled when Ana threw a cutlass at him, severing the grapple he had tied to the scientist.
  • Michael’s a badass at barehand combat. When he wasn’t flinging wild dogs into trees, he was generally found crushing the skulls of pirates into one another.
  • Spirit of the Century encourages a particular mechanism for “player-generated content”. This was exemplified wonderfully by Jack’s observation that he “read once that there was a tribal whaling camp on an island near here, called Ingleshtat.” He paid a FATE point and made an Academics roll, but because I wouldn’t tell him the target of the roll he only knew that he’d “done well”, and not that he’d “done well enough.” He and the other player characters weren’t sure that his knowledge was accurate until they reached the island (and thankfully found that he was right). Similarly, the motivation for the kidnapping wasn’t about aluminium until one of the players speculated that it might be.
  • Ana Midnight’s spectacularly failed attempt at stealth, as she crept via a creaky door into a building full of armed guards. Also, Jack’s fabulous rescue attempt, as he dived and rolled into the building, firing his pistol as he went, while Michael climbed up the zeppelin’s boarding tower, leading to…
  • The tense (and, surprisingly, combat-free… barely!) stand-off and negotiation aboard Hookshot’s zeppelin, towards the end of the story.

There’s a lot of potential for a lot of fun in this game, and we’ll be sure to play it again sometime soon.

× × × ×

Hash Abnib

When I relaunched Abnib the other week (which I swear I didn’t expect to have to do, until people started complaining that I was going to let it die – this genuinely wasn’t some “marketing” stunt!), I simultaneously brought back Abnib Chat (#abnib), the IRC channel.

I blame Jen for this. She told me that she missed the long-dead #rockmonkey chat room, and wanted it (or something similar) back, so I decided to provide one. Hell; if Jen wanted it, maybe other people wanted it to? And it’s an easy thing to set up, I thought.

Personally, I thought that the chat room would be a flop. I’d give it a go, of course, but I didn’t hold up much hope for its survival. When Abnib first launched, back in 2003, the Abnibbers were all students first and foremost. Now, they’ve all got jobs, and many of those jobs aren’t of a variety compatible with sitting on an IRC channel all day. And at night? We’ve got money, nowadays, and homes, and spice, and all kinds of activities that consume our lives on an evening. Many of us get what our younger student selves would call an “early night” every day of the week, and there’s always so much to do that shooting the breeze over a laborious IRC channel simply isn’t compatible with our lives any more.

Looks like I was right. Here’s the channel activity for the first fortnight of the new Abnib Chat:

#abnib participants in June 2011

Sure, the 1st of the month was busy, but not very busy: in actual fact, many of the people who were “around” were only around briefly, and one of those – Guest1332 – didn’t even identify themselves.

We’ve all got new ways of communicating now. Some folks are using Twitter (I occasionally read the feeds of those who write in a way that I’m permitted to see, but I don’t “tweet” myself). Others use Facebook (for a given definition of “use”, anyway). Others still continue to blog (that’s the medium for me: I think I’m just a little too wordy for anything less). In any case; we’re like Abnib: The Next Generation, and we’ve got reliable transporters and replicators and all kinds of cool shit, and hanging around in an IRC channel just feels kind of… backwards.

Perhaps I’ve been watching too much Star Trek recently.

Anyway – unless people object to that, too (seriously?),  I’ll be turning off Iggy later this month: so if you’ve got something important to say to him, say it soon! I’ll leave the “Chat” button on Abnib because it’s lazier than removing it, and you never know if somebody might find a use for it, but I think it’s time to declare the channel “dead”.

Fonts of the Ancients

“Thanks to these changes,” I said, “The Bodleian Libraries websites CMS can now support the use of Unicode characters. That means that the editors can now write web content in Arabic, Japanese, Russian… or even Ancient Egyptian!”

The well-known "man standing on two giraffes" hieroglyph.

It sounded like a good soundbite for the internal newsletter, although of course I meant that last suggestion as a joke. While I’m aware of libraries within the Bodleian who’d benefit from being able to provide some of their content in non-Latin characters – and Arabic, Japanese, and Russian were obvious candidate languages – I didn’t actually anticipate that mentioning Ancient Egyptian would attract much attention. Everybody knows that’s meant as a joke, right?

Streetlights of the 2nd century BC were powered by enormous slugs.

“Is that just Demotic symbols, then? Or can we use all hieroglyphics?” came back the reply. My heart stopped. Somebody actually wanted to use a four thousand plus year old alphabet to write their web pages?

It turns out that there’s only one font in existence that supports the parts of the Unicode font set corresponding to Egyptian hieroglyphics: Aegyptus. So you need to ensure that your readers have that installed or they’ll just see lots of boxes. And you’ll need to be able to type the characters in the first place – if you don’t have an Ancient Egyptian Keyboard (and who does, these days), you’re going to spend a lot of time clicking on characters from a table or memorising five-digit hex-codes.

Papyrus was important, but the Egyptians' greatest achievement was the invention of crazy golf.

But yes, it’s doable. With a properly set-up web server, database, CMS, and templates, and sufficient motivation, it’s possible to type in Ancient Egyptian. And now, thanks to me, the Bodleian has all of those things.

Well: except perhaps the motivation. The chap who asked about Ancient Egyptian was, in fact, having a laugh. In the strange academic environment of Oxford University, it’s hard to be certain, sometimes.

Crocodiles can easily be caught using sleeping bags.

I do find myself wondering what scribes of the Old Kingdom would have made of this whole exercise. To a scribe, for example, it will have been clear that to express his meaning he needed to draw a flock of three herons facing left. Millenia later, we treat “three herons facing left” as a distinct separate glyph from “one heron facing left”, perhaps in a similar way to the way that we treat the Æ ligature as being separate from the letters A and E from which it is derived. He couldn’t draw just one heron, because… well, that just wouldn’t make any sense, would it? So this symbol – no: more importantly, it’s meaning – is encoded as U+13163, the 78,180th character in an attempted “univeral alphabet”.

Starting step in the creation of "vulture and asp soup".

To what purpose? So that we can continue to pass messages around in Ancient Egyptian in a form that will continue to be human and machine-readable for as long as is possible. But why? That’s what I imagine our scribe would say. We’re talking about a dead language here: one whose continued study is only justified by an attempt to understand ancient texts that we keep digging up. And he’d be right.

All existing texts written in Ancient Egyptian aren’t encoded in Unicode. They’re penned on rotting papyrus and carved into decaying sandstone walls. Sure, we could transcribe them, but we’d get exactly the same amount of data by transliterating them or using an encoding format for that specific purpose (which I’m sure must exist), and even more data by photographing them. There’s no need to create more documents in this ancient language: just to preserve the existing ones for at least as long as it takes to translate and interpret them. So why the effort to make an encoding system – and an associated font! – to display them?

Two-headed snakes: the original skipping rope.

Don’t get me wrong: I approve. I think Unicode is awesome, and I think that UTF-16 and UTF-8 are fantastic (if slightly hacky) ways to make use of the breadth of Unicode without doubling or quadrupling the amount of memory consumed by current 8-bit documents. I just don’t know how to justify it. All of those bits, just to store information in a language in which we’re producing no new information.

What I’m saying is: I think it’s wonderful that we can now put Egyptian hieroglyphics on the Bodleian Libraries websites. I just don’t know how I’d explain why it’s cool to a time-traveling Egyptian scribe. Y’know; in case I come across one.

× × ×

Poly and the Census – Part Four

Following up on my earlier blog posts about how data on polyamorous households is recorded in the census (see parts one, two, and three), as well as subsequent queries by Zoe O’Connell on this and related topics (how the census records data on other relationships, such as marriage between same-gender partners and civil partnerships between opposite-gender partners), there’s finally been some progress!

No; that’s a lie, I’m afraid. We’re still left wading around in the same muddy puddle. Zoe’s Freedom of Information Act request, which basically said “Okay, so you treat this kind of data as erroneous. How often does this happen?” got a response. And that response basically said, “We can’t tell you that, because we don’t have the information and it’d cost too much to work it out.” Back to square one.

Still: it looks like she’s not keen to be beaten, as she’s sent a fresh FoI request to instead ask “So what’s the algorithm you’re using to detect this erroneous data?” I was pleased to see that she went on to add, effectively, “I don’t need an explanation: send me the code if you need to,” which makes it harder for them to fall behind the “It’s too expensive!” excuse yet again.

Anyway: it’s one to watch. And needless to say, I’ll keep you all posted when anything changes…

My New Pet Hate, part II

A few years ago, I talked about a pet hate of mine that still seems to be prevalent: that is – that when people send me a screenshot, they’ll sometimes send me it in a Word document, for no apparent reason. They could just send me the picture, but instead they send me a Word document containing the picture, thereby increasing the file size, requiring that I have a program capable of viewing Word documents, and making it more-complex for me to extract the picture if I need to use it somewhere. And on top of all of that, it takes longer for them to do it this way: everybody loses!

Today, I saw somebody take the abuse of screenshots to a whole new level. My first clue that something was amiss was when the email arrived in my Inbox with a 300K TIFF file in it. “Well, at least it’s not a Word document,” I thought. And I was right. It was something more convoluted than that.

My only explanation for the contents of the file is as follows:

  1. Print Screen. The user took the screenshot using their Print Screen key. So far, so good. They captured their whole screen, rather than just what they were trying to show me, but we’ll let that pass.
  2. Open Paint. The user opened Paint. At this point, they could have pasted, saved, and emailed the file to me, and still been doing perfectly well. But they didn’t.
  3. Resize canvas. The user expanded the canvas to an enormous size. Perhaps they didn’t know that this would be done automatically, if required. Or maybe they thought that I could do with a lot of white space in which to make notes on their screengrab.
  4. Paste and reposition. The user pasted the screenshot into the Paint document, and positioned it near the centre, making sure to leave as much whitespace as possible. Y’know, in case I was running out of it on my computer. They could still at this point have just saved the file and emailed it to me, and I wouldn’t have complained.
  5. Print Screen again. For some reason, the user pressed Print Screen again at this point, thereby taking a screenshot of themselves manipulating a screenshot that they’d already taken. Maybe the user has recently watched Inception, and decided that “a screenshot within a screenshot” was more likely to make an impact on me. We need to go deeper!
  6. Open Photoshop. Paint obviously wasn’t going to cut it: it was time for a bigger graphics program. The user opened up Photoshop (waiting for a few minutes while this beast of a program warmed up).
  7. Create a new document and paste again. Now the user had Photoshop open, containing a picture of Paint being used to display an (oversized) screenshot of what they wanted to show me.
  8. Crop. This was a good idea. If the user had cropped the image all the way back down to the screenshot, I might not even have worked out what they were doing. Sadly, they didn’t. They cropped off Paint’s title bar and half of its toolbar. Then they added another few layers of whitespace to the bottom and right, just to be really sure.
  9. Save as a TIFF. They could have saved as a PNG. Or a GIF. Even a JPEG. They could have saved as a PSD. But no, for some reason, an uncompressed TIFF was the way forwards.
I N C E P T I O N. A screenshot of a screenshot within a screenshot.

Back in 2009, I predicted that Windows Vista/7’s new “Snipping Tool”, which finally brought screen captures to the level of more-competent operating systems, would see the end of this kind of nonsense. Unfortunately, Windows XP remains the standard at my workplace, so I doubt that this’ll be the last time that I see “matryoshka screenshots”.

×

Showing Some Pride

Paul and I seem to be featured in today’s Oxford Mail.

"Gay Pride March Ends City Celebration", in the Oxford Mail

From the article –

Friends Dan Q and Paul Mann, of Kennington, decided to mark the [superheroes] theme by dressing as characters from the silver age of comic book heroes, the Flash and Kickass, far left.

Mr Q, 30, said: “We wanted to take part in the march because first of all it’s an excuse to dress up, and also to show that Oxford is home to gay, lesbian, and bisexual people and they should be represented.”

Apart from the obvious fault with the age of our characters – Kick-Ass (here correctly hyphenated) is a very new comic book character, designed in from only 2008 – which could have been corrected with a quick Wikipedia search, the article’s not bad. I’m reasonably pleased with my soundbite quotation, there: the journalist we spoke to caught me off-guard so I just reeled off the first thing I thought of, but it’s not bad, at least.

Ruth managed to carefully avoid appearing in any press photographs, but I think she’ll have been hard-pressed to avoid all of the shots my the Pride photographer, who ran around enthusiastically in a pink day-glow jacket, snapping away.

Dan and Paul.

The Oxford Pride parade was fun, with the exception of the Catholic protest on Cornmarket, with their calls to “repent” from our “sinful lives”, and it was nice to lounge on the grass at Oxpens and listen to the music at the fair. Paul came second, by my estimation, in the fancy dress competition, and then I leapt around on a bouncy-castle/slide-thingy and sent all of the alcohol in my bloodstream rushing to my head.

Later, it rained, and I was too drunk to care.

× ×

On This Day In 2003

Looking Back

On this day in 2003, I first launched this weblog! That means it’s eight years old today! I’d bought the scatmania.org domain name some time earlier with the intention of setting up a vanity site separately from my sub-site on the avangel.com domain, during a rush on cheap domain names perpetrated by some of the friends I’d lived with in Penbryn, but never found a significant use for it until this day. It was at about the same time that I first set up (the long-defunct) penbryn-hall.co.uk, a parody of Penbryn’s website launched as an April Fools joke against the hall, which eventually got me into some trouble with the management committee of the halls. Some friends and I had made it a tradition of ours to play pranks around the residence: our most famous one was probably 2003’s joke, in which we made a legitimate room inspection out to be an April Fools joke, with significant success.

scatmania.org in August 2003. The theme is simplistic, and the blog itself is powered by a custom-built PHP engine back-ending onto a stack of flat files. It worked, just about, but it wasn’t great.

In my initial blog post, I took care to point out that this wasn’t by any stretch of the imagination my first foray into blogging. In actual fact, I’d run a weblog, The Åvatar Diary, for a few years back in college: a few fragments of this still exist and are archived here, too. I suppose that this means that, ignoring the occasional gap, I’ve been blogging for almost thirteen years. The Åvatar Diary died after an incident with a rather creepy stalker: remember that this was in 1999, back in the day when Creepy Internet Stalkers were still new and exciting, and I panicked slightly and shut the Diary down after my stalker turned up in person somewhere that I’d hinted that I might be in a post.

I didn’t mention the new site launch, to begin with, hoping that folks might just “pick up on it” having re-appeared (I’d been promising to launch something at that domain for ages). Later, I launched Abnib, in an attempt to unite the LiveJournal users with whom I associated with those of us who hosted our own blogs. Abnib still runs, after a fashion, although I’m likely to let it die a natural death as soon as it wants to.

scatmania.org in November 2005. The site looked a lot more professional by now, and was beginning to sport the thick blue header that was it’s hallmark all the way up to 2010.

Looking Forward

So here I am, eight years later, still blogging on the same domain. The frequency with which I write has waxed and waned over the years, but I still find that it’s just about the best way for me to keep in touch with my friends and to keep them posted about what’s going on in my life: it’s unintrusive and can be dipped in and out of, it’s accessible to everybody, and – because I host it on my own domain – it’s under my control. That’s a million points in its favour over, say, Facebook, and it’s nice to know that it’ll exist for exactly as long as I want it to.

A recent screenshot of scatmania.org. Whoah: this has all gone a bit recursive.

It also provides a great “starting point” by which people find me. Google for me by name or by many of the aliases I go by and you’ll find this site, which I think is just great: if people are trying to find me online I’m happiest knowing that the first pages they’ll get to are pages that I control, and on which I write what I want to: I’ll bet U.S. Senator Rick Santorum wishes that he had that.

I enjoy blogging about geeky stuff that interests me, things that are going on in my life, and my occasional and random thoughts about life, the universe, and everything (with a particular focus on technology and relationships). It’s put me in contact with some strange people – from pizza delivery guys who used to bring me food on Troma Nights back in Aber to crazy Internet stalkers and confused Indian programmers – and it’s helped me keep in touch with the people closest to me. And because I’m a nostalgic beast, as this and similar posts show, it’s a great excuse to back-link my way down memory lane from time to time, too.

This blog post is part of the On This Day series, in which Dan periodically looks back on years gone by.

× × ×