). Hence I will be traveling on the 16th and 23rd of December, but will attempt to attend remotely on both occasions.
...A WORD TO THE WYZE...
I was recently handed a Wyze Outdoor Camera by a friend who wanted to
get the silly thing working. She had switched platforms, she went
from Android to Apple, and lost use of the camera. What a pain in the ass,
as this security camera does not support RTSP without re-flashing the
camera bios with an unsupported product.
The alternative to reflashing is to build a "Wyze to RTSP" translator in
an LXContainer... Thus the immutable investigation continues...
My foray into Red Hat Bluefin, under the guidance of DTG continues.
Dave and I are more or less in sync in the quest for good Red Hat Bluefin.
As I stated last week, I am sticking with a Gnome GUI Desktop, and am very
happy that my Zope 2 based web efforts at least continue to seem stable and redundant.
My frustration with both Bluefin and Aeon are that both Aeon and Red Hat Bluefin almost need "Ports and Protocols" Documents. The issue here is what can you write to? What directories (and particularly ports)... What you can read and under what conditions would also be useful... This is this evening's frustration...
The latest in the LinuX Containers (LXC) is that I seem to be having some issue in migrating containers from SUSE Aeon to the new Hat Bluefin,
DTG found a work around that I am desperately trying to understand and document.
Maybe this is the interim ultimate way to go involving this IBM/Red Hat
power combination. I long to have my new 32GB of DDR4 making me a
master of multimedia... Other needs involve for instance, the ability
to load programs from Integrated Development Environments or even whole
Operating Systems to and from either Pi's or Arduinos. I would like to
call this relationship between devices and systems "Breathing". By this
I mean that I could "exhale" code to the device from my workstation, but
also "inhale" code from the device to my workstation, a much rarer
functionality.
So, this has given birth to Yet Another Bash Project (YABP :^).
The working title of this is "podmania.sh"... Once you have the
shell script name, the rest is easy... The idea here is to
add both functionality and another less labyrinth overlay to the
"Chomskyic" ("Chomskyish"? ;^) podman suite of scripts...
I am repeating this because I feel it is an important aspect of
computing in general. You may well ask, what is Chomskyic?
Noam Chomsky, early in his distinguished career asserted the
following according to the Google AI:
NOUN AND VERB PHRASES - PHRASE STRUCTURE RULES
Noun And Verb Phrase rules break down sentences into their constituent parts,
such as noun phrases (NPs) and verb phrases (VPs). For example, the first rule
states that a sentence (S) is made up of an NP followed by a VP...
Welcome to transformational grammar and command line programming sez I.
...As usual, apply this to computers (ADP) and you have to reverse the paradigm...
In ADP the verb phrase (VP) is typically first, followed by a predicate
noun phrase (NP). Basically the verb phrase (VP) is recognized in
the system's path... To repeat, there are many basic examples of this
type of machine interaction.
One of my first Chomskyic interactions was BASIC (Beginners All-purpose Symbolic Code). More recently I became enamored with Bash, (Borne Again SHell) to which I have humbly contributed the Visual Bash structural sugar as
enforced by "shebangs" which is the basis for the Visual Bash FED -
(Function. Evaluator and Dispatcher :^). There are many other examples
of Chomskyish, many come to mind... Fortran, Forth, Assemblers,Podman,
Docker, distrobox, and postscript to name just a few, and there is so much more.
So another project topic, a winter's quest...can I forge _javascript_/GoogleScript into a "Chomskyish" structure? This is the major bit of ignorance I still need to overcome in _javascript_.
As I mentioned weeks ago, the good news here is that there is a single
standard for _javascript_ maintained by the European Computer Manufacturers
Association (ECMA), and while they are up to version 6, to my knowledge,
unlike python they have not broken the earlier versions. A feature!
Again to repeat, there are _javascript_ dialects...
GoogleScript seems to be a rather faithful version of ECMA6, and I believe
the mere existence of "GScript" may go a long way to keep Micro$oft and
Visual Studio Code (VScode) editor honest, they love to Embrace, Extend and
Eliminate anything they did not invent. Most folks follow the VScode path.
While VScode Editor is supposed to be open source, I simply
prefer developing in GScript and exporting the completed code.
Bluefin installs VScode on your Desktop whether you want it or not.
So in a perfect world, "Chomskyish" Java/GoogleScript might be called
"ChomskyScript", based on it following the FED principles of Visual
Bash.
Hell! another damned project!!!
One El-dorado I will continue to alternatively seek is a way to expand
Visual Bash or more specifically how to operate Bash as a _javascript_ plug-in.
This may or may not be possible, but it is a fun quest of which I will
attempt to keep you informed...
Maybe the way to ChomskyScript is to carefully lawyer-read the ECMA6
specification and shoehorn it in. Any takers?
My plans for spring include my dream of a meet up of Adult Swim at SugarTower. The working title of this is for now "Open Source Summer Camp" (OSSC) Sing out or attend this evening's meeting in person if you are interested in the SugarTower TechnoRubble organizational project, the OSSC, or the loot.
What would you think of a Summer festival maybe including other FOSS groups
such as the Free Software Foundation? We have a nice 10 acre facility for this
at SugarTower in Williamstown, Vermont.
Tonight, we hopefully shall expand the Bluefin version of Virtual Immutability and
Associated Containers (VIAOC). DTG continues patiently coaching me on VIAOC which is a really cool development environment based upon both KVM and podman. I have preserved the SuSe Aeon which got me started on this quest. Maybe the way is Red Hat... Dave indicates this would be transparent, it is not.
In the meantime we cannot ignore this 800 lb. gorilla. Again, another of this
winter's ambitions to forge in the VIAOC environment include, mastering Pipewire in this, we may be delving into some audio evil... AudioEvil.sh is a mythical Visual Bash script yet to be written, which strikes me as a good name for a bash script to implement and monitor acquisition of protected audio streams (Piracy :^).
As I have mentioned in the past, the next logical step after AudioEvil.sh would be AVRelay.sh. AVRelay would trans-code between different video conferencing applications (E.G. RTSP to jitsi to zoom). Basically, one example; you would run a jitsi server on a container or virtual machine which would relay to an RTSP client. Another example might be to relay an audio-video from one market to another.
Hopefully this will all tie into Kubernetes...
That said, we have a meeting tonight at 6PM.
The life lesson here is that serious development remains for the winter.
Winter shall soon allow us to answer questions like:
- An VIAOC based Arduino and Pi development environment that "Breaths" Code.
- Can we build a Large Language Model server? (Preferably on the cheap)
- Can I use Chat GPT to generate VisualBash scripts?
- Would it make sense to store VisualBash functions in MariaDB?
...so more about these foolish ideas is available this Monday evening at 6 PM at the York Library
in beautiful East Barre Vermont. Thus we are centralizing and convocating at the York
Branch Library this evening. That said, come in person or remotely and bring this and any
other problems and questions and we shall do our thing!
Again this evening, beyond the Library face-2-face & gizmo-2-gizmo, we shall use
https://meet.jit.si/bosi to connect.
Come on to
https://meet.Jit.si/bosi at 6PM! Feel free to click the following link to join...
Feel free to click the following link (around 6PM tonight) to join the meeting:
https://meet.jit.si/bosiLet me know if this works for everyone...
=====
Just want to dial in on your phone?
Dial-in: +1.512.402.2718 PIN: 1992759198#
Note that this dial worked with devastating effect from the road...
Click this link to see the dial in phone numbers for this meeting:
https://meet.jit.si/static/dialInInfo.html?room=bosiTime to get cracking for Halloween!
Kindest Regards,
Paul Flint, Director
Barre Open Systems Institute
