Last night you could literally query and get factual information about election results; but today it wont even tell you who the president was in 2000.

There's a major censorship issue here.

Today it responds with "America does not provide campaign or party information."

The people on Reddit were right.

If you want to design a system specifically to make sure you're not going to get stonewalled for sending me an emdash, you build and maintain a set of permissive rules for sending/reading to avoid my blacklist of people I'll never work with.

Once you got API stuff sorted, just throw a cronjob at it or build a service for that stuff.

^ There be prompts all over the place here, obviously. Realistically your MCP server will end up hacking on POP3.

What features you want it to have? The thing you're saying is super vague, I would just say that one belongs in cloud.

If it must run things on the user's machine, it's gotta be in a rootless container and not be root inside the container. All tools belong in the container. Folder access explicitly configured by the user.

Like I already did this for my local AI: https://github.com/SamInTheShell/loom

It's not perfect or even done, but it works and it shows the security model that should be standard for aligned models we're running.

Unaligned models, absolutely different story.

Also VM is better than container for security, but containers are a bare minimum for me.

When you're a company running around with more than a few billion in the vault, you have no excuse for the level security negligence going on at every phase of rollout.

I gawked at Cursor executing a python script one time and decided enough was enough, I don't raw dog these tools anymore because their developers are the dumbest people to task with security work. They just don't care.

This is all amateur hour shenanigans.

I don't feel this is hacky or even a work around. Just different promises on what goroutines are vs threads/concurrency/processes in other languages.

Exit and panics are promised at the process level in Go.

Regarding the JVM and GC. Good luck with that? Every Java application I've seen in the wild when I supported JVM seemed to never release any ram it allocated. Ever. If it used 1G and even after free, the JVM decided that was going to be used again and wouldn't release it.

It would be hard to sell me on wanting to use Java again (people can pay me enough to do it, but I hate it). Which kinda sucks since Apache Foundation has a ton of really cool projects using it. Kotlin maybe, but I have no real use cases where it would be better than anything else I know right now.

But Go itself comes with it's own runtime built into the final binary. It doesn't work well in some use-cases, I mentioned some of the draw backs in a couple other comments if you want to dig those up.

Also I saw some of the other comments. Channels are ultimately just used for message passing and aren't that complicated. You also can use mutexes or some other locking pattern. There's some primitive atomic structures available that solve some use-cases preventing you from even have to having to really deal with working between goroutines.

It was literally enabling a flag and running some commands to do some really quick exports.

Dealing with the JVM though, heap dumps are slow to process and the UI I had to download was very clunky. I don't know if there are better tools, but even if there are the path to just doing it isn't straight forward.