Videos are much more efficient than apngs or gifs, though, and it's just as easy to allow downloads (unless they're using variable bitrates which are a bit pointless for short animations anyway)
It's just as easy to allow downloads, but it seems a lot more common for sites to go out of their way to disallow video downloads than gif downloads. Also a bunch of them use video tags that don't point to an actual video file but get fed video content out of band.
I'm "guilty" of this on my video site https://pushups.ndn.today (does not work on iOS).
So far one person figured out how to download those videos, after spending 4 hours studying my source code.
> I would have expected them to have fixed the obvious issue with their UI by now.
Are we talking about the same Reddit that still runs three different versions of their website because the newest version is so bad that people refuse to use it? I'm not holding my breath.
That's just using the blob API likely. Nothing stopping you src'ing an <img> tag with one of those.
If the page you're on can survive a reload, you can often find the interesting mp4/m3u8 request in the devtools network tab. You probably knew this already.
I've kind of expected that you have to open the DOM inspector to find image links these days. Not sure what they think they're protecting, but the protection doesn't work.
(Reminds me of sites that disable pasting in passwords from your password manager, so you have to have xdotool type them for you. Again, not sure what they think they're saving me from. And I'm not sure why browsers have APIs that allow this sort of thing.)
Yes this was one of the reasons I built gif.com.ai - GIFs are a special format and my intention for the app was to retain a gif as just that. When you generate a gif you get an Imgur copy and it sometimes formats the gifs to videos but that’s not a problem because you can get the original gif format back by adding “i” in the url prefix and adding “.gif” to the end of the url.
Images and videos can both be downloaded by right click. Also, both of them can be configured not to work that way by html/css structure. It's not a difference between image vs video.
But then you might be able to re-share "their" content without subjecting your friends to that website's ads and that website's tracking (but I repeat myself)
It's not a file format problem, it's a user experience problem. I can't save a Twitter "GIF" and share it without resorting to external tools like youtube-dl.
It's not a file format problem, it's a developer/company problem... They didn't implement it correctly. I can download videos on many sites by right clicking on them. They could "block" right-clicking on GIFs too if they wanted to.