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?

Quote from: bob123 on May 15, 2018, 09:06:24 AM

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

Would that be a good fit for this problem?

Since you are working on an immutable data structure the only way of accomplishing such an 'update' would be to reference to the old block/tx/message.
You approach should just work fine. That would have been my first approach too.

You just have to keep in mind that you still need verification (only poster of the first message can 'update' this message).

But note that the displaying of those messages (especially the updated messages) is done client-side.
It is definetely possible to see all old messages. The client has to be set up correctly and needs to have the blockchain synced and verified to display all messages/posts correctly.

Lets pretend the following:
Alice does post some text at block X.
Alice does edit this post at block X+10.

If Bob opens his clients and syncs, the moment he reaches block X, he will see the first post by Alice.
This will be the only message bob will see until he has synced up to block X+10.

Short answer: Yes, i think so.

Thanks for the answers, so the idea would have a web platform that will be always keep on sync with the blockchain, so this problem would be solved, since the user has no client and he doesn't needs to update it.