Live data from Hacker News

Introducing GIFV

imgur.com

171–180 of 205 posts

Re: Introducing GIFV

#171
post #100
post #13

Am I misunderstanding something here? I don't see anything other than an .mp4 video served via a tag from a URL that ends in .gifv. I was interested in seeing how it worked to look into supporting it for a mime type detection library I've written. The blog post mentions submitting a specification to the relevant standards organization. Are they planning on creating a new mp4 ftyp and registering a mimetype with IANA?

because lame marketing. the imgurl community is always asking for more servers and bandwidth, and the imgurl team is only delivering crappy feature on top of crappy feature that only makes things worse. their goal is not pleased users, its a big fat huge "exit". thats why new feature and buzzwords abound. it impresses investors, which is their goal.

> the imgurl community is always asking for more servers and bandwidth

They serve 2 billion images per day, and they never delete pictures that are still actively accessible from the internet. At no cost to the user.

In any case, cache is golden, and a 5 MB gifs off of their front page could be a 500kb MP4. That difference adds up superfast it's off of their front page and has 30M views.

Re: Introducing GIFV

#172
post #116

Earlier quoted context omitted.

We don't need to tie this behavior to a new video extension or a specific video format. A more sensible approach would be to allow video sources in and restrict their profile to GIF-like behavior. See https://bugzilla.mozilla.org/show_bug.cgi?id=895131

I think at some point, we do. People like this format. GIF, gyfcat, Vine, and now this. Instagram and WebM on 4chan also have things keyed to this behavior. But the thing that GIF has on all of them is that it works everywhere . It plays in a browser, in an email, on the desktop, in an MMS message, etc.. We need a full stop replacement for the GIF that uses a modern encoder.

> We need a full stop replacement for the GIF that uses a modern encoder.

Keeping in mind that one of the big advantages of GIF is NO AUDIO.

It's just deeply anti-social to play audio in some contexts, and a file format which enforces that is a very good thing.

Re: Introducing GIFV

#173
post #144
post #8

Can't we just all settle for .webm? The cancerous patented MP4/H264 combination must die.

Why on earth would you use WebM? WebP is actually an image format and is based on the VP8 codec.

Because WebP is aimed to replace PNG, WebM can replace both MP4 and animated GIF.

Re: Introducing GIFV

#174
No. Just no. These are muted videos, not GIFs.

GIFs have an 8-bit palette. They're lossless. They are meant to be short and sweet, because they take up a lot of bits.

They're also easy to manipulate, easy to encode/decode (I have a single .java file which generates animated GIFs) and unequivocally patent-free.

Let us stand up against this subversion of the pure GIF format. [success_kid.gif]

Re: Introducing GIFV

#175
post #74
post #10

Earlier quoted context omitted.

Unfortunately .webm doesn't work in IE, OSX Safari or iOS. Though I'd far prefer these services work with both WebM and H264, and use whichever works best.

I wonder how many (huge) sites like imgur it would take saying "we're doing webm, if your browser doesn't support it you get a huge, slow GIF instead" for everyone just to settle on a single format? The whole debate is only hurting users and developers, while lining the pockets of MPEGLA (or whoever is responsible for h264 licensing).

How well did that work for flash when apple decided it wasn't going to put it on mobile.

Re: Introducing GIFV

#177
post #40

Earlier quoted context omitted.

This is a marketing endeavor that is pretending to be a technical innovation.

Yep. Plus gfycat.com does that since a while now, but imgur comes as "oh look we're so innovative". " Imgur plans to submit an accompanying specification to relevant standards organizations" Hi we put a .gifv extension to mp4 can we HTML5 standard this non standard file extension of a standard format?! Riite.

Twitter also followed the gfycat lead before imgur: http://blog.embed.ly/post/89265229166/what-twitter-isnt-tell...

Glad imgur is doing it though, so annoying to have to wait for gifs in 2014 and they are intense bandwidth hogs.

Re: Introducing GIFV

#178
post #175
post #74

Earlier quoted context omitted.

I wonder how many (huge) sites like imgur it would take saying "we're doing webm, if your browser doesn't support it you get a huge, slow GIF instead" for everyone just to settle on a single format? The whole debate is only hurting users and developers, while lining the pockets of MPEGLA (or whoever is responsible for h264 licensing).

How well did that work for flash when apple decided it wasn't going to put it on mobile.

Quite well, I'd say. Most of the big sites have a flash-free version now, if only when you're visiting from an iOS device.

Re: Introducing GIFV

#180
post #103
post #88

To all of you here asking 'why not webm?' consider this -- gfycat serves both webm and h264, I'm pretty sure imgur will add that in future, so no big deal. As for support, most of you are sitting on Chrome already, so you won't have any troubles playing h264. Cheers.

the good ol SF engineer bubble. it must be nice to live such a sheltered life. hint: if you only care about chrome users on every feature, and keep looking at you site access log to justify, you may find that there is a reason why your access log mostly have chrome user in the first place...

I'm not sure what you're getting at. What video codec would you pick, and what does it have to do with the SF bubble?

P.s. It is nice to live a sheltered life.

Post reply on HN