-
Notifications
You must be signed in to change notification settings - Fork 570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[.5] Remove The Deprecated Trollbox and Add Support Link to Help Area #455
Comments
I think it's a better idea to remove this tab completely and have a support menu in a more standard location. The support should link a page outside the wallet which can then contain all these links. It doesn't make a lot of sense to have the wallet be the source of truth for this when we have the bitshares.org site. |
Then why not rename this issue to "Remove The Deprecated Trollbox and Add Support Link to Help Area"? Also, if the Help Area is moved out of the Settings Menu and given its own menu like I suggest in issue #436 then these links would be easily found there... or the link to the links as you suggest. |
@wmbutler, can you reopen this under its new title? I could create a new issue but why waste the time when we have already discussed it here? |
I opened the issue here: https://github.com/bitshares/bitshares.github.io/issues/109 |
you plan to run a support team too @wmbutler ? |
I would recommend moving Support to the bottom of the list or even set off by a visual separator like Switch Accounts. |
About the window formerly known as the trollbox ... I suggest you consider re-purposing it instead to make a more personalized wallet experience. If I had a personal list of coin pairs that I wanted to watch, they could go here. |
@btsfav that's not in my immediate plans, although the thought has crossed my mind. My point here was that we don't need to have every support option available in the wallet. Rather, we can direct people to an official support area at bitshares.org. This would also allow anyone who forks the code to change the link to their support methodology. @happyconcepts Coin pairs you want to watch make more sense in a watchlist that would somewhat mirror your portfolio. |
@wmbutler How does that make sense to duplicate my portfolio just to watch it? I am a trader so I look around for trading ideas instead of looking at my portfolio balance.
Please. |
I wasn't suggesting you duplicate your portfolio. I was suggesting that a watchlist has a similar data and potentially a similar layout style making it a good proximity match. You need a lot of the same fields (excluding qty and total value). I think Support at the bottom of the list is a bad idea. We don't want it to get hidden. Support should generally be one of the first items on the menu in my opinion, although I'd be fine placing it below "advanced" |
I gotta say I think it's quite useful to have the links to telegram and discord easily available, so if we're completely removing the chat box we need to put those links somewhere else. |
I agree. That's why I was suggesting a support link that could ultimately go to the bitshares.org/support (but apparently nobody really manages it or at least I don't know who to talk to about it). We also have the help endpoint. This page could display links to telegram and discord:
|
@svk31 The trollbox can be removed not that we have a link from the Help Menu. |
So, we removed the Trollbox from discussion in issues #281 and #289 but now that it is no longer a Trollbox for chatting, but rather a few links to start the chat somewhere else, let's expand its usage to more general useful links and change its name from CHAT to LINKS.
I suggest adding these links as well as the ones already there:
https://bitshares.org/download/
https://cryptofresh.com/
http://bitshares-explorer.io/#/dashboard
https://github.com/bitshares/bitshares-ui/issues
https://coinmarketcap.com/currencies/bitshares/
https://www.btc123.com/market/?symbol=btc38btscny
Anyone else have any good BitShares links?
The text was updated successfully, but these errors were encountered: