zub | Reading

My plans for mudlarking on Saturday were thwarted when all my trains were cancelled. It took me three hours to get to Lincoln’s Inn Fields where I was going for a picnic so I didn't have time to mudlark as well.

On Sunday, I broke a bowl, dropped it on the floor and it smashed, and I held up a triangular sherd and wondered whether people would find the sherd from my bowl in the future, with a peri-peri flavour. I wondered if I should take it to the foreshore.

On the Sunday though, the trains were running again, so I headed to Blackfriars. The blue Croc was still there that I saw on Friday. I walked along a wooden plank that had washed up. It was a hot day but at that time I was the only one on the foreshore.

I picked up more small black tiles, but one had the corner damaged.

I heard music from a busker by the station.

I was no longer feeling how I used to when I started mudlarking, no feeling of Flow, no clearing of the mind. I wondered if I'd grown bored of it and should play more Ingress.

I seem to have trained my eyes to spot pottery sherds but I would like to find other things more as I have a lot of sherds now.

I found a cork and when I got it home I realised it said “Kylie Minogue” on it. I hadn't realised Kylie Minogue wine existed and you can buy it at Sainsbury's.

I found a red piece that could be a bit of brick or tile that looks like it says “Taylor” on it.

I found some glass that looked like it said “ord” on it. Ordinary?

I found a sherd that says “don” and presumably once said “London”.

--
I headed to Wapping after that, as the tide got lower.

While I had been to the Prospect of Whitby (the Pelican Stairs) before I hadn't been to the other bit of Wapping - accessed through the New Crane Stairs.

The steps there were missing at the bottom, replaced with boulders, so I used the green slimy wall for balance.

I thought I was alone there on the foreshore until I noticed the people fishing, with their lines cutting off part of the shore. I walked in the opposite direction and walked along the foreshore to Wapping Pier.

I saw Canada Geese and goslings lying on the foreshore.

I passed one set of stairs that had been removed - Wapping Dock Stairs. There were a few concrete steps to start with but the metal stairs that were once there were no longer.

King Henry's Stairs at Execution Dock, near to Wapping Pier were actually just a metal ladder.

I walked back to the New Crane Stairs.

I saw a duck with five ducklings following, moving fast across the foreshore.

I saw a man in the Thames, water up to his shorts, spear fishing.

I enjoyed Wapping as it was somewhere new - maybe that was the problem earlier, lack of novelty at Blackfriars. It also felt vast and quieter without all the tourists walking past.

I found a lot of pottery sherds in Wapping - I am collecting blue and white ones currently for a mosaic, but there was one that looked almost like a nose, one with a letter ‘E’ and various pieces with patterns I haven't seen before. There was also some glass that had degraded and looked so pretty.

mjg59

Single signon is a pretty vital part of modern enterprise security. You have users who need access to a bewildering array of services, and you want to be able to avoid the fallout of one of those services being compromised and your users having to change their passwords everywhere (because they're clearly going to be using the same password everywhere), or you want to be able to enforce some reasonable MFA policy without needing to configure it in 300 different places, or you want to be able to disable all user access in one place when someone leaves the company, or, well, all of the above. There's any number of providers for this, ranging from it being integrated with a more general app service platform (eg, Microsoft or Google) or a third party vendor (Okta, Ping, any number of bizarre companies). And, in general, they'll offer a straightforward mechanism to either issue OIDC tokens or manage SAML login flows, requiring users present whatever set of authentication mechanisms you've configured.

This is largely optimised for web authentication, which doesn't seem like a huge deal - if I'm logging into Workday then being bounced to another site for auth seems entirely reasonable. The problem is when you're trying to gate access to a non-web app, at which point consistency in login flow is usually achieved by spawning a browser and somehow managing submitting the result back to the remote server. And this makes some degree of sense - browsers are where webauthn token support tends to live, and it also ensures the user always has the same experience.

But it works poorly for CLI-based setups. There's basically two options - you can use the device code authorisation flow, where you perform authentication on what is nominally a separate machine to the one requesting it (but in this case is actually the same) and as a result end up with a straightforward mechanism to have your users socially engineered into giving Johnny Badman a valid auth token despite webauthn nominally being unphisable (as described years ago), or you reduce that risk somewhat by spawning a local server and POSTing the token back to it - which works locally but doesn't work well if you're dealing with trying to auth on a remote device. The user experience for both scenarios sucks, and it reduces a bunch of the worthwhile security properties that modern MFA supposedly gives us.

There's a third approach, which is in some ways the obviously good approach and in other ways is obviously a screaming nightmare. All the browser is doing is sending a bunch of requests to a remote service and handling the response locally. Why don't we just do the same? Okta, for instance, has an API for auth. We just need to submit the username and password to that and see what answer comes back. This is great until you enable any kind of MFA, at which point the additional authz step is something that's only supported via the browser. And basically everyone else is the same.

Of course, when we say "That's only supported via the browser", the browser is still just running some code of some form and we can figure out what it's doing and do the same. Which is how you end up scraping constants out of Javascript embedded in the API response in order to submit that data back in the appropriate way. This is all possible but it's incredibly annoying and fragile - the contract with the identity provider is that a browser is pointed at a URL, not that any of the internal implementation remains consistent.

I've done this. I've implemented code to scrape an identity provider's auth responses to extract the webauthn challenges and feed those to a local security token without using a browser. I've also written support for forwarding those challenges over the SSH agent protocol to make this work with remote systems that aren't running a GUI. This week I'm working on doing the same again, because every identity provider does all of this differently.

There's no fundamental reason all of this needs to be custom. It could be a straightforward "POST username and password, receive list of UUIDs describing MFA mechanisms, define how those MFA mechanisms work". That even gives space for custom auth factors (I'm looking at you, Okta Fastpass). But instead I'm left scraping JSON blobs out of Javascript and hoping nobody renames a field, even though I only care about extremely standard MFA mechanisms that shouldn't differ across different identity providers.

Someone, please, write a spec for this. Please don't make it be me.

rmc28

You may have noticed it's been hot in England. So a lot of this week has just been the extra routines to cope with that (airing out the house at night / early morning, extra hydration, more naps).

It was a three-day week at work for me, with Monday my travel day back from Prague, and Wednesday a multi-errand day. Tuesday was a hectic day at work, but a rare evening with very few plans, so I actually rested. Wednesday had EHCP review for one child; a lunchtime skating lesson for me; a school bowling trip, hospital appointment and shopping all with the other child; and then Kodiaks practice in the evening.

( lots of ice hockey )

This week and next are 4-day weeks at work for me; I am having a long weekend away in Portsmouth with one of my oldest friends from university. Probably my only trip away this year that isn't directly about ice hockey. (But there is a rink in Gosport and both of us skate.) We plan to visit the Mary Rose, and I at least want to visit both the Submarine Museum and the Explosion Museum. I have been intrigued by the latter since I saw a road sign for it on the way to Gosport rink last month, but haven't yet found anything else about it apart from name and location. No spoilers!

squirmelia

I attended an Ambient Lit workshop at Voidspace and we were asked to take a walk and take notes and photos. I took a random card and it said “dog” on it.

–

I am a dog.

I walk through a puddle.

I sniff a bag of rubbish with a coffee cup in.

I am curious about a traffic cone.

I am looking at the road and pavement a lot. There's an intriguing drain cover, I look at the bottom of a bollard.

Another bag of rubbish I sniff at.

I see people waving their arms about and wonder about barking at them.

I walk past a flower on the pavement.

I am lingering longer.

I go up a narrow alleyway and end up at a dead end, so turn around.

I haven't seen any other dogs. I hope to.

An interesting Ironworks sign on the pavement.

A drain cover clonks as I walk over it.

There are no balls to chase.

I bark at some pigeons.

I sniff something on the ground.

I chase pigeons

I want to bark at the policemen.

The ground says Shallow.

I think I've found another dog! Woof! Woof!

I run away from my owner to get back to the theatre on time.

jack

Swam 2mi downstream from Grantchester to the rollers. That's half a mile further than I did to the canoe club at the Slow Swim.

I was out of practice, muscles were v tired but it was v nice to do. I could have gone farther with another little sit down.

I'd been interested to see if I could do that last stretch into town. It's not really good swimming, more punts and more concrete edges, but it was easy to do. I hadn't realised it was only half a mile.

I have previously swum down from Hauxton Mill to Byron's Pool, and Byron's pool to Grantchester. I guess that adds up to 4.5mi of Granta and Cam, compared to ~20mi length of the Cam (excluding the Great Ouse below the Little Ouse and the Granta above Hauxton Mill)

rmc28

(I forgot to mention that for about twenty minutes of the day I flew to Prague, I couldn't find my passport, because it was not in the box where it normally lives at home. That was not a fun twenty minutes, and much love to both Tony and Charles for joining me in the search. We found it eventually, it had fallen down the side of the shelf on which the passport box lives, in a way that meant you could only see it from one specific angle. Thankfully, I eventually stood at that angle and spotted it.)

The ice hockey camp continued to be excellent and very hard work, and I feel like I learned a great deal (and now I need to remember to keep using everything I learned and not fall back into bad habits). The coaching was very supportive and kind while pretty much pushing me to my physical limits. I very much hope to return on future camps.

The Saturday evening we went into central Slaný where there was a kind of beer festival happening, lots of different beer stands around the town square, a live rock band on stage, and a bunch of fairground rides. Sunday lunchtime, after the camp was finished, the original three of us got an Uber into Prague in the gloriously hot and humid afternoon. The other two had been to Prague before so I went off on my own to do some tourist things (boat tour! historical tram! walking across the Charles Bridge!) and messaged them when I was ready to meet up again. Turned out we were about five minutes walk apart at that point.

I took a load of photos but actually this random selfie for my family is one I'm really happy with:

We had dinner in Prague, during which time the hot weather broke into torrential downpour, and did a bit more walking around once that tailed off into intermittent showers, but eventually got back to Slaný for the evening. We got packed up and out of our rooms as requested in the morning but were able to leave our kit in storage while we had a leisurely walk and hipsterish brunch in Slaný before it was time to head to the airport.

Getting home was tediously delayed by train cancellations but I still got home in time to put the first washload on and repack my kitbag for Warbirds practice Monday evening.

squirmelia

It was a hot day and I went to Cousin Lane Stairs to start with and took my hiking pole this time to get over the boulders, which worked well, but I am still wary of the tide there as I haven't spent enough time there to know how long it's safe for.

The Banker pub just at the top of the stairs was busy with people enjoying the sunshine and their beers. One or two people sat on the foreshore for a bit, but I was the only person on the foreshore across the boulder, past Cannon Street railway bridge.

The first thing I found was a plastic card that had a sticker saying “Billy Hicks”.

I also found what looks like the top of a teapot, a few other sherds, and a little yellow bit, which was probably once part of a brick and is now perhaps a Thames potato.

My second location was near the Millennium Bridge and there were a few mudlarkers there. I watched a cormorant enjoying the water.

I picked up an oyster shell with a circular hole in it. I don’t usually pick up shells but I recently read that they may have been used as tiles.

I found a white sherd with a lion mark on it, a sherd with colourful flowers, and a yellow piece with a pie crust edge. I also found another brown star to go with my brown star collection.

“Have you found anything good?” I was asked as I reached the top of the stairs.

My third location was back to Blackfriars and it felt cooler as I walked across the bridge. There was a nice breeze and also some shade under the bridge.

It was nice to just walk along by the river, but then the thoughts came, too many thoughts. I guess that’s the thing with mudlarking - sometimes it clears my mind and I can just focus on the foreshore, and other times as I can’t distract myself by looking at a phone or anything, the thoughts pile on in.

On the top of the pile of bones was a plastic blue shoe, a Croc.

I found a piece of glass that says “PER” on it, which could perhaps once have said “SUPERIOR”.

I found a nice piece of combed slipware, that has a red outline.

I found some nice pebbles and another small black tile to go with my collection.

squirmelia

Wednesday involved no mudlarking, as the tide was too high, but I did walk along the river past Queenhithe, where you are definitely not allowed to mudlark. It is a Scheduled Ancient Monument and has the remains of an old dock there. There are signs beside it and a mosaic, but although I’d read the signs previously, I'd never paid too much attention to it.

I could see sherds and pipes and oyster shells on the foreshore from standing on the path beside it though.

The PLA map has Queenhithe marked in red, but intriguingly on their map, it looks like you could mudlark just to the side of it, or in front of it, if the tide was out enough. I would worry though that I wouldn't know where the line was between allowed and definitely not.

mjg59

23 years ago I was in a bad place. I'd quit my first attempt at a PhD for various reasons that were, with hindsight, bad, and I was suddenly entirely aimless. I lucked into picking up a sysadmin role back at TCM where I'd spent a summer a year before, but that's not really what I wanted in my life. And then Hanna mentioned that her PhD supervisor was looking for someone familiar with Linux to work on making Dasher, one of the group's research projects, more usable on Linux. I jumped.

The timing was fortuitous. Sun were pumping money and developer effort into accessibility support, and the Inference Group had just received a grant from the Gatsy Foundation that involved working with the ACE Centre to provide additional accessibility support. And I was suddenly hacking on code that was largely ignored by most developers, supporting use cases that were irrelevant to most developers. Being in a relatively green field space sounds refreshing, until you realise that you're catering to actual humans who are potentially going to rely on your software to be able to communicate. That's somewhat focusing.

This was, uh, something of an on the job learning experience. I had to catch up with a lot of new technologies very quickly, but that wasn't the hard bit - what was difficult was realising I had to cater to people who were dealing with use cases that I had no experience of whatsoever. Dasher was extended to allow text entry into applications without needing to cut and paste. We added support for introspection of the current applications UI so menus could be exposed via the Dasher interface, allowing people to fly through menu hierarchies and pop open file dialogs. Text-to-speech was incorporated so people could rapidly enter sentences and have them spoke out loud.

But what sticks with me isn't the tech, or even the opportunities it gave me to meet other people working on the Linux desktop and forge friendships that still exist. It was the cases where I had the opportunity to work with people who could use Dasher as a tool to increase their ability to communicate with the outside world, whose lives were transformed for the better because of what we'd produced. Watching someone use your code and realising that you could write a three line patch that had a significant impact on the speed they could talk to other people is an incomparable experience. It's been decades and in many ways that was the most impact I've ever had as a developer.

I left after a year to work on fruitflies and get my PhD, and my career since then hasn't involved a lot of accessibility work. But it's stuck with me - every improvement in that space is something that has a direct impact on the quality of life of more people than you expect, but is also something that goes almost unrecognised. The people working on accessibility are heroes. They're making all the technology everyone else produces available to people who would otherwise be blocked from it. They deserve recognition, and they deserve a lot more support than they have.

But when we deal with technology, we deal with transitions. A lot of the Linux accessibility support depended on X11 behaviour that is now widely regarded as a set of misfeatures. It's not actually good to be able to inject arbitrary input into an arbitrary window, and it's not good to be able to arbitrarily scrape out its contents. X11 never had a model to permit this for accessibility tooling while blocking it for other code. Wayland does, but suffers from the surrounding infrastructure not being well developed yet. We're seeing that happen now, though - Gnome has been performing a great deal of work in this respect, and KDE is picking that up as well. There isn't a full correspondence between X11-based Linux accessibility support and Wayland, but for many users the Wayland accessibility infrastructure is already better than with X11.

That's going to continue improving, and it'll improve faster with broader support. We've somehow ended up with the bizarre politicisation of Wayland as being some sort of woke thing while X11 represents the Roman Empire or some such bullshit, but the reality is that there is no story for improving accessibility support under X11 and sticking to X11 is going to end up reducing the accessibility of a platform.

When you read anything about Linux accessibility, ask yourself whether you're reading something written by either a user of the accessibility features, or a developer of them. If they're neither, ask yourself why they actually care and what they're doing to make the future better.

squirmelia

A butterfly landed on a feather. A little egret flew away. The crows cawed loudly. And me? I was asked if I'd lost something.

I hadn't, of course, I was looking for sherds. Today's finds:

Last time I looked there, I found my first piece of pipe! I also found a sherd with "Maddock" on it, and I found out that John Maddock was a Stoke-on-Trent potter who started in 1830, and John Maddock & Sons continued until 1980.

Some more sherds, mostly blue and white:

squirmelia

I had read that it was possible to get onto the foreshore at Fishmonger’s Hall Wharf but when I got there, I found a ladder which I was reluctant to climb.

I peered over and could see people on the foreshore.

I walked along the river further, wondering if there was another way down, until I found steps outside the Banker pub. Cousin Lane Stairs according to Google Maps. They were decent steps and I headed down to the foreshore. To get to a further bit involved going underneath Cannon Street railway bridge and climbing over a few boulders and I used a soggy algae covered wall for balance. Next time I might take my hiking pole.

It was only about 20 minutes since low tide, but I felt unsure about how long it would remain accessible for. It didn't matter though that day as I didn't have time to linger.

I only picked up two sherds:

squirmelia

I was going to visit the Thames Barrier and wanted to go mudlarking on the way, but didn't quite manage to.

I started at Woolwich - the first set of stairs I looked down were too muddy and the foreshore was similar. The second set, I walked down but they got muddier and I started slipping so turned back. A man saw me doing this and told me there were steps further on that would be better. We walked together to the steps but then found them padlocked.

The steps nearest to the Thames Barrier, outside the Hope & Anchor pub (now closed) seemed to be missing steps and also looked very slippery, so I gave them a miss too.

So mudlarking 19 did not happen that day, and instead the day after.

I headed to Rotherhithe and it was blissfully quiet, I was the only person on the foreshore.

I found a few pieces of shoe soles and picked one up, wondering if anyone had worn it or if it was just surplus.

I found some pottery sherds and a few pieces of glass, and a few bits of pipe.

I headed back up the steps.

“Are you okay?” a man asked after I'd taken my gloves off and wiped my nose.
“Yeah”, I said, nodding.
“Are you a tourist or you live around here?” he asked.
“Neither,” I replied, and he walked off before I could elaborate, seeming annoyed. Then he started cheering random joggers who were running past, who looked at him confused.

I headed to Limehouse after that and there were Canada Geese and goslings, and swans.

I found my first face! I am not sure who he is, although he looks familiar somehow. It may have been part of a Bellarmine jug.

I found quite a lot of sherds with words on:

“Oat” - A part of what looks like a small white pot that says “oat” on the bottom. It seems there was once a face cream called Oatine, so this little pot likely held that. It looks like Oatine was sold in the UK from 1905 to 1960s, but was most popular around the 1920s. Article I found on Oatine: Oatine: The food for the complexion.

“unt” - a small sherd with what looks like “unt” visible. The letter before could have been a “o” so perhaps it spelt county or mount?

“ho” - a sherd where most of the glaze has come off and all that is left looks like it spells “ho”.

Also glass shards with words on:

“ark” - this shard was obviously from Noah’s Ark.

“c.” - a nice letter c and a full stop, but whether the rest of the word was Isaac or maniac or automatic, I don't know.

“by” - possibly, or it could be “ry”, but I think it looks more like “by”.

One where they are obviously letters but what remains of them is too difficult for me to tell.

I found a terracotta coloured stone that looks like it has a little pink heart on it.

I found a button and a blue circle of glass with two holes, which could have been a button also but it could have been on a necklace, perhaps?

Limehouse finds are colourful!

mjg59

I'm lucky enough to have a weird niche ISP available to me, so I'm paying $35 a month for around 600MBit symmetric data. Unfortunately they don't offer static IP addresses to residential customers, and nor do they allow multiple IP addresses per connection, and I'm the sort of person who'd like to run a bunch of stuff myself, so I've been looking for ways to manage this.

What I've ended up doing is renting a cheap VPS from a vendor that lets me add multiple IP addresses for minimal extra cost. The precise nature of the VPS isn't relevant - you just want a machine (it doesn't need much CPU, RAM, or storage) that has multiple world routeable IPv4 addresses associated with it and has no port blocks on incoming traffic. Ideally it's geographically local and peers with your ISP in order to reduce additional latency, but that's a nice to have rather than a requirement.

By setting that up you now have multiple real-world IP addresses that people can get to. How do we get them to the machine in your house you want to be accessible? First we need a connection between that machine and your VPS, and the easiest approach here is Wireguard. We only need a point-to-point link, nothing routable, and none of the IP addresses involved need to have anything to do with any of the rest of your network. So, on your local machine you want something like:[Interface] PrivateKey = privkeyhere ListenPort = 51820 Address = localaddr/32 [Peer] Endpoint = VPS:51820 PublicKey = pubkeyhere AllowedIPs = VPS/0

And on your VPS, something like:[Interface] Address = vpswgaddr/32 SaveConfig = true ListenPort = 51820 PrivateKey = privkeyhere [Peer] PublicKey = pubkeyhere AllowedIPs = localaddr/32

The addresses here are (other than the VPS address) arbitrary - but they do need to be consistent, otherwise Wireguard is going to be unhappy and your packets will not have a fun time. Bring that interface up with wg-quick and make sure the devices can ping each other. Hurrah! That's the easy bit.

Now you want packets from the outside world to get to your internal machine. Let's say the external IP address you're going to use for that machine is 321.985.520.309 and the wireguard address of your local system is 867.420.696.005. On the VPS, you're going to want to do:

iptables -t nat -A PREROUTING -p tcp -d 321.985.520.309 -j DNAT --to-destination 867.420.696.005

Now, all incoming packets for 321.985.520.309 will be rewritten to head towards 867.420.696.005 instead (make sure you've set net.ipv4.ip_forward to 1 via sysctl!). Victory! Or is it? Well, no.

What we're doing here is rewriting the destination address of the packets so instead of heading to an address associated with the VPS, they're now going to head to your internal system over the Wireguard link. Which is then going to ignore them, because the AllowedIPs statement in the config only allows packets coming from your VPS, and these packets still have their original source IP. We could rewrite the source IP to match the VPS IP, but then you'd have no idea where any of these packets were coming from, and that sucks. Let's do something better. On the local machine, in the peer, let's update AllowedIps to 0.0.0.0/0 to permit packets form any source to appear over our Wireguard link. But if we bring the interface up now, it'll try to route all traffic over the Wireguard link, which isn't what we want. So we'll add table = off to the interface stanza of the config to disable that, and now we can bring the interface up without breaking everything but still allowing packets to reach us. However, we do still need to tell the kernel how to reach the remote VPN endpoint, which we can do with ip route add vpswgaddr dev wg0. Add this to the interface stanza as:PostUp = ip route add vpswgaddr dev wg0 PreDown = ip route del vpswgaddr dev wg0

That's half the battle. The problem is that they're going to show up there with the source address still set to the original source IP, and your internal system is (because Linux) going to notice it has the ability to just send replies to the outside world via your ISP rather than via Wireguard and nothing is going to work. Thanks, Linux. Thinux.

But there's a way to solve this - policy routing. Linux allows you to have multiple separate routing tables, and define policy that controls which routing table will be used for a given packet. First, let's define a new table reference. On the local machine, edit /etc/iproute2/rt_tables and add a new entry that's something like:1 wireguard

where "1" is just a standin for a number not otherwise used there. Now edit your wireguard config and replace table=off with table=wireguard - Wireguard will now update the wireguard routing table rather than the global one. Now all we need to do is to tell the kernel to push packets into the appropriate routing table - we can do that with ip rule add from localaddr lookup wireguard, which tells the kernel to take any packet coming from our Wireguard address and push it via the Wireguard routing table. Add that to your Wireguard interface config as:PostUp = ip rule add from localaddr lookup wireguard PreDown = ip rule del from localaddr lookup wireguard
and now your local system is effectively on the internet.

You can do this for multiple systems - just configure additional Wireguard interfaces on the VPS and make sure they're all listening on different ports. If your local IP changes then your local machines will end up reconnecting to the VPS, but to the outside world their accessible IP address will remain the same. It's like having a real IP without the pain of convincing your ISP to give it to you.

rmc28

On an ice hockey camp in Slaný, near Prague. I flew out on Thursday afternoon with two friends from Kodiaks. We arrived at the rink hotel in time to check in, have a little walk down to the nearby supermarket and get food, and settle in for the night. For reasons the three of us were all sharing a dormitory room the first night, and we decided the perfect film to watch over our picnic dinner was Inside Out 2 - also set at a 3-day hockey camp. I hadn't seen it before, though the other two had, and I enjoyed it very much.

Friday morning was pretty relaxed; a fourth Kodiak joined us after leaving home at awful-o-clock in the morning, and we were moved into the nicer ensuite twin rooms in pairs for the rest of the camp. We met in the dressing room at 1pm, were on ice at 2pm and again at 6pm, with a stickhandling session in between. Then dinner at 8 and falling into bed not long after.

It's excellent coaching, I'm being pushed well out of my comfort zone and the balance of drill and rest in each session and between sessions is just right. I hit my "cannot actually skate any more" limit about 3 minutes before the end of the last ice session.

Today will be two ice sessions at either end of the day, with video review (argh), optional swim+spa (yes!), and stickhandling again in between. My muscles this morning are making themselves known but I'm not exhausted. All is good. Time to go get changed.

squirmelia

A busy day of immersive theatre and when I left it was pouring with rain, but when I walked through Blackfriars Station to the other side of the river, it magically stopped raining and I headed down to the foreshore!

It was quiet, as people had been put off by the rain.

Earlier in the day, in an Ambient Lit workshop, I had pretended to be a dog and chased pigeons. “Woof”, I said to the pigeons on the foreshore.

There were patches of metal objects, nails, screws, objects once used.

I picked up pipes, pottery sherds and pieces of glass, and also a tiny heart shaped sticker. Thanks for the love, dear Thames.

Profile

Stuart Brady

My Website

April 2016

S	M	T	W	T	F	S
					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

Page Summary

Style Credit

Style: Neutral Good for Practicality by timeasmymeasure

Expand Cut Tags

No cut tags

Page generated Jun. 25th, 2025 12:32 am

Stuart Brady

Reading

Mudlarking - 22 - Kylie & spear fishing

Why is there no consistent single signon API flow?

Events of note this week (mostly hockey)

I am a dog

(no subject)

A week ago I was in Prague

Mudlarking 21 - Billy Hicks and a teapot

Queenhithe

My a11y journey

Park sherds - lost

Mudlarking - 20

Mudlarking 19 - Oatine and a face

Locally hosting an internet-connected server

In (near) Prague

Mudlarking 17

Profile

April 2016

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags