This is where StructuredData will kick in, when mixed with multiple owners, groups can be created. Now this leads to something I have not discussed yet as I am trying really hard to release small bits at a time (issuing RFC’s with each small part and I have barely started), to ensure all Engineers, community etc. grasp it all a bit at a time and completely grasp it.
So (impatient folks you know who you are ) to dive right into the deepest part of this with no safety net, here are some options (there are so so many ways, I am not even looking at the best or anything like that here, just samples, I am 100% people will come up with better more sophisticated mechanisms, just imagine semantic data types here, etc.
Create a blog type - say type 5555 and a blog page, say identity
a4567b234ec456456...01 So we have a type that is a blog and an identifier.
Now a comment type - say 6666 and now a user creates comment 1 so the identity is
Next commenter can add another comment
and so on.
This can be taken further where the comment type has not only content (unencrypted content, I hope ) but also a parent field. So you can have threaded comments.
This gives commenter full control of first come first served commenting ability (as they will occupy the 6666
Identity space on the network.
So now we want moderated comments. So we can demand that the
6666 type has blog owner as part of 2 part multisig (or not read it) which can allow either party to delete.
Or we can have a type where the comment type
6666 requires that the type contains the blog owner (or owners if blog is owned by a group, multi-sig) only to decide to keep or not.
This goes on and on, so you can have the flexibility you want, even without multi-user access to a specific time and place on the network. In the case here, the App (blog reading) implements the rules of the types (demands the layout of the data element) or considers the element invalid, so ignores it.
I promise we will document and show many ways to achieve this and much much more as soon as we get feature complete for dev bundle 3 at least (then we have more than promised out there and we can create some great apps and get the tech debt and security sprints out the way).
This is a super super simple and crude way of doing what you want, there is so much more but you would not fail with this for sure.
Now create a Map type and link to Reduce types and you can see system wide Map-Reduce capabilities for big data analysis (of public (non encrypted) data). OR perhaps a type that contains semantic index like name: then link that as with the blog for full semantics of name: types, then add city: town: population: etc. Then you can look at adding new owners based on certain characteristics to gain more knowledge, then perhaps these identities can pool their findings, maybe they are AI or robot’s ? The list goes on to the point it sounds mad, but this really is nothing yet. None of this has come close to what I imagine we will be able to achieve. The link with this and public data is going to be a huge step, but really we need to get to dev bundle 3 first. Next sprint dev bundle 2 will be made available so we are closing in.
None of this even has included private shares yet, these will add many more features and will require synchronisation. So a lot of work to get through. Anyhoo hope this helps a wee bit.