simplex-chat / simplex-chat/simplex-chat

Giving a name to my long-term SimpleX address (and multiple long-term ones needed)

Open
#3,194 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement ui
Dominant language
Haskell
Stars
19.5k
Forks
1.4k
Avg merge
1d 20h
Merged PRs (30d)
71

Description

Time ago I asked the possibility to have multiple long-term addresses remained today without any implementation.

However I have the need to rename my long-term address to know from which "channel" a connection request comes.

Just adding a name field, that I can fill like "Job", "University", "Yoga group", "Jennifer' birthday party", etc.

Since long-term addresses can be trashed exactly like disposable ones, the advantage I get is that I can use them multiple times before I trash them. Useful for the suddenly organized parties, to publish a job advertisement, or any occasion that needs to combine the multiple usage with the ability to throw it away when no longer needed.

I hope the multiple long-term addresses will come too in the next SimpleX versions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the existing long-term-address creation, display, and trash flows, then determine how naming and multiple reusable addresses would fit across the clients; done means users can distinguish, reuse, and remove multiple named long-term addresses.

Written by the indexing model from the issue text.

Assessment

Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.