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

help-circle






  • I agree that Windows is bad, and getting worse. But for them it works well enough. Idealistically, I’d like to move them over, but in practice there’s barely any benefit in it for an incredible amount of effort and (limited) time spent for anyone involved.

    Recall isn’t a reason either, especially not with the banking argument: if they want to transfer money, they fill out a piece of paper, go to the bank and put it in a mailbox for those. They don’t do online banking. All they do is email, and one of them edits a couple of photos. They are used to the software that’s Windows-only. They know where on the screen to click. That’s it. It doesn’t matter if it’s Windows or not. I also have no argument they care about to convince them.

    If i wasn’t on my phone I could write much more detailed explanation, but I am, so this will have to do.


  • I don’t own a Windows computer anymore. I’m self hosting the services I need (and have for a long time). Some subscriptions remain, but not to Microsoft, which I’ve never had.

    My parents are still on Windows, as they are too old to switch. But they also don’t actively use anything from Microsoft, let alone cloud services. I could switch them, but I also don’t quite see the point. It’s just a lot of time and effort on my part, for no actual benefit.


  • Self hosting BitWarden still means it’s accessbile for them and/or from them. You also have no way to audit their security from what I understand. VaultWarden is FOSS, if you want to, you can go check. And it does get checked by people with the competence to check this do every now and then. [Edit: I forgot that BitWarden is actually souce-available as well, while not being FOSS that’s still better than most solutions]. I just prefer full FOSS whenever possible. I prefer it not be a black bos I just happen to run on my own server.

    If you self host VaultWarden, the instance can just be not accessible from the internet, and only from behing a VPN. Obviously this is inherently much safer. If that’s possible with the self-host option I don’t know, but even just for licensing the local instance will have to be able to reach their servers (possibly be reachable from their servers, too). I did see they got an “offline deployment” option for air-gapped servers, but haven’t looked into what limitations that entails.

    Additionally, you’re still within their licensing model. So for certain features you need to have a not-free account (like even just more than 2 people).

    And like others said, VaultWarden is much lighter on resources in general and you aren’t limited in what you can and can’t do (users, collecitons, auth-options, …).


  • Your first point is debatable. You still have to trust them to be that secure, and you can’t verify that. If they are ever breached, it’s literally the worst case scenario. You can self-host their solution, but only in the enterprise tier (6$ per user per month). Also BitWarden is a target woth attacking, I am not. BitWarden hosts thousands of instances worthy of being attacked individually. A personal VaultWarden instance of “Mike and Molly Peterson” isn’t exactly an attractive target. I do think they are pretty secure, but a single mistake with these stakes can have immense consequences. LastPass was also breached repeatedly, with a similar buiseness model.

    The second point about electricity wouldn’t be true in my particular case, as the server for self-hosting it is running anyway. Running VaultWarden or not doesn’t change the power usage noticably. Obviously this is different for someone who doesn’t just have a server at home running anyway.

    Side note: I’m not actually running a personal VaultWarden instance, as my personal requirements are being met just fine with KeePass files. We do run an instance at work, but it isn’t world-accessible (internal access only).



  • the form factor is easy to get around

    Why did you just ignore everything I wrote, but you still replied to me? No, it isn’t easy to get around. You can use a server to game, but the server mainboards and CPUs expect and work with differently configured memory (registered DIMMs). All the AI infratructure uses that type. You can’t use that memory in a normal PC. Wikipedia reference if you’d like to read about it, but a relevant quote:

    […] the motherboard must match the memory type; as a result, registered memory will not work in a motherboard not designed for it, and vice versa.

    You would have to un-solder all the chips and remanufacture new memory modules, and nobody is doing that, especially not at scale. It might be an actual buisness model to do that once the bubble pops, but it isn’t a problem that’s “easy to get around”.>







  • First my context: I’m also running multiple Proxmox hosts (personal and professional), and havea paperless-ngx instance (personal/family). I tried Firefly, but the effort required to get it to a point where it would be if use to me was too high, so I dropped it. Haven’t used n8n.

    For the setup I’d just use the Proxmox community scripts, if you haven’t heard of them. Makes updates trivial and lowers the bar to just trying something to basically zero.

    Paperless-ngx I actually use, cause it means I can find something when i need it. It’s all automatically ocr’d and all you have to do is categorize them. With time, it’ll learn and do this for you. You can (manually) setup your scanner to just directly upload files to the “consume” folder and it just works. PC/server power is near irrelevant, it just means OCR takes slightly longer, otherwise it’s a web server. You can run this just fine on a raspberry pi.

    I don’t have any real automation setup, so I can’t really comment on that. My advice is to just install it, see what it does and how it feels. Try to anticipate if and how much automation you need. Many aspects of all this are of the “setup once” variety, where once it’s working, you don’t have to touch it again. Try to gauge if the one time effort is worth it for you, then go from there. As I said, it was fine for paperless for me, but not for Firefly (but I might need to revisit this).