This thread is about KeePass and my comments relate to that. If you pull KeePass2 from the repos in Debian, for example, it’s going to pull the Mono runtime to execute it as well because it’s been built, like most C# apps, for JIT compilation. I doubt it’s even possible to compile KeePass2 using AOT compilation.

This is what the C# KeePass application looks like using the Mono runtime in Debian:

This is KeePassXC:

You can see which has better native integration into the desktop out of the box.

Obsidian is really good. Very feature-rich and customizable.

I personally prefer Joplin for a couple of reasons. It’s fully open source and while it has less features and customizability, I also feel it keeps out of my way more to allow me to focus purely on taking notes and not messing around with other features. Obsidian encourages me to play with its extra features more, which for my case usually just reduces the productivity of my note-taking.

Probably just a me-thing. I tend to gravitate to more straightforward and minimalist solutions generally.

I prefer the KeePassXC fork as it’s written in C++ and not C# so it has better native integration with OSes like Linux, but yeah these are really good solutions with no subscription requirements or necessity to upload to any cloud service.

Supporting the Chromium monopoly is a valid point, but there’s also a reason why a lot of browser companies, even those who market their browser at more privacy-conscious individuals such as Vivaldi and Brave, choose to fork Chromium over Firefox/Gecko. A good portion of that reason is Chromium’s superior security architecture that is a lot more battle tested and mature; the rest of the reason often comes down to compatibility and mobile-readiness.

A lot of people are wary of any browser engine attaining a monopoly since IE achieved this back in the day. It’s not exactly a like-for-like comparison though, since Chromium is actually open source and IE/Trident was not. For that reason, anything problematic can be stripped out by those who fork it which is exactly why we have browsers like Brave, Vivaldi, Ungoogled Chromium, and others who remove anything that feeds data to Google from their releases. The option also theoretically exists to hard fork the project entirely and take it in a different direction which was never a possibility in the IE days, although that would be a monumental effort.

I get it if people want to support Firefox/Gecko for philosophical reasons. In an ideal world there would be several projects of equal maturity to the browser engines we have today. Realistically though, for all intents and purposes, the vast majority of the world is already using Chromium in some flavor or another and it’s a project that has a lot of the world’s best browser engine developers contributing to it. As a user, I care most about using a secure, privacy-respecting browser that I find innovative which caters to my needs through its features rather than fighting a philosophical battle that’s already been lost. Naturally if you find Firefox does cater to all your needs though, more power to you.

Brave and Vivaldi are very different companies. I don’t use Brave specifically because I’m not comfortable with the fact that, essentially, they’re an advertising company primarily looking to push their crypto.

It’s true that using a Chromium base poses some additional privacy challenges. Due to its customizability, it’s certainly possible to harden Firefox to a better level than any Chromium-based browser currently; projects like Arkenfox certainly help with this, as well as the tweaks ported to the browser by the TOR Uplift project. With that said, stock Firefox as shipped by Mozilla isn’t exactly privacy friendly without going to lengths to harden the browser. Mozilla collect an absolute ton of telemetry by default, complete with a unique identifier attached to each download. FF also comes with pre-installed addons with questionable privacy policies like Pocket.

I think concerns about fingerprinting are somewhat overstated, or at least over thought about. The reality is there’s an absolute ton of metrics that can be used to fingerprint a browser by advanced scripts and if a site wants to fingerprint you it will, and it doesn’t really matter if you’re using FF or Chromium. The only realistic way of avoiding this is by using browsers like TOR or Mullvad, which aim to all have the same fingerprint so you’ll be able to blend in with the crowd. Preventing naïve script fingerprinting is the best you can ever hope to do on any other daily driver browser, and addons like CanvasBlocker for Firefox or JShelter for Chromium are typically enough to prevent fingerprinting by opportunistic scripts.

Vivaldi is an awesome browser and the people and company behind it continue to inspire me with confidence that they’re truly committed to providing a Chromium-based browser that is as privacy conscious as it can be.

I’ve always felt very uncomfortable when people and news outlets describe someone as having “lost their battle” with cancer. To me it was almost a projection of weakness on that person for not “putting up a better fight” or something. I know obviously this is never the intention, but I think this highlights how the use of such language can be problematic.

It’s worth noting that the “trees planted” counter is basically an estimate as to how much ad revenue on average is generated from a user based on their number of searches. If you block ads at all, you’re probably not contributing to their revenue at all, thus planting nothing.

I like the idea, but don’t see it as worth sacrificing privacy or allowing ads. Tossing a few bucks every now and then to a charity might be a better option for some.

This reads like a low-quality AI curated article with “tips” that are absolutely useless.

I’d argue it’s perfect timing. Better that users across the broader fediverse know now that supporting Beehaw communities and helping them to grow with content won’t be in the best interests of the fediverse more broadly, and to put their time and effort into communities hosted elsewhere before they’d grown even larger.

In Mastodon there’s an option to keep a “live refresh” of the federated feed, or a static one that only updates when you refresh. For Mastodon timelines, live updates seem to make sense. In a system like Lemmy? Not so much, imo. I hope we get an option to turn live updating off. It’d probably help with server load too.

Interface feels way more snappy and responsive on desktop. Pages seem to load/render faster. Good update!