Funny that you pointed this out. I didn’t actually know about the two distinct sites. The “missing” hyphen in my url was a confusing accident; I just assumed they revamped the website poorly 🤣. I had to check the install instructions and GitHub link before posting

Not to be confused with helix the TUI text editor

Honestly, I avoid helm charts as much as possible. My preference is raw manifests + kustomize, deployed by Argo

I absolutely understand not liking opt-out telemetry. Do people generally not like opt-in telemetry? Is this really why the community shifted to a different project?

OP, my personal preference is to supply raw k8s manifests in a project. These are far easier to manipulate using tool called kustomize. Just think of it as an alternative to helm. The big thing is that kustomize removes the need for forks because it can run against manifests defined by a url.

It looks safe to me in the sense that I don’t see any malicious code in here. I don’t think the committee is trying to sneak in security hopes or similar. So all good on from that perspective.

It’s a very simple helm chart which is consideration! Here’s the thing with charts. They’re meant to be an official means of distributing your app’s manifests for k8s. One package with all runtime needs defined. If the chart supports every tweak I need, then it’s great! If it doesn’t, then I need to modify it myself. This usually means forking the project, making edits, and templating from the fork. It’s a lot of overhead for end users. If the maintainer is willing, it’s so much easier to create an issue or submit a PR with the needed changes.

Your project has some stars and forks. People are likely using it. Grats! The helm chart doesn’t like meet everyone’s needs and I would expect this to spur some extra issues and PRs. Is that good or bad? That’s up to you!!

I expect someone will start a business to remove that aftermarket

There’s cryptpad though I don’t have a clue how complicated it is to manage. But it’s a decent user experience.

Well that’s fair. I had to look closely. It’s a ready made soup. Not just spice. I’m finally getting this post now.

Oh ok. I didn’t realize it’s specifically for soup. But also, it’s probably tasty in some soups like a carrot or butternut squash soup 🤣

I’m not following this one yet. What’s wrong with the pumpkin spice?

If you’d like to learn more about Haptic, why it’s being built, what its goals are and how it differs from all the other markdown editors out there, you can read more about it here.

As others have noted, the app doesn’t work on mobile yet. Anybody willing to share the content here for mobile users?

That basic idea is roughly how compression works in general. Think zip, tar, etc. files. Identify snippets of highly used byte sequences and create a “map of where each sequence is used. These methods work great on simple types of data like text files where there’s a lot of repetition. Photos have a lot more randomness and tend not to compress as well. At least not so simply.

You could apply the same methods to multiple image files but I think you’ll run into the same challenge. They won’t compress very well. So you’d have to come up with a more nuanced strategy. It’s a fascinating idea that’s worth exploring. But you’re definitely in the realm of advanced algorithms, file formats, and storage devices.

That’s apparently my long response for “the other responses are right”

Wait. Who’s genocidal here?

Unfortunately, I’m not familiar with installing Bitwarden so I can only offer general advice.

Port conflicts happen at runtime, not when software is installed. In general, you should be able to install as much software as you’d like that all relies on port 443 but only run one at a time.

If you’re seeing port conflicts when installing Bitwarden, then I suspect that something is starting the app after the install is done. If this is right, then maybe you can disable the automatic start. Or maybe you can ignore the error at install time, then configure the app, then start it.

Strange. I’m not exactly keeping track. But isn’t the current going in just the opposite direction? Seems like tons of utilities are being rewritten in Rust to avoid memory safety bugs

I recently discovered k3d. It’s a light wrapper around k3s, which is kubernetes on docker. It’s amazingly easy to use! If you have docker installed, you can learn the commands and create a k8s cluster in under 5 minutes.

For anyone like me that likes k8s, k3d is a fantastic alternative to docker compose!

The simplest way is certainly to use a hosted service like GitHub Pages. These make it so easy to create static websites.

If you’re not flexible on that detail, then I next recommend Go actually. You could write a tiny web server and embed the static files into the app at build time. In the end, you’d have a single binary that acts as a web server and has your content. Super easy to dockerize.

Things like authentication will complicate the app over time. If you need extra features like this, then I recommend using common tools like nginx as suggested by others.

I recently dug into this because I accidentally trashed my wife’s OS which was encrypted with bitlocker. PITA btw and I couldn’t beat the encryption

Bitlocker encryption key hash is stored in 2 possible places. First is an unencrypted segment of the encrypted drive. This is bad because it’s pretty easy to read that hash and then decrypt the drive. The second place is on a Trusted Platform Module (TPM) which is a chip on the motherboard. This is better because it’s much more difficult to hack. It can be done but requires soldering on extra hardware to sniff the hash while the machine boots up. Might even be destructive… I’m not sure.

Either way a motivated attacker can decrypt the drive if they have physical access. For my personal machines, I wouldn’t care about this level of scrutiny at all.

Anyways you can see if any open source solutions support TPM.

I recently changed my personal email. Updated every account I knew of (thanks Bitwarden!!). Updated about 120 accounts, closed maybe 20, and 5 or so can’t be changed.

Of the ~120 that I changed, I think about half of them were easy to change. Not much confusion. There was a clear enough process. Etc. Most of the rest were difficult to change but I could do so on my own eventually.

Something like ~10 accounts required emails and phone calls to support.

A few were terrible. Things like updating my email address in 10 places for one account. Or the updates go fine but just didn’t work, requiring many repeat attempts or phone calls.

So it’s a real problem in my experience. But not the norm. Maybe 1/10 rather than 9/10