.tech remaining items #158

New issue

Closed

opened 2018-09-27 17:19:50 +02:00 by alyssaoc · 4 comments

alyssaoc commented

2018-09-27 17:19:50 +02:00

(Migrated from github.com)

Differentiate between the before/after view when completing examples
Explain significance of the action
Human-friendly URL in the tip example's URL bar

Show lbry://name#claim_id where name is the claim's name. This should be "cached" and referenced when show result is called.

- [x] Differentiate between the before/after view when completing examples - [x] Explain significance of the action - [x] Human-friendly URL in the tip example's URL bar Show `lbry://name#claim_id` where `name` is the claim's name. This should be "cached" and referenced when `show result` is called.

NetOpWibby commented

2018-09-27 20:05:01 +02:00

(Migrated from github.com)

Message for self
~~Tip example loads indefinitely~~
Last item on the list may not be possible due to how wallet_send works. Actually, pretty sure it's not possible.

_Message for self_ ~Tip example loads indefinitely~ Last item on the list may not be possible due to how `wallet_send` works. Actually, pretty sure it's not possible.

NetOpWibby commented

2018-09-27 23:05:16 +02:00

(Migrated from github.com)

@kauffj ^

kauffj commented

2018-09-27 23:46:55 +02:00

(Migrated from github.com)

@NetOperatorWibby it's true that you need an address or claim id when calling wallet_send (though maybe it should support full URLs cough @eukreign). But I don't understand why we can't show a more readable URL in the bar itself.

@NetOperatorWibby it's true that you need an address or claim id when calling `wallet_send` (though maybe it should support full URLs *cough* @eukreign). But I don't understand why we can't show a more readable URL in the bar itself.

👍 1

NetOpWibby commented

2018-09-28 03:32:48 +02:00

(Migrated from github.com)

@kauffj Would it make sense to do that? Wouldn’t the end user expect to be able to use another human-readable name to tip?

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.tech#158

No description provided.