Your public website / blog? Sometimes you want services that are accessible publicly, like your observability and logging servers (eliminates the VPN point of failure).
I own one and there's nothing shameful about it. It's basically CNCed to Apple's standards, just without the logo. The cool thing is since Studio Displays work on Windows too, with Thunderbolt motherboards you can have a setup that's visually the same as a Mac but is actually a PC.
P.S. Does anyone know how well Studio Displays now work on Linux? The best I could get it to work was on Ubuntu, where it basically worked out of the fresh install. X11 KDE on Fedora was a close second. Couldn't get it working on Wayland whatsoever.
Agreed, but I'm making a distinction between the platform (whether it be Cloudflare Moltworker or a Mac Mini), which a human chooses for the agent to run on (for now), and tools designed to be discovered and consumed by the agents themselves (e.g. code.storage, AgentMail).
I have a suspicion most of these types of agent-targeted SaaS will die out once the human equivalents implement their agent layers / MCPs.
Agents having no way to pay for their use is one thing; lack of deep integration within the business domain is another (e.g. if you're a Git provider, you'd probably want to offer CI/CD, PR workflows, release management, publicly discoverable repos etc., and boom - you just copied GitHub)
I'm so sorry for you and your wife's loss. At the same time, I'm struck by how strong your wife and you are navigating this tough situation. From an Internet stranger to another, may the loving memories of your daughter live on.
Why the condescending tone, OP has a point. Techniques like RigAnything[0] exist - whether this is within the scope of this project is another topic, but this seems like a reasonable request to me (especially considering how many x_2_y-named projects are ML related)
I remember Synology ships their NAS with custom vendor syscalls that used unassigned syscall numbers at the time, but those numbers are now clashing with real syscalls - causing undefined behaviour when running arbitrary code (e.g. Docker)
So TL;DR only implement custom syscalls if you intend to maintain for all of its consequences in the future.