A very interesting addition indeed to Bitwarden. I still personally prefer my own setup as I'm guaranteed not to run any risks of being siloed but I've started pointing others towards Bitwarden because of this and their strong commitment so far towards Open Source [0]
I've been using bitwarden_rs [0] because it's lighter, a bit faster, and a lot easier to set up (it's a single docker image with bitwarden in it, rather than having to reverse engineer their docker-compose "we choose where there data goes" forced deployment docker script.
Being a 3rd party implementation, Bitwarden Send doesn't work. So there are pro's and cons, but you can absolutely control your own data here without needing to use their official services.
For sure. bitwarden implements the Bitwarden API so they tend to get around to all these features. It's just worth noting that they tend to trail upstream.
Same. I use keepassxc and just sftp the database around, but I have my mom using bitwarden. Hopefully I' ll convince my sister to start using it soon too (she is not a believer in password managers, yet).
It's funny to me that I basically had the same setup, family included. My sister finally set up Bitwarden after someone logged into her Facebook account and started sending her friends a picture of Itachi. Keep hoping, security is often just a disaster away :)
[0] https://github.com/bitwarden