Better messaging for takeover amounts on publish page #1940
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#1940
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "publish-overtake-amounts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
More clarity for takeover amounts on claims
Show amount needed to win a claim when editing. Ex: "You have a claim at xxx, for 5 more LBC you will control it"
Changes
I created a new component
NameHelpText
for variable help text under the name input. I movedBidHelpText
under the bid input (which is probably where it should have been in the first place)Before
After
Is "win" the right word here? Maybe control or mention vanity? We use it in a few places...
I'm assuming you'll add this back in :)
I like control. I think we can definitely improve this copy.
Yes. This PR still needs a lot of cleanup.
@tzarebczan I think this is working correctly. Before cleaning up/renaming stuff could you give this a test?
I'm open to adding new messages/re-wording it but I mainly want to see if it's working.
How it should work:
If there is no channel in the uri:
If there are no matches for the short uri or uri with channel:
the messaging about both urls in the last case might be confusing, I think it's enough only to tell them
Any amount will let you control lbry://somerandomclaim
- what do you think?Any amount will let you control lbry://@sean/sean
what if someone takes over @sean?I still haven't run through it, will give that a shot today.
I think it would be ok to only show the short url
@seanyesmunt we also discussed showing vanity top bids when editing claims as part of this PR.
@tzarebczan Added that to the PR description for documentation
@tzarebczan Still working on the exact wording for these messages, but I think this is ready to be tested.
@ -0,0 +28,4 @@
});
nameHelpText = (
<React.Fragment>
Can also use the short syntax (empty tags):
@ -0,0 +28,4 @@
});
nameHelpText = (
<React.Fragment>
Do we need to do something with webpack for that to work? Doesn't seem to build properly when I do that.
If you bid more than 110082.30000001 LBC, when somone navigates to lbry://one it will load your published content.
How can we make it clearer that they can still publish to this URL and have their content at the exact URL? We can't show them the claim id because it's not known until the transaction is created.
(just noticed the misspelling on
someone
)@tzarebczan "However, you can get a longer version of this URL for any price"?
"However, you can get a longer version of this URL for any bid"?
We should also add similar bid help to the channel creation process (this is opened as a separate issue I believe).