Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

alias sorting #27

Open
straef opened this issue May 9, 2022 · 2 comments
Open

alias sorting #27

straef opened this issue May 9, 2022 · 2 comments

Comments

@straef
Copy link

straef commented May 9, 2022

#3 refers to a feature of recalling the most recently generated alias. how is this done?

using firefox extension and the alias i just created in the extension is not shown in the top 10 aliases that are loaded when viewing extensions tab. i have to click load more.

i see that there are several sorting options for aliases, is this referring to those?


related feedback:

several sorting options seem redundant. ie "local part" and "email". i am guessing email would technically also compare the domain as well, but is this necessary? are people making an identical local part for multiple domains available with the service? if so, were they to select the "local part" sort option, what would determine the order of the aliases?

i cannot discern how aliases are ordered when a sort method that evaluates to the same result for multiple aliases. for example when "active" is selected as the sort method, with multiple active aliases, the list does not seem to order them based on any of the following: activity (an email being forwarded or sent), creation, local part, or "updated" (what does this mean?). similarly when i select to sort by domain, since all my aliases use the same domain, i cannot discern any logic to the resulting order. i have not paid attention enough to even determine if it is consistent across uses. it seems to be stable within a browser session.

all that to say that even if sorting is the intended method of helping retrieve the most recently created alias, it would be nice if a "last created" button or other shortcut was available so that any sort order could be used without losing the ability to easily recall last created. for example i might make an alias for a function that i use often and need to be able to quickly reference that alias, maybe as a address that is shared for business contacts, sorting to to keep that on top will eventually eliminate the possibility that new aliases will appear in the top 10. and vice versa.

methods to resolve this could include the ability to pin or favorite aliases making them appear at the top of the list irrespective of the sort. an setting to always show last created alias at the top of the list. a button to copy the last created alias, probably next to the "+" button.

@willbrowningme
Copy link
Member

Sorry for the late response. The ability to recall the latest generated alias was removed when I updated the browser extension to display all aliases since by default aliases are sorted by most recent first.

You are correct sorting by local part and email is kind of redudant, email will compare the domain as well as you say. If they were to select local part then it would simply be sorted like so:

apple@johndoe.anonaddy.com
apple@example.com
apple@johndoe.anonaddy.me
ebay@example.com

and so on...

At the moment there is no other logic when sorting by say "active" or "domain" as that is the only search criteria. Perhaps I should update it so that it is sorted by active AND most recently created (I would have expected this to be default behaviour but apparently not).

I agree, in the next update I'll bring back the "last created" option so that any sort option can be used.

Thanks for the feedback and suggestions.

@willbrowningme
Copy link
Member

I've fixed the sort issue by adding a secondary sortBy latest first for when you sort by "active" etc.

I'll see if I can add back the last created or alias pinning shortly.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants