How to avoid duplicate proposals ?

[SFSandra]

...this is not a bug so much as a question about how the functionality will evolve to prevent individuals from posting the same issue for voting?

[domi41]

The solution used by Google Groups and Discourse (among others) is to show you open threads that might be related to what you're typing when you start a new thread. It's very effective, but pretty tough to actually implement.

[dylangessner]

I'm new to the project but I was thinking about this problem too. What if Members creating Issues had to stake VOTE tokens simply to create a proposal? This may, at the very least, make a user pause before creating an Issue and hopefully search to see if it already exists.

Following on that idea, perhaps Issues would be listed/ranked by the number of VOTE tokens involved via those initially staked by the proposer + other Members casting VOTEs.

If the Issue was Tactical (having an end), then at the close of the Issue the proposing Member gets his/her staked VOTE tokens back, regardless of result.

[RyanCwynar]

Seems like you'd want a retroactive way to merge threads after the fact, in any case. Even with good autocomplete and stuff, it will happen. So allowing people to acknowledge that they've created a duplicate-ish proposal after the fact and allow it to be merge with the older one is likely a good idea.