Langjam-Gamejam Devlog: Making a language, compiler, VM and 5 games in 52 hours
https://github.com/Syn-Nine/gar-lang/blob/main/DEVLOG.md
#HackerNews #Langjam #Gamejam #Devlog #Language #Compiler #VM #Game #Development
Langjam-Gamejam Devlog: Making a language, compiler, VM and 5 games in 52 hours
https://github.com/Syn-Nine/gar-lang/blob/main/DEVLOG.md
#HackerNews #Langjam #Gamejam #Devlog #Language #Compiler #VM #Game #Development
Just finished writing another tool, now I can see NINE known compromised packages are still up for download on NPM! ⚠️
This tool crawls the list of known bad packages and downloads the latest bundle.
It then runs my other checks against the downloaded bundle and logs the results.
https://github.com/datapartyjs/walk-without-rhythm
#WalkWithoutRhythm #Sha1Hulud #NPM #GitHub #Microsoft #nodejs #javascript #cybersecurity #devlog #bash
Updated my listing of Sha1-Hulud detection tools.
I now have found at least 12 other tools for detecting Sha1-Hulud compromise on your dev box and in infrastructure.
#WalkWithoutRhythm #Sha1Hulud #npm #github #nodejs #javascript #cybersecurity #devops
Just finished writing another tool, now I can see NINE known compromised packages are still up for download on NPM! ⚠️
This tool crawls the list of known bad packages and downloads the latest bundle.
It then runs my other checks against the downloaded bundle and logs the results.
https://github.com/datapartyjs/walk-without-rhythm
#WalkWithoutRhythm #Sha1Hulud #NPM #GitHub #Microsoft #nodejs #javascript #cybersecurity #devlog #bash
if you're getting an aneurysm trying to understand how those mtof cases work, that's because you're trying to read it as a function, but the "function head" is the `then` section, at the end of the block rather than the beginning.
in datalog/prolog, order would be correct:
mtof(m, ...) :- ge(m, 0), ...
but then regular rules are not in execution order.
i'm going to explain the relational model with diagrams in an extra post.
so i'm thinking, step 1 is adding "inline" buffers (a solution from soufflé), for which cases don't generate code, and which in usage get inlined directly into other cases.
this already covers the need i have for functional macros and i can put off supporting C exports to a later point.
alright. today's job: support for defining C functions in LRDL.
this should generalize far enough that we can implement `main` this way, and also write shared libraries with it.
but it requires opening the reactor pattern to external users. it significantly complicates interactions and update flow.
hmhmhm. difficult to extract the smallest most elegant idea that works.
Working on BLE packet sniffing and transmission for MeshTNC, bc who doesn't want to do APRS or meshcore over BLE advertisements 😉
My quick hack feels promising so I think I'll clean this up and PR it.
Just needed one tweak to the KISS encoder to define our port usage and give myself a way to put BLE data out a different port than LoRa data when in KISS mode.
Planning to also support streaming GPS NMEA over KISS eventually as well as promiscuous mode WiF sniffing.... eventually.
So reserved some values for that stuff.
Here I was thinking the KISS protocol support was going to be hard ✨
Actually this flew together, mostly bc @meph already did all the hard stuff on KISS handling.
So just check which output mode we're in and yeet the data at the BLE data KISS port.
#amateurradio #wardriving #ble #embeded #esp32 #devlog #MeshTNC
Just needed one tweak to the KISS encoder to define our port usage and give myself a way to put BLE data out a different port than LoRa data when in KISS mode.
Planning to also support streaming GPS NMEA over KISS eventually as well as promiscuous mode WiF sniffing.... eventually.
So reserved some values for that stuff.
First things first, I want to make it so that the ASCII CSV output format for BLE packets roughly matches LoRa packets.
Every packet gets an arrival timestamp, type, RSSI and SNR values. Followed by whatever payload.
In the case of BLE packets there's also a 6 byte MAC so I slap that infront of the payload.
There's no SNR data for BLE so that's always 0.0. But the RSSI is good.
Here I was thinking the KISS protocol support was going to be hard ✨
Actually this flew together, mostly bc @meph already did all the hard stuff on KISS handling.
So just check which output mode we're in and yeet the data at the BLE data KISS port.
#amateurradio #wardriving #ble #embeded #esp32 #devlog #MeshTNC
Working on BLE packet sniffing and transmission for MeshTNC, bc who doesn't want to do APRS or meshcore over BLE advertisements 😉
My quick hack feels promising so I think I'll clean this up and PR it.
First things first, I want to make it so that the ASCII CSV output format for BLE packets roughly matches LoRa packets.
Every packet gets an arrival timestamp, type, RSSI and SNR values. Followed by whatever payload.
In the case of BLE packets there's also a 6 byte MAC so I slap that infront of the payload.
There's no SNR data for BLE so that's always 0.0. But the RSSI is good.