How far back in time can you understand English?

This is a repost promoting content originally published elsewhere. See more things Dan's reposted.

A man takes a train from London to the coast. He’s visiting a town called Wulfleet. It’s small and old, the kind of place with a pub that’s been pouring pints since the Battle of Bosworth Field. He’s going to write about it for his blog. He’s excited.

He arrives, he checks in. He walks to the cute B&B he’d picked out online. And he writes it all up like any good travel blogger would: in that breezy LiveJournal style from 25 years ago, perhaps, in his case, trying a little too hard.

But as his post goes on, his language gets older. A hundred years older with each jump. The spelling changes. The grammar changes. Words you know are replaced by unfamiliar words, and his attitude gets older too, as the blogger’s voice is replaced by that of a Georgian diarist, an Elizabethan pamphleteer, a medieval chronicler.

By the middle of his post, he’s writing in what might as well be a foreign language.

But it’s not a foreign language. It’s all English.

None of the story is real: not the blogger, not the town. But the language is real, or at least realistic. I constructed the passages myself, working from what we know about how English was written in each period.

It’s possible you caught this excellent blog post last month, but if you didn’t, you’re in for a treat. A long rambling “travel blog” story, except that every three or four paragraphs the author’s transported back a hundred years in time, which adapts not only the story but – more-importantly – the language the author uses.

For the last couple of hundred years the English language has been moderately stable and well-defined, although the stylistic mannerisms of authors have changed. But as you read beyond that, the language feels like it’s slowly mutating into something that, by the time you get to a thousand years ago, is nearly indecipherable!

Don’t just read the demonstration until you find you can’t understand it any more, though! After all of that, keep scrolling, and you’ll find that Colin Gorrie’s put together an explanation of what you just read. It describes the linguistic shifts you’ve now just experienced first-hand, the reasons for them, and how they were reconstructed in order to make this amusing distraction.

The footnotes are great too.

Also; it’s well worth watching/listening to the video that inspired it, in which you can hear (twice, the second time with explanatory slides) a linguist read a monologue that starts in the English of around 1,500 years ago and progress, jumping every few sentences, through to modern English. Absolutely fascinating.

With thanks to Ash for sharing.

Note #28497

A lot of things are hard right now. But I appreciate that Spring has come and I can enjoy a cheese & pickle sandwich and a fake beer for lunch in the sun. All to the sounds of the birds singing… and, somewhere behind me, the dog excitedly demolishing a pile of pine cones.

Dan, a white man with a goatee beard and long hair, sits at a wooden picnic bench in front of a sandwich, crisp packet, and can of Lucky Saint.

It could be worse, right?

×

Cold Giraffe

My mum painted a cold giraffe onto a postcard and sent it to me. It’s been added to my collection.

Watercolour painting of a giraffe wearing glasses and a wooly jumper, amidst a snowy sky.

She sent it to my “send me a postcard” PO box (even though she’s got my actual address), which I’m guessing was an indication that it was being “sent” to me “as if” she were a stranger on the Internet.

Or possibly it’s just because I’m, y’know, living in a variety of different places with only intermittent trips back to my actual house, while my insurance company and their contractors do their work to dry out our walls and floors, assess the damage caused after my house flooded, 24 days ago.

Whatever the reason, it was an uplifting piece of mail to receive.

In other things-are-improving news, our insurance company (finally! – after lots of checks and paperwork at their end) accepted liability for paying for the repairs we’ll need and for our temporary accommodation (including the places we’ve already been living for the last few weeks).

×

Horse Gym

My current temporary home – and, necessarily, office – is directly next door to some kind of “horse gym”: a contraption a little like a huge revolving door to encourage one or more horses to exercise by walking around it:

Every now and then my peripheral vision registers that there’s a horse outside the window and, for the dozenth time, I look up from my work and glance around to barely catch it vanishing off on yet another lap.

Dan Q found GC4MJRJ R’n’R #3 – Not Quite A Well?

This checkin to GC4MJRJ R’n’R #3 – Not Quite A Well? reflects a geocaching.com log entry. See more of Dan's cache logs.

Another quick find for the sharp-eyed geokid, once we found the right host. Three for three and that’s time for us to turn about and go have our brunch. TFTC!

Dan and a boy each throw a thumbs-up to the camera from a forest footpath.
Mission accomplished. Time for bacon! (Wait… where’s the dog gone?)
×

Dan Q found GC4MJRT R’n’R #4 – Changing Colours

This checkin to GC4MJRT R’n’R #4 – Changing Colours reflects a geocaching.com log entry. See more of Dan's cache logs.

The woods made it hard to get a good fix, but eventually we were in the vicinity of this excellent cache. It took a few different tree hosts before eventually we were looking in the right place. The younger geokid insists that I log that he caught sight of it before me!

A boy reaches into an ivy-covered tree.
Reaching for the cache.
×

Dan Q found GC4MJX6 R’n’R #6 – what YOU looking at?

This checkin to GC4MJX6 R’n’R #6 – what YOU looking at? reflects a geocaching.com log entry. See more of Dan's cache logs.

Came out for a dog walk from New Yatt this morning. The GZ is deep within thick brambles, but the younger geokid was up to the challenge and soon the unusual cache container was in hand. TFTC!

A boy looks over his shoulder as be begins to walk into a bramble bush.
“I have to go in there‽”
×

I Am Experimenting with Blocking HTTP1.1

This is a repost promoting content originally published elsewhere. See more things Dan's reposted.

Most of the traffic I get on this site is bots – it isn’t even close. And, for whatever reason, almost all of the bots are using HTTP1.1 while virtually all human traffic is using later protocols.

I have decided to block v1.1 traffic on an experimental basis. This is a heavy-handed measure and I will probably modify my approach as I see the results.

# Return an error for clients using http1.1 or below - these are assumed to be bots
@http-too-old {
    not protocol http/2+
    not path /rss.xml /atom.xml # allow feeds
}
respond @http-too-old 400 {
    body "Due to stupid bots I have disabled http1.1. Use more modern software to access this site"
    close
}

This is quick, dirty, and will certainly need tweaking but I think it is a good enough start to see what effects it will have on my traffic.

A really interesting experiment by Andrew Stephens! And love that he shared the relevant parts of his Caddyfile: nice to see how elegantly this can be achieved.

I decided to probe his server with cURL:

~ curl --http0.9 -sI https://sheep.horse/ | head -n1
HTTP/2 200
~ curl --http1.0 -sI https://sheep.horse/ | head -n1
HTTP/1.0 400 Bad Request
~ curl --http1.1 -sI https://sheep.horse/ | head -n1
HTTP/1.1 400 Bad Request
~ curl --http2 -sI https://sheep.horse/ | head -n1
HTTP/2 200

Curiously, while his configuration blocks both HTTP/1.1 and HTTP/1.0, it doesn’t seem to block HTTP/0.9! Whaaa?

It took me a while to work out why this was. It turns out that cURL won’t do HTTP/0.9 over https:// connections. Interesting! Though it presumably wouldn’t have worked anyway – HTTP/1.1 requires (and HTTP/1.0 permits) the Host: header, but HTTP/0.9 doesn’t IIRC, and sheep.horse definitely does require the Host: header (I tested!).

I also tested that my RSS reader FreshRSS was still able to fetch his content. I have it configured to pull not only the RSS feed, which is specifically allowed to bypass his restriction, but – because his feed contains only summary content – I also have it fetch the linked page too in order to get the full content. It looks like FreshRSS is using HTTP/2 or higher, because the content fetcher still behaves properly.

Andrew’s approach definitely excludes Lynx, which is a bit annoying and would make this idea a non-starter for any of my own websites. But it’s still an interesting experiment.

Dan Q found GCAABPG North Leigh Loop #7

This checkin to GCAABPG North Leigh Loop #7 reflects a geocaching.com log entry. See more of Dan's cache logs.

Completing our loop (minus a couple of DNFs, but plus a couple of nearby caches), this damp geopup and I were really happy to finish with this good-sized cache!

Dan crouches by his French Bulldog on a rural footpath.

TFTC, and for the series, if which this was our favourite and so earns the FP.

Now we’d better go get cleaned and dry!

×

Dan Q found GCAABNW North Leigh Loop #6

This checkin to GCAABNW North Leigh Loop #6 reflects a geocaching.com log entry. See more of Dan's cache logs.

Tougher than we expected to find – not only is this a stealthy container but it’s hidden unusually-thoroughly too! TFTC

I’m increasingly regretting my choice this morning to wear comfortable but not waterproof shoes rather than my not-fully-broken-in walking boots. Between the muddy puddles and the long wet grass, my feet are soaked!

Dan Q found GC1QY29 Can Rabbits Climb Trees??

This checkin to GC1QY29 Can Rabbits Climb Trees?? reflects a geocaching.com log entry. See more of Dan's cache logs.

Coming up from Evergreen/Loop #4 the geohound and I made a poor guess about which side the the hedgerow we ought to be on, and – to avoid having to backtrack – opted to cut through red thicket just East of this cache. The little pupper got stuck and had to be carried, which was when I discovered that her belly was completely caked in thick mud. Eww!

We got here in the end and were delighted to find such a nice cache. TNLN, SL, and took advantage of the concealment provided by a nearby tree to relieve our bladders before continuing North. (Well I appreciated the concealment; the doggo is happy to widdle anywhere!)

Dan Q found GC1QYPN Back to Evergreen

This checkin to GC1QYPN Back to Evergreen reflects a geocaching.com log entry. See more of Dan's cache logs.

The geopup and I are out doing the North Leigh Loop from New Yatt, where we’re temporarily living while our house is dried and damage assessed by the insurance company following a catastrophic flood a few weeks ago.

Between Loop #3 and #4 we took a small diversion to find this cache, and I’m glad that we did! So nice to see a properly-sized (and tenured) cache still rocking it!

Lid was not properly attached by a recent finder, sadly, and the container spilled its contents as I picked it up. But once we’d reassembled it all we were able to sign the log and continue our loop.

TFTC to both the hiders and adopters. FP awarded for being the first decent-sized cache I’ve seen today.

Dan Q did not find GCAABMN North Leigh Loop #3

This checkin to GCAABMN North Leigh Loop #3 reflects a geocaching.com log entry. See more of Dan's cache logs.

While the geohound busied herself with the important task of collecting sticks several times larger than herself, I began the search for what I’d figured would be a QEF.

A French Bulldog pulls at the end of a very large stick, in a woodland.

Within the circle of uncertainty lay an obvious-looking host covered with obvious-looking candidate spots into which to squeeze a cache of this kind. After 15 minutes of searching where it “should” have been I wondered, per previous logs, if it might free fallen, and made a brief search of the mulch and leaf litter underfoot. No luck there either! After a total of nearly 20 minutes of searching, we had to give up.

×