Frank Sinatra was upset in Guys and Dolls because Marlon Brando, as Guy Masterson, was the one to sing “Luck, Be a Lady”.
Marlon was not a singer. He likely sang as badly as I, or worse. The claim was that his version of “Luck, Be a Lady” was made by cutting multiple takes together. Some cuts being only a word or less.
This was obviously frustrating to Frank, who is a great singer. Frank went on to make the song his own.
In 1969, Paint Your Wagon was released, starring Clint Eastwood and Lee Marvin. Both men sung their songs. They are not great singers. Nevertheless, the results were good.
I’m at the Fort this weekend (if you’re in the area, come on over and visit!), presenting life in the early spring in a cold environment. I’ll be staying all weekend, with no running water (it’s turned off until all danger of frost is gone) and little electricity (the gift shop has some). I decided that the food I was going to make should reflect the environment I’ll be in, and so these meals are ones that conceivably could have been served at the Fort in the spring of 1750.
Soup Meagre
I’ve adapted this from Hannah Glasse’s recipe of 1765. I find it amusing how closely it resembles the Green Soup that I made a couple of weekends ago for a Viking reenactment I did. There’s never much food in the spring, and what you can get your hands on has to “make do” until you can plant and harvest crops. It’s a tough time of year! This is a very plain soup, but with the seasonings, would probably have been quite the treat. Early greens in New England would include ramps, asparagus, watercress, fiddleheads, dandelion greens, and things we consider weeds like stinging nettle, onion grass, and dock.
Ingredients:
2 tbsp butter
1 onion, finely chopped
2 celery stalks, cut into 1- to 2-inch lengths (“half as long as your finger”)
6-8 oz mixed greens, (spinach, lettuce, arugula, etc), chopped if large
3 tbsp parsley, finely chopped
1 tbsp flour
2 to 4 cups broth
1/2 tsp salt, plus more to taste
1/2 tsp black pepper, plus more to taste
1/4 tsp ground mace and/or nutmeg
Melt the butter in a large kettle or Dutch oven over medium heat. When the bubbling has subsided, add the onions and cook for about five minutes, until transparent.
Add the celery, greens, and parsley, stir, and cook over medium heat for about 10 minutes. Sprinkle the flour over the greens and stir to blend. Add the broth, salt, pepper, and mace, and stir well. Simmer the soup over medium-low heat for about 30 minutes.
Taste and add more salt and pepper, if desired. Serve warm, with bread if you have it.
Notes from Mistress Allyson: If you want to add a bit of protein to this meal (something that would have been in high demand in the 1750s in spring), try some beans or a bit of salt pork. Beans get added right before simmering. Salt pork should go in with the butter at the beginning.
When working with git, there are several areas we might be discussing. The most important areas are “working directory”, “staging”, “local repository”, and “remote repository”.
A repository without a working directory is called a “bare repository”.
The working directory is a location where your files live, with a reference back to the repository. It is possible to extract the files without keeping a reference to the repository.
Most working directories, and what we will assume for our discussion, have the bare repository within the .git directory (folder).
A remote repository is normally a bare repository located somewhere apart from your local working directory. This could be a different directory on the local machine, or it could be located on a remote, network connected system.
Creating a Local Version of a Remote Repository
This is what the remote repository looks like. A pretty simple version.
We don’t copy it, we clone it. The implication is that what we have in the local version is the same as what is in the remote version.
git clone ssh:git@github.com/author/book.git
This creates a directory named “book”, it clones/copies the bare repository from GitHub and places it in “book/.git”. It creates a “remote” reference within “book/.git/refs/remotes” named “origin”. With “origin” it creates a copy of all the branches that are in the remote repository, in our example, just “master”
The clone command then checks out the working directory into “books”. This would be the files “chapOne.md”, “chapTwo.md”, and “chapThree.md”. It creates a file in “books/.git/refs/heads” named master with the commit hash (identifier) of “0ccd79797”.
These two look the same, but notice that the last two commits have different values/hashes. This is because they are different.
Since you are done with your edit, you attempt to send your changes back to the remote repository named “origin” via a push command. git push origin main This fails because there would be two versions of the repository if you did this, there can be only one.
To correct this, you first fetch an updated copy of repo.
We do another fetch, there is nothing to do as nothing else has been added. We then push our commits back to the remote repository. git push origin main
Because I’m not the program, there might be some small ordering issues in the final commit.
The point in all of this is that all of this magic happens behind the scenes. The program can do most merges with no assistance from you. In the rare cases where there is a merge conflict, it is relatively easy to manual merge the changes.
A merge conflict happens when two commits modify the same line of code. In your version, you had “Ciliorys hat” originally. You modified it to be “Billy-Bobs hat” Your editor had changed it to “Cilory’s hat”.
Now you have two edits to the same line. Git says, “You figure it out.” and shows you the two versions of the line, in context. You can pick one version or the other, or put in an entirely different version.
You choose the third option and put “Billy-Bob’s hat”. The world is good.
Conclusion
git is powerful. This discussion barely touches on the power of git.
There is an entire process of modifying code by “forking” a repository. When you are finished with your modifications, you can contribute them back to the original repository with a “Pull Request”.
Git has multiple methods of inserting code review and other tools into the process.
It is so powerful, It can be used to create a full wiki, on the fly. The raw files are served as wiki pages.
There is a method of doing a binary subdivision to find bugs that were introduced in the past. There is a method of tracking who introduced an errant line of code.
There are tools for pulling a commit out of the middle of a branch and applying it to a different branch, without taking the rest of the modifications.
In general, there only about a dozen commands that a user needs to know to work with git.
If you would like to work with git, there are communities ready to help you, there are multiple cloud providers that will allow you to host your repo on the web.
My introduction to source code control came at University. The name of the program was “update”. It took an “update deck” which described lines to remove, by line number, and lines of code to insert.
This format allowed us to inspect the code that was actually being changed, as well as the surrounding code. Every line of code I wrote for the Systems Group that was installed went through three levels of code review and QA testing before going live in the system.
Having those change decks helped in the review process. As a side note, the author’s initials were attached as a note to the right of every line of code we modified. Easy stuff.
After a change deck was accepted, it became part of the “installed version” of the software.
One of the powerful features of working with change decks is that two (or more) people could be working on the same piece of code and unless their changes overlapped, they could be applied independently.
RCS
When I left University, I started working with the BRL CAD project. This introduced me to the RCS system.
RCS was something like “update” but not quite. And you didn’t think in terms of “change decks”. That was handled behind the scenes.
You had a directory (folder) in which you had your code. You also had hidden files that stored the RCS history of the code.
By default, files were stored read-only. You could read them, you could compile from them, but you could not modify them.
To modify a file, you needed to first check out the file. When you checked out a file, it was “locked” to you and nobody else was allowed to modify the file.
You made the changes you wanted to the checked out files, then you tested. When you were happy that your code worked, you checked in the file you had checked out.
This is great when modifying a single file, but if you are modifying more than one file to accomplish your fix or enhancement, you have to check in each file in a separate operation.
There was no linkage between the files to indicate that all the changed files needed to be processed as a gestalt.
When you were ready to make a release, you had to do some magic to mark each file as being part of that particular tag. Then, at a later time, you could check out that entire tree and work on it as if it was the day of the release.
RCS did magic behind the scenes to figure out the “delta” between the checked out code and the original. This was equivalent to the “update deck” I was used to from University Days.
To work in a collaborative methodology, you would have a single “working directory” with everybody on the team having read/write privileges to the directory. If you were working across multiple machines, each machine had to use the same shared directory via a network file system. (NFS at the time)
At one point, I was working on BRL CAD on my home machine. I did not have enough space on the drive to copy the entire RCS tree to my local drive, so I was using NFS over a 28.8k dial-up modem.
Compile times ran about 3 days. And if anybody changed one of the “big” include files, I would have to start the build over again.
If you were working on a copy of the source code, you would extract a patch file from RCS to submit back to the master RCS directory.
It felt easy at the time, but it wasn’t as easy as it seamed. We just didn’t know what we didn’t know.
CVS
CVS was the first major paradigm change in source code control for us. The basic use was the same as with RCS, but they had changed the layout.
You now had an explicit directory, CVS, which contained the history files. When you checked out files, the lock was done in the CVS directory.
In addition, you could check out the files read-only (no lock) remotely from the CVS directories and then checkout with a lock, edit on the remote system, then check in your changes.
This was a game changer. We no longer required a network file systems.
Unfortunately, we had some of the same issues as we had with RCS. The main one being that only one person could check out/lock a file at a time. With team members working nearly 24 hours per day, it was a pain when the morning dude wasn’t available at 2237 to release a lock.
SVN
SVN solved most of the known problems with CVS. It had the concept of a remote repository, it allowed multiple people to work on the same file at the same time. It had better branch and tag capabilities.
All in all, it was a vast improvement.
The two primary weaknesses were no gestalt for files and very slow check out of branches and tags away from the main trunk.
I remember using SVN. I had to use it just a couple of weeks ago. I don’t think I ever fell in love with it. It was a step-wise improvement over CSV.
git
Git is my favorite source control system. I understand that there is another SCS, but I can recall its name at this point. I’ve not used it.
Git changed the paradigm we use for changing the repository. Whereas all the previously discussed SCS’s work on a file by file basis, git works on a “commit” basis.
Even if you are working in a collaborative environment, you work on your personal repository (repo). We will get to collaborative environments shortly.
In the simplest form, you create a “working directory” which you populate with your code. That could be a book, a program, an application, or a web page. It doesn’t matter. Git doesn’t care what the files contain, only that they be text files.
Git can work with binary files, but that is not our focus.
Once you have your initial contents, you create your repo with git init. With this magic command, git creates all the required files to track the history of your project.
Let’s say you are working on a book. You have placed each chapter of the book in a separate file. One of your characters is named Cillary Hlinton. Your editor tells you that the name is just too close to a real person, and he would rather not be sued. He asks you to change the character’s name.
Under update, RCS, CVS and SVN, you would check out individual files, change the name to “Billy Boy” and then check in your changes. When you have made all the changes, you are happy.
The issue is that there Chapter One is on revision 44, Chapter Two is on revision 37, and Chapter Three is on revision 48. How do you figure out the revision from just before you made the changes?
With git, you do not check out files and lock them. Instead, all files are ready for you to modify. You just edit the files and change the name.
Now you have chapters one, two, and three that have been modified. You group them into a single commit by adding them to the staging area. git add chap1.md chap2.md chap3.md
You can do this on one git add or multiples, in one session or multiple sessions. At some point you will be satisfied with your collection of changed files.
At that point, you commit the changes. You will be required to supply a message.
Each of the following circles represents a commit.
Before Name change
After the name change
If we want to see the version before the name change, we can check out commit 4. When we do, all the files are changed back to the version before adding your name changes.
This makes it easy to find one particular point where the state of the book is one way and in the next commit, all the changes have taken place across the entire book.
The other major improvement that git brought was fast branches.
Branches
Here we see two branches added to the repository. The first “HEAD” is a special branch. It represents the commit associated with the working directory. It is manipulated implicitly instead of explicitly.
“master” is the default branch until “rrracist” was applied, so some repos now use “main” instead of “master” branch.
This ability to create branches rapidly allows us to make and destroy branches at will.
We are going to create a new branch, “editor” for our editor to work on. Meanwhile, you are continuing work on chapter four.
Editor and Master branches
And here is where git shows another of its powers, the merge. With the ‘master’ branch checked out, we merge the editor branch, fixing all the little grammar and spelling errors. git checkout master; git merge master
After Merge
With this merge completed, the master branch contains all the work done in the editor branch, but the editor branch does not have any of the new work done on master. To synchronize the editor branch with the master branch we do git checkout editor; git merge master.
After merging master into editor branches
If there is no more editing to be done, it is acceptable to delete the editor branch. No code will be lost.
Because the ability to branch and merge is so quick and powerful, it is normal procedure to start a new branch for each issue being addressed in a project. When the issue is resolved, the new code is merged into master or discarded.
Remote Repositories
Is a tale for another time.
Conclusion
If you can use a source code control system to track your work and changes, do so. It makes life so much easier in the long term.
who has been convicted in any court of, a crime punishable by imprisonment for a term exceeding one year;
who is a fugitive from justice;
who is an unlawful user of or addicted to any controlled substance (as defined in section 102 of the Controlled Substances Act (21 U.S.C. §802));
who has been adjudicated as a mental defective or who has been committed to a mental institution;
who, being an alien-
is illegally or unlawfully in the United States; or
(except as provided in subsection (y)(2), has been admitted to the United States under a nonimmigrant visa (as that term is defined in section 101(a)(26) of the Immigration and Nationality Act (8 U.S.C. 1101(a)(26)));
who has been discharged from the Armed Forces under dishonorable conditions;
who, having been a citizen of the United States, has renounced his citizenship;
who is subject to a court order that-
was issued after a hearing of which such person received actual notice, and at which such person had an opportunity to participate;
restrains such person from harassing, stalking, or threatening an intimate partner of such person or child of such intimate partner or person, or engaging in other conduct that would place an intimate partner in reasonable fear of bodily injury to the partner or child; and
includes a finding that such person represents a credible threat to the physical safety of such intimate partner or child; or
by its terms explicitly prohibits the use, attempted use, or threatened use of physical force against such intimate partner or child that would reasonably be expected to cause bodily injury; or
who has been convicted in any court of a misdemeanor crime of domestic violence,
to ship or transport in interstate or foreign commerce, or possess in or affecting commerce, any firearm or ammunition; or to receive any firearm or ammunition which has been shipped or transported in interstate or foreign commerce.
— 18 U.S.C. §922(g) 2025-03-14
This is the current version of section §922(g). The word “felon” does not appear. All definitions are included within the list.
As you read on, notice that we have gone from actually crossing state lines to “affecting commerce”. This is a huge power grab by the federal government. The Constitution authorizes them to regulate interstate commerce.
The power grab is that they now claim the can regulate anything that might affect interstate commerce.
This is not how it started.
The term ‘indictment’ includes an indictment or an information in any court under which a crime punishable by imprisonment for a term exceeding one year may be prosecuted
— §921 in 1968
It shall be unlawful for any licensed importer, licensed manufacturer, or licensed dealer to sell or deliver—
any firearm to any individual who the licensee knows or has reasonable cause to believe is less than twenty-one years of age, if the firearm is other than a shotgun or rifle.
any firearm to any person in any State where the purchase or possession by such person of such firearm would be in violation of any State law or any published ordinance applicable at the place of sale, delivery or other disposition, or in the locality in which such person resides unless the licensee knows or has reasonable cause to believe that the purchase or possession would not be in violation of such State law or such ordinance.
any firearm to any person who the licensee knows or has reasonable cause to believe does not reside in (or if the person is a corporation or other business entity, does not maintain a place of business in) the State in which the licensee’s place of business is located; except that this paragraph shall not apply in the case of a shotgun or rifle.
to any person any destructive device, machine gun (as defined in section 5848 of the Internal Revenue Code of 1954), short-barreled shotgun, or short-barreled rifle, unless he has in his possession a sworn statement executed by the principal law enforcement officer of the locality wherein the purchaser or person to whom it is otherwise disposed of resides, attesting that there is no provision of law, regulation, or ordinance which would be violated by such person’s receipt or possession thereof, and that he is satisfied that it is intended by such person for lawful purposes; and such sworn statement shall be retained by the licensee as a part of the records required to be kept under the provisions of this chapter.
any firearm to any person unless the licensee notes in his records required to be kept pursuant to section 923 of this chapter, the name, age, and place of residence of such person if the person is an individual, or the identity and principal and local places of business of such person if the person is a corporation or other business entity.
— §922 as of 1968
This does not seem to include as much as the current law does.
In October 1968, the law changed
The term ‘crime punishable by imprisonment for a term exceeding one year’ shall not include (A) any Federal or State offenses pertaining to antitrust violations, unfair trade practices, restraints of trade, or other similar offenses relating to the regulation of business practices as the Secretary may by regulation designate, or (B) any State offense (other than one involving a firearm or explosive) classified by the laws of the State as a misdemeanor and punishable by a term of imprisonment of two years or less.
— §921 — October 1968
Here we see that they have explicitly excluded misdemeanors with possible imprisonment of less than two years. The old version was greater than one year.
It shall be unlawful for any person—
who is under indictment for, or who has been convicted in any court of, a crime punishable by imprisonment for a term exceeding one year;
who is a fugitive from justice;
who is an unlawful user of or addicted to marihuana or any depressant or stimulant drug (as defined in section 201 (v) of the Federal Food, Drug, and Cosmetic Act) or narcotic drug (as defined in section 4731(a) of the Internal Revenue Code of 1954); or
who has been adjudicated as a mental defective or who has been committed to a mental institution;
to ship or transport any firearm or ammunition in interstate or foreign commerce.
It shall be unlawful for any person—
who is under indictment for, or who has been convicted in any court of, a crime punishable by imprisonment for a term exceeding one year;
who is a fugitive from justice
who is an unlawful user of or addicted to marihuana or any depressant or stimulant drug (as defined in section 201 (v) of the Federal Food, Drug, and Cosmetic Act) or narcotic drug (as defined in section 4731 (a) of the Internal Revenue Code of 1954); or
who has been adjudicated as a mental defective or who has been committed to any mental institution;
to receive any firearm or ammunition which has been shipped or transported in interstate or foreign commerce.
— §922 — October 1968
Read that last line carefully. In November 1968, a person who was a “prohibited person” could no receive any firearm or ammunition which had been shipped in interstate or foreign commerce. They could still keep and bear arms. They could not buy or be given guns that crossed state lines.
This means that it was perfectly legal for a prohibited person to keep all the firearms they owned before becoming prohibited and they could manufacture firearms for their use. All legal.
It also meant, that if they were to buy direct from a manufacturer, that would be legal. For example, if they lived in New Hampshire, they could go to the Sig Store and purchase a gun manufactured by Sig in NH.
It shall be unlawful for any person—
who has been convicted in any court of, a crime punishable by imprisonment for a term exceeding one year;
who is a fugitive from justice;
who is an unlawful user of or addicted to any controlled substance (as defined in §102 of the Controlled Substances Act (21 U.S.C. §802)
who has been adjudicated as a mental defective or who has been committed to a mental institution;
who, being an alien, is illegally or unlawfully in the United States;
who has been discharged from the Armed Forces under dishonorable conditions; or
who, having been a citizen of the United States, has renounced his citizenship
to ship or transport in interstate or foreign commerce, or possess in or affecting commerce, any firearm or ammunition; or to receive any firearm or ammunition which has been shipped or transported in interstate or foreign commerce
— §922 — May 1986
Section (h) was rewritten to reference section (g) for who was prohibited. We also see that it is no longer receiving a firearm that is a crime, it is in possessing.
We still see that the limitation is on firearms that cross state lines. We see this in many federal laws. They will reference something crossing state lines being regulated. This is because that is all the Constitution authorizes the federal government to regulate.
These changes were part of “Firearms Owners’ Protection Act”. I just love it when something that is about protecting my rights adds more limits on rights. Yeah, I know, bad people.
In 1996, §§ 921-922 were amended to add definitions and text to prohibit who has been convicted in any court of a misdemeanor crime of domestic violence..
In 1998, in an “Omnibus Consolidated Appropriations” bill, they changed the definition of an illegal alien.
Conclusion
1) reading lawsuits is easy compared to reading “Public Laws”. They write bills like patch files. Instead of showing us the new version with strike through and underline to show removed and new text, they say things like (I) by inserting “transfer of a firearm to or” before “receipt”; and (II) by striking “(g) or (n)” and inserting “(d), (g), or (n) (as applicable)”.
I read that stuff all the time, but I have tools that make it easy to see the changes.
2) The law expands little by little, infringing more and more. What starts with something that feels reasonable ends with something that is totally unconstitutional.
I’m watching the snow melt outside. It’s SLOWER than watching paint dry. Ah well. It’ll be gone soon, and then I can get to work on outdoor stuff. For now, it’s time to plan the outdoor garden space, and decide which things are getting direct sowed. In other words, which things go right into the ground (or raised bed/outdoor container/plant tower/etc) versus those that get started indoors because they’re too delicate for the cooler weather?
The first seeds that I’ll be direct sowing will be radishes, beets, carrots, peas, and spinach. These are all hardy crops, and they like the cold and damp that come along with early spring and late fall. They’re also staples around here. Well, not the beets so much. I like them, but most of the rest of the family doesn’t. That’s fine; more for me.
You’ll note that the beets and carrots and radishes are all what we call “root crops.” This means the edible part is under the ground. Generally speaking, for early spring crops you want to look for ones that say, “Plant seed outdoors as soon as the soil can be worked.” This means that a late frost in the spring won’t destroy your plants, and that’s a very good thing when you live in the northern part of America, or any part of Canada. Most root crops can be planted early, but always check the seed packets (or online if you don’t have the packets).
Before you can sow seeds directly into the soil outdoors (regardless of whether it’s in the ground, in a raised bed, or in a container of some kind), you have to prepare the garden bed. This takes several stages, and is best started as soon as you can get into your garden area. I can’t yet, because we still have snow deep enough to cause issues and I’m not shoveling out the garden. You can speed this up by covering your garden beds with black plastic each fall right before the snow flies. This keeps down on weeds, and also allows the beds to warm up earlier. Once your beds are defrosted and workable, you can begin planting. This is one of the main joys of any kind of raised bed.
git is a source code control system. It is the most powerful or one of the most powerful SCS’s I’ve used.
Like all powerful things, you can break it in hundreds of different ways.
One of its most powerful features is the concept of a remote repository. While other SCS were able to have remote repositories, git takes it a step further. A remote repository is just the bare part of a normal git repository.
This meant that if you had access to a remote server, you could have a remote repository on that server. The issue came when you wanted to restrict what a user could do on that remote server.
The answer came in the form of small applications that allowed you to configure remote access via a git repo. That access, in turn, allowed users to access other repos. By combining SSH keys with this simple software package, you could have multiple users accessing the remote repositories through a single “user” on the remote server.
This simple tool grew into a monstrosity called gitlab. If you purchase a GitLab seat, you get all the tools and do not have to worry about the resources used. Unfortunately, this can be expensive if you have more than a few members of on your team.
There was an option to self-host, but the self-hosted version was missing some very useful features as compared to the paid version. And the thing is a resource hog.
GitHub went a slightly different route. It offers almost all the features of GitLab, maybe more. It has a free tier. But if you want private repos, again, you have to pay per seat.
Enter gitea, as they say, “Git, with a cup of tea.” This thing is fast enough in a low resource environment. It has the remote repos. It allows forking and pull requests.
It has organizations and teams, allow easy control of collaborations. It has everything we need for remote git repos.
And then the extras. First, it has a good issue tracking system. It is not jira but it is good enough. It has projects with Kanban capabilities. It has a wiki.
And it looks like all the “extras” are handled as repos. I’m very impressed.
I feel like we won this round.
Nerd Babble, the bad
Computer motherboards are supposed to be standardized. Yes, some manufacturers make custom boards for their custom cases, but in general, standard is better.
Over the last couple of years, I’ve discovered a small form factor motherboard that is small enough and light enough to attach to the back of a monitor. We have three of these at the house. Thank you to my son for discovering these.
When looking for NAS enclosures, I discovered 4 bay NAS enclosures that were designed to hold a Mini-ITX motherboard.
A Mini-ITX motherboard is 170×170 mm.
This size allows for exactly one expansion slot to the right of the back i/o ports.
Unfortunately, there is another motherboard that isn’t a Mini-ITX which gets sold as a Mini-ITX. It is 170x190mm. This gives enough space for 2 expansion slots.
The NAS enclosures only accept the 170×170 motherboards.
I now have a 170×190 MB that I will have to home.
Snope and Ocean State Tactile
My frustration with the Snope case knows no bounds. This case is old.
It started as a challenge to Kolbe. Kolbe was a challenge to Maryland’s assault weapon ban. It went before the Fourth Circuit court where they assumed that assault weapons were arms under the Second Amendment, and then proceeded to say that they were not protected arms because of “interest balancing”.
This was appealed and cert was denied.
A few years later, Bianchi v. Frosh was started. This was a challenge to Kolbe. The district court followed the Fourth Circuit’s opinion in Kolbe and found for the state. The case was appealed. The three judge merits panel found for the state because they could not override an enbanc panel. A motion was made to have the case heard enbanc.
Regardless, the Fourth found for the state and Bianchi filed a petition for writ of certiorari with the Supreme Court.
Somewhere around that time, Frosh was replaced with Brown. Thus, the case became known as Bianchi v. Brown.
The Supreme Court sat on the case until after Bruen.
After Bruen the Supreme Court granted certiorari, vacated the Fourth Circuit’s finding, and remanded the case back down for a do-over. This is a GVR.
The Fourth Circuit then had the case briefed in light of Bruen and then heard oral arguments before a three judge merits panel. They were the first circuit to hear a Second Amendment case after Bruen.
The merits panel split 2-1 in favor of Bianchi. The sore loser refused to write and submit his dissent on the case. This kept the case in limbo for almost a year. At the end of the year, it looked like the merits panel was going to publish their pro-Second Amendment opinion without the dissent.
At which point the Fourth Circuit decided to take the case enbanc. They required the parties to submit another set of briefs. They then held oral arguments again.
Around this time, Mr. Bianchi left the state of Maryland. This would have mooted the case, but David Snope was also a plaintiff and thus the case was renamed Snope v. Brown. The Fourth circuit then found for the state, again.
This case is now before the Supreme Court seeking certiorari, again.
The court has discussed this case in conference six times. It was distributed for conference seven times, with the first conference being rescheduled.
Which takes us to Ocean State Tactical. This is a magazine ban out of Rhode Island. It is in the same posture as Snope
And now we have Antonyuk v. James. This is a sensitive places case. This case has been to the Supreme Court multiple times. Has been GVRed once. It was denied certiorari once, but with a statement by Thomas telling the inferior courts to do it right.
With all three of these cases before the Supreme Court, seeking certiorari, we might get a trifecta. Here’s hoping.
The Continuing Lawfare against Trump
It is difficult to express just how fast these cases are moving. It is my opinion that the people engaging in lawfare had an expectation of stopping this administration dead in its tracks.
Even when the administration appears to have lost, they are winning. The only case that I’ve noticed that is moving at “regular” speeds is the DoJ v. State of New York. Note, that is not the actual case name.
We’ve had cases move from district court through the circuit courts to the Supreme Court and back down in a weeks time.
In the case of Mahmoud, the administration moved so fast that the lawyers filed in the wrong court. Now they are arguing that it was the right court because at that instant of time, M.K. was in a particular location. This does not seem to be the case.
The left is claiming that Trump is being forced to pay $2 billion dollars. He’s not. The new order says that they have to pay what is actually owed. Not “all billed”. This is another win. That judge was slapped down hard.
Question of the Week
Which of the lawfare cases is most concerning to you?
This is an interesting and challenging case, for me.
This is a Constitutional challenge to Mahmoud being detained and then deported. His claim is that this is a violation of his First and Fifth Amendment protected rights. Because it is a violation of his rights, the court should grant him relief.
Mahmoud is an Arab that claims to be a Palestinian. He entered the United States in December 2022 on a student visa to study for a Master’s degree at Columbia University in New York. He completed that degree in December 2024 and is going to graduate in May 2025. He married in November 2024 and got a green card.
He was granted a green card because he was married to a US citizen. He is still an alien, just not illegal. He has not overstayed his visa, nor is he required to leave when his visa expires.
His lawyer describes his actions in this way:
As a Palestinian, M.K. has felt compelled to be an outspoken advocate for Palestinian human rights and more recently, to speak out against Israel’s genocide in Gaza and the role of Columbia University in financing and in other ways facilitating the genocide. M.K. is committed to being a voice for his People, and calling on the rest of the world to stop providing weapons and support to enable the genocide in contravention with international law.
This describes his actions as speech. Regardless of how reprehensible that speech might be, it is still protected. The First Amendment protects reprehensible speech, not just the words we want to hear. It is easy to believe in “free speech” if the only allowed speech is that which we agree with.
This case is seeking the following relief:
Assume jurisdiction over this matter
Declare that the state violated Mahmoud’s First amendment and Fifth Amendment protected rights
To keep Mahmoud in New York
Release Mahmoud
Pay Mahmoud’s legal fees
Item 3 is mooted because Mahmoud was out of New York before the case was filed. In a later filing they requested that he be returned to New York.
So we look at the Constitutional challenge. One of the things to note is that not all the Constitution applies to everyone. Some apply to Citizens and some apply to “the people”. The rights limited to citizens are called out by the term “citizen”. The rest of the time the founders use the terms “the people”, “person”, and “the accused.”
The Supreme Court has issued many opinions that restrict “The People” to those with a strong connection to the community politic.
With these in mind, it seems clear that Mahmoud is a member of the people. His rights are protected by most of the Constitution.
Is he challenging a federal law prohibiting the free exercise of or abridgment of his speech? Not directly.
Instead, he challenges the law as applied to him, His claim is that he can’t speak while detained and that the threat of detention has a chilling effect on his ability to speak freely.
The state has not justified his detention in court documents — yet. Instead, they are fighting the most relevant parts first. Bluntly, I don’t care if this asshole is deported or rotting in a jail cell. He’s not out there intimidating the people of the United States.
What the state did was they revoked his visa and his green card.
When can a green card be revoked?
5. Security-Related Reasons
Green card holders who engage in activities deemed threatening to U.S. national security can lose their status. This includes involvement in terrorism, espionage, or other activities that undermine the safety of the United States.
Examples of Security Violations
Membership in Terrorist Organizations: Being part of or assisting a terrorist group can lead to immediate revocation and deportation.
Espionage or Treason: Activities related to spying, intelligence gathering for foreign governments, or attempts to overthrow the government are considered severe violations.
Consequences: In addition to deportation, individuals accused of such activities may face criminal prosecution and significant legal penalties.
What this means is that the state need only prove that Mahmoud was part of or assisting a terrorist group. Hamas is a designated terrorist group.
Conclusion
The left loves to talk about hate speech. They love it because it allows them to justify their violence. Hate speech is always in the eye of the offended.
“Violent” speech is violence, according to the left.
Violence can be countered with violence.
Therefore, you saying something that they disagree with is hate speech, which in turn is violence, which means they can punch you.
In the other direction, any real, physical violence they engage in is “just protests” and is “speech” protected by the Constitution.
They are going to lose this one. I’ve seen to many good filings from this administration to believe they aren’t going to win. Maybe not at the district level with all the rogue inferior judges, but they will win higher up.
This case is distributed for Conference on 3/28/2025. This adds an interesting twist on our Second Amendment cases before the Supreme Court.
Could this be combined with the Snope (assault weapon bans) and Ocean State Tactical (magazine bans)?
This case is where New York State’s Bruen tantrum replaced “proper cause” with “good moral character” and then proceeded to make almost all of New York State a sensitive place.
I’m going through some personal stuff right now, and it’s been rough. Some of the responses I’ve gotten to my last few posts have left me feeling raw and frustrated, and unsure of what to do and say going forward. After some long talks with Chris and others, I’m writing this to try and get some general thoughts out that I hope will help you guys and me.
First and foremost, if something is labeled “From Behind Enemy Lines,” then I am doing just that – talking about the Left, FROM the Left. That is what I’ve been asked to do, when I’m posting under that banner. I’ve been asked to give a Left perspective, or at least a “more Left” perspective, so that you guys can learn and to be sure that Vine isn’t an “echo chamber.” I am going to be more obvious in it, adding FBEL at the top of posts that are “representative Left” or “explaining Left” so that they stand out.
So my last post was about the memes I’d seen floating around, and in particular, about the Trump 2028 one. From where I’m standing, there are three groups of people. First, we have the far Left. They’re going to do what they’re going to do, and nothing you or I say is going to change it. I ignore them. Second is the group of “normal Left” or what I tend to call “thinking Left.” These are people who have chosen willfully to be Left of center, but are self-consistent, thinking, and reasoning. I might not LIKE their reasoning, and I may think it’s false in the grand scheme of things or missing important points, but they’ve shown me that they give actual thought and consideration to their position. I have many friends in this group.
The third group consists of people like me. We were a little Left of Center, if you asked us. People on the Right just lumped us in with “The Left,” and the Left considered us oddities and “too far Right for comfort” but generally tolerated us. We are no longer “a little Left of Center.” We are deep state Right, at this point, because the Left has shifted so far Left that we’re not even close anymore. Some, like myself, have chosen to take the couple of steps Right to join the rest of you under the Conservative tent, albeit in our own little corner while we acclimate. Others are dithering out there on the sandbar, wondering where the hell the tide went and why it’s so fucking cold these days.
