emperor: (Default)
posted by [personal profile] emperor at 06:06pm on 22/06/2009 under , , ,
I would like to remind everyone of rule 163 [0]. It exists to protect a vulnerable minority who are regularly subjected to abuse and intimidation by a more powerful group. That intimidation and abuse nearly always goes unpunished unless injury results, and if this minority are killed and a prosecution occurs, the penalties are relatively small. I'm talking about cyclists.

Rule 163 states, amongst other things "give motorcyclists, cyclists and horse riders at least as much room as you would when overtaking a car", which is sadly not very clear, but is helpfully illustrated:



It is my experience that many many drivers ignore this rule entirely if obeying it would mean the slightest delay to their journey. When you're in a car, please remember rule 163, and give cyclists plenty of room; if you're not driving, encourage the driver to do so, especially if they are a professional driver.

When commuting, I find I often have an unpleasant choice to make - either I cycle in the primary position, in the center of my lane, and get shouted and honked at and overtaken dangerously by some drivers who want to punish me for holding them up, or I cycle in the secondary position (about 1m from the kerb) and get people squeezing past with inches to spare because they are trying to overtake even though there is oncoming traffic and it's not safe to do so. This is quite frankly unacceptable.

On one evening cycle home, one taxi driver passed me twice (I overtook him while he was queuing in traffic). On both occasions, he sounded his horn repeatedly, revved his engine hard, and overtook dangerously close - if he'd misjudged it, or I'd wobbled, he would surely have hit me. I complained to the council's taxi licensing officer who said he'd do nothing unless there was a prosecution. The police/CPS won't prosecute unless a cyclist is injured, so taxi drivers can (and do) behave dangerously around cyclists they don't like without fear of any comeback.

There are a few further points I'd like to raise:

Cycle facilities are often worse than useless. The recommended width of a cycle lane is 2m; almost none that are not also bus lanes are this wide. That means that motorists overtaking at the white line (which many of them do) are passing at much less than the Rule 163 distance. Furthermore, the surface of these on-road cycle lanes is often poorer than the rest of the road, and they fill with debris from the road. I often cycle just outside these sort of lanes for these reasons. Shared-use paths for pedestrians and cycles are dangerous, for both cyclists and pedestrians; indeed there is research showing they are more dangerous to cycle on than the road proper. If you cycle much faster than walking pace, there is a risk of collision with pedestrians who meander across the shared-use path as if it were a pavement, and for all cyclists, there is a risk of collision wherever the path crosses a side-street - it seems that drivers don't expect to meet cyclists at these points, so fail to spot them. Indeed, I'd go as far as to say that many cycle facilities actually make cycling more dangerous, as drivers are more likely to bully cyclists using the road if they see such a facility that the cyclist isn't using.

Accordingly, I'd like to remind drivers that cyclists are not obliged to use these facilities, and you should not shout at those that choose not to. As I say above, often the cyclist is safer on the road. More generally, though don't intimidate cyclists who you feel are delaying you. Cyclists are perfectly entitled to be on the roads, and are a vulnerable group of road users. If you feel a cyclist has made an odd decision about whether to use a cycle facility or not, whether or not to wear a helmet, or whatever, consider that they are entitled to make their own minds up about these things, and have probably given the matter more thought than you have. Shouting "helpful" comments to them is bullying.

Finally, and it shouldn't need saying, driving dangerously to intimidate or punish cyclists is immoral and illegal. Don't do it! I should be able to cycle to and from work free from people threatening to kill or maim me with their vehicles. In an ideal world, there would be effective sanctions against dangerous drivers who collide with cyclists, even if the cyclist is not seriously injured. In practice, this doesn't happen, and even when drivers kill cyclists, they not infrequently escape being charged with any offense.

So yes, remember rule 163, and give cyclists a chance!

ETA This DfT article is quite sensible.

[0] No, this isn't a joke about rules about porn on the internet
emperor: (Default)
posted by [personal profile] emperor at 09:46pm on 27/03/2007 under ,
I've been thinking about this post for a while now, and held off posting it for fear of offending someone. After discussion on #chiark, I've decided to post it.

cut for content that some may find distressing )
emperor: (lego scholar)
posted by [personal profile] emperor at 07:20pm on 08/07/2005 under , ,
Someone linked to This article from the New York Times (requires registration, bugmenot works) on SOCNET, the mailing list for INSNA members, and other researchers working in social networks. The article annoyed me, so I composed a response:

Read more... )

One reader suggested I send it to the editor of the NYT; I note they say 150 words is the maximum length of a letter. Maybe I should just send it anyway? I'm not sure I have arsed to chop it to 150 words.
Mood:: 'determined' determined
emperor: (Default)
posted by [personal profile] emperor at 05:23pm on 29/06/2005 under , ,
Another machine I have an account on has recently created a "journals" newsgroup, which I will refer to here as cabal.journals. The idea is that cabal users will post their lj/blog/mono/whatever diary entries into it along with a subject-line tag to say whose they are. So, if my username on cabal was herringl, this entry would appear as something like:

From: localpart@domain
Newsgroups: cabal.journals
Subject: [herringl] cabal.journals
...

And any comments would start a usenet-style thread.

I was initially a little uncomfortable with the idea, so I thought I'd set down what I thought about how I use LJ, and how that interacts with such nntp-gateways. During the gestation of this essay, OpenID has come along, so excuse me if my thoughts about that are a little dysmature, as it were.

So, what do I use LJ for? I can divide my entries up into a few broad categories:

  1. Essays on things I consider important or interesting (e.g. the comments on the Lancet's paper on the death penalty)
  2. Essays on professional topics (e.g. the organic milk rant)
  3. More or less lengthy/interesting comments on what's going on in my life
  4. Plugs for events or church services
  5. Writings about what I'm doing at work
  6. Requests for help
  7. The odd meme
  8. Keeping up with my friends, both "real" and "online"


Now some of these are obviously things that I want to achieve wide readership, so are posted publically. Some of them I don't really care who reads them (so are posted publically). Some I want to be extra sure that googling parents, future employers, current co-workers and so on can't read, so get friends-locked. Some I only want a few close friends to read, so can be posted to small friends-filters.

cabal.journals provides a means whereby people who don't want to use their own RSS aggregator of choice can read my public entries. I don't feel I can post any of the categories of friends-locked posts there since I don't know all the people with accounts on cabal, and I know that at least some of the accounts on there are pseudonyms. Also, while I can be pretty sure I'll never friend a co-worker on LJ, I can't really say to sysadmin@cabal "no, don't give that person an account because I don't want them to see bits of my journal". Furthermore, there's absolutely no way of restricting who can read my postings to cabal.journals, so I want to discourage people I actually know reading my witterings there, as they could read more of my LJ via a method where I can restrict readership (LJ or OpenID currently).

The downside of propagating articles to cabal.journals is that because the propagation technology is one-way, it means I have to go chasing after comments in more places than I do now, and that I might end up with two different conversations out of sync with each other in response to the same entry. Experience suggests that people aren't good at following instructions of the form "you can read this in this medium, but please go and comment on it over there". I clearly also have an interest in my friends maintaining journals in the same place, as it makes keeping up with them easier. If everyone I wanted to keep in touch with had LJs this would be ideal; blogs that can be syndicated to LJ are OK, but there's the faff about keeping up with comments (LJ doesn't currently extract comments from syndicated entries and put them into the LJ-feed).

OpenID will complicate matters, I think. If Fred is using blogspot, and starts wanting to OpenID-filter their posts, then the current LJ-feed mechanism is going to become inadequate (already, you can't usefully friends-lock an LJ-feed). OpenID should make it possible for people to read my LJ, including some friends-locked posts, without them needing an LJ-account, although I'm not sure if this can actually be usefully made to work yet.

I should address some of the supposed advantages of cabal.journals. Firstly, it has been opined that LJ-comments are a pretty ropey way of holding a discussion, particularly between third parties - if you're not the journal's owner, you can't get LJ to email you all comments to an entry (and AIUI the RSS support for comments on LJ isn't useful), so keeping up with old discussions is hard. Also, the comments interface to LJ isn't great for large discussions. I must accept these criticisms of LJ. I think the answer is to fix LJ, though. Many of my LJ-fiends don't have access to cabal, so LJ is currently the only place that discussion can carry on and be participated in by all readers of an entry. Maybe if it could be fixed such that comments went both ways that would help...

Also, it has been pointed out that some LJers have a very autocratic view of what goes on in their LJ, and will delete comments or whole entries on a whim, or if something someone says offends them. Also, users may be de-friended by someone, and then be unable to read the long insightful comment they left in a locked entry in that person's journal. This, I think, is a social problem. Whilst posting to cabal.journals would stop me deleting discussions on a whim, there would clearly have to exist a mechanism where I could require cabal's newsmaster to do so for me (if a commenter disclosed confidential information about me, for example), and that's a whole extra can of worms, unless the relevant policy is exceedingly well-written. So, dear reader, you'll have to take it on trust that I won't behave like an arsehole here ;)

In summary, I remain unconvinced that cabal.journals is not a bad idea. It addresses valid problems, but not in a manner that seems to be compatible with what I reasonably want to use my journal for.

[As an aside, I've added the facility for readers to tag my entries. Friends can create new tags and so on, too. Please don't abuse these powers.]

October

SunMonTueWedThuFriSat
      1
 
2
 
3
 
4
 
5
 
6
 
7
 
8
 
9
 
10
 
11
 
12
 
13
 
14
 
15
 
16
 
17
 
18
 
19
 
20
 
21
 
22
 
23
 
24
 
25
26
 
27
 
28
 
29
 
30
 
31