Skip to content

feat: add hash property #55

@tipogi

Description

@tipogi

One issue we’re facing is that when one event references another, we can’t be sure the referenced content is still the same because it may have been edited since we pointed to it, e.g:

  • A user replies to a post. If the post’s author later modifies that text, the reply no longer matches what was originally referenced
  • Same with repost, tags and bookmarks

Solution

When creating a event that references another event, generate the hash of the target content at that moment. Then, each time we render in the app:

  1. Compare the stored hash with the current content
  2. If they don’t match, display a warning like “The referenced content has been changed”

This ensures users always know if the content they referenced has been edited

Breaking changes

The need to add the hash property in the specs models, it affects to the app and nexus watcher

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions