That would be great. I frequently have to click the link and navigate to a home page for a meaningful description. Here’s the opening statement from Koto’s README on GitHub.

Koto is a simple and expressive programming language, usable as an extension language for Rust applications, or as a standalone scripting language.

This is the first thing I need to read to understand if I should or should not care about the project and its new release.

There are many reasons to use k8s. Managing multiple nodes is one good one. But more importantly, k8s gives you an api-driven runtime environment. It’s really not comparable to docker compose.

Yea I’m not a fan of helm either. In fact, I avoid charts when possible. But kustomize is great.

I feel the same way about docker compose. If it wasn’t already obvious, I’m biased in favor of k8s. I like and prefer that interface. But that’s just preference. If you like docker compose, great!

There’s one point where I do disagree however. There are scenarios where a local k8s cluster has a good and clear purpose. If your production environment runs on k8s, then it’s best to mirror that locally as much as possible. In fact, there are many apps that even require a k8s api to run. Plus, being able to destroy and rebuild your entire k8s cluster in 30s is wonderful for local testing.

Edit: typos

Honestly, k8s is super easy and very lightweight to run locally if you know the rights tools. There are a few good options but I prefer k3d. I can install Docker/k3d and also build a local cluster running in maybe 2 minutes. It’s excellent for local dev. Even good for production in some niche scenarios

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

I use proton vpn and Firefox Focus on iOS. I’m not sure which of them is doing the heavy lifting, but I rarely see ads on my phone.

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”

deleted by creator

I like that Meta is fined for this bad practice. But why are they paying the state? How does this help anyone that was actually victim of the facial recognition?

I can see an argument based on how state funds help state residents. But it still doesn’t really feel right to me.

A real tangential thought: What if fines claimed by the state didn’t increase the states fund? What if those funds reduced the tax burden of residents from the bottom up?

lol thanks for the answer. This is the really relevant bit isn’t it? My Linux machines have also never died this badly before. But I’ve seen windows do it a number of times before this whole fiasco.

This is funny timing for me. I mentioned something related to my wife yesterday. When I was a kid, my perception of other countries was completely ridiculous. Low tech, uncivilized, impoverished, etc. compared to the USA. It took way too long for me to achieve a more realistic perspective of foreign countries at large. I’m not sure who to blame for this but the they surely belong to the previous generation or two.

What’s the user experience like there? Are you prompted to do it if the system fails to boot “happily”?

I’m familiar enough with Linux but never used an immutable distro. I recognize the technical difference between what you describe and “go delete a specific file in safe mode”. But how about the more generic statement? Is this much different from “boot in a special way and go fix the problem”? Is any easier or more difficult than what people had to do on windows?

A complicated plugin ecosystem (e.g. Jenkins) makes for a terrible use experience. It’s annoying to configure a bunch of config files. Managing dependencies can be a complete nightmare. these problems also complicate your ci/cd.

So I’ll offer a slightly different answer. I prefer a single file instead of splitting up the config. And I’ll use OpenTelemetry as an excellent example of why. the plugins are compiled right into the app binary. This offers a ton of advantages, including a great reason to merge all of your app configs in a single file.

This really only works well if you have a good app though.

Ya this is definitely one to maintain some skepticism about. People are criticizing the API’s security in other posts.

The EU is a large enough governing body to have a significant global impact. And I truly appreciate the progress it makes on important subjects.

However, it’s still not effective enough. Apple doesn’t allow third party app stores in countries outside the EU.

Exactly. There is a general need to destroy and rebuild a system but it is often dangerous and costly. Especially with regard to a system of laws and government. Improving the system more naturally is far more safe and more achievable at smaller scales.

Wow. I 100% agree with you here.

There’s an element of trust when you buy a product. You trust that the product itself isn’t malicious and is intended to help you in some way. E.g. “This food is safely prepared and won’t poison me.” Harvesting user data and advertising really violate that trust.

Though it is worth noting that we don’t buy web browsers. We simply use them for “free“.

Exactly. It sounds like Mozilla is trying to protect those that aren’t willing or able to protect themselves. It’s a noble reason to do just a little bit of evil. This is roughly the source of my mixed feelings on the subject.