Let the entry with the longest history become the 'primary' entry for the topic, leaving the others to be found in the history. I'm thinking in terms of how the Bitcoin blockchain operates, where ~ every 10 minutes a hash function is confirmed and the next block is established. Maybe every hour the wiki system runs a hash function and locks down the content on each page, and the link to the version of the page with the longest history of hash confirmations becomes the destination for any links looking for that page. If no change, no hash function operations are needed so the system saves resources by not running it. More active pages might accelerate the frequency to prevent too much branching.

I'm just brainstorming. While collaboration is critically important, what matters is whether a page and its content are secured and not subject to branching and manipulation. The communications related to trying to get a page or article content agreed by all parties would need to be a "talk page", similar to how Wikipedia does it, but more formalized and in the open. I would love it if someone would put together an instance of Apache Wave for this that works on Nostr. Loved that system.

Reply to this note

Please Login to reply.

Discussion

No replies yet.