Warn when publishing ipns records without a running daemon.

[Stebalien]

It technically works and has some use-cases but IPNS records won't persist unless a daemon republishes them in the background. This has now come up several times on the forums and I expect it to come up more frequently in the future.

[kjzz]

Hey @Stebalien , if nobody is doing for this, Can i work on it?This can help me know more about ipns.Dou you have any advice for this issue?Add a warning log or others?
In addition,I have a question that if in terminal we can use command ps aux | grep ipfs to know any daemon running or not.Also golang has execpackage to execute command，but i do not think it is a great way.WDYT?

[Stebalien]

After thinking about this, I believe we actually want to error out but add a flag to bypass the offline check. That is, add a boolean --allow-offline flag such that:

1. If the flag isn't passed (or is false), return an error if the node is in "offline" mode. When I say "the daemon isn't running", I'm talking about offline mode. You can check this inside a command by checking node.OnlineMode(). See: https://github.com/ipfs/go-ipfs/blob/2de616300ba663018bb8918bea72193892059115/core/commands/name/publish.go#L81-L87

2. If the flag is specified (true), keep the current behavior.

This will be a breaking API change but I believe it's for the best (most users would be surprised by the current behavior).

Given that this is a breaking change, anyone on @ipfs/go-team have opinions?

[kjzz]

Thx for advice.I will work for this

[kjzz]

Hey @Stebalien ， i has refactor some code and add allow-offline command in publish.Please help me review the pr #5477 ,Thx a lot.