Skip to main content

Alpha This is a new website theme. Help me improve it and give your feedback (opens in a new tab).

Web

Netlify Mixed Content Warnings

Looking at my blog today, I noticed that Netlify now warns you if you link to non-HTTPS URLs in your site:

2:37:56 PM: Starting post processing
2:37:56 PM: Mixed content detected in: /blog/index.html
2:37:56 PM: --> insecure link urls:
2:37:56 PM:   - http://w6d6vblb6vhuqxt6.onion/blog/
2:37:56 PM:   - http://tvin5bvfwew3ldttg5t6ynlif4t53y3mbmb7sgbyud7h5q6gblrpsnyd.onion/blog/
2:37:56 PM:   - http://creativecommons.org/licenses/by-nd/4.0/

This is really handy in catching those URLs you’ve forgotten to make into HTTPS URLs, but Tor Project exempts .onion hostnames from mixed content warnings (see Tor ticket #23439) and this is even applied upstream by Mozilla in Firefox (see Mozilla ticket #1382359).

Mastodon

I joined Mastodon today. So did metrics-bot who is now simultooting to the fediverse.

metrics-bot on Mastodon

metrics-bot on Mastodon

Annoyingly, the API for Mastodon is different enough from the API for Twitter that I’ve needed to use a new library in metrics-bot. I’m using the mastodon4j library for now, but I’m really using so little of the API I do wonder if it would be easier to just reimplement the parts that are needed and drop the rest. The only part I’m really worried about is the OAuth authentication and I’m sure that won’t be anywhere near as bad as I think it will be.

Bugs in websites

Reporting a bug in free software is easy. It turns out that everything I thought I knew about bug reporting was turned on its head when I tried to report a bug in the Tesco groceries website.

I was finding some sort of JavaScript problems in that my CPU was held at 100% and the page wasn’t really usable.

As with bug reports, I was expecting to at least have some technical information logged along with my email address so someone can contact me if they want me to try some things out. What I actually got:

Contact