Live data from Hacker News

Twitter's GIF hack

blog.embed.ly

71–80 of 160 posts

Re: Twitter's GIF hack

#71
post #67

Earlier quoted context omitted.

In a way they're doing it better. Twitter only seems to support MP4 whereas gfycat et al will deliver WEBM or MP4 based on the user's browser.

Agreed. MP4 doesn't work on Firefox (out of the box).

You should probably qualify that somehow, because MP4 works for me on Firefox (on OSX 10.9).

Re: Twitter's GIF hack

#73
post #65
post #53

Earlier quoted context omitted.

Just a nitpick, JPEG always encodes the color channels at half resolution. It's amazing how difficult it is to notice this, though.

No, there are 4:4:4 and 4:2:2 modes in JPEG. H.264 also defines such modes, but no consumer hardware decoders support them so they aren't commonly used.

My mistake, I must have been going off what's common versus what's allowed. Thanks for pointing it out.

Re: Twitter's GIF hack

#74
post #72

This article makes it sound like Twitter invented a whole new optimization, when they really just recycled a concept already in use by gfycat ( http://www.gfycat.com/ ) and MediaCrush ( https://mediacru.sh/ ).

The latter being open source (I made it): https://github.com/MediaCrush/MediaCrush

Re: Twitter's GIF hack

#75
post #17
post #10

This is on a fully-patched RHEL6 workstation: http://i.imgur.com/NleqJTD.png Another example of "use bleeding-edge tech or go fuck yourself" from the modern web.

I suspect some implementation issues rather than a GFY attitude, it doesn't work on FF or Chrome on OSX 10.9. Safari works though.

I recall reading on gfycat's subreddit that desktop Chrome's H264 support is occasionally spotty, so they chose to force on VP8/WebM in Chrome.

The upside is that users get a reliable experience. the downside is that laptop Chrome users get a reliably lower battery life, as VP8 isn't typically hardware accelerated.

Re: Twitter's GIF hack

#76
post #71
post #67

Earlier quoted context omitted.

Agreed. MP4 doesn't work on Firefox (out of the box).

You should probably qualify that somehow, because MP4 works for me on Firefox (on OSX 10.9).

It does not work for me, too. FF30, OSX 10.9.3.

https://www.evernote.com/shard/s19/sh/e81e070a-4e2e-4367-9eb...

Re: Twitter's GIF hack

#78
post #67

Earlier quoted context omitted.

In a way they're doing it better. Twitter only seems to support MP4 whereas gfycat et al will deliver WEBM or MP4 based on the user's browser.

Agreed. MP4 doesn't work on Firefox (out of the box).

MP4 works out of the box on my Firefox (latest stable).

Re: Twitter's GIF hack

#79

Earlier quoted context omitted.

Support for mp4 isn't bleeding-edge tech on other operating systems / distributions, unfortunately. It's a couple of years old in terms of being supported by Chrome; it's supported in Firefox as of last August. At this point, desktop configurations that can't play mp4s are at risk of being considered "broken."

Is it really that difficult to supply a free format like WebM in addition to patent-encumbered H.264? If you only supply H.264, you're cutting out Firefox on OS X, Chromium, and Opera.

It does mean you need to transcode and store twice as many files, which can be a serious pain if you've got a number of different bitrate H.264 assets. It can be a big pain if your software assumes there'll only be a single media file. Not insurmountable but painful for small operations (and for large operations, where there may be a back-catalogue to worry about)

I'm with you in spirit, but in practice I think we can all understand why people often just go for H.264

Re: Twitter's GIF hack

#80

Earlier quoted context omitted.

Support for mp4 isn't bleeding-edge tech on other operating systems / distributions, unfortunately. It's a couple of years old in terms of being supported by Chrome; it's supported in Firefox as of last August. At this point, desktop configurations that can't play mp4s are at risk of being considered "broken."

Is it really that difficult to supply a free format like WebM in addition to patent-encumbered H.264? If you only supply H.264, you're cutting out Firefox on OS X, Chromium, and Opera.

Interestingly, the gif->mp4 in the source link uses Constrained Baseline H264, the only profile that's supported by Cisco's BSD-licensed OpenH264[1]. The MPEG-LA patent fees are already covered, so that small projects can freely use the decoder/encoder.

[1] https://github.com/cisco/openh264

Post reply on HN