llarsson

The ability to sandbox Google Play Services (if you need it, but realistically, you probably do) and to simply not assign it more permissions than it absolutely needs is awesome. I run it with very restricted permissions, where it by default requests every single permission it can. In stock Android, it has all those, and you can't limit it. Just that is worth it for me.

Other solutions that use the same underlying technology:

https://fidesmo.com/consumer/wearables/

Imagine what can happen if the French and other governments would start pouring all the money into developing that further in the open, rather than just giving it all to Microsoft instead?

Built in functionality that may offer something similar:

https://linuxhandbook.com/cdpath/

Because it's been trained on decades of StackOverflow and forum posts. And because while some command line tools go in and out of fashion, quite a lot are very stable, so their use will show up all the time in the training material.

Since it's all statistics under the LLM hood, both of those cause proven CLI tools to have strong signals as being the right answer.

A question because I'm not using speech-to-text, but find it intriguing (especially since it's now possible to do locally and for free).

How have your computing habits changed as a result of having this? When do you typically use this instead of typing on the keyboard?

There are already APIs being developed that assume a browser has an LLM either inside it or otherwise available, see for instance https://developer.mozilla.org/en-US/docs/Web/API/Summarizer_...

So they pretty much have to ship one, to stay relevant. And they are privacy-focused, so I'm happy they are not just using ChatGPT or whatever under the hood to implement support.

Attention is all you need, as the transformative paper (pun definitely intended) put it.

Unfortunately, you're only getting attention in 3 second chunks.

Telling people to use nano would of course have been next to impossible. Much easier to rewrite a DOS-era editor in Rust, naturally.

That's also where etcd came from. It really felt, to me, like the precursor to Kubernetes.

Help me understand what this means to e.g. GrapheneOS, please. Will it be able to exist and just have to wait longer for updates or will it be in real jeopardy?

A GameBoy emulator written in PHP would certainly piqued my interest, but more like a morbid curiosity than anything else. :)

It is interesting that this relates exactly to everything that goes as "cloud native" these days, without really mentioning the fact that due to Kubernetes and the Cloud Native Computing Foundation's huge landscape of open source software that targets specifically Kubernetes, you can have a comprehensive platform on "any" infrastructure. On-premise, private cloud, public clouds that are in the EC2/S3 era of services (VMs and object storage)... it doesn't matter. You can literally run the same database that powers YouTube, it's freely available and operates great on Kubernetes.

Yes, the problem is that someone has to manage it all (full disclosure: I work for Elastisys, a company exactly in the space of fully-managed application platforms on top of the infra operated by others).

But the fact that smaller cloud providers haven't had the money to invest in their capabilities to offer managed services to the same degree as the enormous hyperscalers isn't exactly impossible to overcome. In fact, it's never been more possible. Other comments here show that very well, too. And that the particular choice of identity management services is perhaps not the best for showing where the hyperscaler options shine.

Do you need fancy looking ones or just barebones QR codes? Because the latter you can just get from the qrcode Python package and simply go "qr news.ycombinator.com > hn.png" in your terminal.

https://pypi.org/project/qrcode/

That's right, and it's also why you see Kubernetes distributions popping up.

That way, someone has already done all the configuration of various plugins and components for you. For instance, the major clouds that all let you easily start with their Kubernetes services and that they integrate well with the logging and monitoring systems, IAM, server/node provisioning, etc.

Or ones that are not tied to any particular cloud provider, and perhaps focused on security (full disclosure: I work for Elastisys, who makes exactly that) or ease of use.

I'm sure we will see more and more such efforts in this space, exactly because cobbling together something yourself from scratch (basically just a control loop runner, as you said) is neither very appealing when you think about ongoing maintenance, nor very cost-effective for businesses to spend engineering time on.

As writing advice, it went from very understandable and approachable to stuff like:

"You can get this property by stapling HKDF onto your protocol (once for key derivation, again for commitment). See also: PASETO v3 and v4, or Version 2 of the AWS Encryption SDK.

It may be tempting to build a committing AEAD scheme out of, e.g., AES-CTR and HMAC, but take care that you don’t introduce canonicalization risks in your MAC."

I would almost suggest breaking stuff like this into two articles, one which is very technical and correct, and one that conveys the high-level message. The high-level one can link to the technically correct one whenever the urge would come to explain something more fully.

Can't do it myself, but I've heard that people listen to typical traditional "video game music" for this purpose. Fast, upbeat, and never something you need to focus on, but rather, it just helps you keep up the concentration.

...if you're the type of person who can listen to music while working, that is.

It's fast, but laughably inaccurate. Open shirt? Windsor knot. Hand against chin? Stethoscope. Cell phone close to face? Harmonica.

You could have just had your Geek Code in there to be efficient.

https://en.wikipedia.org/wiki/Geek_Code for the people who didn't get to experience it

In tons of enterprise and just general office settings, you'll be given a CSV file, rather than a database dump. Heck, even scientific lab equipment will output CSV for you. It's basically the lowest common denominator for all kinds of tabular data.

So anything that makes using CSV files easier with your product is likely going to be a welcome change for a lot of people.

Realistically, your database engine can probably ingest the CSV file in a simple import statement, so you're likely 98% done already with this. :)

The point of Kubernetes was to make "run this software on a cloud" trivially compatible across clouds. No specialized code that is needed for load balancers, storage, networking... you should be able to take your containerized application and the set of YAML files that describes what you want to do, and they work on "any" cloud.

As long as you don't rely on implementation details like a specific Ingress Controller that needs special annotations, this is exactly what Kubernetes does, and the reason why you have Helm Charts that don't need to take into consideration which the underlying cloud is.

Going back to what we had before, you had to be very aware of exactly which cloud provider you'd use. And since AWS had about 80+% of the market then, that meant that instructions for how to run things on Google's cloud were not very good, if they existed at all.

The fact that they resorted to writing crap these days with AI is what is making them lose relevance, not that they have been in the business for a long time, and have thousands upon thousands of articles.

CNET used to, perhaps not be cool, but it certainly was a place you'd go get tech news from every once in a while. Just imagine they were huge enough to buy download.com, back then, even! For a while, they were essentially *the* place you'd go for downloads of various shareware stuff.

Now, it's a ghost town of a site with AI-written junk.

You can be an ultra nerd on Linux and go this with the networking QoS tools: https://tldp.org/HOWTO/Traffic-Control-HOWTO/components.html

If their romantic significant others are fine being number two in this way, and it's all consensual, then they should do it and move their lives the way they want to.

I would personally not be OK with this setup with a romantic partner (neither as one who would see a friend as my number one or if the romantic partner did with someone else), but that's obviously not supposed to limit them in any way, since I'm not part of their equation.

All relationships could do well with clear boundaries, understanding, and a ton of communication to continuously maintain that as relationships evolve.

Semantic difference.

Brave takes away ads from pages.

Then, it shows other ads in other ways:

https://brave.com/brave-rewards/ https://brave.com/brave-ads/ad-formats/

So while the statement that it "replaces ads with their own ads" is technically false (the ads are not injected into the web sites in place of the blocked ones), it's still a sloppy but mostly correct way of pointing out that the business incentive behind Brave's ad blocking means that the goal isn't abolish ads as a concept altogether. The point is still to show ads if companies want to pay for it.

Stuff like the Language Server shows that people are interested in making new stuff work well with our old beloved editors. I have faith.

Already been hugged to death.

The status quo was "months ahead of time", but their startup idea was to cater to "last-minute" types of travelers, and challenge that status quo.

Have a sudden urge to have a nicely planned and well-put together weekend in a new cool place? Too much of a hassle to deal with yourself, maybe, but a whole lot nicer if you can just see what someone has packaged for you.

Cool idea, and would love to take it for a spin!

Feedback: the MongoDB dependency is annoying, from an enterprise (self-hosting) perspective. Due to their licencing, you can't have a managed service provider host it for you (unless that provider is Mongo itself). I have not looked into what data you store, but I can't imagine it's that schema-less at this point, so perhaps it could be possible to store in an SQL database instead? Or in PostgreSQL via its JSON support?

In this case, I would recommend that you get an employer-specific GitHub account, so you can compartmentalize it that way. A bit of a hassle, yes, but then, you're definitely not tying yourself in git history to that employer for your entire career.