Wouldn’t the issue be executing the models to third parties without filters?
No idea if this is right but the same it would apply to Anthropic that they couldn’t run the model without the filter system having a chicken an egg problem. Can’t develop the filter without looking into the model.
I really want NixOS to succeed in becoming easy to configure, operate and onboard. I would like to avoid any other configuration management tool in my life again. In this way, you can have simple vm's and k8s for distributed use cases. Both that can be declared in code.
This is a hard no for me. This is the whole thing about reconciliation loop. You can just push something to the api/etcd and eventually it will become ready when all the dependencies exist.
Now, rejecting manifests because crd’s don’t exist yet is a different discussion. I’m down to have a cache of manifests to be deployed waiting for crd but if the crd isn't deployed, then a garbage collection alike tool removes them from cache.
This is what fluxcd and argocd already do in a way but I would like to
Have it natively.
Isn't this the whole point of SPIRE/SPIFFE?.
A workload can identify itself to a different trust domain as long as there's trust between the different domains and a policy that allows it.
This reads like paraphrasing of SPIFFE.
I’m down for it but I wonder of compromised devices that can figure it out how to keep the auth alive (or replicating user behavior). In those cases expiration still sounds like a good idea.
If there’s something I’m looking forward with end to end vibe coding tools like Github Spark, Lovable and others is getting rid of these suckers.
It would be easier to provide similar functionalities and customize them without major issues. Yes, it’s still not seamless enough for your average user but it’s heading in the right direction.
Ok, This is interesting. I need something alike that can measure whatever marijuana grow facilities generate.
A neighbor lives in disbelief their facility doesn't produce any smell but neighbors in a mile radius disagree with it. He is willing to set up measurements to reduce any impact but I don't have a way to collect real data beyond it's smelling. I always depends on where the wind is blowing but it's constant.
I feel you. In the late 00's/early 10's, downloading and getting American movies were fairly easy but getting the subtitles was a challenge. It was even worse with movies from other regions. Even now I know people that record conversations to be replayed using Whisper so they can get 100% the info from it.
Disclaimer: I'm not praising piracy but outside of US borders is a free for all.
I'm more excited I can run now a custom site, hook an MCP for it, and have all the cool intelligence I had to pay for SaaS without having to integrate to them plus govern my data, it's a massive win.
I just see AI assistant coding replicating current SaaS services that I can run internally. If my shop was a specific stack, I could aim to have all my supporting apps in that specific stack using AI assistant coding, simplifying operations, and being able to hook up MCP's to get intelligence from all of them.
Truly, OSS should be more interesting in the next decade for this alone.
If lovable, bolt.new, etc kept integrating with them, that's a money maker without needing to do much sales. There's a wave of AI tools that require somehow save state and Supabase provides that. I'm absolutely amazed others haven't jumped in the same ship yet.
I feel I've built something similar using fluxcd + cuelang. FluxCD allows having order through depends on and how you organize your Kustomization resource.
I still believe the FluxCD project needs a UI that matches what you can get from the cli. CLI has so many features that you might or might not get fully from the available UI's.
I believe github used to have a service like this but they shut it down.
I wish Gitlab and Github provide a paid api with this metadata so talent sources can reach put people based on contribution and experience.
> I've found the Nix ecosystem to be lacking, missing packages, wrongly built packages (from the official upstream), and out of date versions. Homebrew still outclasses Nix in this regard (quality over quantity).
That's also the case with the Docker ecosystem. On top of that, you need to take into account the base image, versions, etc.
At the end what I look for is for a project being able to build my source code with runtime dependencies and supporting tools that won't change overtime for the architecture that I need.
I feel Nix is eating their lunch. Even though Nix as a language could be tough, it's a simpler solution than Dagger.
It provides a shell, almost complete reproducibility and isolation can be added through containers.
Working with dependencies to build source code using nix is usually straightforward but having the right binary version that doesn't have the same love as major languages (i.e. terraform, flux, etc) is one thing Nix really needs to implement. Marcelo's package version search[1] is a way to discover the particular hash but then you need to explicitly use that nixpkgs version for that particular binary and do a lot of mental gymnastics in your nix files. Nix could implement a syntax where you define the package versions as attribute set and then internally does a discovery of the nixpkgs hash for that versions and installs it. Flox and DevBox follow this pattern but I don't see why you need and external tool where this can be embedded in Nix (the cli).
> For now, they are worth evaluating and discussing, but are not ready for us to delegate the precise task of creating reliable, secure, and scalable software that powers our society.
The good thing about vive coding is it avoids the software development lifecycle completely from the user perspective in a platform that has an integrated SDLC which means from defining idea to ensure visibility in changes to a runtime where the user can see it. In my mind, modifying without a hassle in a controlled environment is what users look for. Software development assisted by AI will be a thing for engineers but Vive coding is aimed for users outside of engineering.
I sadly see only a handful of companies being able to pull this off.
I really like this. I don't mind Internet acting like the Wild Wild West but I do mind there's no accountability. This is a nice way to pass the economic burden to the crawlers for sites who still want to stay freely available. You want the data, spend money on your side to get it. Even though the downside is your site could be delisted from search engines, there's no reason why you cannot register your service in a global or p2p indexer.
You can always rebuild the dockerfile, or create an account increasing your pull limit, or just host all the free infrastructure they’ve already built, or use competitors providing the same service with the risk of them doing exactly the same in the future.
The difference with docker hub and just mirroring a linux repo is docker made it really easy for people so they don’t need it to get into infra weeds but the complexity was always there.
I've been using plain git with a git server to sync several machines even though I have to execute a script to do it in each machine. If you see the vault is just the workspace plus markdown files. I didn't know you could add plugins to obsidian. This is interesting. I do wonder if this can be added to mobile - Android/iOS.
it means they can serve more with what they have if they implement models with deepseek's optimizations. More usage doesn't mean Nvidia will get the same margins when cloud providers scale out with this innovation.
There's going to be a whole new industry on reliability if this becomes reality.
I wonder how "you build it you run it" would evolve. Would we end up with ops figuring out how to remediate the code?. Would the remediation be done by whoever opened the ticket? Would the person who accepted the PR/MR be held accountable for this?.