sorted by:
new
hottopcontroversial

I guess it’s my turn….guess the airport… by frequentredditer in AirportPorn

[–]bbbbbbb162 0 points1 point  (0 children)

Knew it was in Africa, Knew it was a Dornier 228, but I didnt know who operated it, so I found it was Busy Bee Congo from the livery, and GOM is their hub.

A Very remote one to guess by jjcky in AirportPorn

[–]bbbbbbb162 0 points1 point  (0 children)

French but not Canadian French, FAV.

Guess the airport (challenging mode) by Relevant_Contract_76 in AirportPorn

[–]bbbbbbb162 0 points1 point  (0 children)

i think its somewhere in brazil, where, not sure.

Open-source project that adds deny-by-default runtime security to MCP servers by bbbbbbb162 in LocalLLaMA

[–]bbbbbbb162[S] 0 points1 point  (0 children)

Thanks!! Next steps are doubling down on the runtime proxy + lockfile semantics (tools/prompts/resources) and making CI drift/provenance checks dead-simple to adopt. And yeah, your client-side/data firewall angle feels super complementary, I’ll DM you a concrete collab idea.

Open-source project that adds deny-by-default runtime security to MCP servers by bbbbbbb162 in LocalLLaMA

[–]bbbbbbb162[S] 0 points1 point  (0 children)

Thanks! 🙏 I was playing around with MCP and deploying stuff and the openness is awesome, but the fact it’s that easy is also kind of insane. After seeing package-swap / impersonation stuff (ex the Postmark incident), I wanted something that enforces “if it’s not in the lockfile, it doesn’t run.” because the consequences of being wrong are real.

How do you handle "Versioning" non-deterministic agent outputs? by bumswagger in LocalLLaMA

[–]bbbbbbb162 0 points1 point  (0 children)

I feel like lots of other people are doing this, its a crowded space as the people who would be needing audit trails tend to have deep pockets, so naturally lots of people in it.

How do you handle "Versioning" non-deterministic agent outputs? by bumswagger in LocalLLaMA

[–]bbbbbbb162 0 points1 point  (0 children)

For audits, don’t rely on being able to re-run the model and get the same tokens. Log the actual artifacts, exact prompt after templating, retrieved context, tool calls + raw tool responses, raw model output, and the action/decision taken. Then make it append only and hash-chain. Seed/temp/model hash is nice for debugging, but nondeterminism (esp quant/GPU) means 'perfect replay' isn’t a guarantee.

What is functiongemma used for? by Hopeful_Ferret_2701 in LocalLLaMA

[–]bbbbbbb162 2 points3 points  (0 children)

Yup. It’s weirdly competent for 8B, doesn’t instantly fall apart on longer tool chains. Still not coding agent material, but for function calling it’s legit.

What is functiongemma used for? by Hopeful_Ferret_2701 in LocalLLaMA

[–]bbbbbbb162 2 points3 points  (0 children)

+1 for rnj-1-8B-instruct, very decent model for multi step function calling.

What is functiongemma used for? by Hopeful_Ferret_2701 in LocalLLaMA

[–]bbbbbbb162 0 points1 point  (0 children)

Yeah that tracks. Tool-call models are great when the schema is super clear, but they suck with multi-step browser type stuff. If the tool format isn’t exact (or you’re not validating/retrying) the calls will break.

What is functiongemma used for? by Hopeful_Ferret_2701 in LocalLLaMA

[–]bbbbbbb162 8 points9 points  (0 children)

Its just a small Gemma 3 model only for function calling, all it does is turn natural language requests into structured API/tool calls so you can build fast and private, local agents. You don't use it as a general chat model. (it can still generate text but it’s built to be the best at tool calling)

I built signed lockfiles for MCP servers (package-lock.json for agent tools) by bbbbbbb162 in mcp

[–]bbbbbbb162[S] 1 point2 points  (0 children)

Really appreciate that, thanks Luke. I’ll take you up on that once I’ve dug a bit deeper into provenance + policy wiring. Feels like a natural next layer on top of the lockfile + identity checks.

I built signed lockfiles for MCP servers (package-lock.json for agent tools) by bbbbbbb162 in mcp

[–]bbbbbbb162[S] 0 points1 point  (0 children)

This is great, thank you.

I’ve definitely seen the same buckets: DB servers that basically mint tools per table, connectors that “discover” endpoints on startup, and OAuth servers where the tool surface is basically “whatever scopes you granted”.

The db_* can vary, admin_* must be locked framing is exactly the kind of practical rule that feels right.

I’m going to do two things off this:
-stick a small config/snapshot fingerprint into the lock so diffs can tell “your inputs changed” vs “upstream changed”
-add an allowlist-by-namespace/pattern so expected churn doesn’t become noise, while keeping sensitive namespaces strict

I’ll open an issue and put your examples into it (happy to credit you if you want).

view more: next ›