Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Integration between Linux app and Snap Firefox
Some days ago it was released the support for Native Messaging (still experimental) with Snap Firefox. I checked, but the integration between Linux app and Snap Firefox still doesn't work. I was wondering if the integration uses Native Messaging or other way to implement, and if it is using other way, if it could be ported to use Native Messaging, so Linux app could work with Snap Firefox. We are discussing this matter here 1Password Version: 8.9.0~1.BETA Extension Version: 2.3.7 OS Version: Ubuntu Kinetic Browser:_ Firefox
New item login field already populated
Hi, When I create a new item in the Linux, Android and iOS 1Password apps, the login field is already populated with an email address and focus is set on the password field. How to change that? I would like it to be empty. It is especially annoying because in my case, it is filled with a an email address I am not using that often. This change of behavior seems to be relatively recent. Thanks for your help. Spacehog
1Password Shortcuts on Wayland
1Password is an application that works very well when users can invoke it from anywhere. Quick Access in particular is a feature that is meant to be invoked from anywhere on your desktop. However, as many of you know, the Wayland developers made a deliberate choice to not allow applications to set global shortcuts. To my knowledge, all Wayland implementations have continued to honor this choice. The reasoning is valid, though: global shortcuts make keyloggers trivial. 1Password can run as a native Wayland application, and defaults to XWayland. This, however, does not help since the primary desktop environment is itself Wayland. For a variety of reasons, we have provided command line options for several of the most useful 1Password commands. In this article, I'll describe how to use those options to set up global shortcuts for 1Password with both Gnome Shell and Sway. It is, fortunately, very easy. Gnome Shell For this example, I'm running Gnome Shell 40.4.0, Wayland mode, on Fedora Core 34. Start by finding Keyboard > Customize Shortcuts in your Settings application. Next, select Customize Shortcuts Your list of custom shortcuts may start empty, but you will want to get to something like this: Press the + button at the bottom to create a new shortcut, and you'll get a screen like this: As you create each shortcut, name each one in a way that makes sense to you. In the Command field, you will write a trivial script that invokes 1Password with the option that you want. Once you have created that invocation, set the keyboard shortcut as you desire. I recommend multiple key bindings that all work together. The following is the 1Password defaults set on other platforms, and on XOrg-based displays. Name Command Shortcut Open or Toggle 1Password 1password --toggle Ctrl + p Lock 1Password 1password --lock Ctrl + Shift + L Open Quick Access 1password --quick-access Ctrl + Shift + Space note: there is no default for Open or Toggle 1Password, so I made something up. Sway Sway does not have a GUI configurator, but instead does everything in the configuration file at ~/.config/sway/config . Fortunately, this is very easy to set up: bindsym Ctrl+Shift+l 1password --lock byndsym Ctrl+Shift+space exec 1password --quick-access KDE Plasma coming soon
Feature Request: Show Original Contributor of Items in Shared Family Vaults
Summary Please add a built-in way to display who originally created or contributed an item to a shared vault in 1Password Family. Problem In shared family vaults, it is currently not possible to see who an item originally belongs to once it has been shared. This makes it unclear who owns a specific account, even though the item is visible to everyone in the family. As a workaround, we manually add tags with the name of the person who created or contributed the item. This allows sorting and filtering by owner, but it is manual, error-prone, and easy to forget. Proposed Feature Display non-editable metadata such as: “Contributed by: Name” or “Original owner: Name” This information should remain visible in the item details after sharing or moving an item into a shared family vault. Benefit This makes it easy to understand who an account actually belongs to, even when it is shared for convenience. It improves clarity in family vaults, avoids confusion, and removes the need for manual tagging. Reference Apple Passwords already shows this information for shared items using labels like “Contributed by: Name”, which provides clear ownership at a glance.Support for immutable linux (Bazzite, etc)
1password is rough to use on immutable fedora (Bazzite, Aurora, etc), since flatpak doesn't let 1password communicate with browser, use SSH, or fingerprint scanner. I'm not fully sure what solution would be since AppImage is depreciated. Maybe flatpak permissions config that would let 1password talk to browser?
Support for Imput's Helium Browser
Hiya! I'm an avid 1Password user and I utilize every possible corner of it. BUT there's a certain issue that I'm facing when I'm using it with unsupported browsers. Mainly, Helium Browser (https://github.com/imputnet/helium) which includes unbiased privacy at no compromise to webpage functionality isn't supported. This is an issue because there's no other browser I'd use. The problems that arise are apparent on all platforms, like: Manual addition in the 1Password app on macOS (which, lately, seems to spaz out when using it with the extension) Inability to use with the system app on Windows which inconveniences users by making them log into their vault twice (which, if I guarantee, many have a complex password for and can't bore themselves typing it out multiple times per session) Broken behaviour on Linux, where even with the custom browser config it still can't unlock the vault if it's unlocked on the system. No, I wasn't running the Flatpak version. IMHO 1Password is better than the competition in terms of UX, but seeing my daily driver struggle with that with no way to fix without resorting to this is awful.
