cryptomator / cryptomator

Multi-platform transparent client-side encryption of your files in the cloud
https://cryptomator.org
GNU General Public License v3.0
11.4k stars 978 forks source link

Adjust handling of file extension metadata for Linux Builds to "new standard as of #1089" #1544

Open JaniruTEC opened 3 years ago

JaniruTEC commented 3 years ago

Summary

As of now Linux Builds don't show the correct icon for Cryptomator files (e.g. .c9r) and are missing some mimetypes. Linux Builds should offer the same features as Windows/macOS Builds in this matter as far as possible. This "new standard" was developed in issue #1089

Motivation

Achieve the same level of quality for file extension metadata for all supported platforms.

Additional Context

See #1089 for the original issue and https://github.com/cryptomator/cryptomator-mac/pull/7 and https://github.com/cryptomator/cryptomator-win/pull/36 for the scope of this issue. (As well as https://github.com/cryptomator/cryptomator-win/commit/c60947525917e43213576f30ebdf65ba4714a49a and https://github.com/cryptomator/cryptomator-win/commit/2447ddbd25cd5173e904d75f74882169c3e5ad84)

infeo commented 3 years ago

Cryptomator is build and delivered as an appimage. According to their docs, the media type registration is done by another service: https://docs.appimage.org/user-guide/faq.html?highlight=mime#question-how-can-i-integrate-appimages-with-the-system

So i guess we only have to put the correct info inside the appimage at the correct spot.