Mutable & Replyable Storage (Novel? IPNS/DNSLink alternative?)

Has anyone explored just requesting related content id's from a peer hosting an origin piece of content, post peer discovery?

It seems they could just tell you of addresses to new versions, signatures, replies, previous versions, etc. Been mulling on this trying to figure out whats wrong with it; Ideas (new to this area)?

I know it converts this into a peer trust & filtering problem, but it seems the opportunities (content id augmented outward indexing, & social media) outweigh any difficulty there. Also (assuming good idea), not sure if this would be better served in something like libp2p, [Bep-0005](http://www.bittorrent.org/beps/bep_0005.html) (to make mutable everything), or as a separate protocol parallel to IPNS as shown [here](https://github.com/ipfs/go-ipfs#map-of-go-ipfs-subsystems). Seems too this could facilitate peer to peer git vs federated server client (just set git to Sha-256, throw all objects into IPFS, and respond to a set of relationship requests as a peer), would make web archival (better? - a breeze?).

Using this to point to mutable IPFS based URI tables or DNS like structures would then also be trivial.

Full proposal wip [here](https://github.com/inventor2525/Mutable-Decentralized-Storage-Concept) (written for those less aware of DHTs, Merkle DAGs, etc)

*(Not sure atm if this should go in [IPFS notes](https://github.com/ipfs/notes/issues), here, or [libp2p specs](https://github.com/libp2p/specs))*