u/rbprepin

Congress zeroed out the $200 NFA tax on suppressors and SBRs this year, but left the registration and approval system in place.

Yesterday a federal judge ruled that created a constitutional problem.

The interesting part is that this wasn't a Second Amendment decision. The NFA was originally built under Congress's taxing power. The judge's reasoning is basically: if the tax is now $0, the government can't keep using its taxing authority to justify the registration system that existed to administer that tax.

If this survives appeal, I think the implications for preparedness are bigger than saving $200.

Suppressors are genuinely useful equipment on a rural property. They don't make a firearm silent, but reducing muzzle blast matters if you're dealing with a predator or other emergency and don't have hearing protection on.

SBRs have an obvious compactness advantage around vehicles and buildings.

But the part I find most interesting is the registry.

There are now more than 6.5 million suppressors in the federal NFA registry and about 1.2 million SBRs. Until now, owning either meant accepting federal registration as part of the deal. If this ruling ultimately applies broadly, that connection could disappear.

Important caveat: nothing changes today. The judge stayed his ruling for seven days to give the government time to appeal, and the injunction isn't a blanket nationwide exemption. State laws wouldn't disappear either.

So don't read the headlines and start ignoring NFA requirements.

But if the ruling survives, would removing federal registration change your willingness to own a suppressor or SBR?

For me, the registry has always been a bigger issue than the $200.

I wrote a longer breakdown here if anyone wants the sources and legal details: https://getready.team/news/policy/2026/08/06/congress-killed-the-200-suppressor-tax

Most of us think about wildfire risk by looking around our own property.

Clear the brush. Cut the grass. Move the woodpile. Keep vegetation away from the house.

All good advice. But the Spokane fire this weekend made me think we're often looking at too small an area.

Indian Trail and Five Mile Prairie are residential neighborhoods inside Spokane city limits. Mowed lawns, streets, cul-de-sacs. Yet hundreds of structures burned in the Old Trails fire.

The interesting part is where the fire came from.

It started several miles west of the neighborhoods in open grass and shrub country. Strong southwest winds pushed it northeast, across the Spokane River and up the terrain toward the neighborhoods above.

So if I were evaluating my own property for wildfire exposure, I'd want to know four things:

1. What's upwind of me?

The amount of hazardous vegetation nearby matters, but its direction matters too.

I'd pay particular attention to large areas of grass, brush or forest that line up with the winds I typically get during hot, dry weather.

2. What's below me?

This is one I hadn't thought enough about.

If your house is on a ridge, bluff or elevated lot, look at what's growing below you. Fire generally moves faster uphill, so a wooded or brush-covered slope below the house can matter a lot more than the relatively clear ground you see immediately around you.

A high lot can look pretty safe while having a significant fuel source just out of sight.

3. What do I assume will stop a fire?

A river looks like a firebreak on a map. So does a highway, greenbelt or cleared area.

But wind-driven fires throw embers ahead of themselves. The Spokane fire crossed the river.

I'd be very hesitant to assume any single feature between me and a large fuel source means the problem stops there.

4. Is there a continuous path to me?

This might be the biggest thing I'd look for.

Imagine drawing a line from the nearest large area of grass, brush or forest toward your house.

What's along that line?

Two miles of continuous dry grass and brush is very different from two miles broken up by irrigated fields, parking lots, subdivisions and large cleared areas.

Distance by itself doesn't tell you much without knowing what's between you and the fuel.

And this changes how I think about defensible space too.

You probably can't do anything about the forest, grassland or state park two miles away.

What you can control is what happens when embers arrive.

That's where the boring stuff suddenly matters a lot:

• Keep the first 5 feet around the house as noncombustible as practical.
• Don't stack firewood, fuel or other combustible material against the structure.
• Keep gutters and roof valleys clean.
• Screen vulnerable vents with appropriate metal mesh.
• Maintain defensible space farther out where possible.
• When replacing roofs, siding, decks or fencing, consider ignition resistance instead of just appearance and price.

I used to think about wildfire exposure mostly as a radius around a property.

Now I think the better questions are:

Where is the nearest large continuous fuel source?

Is it in the direction fire weather usually comes from?

Am I above it?

And what, if anything, actually interrupts the path between it and me?

I'm curious how many people here have actually looked at their property this way. I hadn't.

Disclosure: I run getready.team. This isn't a promo post, just the numbers, but wanted to say that up front.

All of this rides on DeFlock's mapping work. I pulled every surveillance:type=ALPR node from OSM (118,475 worldwide, 109,518 in the US) and did two things with it: matched cameras to real city boundaries (Census place polygons, not a radius guess), and clustered cameras by proximity to estimate distinct store locations for the two biggest retail operators.

**Lowe's:** 1,432 documented cameras nationwide, clustering into 661 distinct locations. That's roughly 1 in 3 of Lowe's ~1,760 US stores. Usually two cameras per lot, one per entrance lane.

**Home Depot:** 883 cameras, 395 locations, about 1 in 5 stores.

Combined, that's more documented cameras than the NYPD, Chicago PD, San Francisco PD, and San Diego PD have between them (1,346).

The obvious caveat: only about 20% of cameras in the dataset carry an operator tag at all, and retail brands are way easier for a mapper to identify than an unmarked pole outside a precinct. the government is almost certainly undercounted compared than retail. Point isn't "retail beats police." Point is that two hardware chains built networks the size of a major city PD.

Why it matters beyond the count: these are Flock cameras, same network as the municipal ones. EFF's public records request out of Johnson County, TX showed one sheriff's office running a single query across 83,345 cameras / 6,809 separate networks (404 Media covered the retail-access angle: https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/). Doesn't matter who owns the pole. It's one searchable system.

As the pressure campaign increases against local government, officials may say, "Ok, we won't install any more Flock cameras", but that doesn't mean the surveillance stops, they're just using retail giants as a backdoor.

Also in the data: 33 HOA-run networks (Holmby Hills, St Francis Wood, Woodbridge, among others), tagged the same way.

Full write-up, city-level breakdown, and an address lookup: https://getready.team/news/safety/2026/07/21/one-in-three-lowes-license-plate-camera

Raw data if you want to check my clustering: https://getready.team/data/alpr-city-counts.csv

Exact extraction query: https://getready.team/data/alpr-query.txt

Happy to answer questions on methodology, or pull a specific city's numbers if anyone asks.

I’ve been looking at a piece of land approximately 90 miles from Charlotte. It’s far enough from the city where I think it could be a great bug out location, but not too far that I can’t make the trip. But I started to model out what a mass evacuation would look like and now I have some doubts.

Charlotte's population is about 793,000. In some scenarios, like an Economic Collapse, most would probably stay put, but a dirty bomb or a grid-down cyber attack could empty it fast, either because the place is contaminated or because the water stops and people leave before it does. If a meaningful number of those people left, they wouldn’t just scatter in random directions, they would funnel along major roads.  My modeling puts the displacement band somewhere between 40 and 120 miles depending on what you assume, and 90 sits right in the middle. I really don’t want half of Charlotte running out of gas in front of my house.

Keep in mind that band is my own estimate of how far people get before fuel and traffic stop them, not something the model calculates. So take it with a grain of salt.

Looking at these maps, maybe distance doesn’t matter all that much and terrain is the key consideration. Maybe being 45 miles away from the city in a maze of backroads is safer than being 130 miles away just off an interstate. Or maybe people just stay put regardless and I'm overthinking it.

If you’ve already bought land, how important was distance away from a major city? Was it a top 5 factor, or something you're not really worried about?