#vaultwarden — Public Fediverse posts

I gave vaultwarden a try last year when I was also playing with the idea of going from iOS to grapheneOS. But I didn’t switch and it languished stale on the hardware.

My question is this. Is the best path still to self host vaultwarden or switch to the official server?

#selfhost #1password #bitwarden #vaultwarden

After some spontaneous hacking on BitRitters edit mode, i made some good progress: First time i could change values and save them to the database/server.
It really means alot to le because after 2 failed applications for funding i ditched the topic for too long.
It might need a major rework of the UI internals though, but now i am motivated again.

#BitRitter #VaultWarden #BitWarden #PasswordManager #LinuxPhone #LinuxMobile #Relm4

Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
#BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden

Making progress with #BitRitter. Slow, but steady.
Today i implemented a password input to unlock the #BitWarden / #VaultWarden vault, so we can soon remove a part of the credentials.toml (which was just a workaround for faster testing) and make the app safer.
#Relm4 feels nicer the more i get to work with it.

Sadly my ARM CI did not work as nicely as the x86, so i can't package for my phone easily.

#MobileLinux #LinuxMobile

In the next iteration of my app i want to have proper test and CI for x86_64 and arm64.
So the next steps will be:
- try out #testcontainers to provide a #VaultWarden instance
- maybe send a PR with said container definition upstream
- get the CI running according to the #Relm4 documentation. That said i need to convert the actions used in the example to #ForgejoActions since i am hosting on #CodeBerg.

Then i will work on more features like the password dialog and the detail page.

My first (very incomplete and WIP) iteration of my #MobileLinux #BitWarden client. It ia usually not ready for others to use, but i need to publish it to stay motivated.
Works with #VaultWarden aswell. You have to build it fron source though, for the time being.

https://codeberg.org/Chfkch/bitritter
#LinuxMobile #Relm4 #GTK

@brunty
I LOVE this question!

#seafile - G-drive style file storage/sharing
#vaultwarden - bitwarden implementation
#nextcloud - Like G-suite but infinitely useful
#Linkace - Bookmarks, link collections, sharing
#mastodon - go figure!
#gitea or #forgejo - Lighter than gitlab!
#opengist - just like GitHub gists
#privatebin - secure and flexible Pastebin

Bonus round: nextcloud can be used as a #webdav endpoint so you can use it as the storage backend for #joplin and #obsidian note apps.

Today i learned more about iterators, references with my buddy #clippy while working on my side project.
The #Relm4 channel was useful and quick in response as ever.
My #BitWarden #LinuxMobile app is shaping up, though progress is slower than expected. But progress nonetheless.
A first prototype will not reach public this year i think, but should not take so long.
#MobileLinux #VaultWarden

I tried to use the #rbw crate to connect to connect to my #VaultWarden instance. Seems i cannot even construct a client and login: Some #reqwest error with relative base url.

If i construct the reqwest client directly it works. Any ideas? I cannot upload the code right now, maybe later.

#Rust #RustLang