Following on from this previous post , the WPF and Silverlight code that I've been running tries to access a MeshObject ( containing a DataFeed of photos ) that the code itself creates at initialisation time. What I wasn't sure about at all was how that'd work if I wanted to make the same data available to another person altogether. As it stands, my WPF code runs up and does; Check local mesh for "photos" MeshObject. If not present, check cloud mesh for the same. If not present, create it. If I want to share my photos with lots of other users of the same application then is that what I want? All my users will end up with their own MeshObjects with their own photos and none of them will ever see each other. So...I set about trying to figure out what the "shared data story" is. There's a sample in the walkthroughs called MeshageBoard ( no, really :-) ) which helps quite a lot with this in that it shows the way in which one user can send invitations to another. In order to experiment with this, I decided that it...