Passbolt VS flood

Passbolt - Open Source Alternative to 1Password

Here's another to add to the list, Passbolt. It is open source and basically built for teams and enterprise. It is design primarily with a unique security model which is based on asymmetric end-to-end encryption, with user-owned encryption keys and support easy cross functional team collaboration. Can it hosted on-prem or host it in cloud depending on your preference. Might be too much information and a tad bias as I work here but wanted you to have all the information as passbolt fits your requirement for business level password manager.

Fyi there is also Passbolt.

I currently switched from keepass to passbolt: https://www.passbolt.com/

I might be bias here as I work here but another recommendation would be passbolt. Open source password manager that is built for teams and businesses. You can either self-host or host it in the cloud, really depending on what you require and supports secure granular sharing of credentials with nested permission in just a few clicks. Its a solution that is built with security as a top priority. It supports asymmetric end-to-end encryption based on OpenPGP cryptography using both public-private key for encryption/decryption. No secret key is stored on the server side. Both the free community edition and the paid pro version are 100% open source.

All that said...here's my shameless plug: I work for passbolt. You mentioned you have a small team, you might give it a look: https://www.passbolt.com/ there's a community edition you can install for free on the server of your choice. I'm here and happy to answer any questions.

Passbolt for passwords (backed up to KeepassX files)

Have you checked out Passbolt? Its open source built for teams and organisations. Supports asymmetric end-to-end encryption, based on OpenPGP. Its on-prem or you can host it in cloud. You can either opt for the Pro/Enterprise version or the free community edition depending on what you need.

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Only one that I'm aware of is Flood: https://github.com/jesec/flood

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile

https://flood.js.org/ ?

If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)

qbitorrent-nox with flood-ui

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood