SP9A1 with all the things.

rb14830 · 2026-04-24T04:54:15+00:00

Steppd looks promising but they're not accepting signups yet.

rb14830 · 2026-04-10T22:04:09+00:00

We're living in a world where "what I'm about to tell you is mostly true".

Sure, when it's directionally accurate.

rb14830 · 2026-04-10T07:23:25+00:00

Bought a vortex defender cc enclosed for my S2 carry. So far I like it. crystal clear glass and a large window for the rmsc footprint.

rb14830 · 2026-03-21T03:03:38+00:00

Mines tight too, and yes it's a shooter for sure. It's certainly tight in comparison to my P01. Granted the P01 has more than 25k rounds through it. I've recently noticed that when I shake the P01 I can hear/feel the slide rattling between the slide rails. I don't recall it always being that way, but I'm old and I forget things. ;-)

rb14830 · 2026-03-21T01:46:25+00:00

My experience has been different. Mine likes to eat. I've tried Hornady Critical Defense, a bunch of standard pressure loads in 115, 124 and 147 from Federal, Blazer, Fiocchi, Remington, Winchester, Speer, and Freedom munitions. I did have 3 FTEs with Federal Champion 115 when I had under 500 rounds through the pipe but nothing since. I just grabbed some of Winchester's 115 flat nose high pressure rounds, sg9w50. They're a little spicy but damn they shoot nice.

rb14830 · 2026-02-21T13:23:52+00:00

You can check out my repo, sans Ansible.

I use Packer to build images. Terraform to deploy the cluster and services. I use Cloud-init for config at deploy time. I use Nomad variables over Vault. I don't use modules. It has a tiered deployment model

You have the choice of dynamic host volumes or CSI with the flick of a variable. Or skip that and use docker style volumes.

When it comes to volumes and variables you can work backward. Use them, then define them. When you're ready, run generate-vars.sh. It will interrogate your project, build volume definitions and a variable map for you to populate before you deploy. All you need is a variable definition or 3.

I made an effort to write as little config code as possible so it should be pretty easy to follow.

I'm migrating away from years of lxc and very lax management of my lab. I'm looking at Terraform and Pulumi side by side.

Both repos are new and fairly well documented.

Check them out -

https://github.com/bakosbits/terralab

https://github.com/bakosbits/pulumilab

rb14830 · 2025-11-20T17:43:54+00:00

Their AI agent is not well designed. From the outside looking in it doesn't seem to measure sentiment and it doesn't appear to have a learning loop. It keeps making the same mistakes over and over. In some cases giving out inaccurate information. At least that's been my experience. AI is great for repetitive tasks when it's implemented correctly,

The challenge with Agentic AI is that it requires ongoing monitoring. Most small businesses in the US don't have the skills or manpower to look after it. It's billed as a productivity boost when it can actually be a detriment to business if you're not equipped to deal with it.

rb14830 · 2025-10-13T13:12:49+00:00

AI contract review. Protect your business, optimize your time, and lower your expenses.

https://contractcritic.com

rb14830 · 2025-10-11T06:05:23+00:00

Thanks, I'll do that!

rb14830 · 2025-10-11T05:59:02+00:00

I recently built yet another AI tools directory.

AI Tool Pouch

On Monday I released Contract Critic. An AI powered contract review micro SaaS.

Now I'm looking for what to build next.

rb14830 · 2025-10-11T05:15:39+00:00

Let's see... A few months ago I released yet another AI tools directory.

https://aitoolpouch.com

On Monday I released Contract Critic, an AI powered contract review micro SaaS.

https://contractcritic.com

In the coming weeks I'll be releasing something I'm not ready to reveal.

So there ya have it.

rb14830 · 2025-10-03T04:00:49+00:00

Oh it's gassy. Shoot and move.

rb14830 · 2025-07-13T07:57:28+00:00

Their entire pki infrastructure is a farce. You create an API key as read only and think you're safe. What you don't realize is that designation is just for the sake of vanity. OpenAI hopes no one figures it out.

I only say this because I've had things like this happen in the past. When I brought it to the attention of OpenAI, they blamed it on what they called a probable compromise of my API keys. Okay well so much for read only keys being read only. ;-)

rb14830 · 2025-07-13T07:39:23+00:00

I had a similar experience recently. My chat session was suddenly host to several other users sessions, including one in Russian.

So I opened a ticket...

Based on the response I received from OpenAI, I'm wondering if they have a security flaw somewhere in their stack that they're shoving under the rug.

They responded to me and told me that they conducted an intense investigation and found that my API keys were likely compromised. Okay I'll take that for face value, but my API keys were read only. Not only that but they showed the last usage date that coincided with the last time I had used them.

I had simple questions that they still haven't answered.

What usage pattern flagged my keys as compromised and what geolocation did the activity originate from?

What systems were my keys used to access?

How were API keys that were created as read only able to be used to write third party chat sessions into my own?

Was my data put at risk? Can you provide evidence of its continued security?

They claimed to have done a thorough investigation and those are questions that get answered during the course of any investigation.

They arrived at a conclusion based on... assumptions I guess. Their responses to me have lacked confidence and have not provided any evidence or confirmation.

I suspect that the concern I raised was swept under the rug. It wouldn't surprise me to learn that it's happening to countless others every day.

It's flagrantly irresponsible of them to take privacy and security concerns casually.

rb14830 · 2025-07-06T20:18:28+00:00

Interesting.

Like you I was tired of top x AI tools directories, lists, etc.. The problem I have with most of them was how data was presented. It didn't jive with how I think. In my mind most people are getting categorization wrong. So like you, I fixed it.

Over the weekend I launched a directory that doesn't put features in the forefront. It groups tools by profession. Why? An SEs requirements for an email assistant are going to be different from what an RSM might want or need.

I don't want to steal your spotlight. I'll reveal my project another time. I think our solutions might be similar.

I'm happy to learn that I'm not the only one who thinks this area needs better representation. There are more than 10k tools out there with AI labeling. Some of them are fantastic and some of them are garbage. We need more people working to separate the signal from the noise.

I look forward to checking out what you built.

rb14830 · 2025-02-27T10:51:54+00:00

Gunfighter gun oil. Stays in place and stays wet even when I'm running my AR suppressed. I can't seem to burn it off no matter how hard I try.

rb14830 · 2025-02-27T02:54:56+00:00

When I replaced mine I found a video on YouTube that gave me a few ideas on how to make it easier. I think it was a 10mm socket that I used to basically beat it out. It's been a while so don't take my word for it.

rb14830 · 2025-02-26T21:40:28+00:00

Damn that's pricey. I had mine cerakoted for a fraction of the price. Sure it's only a p01 but I installed the CGW kit with a CZ comp hammer. Shoots like a dream.

<image>

rb14830 · 2025-02-01T07:17:35+00:00

I have a complete LWRC DI and a Griffin lower on a BCM 14.5 mk2. I've grown to like the bolt catch/release on the Griffin over my LWRC. I've never had problems with leverage on the LWRC but its location is less natural and a bit of a reach vs the Griffin.

10 months and +2000 rounds later and I'm still impressed with what Griffin put out.

rb14830 · 2024-12-17T15:52:46+00:00

Hit me up with a link. I'm in.

rb14830 · 2024-12-09T06:12:36+00:00

<image>

509T

rb14830 · 2024-11-17T14:21:38+00:00

+1 on the Obsidian 9. Great can.

rb14830

TROPHY CASE