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

[feature request] using different nickanme (own) per friend #6643

Open
eqn-group opened this issue Jun 12, 2022 · 3 comments
Open

[feature request] using different nickanme (own) per friend #6643

eqn-group opened this issue Jun 12, 2022 · 3 comments

Comments

@eqn-group
Copy link

Hello,
i request the feature to use different names for each user, so everyone doesn't see my same name on qtox.

thanks

@TimeHastens
Copy link

I think maybe there is a problem with your approach: who should you ask to change the name of a user who is already registered? For example, if there are three people named "Alice", which Alice should you ask to change her name? Or all of them?

I don't think this would be a problem if we could use a unique 'username' for a user and a 'nickname' that could be repeated with others and displayed at the same time. But this might involve users who are already registered, so it's also a bit tricky.

@Green-Sky
Copy link

The underlying toxcore library does not support this. Which makes it not so easy. Also please change the title of the issue to something like "different name per friend" or something 👍

@eqn-group eqn-group changed the title [feature request] easy feature [feature request] using different nickanme (own) per friend Aug 17, 2022
@eqn-group
Copy link
Author

I don't think this would be a problem if we could use a unique 'username' for a user and a 'nickname' that could be repeated with others and displayed at the same time. But this might involve users who are already registered, so it's also a bit tricky.

unique username ? but you can change your tox id to prevent spam.
I am saying, i want to use my different name for each friend, i.e. i want to change my name, not theirs.

I think this can be done by just broadcasting different nick to different friends ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants