I'm keeping an eye on Ollama's service offerings - I don't think they're in enshittification territory yet, but I definitely share the concern.

I still don't believe the other LLM engines out there have reached an equivalent ease of use compared to Ollama, and I still recommend it for now. If nothing else, it can be a stepping stone to other solutions for some.

ಠ_ಠ

That's not quite the same - that gives you the appearance of being a local device, which is enough to fool the restriction.

Their policy and technology enforcement is to charge for remote access, not relaying.

It's the official feedback form from https://developer.android.com/developer-verification

You didn't confirm anything.

Let Google know what you think: https://docs.google.com/forms/d/e/1FAIpQLSfN3UQeNspQsZCO2ITkdzMxv81rJDEGGjO-UIDDY28Rz_GEVA/viewform

If it's peace of mind that you're after, you can never go wrong with a backup.

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.

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

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 tried to take hourly snapshots of an already-large Minecraft world using Git, but after a few years of snapshots, the repository became corrupted.

One of the issues was that regardless of any player-based changes that occurred, the spawn regions were always different as they were always loaded in memory.

It doesn't quite say that, but I think the meaning is essentially the same: "Don't choose a name after a project unique to that machine." - RFC 1178

For my homelab, I think that's fine to do. I'm unlikely to have multiple Plex servers locally, for example, and if so, numerically naming them is fine - I provision with Ansible, and if I'm at the point where I'm having sequentially numbered hosts, they'll be configured as cattle anyway. Also, having the names reflect the services a host provides makes it easier to match in my playbooks.

I think it's a better scheme than turning to mythology, fiction, or animal species, which oddly enough RFC 1178 does encourage you to do.