xcjs

Thank you! I was struggling to remember the proposal name.

Google was working on a feature that would do just that, but I can’t recall the name of it.

They backed down for now due to public outcry, but I expect they’re just biding their time.

Not with this announcement, but it was.

It depends on the model you run. Mistral, Gemma, or Phi are great for a majority of devices, even with CPU or integrated graphics inference.

Show me a music store I can purchase music from on my phone through an app, and I’ll purchase it.

I’m also going to push forward Tilda, which has been my preferred one for a while due to how minimal the UI is.

Or maybe just let me focus on who I choose to follow? I’m not there for content discovery, though I know that’s why most people are.

I was reflecting on this myself the other day. For all my criticisms of Zuckerberg/Meta (which are very valid), they really didn’t have to release anything concerning LLaMA. They’re practically the only reason we have viable open source weights/models and an engine.

That’s the funny thing about UI/UX - sometimes changing non-functional colors can hurt things.

My go-to solution for this is the Android FolderSync app with an SFTP connection.

I mean, sysvinit was just a bunch of root-executed bash scripts. I’m not sure if systemd is really much worse.

Systemd was created to allow parallel initialization, which other init systems lacked. If you want proof that one processor core is slower than one + n, you don’t need to compare init systems to do that.

Correction: migrated to GitLab, but I don’t expect they’ll want to keep it there.

The Nuzu repository is already wiped.

With UI decisions like the shortcut bar, they really don’t. I switched to another SMS app because I couldn’t stand it.

I…do not miss XP, but I understand the nostalgia attached to it.

I learned a lot of technical skills on XP, but that’s what made me appreciate the architectural decisions behind UNIX-likes all the more.

Of course!

The Docker client communicates over a UNIX socket. If you mount that socket in a container with a Docker client, it can communicate with the host’s Docker instance.

It’s entirely optional.

There’s a container web UI called Portainer, but I’ve never used it. It may be what you’re looking for.

I also use a container called Watchtower to automatically update my services. Granted there’s some risk there, but I wrote a script for backup snapshots in case I need to revert, and Docker makes that easy with image tags.

There’s another container called Autoheal that will restart containers with failed healthchecks. (Not every container has a built in healthcheck, but they’re easy to add with a custom Dockerfile or a docker-compose.)

It’s really not! I migrated rapidly from orchestrating services with Vagrant and virtual machines to Docker just because of how much more efficient it is.

Granted, it’s a different tool to learn and takes time, but I feel like the tradeoff was well worth it in my case.

I also further orchestrate my containers using Ansible, but that’s not entirely necessary for everyone.