Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

Allow using the network icon as avatar or something similar #797

Closed
michaelthecryptoguy opened this issue Dec 20, 2018 · 10 comments
Closed
Labels
Priority: Low The issue or pull request will not affect most users.

Comments

@michaelthecryptoguy
Copy link

Feature Request

Solution i'd like
Instead of an avatar, place the ARK Tokens logo or a custom picture.

@zillionn
Copy link
Contributor

Yes, you already have the logo of the network, you should use that one for the profiles.

@j-a-m-l
Copy link
Contributor

j-a-m-l commented Dec 20, 2018

You could have more than 1 profile for the same network. For instance, I could have 1 profile for my company's ARKs, other for my personal ARKs and other for my retirements.

So, I don't see any reason to remove them.

An optio to upload a custom image would be implemented later.

@j-a-m-l j-a-m-l closed this as completed Dec 20, 2018
@zillionn
Copy link
Contributor

@j-a-m-l In that case you'll use different profile names not avatars. IMO the avatar should be the network logo. Every bridged chain will add their logo and it'll be 100 times easier to distinguish networks than some random avatars.

@zillionn
Copy link
Contributor

Or at least make the default avatar the network logo.

@j-a-m-l
Copy link
Contributor

j-a-m-l commented Dec 20, 2018

We are thinking about several alternatives:

  1. Using the first character of the profile name as the avatar
  2. Custom avatars

Depending on how we implement option 1 and 2, we might have a way to choose the network as avatar too, although, as I explained, the problem with that is having several profiles for the same network.

A solution would be adding the token circle that is now on the wallets to the profile.

@j-a-m-l j-a-m-l reopened this Dec 20, 2018
@zillionn
Copy link
Contributor

I would really love to be able to use the network logo as avatar.

@j-a-m-l j-a-m-l changed the title Remove Human Profile Avatars Allow using the network icon as avatar or something similar Dec 20, 2018
@j-a-m-l
Copy link
Contributor

j-a-m-l commented Dec 20, 2018

OK, I've renamed the issue to make it clear what could be implemented.

@doubled1c3
Copy link

doubled1c3 commented Dec 29, 2018

I think the issue that is attempting to show through here is a "profile" is tied to exactly one network. However, as the profile is a person or business, that person or business may be using multiple networks. This is why the profiles as people aren't making too much sense as it stands now. It makes no sense to make a "Bill" ARK profile, a Bill DARK profile, and a Bill PERSONA profile. They are all Bill.

Profiles are useful and important though, and should remain. In desktop wallet, you may create a profile "Bill" and another "Bill's Business #1" and "Bill's Business #2", or if it's a shared PC, would create "Dad, Mom, Sister, Brother" profiles.

The architecture needs to be changed such that you do not specify a network when creating a profile at all. Once inside the profile, you would specify one or multiple networks, and each network would have a cluster of wallets as we already see today.

Then you would have profile "Bill," who might have both ARK and DARK networks inside of Bill's profile, and Bill's Business, who might have ARK and MARACHAIN network with a separate cluster of wallets.

At that point the profile concepts make sense, the networks therein are clustered according to the profile, and switching between profiles makes sense for the user's brain.

@faustbrian faustbrian added Priority: Low The issue or pull request will not affect most users. and removed Priority: Low labels Jan 4, 2019
@luciorubeens
Copy link
Contributor

Closed via #947

@ghost
Copy link

ghost commented May 29, 2019

This issue has been closed. If you wish to re-open it please provide additional information.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Priority: Low The issue or pull request will not affect most users.
Projects
None yet
Development

No branches or pull requests

6 participants