Explore extension identifier with keepassxc.org

[kkapsner]

To get proper official support from keepassxc it would be better if the extension identifier would be keepassxc-mail@keepassxc.org

Todo:

• check id change in ATN
• check id change in application
• get permission from keepassxc to use that domain

[kkapsner]

references:

• Add Thunderbird native messaging to browser integration settings keepassxreboot/keepassxc#7838
• Add support for Thunderbird keepassxreboot/keepassxc#9706

[kkapsner]

@varjolintu: who can give the official go for me to use this domain despite me not being associated to keepassxc.org?
Or other question: how can I (or this project) get officially associated and what consequences would it have?

[kkapsner]

@jobisoft: do you know if I can change the extension identifier in ATN? Or do I have to try it with a "bogus" extension?

[jobisoft]

You cannot change the id of an add-on after it has been published. You can only sunset the old one and release a new one. How did you end up with this id, which uses a domain you have no control over? Did you pick it on your own?

[jobisoft]

If this add-on is not officially controled/managed by keypassxc.org, I do not suggest using an id which could indicate otherwise.

Note: Nobody really sees the id.

[kkapsner]

Thanks for the answer. I currently use a domain I have control over. The folks at keepassxc may want to use have a different ID to fully support it in their application (which provides the native messaging proxy).

So your suggestion would be to just leave the old ID as the end user does not see it in Thunderbird.

Let's see what @varjolintu says...

[varjolintu]

It should definitely be keepassxc-mail@keepassxc.org. keepassxreboot/keepassxc#9706 (comment)

[kkapsner]

OK - then do I have the official permission?
Or do you want to create a fork with the changed ID and manage ATN?
What is the plan?

[varjolintu]

There's no need for a fork. Let's just change the id?

[kkapsner]

OK - I see that as an official permission.

[kkapsner]

I think I have an action plan:

• create a new entry at ATN for the new ID
• add an API to transfer the settings from one extension to the other
• update the descriptions of both extensions to clearly communicate which one to use
• create a new version of the old extension with the following functionality
• notify the user about the ID change and the actions that will be performed (and that the user will have to perform)
• use the management API to automatically install the new extension
• transfer settings to new extension
• remove old extension