HN user

russell_h

1,715 karma

Head of Engineering at C1: https://c1.ai

Formerly:

  - CTO of EdgeBit: https://edgebit.io
  - Co-Founder of ScaleFT (acquired by Okta).
Email: russell.haering@c1.ai
Posts12
Comments411
View on HN
Making 4 hours ago

Whoa, I had no idea Beej is teaching at OSU!

Back when I was an OSU student I taught myself a lot about practical systems programming, and I was consulting Beej's Guide to Network Programming daily. I kept lamenting to myself that I wished the expensive university was proving as useful as this guy's free website.

Awesome that it has come full circle, great hire by someone.

MCP auth has been a huge pain point for us at C1 - both for our own internal MCP use and in our in-product MCP Gateway - so very glad to see this landing.

We launched support today for C1 to act as an EMA identity provider (we mint the short-lived scoped tokens), so I'm excited to hook this up for Linear and some of the other MCPs we use, and get out of the business of constant OAuth flows. Claude has been doing this magically for some of their built-in connectors (at least Slack I think) and the experience is pretty great.

Disclosure: VPE at C1. We wrote up how we’re approaching it here if anyone’s in the weeds on this: https://www.c1.ai/docs/product/admin/enterprise-managed-auth...

ConductorOne | ONSITE (SF / PDX) | Full-Time

ConductorOne is building the platform for identity security and least privilege automation — helping companies secure access to everything, without slowing people down. Our engineering culture emphasizes small, high-ownership teams that deliver measurable impact and move quickly.

We’re hiring across many areas:

  - Software Engineers – We’re growing our product development teams in SF and Portland.

  - Site Reliability Engineering – We’re looking for SREs and a hands-on SRE manager (SF or Portland) to own reliability, performance, and infrastructure as we scale.

  - Forward Deployed Engineering (FDE) – We’re building a brand-new customer-facing engineering org: we're looking for engineers who want to work closely with customers to modernize and automate identity operations, and a Manager, FDE to lead the team.

  - Governance, Risk & Compliance (GRC) – We’re building a new GRC function and hiring our first Compliance Engineer to help scale our security and audit programs.
We work primarily in Go and TypeScript, on AWS + Kubernetes.

Apply here: https://www.conductorone.com/careers

I don't quite understand the goal of this project.

It says they're preventing 15,000 tons of emissions, but there are all kinds of ways to prevent or offset greenhouse gas emissions for under $10/ton. So at a glance this project appears to be allowing almost 2 million tons in preventible emissions in order to... pay people to bike around and collect food scraps?

This looks great!

At risk of harping on a tired topic, have you thought about embedding an AI query generator? For ad-hoc queries like I mostly use DuckDB for I’ve found it’s almost always fastest for me to paste the schema to ChatGPT, tell it what I’ll looking for, then paste the response back into the DuckD CLI, but the whole process isn’t very ergonomic.

I think I’m sort of after duckbook.ai, but with access to a local duckdb.

ConductorOne | Software Engineer | Hybrid (Portland, San Francisco), Remote(US) | Full Time

ConductorOne (https://conductorone.com) is a modern identity governance platform built to secure and simplify access management for today’s fast-changing, cloud-based environments. We unify access and permissions data from across all your cloud, infrastructure, and on-prem tools, giving real-time visibility and control, and help our customers reduce identity risks, automate access reviews, and streamline access requests, with powerful automation and user-friendly experiences. Trusted by teams at DigitalOcean, Instacart, Ramp, and more.

We use lots of Go, React, Temporal, gRPC, DynamoDB, Postgres and AWS. We’re looking for product-minded engineers, who love taking ownership of the product and shipping every day.

Frontend Engineer (SF preferred): https://jobs.ashbyhq.com/conductorone/01862e6d-0d75-43da-8fc...

Go Engineer (Portland, SF, Remote (US)): https://jobs.ashbyhq.com/conductorone/7a164d64-6427-4fba-b71...

Apply directly via the links above and mention this post, or reach out via the email in my profile.

In security contexts the term “enumeration” is understood to mean “brute force”. You can Google “enumeration attack” to see a bunch of examples where this is explicitly defined.

They’re only partially correct no matter what. The timestamp in a ULID has only has millisecond resolution, so two IDs generated in the same millisecond, even within the same process, will be randomly ordered.

In practice though there are a lot of advantages to having approximately-time-ordered IDs, and I’ve found the pitfalls easy enough to avoid.

In this context WASM is more like a slower container than an application runtime. The potential advantages being:

  * Far better isolation than a normal Linux container
  * If WASM takes off, maybe architecture-independent artifact distribution
  * If WASM takes off, maybe improved ability to call from one language into another
As a Kubernetes container runtime WASM today is probably most comparable to gVisor, with the somewhat huge caveat that it prevents you from just running normal Linux software.

They're looking at browser traffic. I assume people don't do a lot of web browsing with Steam Decks (maybe I'm wrong, never used one), so they're probably not being counted.

Some data I found on the internet suggests Apple ships about 6 million Macs per quarter, and they're at around 15% market share in the stats linked here. Other data I found on the internet leads me to guess Valve has sold around 3 million Steam Decks in the 2 years since they launched.

So my guess is that if you factored Steam Decks into this they'd account for about another 1% - very roughly.

Is there really much room for improvement on efficiency without moving to very different form-factors?

I would have figured that rolling resistance and air resistance account for the huge majority of the energy usage without much room for improvement over eg a Model 3, unless you make it look like an F1 car or give it solid tires or something.