Publishing - Allow publish even if bid amount doesn't result in vanity takeover #634

New issue

Closed

opened 2017-09-28 00:42:39 +02:00 by tzarebczan · 1 comment

tzarebczan commented

2017-09-28 00:42:39 +02:00

(Migrated from github.com)

The Issue

Breaking out issues discussed (mostly by me) from https://github.com/lbryio/lbry-app/issues/214

Currently, the LBRY publish feature does not allow you to publish to an existing claim name unless you outbid the current claim. I'm pretty sure we want to allow users to do this but need to clearly explain that the content will only be available at the long URL and not the vanity URL.

Steps to reproduce

Go to Publish, type one in URL
Says "A deposit of at least "50000" credits is required to win "one" and Publish is disabled

Expected behaviour

Allow publish at existing claim name without a takeover, but explain this to the user

Actual behaviour

Cannot publish without takeover

System Configuration

LBRY Daemon version: 0.16.1
LBRY App version: 0.16.
LBRY Installation ID:
Operating system: Windows

Anything Else

Screenshots

## The Issue Breaking out issues discussed (mostly by me) from https://github.com/lbryio/lbry-app/issues/214 Currently, the LBRY publish feature does not allow you to publish to an existing claim name unless you outbid the current claim. I'm pretty sure we want to allow users to do this but need to clearly explain that the content will only be available at the long URL and not the vanity URL. ### Steps to reproduce 1. Go to Publish, type one in URL 2. Says "A deposit of at least "50000" credits is required to win "one" and Publish is disabled ### Expected behaviour Allow publish at existing claim name without a takeover, but explain this to the user ### Actual behaviour Cannot publish without takeover ## System Configuration   - LBRY Daemon version: 0.16.1 - LBRY App version: 0.16. - LBRY Installation ID: - Operating system: Windows ## Anything Else  ## Screenshots

tzarebczan commented

2018-06-28 20:16:59 +02:00

(Migrated from github.com)

This is fixed in the redesign