This is exciting. My only request here is: whenever it works please release a standalone wasm file somewhere (anywhere). So many projects either require building the wasm themselves, or instead of releasing a .wasm, they release a JS wrapper that auto-loads the wasm/wasm-imports. Its a pain to try to extract the wasm out of those projects.

What I am doing is to create a omnikee-lib crate within the project that will get compiled to WASM, not just plain keepass, because I need additional adapter methods to interface with the web part of the application. I don’t have the bandwidth to turn keepass into a general WASM package that could be npm installed at the moment. As I am dogfooding the crate, I might get to a point where I know what a good JS interface for it would be, though, and the omnikee-lib crate could become the official WASM interface for keepass.

sweet! I sent you the invite.

Currently, SSH key management is not supported, but it would probably be possible to implement the SSH agent protocol in the Rust part of the application. I see that russh has a SSH agent server implementation. Let me know if you are interested in contributing such a feature - I am currently working on exposing all the custom entry fields in the UI, so the project would almost be ready. edit: would be ready to add that feature now

thanks for your interest! I have sent you a response with an invite link.

I think the Google as an identity provider example is misleading. The more common use case will be medium to small companies where several admins/developers need to login to various servers and where manually adding and revoking keys across these servers will be cumbersome.

As the other commenter said, in those cases, the organization would also deploy its own IDP.

Here is an exported result list from Kagi that should be accessible without an account.

deleted by creator

Lucky for you, the post contains an animated JPEG showing the change over time. Lemmy clients that don’t support playback will only show a static image

Hey URL, go and fetch your friend JSON!

Makes perfect sense.

Thanks for sharing! I agree with your main point about overall emissions not changing too much since most of that reduction comes from feedlots already.

One small addition: the product that I originally linked is based on 3-nitrooxypropanol, a petrochemical-derived active ingredient, not from red algae (so there is probably a different calculation about production cost and CO2 impact than growing, processing and transporting red algae on a large scale).

Fun fact, there is already a food additive to reduce methane emissions from cows