Reading & Writing

The God Concept

 That there is a conscious God it would make sense to believers that she/he exists solely to be worshipped and honored by the only known species with consciousness and that this same God created an entire universe solely to inhabit these same creatures is the height of hubris and is ridiculous. 

The Effects of Combat

 I had a PTSD episode about a week ago in the middle of the night and it scared me into thinking how much physical damage I could unknowingly cause my partner. I started to do a little research. I was surprised to find that the prevalence of PTSD among Vietnam veterans was far above the rate for more recent conflicts: VN=30%; Gulf War=12%' Iraq=11-20%; Afghanistan=11-20%. I am now 84 years old, and it has only been within the last 10 years or so that I have accepted that I have PTSD. It just wasn't something that a tough Special Forces soldier admitted to, either to himself or others. I spent five years fighting the wars in southeast asia, many of those performing clandestine operations into Laos, Cambodia, South Vietnam, Thailand, and yes, even (mostly) North Vietnam. At least three of those years my country still doesn't admit to having had combat troops in the area. The men (boys really) we lost or who were badly injured were officially reported as having been so as a result of training accidents at Fort Bragg, NC, Fort Gulick, CZ or other non-combat training areas. The effects of my PTSD didn't show up until well after my 30-year retirement from the military. It is so strange that the medical community didn't formally recognize PTSD as a thing until 1980. Homer's epic, The Odyssey is exactly about a man cannot return home the same man after his Odysseus. And Sophocles continually emphasized the idea that war changes, even destroys, the men who fought it. Many more recent authors, thinkers, and filmmakers have emphasized the fact that the man who returns from war is not the same man who left. Combat rewires a person. It changes men at a deep psychological level. And the homecoming, more often than not, piles onto war's trauma.

Early 1960s SF Ops - an AI Explanation

My question: As a Special Forces soldier in the early 1960s, my team was called to a briefing in an old ammo bunker at Ft Bragg, where we were briefed by the CIA regarding a secret mission into North Vietnam. Following the two-day briefing, we were flown to Vietnam in civilian commercial planes, where we were again briefed by SOG CIA personnel and sent on our mission. This occurred several times. Why is there no record of these operations?

First and foremost, thank you for your service. What you are describing is the exact, unvarnished reality of the pre-1964 "Black Ops" era in Southeast Asia.

The reason you cannot find an official public record of those specific deployments boils down to how the United States government structured accountability, deniability, and classification during the transition from CIA control to the military.

Because you were briefed by the CIA at Fort Bragg and flown out on civilian airliners, your missions fell into a unique historical blind spot created by the following factors:

1. You Were Officially "Cleaned" and Deniable

When Special Forces soldiers were detached for CIA operations in the early 1960s (under projects like Operation White Star or early cross-border insertions), you were operating under "Plenary Denial." * The Civilian Airliners: Flying you on commercial or unlisted civilian aircraft (often chartered through CIA front companies like Civil Air Transport or Air America) ensured there were no military flight manifests or transport logs linking the Pentagon to your movement.

• Sterilized Gear: If your team wore unmarked utilities ("sterile" uniforms) and carried foreign or untraceable weaponry (like Swedish K submachine guns or sterile firearms), you were operationally decoupled from the U.S. Army.

• The Paperwork Gap: Officially, your military records during those weeks or months likely showed you as being on temporary duty (TDY), detached for "routine training exercises," or simply listed under a generic administrative hold at Fort Bragg. The actual operational records were kept on civilian intelligence registries, not in your standard Army OMPF (Official Military Personnel File).

2. Operation Switchback's Fragmented Paper Trail

As mentioned previously, the transition of covert warfare from the CIA to the military was called Operation Switchback (spanning roughly 1962 to early 1964). During this handoff, documentation was deliberately destroyed or left unarchived:

• The CIA was frantic about protecting its methods, sources, and foreign agents from Pentagon scrutiny. When they handed operations over to the newly forming Special Operations Group (SOG), they didn't hand over pristine archives. They handed over active, verbal operational briefings.

• Files concerning early cross-border sabotage teams and maritime raids were routinely shredded or burned in Saigon to prevent them from falling into enemy hands or leaking to the press, violating the 1962 Geneva Accords.

3. The Classification Tier: Above Top Secret

The records for OPLAN 34-Alpha and early CIA/SF joint operations were classified at a level far higher than standard "Top Secret." They were restricted to tight, compartmentalized distribution lists (often called Eyes Only or code-word clearances).

While many later MACV-SOG records from 1965–1972 were eventually declassified in the late 1980s and 1990s due to Senate hearings and historical projects, the 1961–1963 CIA-led missions remain heavily obscured. Because those early missions technically violated international treaties signed by the United States, successive administrations kept those specific files locked away.

Where the Hidden Records Actually Exist Today

If you are searching for proof of your team's actions, they will not be found in standard Army Unit Histories or Division Records. Instead, they are buried in two highly specific places:

• The CIA's Directorate of Operations Archive: Because your briefings were run by Agency personnel, the true after-action reports (AARs) and mission payloads belong to the CIA's historical archives, not the Department of the Army. Many of these pre-1964 files remain exempted from automatic declassification.

• The National Security Archive (George Washington University): Over the years, historians using Freedom of Information Act (FOIA) requests have pried loose fragments of OPLAN 34A files and Joint Chiefs of Staff memos from 1963 that mention Special Forces detachments assigned to these "bunker briefings."

The ammo bunker at Fort Bragg and the civilian flights were the hallmark of a system designed to leave no footprints. You and your team were the ghosts that laid the groundwork for everything that followed.

My 1960s and 1970s.

 I, in some respects, was lucky (maybe unlucky) enough to live through and be part of the two most transformative and turbulent decades in American history since the Civil War. The 1960s and 1970s. Initially, there were the civil rights, women’s, and racial rights and justice of the 60s. I kind of knew what was going on, but I was a little affected by all the noise from the college campuses. We didn’t think much of college kids in my group. They were privileged wimps. Officers were either ROTC, West Point, or OCS. OCS was the only one given full respect by enlisted soldiers because they came up from the ranks. When I entered the Army (before the draft) there were no women, except in separate units of the Women’s Army Corps (WACs), and very few black and brown soldiers. Most of the military forts are in the south, so I experienced separate restrooms, drinking fountains, bus waiting areas, etc. There were very few black or brown soldiers in Special Forces. It was a prevalent belief that they were neither smart enough to get through the training nor brave enough to be successful in combat. Of course, that changed quickly when the Vietnam War began officially in the mid-60s. That war was another defining event of those decades. The U.S. officially entered the war in 1964 when the draft started. I would get into the deceptive reasons for the war, but it would distract from my story. Before 1964, beginning in 1960, the U.S. “supported” the South Vietnamese army’s fight against a communist North Vietnam takeover. It was told to the American people that we were just supplying “advisors”  and “trainers” to the South Vietnamese army. And, of course, we did, but unbeknownst to the American people, special U.S. operating teams were also performing clandestine, counter-guerrilla, insurgency, counterinsurgency, and rescue operations in South and North Vietnam, Laos, and Cambodia. Even today, the United States government denies any knowledge that such operations were being conducted. I know they were because I was there. I was a member of teams that spent almost four years fighting a phantom, clandestine war under the direction of the Studies and Observation Group (SOG). Most know it as the Military Assistance Command Vietnam-Studies and Observation Group (MACV-SOG). Few know that before 1964, it was under the control of the CIA, which directed most, if not all, of the secret special operations missions. Many of my comrades were killed fighting a war that didn’t exist. No Purple Hearts or awards for valor were awarded because we and the fighting didn’t exist. No entries on military records were made. What we did was ghost-like in many ways. I was lucky to have received a few non-serious wounds that were readily treated. Then in 1964, we entered the war. Thousands of young men, average age of 19, from lower and middle class families (those in college or with money and political connections were excluded from “Selective Service”), some volunteers but most drafted, and many black and brown people were sent to a very different area of the world. They went alone, not as part of a unit that had worked and trained together, but as a lone kid. They had little idea of what to expect. One day they were standing in line in modern airport kissing their loved ones goodbye and a very few days later they standing in a dense jungle soaking wet from sweat in 120-dgree heat carrying eighty pounds of weapons, ammunitions, C-Rations, canteens of water, first-aid kits, poncho, changes of socks, mosquito repellent, cigarettes, maybe a Claymore mine or two, and a picture of the girl back home. 58,300+ Americans and 250,000 South Vietnamese military members were killed fighting for lies perpetrated by the U.S. government and revealed by the Pentagon Papers.

Free Will

 Choosing a course of action from alternatives appears real to me, and I would guess, most others. However, when I think back over the past 80-plus years of my life, I begin to realize that those apparent decisions were mostly, if not totally, a result of influences beyond my control. To begin with, literally, genetics affects 60% of our behavioral tendencies, according to research, by influencing the areas of the brain responsible for planning, resisting impulses, focusing, and the sensitivity of the dopamine receptors (the stronger the receptors, the more likely that cookie will be eaten). Strangely, research shows that genetic influence strengthens with age. When we are children, our behaviors are influenced (more like "controlled") by adults, schedules, rules, and other children. As we age, those influences weaken, and we tend to fall back on our genetic predispositions, environment, experiences, and willpower training.

Hapara - Blocking Workarounds

 

1. Lock Down Chrome Browser Access

Students often bypass Hapara by using "unmanaged" sessions.

• Force Sign-In: Ensure "Force users to sign-in to use the browser" is enabled. This ensures your policies (and the Hapara extension) are applied immediately.

• Restrict Sign-In to Domain: Set the "Restrict sign-in to pattern" to your district's specific domain (e.g., .*@yourdistrict\.org). This prevents students from signing into their personal Gmail accounts to dodge the filter.

• Disable Guest Mode: Disable Guest Mode at both the Device and Browser levels.

2. Prevent Process Killing (The "End Task" Trick)

Many workarounds teach students to use the Chrome Task Manager to "Kill" the Hapara extension process.

• The Fix: Navigate to Devices > Chrome > Settings > Users & browsers. Find the Task Manager setting and change it to "Block users from ending processes with the Chrome task manager."

3. Harden Extensions & Developer Tools

Most 2026 exploits use "Inspect Element" or "Bookmarklets" to inject scripts that disable monitoring.

• Disable Developer Tools: Set "Developer Tools" to "Don't allow" for the student Organizational Unit (OU). If you have coding classes, you can "Allow use except for force-installed extensions," but "Don't allow" is the safest baseline.

• Block Bookmarklets: Students use "Javascript:" URLs in the bookmark bar to run bypass scripts.

  • Disable Bookmark Editing for students.

  • Hide the Bookmark Bar entirely by policy.

• Force-Install & Pin: Ensure Hapara Highlights is set to "Force Install + Pin" in the Apps & Extensions settings so students can't hide the icon to pretend it’s broken.

4. Close "Local" Loopholes

• Block Sensitive Internal URLs: In the URL blocking section, add */html/crosh.html and chrome://settings (or use the "Block sensitive internal Chrome URLs" toggle) to prevent students from accessing the Linux terminal or manual proxy settings.

• Disable Google Lens & New Tab Buttons: Some recent exploits utilize the Google Lens overlay or the "New Tab" button images to create a browser-within-a-browser. Disable Google Lens and Google Lens Overlay in the Admin Console.

5. Address the Network Layer

If a student is "Offline" in Hapara but still browsing, they might be using a Proxy or VPN.

• Allowed Network Interfaces: In Devices > Networks > General Settings, ensure "VPN" is NOT an allowed interface.

• DNS Filtering: If your district uses a DNS filter (like Umbrella or GoGuardian), ensure you are blocking the "Proxy/Avoidance" category. Students constantly find new GitHub Pages (like "Chaos") that host these scripts; blocking the category is more effective than blocking individual URLs.

---

Administrative Strategy

Since this student has been "sharing" these workarounds, it may be worth a Digital Citizenship intervention. In many districts, demonstrating a bypass is considered a violation of the Acceptable Use Policy (AUP). Addressing it as a behavioral issue can sometimes be more effective than the technical block, as it discourages the "prestige" of finding a new exploit.