Live data from Hacker News

1Password for SSH and Git (Beta)

developer.1password.com

201–210 of 406 posts

Re: 1Password for SSH and Git (Beta)

#201

Earlier quoted context omitted.

Memory is a precious resource. Every additional Electron app that’s running increases the likelihood that your system will have to swap, and then it will feel like a a turtle in a tarpit. Also, there’s some concern that continuous swapping prematurely ages SSDs, reducing the overall lifetime of laptops. The modern trend is to solder storage chips directly to the main board, making them difficult to replace.

Memory is not a precious resource, this narrative needs to die an unceremonious death. This isn't the 90s, we live in the future.

Of course it is a precious resource. Any bytes wasted by bloated electron apps are bytes that your kernel cannot use for disk caches.

Pretty much every file I use daily is always in my disk cache, but they won't all fit there if I run a bunch of electron apps.

Re: 1Password for SSH and Git (Beta)

#202
post #195

Earlier quoted context omitted.

SSH keys have both a private and a public file. The private file is multi-line text. I don't like putting the private key in the notes field, because its name is still "notes" (but I'd prefer the label be the key's file name), it's actually markdown formatted text, not literal text, and what if I still want to write a note, but I've already used the notes field for the key? HTTPS certificates including multiple certi…

Maybe a solution would be to get inspiration from keepass(xc) attachement's feature. It allows you to save abitrary files as attachement to an entry (btw this is how keepassxc does ssh key managment). Other keys/ certs (like HTTPS certs) would be supported such a feature too. The 'only' downside is the comparatively high increase in database size for the hoster.

1Password already has this…

Re: 1Password for SSH and Git (Beta)

#203

Earlier quoted context omitted.

Memory is not a precious resource, this narrative needs to die an unceremonious death. This isn't the 90s, we live in the future.

As someone who has to occasionally unstick stuck systems by way of `echo 3 > /proc/sys/vm/drop_caches` because memory management in the real world doesn't work the way the people who write condescending sites like linuxatemyram.com say it does: Memory most definitely is a previous resource.

What’s funny about this comment is how detached from reality it is.

If you round, approximately zero users of Electron apps know how to do what you’re talking about, and yet they continue to successfully use Electron apps across a variety of platforms.

The fact that you have to finely manage your system’s memory is a you thing, not an Electron thing. The two are entirely orthogonal.

Memory is not a precious resource, no matter how much you want to live in a world where your obsessive compulsion to manage it is reasonable.

Re: 1Password for SSH and Git (Beta)

#204
post #201

Earlier quoted context omitted.

Memory is not a precious resource, this narrative needs to die an unceremonious death. This isn't the 90s, we live in the future.

Of course it is a precious resource. Any bytes wasted by bloated electron apps are bytes that your kernel cannot use for disk caches. Pretty much every file I use daily is always in my disk cache, but they won't all fit there if I run a bunch of electron apps.

False choice; you have memory for both Electron apps and your kernel for disk caching.

Besides, with SSDs and NVMe your experience loading data from disk is plenty fast. Again, this is the future; I/O isn’t the bottleneck it once was.

Re: 1Password for SSH and Git (Beta)

#205
post #30

And yet we still can't use the keyboard to navigate to the `Generate Password` button like we could in every version of 1Password before the current one.

I work at 1Password. Could you tell me a little more about this? I tested this in the latest version of 1Password 8 and when I'm creating or editing a password, I see a "Generate Password" button pop up beneath the password field. I can access it by either pressing the down arrow or tab. Does this not work on your end?

Re: 1Password for SSH and Git (Beta)

#207

Earlier quoted context omitted.

Frankly I'd rather pay for 1Password sync that have Dropbox installed on my machines anymore with all the low-level hackery and product shenanigans they've pulled as the internal pressure to "innovate" and move up market has taken hold. I'm also worried about 1Password in the long-term with this recent VC investment which likely will create the same kind of pressures, but for now they still have the best product in t…

That's reasonable if you don't already pay for any cloud synchronized storage solution. But many of us already pay for cloud file syncing across our devices and 1Password's previous solution worked just fine. Having it removed so they can charge their SaaS fees feels like a blatant worsening of the product.

To be fair I'm not familiar with the dropbox+1pass combo solution you're referring to, but I imagine that the people using that solution are in the minority and that by focusing on one unified solution and not spending time supporting an old one probably provides net positive experiences across their product.

I kind of agree that if it works and it's in place just leave it be, but if it needs maintenance time, support time, and even development time as the product evolves then I can see the "business folks" pushing for the removal of those features so the team can focus on what more people are using.

Re: 1Password for SSH and Git (Beta)

#208

A huge problematic deficiency of 1Password is that it lacks literal multi-line text field types. The items in its database let you define custom fields for them, but there is no literal multi line text field. There's a "File" type, but you can't simply define fields with multi-line text values. However, every item has exactly one built-in "notes" field, but that's actually styled markdown text. And you only get one.…

Could you share a little bit about what you'd want to use this for? (I'm part of the 1Password design team)

It would be nice if 1Password understood private key + certificate pair, how it is used often for TLS connections.

Re: 1Password for SSH and Git (Beta)

#209

Earlier quoted context omitted.

Please elaborate to those of us who have actually experienced the “swap swamp” within the last year, in the 2020s, and who have enough systems knowledge to properly instrument this stuff. Are you gaslighting us?

Quoted post unavailable.

This is a non-sequitur. And you haven't actually substantively rebutted my claim (or anyone else's here, for that matter).

Re: 1Password for SSH and Git (Beta)

#210
post #201

Earlier quoted context omitted.

Of course it is a precious resource. Any bytes wasted by bloated electron apps are bytes that your kernel cannot use for disk caches. Pretty much every file I use daily is always in my disk cache, but they won't all fit there if I run a bunch of electron apps.

False choice; you have memory for both Electron apps and your kernel for disk caching. Besides, with SSDs and NVMe your experience loading data from disk is plenty fast. Again, this is the future; I/O isn’t the bottleneck it once was.

Just because you haven't personally experienced this problem doesn't mean that many others have not. The experience of others is just as valuable as your personal experience, and to denigrate the experiences of others demonstrates a lack of empathy and understanding. Not everyone has an SSD, and not everyone has more than 8GB memory in their laptops. Many laptop manufacturers (including Apple) continue to sell lower-memory systems in droves; and there is a widely-installed base of older computers dating 5 years and even longer.
Post reply on HN