Petr

I see your point. From reliability perspective, checking against checksum files in releases might help a bit, but I guess modern https is very good already in ensuring reliable transmission....

Let me give a couple of examples: - https://github.com/wireapp/wire-desktop/releases/tag/linux%2F3.28.2946 - https://github.com/syncthing/syncthing/releases/tag/v1.20.4-rc.1 - https://github.com/dundee/gdu/releases/tag/v5.14.0 The checksums are either given as a single file (usually `.txt.asc`) which contains both the original checksums...

More than happy to! I'll write you to the email address I found in #50 to arrange that.

Friendly ping?

> it's been available in the Secure Shell extension for about 2 years now I'm not sure how to interpret this. Does it mean this project is deprecated in favor...

By debugging why this plugin doesn't work on my Vim 8.1 installation. 🙂 Confirmed in https://vimhelp.org/version8.txt.html#added-8.2

In my case it's because I'm using Debian oldstable (can't upgrade because of some other compatibility issues), which has [vim v. 8.1](https://packages.debian.org/search?keywords=vim). Similarly Ubuntu Focal LTS has [vim v. 8.1](https://packages.ubuntu.com/search?keywords=vim)...

This file type detection could also be an optional feature, so users could decide at compile time whether they prefer a smaller binary or a larger one with auto-detection. Some...

I'd very much appreciate this kind of content type auto-detection in any form - even a very primitive one would be very helpful.

The short name should rather be `btmh` (for "BitTorrent Multi-Hash"), following the standardized prefix `magnet:?xt=urn:btmh:`. See also https://blog.libtorrent.org/2020/09/bittorrent-v2/.