-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add dnslink namespace #268
Conversation
sgtm, but could we bump this above |
I understand the problem, but I don't understand the solution. Would adding this one csv entry, allow go-ipfs to interpret /dnslink? Thus we would re-add (later on) this feature in the dnslink docs to say, 'Hey! If you're using dnslink for your site, use "/dnslink" instead of "/ipns". Because of this...! :
|
@rvagg I don't think it will be as useful as @mrodriguez3313 It is not enough, this PR is only a formal prerequisite that needs to happen before we implement support for mentioned use cases. |
What would CIDs with this new codec look like? |
@RangerMauve bit bizarre, but in places where DNSLink has to be passed as a CID, one could inline DNS name (ASCII) using
(but with |
This comment was marked as off-topic.
This comment was marked as off-topic.
@RangerMauve agree on many of your points, would appreciate your feedback in discussion on "how to pin mutable content paths" happening in ipfs/pinning-services-api-spec#85. Let's keep discussion in this PR limited to adding |
I know too little about all this, hence this one is not blocked on me. |
Rationale: - been around since the very early days, seems we just never added it? - we already have dnsaddr, which works similar way, but for multiaddrs (TXT records) - we want to support IPNS-agnostic recursive TXT values `dnslink=/dnslink/example.com` - we need a way for pinning DNSLink names within Pinning Service API
658b915
to
1c207df
Compare
Rationale:
/ipns/
was good enough for existing use cases/ipns/
in TXT records, so it is useful for non-IPFS use casesdnslink=/dnslink/example.com