We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
it seems like between #1 and --enable-namesys-pubsub, we should be able to automagically trigger a pin whenever the name is updated
--enable-namesys-pubsub
I can’t quite figure out how to access this with the current ipfs name pubsub porcelain but it feels so close, doesn’t it?
ipfs name pubsub
(edit this would probably need two layers of IPNS, with the top-layer dnslink pointing to a pubsub based actual-IPNS for the mutable content)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
it seems like between #1 and
--enable-namesys-pubsub
, we should be able to automagically trigger a pin whenever the name is updatedI can’t quite figure out how to access this with the current
ipfs name pubsub
porcelain but it feels so close, doesn’t it?(edit this would probably need two layers of IPNS, with the top-layer dnslink pointing to a pubsub based actual-IPNS for the mutable content)
The text was updated successfully, but these errors were encountered: