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.

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

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.

At some point, you lose productivity and reduced work weeks have shown increases in productivity can happen.

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

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’ve been disappointed in general with the XPS line in recent years. Dell has made some keyboard changes that I am not a fan of:

• A touch bar instead of function keys? Why? Did they not learn from Apple’s mistake?
• Changing Fn + Left to Page Down instead Home? And Fn + Right to Page Up instead of End? Once again, why?

I’ve been purchasing the XPS line of laptops since 2013, but I stopped as soon as those changes landed and the Developer Edition of their laptops shipped with inferior hardware compared to the Windows ones.

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!

Valid, but not standard and more inconvenient.

Additionally, you act like query strings can’t be used to track you when they certainly can.

Most of the advantages of Gemini are implemented in the client and not the protocol itself.

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.

The issue is that some of those techniques are only useful after the client has rendered the content rather than before.

You can tinker in the image in a variety of ways, but make sure to preserve your state outside the container in some way:

1. Extend the image you want to use with a custom Dockerfile
2. Execute an interactive shell session, for example docker exec -it containerName /bin/bash
3. Replace or expose filesystem resources using host or volume mounts.

Yes, you can set a variety of resources constraints, including but not limited to processor and memory utilization.

There’s no reason to “freeze” a container, but if your state is in a host or volume mount, destroy the container, migrate your data, and resume it with a run command or docker-compose file. Different terminology and concept, but same result.

It may be worth it if you want to free up overhead used by virtual machines on your host, store your state more centrally, and/or represent your infrastructure as a docker-compose file or set of docker-compose files.