Proxy image urls get mangled

a month ago by NightFantom to c/boostforlemmy

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

probable_possum 2 points a month ago

Have seen this, too. Once. With boost. No developer in here, don't expect a solution.

save

path: 0 25674345, hotness: undefined, score: 2, children: 3

spicehoarder 2 points a month ago

Oh shit, did the dev peace out?

save

path: 0 25674345 25685935, hotness: undefined, score: 2, children: 2

frongt -1 points a month ago

Maintaining the app is not a priority for him. He pushed an update recently that broke a bunch of features.

save

path: 0 25674345 25685935 25691109, hotness: undefined, score: -1, children: 1

spicehoarder 3 points a month ago

What a shame. This is my favorite app. I wish he'd open source it.

save

path: 0 25674345 25685935 25691109 25692884, hotness: undefined, score: 3, children: 0

BigDanishGuy 2 points a month ago

Where's the images hosted on slrpnk.net or the site in the mangles URLs (which I can't see now, while typing this)?

Because if you didn't mean to link to images on slrpnk.net, then I have a hard time believing it's not something misconfigured on slrpnk.net.

Otherwise why should you get that specific string added? Sure, if it had just been the site part, maybe it could be boost, but I'd still doubt it. But the extra path? That's some kind of proxy module the admin has installed and forgot about.

How does other posts, by other users on your in instance, with image links look?

save

path: 0 25744987, hotness: undefined, score: 2, children: 1

NightFantom 1 point a month ago

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

save

path: 0 25744987 25746559, hotness: undefined, score: 1, children: 0

NightFantom 1 point a month ago

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?

save

path: 0 25764676, hotness: undefined, score: 1, children: 0