• 1 Post
  • 328 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle




  • You can’t have it both ways. It’s hard enough to get people to switch to signal, or least also use it next to other messengers. Now imagine they’d have to connect to multiple servers to talk to multiple people. Possibly everyone connection details. Even if that’s done in the background, you have to somehow get the connection registered once, discovered if you will.

    Anything and everything you send through their server is end-to-end encrypted. Some people hate on the phone number being required to create an account, but it’s also the reason it works at all: anyone in your contacts who also has signal you can talk to. Phone numbers are an international standard. If course this also has downsides…

    Finally what you’re asking for exists. NextCloud has “talk”. Which is essentially a messenger app, it’s built in. Go use it. I have a NextCloud instance and I don’t use it either. What’s the point of having an app I can only use to talk with people so close to me that they’re in my NextCloud with an account already?


  • If you’re using a keepass database, Keepass2Android can natively sync with many cloud options including self hosted and generic ones, even without specific “companion” apps. That’s what I use. In my case, it’s backed by my NextCloud, but it used to be Google drive before.

    Just also sync the file on your PC, merging changes from different clients is part of the keepass database format and “just works”.

    Also VaultWarden works great if your can self host it, but I prefer keepass for a variety of features and integrations.


  • Yeah, they do need to clean up the installer a bit. It’s also not quite turnkey for a Windows dual-boot.

    Mind letting us know why or how? When I installed it almost a year ago on my desktop, I did install it as a dual boot option with no issues. Of course this doesn’t mean there aren’t issues I just didn’t run into. I’m also not new to Linux and didn’t pick a fully default install, if that makes a difference. So I could’ve probably fixed it if it did break, but it never gave me any issues.

    The only thing that I dislike, and that could probably cause issues, is that for my installation the mount point for the efi/boot partition isn’t specified in fstab using a uuid, but using the device name (which isn’t fixed and can change with hardware changes). That is a very weird (and unnecessary) decision IMHO.












  • Oh the impot itself went fine and quickly. But I have like 400+ playlists or something, so not being able to use folders isn’t an option. Cause that’s just inexcusable in 2026 to have a service where you can’t even nest or sort playlists. That was absolutely wild to me, and a hurdle I didn’t expect was even possible.

    Additionally, when checking for which songs it failed to import, of which there was a surprising number, quite a few of my favorites were missing. And it’s not like it just didn’t correctly map them, they weren’t available at all. Generally like 15-20% of songs were missing. And that’s just waaay too much to accept for me.