11–20 of 78 posts
GIF is a terrible format for video, but OTOH it's fairly lightweight for the browser for simple animation. Historically, playing video in the browser has required loading plugins, increasing the attack surface of the browser quite a bit, as well as inflating memory usage, increasing fragility, etc. HTML5 video is also blocked by my flash blocker. Up until the latest version of Firefox, animated gifs were blocked by m…
GIF is a terrible format for video, but OTOH it's fairly lightweight for the browser for simple animation. Historically, playing video in the browser has required loading plugins, increasing the attack surface of the browser quite a bit, as well as inflating memory usage, increasing fragility, etc. HTML5 video is also blocked by my flash blocker. Up until the latest version of Firefox, animated gifs were blocked by m…
Is OTOH really an acronym people are using now?
GIF is a terrible format for video, but OTOH it's fairly lightweight for the browser for simple animation. Historically, playing video in the browser has required loading plugins, increasing the attack surface of the browser quite a bit, as well as inflating memory usage, increasing fragility, etc. HTML5 video is also blocked by my flash blocker. Up until the latest version of Firefox, animated gifs were blocked by m…
Historically, this hasn't been the case. Certain browsers used to process the entire gif up to the current frame when rendering a new frame, causing long gif animations to slow down progressively.
> The problem is that html5 video doesn't work everywhere (we actually encode six different videos to cover the most browsers) Six different videos?? Anyone knows more about html5 video fragmentation and why six videos are required?
If I had to guess, they're probably encoding MP4/H.264, WebM/VP8, and Ogg/Theora.
Been using this on reddit for the past couple of weeks, and it works wonders. It's especially handy on mobile, where bandwidth can be scarce. But what has really struck me about the mobile experience is that using HTML5 video significantly improves the performance. This is important for GIFs/videos with a high resolution, which as GIFs would not render in real time on my phone (which has an S800, so I can only imagin…
GIF is a terrible format for video, but OTOH it's fairly lightweight for the browser for simple animation. Historically, playing video in the browser has required loading plugins, increasing the attack surface of the browser quite a bit, as well as inflating memory usage, increasing fragility, etc. HTML5 video is also blocked by my flash blocker. Up until the latest version of Firefox, animated gifs were blocked by m…
> but OTOH it's fairly lightweight for the browser for simple animation. Historically, this hasn't been the case. Certain browsers used to process the entire gif up to the current frame when rendering a new frame, causing long gif animations to slow down progressively.
Imgur should do something like this when people are viewing gifs at the Imgur site itself (as opposed to viewing a hotlinked gif file), automatically replacing the embedded GIF file with a video. I imagine they could save a lot in bandwidth costs
> The problem is that html5 video doesn't work everywhere (we actually encode six different videos to cover the most browsers) Six different videos?? Anyone knows more about html5 video fragmentation and why six videos are required?
They offer the ability to playback in reverse, so I imagine it's three different formats, doubled so that there's a reverse copy of each video. If I had to guess, they're probably encoding MP4/H.264, WebM/VP8, and Ogg/Theora.
> Note that there are 6 separate encodings -- mp4, webm, and reduced mp4, for forward and reverse