[apenwarr]

You might mean if you turn "on" HTTPS-only mode?

The silly trick blip uses involves pinging non-encrypted HTTP web servers, which is not allowed from an encrypted web page. So you really have to load blip from a non-encrypted server.

This code is from 10 years ago. Most likely we could find some way to work with HTTPS nowadays, but alas, I don't have time to maintain it.

[fmajid]

It might be from 10 years ago, but it's still incredibly useful.

I recently upgraded to a Mac Studio with 10GBase-T and was experiencing regular SSH disconnections. Blip allowed me to isolate this to some sort of sporadic incompatibility with the 10GBase-T SFP+ modules I used in my Ubiquiti switch (despite having tried two brands of SFP+). Switching to a switch with native 10GBase-T ports (Zyxel XGS1250-12, only £225) fixed this.

The multiple ring buffer timescales is genius!

[drewtato]

The page still loads in HTTPS, but turning off HTTPS-only mode means that the HTTP requests succeed, at least more than before. So I guess there's nothing wrong there.

The blue ticks actually don't work, though. They're always accompanied by red and seem to be timing out instead of the usual exceptions.