Replies: 5 comments 9 replies
-
How about SigWeb? |
Beta Was this translation helpful? Give feedback.
-
Although I could live with a repo named "signify-browser-extension", I don't think a browser extension with that name is going to go over well. I think we need a more interesting name for the listing in the extension catalog. I could see the name "Signify" as that name, or "Polaris" or "Crux" or whatever -- but not "Signify Browser Extension". |
Beta Was this translation helpful? Give feedback.
-
Since the wallet is like a utility on a belt (aka Batman's belt) how about the name "Zeta", the latinized version of the largest star in Orion's belt, Alnitak? No extension exists with that name:
|
Beta Was this translation helpful? Give feedback.
-
The name we use for the repo does not have to match the name of the published app, right? Leaving the name of the repo alone makes it really clear for people looking at the WoT org what this repo does. |
Beta Was this translation helpful? Give feedback.
-
Given the responses, we will keep THE REPO NAME as "signify-browser-extension" and I will start a new poll for the extension name as seen by the extension catalogs. We can revisit this repo name later with another poll after we settle on a public facing extension name. |
Beta Was this translation helpful? Give feedback.
-
This open source project provides the KERI community a signify browser extension for authentication. Users will use the extension to securely leverage Signify+Keria to do simple management of AIDs and their associated keys and ACDCs — just enough to establish trust with websites.
The goal is for the extension to be available in the Chrome extension and Firefox extension catalogs.
This "authX" feature set is at the heart of what is called a "wallet" in our industry. However, in the minds of many people, "wallet" is a much bigger term. This extension intentionally has a much more limited scope, to make security audits, etc. easier.
7 votes ·
Beta Was this translation helpful? Give feedback.
All reactions