Fabric icon indicating copy to clipboard operation
Fabric copied to clipboard
Published 2 days ago • verified publisher icon danielmiessler

[Question]: Duplicate Large Logo GIF Files in Repository

Open ptu14 opened this issue 1 year ago • 0 comments

What is your question?

Description

The project currently contains two identical GIF files that are over 40 MB each and are in very high resolution. These files are used in different locations:

  1. installer/client/gui/static/images/fabric-logo-gif.gif - Displayed as a 40x40 image in installer/client/gui/index.html.
  2. images/fabric-logo-gif.gif - Displayed as a 400x400 image in README.md.

Problem

Having these large, duplicate GIF files in the repository leads to several issues:

  • Increased repository size: Each file is over 40 MB, making the repository unnecessarily large.
  • Redundancy: The same file is stored in two different locations.
  • Performance: Large files can slow down cloning and pulling from the repository.

Suggested Solutions

  1. File Optimization:

    • Convert to AVIF: This format offers better compression (Only available on macOS 13 Ventura or later).
    • Compress GIF: Reduce the size of the GIF files while maintaining quality.
    • Convert to MP4: For the use case in README.md, consider using an MP4 video.

  2. Image Size Reduction:

    • Ensure the images are resized to the actual display dimensions (400x400 and 40x40) before being added to the repository.

  3. Asset Hosting:

    • Host these assets externally, such as on GitHub Pages, to avoid increasing the repository size.

Action Items

  • Evaluate and implement the best compression/conversion method.
  • Remove duplicate files and reference the optimized versions in both locations.
  • Consider hosting large assets externally and linking to them from the repository.

Impact

Addressing these issues will:

  • Reduce the repository size, making it faster to clone and pull.
  • Eliminate redundancy, making the repository cleaner.
  • Improve performance for contributors and users.

I apologize for not preparing a pull request for this issue. I'm not certain which direction the project maintainers would like to take. Once this is clarified, I am more than happy to assist with the implementation.

ptu14 avatar May 30 '24 18:05 ptu14