Plot twist!

by @edent | # # # # # | Read ~963 times.
Doctor Who holding a glowing key

A mysterious woman, with a non-London accent and blonde hair, reached out her hand. She asked me a simple, yet terrifying, question - "Do you want to come on an adventure?" Sadly, Hadley Beeman does not have a TARDIS (Well, as far as any of us can tell...). What she does have is an interesting… Continue reading →

Limitations of HTML's title element

by @edent | # # # # | 7 comments | Read ~194 times.
The raw HTML displays in the tab.

How much do you know about the humble <title> tag? It has been there since the earliest HTML specification. The 1995 spec says: There may only be one title in any document. It should identify the content of the document in a fairly wide context. It may not contain anchors, paragraph marks, or highlighting. Remarkably… Continue reading →

Is HTTP 451 suitable for GDPR blocking?

by @edent | # # # | 8 comments | Read ~3,150 times.
451: Unavailable for legal reasons We recognise you are attempting to access this website from a country belonging to the European Economic Area (EEA) including the EU which enforces the General Data Protection Regulation (GDPR) and therefore cannot grant you access at this time. For any issues, e-mail us at techguy@journaltimes.com or call us at 888-460-8725.

Hello, it's me - the idiot who helped inspire the HTTP 451 status code. I graciously allowed Tim Bray to do the hard work of getting it through the IETF process, and now it is an official RFC. Recently, I've seen lots of people getting het up about its "misuse" - so I want to… Continue reading →

únicode is hard

by @edent | # # | 15 comments | Read ~29,000 times.

In the last couple of months, I've been seeing the ú symbol on British receipts. Why? 1963 - ASCII In the beginning* was ASCII. A standard way for computers to exchange text. ASCII was originally designed with 7 bits - that means 128 possible symbols. That ought to be enough for everyone, right? Wrong! ASCII… Continue reading →

Whatever happened to URI Schemes?

by @edent | # # | Read ~1,039 times.

A few days ago, I ranted about how chat apps have poor support for URI schemes. By "Chat Apps", I'm talking about the new wave of messengers - WhatsApp, WeChat, Telegram, Wire, and the like. What do I mean by "URI Scheme"? You're probably familiar with: https://example.com The "scheme" is https - it tells the… Continue reading →

What Time Is It?

by @edent | # # # | 2 comments | Read ~4,543 times.

For a bit of light reading, I've been going through some of the documents published by Sir John Chilcot's Iraq Inquiry. There are thousands of Telegrams, eGrams, Teleletters, and other miscellaneous communications. For those unfamiliar with the jargon, the inquiry have helpfully published a guide to reading the evidence. In it is this delightful titbit… Continue reading →

I'm in an RFC!

by @edent | # # # | 1 comment | Read ~570 times.

Friends, allow me to wallow in a little boasting! Four years ago, I made a modest proposal for a new HTTP Code to indicate censorship. A few days ago, RFC 7725: An HTTP Status Code to Report Legal Obstacles became an approved standard by the Internet Engineering Task Force. This allows a website, proxy, or… Continue reading →

Hashtag Standards

by @edent | # # # # # | 4 comments | Read ~4,349 times.

This is one of the longest and geekiest posts I've done. It's a work in progress. All comments and abuse welcome. #hashtag – As long has there has been a way to search Tweets* people have been adding information to make the easy to find. The #hashtag syntax has become the standard for attaching a… Continue reading →