Allow markets to be filtered by "closed and not yet resolved".

'allow':1 'close':7 'filter':5 'market':2 'resolv':11 'yet':10

'add':1 'sort/filter':3 'total':5 'trader':6

Add a sort/filter for elasticity, limit orders, and/or some other similar measure

'add':1 'and/or':8 'elast':5 'limit':6 'measur':12 'order':7 'similar':11 'sort/filter':3

Add a "not" option in the search fields, to exclude a certain term.

'add':1 'certain':12 'exclud':10 'field':8 'option':4 'search':7 'term':13

Allow searching with regular expressions.

'allow':1 'express':5 'regular':4 'search':2

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

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.

'copi':16 'copy-past':15 'els':33 'link':26,28 'live':4 'modifi':8 'past':17 'search':10,30 'send':24 'someon':32 'updat':1 'url':3,19 'user':7 'want':22

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

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

Make the "time until close" display update automatically, so there's a live countdown.

'automat':8 'close':5 'countdown':14 'display':6 'live':13 'make':1 'time':3 'updat':7

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

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

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

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

Fix the lag, so that user input is responsive.

'fix':1 'input':7 'lag':3 'respons':9 'user':6

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

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

Retrieving new markets should happen concurrently rather than one at a time.

'concurr':6 'happen':5 'market':3 'new':2 'one':9 'rather':7 'retriev':1 'time':12

Use a market's lastUpdatedTime to determine how frequently it needs to be queried for updates.

'determin':7 'frequent':9 'lastupdatedtim':5 'market':3 'need':11 'queri':14 'updat':16 'use':1

Listen to /bets and get a new probability for any market that was just bet in.

'/bets':3 'bet':15 'get':5 'listen':1 'market':11 'new':7 'probabl':8

When a user places a bet via the search page, use the returned probability to update that market immediately.

'bet':6 'immedi':19 'market':18 'page':10 'place':4 'probabl':14 'return':13 'search':9 'updat':16 'use':11 'user':3 'via':7

Query markets more often if they're near their close date.

'close':10 'date':11 'market':2 'near':8 'often':4 'queri':1 're':7

Get market data from supabase instead of the Manifold API.

'api':10 'data':3 'get':1 'instead':6 'manifold':9 'market':2 'supabas':5

Crawling the full dump of all markets can happen concurrently with other market updates rather than putting them all on hold.

'concurr':10 'crawl':1 'dump':4 'full':3 'happen':9 'hold':21 'market':7,13 'put':17 'rather':15 'updat':14

If a single number is entered into a time/date filter, rather than try to match markets with that exact number (very unlikely), default the other end of the range to the present time.

'default':23 'end':26 'enter':6 'exact':19 'filter':10 'market':16 'match':15 'number':4,20 'present':32 'rang':29 'rather':11 'singl':3 'time':33 'time/date':9 'tri':13 'unlik':22

If a single number is entered into a time/date filter, rather than try to match markets with that exact number (very unlikely), match a small range around that number.

'around':27 'enter':6 'exact':19 'filter':10 'market':16 'match':15,23 'number':4,20,29 'rang':26 'rather':11 'singl':3 'small':25 'time/date':9 'tri':13 'unlik':22

Let a user see their own positions in each market

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

Let a user filter to markets in which they have positions

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

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

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

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

'add':1 'chang':14 'graph':4 'market':12 'recent':15 'row':7 'show':9 'tini':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

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

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

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

'els':6 'everyon':5 'posit':8 'see':4 'way':2

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

Option to have the colored probability display be only in the probability column rather than across the whole table

'across':16 'color':5 'column':13 'display':7 'option':1 'probabl':6,12 'rather':14 'tabl':19 'whole':18

Shift-click on someone's name to go to their profile

'click':3 'go':9 'name':7 'profil':12 'shift':2 'shift-click':1 'someon':5

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

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

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

When the user hovers over a topic, display the total number of markets in that groups

'display':8 'group':16 'hover':4 'market':13 'number':11 'topic':7 'total':10 'user':3

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

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

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

Add a quickbet button where the user just inputs their expected probability, and it calculates the appropriate kelly bet size for them.

'add':1 'appropri':17 'bet':19 'button':4 'calcul':15 'expect':11 'input':9 'kelli':18 'probabl':12 'quickbet':3 'size':20 'user':7

Let users select rows by clicking on them, then perform bulk actions on those rows. (Bet, add to dashboard, add group, etc.)

'action':12 'add':17,20 'bet':16 'bulk':11 'click':6 'dashboard':19 'etc':22 'group':21 'let':1 'perform':10 'row':4,15 'select':3 'user':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

Split saved data between the OPFS and IndexedDB, for faster loading.

'data':3 'faster':10 'indexeddb':8 'load':11 'opf':6 'save':2 'split':1

Stream data retrieval from the OPFS, so it loads in chunks rather than blocking the page for ~500ms.

'500ms':18 'block':14 'chunk':11 'data':2 'load':9 'opf':6 'page':16 'rather':12 'retriev':3 'stream':1

Bug: numeric markets are displayed as though they were regular percentage markets.

'bug':1 'display':5 'market':3,12 'numer':2 'percentag':11 'regular':10 'though':7

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

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

Add an OR conjunction for search terms. (Particularly relevant for groups, but also useful for grey vs. gray and whatnot.)

'add':1 'also':13 'conjunct':4 'gray':18 'grey':16 'group':11 'particular':8 'relev':9 'search':6 'term':7 'use':14 'vs':17 'whatnot':20

Let people link to specific visibility options and sorting order via URL parameters.

'let':1 'link':3 'option':7 'order':10 'paramet':13 'peopl':2 'sort':9 'specif':5 'url':12 'via':11 'visibl':6

Don't sort all markets, just find the ones that would be in the top 200 of the sort.

'200':16 'find':7 'market':5 'one':9 'sort':3,19 'top':15 'would':11

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

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

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

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

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

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

Let people see their profit in each market

'let':1 'market':8 'peopl':2 'profit':5 'see':3

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

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:

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 

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.