21–30 of 41 posts
I'm not sure the "journos" from Techradar are too familiar with how networks ... work. IPv4 requires an inbound NAT these days to work at all globally, unless you actually have a machine with a globally routable IP. There will probably be a default deny firewall rule too. I do remember the days before NAT ... IPv6 doesn't require NAT (but prefix translation is available and so is ULA) but again a default deny is like…
Fun fact! On macOS you can expose privileged ports ( But ONLY if you don't bind the listening port to any interface. So you try to create a listening port on localhost (e.g. 127.0.0.1:443) under a non-root account you get a permission error. Edit: the thing is, you CAN expose "0.0.0.0:443" without root privileges!
How exactly are the ports "exposed" if they can't be bound to an interface?
Fun fact! On macOS you can expose privileged ports ( But ONLY if you don't bind the listening port to any interface. So you try to create a listening port on localhost (e.g. 127.0.0.1:443) under a non-root account you get a permission error. Edit: the thing is, you CAN expose "0.0.0.0:443" without root privileges!
it's called a privileged port and it's been like this for decades, on every system, ever. Here's a reference to this "macos feature" from 1995: https://www.w3.org/Daemon/User/Installation/PrivilegedPorts....
- you ll be surprised how many OLLAMA API KEYS [you can find here]( https://github.com/search?q=%22OLLAMA_API_KEY%22&type=code&p... ) its 2026 and this technique still works. I wonder if github supports regex search
example:
$ OLLAMA_HOST=http://47.101.61.248:9000/ ollama run gemma3:27b "outline ww2"
Many appear to be proxies. I'm familiar with some "serverless" architectures that do things like this https://www.shodan.io/host/34.255.41.58 ... you can see this has a bunch of ollama ports running really really old versions
You can pull down "new" manifests but very few ollamas are new enough for decent modern models like glm-4.7-flash. The free tier for the kimi-k2.5:cloud is going to be far more useful then pasting these into you OLLAMA_HOST variable.
I think the real headline is: "thousands of slow machines running mediocre small models from last year. Totally open..."
Anyways, if codellama:13b is your jam, go wild I guess.
- you ll be surprised how many OLLAMA API KEYS [you can find here]( https://github.com/search?q=%22OLLAMA_API_KEY%22&type=code&p... ) its 2026 and this technique still works. I wonder if github supports regex search
/it does like this/
[1] https://www.glukhov.org/post/2025/09/ollama-enshittification...
To not even be able to disable data being exfiltrated with their automatic updates is terrible behavior.
I ironically found out about this website from Mr Robot tv show.
Earlier quoted context omitted.
Yes the binding interface can be specified, but the default for -p 11434:11434 is 0.0.0.0. IMO the default should be 127.0.0.1 and the user should have to explicitly bind to all via -p 0.0.0.0:11434:11434.
Apparently been that way for a while haha https://github.com/moby/moby/commit/1cbdaebaa1c2326e57945333...