jaimecgomezz / rofi-1p Goto Github PK

Description

The current performance depends entirely on the network, as every step required to access a given field needs to retrieve information from the 1password database, as described:

1. Retrieve the complete list of available items (logins, identities, credit cards, notes, etc)
2. Select an item.
3. Retrieve the item and list all the non-empty fields.
4. Select the required field.
5. Retrieve the item and access the required field.

This flow is unnecessary slow for quite a simple task like copy-pasting your accounts information. It demands a performance boost.

Describe the solution you'd like

The first approach that comes to mind is having a cache system that rofi-1p can query instead of the 1password database every time it needs to access an item information. The characteristics of this cache-like system should be:

• SECURE, accessible ONLY by the account owner.
• Refreshable, so the user can decide whenever the cache needs to be updated.
• Self-destructive, so the user won’t need to manually delete it.
• Simple, so the user won’t notice the difference while using it.

Teachability, documentation, adoption, migration strategy, etc.

It is almost sure the this system will require implementing the gpg encryption.