Let a user filter to markets in which they have limit orders

'filter':4 'let':1 'limit':11 'market':6 'order':12 'user':3

Let moderators users add/remove tags directly from the search page

'add/remove':4 'direct':6 'let':1 'moder':2 'page':10 'search':9 'tag':5 'user':3

Fix the bug that causes numeric markets to be displayed as though they were regular percentage markets.

'bug':3 'caus':5 'display':10 'fix':1 'market':7,17 'numer':6 'percentag':16 'regular':15 'though':12

add reminders to check back on a market after some time

'add':1 'back':5 'check':4 'market':8 'remind':2 'time':11

Add fuzzy searching that can catch typos and synonyms

'add':1 'catch':6 'fuzzi':2 'search':3 'synonym':9 'typo':7

Add an OR conjunction for search terms, so people can search for something like "question includes 'altman' OR 'OpenAI'"

'add':1 'altman':17 'conjunct':4 'includ':16 'like':14 'openai':19 'peopl':9 'question':15 'search':6,11 'someth':13 'term':7

Add tiny arrows in each column header as a visual indicator that they can click there to sort the column

'add':1 'arrow':3 'click':15 'column':6,20 'header':7 'indic':11 'sort':18 'tini':2 'visual':10

Add a quickbet button where the user inputs their expected probability, and it calculates and places the appropriate Kelly bet size based on their portfolio.

'add':1 'appropri':18 'base':22 'bet':20 'button':4 'calcul':14 'expect':10 'input':8 'kelli':19 'place':16 'portfolio':25 'probabl':11 'quickbet':3 'size':21 'user':7

Let people filter by market type. (Binary vs. multiple-choice, etc.)

'binari':7 'choic':11 'etc':12 'filter':3 'let':1 'market':5 'multipl':10 'multiple-choic':9 'peopl':2 'type':6 'vs':8

Add a way to go directly to a creator's profile from the search page

'add':1 'creator':9 'direct':6 'go':5 'page':15 'profil':11 'search':14 'way':3

Add an option to display each answer on a multiple-choice market as its own row in the search results.

'add':1 'answer':7 'choic':12 'display':5 'market':13 'multipl':11 'multiple-choic':10 'option':3 'result':21 'row':17 'search':20

Add hotkeys or a similar workflow for placing bets extremely quickly across multiple markets

'across':12 'add':1 'bet':9 'extrem':10 'hotkey':2 'market':14 'multipl':13 'place':8 'quick':11 'similar':5 'workflow':6

Add a "concise mode", which removes all extraneous text from the table, like the percent sign, M$ sign, etc.

'add':1 'concis':3 'etc':19 'extran':8 'like':13 'm':17 'mode':4 'percent':15 'remov':6 'sign':16,18 'tabl':12 'text':9

Let a user filter to markets in which they have positions

'filter':4 'let':1 'market':6 'posit':11 'user':3

Let a user see their own positions in each market

'let':1 'market':10 'posit':7 'see':4 'user':3

Add a tiny graph/sparkline on each row to show how the market has changed recently

'add':1 'chang':14 'graph/sparkline':4 'market':12 'recent':15 'row':7 'show':9 'tini':3

Instead of a target probability, let users specify a target change, e.g. "increase probability by 1.5x". This way they can bet multiple answers in a multiple-choice market down in arbitrage without taking a position on which is more likely

'1.5':16 'answer':24 'arbitrag':33 'bet':22 'chang':11 'choic':29 'e.g':12 'increas':13 'instead':1 'let':6 'like':42 'market':30 'multipl':23,28 'multiple-choic':27 'posit':37 'probabl':5,14 'specifi':8 'take':35 'target':4,10 'user':7 'way':19 'without':34 'x':17

'add':1 'filter/sort':3 'recent':5 'subsid':6

Let the user input some custom time interval like "5 minutes" or "1 day", and add a column that displays the market price that long ago.

'1':13 '5':10 'add':16 'ago':26 'column':18 'custom':6 'day':14 'display':20 'input':4 'interv':8 'let':1 'like':9 'long':25 'market':22 'minut':11 'price':23 'time':7 'user':3

Add a filter to only show markets the user hasn't seen before.

'add':1 'filter':3 'hasn':10 'market':7 'seen':12 'show':6 'user':9

Put it up on Github and let anyone contribute changes

'anyon':8 'chang':10 'contribut':9 'github':5 'let':7 'put':1

Add a way to sort markets by potential profit, including limit orders

'add':1 'includ':10 'limit':11 'market':6 'order':12 'potenti':8 'profit':9 'sort':5 'way':3

Let people resolve markets directly from the search page

'direct':5 'let':1 'market':4 'page':9 'peopl':2 'resolv':3 'search':8

Give an option to use regular expression wildcard search syntax of market titles and or descriptions.

'descript':16 'express':7 'give':1 'market':12 'option':3 'regular':6 'search':9 'syntax':10 'titl':13 'use':5 'wildcard':8

Add an omnibox for faster searching if you're already familiar with the syntax, like Scryfall offers

'add':1 'alreadi':10 'familiar':11 'faster':5 'like':15 'offer':17 'omnibox':3 're':9 'scryfal':16 'search':6 'syntax':14

Add a sort/filter for market lucrativeness that takes limit orders into account somehow. (Could use Manifold's elasticity metric, or do it some other way.)

'account':12 'add':1 'could':14 'elast':18 'limit':9 'lucrat':6 'manifold':16 'market':5 'metric':19 'order':10 'somehow':13 'sort/filter':3 'take':8 'use':15 'way':25

Make the choice of which markets to store locally smarter, so it won't accidentally cross the 5MB localStorage limit.

'5mb':18 'accident':15 'choic':3 'cross':16 'limit':20 'local':9 'localstorag':19 'make':1 'market':6 'smarter':10 'store':8 'won':13

If the user enters a date, it should be treated as a range from the beginning of that day to the end, not just the single millisecond at which that day begins.

'begin':16,32 'date':6 'day':19,31 'end':22 'enter':4 'millisecond':27 'rang':13 'singl':26 'treat':10 'user':3

Make saveMarketData faster and run it immediately after any market data is updated

'data':11 'faster':3 'immedi':7 'make':1 'market':10 'run':5 'savemarketdata':2 'updat':13

Check to see if any of the code has changed upon page load, and if so wipe the cached market data and reload it.

'cach':19 'chang':10 'check':1 'code':8 'data':21 'load':13 'market':20 'page':12 'reload':23 'see':3 'upon':11 'wipe':17

Let users filter/sort/view by their profit in each market

'filter/sort/view':3 'let':1 'market':9 'profit':6 'user':2

Add direct links to user profile and/or group pages, maybe accessible by shift-clicking on them.

'access':11 'add':1 'and/or':7 'click':15 'direct':2 'group':8 'link':3 'mayb':10 'page':9 'profil':6 'shift':14 'shift-click':13 'user':5

Add cleverer hyphen parsing in the date fields, so that people can enter things like "2023/01/01-2024/01/01" or "-1y-1y".

'-1':18 '1y':21 '2023/01/01-2024/01/01':16 'add':1 'clever':2 'date':7 'enter':13 'field':8 'hyphen':3 'like':15 'pars':4 'peopl':11 'thing':14 'y':20 'y-1y':19

Add support for other platforms. Polymarket, Kalshi, etc.

'add':1 'etc':8 'kalshi':7 'platform':5 'polymarket':6 'support':2

Add more complex diff detection so that the client can catch up on what it missed if it loses internet for a few minutes.

'add':1 'catch':11 'client':9 'complex':3 'detect':5 'diff':4 'internet':20 'lose':19 'minut':24 'miss':16

Let people select multiple answers and bet in them all at once, providing a single total amount of mana and a single target probability that's split up along them all in an efficient manner. (Not equal; further get more)

'along':29 'amount':17 'answer':5 'bet':7 'effici':34 'equal':37 'get':39 'let':1 'mana':19 'manner':35 'multipl':4 'peopl':2 'probabl':24 'provid':13 'select':3 'singl':15,22 'split':27 'target':23 'total':16

Let people see the profit of selected other users in each market

'let':1 'market':12 'peopl':2 'profit':5 'see':3 'select':7 'user':9

Add an option to change the height of each row such that it's proportional to the width of the interval between the previous market's close time and the next market's close time, so distance down the page represents time in the future.

'add':1 'chang':5 'close':27,34 'distanc':37 'futur':45 'height':7 'interv':21 'market':25,32 'next':31 'option':3 'page':40 'previous':24 'proport':15 'repres':41 'row':10 'time':28,35,42 'width':18

Change "groups" to "topics" and use that consistently

'chang':1 'consist':8 'group':2 'topic':4 'use':6

Option to show dates in a standardized day/hour/minute format that all lines up

'date':4 'day/hour/minute':8 'format':9 'line':12 'option':1 'show':3 'standard':7

A column to display the market price X amount of time ago, input by the user

'ago':12 'amount':9 'column':2 'display':4 'input':13 'market':6 'price':7 'time':11 'user':16 'x':8

Add some way for clicking on a group or creator to wipe the rest of the search. Maybe shift-click? Or maybe it should be the default?

'add':1 'click':5,21 'creator':10 'default':28 'group':8 'mayb':18,23 'rest':14 'search':17 'shift':20 'shift-click':19 'way':3 'wipe':12

If the user's cursor is in a betting field, that location should remain when the list of markets is updated.

'bet':9 'cursor':5 'field':10 'list':17 'locat':12 'market':19 'remain':14 'updat':21 'user':3

Option to display close/creation/last update time in absolute terms rather than relative

'absolut':8 'close/creation/last':4 'display':3 'option':1 'rather':10 'relat':12 'term':9 'time':6 'updat':5

Fix the memory leak. (Evan reported 12GB of memory usage on one occasion, and mine sometimes crashes after left open for a long time.)

'12gb':7 'crash':17 'evan':5 'fix':1 'leak':4 'left':19 'long':23 'memori':3,9 'mine':15 'occas':13 'one':12 'open':20 'report':6 'sometim':16 'time':24 'usag':10

'default':7 'market':2 'new':4 'open':1 'tab':5

Add a description of the functionality of the dashboard checkbox to the docs page

'add':1 'checkbox':10 'dashboard':9 'descript':3 'doc':13 'function':6 'page':14

 $30,000 over the next three months to projects designed to benefit the Manifold community. (The first payout date is December 15th, and that's the one this market will resolve based on.) I 

custom search function and trading dashboard

A valid answer to this market is a feature suggestion or bug report. Any answer that I do not implement by December 15th resolves N/A. If my project receives at least $500 as part of the December 15th payout, all answers that I implemented resolve YES. Otherwise, they resolve NO.

To rephrase, each answer implements the question "conditional on [feature] being implemented, will Isaac's trading dashboard get at least $500 in the first payout?" (Determining causality is hard, so it's irrelevant whether the feature 

That means you should bet YES on features that you think make Manifold more likely to see this project as benefitting the community, and bet NO on answers that you think they won't care about. (Given that I have limited development time and any time spent on one feature trades off against another, you actually want to bet on "how useful is this feature relative to how hard it would be to add?".)

Any answer that is a duplicate of an existing answer, or that I had already implemented before submission, will resolve N/A. Feel free to submit variants on existing answers if you think the difference is relevant.