Prior discussions: https://news.ycombinator.com/item?id=6773039 and https://news.ycombinator.com/item?id=6189397
Open source: https://github.com/MediaCrush/MediaCrush
Browser extensions: https://mediacru.sh/apps
51–60 of 78 posts
Prior discussions: https://news.ycombinator.com/item?id=6773039 and https://news.ycombinator.com/item?id=6189397
Open source: https://github.com/MediaCrush/MediaCrush
Browser extensions: https://mediacru.sh/apps
If someone can create a simple Firefox/Chrome addon that takes imgur .gif links, and automatically converts the URL from this: http://i0.kym-cdn.com/photos/images/original/000/666/838/7fb.gif To this: gfycat.com/fetch/http://i0.kym-cdn.com/photos/images/original/000/666/838/7fb.gif I'm sure it would easily become a top 20 addons hands down.
Extension is now published, though there is no fancy art yet: https://chrome.google.com/webstore/detail/autogfy/aleldfepmn... Enjoy!
If someone can create a simple Firefox/Chrome addon that takes imgur .gif links, and automatically converts the URL from this: http://i0.kym-cdn.com/photos/images/original/000/666/838/7fb.gif To this: gfycat.com/fetch/http://i0.kym-cdn.com/photos/images/original/000/666/838/7fb.gif I'm sure it would easily become a top 20 addons hands down.
Extension is now published, though there is no fancy art yet: https://chrome.google.com/webstore/detail/autogfy/aleldfepmn... Enjoy!
Earlier quoted context omitted.
I imagine it's because your phone has hardware H.264 decoders, while GIF is being done in CPU.
No, every mobile can process a 80ties picture format in tiny resolutions. 90ies computers could do that without a problem without any allocation an needed only a fraction of their cpu. Now we have quadcore cpus clocked at >1 GHz in our mobiles. It's just the saved bandwidth. And, btw, hardware allocation is a way overrated. There is a HEVC software implementation for the iphone. Just compare the complexity of HEVC to…
GIF's are really a nineties format (90ties??), the animation and alpha components weren't added to the standard until 1989, and adoption wasn't widespread until after then.
You're also overlooking the fact that you simply didn't get 4.5MB+ GIFs in the nineties like the example given because it would take ten minutes to download that on a 56K modem. I must resign myself to the fact some people never grew up with dial-up!
Animated gifs in 1995 were rather different to animated gifs now.
Earlier quoted context omitted.
Is OTOH really an acronym people are using now?
Earliest usage of the term I can of the term on newsgroups is 1988. I was certainly using it in the early 90s.
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
They could serve webp files to browsers that claim to support them in their request headers. It can confuse users that save files to not actually have a gif, though.
Earlier quoted context omitted.
Extension is now published, though there is no fancy art yet: https://chrome.google.com/webstore/detail/autogfy/aleldfepmn... Enjoy!
Can you put the source on Github please?
Is there any way of doing this offline for large animated GIF collections?
Is there any way of doing this offline for large animated GIF collections?
Edit: It uses ffmpeg