This thread was made for people like me!
Okay, so I see everyone throwing around MDs that can be shared. Hey, share with your friend, share with yourself, share with nobody. This all sounds fantastic! I’d love to share some MDs with myself across app sessions, more than just using the Own container. I absolutely see people saying this is a thing that happens.
I’m parsing through the breaker-plugin-safe-app 0.3.0 API. Perhaps I need to be pointed to a more relevant source?
ImmutableData has an XoR name. You can
fetch() it. Sweet! I can share IDs! I can create an ID, I can get the XoR name for that ID, I can share an ID by sending someone the XoR name, and if someone gives me an XoR name I can fetch it!
I know I can create an MD (lots of ways,
newPrivate*, toss in a bit of
quickSetup for seasoning). I know I can fetch named containers with
App.getOwnContainer. Great! Okay. Now I’ve got this MD and I want to stash some kind of reference to it in … I dunno let’s say my Own container … so that I can access it in later sessions. Or I want to send it to Bob from Accounting.
Where and how does this actually occur? There is only one reference to an XoR name in that entire API relating to MD:
safeApp.authoriseShareMd(). How do I get the XoR name for an MD that I’ve created? I assume once I’ve got the XoR name, I share the MD with others using
authoriseShareMd()? Honestly the docs for that function say “authorise this application with specific mutation permissions for a MutableData” and not “fetch this MutableData from the Network, also btw we’ll use these permissions.” It sure doesn’t sound like it actually helps you get MD off the Network. Not that I know how to get an MD XoR.
From what I’ve seen of handles, those appear to be transient, app-specific, volatile references. I’m not going to create an MD, store its handle to my Own container, and make use of that handle later, right? Or is that the vital piece I’ve completely missed? If so, why is ID different?