Titusz

It is in the works. We have requested a multicodec code for the next release of ISCC. See: https://github.com/multiformats/multicodec/pull/252 Also the Instance-Code component of the ISCC is meant to be...

We now use CIDv1 as the default hash for ISCC Metadata: https://core.iscc.codes/utilities/utils/#iscc_core.utils.cidv1_hex

Yes base32 encoding is on its way (see: https://github.com/iscc/iscc-specs/blob/develop/iscc/codec.py#L183). The switch is planned to be included with the upcoming 1.1 release. I created a separate issue for that. One open...

Yes we should carefully think about self-descriptiveness and forward compatibility. The ISCC is a composition of multiple hashes, that can also be used separately if required. One way would be...

@lrosenthol thank you for pointing this out. Adopting existing standards is indeed preferable where it makes sense. I am following the development of [multiformats](https://multiformats.io/) closely and have also been [experimenting...

@lrosenthol I have opened an issue to make the next version of ISCC multiformats compatible: https://github.com/multiformats/multicodec/pull/252#issuecomment-996740862

Can you confirm that the error also happens if you call the iscc-cli command directly from the command line on the system? You could also check under what locale the...

Yes that is an issue. But it is an issue for any kind of user generated metadata. We should add a warning in the specification. Something along the lines of:...

I am also not sure if the Linux binaries can cause problems. I built them with [manylinux](https://github.com/pypa/manylinux). Their claim is "Python wheels that work on any Linux (almost). 🤷

Ok I see they write: PEP 600 has been designed to be "future-proof" and does not enforce specific symbols and a specific distro to build. It only states that a...