Crosspost detection failing due to image proxying

[Nutomic]

Viewed from here it works fine: https://lemmy.ml/post/40500530

But here its not showing the crosspost: https://lemmy.dbzer0.com/post/59857979

[dessalines]

I don't see a clean way around this. Since the cross-post detection uses exact urls (we put this in the post.url field, its not going to work for two instances that use image proxying.

I really don't want to re-work how cross-posts work, and we'd probably be better off reworking how we store the proxied urls. We probably shouldn't be storing them as post.url.

We already have local and remote image tables, so we should probably store the original as post.url, and store the proxied link in one of those tables.

I hate dealing with images so much, the internet needs an actually decentralized torrent-style image host 2 decades ago. Instead we have 50 servers hosting the exact same file and sharing none of the bandwidth.

[Nutomic]

I hate dealing with images so much, the internet needs an actually decentralized torrent-style image host 2 decades ago. Instead we have 50 servers hosting the exact same file and sharing none of the bandwidth.

IPFS might be a good solution for that. Iirc it uses p2p distribution like torrents, and files are referenced by hash, so the same file always has the same url. Maybe it could be integrated into Lemmy.

https://ipfs.tech/