# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 12
# self = https://watcher.sour.is/conv/nlzhexa
Bitwarden is truly excellent. Highly recommend
@shreyan ever tried KeepassXC or Pass/Password Store ? They are worth giving a try ... Then you can keep your KeepassXD database in synch across your devices with (NOT /R/s/y/n/c) I meant Syncthing or git in the case Pass (using a git repo in within your local network of course) 👍🏼(edited)
@aelaraji I've also been using pass/gopass for years now and loce it 👌
@aelaraji I've also been using pass/gopass for years now and loce it 👌
@aelaraji I've also been using pass/gopass for years now and loce it 👌
I use 1Password, and iCloud Passwords. I had migrated from 1P to iCloud, but ran into issues that forced me to continue with 1P. I pay for a family plan on 1Password.
I use KeePassXC because I really only use one device. I imagine it would be challenging to rsync the database around if I needed my passwords on more machines. It's probably fine if you're deliberate enough, but I don't think it would take long before I'd lose a password by editing an outdated version of the repository and overwriting the main copy.
I like the simple architecture of Pass, and it would indeed lend itself well to a Git repository, but I don't like that service names are visible on the filesystem. pass-tomb might mitigate this somewhat but it seems messy and I don't know if it would work with Git without compromising the security of the tomb.
What's so good about Bitwarden? Everyone seems to love it. I like that it can be self-hosted. I certainly wouldn't want a third party in control of my password database.
@mckinley You definitely have got a point!
It is kind of a hassle to keep things in sync and NOT eff up.
It happened to me before but I was lucky enough to have backups elsewhere.
But, now I kind of have a workflow to avoid data loss while benefiting from both tools.
P.S: my bad, I meant Syncthing earlier on my original replay instead of Rsync. 🫠
@aelaraji I've never had a use for Syncthing but I hope I get one at some point so I can see how it works. Do three-way merges work on Keepass database files?
@mckinley I can't say for sure. I didn't even know how three-way merges work till I looked it up. I guess it's more of git thing that would prove useful in the case of using passwordstore/pass.
As for Keepass, all I do is syncing it's database file across devices using syncting. Never felt the need to try anything else.
I guess it is safe enough for my use case, with Backup database before saving on and custom Backup Path Placeholders as Backup plan in case of an Eff up.
Indeed, BitWarden works nice as a credentials manager, and I'm quite happy with the implementation of Passkeys.
Indeed, BitWarden works nice as a credentials manager, and I'm quite happy with the implementation of Passkeys.
Sadly my old Android 9 is not compatible with the mobile app, although I use the web for that case.
That said, that's what I've been using for years and I can't find a reason to try another (as usually happens with these tools)
I'd suggest of self-host or trying a public instance of Vaultwarden like https://passwd.hostux.net
(donation supported)