Should Collision support more hash functions?

[GeopJr]

There are two approaches:

• Support only the popular ones / only the ones Crystal's Digest supports (md5, sha1, sha256, sha512)
• Support as many as possible

Even though Collision calculates them in a multi threaded way, the more added => the more time or resources will be needed.

There three ways I have in mind for showing them:

• Keep it as is - a spinner until they are ready.
• Add them to the list as soon as they get calculated.
• Select the function in advance.

1. Showing a spinner is fine, but waiting 30s-1m for (the hashes of) an image is too much.
2. Adding them as soon as they get calculated introduces a "moving ui" that will probably be slightly annoying IMO (see Twitter skeletons). Users will still need to wait for their desired hash function to finish.
3. While great if you already know what function you want, for users who want all possible hashes it would require multiple clicks to get them (select function -> copy -> back -> repeat).

Any ideas or suggestions are welcome!

relevant: #102