![]() by converting them to WebM files, would be a simple way to reduce its carbon footprint. That's why we figured that reducing the size of the video assets of the react-admin documentation, e.g. Experiments with GreenFrame taught us that carbon emissions of websites are correlated with their web performance. However, it is far from being the most efficient format in terms of size.Ī common web performance optimization practice is to replace animated GIFs with video for faster page loads. These videos use the GIF format, as it allows easy embedding and has no video compression artifacts. The documentation includes 87 screencasts at the time of writing. Most visitors come for React Admin documentation, with more than 15k monthly views for the Tutorial page alone. With more than 300k views and almost 50k visitors in the last 30 days, the React Admin website receives a lot of traffic. Reducing Carbon Footprint By Using A Better Video Format We will also explain how we built a CLI tool to make the process easier. In this article, we will explain how we reduced the size of the video assets of the React Admin documentation by 62%! By providing open-source tools like GreenFrame, we want to help developers reduce the carbon footprint of their websites.įollowing this pledge, we also want to reduce the carbon footprint of our own websites. Offer an integration piece with imgur that uses imgur to do this … any gif larger than X gets sent to imgur for recompression.At Marmelab, we are convinced that we can use digital innovation to make the world a better place. Get ffmpeg into our base image and do the webm and mp4 conversion for all animated gifs, don’t worry about the flash fallback. If people hotlink anything larger than say 10mb force a “click” to actually download the image and hide it behind a preview I see a few actionable things we can do here: It’s really just a video element with a bunch of fallbacks. Gifv technique championed by imgur is good It does not sound like a good default for Discourse: maybe it is possible to create it as a plugin?Ĭhrome does a terrible job with huge gif files, they can choke the web browser and cause all sorts of nasties not to mention mobile paying a hefty price on traffic and blowing data plans. Such native functionality requires ffmpeg as a dependency and comes with additional security risks. webm versions (we could add another setting: convert only. We would have an additional setting replace. webm it would be just an extension to already existing download remote images to local feature. We can replicate functionality with ffmpeg alone (see 4chan’s guide to converting GIF to WebM). I don’t think they (gfycat) do anything magical beside handling hight traffic quite well. webm into posts via background job would be of course more elegant. gif with video in post (see section “How can I embed these or link to them?”)Ĭustom plugin which bakes. It downloads&converts remote image (if not already present) and returns JSON with video details. Lets say JS iterates over posts and if it finds. Quick hack would be to just use API.Īssuming one does not mirror remote images, I think it is achievable even with pure Javascript which you can add via /admin/customize/css_html. ![]() Some communities would benefit from such functionality.Įspecially ones with download remote images to local setting enabled, but faster page loads alone is a good reason to think about it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |