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
I guess that's what I'm asking, is the proxy a default lemmy feature or my instance's specific implementation? Could it be a boost thing? There's so many options and I don't really understand enough about this to really reason about it