People can resolve their own forecasts and if disputed there is a vote. If there is a Community Notes-style consensus[1] for “Yes” or “No” it resolves that way. If not then the question gets delayed 6 months and attempts to resolve then. And over and over.
This way a single user couldn’t delay resolution because there would still be consensus, but lacking consensus isn’t game over, it just roles over.
I’m gonna describe this as requiring consensus where very similar views count for less. So you need support across twitter rather than just a lot of concentrated support (perhaps because others didn’t see the question). I guess it’s strictly more demanding that a majority.
People can resolve their own forecasts and if disputed there is a vote. If there is a Community Notes-style consensus[1] for “Yes” or “No” it resolves that way. If not then the question gets delayed 6 months and attempts to resolve then. And over and over.
This way a single user couldn’t delay resolution because there would still be consensus, but lacking consensus isn’t game over, it just roles over.
I’m gonna describe this as requiring consensus where very similar views count for less. So you need support across twitter rather than just a lot of concentrated support (perhaps because others didn’t see the question). I guess it’s strictly more demanding that a majority.