-
Notifications
You must be signed in to change notification settings - Fork 178
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
Improve orderbook human readability #1330
Comments
To additionally motivate the request: I understand this is but a minor addition, yet JM comes from a place where it's "the hard and complex alternative to samourai and wasabi (eugh)", and any little effort spent in making the experience better for the end users I think would greatly improve its potential adoption. |
Which software does
Agree on this! |
Know what? I wouldn't be able to tell you for sure anymore, I believe it was a notation used by ThunderHub? RTL? Just around plebnet groups? Since my very first few days after experimenting with GUIs, I've always worked with CLI and took up the _ separator for thousands as specific for lightning. I'm okay with any separator obviously, as long as it's monospace and makes the 1234567890 numbers easier on the eyes, after all JM is not about LN 🙂 |
Definitely not RTL, I'm using that myself. |
Confirmed here. Additionally, I have never seen |
Ok you're now making me feel like "the crazy one", I know I picked it up back when I started lurking in plebnet... no matter where it came from though, I'd say a thousands separator, however you want to choose it, would be a welcome addition, no? |
I'd probably agree there. Albeit it's not too important. PRs welcome from anyone on that. |
As someone used to running a LN routing node, I am accustomed to LN notation of 1_234_567 to represent 1234567sats, or 0.01234567BTC. Also, all my accounting script reports are in monospace fonts, easy to pad.
Consider this:
I believe it would be trivial on one side, and on the other, greatly improve the way users can gauge the OB, if:
The text was updated successfully, but these errors were encountered: