How many people interacted @1password.bsky.social when they did their taxes this year? How did it go? Want the good and the bad.

1Password developer/SDK docs now have first class LLM support! developer.1password.com/docs/buildin...

I was inspired by @s.ly 's recent piece on Latent Space Engineering. I wanted to see if his observations also applied to the security domain. What started as small experiment turned into a full blown agentic AI benchmark that I'm releasing as OSS at 1Password. 1password.github.io/SCAM/

Getting phished is both scary & humiliating and with AI its happening more often. As we've said, the long-term answer is passkeys, but not everyone uses them. Today, 1Password is shipping a deceptively simple change that massively improves the situation for passwords. 1password.com/blog/as-ai-s...

Great news for all who depend on a Ruby ecosystem that's healthy and secure.

Good news for the Ruby ecosystem. RubyGems now has the same governance as Ruby itself. Matz and Ruby Core as stewards. If Ruby Core has authority over where gems (by default) install from, this alignment makes sense. Viva la Ruby! www.ruby-lang.org/en/news/2025...

Arko in this post says he’s in control of a second 1Password account. One thing he should do is check if he’s the only owner. If he is, no one can evict him and regain the account. IMO he should have disclosed this access to them in his original email, esp if it’s how he got AWS root access.

I am so excited by this feature. developer.1password.com/docs/environ...

How can you tell if non-tech leadership understood your tech idea? Their first questions are about patent status.

3 things I found are always true when making SaaS. 1. To know what you need to build, you must first build it. 2. A fast and cost-effective way to find and fix bad bugs is to ship them to production. 3. If you're nervous about deploying to production, the solution is to deploy more frequently.

Here it is! The toothpaste that most accurately simulates brushing your teeth with dirty swimming pool water!

How I used ChatGPT today. This saved me at least 20 minutes because I always (ALWAYS) mess up stuff when it comes to time.

We’ve got more “small teams” than ever before. They’re all mostly B2B SaaS. I think B2C is the big upset. How do we explain to people that they should “shop local” when it comes to software. And pay for it!

Happy Fourth of July! …or as it is better known in the UK, “Urgent Support Ticket Submission Day”

Awww yeah. https://www.kolide.com/docs/getting-started/connect-kolide-to-okta/overview#step-5-set-up-factor-sequencing-optional

What do you do on a day like today? You write docs.

I love our channel on the #macadmins Slack and I love the passionate people who build things with our API. Thanks Thomas. ❤️ https://www.macadmins.org/slack

It’s happening!

...And 4 emails and docusign later, it's already 6:00am. Gotta get these three noobs up for the day!

Third task for the day. Lot's of stuff shipped over the weekend. What I like to do is let individual customers to know via our shared Slack channels when something they cared about ships. This is one of those things that won't scale for long, but we do it anyway because it's the right thing to do.

Btw, we can see when this commit is deployed by going to https://www.kolide.com/version which simply shows the SHA1 hash of the git commit deployed. This was an idea I stole from a GitHub talk in the early 2010s. I think from Kyle Neath?

Second Problem. Customer bug report. Kolide offers Slack based support (which btw is the best decision we've ever made) & while normally it's quiet, we have a customer who is hitting a problem with mobile registration. This is bad because I _just_ changed this code last night. What did I break?

First problem. The kolide.com/blog uses the srcset so that a lower resolution image is loaded on mobile. Sadly on Safari, the first cover image does not show up.

It’s 4:25am, it’s Monday. Let’s get into it.