Devlog 1 - Started Working

So i thought of an idea on making a game emulator that could run basic old games on your terminal , so like you have some random fun things to play when your bored . I first started with making a box and getting a “@” moving in it using W A S D, then i built a working snakes game, Then I made a working snakes and added play again feature , in the game and it is working properly for this setup , i dont know my VS code was showing file errors but my cmake build worked properly so like my build feature is working but its a vs code error in file detection and also i basically added multiple apples as per your score , maximum currently goes to 4 apples with 15 + Score
Score 0–4 → 1 apple
Score 5–9 → 2 apples
Score 10–14 → 3 apples
Score 15+ → 4 apples

Finished with Snakes

SO uhh i started working on sm other things and it am on a learning stage

Devlog - 2 - made it work with VMs (kind of)

Last time I worked my node could already listen to TCP port 8765, recieve JSON msges , respond to hello, return basic system info. WAS not really a big mesh it was just a basic mesh, then I thought of actually start making an actual network. First I tried connecting across VMs and environments but that ended not good as I used a nest VM and its pretty restricted so I just thought why not first experiment on Codespace and thankfully that worked , It ran on 2 different nodes, laptop and codespace with same port, I faced some problems with port forwarding on codespace initially it was due to the wrong gh port being used , and same being used at the same times, now i also added it so it could talk with “python test_client.py 127.0.0.1 9000” like now it was not js working locally rather on a specified tcp address.
Now here comes the biggest part I added a peer system , it basically means a MESH node can remember other nodes on the network, a peer represents another node and currently stores - id, endpoint, last seen and status.
Added a peer registry which is basically the local database of these peers
Added register, allowing one node to tell another “I exist, and here’s how you can reach me…”
Current MESH state: nodes can communicate remotely, identify themselves, register peers, and maintain basic peer state.

Devlog 1 - Js started

I started making my mesh in python , I first needed to understand how the mesh actually worked so for first few hours i was trying random things on my pc with python that might add onto my mesh later on , i first start with making my protocol file which basically define the messages that my MESH nodes will understand, wasnt really that tough , then later on I went to make my first Node, i first defined ports and hosts and then went on to defining how they will communicate and how it will be done, and for the cli i for now gave it one command only

For now i really js made my terminals communicate , later i will add more features

Devlog - 1 yayyy!!

So I started making a website that shows you realtime ISS data , like what region is it currently above , i used vanilla with javascript vite for this projecttt , made front page
Also completed with the main functionality of the the website where it shows the data of the main positioning and everything..

And also added cards of the current heroes, the people in the space right nowww!!
Check it out for urself!!

Made this whole site in One GO!! I mean not exactly but like I completed it and then i am devlogging bcs yk i was kind of locked in with all the debugging and thinking for my custom sizes and layouts of my website work,
First I completed with the HTML in like 2 Hours because the shi just kept going wrong, like its on a random offset, and sometime its size is just so wrongg !!!! But i finally got it done!
Then I was doing CSS all the time it had was just me having fun and trying random font colors from the HEX Website to see what went it and what font went with my website !! And in final it looks good and Im pretty happy about making this website..

Almost done with the Basic HTML part and this was easy, easier than i thought i cant lie i thought this would be much more tougher i mean its not my first time and compared to my previous projects this was kind of easy , ngl It took me some to write and think becauase no AI usage really is bad, but Guide helped abit throughout the way i cant lie, so uhh i am then done and will start CSS now.

Almost done with the Basic HTML part and this was easy, easier than i thought i cant lie i thought this would be much more tougher i mean its not my first time and compared to my previous projects this was kind of easy , i love completing hackclub’s missions, and the guide also made it so much easier, ngl It took me some to write and think becauase no AI usage really is bad, but Guide helped alot throughout the way i cant lie, so uhh i am then done and will start CSS now

FINALLY FIXED EVERYTHING AND THANKS TO GOD MY TERMINALLL IS WORKING PROPERLY!!!! I currently only added 4 commands to it but i find it pretty cool for my first WebOS. Thankfully i hope i get reviewed good :)))

Tried adding a terminal application inside my WebOS with commands but accidentally ran into an error that restricts my Application opening, i.e i might have forgot to define div id properly , will fix it soon enough and come up with the terminal feature that works properly and name defined as “root@churu” want to give it the linux vibes yk.

I First made a loading screen which is very easy to make all it needed was to use some HTML to make the loading screen appear and then all it needed was basic CSS for it cover the whole screen to give it a very cool effect and then i js took some help with javascript to make the bar load, also Made the whole inside as in the images below i have shown that all the apps i made via javascript are shown i used wttr API via wttr.in for weather broadcast and the thing is it does not require any API key and is totally free and works pretty good i mean it does sometimes show random weather but yeah it is a very good API that can be used. and For the images i js kept a web theme and a kind of a spiderman theme cuz it looks cool like that.

I First made a loading screen which is very easy to make all it needed was to use some HTML to make the loading screen appear and then all it needed was basic CSS for it cover the whole screen to give it a very cool effect and then i js took some help with javascript to make the bar load, also Made the whole inside as in the images below i have shown that all the apps i made via javascript are shown i used wttr API via wttr.in for weather broadcast and the thing is it does not require any API key and is totally free and works pretty good i mean it does sometimes show random weather but yeah it is a very good API that can be used. and For the images i js kept a web theme and a kind of a spiderman theme cuz it looks cool like that.

so i made this voice assistant “jarvis” in python
basically it listens for a wake word, then you talk to it, and it replies or runs stuff like opening apps / answering questions / whatever i wired into it
I built a Python voice assistant called Jarvis. It listens for a wake word “Jarvis”, processes spoken input, and then responds using tts or executes basic system actions like opening apps, running commands, or answering queries through an AI/API layer.

How it works (in simple terms)

The flow is basically:

1. Microphone input
   The program constantly listens through the mic until it detects the wake word.
2. Wake word detection
   Once “Jarvis” is detected, it switches into active listening mode.
3. Speech-to-text
   Your speech is converted into text using a speech recognition engine.
4. Processing layer
   The text is either:
   matched to predefined commands (like opening apps, searching, etc.), or
   sent to an AI model/API for a response
5. Response output
   The response is converted back to speech and played through speakers.
6. State control
   It manages states like “listening”, “thinking”, and “speaking” so it doesn’t overlap audio input and output.
   at first it was kinda simple but then everything started breaking

mic input was the first pain
it either didn’t hear me or picked up the wrong device
spent way too long just figuring out why it was “silent” but actually listening to the wrong mic

then speech recognition started being annoying
like it would randomly misunderstand words or just freeze if i spoke too fast

also made the classic mistake of letting it listen while it was speaking
so it would hear its own voice and start looping responses , so i had to add a lock so it doesnt talk while talking

biggest headache was the API / env stuff
worked fine when i ran python main.py
then i packaged it and suddenly everything was “missing key / file not found / module not found”

turned out i had hardcoded paths and assumed my machine layout is universal fixed that by making paths dynamic + cleaning up env loading

also packaging with pyinstaller was pain
some imports just randomly didn’t show up in dist build and i had to manually force include them

now it mostly works but i still feel like it’s fragile,
one change and it might break again.

but yeah overall it taught me:

audio stuff is way harder than it looks
packaging python apps is cursed
and debugging voice stuff is basically just “try everything until it works”