You can specify multiple gpg ids when using "pass init":

  pass init [-p sub-folder] user1@example.com user2@example.com

This enables you to control access per subfolder. You can keep your personal passwords in one subfolder and then have various shared subfolders. "pass mv" and "pass cp" will reencrypt with the gpg ids for each subfolder as necessary. You can also "pass init" an existing subfolder to add or remove gpg ids for existing files. See the man page for details [1].

[1] http://git.zx2c4.com/password-store/about/

Thanks for the feedback! ⌘1 is what you want to focus the sidebar, and <Esc> will take you back to your buffer. We're working on some improvements to the View menu.

That works! Thanks! Looking forward to the next round of improvements.

We will soon document all key shortcuts in the wiki on GitHub.

There are quite a few, and they're documented on the wiki[1].

If you find that there's a specific feature missing, please open an issue. All feedback is appreciated :) This is still very much a work in progress.

[1] https://github.com/qvacua/vimr/wiki/File-Browser-Actions

Here's a json file with sha1 hashes of the solutions.

https://gist.github.com/dnerdy/30e2847188a95178688f

I created it using the encrypted solutions from this project: https://github.com/csu/project-euler-offline

Hashed solutions is brilliant! Thank you!

I have a tool that syncs my DNS records to CloudFlare using flat files that I keep under version control. I just extracted it from my personal tool set:

https://github.com/dnerdy/namesync

This flat file format seems to work well, and the tool could potentially be updated to support other DNS providers.

That is much more useful to me than the OP service. Thanks.

This video does a great job explaining how Bitcoin works. Here's the accompanying blog post:

http://www.imponderablethings.com/2013/07/how-bitcoin-works-...

Pac Global Insurance Brokerage, Inc - REMOTE or Los Angeles, CA

Full stack Rails developer.

This is a somewhat unique position for the hiring thread. We're looking for someone to take over the development of our website and related back office tools. You would be a one man show working closely with our Operations Manager and have lots of control with respect to scheduling and the technologies we use. Our existing contractors are HN readers (they're the ones helping us make this post). We're looking to take someone on full time. They've used modern tools/frameworks and kept the code base in good order. The point is this: you'll be taking over a well maintained project... not walking into a nightmare.

We think this is a good opportunity for someone who would like to work solo but also be secure in a full-time position.

https://pacglobalins.com

http://careers.stackoverflow.com/jobs/40899/full-stack-ruby-...

jobs@pacglobalins.com

Text-only is also what I was thinking.

Implemented via the Web Inspector:

http://static.deliciouslynerdy.com/tarsnap/logo-and-favicon....

http://static.deliciouslynerdy.com/tarsnap/styles.png

I'm glad to see work in the area of making linux containers more accessible. I recently stumbled upon openruko[1], an open source Heroku clone, and from there discovered linux containers and lxc[2]. It takes a bit of configuration to set up useful containers, though. I think the ideas behind Heroku and The Twelve-Factor App[3] are good, and containers are an important building block. I'm excited to see (and I'd like to see more) tools like Docker that aid in robust and streamlined container-based deployments in-house.

[1] https://github.com/openruko [2] http://lxc.sourceforge.net/ [3] http://www.12factor.net/

I've been making heavy use of OpenVZ. The documentation isn't the best, but it's often used for VPS slices.

I think a common use case that requires a bit of hoop jumping is using an email address in place of a username. Example from the docs: https://docs.djangoproject.com/en/dev/topics/auth/customizin....

I suspect this may be the nastiness that's being referred to; this is the use case that I was hoping would be made dead simple.

With previous versions of Django I generated a random hash for use as a dummy/unguessable username, required an email address in the RegistrationForm, customized the AuthenticationForm, created a custom email authentication backend, and monkey patched User with various helper methods.

In 1.5 it looks like the AuthenticationForm will adapt to the field defined in USERNAME_FIELD[1], but a lot of work is still required. Support for easily using email address as the username (or support for easily specifying the username field in general without requiring all the other boilerplate) would probably go a long way.

[1] https://docs.djangoproject.com/en/dev/topics/auth/customizin...

Thanks, that's a good point. Hopefully we can do something about that in 1.6.