How Discord Resizes 150M Images Every Day with Go and C++

Re:How Discord Resizes 150M Images Every Day with Go and C++ by Lutin on Tuesday November 14, 2017 @01:21PM (#15697679)

This is for proxying images that users link in chat, not for when users upload images to the service. It doesn't make sense to talk about doing this resize on the client, as the client doesn't have the image.

[ Parent | on HN ]

Re:How Discord Resizes 150M Images Every Day with Go and C++ by TrinaryWorksToo on Tuesday November 14, 2017 @01:50PM (#15697963)

That is a great point. It could still be feasible to cache the image on the client, and have it do the resize. Although I probably wouldn't accept it as a client, especially if my internet cuts out halfway through.

[ Parent | on HN ]

Re:How Discord Resizes 150M Images Every Day with Go and C++ by Xeoncross on Tuesday November 14, 2017 @01:56PM (#15698029)

Yes, the use-case of proxying images is a different mater. I was talking about client uploads since so many companies seem determined to waste my bandwidth and time uploading without resizing first.

[ Parent | on HN ]

Re:How Discord Resizes 150M Images Every Day with Go and C++ by drdaeman on Tuesday November 14, 2017 @02:54PM (#15698541)

Client uploads with client-provided thumbnails could lead to some pranks.

You know, a thumbnail with a cute kitten but something completely different after you click on it ;)

[ Parent | on HN ]

Re:How Discord Resizes 150M Images Every Day with Go and C++ by Xeoncross on Tuesday November 14, 2017 @03:24PM (#15698768)

I think you misunderstood. The client is uploading a single data blob for each image, but the blob can be smaller if the client resizes it first.

[ Parent | on HN ]