LBRYCommunity/lbry-desktop

Fork 0

Meaningfully Styled URLs #2135

New issue

Open

opened 2018-12-05 06:04:53 +01:00 by QuirkyRobots · 9 comments

QuirkyRobots commented

2018-12-05 06:04:53 +01:00

(Migrated from github.com)

The channel part of a URL (not shown) could also have a slight colour adjustment, such as a LBRY shade of green, to help a user identify that part and help make the URL more meaningful.

More crazy ideas from me, but what would the world be without crazy people! 😭

Normal Style: Looks messy and confusing.

Meaningful Style: Looks pleasing and informative.

As someone that is very UX/UI focused, I thought it would be a good idea to have the different parts of the URL more apparent than others. The permanent part of the URL is not something that needs to be seen. Making it less obvious with an opacity reduction would make the whole URL look more attractive and more obvious what it points to. The channel part of a URL (not shown) could also have a slight colour adjustment, such as a LBRY shade of green, to help a user identify that part and help make the URL more meaningful. More crazy ideas from me, but what would the world be without crazy people! 😭 **Normal Style**: Looks messy and confusing. ![lbryapp2](https://user-images.githubusercontent.com/29914179/49491691-f72a4b00-f8a0-11e8-8851-1904fb0507ec.jpg) **Meaningful Style**: Looks pleasing and informative. ![lbryapp1](https://user-images.githubusercontent.com/29914179/49491124-bb8e8180-f89e-11e8-8c1a-00ef54eb5740.jpg)

neb-b commented

2018-12-05 06:07:40 +01:00

(Migrated from github.com)

@Invariant-Change This is a great idea!

❤️ 1

tzarebczan commented

2018-12-05 06:07:46 +01:00

(Migrated from github.com)

The permanent part is necessary because of how vanity URLs work. I don't think not shading it is the answer. This will be solved with https://github.com/lbryio/lbry/issues/958
We aren't showing channel URLs on most claims do to some bugs on how they are resolved if there are duplicates.

1) The permanent part is necessary because of how vanity URLs work. I don't think not shading it is the answer. This will be solved with https://github.com/lbryio/lbry/issues/958 2) We aren't showing channel URLs on most claims do to some bugs on how they are resolved if there are duplicates.

👍 1

QuirkyRobots commented

2018-12-05 06:15:53 +01:00

(Migrated from github.com)

Yes, they are necessary, but they are also ugly and get in the way of the useful vanity URL. In this example, you can still see the permanent URL and it's still fully functional, but the less obvious style of it gives the whole URL more meaning and aesthetics. Visual ergonomics! My crazy creative mind loves it. lol

neb-b commented

2018-12-05 06:21:24 +01:00

(Migrated from github.com)

~~I think we should still show the full url. If we show the vanity url and a user tries to copy that, the person they share it wil may be directed to a different claim.~~

I misunderstood that issue. I still think this would be a good change. It puts more emphasis on the name, no one cares about the claim id

It's also common in browsers:
screen shot 2018-12-05 at 12 21 03 am

~I think we should still show the full url. If we show the vanity url and a user tries to copy that, the person they share it wil may be directed to a different claim.~ I misunderstood that issue. I still think this would be a good change. It puts more emphasis on the name, no one cares about the claim id It's also common in browsers: <img width="347" alt="screen shot 2018-12-05 at 12 21 03 am" src="https://user-images.githubusercontent.com/16882830/49491827-b17b6d00-f823-11e8-81bf-f963a9b3f5c4.png">

👍 1

QuirkyRobots commented

2018-12-05 06:21:26 +01:00

(Migrated from github.com)

I'm trying to digest how a URL will look with the new approach on https://github.com/lbryio/lbry/issues/958 so can't comment on that part atm. I might need another coffee!

kauffj commented

2018-12-05 15:40:37 +01:00

(Migrated from github.com)

Good change. We could consider de-emphasizing the lbry:// portion as well.

Post https://github.com/lbryio/lbry/issues/958, when the claim ids should only be a few characters, we should consider showing them again.

Good change. We could consider de-emphasizing the `lbry://` portion as well. Post https://github.com/lbryio/lbry/issues/958, when the claim ids should only be a few characters, we should consider showing them again.

tzarebczan commented

2019-07-18 19:38:11 +02:00

(Migrated from github.com)

@Invariant-Change what else should we do on the current version to improve this? If it looks good, we can close it.

QuirkyRobots commented

2019-07-19 09:03:32 +02:00

(Migrated from github.com)

It's looking good how it is, but would be a little better with end junk part being greyed out.

It's looking good how it is, but would be a little better with end junk part being greyed out. ![image](https://user-images.githubusercontent.com/29914179/61515911-14ceae00-aa47-11e9-969f-b6a57edd8386.png)

neb-b commented

2019-07-19 17:58:00 +02:00

(Migrated from github.com)

Thanks for updating this. I agree

On Fri, Jul 19, 2019 at 3:03 AM Electron - Mark Firth <
notifications@github.com> wrote:

It's looking good how it is, but would be a little better with end junk
part being greyed out.

[image: image]
https://user-images.githubusercontent.com/29914179/61515911-14ceae00-aa47-11e9-969f-b6a57edd8386.png

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-desktop/issues/2135?email_source=notifications&email_token=AEAZZDSD3ZWGCLK26O7GNL3QAFRMRA5CNFSM4GIIBYR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KY3RA#issuecomment-513117636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEAZZDRM5VFQFQ73MWR6PP3QAFRMRANCNFSM4GIIBYRQ
.

--
Sean Yesmunt
Engineer for lbry.com

Thanks for updating this. I agree On Fri, Jul 19, 2019 at 3:03 AM Electron - Mark Firth < notifications@github.com> wrote: > It's looking good how it is, but would be a little better with end junk > part being greyed out. > > [image: image] > <https://user-images.githubusercontent.com/29914179/61515911-14ceae00-aa47-11e9-969f-b6a57edd8386.png> > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-desktop/issues/2135?email_source=notifications&email_token=AEAZZDSD3ZWGCLK26O7GNL3QAFRMRA5CNFSM4GIIBYR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KY3RA#issuecomment-513117636>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AEAZZDRM5VFQFQ73MWR6PP3QAFRMRANCNFSM4GIIBYRQ> > . > -- Sean Yesmunt Engineer for lbry.com