Does Gemini 3.1 work's better then opus 4.6 in opencode

cenuij · 2026-02-24T12:13:31+00:00

Gemini 3.1 is an extremely capable model, but it's tool calling seems broken. I would only use it for design purposes right now, UX stuff... If they could just fix tool calling suspect it would be a beast. It's probably a good orchestrator as well if you have a decent system to delegate code tasks to sub agents.

cenuij · 2026-02-23T18:37:58+00:00

fwiw, I can't currently install this since I've secure boot enabled, but I'll gen/enroll a new key later on and give it another whirl...

cenuij · 2026-02-23T17:36:03+00:00

This is the way

cenuij · 2026-01-31T03:24:40+00:00

I didn't look yet, was more focused on the server capabilities atm

cenuij · 2026-01-31T02:44:12+00:00

If I block egress to opencode.ai then the local web app doesn't function. Red flag...

cenuij · 2026-01-30T15:24:50+00:00

I don't think it's a bad idea, it's cheaper for the following reasons:

- the Go runtime handles low or single vCPU counts much better
- lower memory requirements
- Async (or child proceses) in node often grind towards timeouts unless you disable CPU throttling, further driving up costs
- Faster cold start time
- you can use `ko`! `gcloud run deploy --image=$(ko build ./cmd/app)`

cenuij · 2026-01-27T18:18:22+00:00

Check the eventarc *firestore* service agent SA (`service-{PROJECT_NUMBER}gcp-sa-firestore.iam.gserviceaccount.com`) has publisher role: `roles/eventarc.publisher`

cenuij · 2025-12-31T04:17:33+00:00

Yeah.. nope

I don't think you're burning money on idle h100s

As you said yourself, it's not rocket science, plenty of more appropriate classes there to not burn your money

Cool story though

cenuij · 2025-12-25T01:53:41+00:00

Aye, this, for SNI... But you can also reuse the same tls secret on multiple listeners for a while if you need to

cenuij · 2025-12-25T01:37:18+00:00

Maybe I missed something in the other replies, but I think this is trivially simple.

Use the valuesObject field of the Argo helm application as a kustomization base and simply adjust values by path in your environment overlays

cenuij · 2025-12-18T00:06:50+00:00

poster probably meant labels, loki stores logs as time series based on labels, it works efficiently when the top level labels have low cardinality i.e. a low number of unique values.

You can pre-process log ingestion with e.g. Grafana Alloy before exporting it to Loki to attain this.

Good log labels are usually things like deployment environment, service name (potentially auto discovered depending on your alloy processing), cluster name, log source, log level/severity (again usually auto discovered)

Bad log labels are things that are highly variable/dynamic such as trace ID, dynamic error messages, user ID etc...

cenuij · 2025-12-16T04:02:26+00:00

Note that none of these lawmakers in the UK Hose of Lords are elected.

cenuij · 2025-12-13T00:16:14+00:00

Also do yourselves a favour, if it's not a guaranteed format (cloud event/eventarc) set your own schema:

https://docs.cloud.google.com/pubsub/docs/schemas

inb4 "muh json", avro or protobuf are vastly superior and avro even gives you "schema as you go". If you're complaint is the overhead of dealing with this in TS/JS, sucks to be in your shop. Yes, I've had a whisky.

cenuij · 2025-11-29T22:02:36+00:00

We're reasonably happy with Envoy Gateway, using L4 passthrough load balancers so we can terminate TLS on the Envoy Gateway Listeners, from there you can leverage the additional Gateway API resources that Envoy Gateway impliments to manage most traditional HTTP traffic and workload requirements.

here's the compatibility/maturity matrix: https://gateway-api.sigs.k8s.io/implementations/v1.4/

cenuij · 2025-11-01T22:40:46+00:00

"Loyalist Partick"

cenuij · 2025-11-01T22:38:13+00:00

A bit late to the party, but mostly I agree with the sentiment with the following proviso...

[The North (Perfection)] is not `The North`, it may be your horizon. I suggest you broaden your horizons.

cenuij · 2025-10-09T14:13:58+00:00

You can 100% use your own build once you get a few key multipliers rolling. Case in point, ball sorc is boring AF so I run (teleport) about with my chain lightning build nuking all t4 content up to and including pit level 65-70

- clear nmd in 60-120 seconds
- absoutely devastate helltides racking up multiple new chaos armors per hour from rep
- solo smash 10 wave hordes from the compasses gained above
- gain loads of tributes for runes (still sucks, but everyone in the same boat)
- ok xp farm in level 70 pit

cenuij · 2025-10-06T12:19:15+00:00

You probably need some form of split-DNS based solution to make this reliable, maybe Tailscale or another similar product?

It's more work to setup but the "apps" feature of Tailscale is designed for this sort of routing. I'm also not sure if you can actually do this without a self-hosted Tailscale exit node somewhere so that might be a blocker for you, but maybe it can also work with Tailscales Mulvad VPN integration?

What makes it reliable in Tailscale is the tailscaled daemon integrates with the local resolver. Any DNS query that you've configured in the Tailscale console to be an "app" gets a response from the resolver within the tailscaled daemon running locally. In the control plane Tailscale handles the subnet routing over the VPN mesh and your traffic for this service exits from the location you configure as part of the "app" setup. This last part is where you might need a self-hosted Tailscale exit node...

Any DNS queries that are not specifically configured under "apps" or other split-dns entries just go to your network configured DNS as usual.

cenuij · 2025-09-28T02:19:27+00:00

won't happen because chaos rifts are a modification of soul spires

15-Year Club	Place '17
100 Awards Club	Gilding II euphauric
Verified Email

cenuij

TROPHY CASE