You can. The point of having your agent keep track of it is that it will likely notice things you won't, and it can automate cataloging it with relevant metadata (prompts, environment, examples, etc.) that make it trivial to automate rerunning those tests when new models launch.
Fair point, but we still need people (like Linux enthusiasts) in Australia to buy these phones and complain to the manufacturer to add support for any missing features needed for 000, and work with the carriers to whitelist the devices. If no one buys these devices in the first place and no one complains about it, Linux phone makers would have little incentive to resolve the issue.
Maybe the Aussie Linux users could get together and work together with Linux Australia[1] to act as an intermediary and work something out.
I don't believe Linux Australia is the first port of call. Rather, conferences/meetups that are supported by Linux Australia would be the way to go. Basically, it needs to be very grassroots, and start with (capable) people who are genuinely interested in this and not distracted by other things that are a waste of attention. Any other strategy will likely be even more difficult and less likely to take fruition.
The crap part is a lot of niche phones got banned because you need to prove it can call triple zero not by default, so it'll be a real pain, and carriers don't really care.
I was deploying some dotnet app and it broke because the devs baked a config key into the image that was otherwise unset, which enabled it trying to start a SSL endpoint without a cert, thus breaking the app.
They're not all tooootally atomic, I have clustered things like libation+audiobookshelf, ollama+ds4+litellm, but I like that I can manage things almost entirely at the network and host level, generally atomically per service, and especially between services (eg homeassistant and the local ai).
It's DEFINITIVELY overkill, and fills up fast, but nix making everything near fully declarative to roll fwd/back or shuffle between proxmox hosts at any time makes for a clean and easy mental model. Both for me and the AI, because it can infinitely retry a nix flake config until it gets it perfect.
Sounds like a poster child for LXC containerization with Proxmox — all the host-level management of a non-ephemeral VM (including snapshots!), without the every-machine-has-its-own-kernel overhead.
I do have a couple LXC for the things that need tight GPU control. Ollama and DS4 permanently, and an ml-workbench that steals the 3090 from my Cachy gaming VM when I get it in my head that I could try implementing some cool gsplats paper haha.
I could definitely slim things down without disko, virtio, etc, and especially whole separate kernels.. but it's also not such a huge diff that I mind. I'm not adding new services all that fast anymore now that I've got my basics + wishlist set up, so I'll grab another box from the local pc recycler if I ever need space for another ~30 VMs some day rather than when I need space for another ~40-50 LXCs.
And in the meantime if OpenAI publishes a scary brag about how GPT-7 popped a shared kernel on accident I can be relieved that my private bookmarks repo isn't vulnerable while the internet burns down.
I use nix, but I assume the same goes for guix, you write a package or run it with something that emulates a FHS (like steam-run, don't mind the name) and hope it works.
Writing a package is not as bad as it sounds, nix and guix have very little difference between "package maintainer" and "user" so most users probably can package software. Normally copying something from nixpkgs or similar will get you most the way there.
There is a large gap between public domain and GPL. For starters if Copilot is emitting GPL code for closed source projects... that's copyright infringement.
Copyright infringement is emitting the code. The license gives you permission to emit the code, under certain conditions. If you don't meet the conditions, it's still copyright infringement like before.
Copyright infringement could be emitting the code in a manner that exceeds fair use.
The license gives you permission to utilize the code in a certain way. If Copilot gives you GPLed code that you then put into your closed source project, you have infringed the license, not Copilot.
> If you don't meet the conditions, it's still copyright infringement like before.
Licensing and copyright are two separate things. Neither has anything to do with the other. You can be in compliance with copyright, but out of license compliance, you can be the reverse. But nothing about copyright infringement here is tied to licensing.
To be clear: I am a person who trashed his Reddit account when they said they were going to license that text for training (trashed in the sense of "ran a script that scrubbed each of my comments first with nonsense edits, then deleted them"). I am a photographer who has significant concerns with training other models on people's creative output. I have similar concerns about Copilot.
But confusing licensing and copyright here only muddies waters.
Justine was kicked out of llama.cpp for introducing changes before the rest of the maintainers approved them.
Much drama has been had since then and I've lost interest in both projects.
It's just been exhausting wanting to build good software without ego in this space. Everyone is trying to get rich quick before the inevitable AI ice age starts and all these skills are again useless.
The last commit from Justine I can see to the llama.cpp repo is a week ago, so whatever drama there was appear to have been at a minimum partially resolved.
why would being russian make it this? it could be if it was made in any country. they did this attack once, okay? but its not like other countries dont pay attention.
reply