I render my former answer. There is no language that can’t.

It sounds like you have little or no programming experience? You’ll need to start with learning to code. Lots of people recommend Python for beginners, though I’m not a fan personally of the language. That said there are a ton of tutorials for it.

Apparently it doesn’t.

Whatever language you want, and then math. Lots of matrix math. Get a book on the math behind 3D graphics.

I highly doubt the law is settled on this topic and you’re assuming it is. I can’t see the courts accepting that your duplicate version of my work created through “magic” is not going to be a violation of my copyright. Especially if my work was included as input to the “magic box” that created the output.

That doesn’t make it “no longer copy-written” though. The original copyright holder retains their copyright on it. I can’t see any court ruling otherwise.

Section 1 says you’re using freedns.afraid.org though.

Aye - that’s another reasonable use of the phrase.

Ugh really? I haven’t seen that myself but that’s frustrating.

Non-containerized applications. Not in a container. It’s not complicated. Running “on bare metal” sounds cool but it’s a wildly inaccurate description. Containerized applications run on the system natively just like non-containerized applications. So if one of them runs “on bare metal” then then others do as well.

But historically “on bare metal” is used for embedded or micro-controllers where you don’t have an OS.

• Users will stop referring to non-containerized applications as “running on bare metal”

What “other technology” is going to make sure your API doesn’t have SQL injection and bad authentication vulnerabilities?

You know what? Rather than over-complicate things you can probably just check that filenames contain a small set of white-listed chars. [a-zA-z-._] (and != ‘…’ or ‘.’) or something.

And one other nit-pick if you’re up for more code-review - your authentication logic should probably be inverted:

if !ok || user != session.config.username ||
				pass != session.config.password

I’d change that to be something like

if ok && user == session.config.username && pass == session.config.password {
   // do login
} else {
   // not auth
}

There’s a whole category of security errors where an exception in logic like that causes the code to skip the “you’re not allowed” logic and go right to the “you’re allowed!” block. It’s more of an issue with languages that support exceptions but it’s still considered a best practice generally (it’s also typically easier to read).

“Security” is not just “ssl”…

Ah - I missed that other parms were keys. Still - best practice is to sanitize all user inputs. Try throwing lots of file-path-like args at it to see what it does. it’s a historically tricky problem so there should be some libraries that help with it.

Happy 2026! And happy hacking!

You try using “…/…/…/…/…/etc/passwd” as the filename in your requests? I don’t see anywhere where ‘…’ is escaped or removed from file strings. Sending untrusted filenames directly to file operations without scrubbing and sanity checking is very dangerous and potentially allows a malicious user to read and overwrite any files the application has permissions for.

I think you should make it more clear in your docs that this is wildly insecure and should be restricted to “tinkering” usage only.

That said it seems like a fun project to write.

UDP — Blocked. Deprioritized. Dropped. “Security risk.”

It’s this actually a thing? I’ve never seen any corporate network that blocks UDP. HTTP/3 will even rely on it.

Since it’s just to monitor AI agents streaming the text is exactly what they want. You could watch them over a modem.

Ssh port forwarding and socks proxying. Unless they block port 22.

Edit: If they do block port 22 run ssh on port 443.

AI is so much faster than reading docs. And you get context specific responses that you can drill into. When used correctly it’s very useful.

This was using it… incorrectly though…