Will Manifold Markets add a Merge Function for Multiple Answer Questions by the end of the year?
12
323
resolved Jan 10
50%46%
No
50%46%
No
0.6%
Yes
0.7%
Yes
3%
Question Creator can Merge
0.8%
Answer Creator can Merge
0.7%
Community Process for Merging
0.2%
Creator can delete duplicates
This market will resolve to yes if there is *any* merge functionality added to Free Response questions before the end of the year. In markets that allow multiple answers, sometimes duplicate answers are created by users. This disrupts the accuracy of the market and will distort payouts and costs. For example, in the @AdamAdam pointed out here: https://manifold.markets/TheSkeward/who-will-be-the-administrator-of-th#UVHCb6sRp0IO3M0HX7Iv That @Test Test submitted a duplicate answer that I had already submitted. When I checked the other answers I noticed that this was not the only duplicate. There are many different ways that Manifold could create a merge function. Allow the question asker to merge answers, allow answer submitters to merge them collaboratively, or some sort of community nomination and confirmation process. This market will resolve as long as there is some kind of merge function before the end of the year regardless of the specific function that Manifold Markets chooses (or not) to implement.
Get Ṁ200 play money

🏅 Top traders

#NameTotal profit
1Ṁ73
2Ṁ40
3Ṁ10
4Ṁ5
5Ṁ0
Sort by:

I resolved using the multiple no answers. Resolving to multiple answers solves the same problem that merging solves, but it is a different process than merging is so I went with no.

answered
Creator can delete duplicates
bought Ṁ1
Strongbad merge
answered
Question Creator can Merge
bought Ṁ20
@Honourary Yes! This is something we want to do. Aside from merging, we also want to support betting against answers. Plus, we intend to switch to fixed payouts (instead of the current system which only roughly gives the payout it says.) With these mechanics, I think free response markets will be a lot more useful!

@JamesGrugett Did you manage to do this? How should I resolve.

@Honourary Nope, we did not, sorry. You should resolve NO.