I am same there (using KDE Plasma with global menu). Recently, with VSCode's menu on title bar, it seems to have started a trend doing so. For example, JetBrain's IDEs are also designed that way. I found the term for that, it's called LIM (locally integrated menu). Now, Unity has done that many years ago. If I remember correctly, the behavior was: when maximized, it behaves like a global menu; when not, it's a LIM.
Fortunately, there's a PR for implementing such things in KDE Plasma. Here is the discussion [1]. Right now, you can use it, but it probably won't be merged into the main branch soon.
This seems like a weird half-step between "headerbars" / client side decorations / hamburger menus. KDE Maui is going that direction: https://mauikit.org/apps/
Sadly it just seems to be more like a custom window decoration that only does shadows (no actual title bar) and regular KDE headers, no actual window controls / CSD.
That's exactly what the Soviet era was. Say you work in a hospital, you would be living within 10 minutes walk away from your office. You will eat in the hospital cafeteria. Your kids will go to the hospital-sponsored schools. Unsurprisingly, your neighbors will be your coworkers. Your kids' friends will be your coworkers' kids. Life is simple and efficient but there some other downsides that's probably not relevant here.
The Soviet era? You mean in the USSR? How is that relevant here? And are you really claiming that everyone in the USSR had a 10 minute commute? That would be some incredible planning!
I have been using Lepton since the beginning. Currently browsing this page with Lepton! Thank you for making the theme and a detailed history of FF theme.
KPXC is brilliant. Recently I switched to it from BitWarden and I am satisfied. The only issue for me is the autotype support on Wayland (it's not there yet; currently only able to auto fill password and username for xwayland app).
Sorry for the late reply. BitWarden is great. I really don't have anything to complaint (before BitWarden, I was using browser built-in password manager). However, I changed. I start to value the following:
1. I need a tool that can save not just password, but something more general. For example, a desktop software credential (with BitWarden, I need to open a browser or electron app to do that). Another example would be a PIN required each time I use the voice mail. Or certain PIN for my bank accounts (not the one used to login the online banking). I am aware you can save them in the note section, but it feels better when you can customize these fields. These non-password secrets used to be saved in plain text scattered around in various files on my PC. Now I have a centralized and organized access.
2. I know that with some configuration you can have self-hosted BitWarden vault. But I think KPXC + whatever_file_sync_app is simpler.
3. I actually started using KeePassXC because IT forced me so. I hated it initially, but later discovered it's actually a great tool for managing secrets in general.
4. HN Syndrome: preferring "native" app than web/electron.
Ah, didn’t know Bitwarden doesn’t support extra fields like that, that is something I use as well. Thanks for the reply, it’s rare to hear about some (even personal) negatives of bitwarden :)
I chose KPXC because I am in easy access to the database, and since I already pay for cloud hosting I just sync the database on the cloud (I use Seafile, I recommend!). Open and convenient :)
I'm sure Bitwarden is more than adequate as well though.
I've migrated from KPXC to Bitwarden because of all the sync conflicts and having to diff different versions and figuring out, which data is latest (yes, keepass-diff is a thing).
With Bitwarden, I cannot create a new password or change existing one without being online, but I consider that a small price for not having to deal with conflicts anymore.
The sync conflicts happened to me whenever I left keepass databases open and changed it on multiple devices. Usually, those changes were adding new accounts into the databases or changing a password on one while adding something on the other. This regularly happened when working in a team.
I assumed people would switch from Keepass + database synced on a private server to something else when they started working in teams and need better/easier permission models. :)
As you have mentioned it, I have written the tool keepass-diff (<https://github.com/Narigo/keepass-diff/>) to help me for exactly these conflicts and I could quickly resolve the issues with it. It was still useful enough to let me keep using Keepass. Was it not working for you or was it too hard to use because of how it needs to be set up first? Would you have stayed with Keepass + sync if something similar to this was integrated into UI clients?
I've used 'Automatically save after every change' and 'Automatically reload database when modified externally', as the other comment says, with syncing via Syncthing. It wasn't in team, but between multiple devices - laptop, desktop, phone and with a NAS in the sync chain, so there is something always on.
Yet, the sync conflicts happened anyways. The first time it was quite shock, why my password doesn't work, but then I found the conflict password file and the password from there worked.
Your tool made it much easier, big thanks for creating it.
Maybe, if the keepassxc had in the UI, that it detected a sync conflict (that would involve a knowledge how the misc sync tools work) and offered merging them, I would probably stayed.
Ultimately, I switched to vaultwarden, on the same above-mentioned NAS. It does not have all the features of the keepassxc, but it is good enough for me, the sync problems disappeared, and the browser integration works a little bit better (doesn't complain that the main app isn't running, while it is).
I have checked a few settings on KPXC, and it has 'Automatically save after every change', 'Automatically reload database when modified externally' (and 'Safely save database') all enabled, not sure it helps (as I mentioned, never had any problems).
Not sure if NextCloud could be causing some issues? As I mentioned, I believe Seafile automatically overwrites (to newest version) and it's been fine (there's history if you lose something, which shouldn't happen anyway).
I do think this merge functionality would be very nice in KPXC, but for other reasons: I sometimes use the browser databases to save passwords (when I forget to open KP) and I need to merge the new entires.
Since logging in is an online activity, that means every modification should automatically sync to the database as well. Thus I've never had conflicts, I think Seafile handles conflicts very well (mostly silently?). Never had an issue really (although the Android app is slightly clunky).
Logging in doesn't have to be on the public internet. It doesn't have to be a some intentionally isolated network either, but think setting up IoT devices: you log to the AP they created, create credentials and then connect them to some other network with Internet connectivity. So while you are connected to their AP, you don't have sync.
I recently tried it, as I don’t need 90% of the features NextCloud offers anyway. Sadly, the installation process seems far more complicated, and I ended up just abandoning it and going back to NC after getting unclear error messages.
I see; I use hosted version (some here https://www.seafile.com/en/partner/ -- they should advertise it better imo). Had no problems from the beginning (there are clients for Linux/Win/etc. as well).
I like the idea of self-hosting a lot, but I also think it's fine to have hosted services of OSS (I think you need to be technically oriented to make it work easily and reliably, which isn't everyone).
I am curious why you switched from Bitwarden? Usually when people are exiting a password manager it’s migrating to Bitwarden or KeePass but you’re the first I’ve heard moving from Bitwarden itself.
I too switched from BitWarden to KeePass. I was reading about browser security and became concerned about running my password manager in the same process as the browser and relying on its sandbox. With KeePassXC I have the option to either forgo browser integration completely or use their addon which communicates to the manager and asks for an entry, which prompts for permission itself or uses an allow list by URL. That makes it much harder for a website to somehow break the sandbox and access my entire database.
It's a small change but it does reduce the attack surface as well as force me to manage my data myself which I want to do more of.
Also with BitWarden, their UI annoyed me when I needed a password outside the browser. L
I'm not the person you asked but I switched from BitWarden to KeepassXC. BW was very good so the only reason I looked for an alternative was I wanted something that would support entering passwords with autotype in OS apps instead of just the browser.
I'm going to take a guess and say that you're using GNOME if you're using Fedora and yeah, I don't think auto type works on GNOME's wayland version yet. They're working on their own protocol called libie the last time I checked.
However, auto typing on Wayland works pretty well if you use wlroots compositors/window managers like sway.
My guess is probably the QuickJS has less resource usage compared to the more performant V8.
UPDATE:
Now I have read the linked article, here is the reasons (copied from the article):
API and integration principles are close to what TIScript uses – it took me just 1 month to add QuickJS to Sciter core. And 4 months more to expose HTML/CSS runtime to JS.
Relatively compact implementation – QuickJS is slightly more fatty (by 100 kb) but still in acceptable range. For the note: full version of V8 is about 40 mb – 5 times larger than Sciter itself;
Liberal MIT license. Sciter cannot use GPL/LGPL code – many customers expressed this requirement;
