multiformats / multicodec

Compact self-describing codecs. Save space by using predefined multicodec tables.
MIT License
337 stars 201 forks source link

Adds Textile Thread multiaddr #201

Closed carsonfarmer closed 3 years ago

carsonfarmer commented 3 years ago

The thread protocol is now relatively well-recognized in the community. Perhaps its time to make it official?

Stebalien commented 3 years ago

What is a thread multiaddr used to address? Usually, multiaddrs are used to address endpoints/machines, not resources/content.

However, this issue comes up so frequently I'm writing a proposal to see if we can unify around a "multipath" concept: https://github.com/multiformats/multiformats/pull/55.

carsonfarmer commented 3 years ago

Yup, multiformats/multiformats#55 is probably exactly what we're looking for. In theory, a thread multiaddr is used to address a resource available via a particular peer/endpoint. But it does go one step further than "endpoint/machine" to address a resource.

carsonfarmer commented 3 years ago

I see the conversation around the above linked "multipath" proposal is somewhat stalled. What is the likelihood of moving forward on that, versus just working with the code proposed in this PR?

rvagg commented 3 years ago

@Stebalien you're probably the authority for that question ^, specifically does:

But it does go one step further than "endpoint/machine" to address a resource.

raise thread to being something we can fit in here?

Stebalien commented 3 years ago

Yes, that's why I made the multipath proposal. It's a simple generalization of multiaddr.