Discussion on "How to Query Records by Protocol Path"

Rizel Scarlett · 2023-10-25T02:16:26.957Z

Starting a new job is thrilling because I get to learn new things. At my new job, I'm learning about Web5 and decentralization. So, I'm writing this blog post to share my insights about protocols and querying records. When I built my first Web5 appli...

Hello, I just wanted to say thanks for your post; it was a fascinating read. It mentioned the following protocol URL when I was reading it: blackgirlbytes.dev/ChatProtocol. Upon attempting to access it, I found that the hyperlink does not seem to lead to an active webpage.

Given how often non-functional URLs are included with protocol specs, I'm curious as to if this is really a placeholder URL used for illustration. Could you please confirm if the URL to be used when defining a protocol is meant to be a working example or a valid one?

Thank you again for this post.

Hi! Your protocol doesn't have to be hosted anywhere. Your protocol will still work if you use a uri that's not resolvable aka it returns a 404. But the point of it is for it to be unique and descriptive. That way you can identify it between other protocols..and you know what it's being used for.

My strategy for now is I usually use a domain I already own..which is blackgirlbytes.dev and then I add on something that describes the protocol like blackgirlbytes.dev/chat-protocol or blackgirlbytes.dev/contacts-protocol

These addresses will lead you to a 404, but they help me know what the protocol is supposed to do.

@blackgirlbytes

Thank you for the reply. I get it now. I got confused at first when all the protocol URLs I saw were leading to non-existent pages.

Thank you very much 😊

Search Hashnode

How to Query Records by Protocol Path

Responses1