Just vibe coded a calendar based group meeting app. A group of friends create a calendar and share the link, can coordinate in the chat, and in a calendar choose the day and time to meet. Everybody votes and that's it. All this in a nice brutalist web design. And no registering needed.
When they say "The episode occurred when threat actors gained access to this third party legacy system which was not decommissioned properly. " for me it sounds like a not properly wiped disk that got into the the bad guys hands. It would be interesting to know more to be prepared for proper decommissioning of hardware.
A cpp code generator like esphome, to generate the firmware for midi devices in a simple yaml file, for raspberry Pico.
It would have been so much easy just to program the midi hub I wanted to program but wanted to make it generic.. now I can make the firmware for any configuration in seconds!
If I were them I would make sure the V3 instructions are not used until late in the boot process, and some apt command that makes sure all installed programs are in the right subarchitecture for the running system, reinstalling as necessary.
But that does not sound like a simple for non technical users solution.
Anyway, non technical users using an installation on another lower computer? That sounds weird.
I use home assistant and a smart plug to get notifications when the socket has less than 1w load for 5 mins -> washing machine finished. Maybe one of the best automations I have. And all local.
Happened to me last week. One morning we wake up and the whole company website does not work.
Not advice with some time to fix any possible problem, just blocked.
We gave very bad image to our clients and users, and had to give explanations of a false positive from google detection.
The culprit, according to google search console, was a double redirect on our web email domain (/ -> inbox -> login).
After just moving the webmail to another domain, removing one of the redirections just in case, and asking politely 4 times to be unblocked.. took about 12 hours. And no real recourse, feedback or anything about when its gonna be solved. And no responsibility.
The worse is the feeling of not in control of your own business, and depending on a third party which is not related at all with us, which made a huge mistake, to let out clients use our platform.
rtpmidid[1]. After getting some hardware synthesizers and wanting to connect them without using a computer.. but being able to use them too using the computer I stumbled upon with rtpmidi the protocol and it ticked all the boxes I needed. I could connect all my gear to a raspberry pi, use ALSA sequencer to connect devices to each other with another of my programs AseqRC[2], and then use my synths from my DAW without touching any cable.
So after a fast prototype I created rtpmidid and I'm quite happy on how it works.
And it also helps with the USB ground loop noise that it seems unavoidable some times.
For some time I had even two Orange Pis connected to two sections of my gear, using USB gadget support so my MPC One could speak rtpmidi. MPC One has support to connect as host to MIDI devices, but as guest (connect to the computer) only in controlled mode which is not what I needed to convert my MIDI tracks to my DAW.
I will add the request for ALSA sequencer devices, which I think should include Jack ones.. but I will investigate this further, as maybe I'm wrong. There is a bridge for sure.
Anyway just don't hijack the MIDI device and be nicer with the linux MIDI ecosystem is a must.
And don't forget distcc [1], together they can speed up compilations and recompilations. I remember using colleague computers to speed up a 30 min C++ compilation to just 5 min... to just seconds on second compilation.
For reference, as I didn't know, posits are a modern float number alternative to IEEE 754. Wikipedia[1] claims better in many aspects, but, as ubiquitous as IEEE numbers are I don't see them getting replaced soon.
IANAL, but as far as I know it's very important it's GPLv3 which means the antitivoization clause, which means that hardware that uses this firmware must provide full source code and a way to let you use your own firmware.
If somehow this code is not in a firmware... No idea.
Not exactly what you are looking for, but I created a web interface for ALSA sequencer, which effectively makes any raspberry pi what you are looking for.
For old MIDI DIN you would need a MIDI adapter or use the raspberry pi serial ports and some circuitry. Can be powered by an USB powerbank for example.
I've been using the Pi agent with Deepseek for some days.. and I'm more than happy with that.