mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 22:25:55 +03:00
[GH-ISSUE #293] [Feature Request] Option to transfer ownership of the alias to another AnonAddy user #248
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#248
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @w3lld0ne on GitHub (May 26, 2022).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/293
There are some sites that don't allow you to change email directly. However, with AnonAddy we are able to change the recipient of the alias whenever we want, that's great! The only thing that may be improved is to allow even more freedom in what we can do with alias, that is, ownership transfer.
So my friend, for example, can receive full control over that-randomly-generated-email@anonaddy.me and do whatever he wants with both the alias and the site alias is linked to.
P.S. Not sure whether to allow the transfer for aliases tied to your username or custom domain, but at least shared domain is a perfect place to do that.
P.P.S. There can also be a situation where one paid user constantly registers aliases on paid-only shared domains and gives them to free accounts. Well I think we can apply a restriction to only transfer ownership of the aliases to accounts of the same level (or above) as yours (paid to paid only, free to free/paid etc.).
P.P.P.S. There is one possible drawback: some sites may blacklist AnonAddy addresses completely for that.
@willbrowningme commented on GitHub (Jun 16, 2022):
Thanks for the suggestion, this is already on the roadmap here - https://github.com/anonaddy/anonaddy/projects/1#card-78194939
I'll see if I can add this in the near future, closing this issue since it is already on the roadmap.
@w3lld0ne commented on GitHub (Jul 13, 2022):
That's ok, but one point to note is that you're talking there about custom domains only (actually I even think your idea is about transferring whole domains with all their aliases at once, isn't it?), while this suggestion mainly proposes the feature on the shared domains on a single item/alias level.