What changes will I make to my Manifold search function and trading dashboard by the end of November?
6
3.7kṀ16k
resolved Dec 1
Resolved
YES
Add a sort/filter for total traders
Resolved
YES
Add a "not" option in the search fields, to exclude a certain term.
Resolved
YES
Allow searching with regular expressions.
Resolved
YES
Update the URL live as the user modifies their search, so that they can copy-paste the URL if they want to send a link to link the search to someone else.
Resolved
YES
Use a market's lastUpdatedTime to determine how frequently it needs to be queried for updates.
Resolved
YES
Listen to /bets and get a new probability for any market that was just bet in.
Resolved
YES
Crawling the full dump of all markets can happen concurrently with other market updates rather than putting them all on hold.
Resolved
YES
Filter by market type.
Resolved
YES
Add a column for volume
Resolved
YES
When the user hovers over a topic, display the total number of markets in that groups
Resolved
YES
Stream data retrieval from the OPFS, so it loads in chunks rather than blocking the page for ~500ms.
Resolved
YES
Let people link to specific visibility options and sorting order via URL parameters.
Resolved
YES
Allow markets to be filtered by "closed and not yet resolved".
Resolved
YES
Make the "time until close" display update automatically, so there's a live countdown.
Resolved
YES
Fix the lag, so that user input is responsive.
Resolved
80%
Retrieving new markets should happen concurrently rather than one at a time.
Resolved
NO
Bug: numeric markets are displayed as though they were regular percentage markets.
Resolved
NO
Let a user filter to markets in which they have limit orders
Resolved
NO
Don't sort all markets, just find the ones that would be in the top 200 of the sort.
Resolved
NO
Add a sort/filter for elasticity, limit orders, and/or some other similar measure

I would like suggestions on how to improve my third-party Manifold search page and trading dashboard. If there's something you'd like to see added, add it as an answer, and explain in the comments why you think it would be useful. If you have a suggestion that includes multiple independently-implementable parts, err on the side of making it multiple separate answers.

I am more likely to implement changes that are:

  • Useful for practical purposes.

  • Wanted by more than one person.

  • Easy to implement.

That's not to say I won't take on harder or more niche projects, espetially if it's something I myself would find useful. I enjoy programming, I just don't have infinite time. Please suggest even minor improvements that you'd like to see; the worst case scenario is just that I decide not to do that.

If you see a suggestion from somebody else that you'd also find useful yourself, please like that comment or indicate your agreement in some other way, so that I can get an idea of what to prioritize.

Any time I impliment one of the answers, I'll resolve it to YES. Any that I haven't fully implimented at the end of November will resolve to NO. If there are redundant or overlapping answers, that's fine, they'll each resolve appropriately. If anyone adds an answer that's already been implemented, I'll resolve it N/A.

I won't bet NO (so you don't need to worry about me choosing not to impliment something in order to turn a profit), but may bet or sell YES.

Get
Ṁ1,000
to start trading!

🏅 Top traders

#NameTotal profit
1Ṁ810
2Ṁ352
3Ṁ124
© Manifold Markets, Inc.TermsPrivacy