@Tlusty

Starting to work on a WebSecurity Platform again

deciding on making architecture of FS for future use of commands

Today i was looking into how to make my calculator better then i found inspiration

https://github.com/nikita9604/Scientific-Calculator-with-Keypad.git

I will try to remake this code myself for this calculator to make it POWERFUL!

today didn t have time to work much but i managed to fit extra 40 min , so today i worked on code optimization and planning to add extra features to this calculator

i think the whole project was really funny i can t wait until i see my teacher face when i pull this out mid exam

Today i worked on kittycalc in arduino IDE code is really messy needs working but the project is assembled and it is working

Devlog 2: Command History & Interactive VFSImplemented a fully functioning command history. No more retyping commands. ArrowUp and ArrowDown now traverse the bash history with proper state resets on Enter, coded completely from scratch But the roadmap is shifting. I’m turning this terminal into a simulated Linux-like Virtual File System (VFS). The plan is to build a mock directory structure where users can run ‘cd’, ‘ls’, and ‘cat’ This won’t just be an aesthetic feature. The goal is to demystify Linux system architecture for beginners. By navigating directories like /etc, /bin, or /var directly in the web terminal, people will learn where critical system files and configurations hide, and how misconfiguring them can compromise a whole system

Devlog: Pivoting KittyCalc from Assembly to C (And Why Hardware is Hard)To be honest, I was a little shy about recording myself at the start of this project. Why? Because the beginning was messy, chaotic, and downright bad. But hardware is hard, and there is no point in hiding the struggle It all started with an idea, some thoughts, and a custom 3D model of a cat-ear enclosure I designed. With the design ready, I decided to take the hardcore route: writing the firmware in pure Assembly (ASM).Everything was going relatively fine until I hit the ultimate roadblock: programming the LCD screen Trying to write I2C communication protocol logic and drive an LCD display directly in raw Assembly for my first hardware project was a special kind of masochism. After staring at register maps for way too long, I made the executive decision to change things I am officially pivoting to C.It is not a defeat; it is pure optimization. Using C will let me actually finish the I2C logic, get the screen working, and keep the project moving forward without getting stuck in ASM register hell forever Next steps:Set up the C toolchain and SDKWire up the I2C backpack once it arrives in my local parcel locker Print the cat-ear enclosure on the Bambu printer once the rails are lubricated The grind continues

Devlog 1: started building a lightweight, vanilla JS retro web terminal from scratch (no frameworks, no AI).

But as I was fixing bugs and styling the prompt, I realized something. Why not use my own projects to teach others cybersecurity?

So, I turned my terminal into the first interactive lab for my upcoming project: CyberSecurityLearningLabs In the latest update, I intentionally swapped textContent with innerHTML inside my terminal history function. This opens up a textbook DOM-based XSS vulnerability.

If you type a malicious payload like an img tag with an onerror event directly into the terminal, the browser parses the HTML, fails to load the broken source, and triggers the JavaScript payload (like a classic alert pop-up).

I left a hint in the code comments explaining how to patch it using textContent, making it a perfect, hands-on demonstration of why sanitization matters

an investment calculator that makes the journey to financial independence real and achievable for everyone. Using Next.js