Cyclists In Southwark

There is a postcode lottery about which boroughs you have to live in, if you want to automatically belong to an LCC borough group. The boroughs shown in blue on this map do not have an LCC website (probably for political reasons), so will have difficulty in organising LCC rides.

It was a lovely sunny morning when four of us met at the Southwark Needle to do what had morphed into a Silvertown Tunnel Ride. Unfortunately one of our riders couldn't make it because of a domestic emergency. There were no Southwark Healthy Riders in sight, but this must have been because we had chosen a wrong Saturday. There was another group of four at the start point, but it wasn't clear what website they had used to arrange to meet up.

Once we had set off, we could see that works were still taking place to improve Cycleway 4. But they had don a good job because it now only takes about half an hour to reach Cutty Sark.

We then chose a route which took us through the heart of the construction works to build the Silvertown Tunnel. This, of course, is the bête noire of some cyclists, but is clearly needed to reduce congestion and pollution on the A102 Blackwall Tunnel Approach Road on the Greenwich Peninsula. The construction work is progressing well and it should be operational in about a year's time. This is a surprise considering how long it is taking to reinstate the traffic flow across the Hammersmith Bridge.

Just as we arrived, we saw a large section of the new Boorde Street walking and cycling bridge being hoisted into position. The bridge is very impressive, with very wide aisles and a gentle gradient:

We then stopped off to see the impressive Damian Hurst statue at the Cable Car Station.

The Thames Path has now been reinstated on the section just before the Woolwich Ferry. When we got to the Woolwich Ferry we came across a very large Let's Go Cycling group (which, despite doing rides that are very much like Southwark Healthy Rides, is rumoured to have broken away from the now-defunct LCC group Bexley Cycling because of a dispute about the wearing of cycle helmets!). This group had cycled from their meeting point in Danson Park. We joined in with them for a short distance to the Woolwich Foot Tunnel and nearly lost a couple of riders there to that group (this was not the first time that this had happened - a similar thing happened to a group of Southwark Healthy Riders on an earlier Royal Docks Ride, who bumped into the Let's Go Cycling group near The Crystal building!).

We had to use the Woolwich Foot Tunnel as the ferry no longer runs at the weekend. The north lift was out of action and were told it has been like this for a year or so - it has been difficult to find replacement parts for the lift.

After stopping off at the Well Bean Café, we returned past the northern Silvertown Tunnel works to Tower Bridge.

Experiments have been carried out to see what would happen if someone tried to clone the "official" Cyclists in Southwark website and set up an unofficial one. It would still have HTTPS encryption, but its security certificate would be "self-signed", rather an being approved of by an official organisation. Rides could be advertised on the site, but they would be uninsured. If you want to find this "fake" Cyclists In Southwark website, its URL is the subdomain f.cyclistsinsouthwark.org.uk. If you go to this site, your browser will give you various warnings indicating that the site is not to be trusted and should not to be used for storing personal data. If you click on the "Advanced" button, the browser will still let you go to the site, but you will have to acknowledge that you are aware of the warnings.

If you type in the following at a Linux command line prompt:

• curl https://f.cyclistsinsouthwark.org.uk/

this is the message you get back:

• curl: (60) SSL certificate problem: self signed certificate
  More details here: https://curl.haxx.se/docs/sslcerts.html
• curl failed to verify the legitimacy of the server and therefore could not
  establish a secure connection to it. To learn more about this situation and
  how to fix it, please visit the web page mentioned above.