* Show majority stake on comments
* Darken comment input text
* Fix old FR comments displayed in general section
* Refactor feed comments and bets into files
* Only allow user to comment on most recent bet
* Fix overlapping sign in to comment
* Only calculate current users bets once
* Minor tweaks & is betting @ prob
* Show user bets on their profile
* Add an alert for current users
* Replace `/portfolio` with `/Austin?tab=Bets`
* Replace `/Austin?tab=Bets` with `/Austin/bets`
* Use replaceState for better browser history
* Remove two console.logs
* Note a bug
* Fix path
* Write in description of why we're doing this
* Get answer outcome from comment
* Avoid db call if possible
* Include general comments note in comment emails
* Send market-comment on general comment
* Add activity page. Copy explore page into home
* Update navbar with activity. Show explore instead if signed out.
* Move category selector into contract search
* Make algolia filter by category
* Default tag page to all filter
* Add bet buttons to embed
- Make only title link to market
- Prevent avatar / username from being clicked on
* refactor: remove extra elem, de-indent
* adjust embed info row styles
* make bet panel smaller
* make sell panel smaller
* Link to comments & highlight comment
* Copy link, show toast and fade bg
* Remove unused imports
* Standardize link copied toast
* Add linking to answer comment threads
* Refactor open answers component, use indigo highlight
* Distinguish chosen answer a bit more
Pros:
- Better emphasizes "mana"
- Visually pleasing
- Visually distinct (acts as an icon)
- Single character
Cons
- Harder to correctly type (but users can just do m1234 for shorthand)
* Add /private-users/apiKey to DB
* Add field to edit API key on profile
* Move API key to bottom of profile page
Austin thinks this is better since most people don't care about it.
* randomString: generate a securely random string.
Also, support lengths > 12 in case that's ever needed.
This is used in at least one case (creating device tokens for users)
where it seems important that the output is unpredictable.
* Try harder to create unique usernames.
The previous version added 16 bits of entropy to the username, which
isn't all that much. Due to the birthday paradox, it would be enough to
create ~256 users with the same prefix to get a collision.
Trying that would probably fail later on, and not create security
issues... but it just seems better to be on the safe side here.
