pull down to refresh
10 sats \ 5 replies \ @BlueSlime 23 Apr 2022 \ parent \ on: Daily discussion thread
I just did the same as well. I thought there was a mandatory minimum, but both posts went through with 0 sats. Now I can't boost. May just delete and repost later.
Boost is not necessary. That's why it's in the 'options' panel. Is that unclear?
reply
This language pops up...
must be at least 1000
...and it goes red. Unless you remove it completely. Kind of non-standard, or just oddly subjective UX, IMO.
I couldn't reason about why the choice would be from the set
{0, 1000, 1001, 1002, ...}. I would have expected any positive integer if it was actually optional.reply
Hmmm I can see why that'd be confusing. I'm just not sure how to design it otherwise. Any ideas?
reply
...right now, you kind of have like a Schrödinger-cat equivalent of a None/Zero.
Maybe subtle change to the form validation logic:
Current:
- {Negative Integer} -> Red ->
"must be at least 1000" - {None} -> Yellow -> lets you post
- {0, ..., 999} -> Red ->
"must be at least 1000" - {1000, ...} -> Yellow -> lets you post
Proposed:
- {Negative Integer} -> Red ->
"must be 0 or at least 1000" - {None, 0} -> Yellow -> lets you post
- {1, ..., 999} -> Red ->
"must be 0 or at least 1000" - {1000, ...} -> Yellow -> lets you post
reply
Ah I get it! I just need to say 0 is allowed!
reply