Second Amendment Cases Seeking Cert
Yes, there are cases seeking cert.
No, there has been no real movement.
Yes, they are still there.
What does it mean? I don’t know. Mark Smith suggests that Snope being conferenced 16 times is a good thing. Certain controversial cases have been conferenced this many times, or more.
If they grant cert, oral arguments will not be heard until October. We would expect to see an opinion issue 3 months later. If cert is granted, the court must publish their opinion by the end of June 2026.
Why is there now movement on 2A cases?
Bluntly, everything is in a holding pattern. It doesn’t matter what happens in the different circuit courts, the rogue inferior courts have made their play. Bruen stopped the two-step shuffle and replaced it with a new two-step shuffle.
The old two-step was to first assume without granting that the plain text of the Second Amendment was implicated. Then deciding on what level of scrutiny was required. In rogue courts, the balance was always in favor of gun control. The Ninth Circuit is over 120 opinions in favor of gun control and zero in favor of The People.
Snope is the best vehicle forward we have. The Supreme Court can address the issue of what is an arm, slap down the gun bans and magazine bans, all at once. This leaves the sensitive places issue still to be heard.
Long Days
Wrapping my head around different concepts is not difficult. My problem comes in seeing how complex issues are tied together. Sometimes it is documented, sometimes it isn’t.
There are three templating languages that I know and use. Twig, Jinja2, and Django Templating Language. They all have similar syntax, and they all have the same basic concepts.
The gist is that you have a template which has “tags” and “variables”. When you insert a tag, it can render something, it can modify variables, or it can add programming structure. Variables just render the content of the variables as a string.
When we address forms, Django has a sophisticated system. You define a form by asking for a form to be built from a model (a record in a database) or by hand. Each field is identified. Each field is assigned a rendering widget.
In the simplest form, you can render a complete form with: <form method="POST" action="">{{ form }}<button type="submit">Submit</button></form> Which is wonderfully powerful.
The issue comes when you need something extra special. In my case, I needed to set a CSS class on a subwidget. I could not make it work. I read the code, I knew what it was doing, but I just could not access the context I required.
The issue? When a field from a form is rendered, a new context is created which is passed to the widget templates. My templates came before the field was rendered, making it impossible to access context which had not yet been created.
The Fort at No 4
I’m heading up to the Fort at No 4 today. We’ll be there most of the day, interacting with school kids there as classes. This will be my first time doing this. I have no idea how well I will do, or what I will be doing. I might just sit and comb wool.
Rogue Judges
We have now reached the point where administrative judges are issuing injunctions against the Trump administration.
We have a district court in Maryland issuing a standing order that any Habeus filing involving a criminal alien will automaticity find against the state.
Rogue inferior judges now believe that they have the power to supervise the Article II executive branch in all things.
Just tired of this…
More and more people are grumbling about being tired of this shit. People are no longer allowing themselves to be pushed around.
In my opinion, this is because they believe that the state will have their back. It is no longer Daniel Parry doing the right thing and then being forced to go through lawfare. There is a growing feeling that if you stand up for what is right, things will go OK for you.
Question of the Week
There were disturbing noises out back last night. When I went out to investigate, I took the R95 in .357 Magnum. This is more than enough for the small game I normally deal with back there.
As I followed the sounds, it sounded like small game. Then I heard what, I thought, was a wild pig. And I remembered that there had been bear sightings around here.
My question, if you were to see a boar or bear over the sights of a lever action .357 magnum, coming towards you. Do you fire? Do you try to retreat? Do you head back to get something bigger? Is 30-30 big enough? Or would you move up to 45-70?
Comments
One response to “Friday Feedback”
The best caliber for a large animal, bear/boar/moose/etc… is the one you have in your hands right then. You fire. Multiple times. Better to put two, three… five smaller holes into it, than insist that one large hole is the only solution. That is why I changed my hiking rig from a .454 Casull to a 10mm. Better to have 16 chances to hit than six.
As to caliber…
.357 is a punishing round out of a 4″ barrel, but out of a rifle it is even more punishing. Will it kill a bear in one shot? No, not unless you are very lucky. Will a single shot make a curious bear decide this area is painful and maybe they should go somewhere else? Good chance of that.
If you have time to run back inside and get a different caliber firearm, just stay inside. Unless you are protecting livestock, or you know the animal is a danger, odds are, it is just curious and will move on. Waste of ammo, and it is just clearing up space for another animal to take over the territory.
Now, if you want a single shot kill of a bear or other large animal, we are talking a larger caliber, higher power rifle. No, handguns are not going to cut it. Rifle. 30-06/30-30, many 6mms… Obviously 45-70 will do the job. (It will do the job for pretty much everything actually…) If it starts with a “.2” or a “5.XXmm” it is underpowered, and not going to help out much. (Exceptions apply)
The real question is what do you really want to do? Kill the animal? Scare it away? For kill, go with as large as you have. For scare, pretty much anything will work.