software should be developed in terms of the user, not the developer. Not every one knows every windows/linux command and debugging to fix problems.
Browsers and platform defaults could go a long way to improve video UX but they don't. Not having to open my network tab to save video would be a place to start. Being able to right-click to copy/paste them would be another.
These aren't "lowest common denominator" things. They're everyone things.
Uh... Right click, "Save video as..." in Chrome. Has been that way as long as I can recall. I'm 95% sure Firefox works the same way. No idea about IE or OG Edge because who really cares, presumably Edgium behaves like Chrome.
A lot of sites override the right click menu in one way or another, but that's not the browser's fault. A standard video embed is easy to save.
> Being able to right-click to copy/paste them would be another.
I think that might run in to some practical limitations, both in terms of simple clipboard data limits and the fact that while an image is loaded entirely in to RAM to play a video may not be. If the user does a right-click>copy five seconds in while the video is still loading but has already started playing, what should the browser do? How should it handle extreme situations like someone clicking "Copy" on their Plex Web Player embed of a 100GB 4K UHD movie?
Copy/paste with video in a browser is not as straightforward as images.
You can’t yet. Thats the point. GIFs are not 100GB 4K movies, yet the current state of the art treats the two the same.
We need a standard method to distinguish an (optionally) looping, soundless “GIF” video from a traditional video, and mimic the behavior of an image in the case of a GIF.
Also GIF videos needs to behave like GIF images consistently across all modern browsers and mobile devices.
> Copy/paste with video in a browser is not as straightforward as images.
Copy is already broken and weird for images, since it doesn't get you the original file. But if you fixed that, I would expect pasting to give me a 'transferring...' window as long as the browser is still open and it can't be fed from cache. That wouldn't be particularly hard to implement. (And being unable to feed from cache wouldn't be unique to video at all. Image downloads already ignore the cache all the time.)
Yes, videos lose quality and sound when converted to a gif. They also lose proprietary encoding and all their metadata (including licensing information).
This makes gif's infinitely more transmittable on the web.
If I were to guess, I think the internet has somewhat helped make this worse, because it separates some of the human connection from your everyday interactions. If you can't read someone's emotions on their face, and you're just reading their words on a support ticket, it's very easy to dismiss them as dumb or foolish when in fact it's you who does not understand the problem from their perspective.
I guess part of the problem might be that what's obvious to someone who's already encountered that problem may be non-obvious to someone who's entirely new to a particular domain (or product or whatever).
Until that happens though, I just don't see .gifs ever losing traction. I still need to upload gifs to slack if I want autoplaying/looping behavior without user interaction, I still need to embed .gifs in my confluence pages, and when documenting user interactions in github readmes gifs are still king.
FWIW I've made a small user script for encoding gifs in a two pass approach (as most gif encoders I've seen do a pretty shit job). If anyone wants it here's the script: http://files.jjcm.org/gif.sh
(to use, just type `./gif.sh -s=SIZE -f=FPS input.mp4 output.gif`)
It's not just Apple, webp files can't even be opened by Photoshop. You're basically making proprietary Chrome image files if you actually use that format.
Shaking my head as to why this format has any support at all.
Until webp works everywhere then the web shouldn't be polluted with this proprietary Google Chrome image format.
What does that mean?
I often trip on that, was similarity with AVI accidental or intentional..?
Google claims this doesn't apply to videos with muted, but at least in my Chrome, it does.
Muted-by-default makes complete sense to me. I hate it when a web site makes noise. But no autoplay (even muted) is broken.
So is having Google act as the arbiter of which web sites get to autoplay (Google's Youtube) and which ones don't (my personal domain). That's a huge conflict-of-interest and hugely anti-competitive behavior right there. It crushes the little guy.
Disclaimer: Google claims this is based on some kind of objective metrics.
But the metric is bad.
They are definitely tradeoffs. At least for my personal website, the size disadvantage of GIFs still outweighs them, in my opinion. I think bandwidth usage and battery drainage are also worth thinking about on behalf of the user.
For bandwidth, I'm going to blame my ISP, Chrome, firefox, etc.
For the media (gif versus movie), I'm going to blame the website.
I mean, I know everybody is really pumped about webGL and shadow DOMs and webcomponents and webASM, but I feel like the basic "html as document language" could use some loving to solve this.
This whole mess reminds me of SVG. I get that there are fantastic reasons why SVG has JavaScript and its own DOM and can pull in external resources, but sometimes we don't want a whole new framework for new forms of content, we just want an IMG.
Gifs have just enough capability to be really useful and very hard to replace.
I personally hate videos just served up. Not always, just most of the time doing that causes more grief than it adds value.
it does for me with VLC (it is dependent on your player if you save it to your computer)
But yeah, I can't right click on a video to save it. Got to use youtube-dl for that...
> THE EXACT SAME BEHAVIOUR, EVERYWHERE.
no sound?
No sound by default depending on user settings would actually be progress in my opinion. But considering half the online video players break in some way as soon as I disable autoplay in the browser I don't think this will be achievable before the end of the century.
Meanwhile, there have been numerous patent suits against google from other big companies around VP8, VP9, and webm. Google isn’t the bad guy in this story.
The video per se won't loop if I save it in my computer or phone. I can't drag and drop, right click, long tap.
To have anything replacing gif you need THE EXACT SAME BEHAVIOUR, EVERYWHERE.
It doesn't matter for the consumer whose fault it is: encoding, the app, how the file is created. The user uses it, they don't care how it works. They will use whatever have the same behaviour.