Quote from: redigaffi on May 16, 2018, 08:22:59 AM

Quote from: ETFbitcoin on May 15, 2018, 01:36:07 PM

Quote from: bob123 on May 15, 2018, 09:35:39 AM

Quote from: redigaffi on May 15, 2018, 09:21:08 AM

Quote from: innovator256 on May 15, 2018, 09:08:43 AM

you would be creating a problem rather than a solution in the long run. Such data could be stored on ipfs anchored to the actual chain

Could you elaborate your answer a little bit more please?

I can't follow this statement either..

Surely he means such idea/project better done with InterPlanetary File System where node don't need to store each data. On high-level, it's similar with Torrent file distribution.

Quote from: redigaffi on May 15, 2018, 08:38:37 AM

Would that be a good fit for this problem?

Not bad idea, but IMO it would be better if :
* the type of the changes is "updated_post" or "edited_post", not "post". It's even shorter if we use type_id instead to lower the size.
* Only input the info/post changes to lower the size. Similar with Git commit where git only save the different part to save storage space and make commit process faster.

Good idea, surely that would save a lot of space/memory in the long run, but that would add an extra layer of complexity.

True, but that would make scaling easier even though there's higher computation power needed to make and verify the differences.
IMHO longer development time or higher complexity is bigger than sacrifice decentralization.