Bill Binney & Katherine Horton - Directed Energy Weapons, 4117

Bill Binney and his wife, Dr. Katherine Horton were very insistent to come on for another interview on the topic of the use of directed energy weapons against disobedient civilians.

I was hesitant about this interview because I feared it would discredit their work on NSA illegal surveillance. However, if you stick with this interview, you will gradually discover that once again, these two brave Americans are standing up for truth and are way, way ahead of anyone else.

Towards the end, I was floored when Katherine showed that the amount of current R&D money being spent on these weapons systems is now in the tens of billions of dollars.

Full video here: rumble.com/v2std78-bill-binney-and-katherine-horton-directed-energy-weapons-4117.html

#2023 #TheStillReport #4117 #BillStill #Interview #BillBinney #KatherineHorton #News #World #US #America #Europe #Asia #Classified #Patented #Technology #Business #Industry #Pulse #Projectiles #DirectedEnergy #Weapons #Assault #Conspiracy #Domestic #Global #Espionage #Intelligence #Gangstalking #CultureWar #SpiritualWarfare #PsychologicalWarfare #UnrestrictedWarfare #Demoralization #IdeologicalSubversion #BiologicalWarfare #DemocraphicDisplacement #Replacement #Ideology #Paganism #Freemasonry #Satanism #MentalIllness #MoralIllness #Over #1hour

OMG I might be in heaven. This appears to be exactly what I need. I don't want to play with boring Arduino shit and signal wire madness, and hellish programming-language-of-choice binding situation. The difficulty to payoff is so fucking high. I don't want to be married to python forever.

I also don't want to be beholden to a distant foreign corporation who will allow me to connect to something that is just a few tens of meters away from me. I can easily do in purely scriptable IO dance.

It's actually really hard to find a relay that is designed for a very high skill level of software and Linux, but doesn't assume that you want to get all Wozniak about wiring it out. Capitalism - when it's not completely gay - is just great because I can pay these guys some tens of dollars of profit to put it all into a clean package with nice features.

I just want to automatically pump shitty duck water from a cool on-site website that I've made up. I just don't want to fuck with signal wires. I just, I just can't even.

WiFi ESP32 Module with 8 Relays & 8 Inputs

I'm going to try a build-less front end. So I'll use htmx, hyperscript, alpinejs, and lit-html.

The idea is to get back to a much simpler webdev experience. The server will be loading all HTML directly, but with caveats. htmX allows me to start everything with a simple model where the server old-school loads HTML via a route. So that is like the web of 1995. From there htmX (The loud X is emphasis added by me) allows me to make very simple swaps and actions. The interesting part is that the server will be sending HTML instead of JSON. That is very simple, even if oddly disconcerting to the modern web developer.

From there I have a few options for making a page more dynamic. In no particular order, I can use a a vue-like syntax using alpinejs to dynamically iterate on lists and json data. Within the alpine template I can place htmX directives on it for quick and easy form updates.

Perhaps even more useful (if not oddly so) is Hyperscript. It's a strange dialect that allows complex interactions to be written on the element in an English-like syntax. It's very powerful, in particular becomes it smooths out synchronous and asynchronous actions so that you don't have to think about them. This appears to be a real winner for me around simple interactions that jquery is great for, but I'm not so sure about these large multi-line Hyperscript directives.

The great part about these techs is that they're very small, and they don't require a bundling step, or a package installing step. I will be manually downloading these dist files and placing them into the public web directory - old school. They don't really need to be updated. Alternatively, you could still use NPM to fetch them, and then with a most minimal build step which simply bundles them together. Of course you can also directly link to the CDN.

Finally there is Lit-HTML. This is a successor to the Google Polymer project that was able to dramatically slim up the library due to much of that research making it into the formal HTML and Javascript specifications. Basically it allows you to define custom HTML elements. So the idea here is that you could hide a JSON API call, or complex JS interaction behind a custom element, that you can then place on the page with HTMX or Alpine. These are just custom html element with a thin helper wrapper, and so that isn't going anywhere for a decade or so. Any future changes will be very easy to upgrade to.

The interesting thing about all of these techs is just how completely tiny that the runtime is, and how they automatically convert any HTML that is written to the body. So it's like that HTML is actually live.

About HTML custom elements, think about your default HTML video player if you were to simply place a <video> tag onto the page. This is basically just a custom element with a shadow DOM (for encapsulation). In fact, this default implementation on browsers is likely simply a build-in custom element that is using the same exact mechanisms that are available to us.

So all of this said, I still think that for a complete SPA (Single Page Application) with all of the bells and whistles that Svelte is by far the best. I've written advanced Vite build steps, integration with Go, and Vite manifest parser that sets up multi-staged loading with prefetch and preload, etc. The problem is that this is just a really damn heavy place to start for your average fuck-around site, or for personal use.

The actual motivation though is that is makes it difficult to develop on a Raspberry Pi if a complication step is needed for every little thing. I would like to build my Golang binary with all of the bindings that I require, and then to be able to hack on the code such that every little change doesn't trigger a slow multi-second long rebuild step. That rebuild step can be as long as 10-15 seconds. I basically want to have the old-school PHP experience, but in a modern way.

I'm going to be able to experiment with all of these different libraries interacting together in order to find the exact correct combination of them in various circumstances. For example, for admin forms, HTMX seems like the clear winner. There is very little reason that a server needs to return JSON that then needs to be converted into HTML. Instead the server can just control all of this. Forms are boring, and far too much time is spent massaging the data into a nice API, and then turning that nice API into a form UI update.

Professionally I'll likely be continuing to use Svelte for the magic part of an app, and then I'll use HTMX with support for admin forms. For passion projects I'll likely be making much more clunky apps that are dead simple using all four of these techs in conjunction. They all play well together, except in situations where dynamic page reloads are necessary and one is wanting to maintain complex alpinejs state. In such a situation I think that the best thing to do is to just make a full page refresh instead of spending 10x of the time to smooth out something that is really not a big deal.