RE: The biggest problem about this is the API definition. Libraries have APIs. But in a completely different way, webservers have APIs. If I say “we are going to a conference on API’s” what do you hear? That we are going to talk about REST, GraphQL, or gRPC, or web server APIs of some type. This is common phraseology. However, one time I was invited to such a conference, and it ended up being about C# design philosophy.

In that way API is an adjective (REST API, C# API, …) AND a noun (webserver API). That’s a problem.

And as an adverb, there is some justification to replace it with Library and others (REST Endpoint, C# Library)

Because otherwise all public functions are API’s, which doesn’t seem necessary to me. Saying a Library has an API is somewhat redundant. Saying a server hosts an API is not, many servers run jobs or databases. Many websites don’t host APIs. Etc.

That might be worth it. Is bitwarden self hosted FOSS?

Yeah but without email aliases it would not be worth it

I did weeks of work migrating every password and email address to proton. Sucks the stances they are taking but now I’m kinda stuck, and it’s still better than Google.

You can say other things. Good. It’s been better. I’m alive. Just keep it short.