Is this a boost bug perhaps? What injects this proxy part? slrpnk.net admin said they think it's a client bug so here I am
Note the hhttps (double h) and the missing h further after the proxy ttps
Interestingly I just saw it happen in another post: https://lemdro.id/post/lemdro.id/45613195 the bottommost image link has the double hhttps, which is silly because the other images are fine, but this probably proves it's not my client as I could reproduce in an incognito browser. It does seem to be quokk.au links in both cases? But why would proxies choke on that specifically?