Safe Network will speed up the Internet?

[happybeing]

It might not be one size fits all, but better to put some control in the app via an API.

[Traktion]

@dirvine

Nicely put and I agree with all of this. We are pushing that all mutable data holds only pointers or 32byte identifiers. All data itself would be immutable. This give us a few good points. I See it like this (and @bochaco / David Rusu are looking at this now, amongst many other points):

That’s interesting to hear. I was thinking that this approach would probably be best design either way, so enforcing it may be no bad thing if it helps the network stay responsive and resilient overall.

Lists of lists (sequential) buys an awful lot of functionality. Likewise for maps of lists or lists of maps.

Imagine a blog, for example. Lists of lists, pretty much. A list of blog posts, with each post being a list of immutable data iterations (maybe just one).

Comments on a blog could be a map to a list of lists to immutable data. The map to link the post to comments, with a list of comments, each as a list of of immutable data iterations (to allow edit comments).

Converting these sequences to immutable data easily could be handy too. Care taker procedures could run and do this on older data, to make it immutable, with all the benefits it brings.

Even the setup of the blog app could be an immutable data item. It could just be linked via an NRS parameter to bootstrap the app (safe://blog-app-xorurl?config=safe://config-xorurl → safe://traktion-blog). The NRS link could be tweaked when the configuration redefined to a new xorurl immutable data.

I’m looking forward to experimenting with some of this stuff soon!

[jlpell]

@dirvine

• Immutable data must go through self_encryption (bad apps might not do this, but they should be flagged as bad).
• Data is then obscured and nodes store what looks like junk (non identifiable data)
• People cannot “hide” data in mutable data elements

Assuming that the mutable data / inodes / pointers are stored on the elders, couldn’t you store a symmetric encryption key in them? That way all chunks get encrypted by the elder prior to being sent out to the adults, and decrypted before being sent back to a client. Even if the app or user was bad and didn’t use self-encryption, the data is still obfuscated at rest in the adult. This is good protection for everyone.