We're probably headed for a world in which everything is rendered to an image server-side. The HTML/CSS/Javascript mess has become so bloated and attack-ridden that sending images needs less bandwidth and is simpler.
The new image solution is strictly more powerful than anything currently offered. Since they also control the initial rendering of the HTML, they can seamlessly opt to embed an image via a data url.
I built an image sharing utility connected to a friend's service, because I wanted to be able to directly share an image from anywhere on my phone without going on his website.
But once they're pasted in there, they can only be used there. It's barely harder to upload a file to any myriad of file sharing/hosting services and paste a link which most graphical IRC clients can be configured to auto-expand (and users who don't care/don't want a bunch of images can choose to handle links differently)
Offloading the image part to a cheaper service is a good idea - the rest is fairly lightweight, and once they're generated, the images are themselves are fixed/cacheable. Thanks!
Agreed, though that would require a lossless format (e.g. png) and would limit exchanges to sources that don't change the image (e.g.as email attachment) but not social networks that resize or otherwise reprocess the image
Not just images but specifically photographs for web distribution. if that's not as far away from intended PNG use cases as can be, it’s getting there.
There’s also a privacy aspect here. Upload to discord and the image URL can easily be copied around and shared outside of the server and the intended audience.
This is at least a crude way to stop that and I think it’s a good thing.
reply