Simple example of datapod profile publish process

The mutation scheme is not compatible with the decentralized signed tracable ipfs-based datapod system yet. So the mutations are reserved for instance admins (for moderation purpose for instance).

@poka worked on a centralized datapod infrastructure with mutations that is talked about here : V2s-datapod: Hasura with Deno middleware to store profiles. You can use this, however :

  • you will have to setup an instance for users to put data on it
  • there will be no mechanism to decentralized data
  • you will be responsible for user data and service uptime

I recall that my datapod suggestion aims to be decentralized and is at the PoC stage. Clients developers can choose on which backed they want to store offchain data, each with benefits and drawbacks. One could event use firebase, even this would be quite far from Duniter philosophy.