multiformats / multibase

Self identifying base encodings
289 stars 74 forks source link

Consider encoding: NewBase60 #36

Open singpolyma opened 6 years ago

singpolyma commented 6 years ago

http://tantek.pbworks.com/w/page/19402946/NewBase60

In heavy use by the IndieWeb community

ribasushi commented 4 years ago

Could you elaborate on the benefits of adding support for this codec?

Multibase sits at a rather pivotal "entrypoint" in the decoding process: adding additional encodings carries implementation costs to each individual language/library. Some already unilaterally decided not to support the full gamut: https://github.com/richardschneider/net-ipfs-core/issues/54

If anything we are considering dropping some of the entries: https://github.com/multiformats/multibase/issues/59#issue-475808734

ribasushi commented 4 years ago

🤦 I replied to the wrong issue 😸

But the notes above apply to base60 as well: could you elaborate on how adding the NewBase60 codec would benefit either IndiWeb or IPLD?

singpolyma commented 4 years ago

NewBase60 is often used in indieweb identifiers that are meant to last s long time in archives past the death of their website hosting, etc, on multiple services as social data gets syndicated to multiple services, etc.

So having an assigned multibase identifier can help these be more self-documenting when someone comes across one out of context especially, which is likely.