Show permanent url for published items #228

Closed
opened 2017-06-12 04:37:49 +02:00 by tzarebczan · 1 comment
tzarebczan commented 2017-06-12 04:37:49 +02:00 (Migrated from github.com)

More of a feature request, but much needed IMHO. We should show the claimid, which allows for permanent resolution, somewhere on the published page or on the claimed item.

The Issue

You'd need to look up the claimid manually using cli.

Steps to reproduce

  1. n/a

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on Slack at https://slack.lbry.io --> More of a feature request, but much needed IMHO. We should show the claimid, which allows for permanent resolution, somewhere on the published page or on the claimed item. ## The Issue You'd need to look up the claimid manually using cli. ### Steps to reproduce 1. n/a 2. 3. ### Expected behaviour Tell us what should happen ### Actual behaviour Tell us what happens instead ## System Configuration <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> <!-- For the daemon, run: curl 'http://localhost:5279/lbryapi' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here -->
6ea86b96 commented 2017-06-23 09:00:48 +02:00 (Migrated from github.com)

Fixed (I think) in #227

Fixed (I think) in #227
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#228
No description provided.