I wonder how this compares to pgModeler (https://pgmodeler.io/) which I've been using the most in the recent years, would love is someone who had tried both could share some observations.
What kept me using Mac over Linux as my main OS was Adobe CC + Sketch. You could get _some_ stuff working with wine, but it required too much tinkering for me to be a distraction.
Now the software is less of an issue, but the battery life on my M1 is just so much better than anything else.
Yeah, these are not general recommendations, rather the stuff I ended up using.
Thanks, I'm actually going to give Inkscape another try. I think the last time I used it was 5-10 years ago.
I don't remember why I stopped using Darktable. I remember researching it and trying it out for a bit before buying CO. Does it have decent camera profiles? How do you find working with it (raw editing + culling/managing catalogues)? I use fuji mirrorless cameras.
The only thing I'd suggest to consider to add is some sort of authentication. If I deploy this on a server so I could reach it with my mobile, on the go, and it has my API credentials, I wouldn't want anyone who stumbles upon the page to be able to interface ChatGPT on my expense.
Well, I'd love to see a change there as well, then: if I'd want to share the interface with my family I wouldn't want to reenter everything everywhere they might be accessing the page from.
Unfortunately, because of the logistics of how this works, there is no free trial period. We do our best to give you an idea of what you're buying via public documentation, videos, and an overview of the repo. If you buy it and truly decide you aren't going to use it, contact us about a refund.
Wish I could figure out how to do a free trial. I've obviously considered whether the whole thing should be free and open-source in the first place, but getting paid to work on this stuff is the best way I know to make something high quality, where good support, improvements, fixes, etc. are all expectations.
Happy to give out some discounts if people are interested in that.
I'm in no way affiliated with them, but as a very happy user I can recommend you to try BitWarden [0] instead of 1Password. It doesn't have the bug you have described, nor it shows passwords in plain text by default (you can also copy a hidden password to clipboard - useful when you share a screen with someone).
Been using Bitwarden ever since LastPass imploded themselves with their idiotic policy of no Destkop + Mobile for free users.
Very happy with Bitwarden. Has a self-hosting option, too, which I like. been debating setting up a self-hosted server here at home for storing my passwords.
I was actually looking for a password manager around the time LastPass introduced that policy. I was considering it but when I saw that I was like, "Okay, looks like LastPass is off the table."
I ended up going with Bitwarden and I am very happy with it. Actually, 4 days ago was my official one-year anniversary with them!
What if https://bitwarden.com/ gets hacked? Please don't say self-host cause that's not an option for most regular people. At least with KeePassX/KeePassXC you can use that own its own without an online account.
The fact that I have to create an account and an online vault with a master password is the biggest turnoff for me. https://vault.bitwarden.com/#/register
They only store the encrypted vaults, which is useless without your master password. So even if it is hacked, the only thing the hackers get is an encrypted blob.
> you can use that own its own without an online account.
That is because KeePassX/KeePassXC is an offline app that reads a database (.kdbx file) you have on your computer. Bitwarden is for people who want to use their password manager on multiple devices. So an account is necessary.
How do you use Keepass across multiple devices. Please don't say Syncthing cause that's not an option for most regular people. And if you use something like Dropbox, what if https://dropbox.com gets hacked?
> The fact that I have to create an account
This is for authentication (needed it for syncing it across multiple devices).
I would assume that the most likely issue you would face is malware running on your own computer that captures the master key or sends passwords back to an attacker. Not someone gaining access to the encrypted password vault and then cracking it - unless you have a very week key.
No weak key here, and you may be right, but my main concern is that encryption is only strong in a given time period.
If someone could gain a copy of a known high-value ciphertext, they may not be able to crack it now, but time is on their side, and I can't recover the file once it is out there. My only recourse is to speculatively rotate passwords inside the file.
...but not wisely concerned about the security risks of running your own SaaS on your own server, and have enough spare time and energy to meticulously implement proper security procedures, and keep it up to date, safe and secure, 24/7.
He said "Please don't say self-host" for a good reason. Do you really believe that most regular people have the free time and technical skills and security chops to "easily run your own server instance" safely and securely?
If you think that's "easy", then you're doing it wrong.
> ...but not wisely concerned about the security risks of running your own SaaS on your own server, and have enough spare time and energy to meticulously implement proper security procedures, and keep it up to date, safe and secure, 24/7.
Run it behind a VPN? Use a properly secured containerized image? Implementing good security is much easier at small scales than at large scales.
> Do you really believe that most regular people have the free time and technical skills and security chops to "easily run your own server instance" safely and securely?
Who's talking about "regular people"? We're discussing what solutions we -- users of HN -- find most effective for our own use.
> Linux is only free if your time is worthless. ;)
My experience, especially in a business context, has been quite the the opposite. Implementing complex projects with proprietary vendor solutions involves a vastly greater amount of time dealing with requirements analysis, project scoping, contract negotiations, support escalations, etc., only to be locked into something proprietary and idiosyncratic, a sealed black box where even trivial modifications require another round of analysis, project scoping, etc. usually with a heft cash payout.
Conversely, the time we spend setting up and maintaining self-hosted FOSS solutions improves our own knowledge and skills such that every subsequent project becomes incrementally easier, and therefore much faster to implement.