Seed Surveys Module

Random notes. Don't take them seriously.

Targeting an object or resource should be enough. The daemon should handle delivery and networking. Instead, I have to take care of the networking.

A module, by default, can include a specific Peer

I added those peer addresses as the built-in default for this destination account:

z6MkkeXDXo4p5y483NqxnMjZKbE4VAv8GPXp3kQ5JGYbTTsR

So your existing config can stay like this:

{
  "registeredAccountUid": "z6MkhGQJc96o3UNQ3JyUbCKfQo2bvaQ9KDNa9xxYHJFWWTwg",
  "sourcePeerId": "12D3KooWD8enqrfeXVpeKWFsgg8dyojKchLxAwx3mUZtQbRtXvyv",
  "feedbackDestinationAccountUid": "z6MkkeXDXo4p5y483NqxnMjZKbE4VAv8GPXp3kQ5JGYbTTsR",
  "feedbackDestinationLabel": "Seed Surveys",
  "feedbackSignerAccountUid": "z6MkmYhMohZM7agevqQdejj56Y6ZQNVVMw2Mq3LUmER4jNtf",
  "feedbackDestinationCapabilityCid": "bafy2bzacedh3rr5ew5nvy4exly2zietju3dkqawyqzciyjkevtqewwp7kdq7k",
  "feedbackDocumentVisibility": "public"
}

You only need to add feedbackDestinationPeerAddrs if later you want to send feedback to a different destination account/siteor override the default Seed Surveys peer.

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime