A problem that often comes up is how to deal with updates in a immutable world. One solution is to use IPNS but the user (as IPNS is right now) don't get a choice which hash to be loaded when they load it. Instead the user has to resolve the IPNS record, save the IPFS hash and load that instead of IPNS. Might not be a big hassle, but the user might miss out on updates they want.
Taking inspiration from various nodejs cli modules, there could be a solution deployed with pubsub. Some nodejs clis will output a message after finishing running, telling users that there is a update available and instructions to upgrade. Similar could be done via pubsub (or still IPNS).
If this is on the application layer, even if the user is using IPFS hash instead of IPNS, they can be notified of new upgrades and get a link to a new hash.
A problem that often comes up is how to deal with updates in a immutable world. One solution is to use IPNS but the user (as IPNS is right now) don't get a choice which hash to be loaded when they load it. Instead the user has to resolve the IPNS record, save the IPFS hash and load that instead of IPNS. Might not be a big hassle, but the user might miss out on updates they want.
Taking inspiration from various nodejs cli modules, there could be a solution deployed with pubsub. Some nodejs clis will output a message after finishing running, telling users that there is a update available and instructions to upgrade. Similar could be done via pubsub (or still IPNS).
If this is on the application layer, even if the user is using IPFS hash instead of IPNS, they can be notified of new upgrades and get a link to a new hash.