choosegoose

I've found https://contexts.co/ to be the best solution for OSX. It wont let you ⌘+tab through the browser tabs but if you have multiple windows of the browser open you can see them individually.

We use Twistlock (https://www.twistlock.com/) as it does the CVE scanning but you can setup rules for compliance, binary monitoring and a whole plethora of other security/auditing type things. It also has a jenkins plugin so you can fail builds if a certain threshold of CVEs/compliance failures are introduced by developers (the only way to actually get the team to care about security).

Our security folks haven't really decided what to do with containers although some people are just using RHEL7 base images since its "enterprise-y". Our group personally uses alpine base images. If we have something like a java service hosted by Tomcat, we build alpine then build tomcat and then build our "service" container. While most people are fine pulling from Dockerhub, we do work in closed-loop environments and have a private docker registry where we host our "chain" of docker images which are versioned and updated regularly.

And you can self host it, which was what convinced me to switch from lastpass.

https://github.com/mprasil/bitwarden_rs

This is a 3rd party implementation of the bitwarden api, which gives me more confidence in the 1st party product.

Are you on an iOS device or Android? If you are on an android device that is Oreo or higher, bitwarden uses the autofill framework:

https://blog.bitwarden.com/bitwarden-the-oreo-autofill-frame...

That seems really exciting. When that occurs I will most likely switch over. Unfortunately you can't quite host it your self yet: https://github.com/wireapp/wire-server/issues/2

Are you not concerned with the data Wire collects?

https://news.ycombinator.com/item?id=14069674

Versus the data Signal collects:

https://signal.org/bigbrother/eastern-virginia-grand-jury/

Although I agree Wire looks like a much more (visually) polished chat service, it seems like they (Wire) collect more data than is necessary.

Your headphones would need a DAC if you want to charge your phone and use the headphones at the same time.

Ideally you would be able to use a splitter that would male USB-C on one end and female 3.5mm + female USB-C. Unfortunately you'll be stuck with only 500mA.

The USB-C spec calls for the negotiation of power delivery (amperage) via two lines that are used for audio passthrough. When those lines are occupied the device will only pull 500mA from the cable to ensure components aren't fried.

Now if your splitter had a DAC, you could get full power but it sucks you have to spend money to listen to audio and charge your phone at the same time.

From USB Type-C Specification Release 1.3:

Analog audio headsets are supported by multiplexing four analog audio signals onto pins on the USB Type-C™ connector when in the Audio Adapter Accessory Mode. The four analog audio signals are the same as those used by a traditional 3.5 mm headset jack. This makes it possible to use existing analog headsets with a 3.5 mm to USB Type-C adapter. The audio adapter architecture allows for an audio peripheral to provide up to 500 mA back to the system for charging.