|
4201
|
My first slack bot! by @priyavishnuch | Stardance
|
priyavishnuch
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @priyavishnuch | Sta Title: My first slack bot! by @priyavishnuch | Stardance...
|
1792770627.048289
|
1793375427.048289
|
|
4202
|
Screen Time Tracker Widget by @Mathman14159 | Star Screen Time Tracker Widget by @Mathman14159 | Stardance...
|
Mathman14159
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Screen Time Tracker Widget by @Mathman14159 Title: Screen Time Tracker Widget by @Mathman14159 | Stardance...
|
1792662720.093664
|
1793267520.093664
|
|
4203
|
Flapy bird AI model by @CY3er | Stardance
|
CY3er
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Flapy bird AI model by @CY3er | Stardance
|
1792727488.291065
|
1793332288.291065
|
|
4204
|
A galaxy website by @Trixie | Stardance
|
Trixie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A galaxy website by @Trixie | Stardance
|
1792551222.420632
|
1793156022.420632
|
|
4205
|
Untitled by @starlitfire | Stardance
|
starlitfire
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @starlitfire | Stardance
|
1792795826.3219178
|
1793400626.3219178
|
|
4206
|
Lyrically Inclined by @RishabhGarg | Stardance
|
RishabhGarg
|
0
|
1.6
|
0
|
[]
|
[{"post_id": 997, "ts": "2026- [{"post_id": 997, "ts": "2026-06-02T19:36:01Z", "hours": 0.9886, "text": "Installing postgres and setting up the vector + regular database of lyrics"}, {"post_id": 657, "ts": "2026-06-02T05:57:00Z", "hours": 0.6136, "text": "Set up the initial app structure and webpage with Flask and Bulma"}]...
|
Title: Lyrically Inclined by @RishabhGarg | Starda Title: Lyrically Inclined by @RishabhGarg | Stardance
Devlogs:
Set up the initial app structure and webpage with Flask and Bulma
Installing postgres and setting up the vector + regular database of lyrics...
|
1792554763.511527
|
1793159563.511527
|
|
4207
|
Froststrap by @SysError06 | Stardance
|
SysError06
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Froststrap by @SysError06 | Stardance
|
1792630256.5313296
|
1793235056.5313296
|
|
4208
|
Slice of a pie - goal tracker by @adwitha | Starda Slice of a pie - goal tracker by @adwitha | Stardance...
|
adwitha
|
0
|
13.14
|
0
|
[]
|
[{"post_id": 47769, "ts": "202 [{"post_id": 47769, "ts": "2026-08-15T22:41:18Z", "hours": 1.0153, "text": "I worked on adding two new functionalities for this devlog, which were the new sidebar and making the check-in frequency value chosen be used for its intended purpose Goal The main goal of this devlog was just setting up the necessary features for the big upcoming addition which is the daily check-in feature where the app keeps track of what progress has been made on goals that have check-ins due on that day. This information will also be used for the journal feature that will be added later on. The Sidebar For the sidebar, I realized that I wouldn’t need a dedicated sidebar to store all the buttons for navigation, as there aren’t many buttons necessary, so I decided to create a sort of hybrid sidebar that just lived on the side of the main page. I also think this is much more visually pleasin design as the floating logos glide behind it and it feels very integrated. This was a simple addition where I just made a sidebar outside of the main homepage content div and styled it to look the way it is. It also has a hover effect, which simply makes the background’s opacity increase. Currently, I have not built either of these menus yet so the buttons do not do anything. I will be adding functionality to the Daily Check-in button in the next devlog. Check-in frequency This is what I originally started working on for this devlog, but I realized that I don’t even have a way to get to the check-in page besides when it automatically pops up once daily. Therefore, I added the sidebar. As for progress on this, I have made the goal object take in the chosen option and store it in a variable. I have added a function which uses this info and the last done check-in to find out whether there is a check-in due on that particular day for the passed in goal. This will be called in the daily check-in menu function that I will be making next. If this gives true, then that goal will have a check-in in today’s check-in"}, {"post_id": 44793, "ts": "2026-08-10T20:06:52Z", "hours": 0.8836, "text": "I worked on two new features for this devlog. One was kind of an impulse decision to add floating logos that bounce off the edges of the main page, like the DVD logo, and the other was making the time remaining section work on the goal cards instead of being a placeholder. Floating logos I felt like the background was super plain here and it felt kind of soulless, so I decided to give it that little nostalgic touch and have logos bounce around the user’s screen without making them too distracting. I made this by adding 7 floating logos outside of the main HTML, and then I Used the Math.random function to randomize the object’s size, speed, and starting point Adjusted the opacity of them so they won’t be too annoying Bounded the speed so they all are roughly moving at the same type of speed with slight variation Made them bounce off the edges of the screen using the window width and height and negating their speed value when they come in contact with the boundary With that done, I was testing the app’s functionality and discovered that the days remaining was still using a placeholder of “5 days,” which I had put there earlier. Days Remaining I made this work by writing a function that calculated how many days remained between the current day and the chosen completion date. I did this by using the new date() function to get dates in the format where I could directly subtract them to get the remaining days. This made it very convenient to work with."}, {"post_id": 44411, "ts": "2026-08-10T04:17:17Z", "hours": 3.1861, "text": "I have been working on adding functionality to the app as I was getting pretty satisfied with how the UI looked. I started by adding the functionality for the goals to be saved as one object so they can be stored and retrieved easily Setting up goals I did this by creating a goals array that holds each goal, and I added a function that is triggered when the “add goal” button is pressed in the add goal menu. Within this function, I added a goal object which held the following: A randomly generated ID to easily access a goal The title The description The completion date The category of the goal The chosen check-in frequency The milestones With this, the goal could be easily stored, accessed, and edited by simply changing the information within the goal object in the goals array. With this made, I needed a way to display the information entered on the screen, so I created what I call goal cards. Goal Cards Making the goal cards was a very cool learning experience as I got to deal more with dynamic HTML creation. Once the Add Goal button was clicked, it would call the displayGoal function. This function would: Get all the information from the particular goal object we are displaying Create the goal card using dynamic object creation and add CSS classes that have been made for it Update the goal card every time it is edited, like when milestones are checked off; it will update the progress bar. Speaking of the progress bar, clicking on the goal card brings up the menu shown in the image below, which allows the user to see a bigger view of the goal and allows them to check off milestones. I plan on expanding this to add editability to goals and other functionality. Goal menu This was created using the same technique as the add goal menu from a previous devlog, but instead of showing the same information for everything, it changes based on the goal object being targeted. The styling is not perfect yet, as I was focusing on the functionality more, but as more is changed, it will look closer to the true final product. Conclusion Overall, this was a very productive devlog, and I think I learned a lot of new valuable skills in JavaScript. I think the next thing I will work on is adding the check-ins and setting up the data to be stored locally so it doesn’t go away after a page refresh."}, {"post_id": 32686, "ts": "2026-07-22T00:16:02Z", "hours": 6.3917, "text": "I have been working on the frontend of the app updating it to look more like how I want it to when the app is published. The first image showcases the main page of the app where the goals that are added will show up seperated by short term, medium term, and long term. New goals can be added by pressing the add goal button under each subdivision. Pressing that button brings up the menu from the second image, which is the menu to add a new goal. This menu sets up not only a goal to achieve, but a plan to stick to it. This includes setting up a check-in frequency that tells the app how often in the daily check-ins there should be a progress update for this particular goal. This also includes setting up milestones/steps to achieving a certain goal. This allows for progress tracking of a goal that was set up, and even a feature where the app tells you if you are behind, on track, or ahead on your goal. The biggest challenge I faced while creating this was the feature for adding your own custom milestones, as it was designed to give a lot of freedom to the user. You can move the milestones that were added, give them specific completion dates, or choose to let the app space them evenly. You can add as many milestones as you want, and you can even choose not to add specific milestones and let the app deduce how many and how to split up the milestones. The reason this was difficult was that I have very minimal experience with JavaScript, so this took a lot of time to design, troubleshoot, and iron out. My next steps are to start working on the backend so that the stuff that is entered in the goal setup menu is actually reflected in the main page, and the daily check-in system is setup"}, {"post_id": 7627, "ts": "2026-06-12T19:05:30Z", "hours": 1.6583, "text": "Hi, I am currently learning HTML, CSS, and JavaScript, and along the way, I wanted to make a project to solidify my learning: A goal tracking app! I am very excited to share my current progress, as I was able to make an overlay menu that displays over the app without going to a different page. This was a difficult task as I had not worked with JavaScript before, but with the help of resources like Stack Overflow, I was able to figure out how to implement it! I used an on() and an off() function that displayed a full-screen overlay, which had a child overlay containing the pop-up menu. This can be seen in the second picture below. The overlay is display= “none” by default and then gets set to display= “flex” when the on() function is called. Off() sets it back to none. I haven’t added the exact content that I want or styled anything yet, but I just wanted to share this milestone! The app that I am making is a goal-tracking app that allows the user to add different types of goals (short, medium, long term) to keep track of their goals. The app will also keep the user accountable as it will require the user to set steps/mini goals that need to be achieved, and will have the user complete a daily check-in to track their progress. Different types of goals can have different time frames, and the app will account for that. The user can input a time frame, or the app will use pre-determined values."}]...
|
Title: Slice of a pie - goal tracker by @adwitha | Title: Slice of a pie - goal tracker by @adwitha | Stardance
Devlogs:
Hi, I am currently learning HTML, CSS, and JavaScript, and along the way, I wanted to make a project to solidify my learning: A goal tracking app! I am very excited to share my current progress, as I was able to make an overlay menu that displays over the app without going to a different page. This was a difficult task as I had not worked with JavaScript before, but with the help of resources like Stack Overflow, I was able to figure out how to implement it! I used an on() and an off() function that displayed a full-screen overlay, which had a child overlay containing the pop-up menu. This can be seen in the second picture below. The overlay is display= “none” by default and then gets set to display= “flex” when the on() function is called. Off() sets it back to none. I haven’t added the exact content that I want or styled anything yet, but I just wanted to share this milestone! The app that I am making is a goal-tracking app that allows the user to add different types of goals (short, medium, long term) to keep track of their goals. The app will also keep the user accountable as it will require the user to set steps/mini goals that need to be achieved, and will have the user complete a daily check-in to track their progress. Different types of goals can have different time frames, and the app will account for that. The user can input a time frame, or the app will use pre-determined values.
I have been working on the frontend of the app updating it to look more like how I want it to when the app is published. The first image showcases the main page of the app where the goals that are added will show up seperated by short term, medium term, and long term. New goals can be added by pressing the add goal button under each subdivision. Pressing that button brings up the menu from the second image, which is the menu to add a new goal. This menu sets up not only a goal to achieve, but a plan to stick to it. This includes setting up a check-in frequency that tells the app how often in the daily check-ins there should be a progress update for this particular goal. This also includes setting up milestones/steps to achieving a certain goal. This allows for progress tracking of a goal that was set up, and even a feature where the app tells you if you are behind, on track, or ahead on your goal. The biggest challenge I faced while creating this was the feature for adding your own custom milestones, as it was designed to give a lot of freedom to the user. You can move the milestones that were added, give them specific completion dates, or choose to let the app space them evenly. You can add as many milestones as you want, and you can even choose not to add specific milestones and let the app deduce how many and how to split up the milestones. The reason this was difficult was that I have very minimal experience with JavaScript, so this took a lot of time to design, troubleshoot, and iron out. My next steps are to start working on the backend so that the stuff that is entered in the goal setup menu is actually reflected in the main page, and the daily check-in system is setup
I have been working on adding functionality to the app as I was getting pretty satisfied with how the UI looked. I started by adding the functionality for the goals to be saved as one object so they can be stored and retrieved easily Setting up goals I did this by creating a goals array that holds each goal, and I added a function that is triggered when the “add goal” button is pressed in the add goal menu. Within this function, I added a goal object which held the following: A randomly generated ID to easily access a goal The title The description The completion date The category of the goal The chosen check-in frequency The milestones With this, the goal could be easily stored, accessed, and edited by simply changing the information within the goal object in the goals array. With this made, I needed a way to display the information entered on the screen, so I created what I call goal cards. Goal Cards Making the goal cards was a very cool learning experience as I got to deal more with dynamic HTML creation. Once the Add Goal button was clicked, it would call the displayGoal function. This function would: Get all the information from the particular goal object we are displaying Create the goal card using dynamic object creation and add CSS classes that have been made for it Update the goal card every time it is edited, like when milestones are checked off; it will update the progress bar. Speaking of the progress bar, clicking on the goal card brings up the menu shown in the image below, which allows the user to see a bigger view of the goal and allows them to check off milestones. I plan on expanding this to add editability to goals and other functionality. Goal menu This was created using the same technique as the add goal menu from a previous devlog, but instead of showing the same information for everything, it changes based on the goal object being targeted. The styling is not perfect yet, as I was focusing on the functionality more, but as more is changed, it will look closer to the true final product. Conclusion Overall, this was a very productive devlog, and I think I learned a lot of new valuable skills in JavaScript. I think the next thing I will work on is adding the check-ins and setting up the data to be stored locally so it doesn’t go away after a page refresh.
I worked on two new features for this devlog. One was kind of an impulse decision to add floating logos that bounce off the edges of the main page, like the DVD logo, and the other was making the time remaining section work on the goal cards instead of being a placeholder. Floating logos I felt like the background was super plain here and it felt kind of soulless, so I decided to give it that little nostalgic touch and have logos bounce around the user’s screen without making them too distracting. I made this by adding 7 floating logos outside of the main HTML, and then I Used the Math.random function to randomize the object’s size, speed, and starting point Adjusted the opacity of them so they won’t be too annoying Bounded the speed so they all are roughly moving at the same type of speed with slight variation Made them bounce off the edges of the screen using the window width and height and negating their speed value when they come in contact with the boundary With that done, I was testing the app’s functionality and discovered that the days remaining was still using a placeholder of “5 days,” which I had put there earlier. Days Remaining I made this work by writing a function that calculated how many days remained between the current day and the chosen completion date. I did this by using the new date() function to get dates in the format where I could directly subtract them to get the remaining days. This made it very convenient to work with.
I worked on adding two new functionalities for this devlog, which were the new sidebar and making the check-in frequency value chosen be used for its intended purpose Goal The main goal of this devlog was just setting up the necessary features for the big upcoming addition which is the daily check-in feature where the app keeps track of what progress has been made on goals that have check-ins due on that day. This information will also be used for the journal feature that will be added later on. The Sidebar For the sidebar, I realized that I wouldn’t need a dedicated sidebar to store all the buttons for navigation, as there aren’t many buttons necessary, so I decided to create a sort of hybrid sidebar that just lived on the side of the main page. I also think this is much more visually pleasin design as the floating logos glide behind it and it feels very integrated. This was a simple addition where I just made a sidebar outside of the main homepage content div and styled it to look the way it is. It also has a hover effect, which simply makes the background’s opacity increase. Currently, I have not built either of these menus yet so the buttons do not do anything. I will be adding functionality to the Daily Check-in button in the next devlog. Check-in frequency This is what I originally started working on for this devlog, but I realized that I don’t even have a way to get to the check-in page besides when it automatically pops up once daily. Therefore, I added the sidebar. As for progress on this, I have made the goal object take in the chosen option and store it in a variable. I have added a function which uses this info and the last done check-in to find out whether there is a check-in due on that particular day for the passed in goal. This will be called in the daily check-in menu function that I will be making next. If this gives true, then that goal will have a check-in in today’s check-in...
|
1792731051.952001
|
1793335851.952001
|
|
4209
|
My awesome macropad! by @baluwaladaniyal | Stardan My awesome macropad! by @baluwaladaniyal | Stardance...
|
baluwaladaniyal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @baluwaladaniyal | Title: My awesome macropad! by @baluwaladaniyal | Stardance...
|
1792738164.965687
|
1793342964.965687
|
|
4210
|
My first slack bot! by @Maria717 | Stardance
|
Maria717
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Maria717 | Stardanc Title: My first slack bot! by @Maria717 | Stardance...
|
1792576149.1608088
|
1793180949.1608088
|
|
4211
|
Wheat Operating System (WheatOS) by @Ravduct | Sta Wheat Operating System (WheatOS) by @Ravduct | Stardance...
|
Ravduct
|
0
|
60.63
|
0
|
[]
|
[{"post_id": 80878, "ts": "202 [{"post_id": 80878, "ts": "2026-10-19T04:37:06Z", "hours": 9.5486, "text": "Heap Allocation For Kernel I make heap allocations for the kernel (kmalloc and kfree). It will reserve a certain amount of memory for the kernel. I will do heap allocation for user later."}, {"post_id": 76992, "ts": "2026-10-05T08:56:10Z", "hours": 13.0931, "text": "Adding typing feature I did a lot of memory management before this to get the keyboard to work in my kernel. I also optimized and organized my source code a little bit."}, {"post_id": 70995, "ts": "2026-09-20T05:39:23Z", "hours": 8.3692, "text": "Foundation of Kernel I finished the basic printing functions. E820 Memory Map I also loaded the E820 memory map into the kernel so the kernel knows which areas of memory are usable or reserved. Screenshot Information In the picture below, the first row of numbers is the base address . The second row of numbers is the memory length (base address - memory length = physical memory area). The third row of numbers indicates the memory type (usable or reserved). In addition, the memory information will differ depending on how much memory I allocated to QEMU. In conclusion, the usable memory is 8.59GB."}, {"post_id": 63390, "ts": "2026-09-07T06:04:58Z", "hours": 9.6458, "text": "My bootloader Is Finished!!! It loads into Protected Mode (32-bit) and Long Mode (64-bit), and then jumps to the kernel. My Next Goal My next goal is to work on my kernel. Can y’all give me some ideas about the kernel? What features should it have?"}, {"post_id": 45570, "ts": "2026-08-12T04:53:27Z", "hours": 9.4389, "text": "Protected Mode (32-bit) Enabled I got into protected mode in my stage 2 bootloader. 1. A20 Line First, I have to enable the A20 line to give the computer permission to access more than 1MB memory. 2. E820 Memory Map Next, I write a part of code that informs the computer of the safe physical memory access range (tells the computer about memory areas) 3. Global Descriptor Table (GDT) Before switching to protected mode, the kernel has to know what memory areas is for what. That is why we have GDT to inform the kernel. 4. CR0.PE = 1 Finally, I enable protected mode through the register CR0."}, {"post_id": 31066, "ts": "2026-07-19T04:57:36Z", "hours": 4.2417, "text": "Stage 1 Rebuild I rebuilt the Stage 1 bootloader in a new way. It successfully loaded into the Stage 2 bootloader, but I didn’t fully develop the Stage 2 bootloader. Disk.asm I made a new file named “disk.asm” to load data from the disk into memory. It will be used by both Stage 1 and 2 bootloaders."}, {"post_id": 20557, "ts": "2026-07-02T05:17:15Z", "hours": 0.4719, "text": "Finished Stage 1 Everything in Stage 1 is done. It only works for x86 machines that have a BIOS from 1998 or later because it supports the feature that my Stage 1 bootloader has (Int 0x13, AH=0x42). What’s Next? I will work on the Stage 2 bootloader and load the machine into Long Mode (64-bit). First of all is get the Real Mode setup."}, {"post_id": 18450, "ts": "2026-06-29T16:42:59Z", "hours": 0.8031, "text": "Final of Stage 1, Beginning of Stage 2 I just found out that there are some final tasks I have to do in Stage 1 before I can completely switch to Stage 2. What’s Wrong I need to make sure the BIOS supports the function to switch to Stage 2"}, {"post_id": 14881, "ts": "2026-06-24T04:57:26Z", "hours": 0.6, "text": "Bootloader Stage 2 (still in progress) After stage 1, I continue with stage 2, which will extend the memory limit, so the os can handle more complex tasks. What Happened? Surprisingly, I don’t know why it has an error. disk_address_packet: db 0x10 db 0 dw 1 dw 0x8000 dw 0x0000 dq 1 disk_error: mov si, disk_error_message call print_loop jmp hang ret “disk_address_packet” and “disk_error” labels are to allow you to understand my screenshots more easily."}, {"post_id": 14193, "ts": "2026-06-23T05:50:17Z", "hours": 0.9475, "text": "Stage 1 Bootloader I just realized that I have lost in my own project 😅. I didn’t know what I was doing or whether it was right. Today, I finally kinda make a Stage 1 bootloader"}, {"post_id": 13554, "ts": "2026-06-22T05:56:27Z", "hours": 0.4569, "text": "Switching to A New Virtual Machine I have switched to a new virtual machine, QEMU, because I can compile and run my Assembly file (.asm) more quickly. My file will output “ Loading into Protected Mode 32-bit ” once it runs.😅 😅 😅 I am still stuck in Real Mode and still can’t get to Protected mode."}, {"post_id": 11805, "ts": "2026-06-19T06:47:33Z", "hours": 0.7722, "text": "Trying to switch CPU mode in bootloader (Part 2) Today, I am still stuck with the process of how to switch from Real Mode (16-bit) to Protected Mode (32-bit), but I think a little bit outside the box. Not only focused on A20, but I also researched the other parts in Real and Protected Mode."}, {"post_id": 11136, "ts": "2026-06-18T06:43:00Z", "hours": 0.7986, "text": "Trying to switch CPU mode in bootloader I’m currently working on the bootloader to make it from Real Mode (16-bit) to Protected Mode (32-bit) I’m still stuck with the A20 gate. I need to learn more about Assembly syntax, so it will help me understand how my CPU actually works."}, {"post_id": 7908, "ts": "2026-06-13T06:01:20Z", "hours": 0.8483, "text": "Shortcut for building files I just made a shortcut today, so it will help me later in this project. PowerShell file I have added a PowerShell file to build a Binary file (.bin) and other files (.img, .vdi) from my main Assembly file (.asm). & \"C:\\Program Files\\NASM\\nasm.exe\" -f bin boot.asm -o boot.bin del disk.img -ErrorAction SilentlyContinue del disk.vdi -ErrorAction SilentlyContinue $disk= New-Object byte[] (1474560) [IO.File]::WriteAllBytes(\"disk.img\", $disk) $boot= [IO.File]::ReadAllBytes(\"boot.bin\") $disk= [IO.File]::ReadAllBytes(\"disk.img\") [Array]::Copy($boot, 0, $disk, 0, 512) [IO.File]::WriteAllBytes(\"disk.img\", $disk) & \"C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe\" convertfromraw disk.img disk.vdi --format VDI"}, {"post_id": 6620, "ts": "2026-06-11T03:18:59Z", "hours": 0.3044, "text": "I finally get my operating system on a virtual machine and make it output some words"}, {"post_id": 6600, "ts": "2026-06-11T02:28:18Z", "hours": 0.2869, "text": "I am researching assembly programming and how hardware and software work together."}]...
|
Title: Wheat Operating System (WheatOS) by @Ravduc Title: Wheat Operating System (WheatOS) by @Ravduct | Stardance
Devlogs:
I am researching assembly programming and how hardware and software work together.
I finally get my operating system on a virtual machine and make it output some words
Shortcut for building files I just made a shortcut today, so it will help me later in this project. PowerShell file I have added a PowerShell file to build a Binary file (.bin) and other files (.img, .vdi) from my main Assembly file (.asm). & "C:\Program Files\NASM\nasm.exe" -f bin boot.asm -o boot.bin del disk.img -ErrorAction SilentlyContinue del disk.vdi -ErrorAction SilentlyContinue $disk= New-Object byte[] (1474560) [IO.File]::WriteAllBytes("disk.img", $disk) $boot= [IO.File]::ReadAllBytes("boot.bin") $disk= [IO.File]::ReadAllBytes("disk.img") [Array]::Copy($boot, 0, $disk, 0, 512) [IO.File]::WriteAllBytes("disk.img", $disk) & "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" convertfromraw disk.img disk.vdi --format VDI
Trying to switch CPU mode in bootloader I’m currently working on the bootloader to make it from Real Mode (16-bit) to Protected Mode (32-bit) I’m still stuck with the A20 gate. I need to learn more about Assembly syntax, so it will help me understand how my CPU actually works.
Trying to switch CPU mode in bootloader (Part 2) Today, I am still stuck with the process of how to switch from Real Mode (16-bit) to Protected Mode (32-bit), but I think a little bit outside the box. Not only focused on A20, but I also researched the other parts in Real and Protected Mode.
Switching to A New Virtual Machine I have switched to a new virtual machine, QEMU, because I can compile and run my Assembly file (.asm) more quickly. My file will output “ Loading into Protected Mode 32-bit ” once it runs.😅 😅 😅 I am still stuck in Real Mode and still can’t get to Protected mode.
Stage 1 Bootloader I just realized that I have lost in my own project 😅. I didn’t know what I was doing or whether it was right. Today, I finally kinda make a Stage 1 bootloader
Bootloader Stage 2 (still in progress) After stage 1, I continue with stage 2, which will extend the memory limit, so the os can handle more complex tasks. What Happened? Surprisingly, I don’t know why it has an error. disk_address_packet: db 0x10 db 0 dw 1 dw 0x8000 dw 0x0000 dq 1 disk_error: mov si, disk_error_message call print_loop jmp hang ret “disk_address_packet” and “disk_error” labels are to allow you to understand my screenshots more easily.
Final of Stage 1, Beginning of Stage 2 I just found out that there are some final tasks I have to do in Stage 1 before I can completely switch to Stage 2. What’s Wrong I need to make sure the BIOS supports the function to switch to Stage 2
Finished Stage 1 Everything in Stage 1 is done. It only works for x86 machines that have a BIOS from 1998 or later because it supports the feature that my Stage 1 bootloader has (Int 0x13, AH=0x42). What’s Next? I will work on the Stage 2 bootloader and load the machine into Long Mode (64-bit). First of all is get the Real Mode setup.
Stage 1 Rebuild I rebuilt the Stage 1 bootloader in a new way. It successfully loaded into the Stage 2 bootloader, but I didn’t fully develop the Stage 2 bootloader. Disk.asm I made a new file named “disk.asm” to load data from the disk into memory. It will be used by both Stage 1 and 2 bootloaders.
Protected Mode (32-bit) Enabled I got into protected mode in my stage 2 bootloader. 1. A20 Line First, I have to enable the A20 line to give the computer permission to access more than 1MB memory. 2. E820 Memory Map Next, I write a part of code that informs the computer of the safe physical memory access range (tells the computer about memory areas) 3. Global Descriptor Table (GDT) Before switching to protected mode, the kernel has to know what memory areas is for what. That is why we have GDT to inform the kernel. 4. CR0.PE = 1 Finally, I enable protected mode through the register CR0.
My bootloader Is Finished!!! It loads into Protected Mode (32-bit) and Long Mode (64-bit), and then jumps to the kernel. My Next Goal My next goal is to work on my kernel. Can y’all give me some ideas about the kernel? What features should it have?
Foundation of Kernel I finished the basic printing functions. E820 Memory Map I also loaded the E820 memory map into the kernel so the kernel knows which areas of memory are usable or reserved. Screenshot Information In the picture below, the first row of numbers is the base address . The second row of numbers is the memory length (base address - memory length = physical memory area). The third row of numbers indicates the memory type (usable or reserved). In addition, the memory information will differ depending on how much memory I allocated to QEMU. In conclusion, the usable memory is 8.59GB.
Adding typing feature I did a lot of memory management before this to get the keyboard to work in my kernel. I also optimized and organized my source code a little bit.
Heap Allocation For Kernel I make heap allocations for the kernel (kmalloc and kfree). It will reserve a certain amount of memory for the kernel. I will do heap allocation for user later....
|
1792713180.2731435
|
1793317980.2731435
|
|
4212
|
Pc sim dashboard by @keledanko23 | Stardance
|
keledanko23
|
1
|
53.36
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-21T15:11:11Z", "hours": 5.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "It was hard to guess the numbers, but how i said there will be continuing about the real hardware", "repo": "https://github.com/keledanko23/Octavia-1-dashboard", "demo": ""}]...
|
[{"post_id": 57228, "ts": "202 [{"post_id": 57228, "ts": "2026-08-29T10:19:04Z", "hours": 5.6872, "text": "Finally finished the pcb, it´s ready for order, i will drop the files in the repo"}, {"post_id": 50866, "ts": "2026-08-20T10:06:18Z", "hours": 9.3222, "text": "Fixed the layout, changed some expensive IC-s to cheaper ones, almost finished"}, {"post_id": 47664, "ts": "2026-08-15T18:26:35Z", "hours": 9.3339, "text": "Added the components and conected most of the traces but I can´t make it cleaner, and i ran the DRC it said it has 250 errors and 110 alerts so i have a lot of work to do"}, {"post_id": 45674, "ts": "2026-08-12T09:58:53Z", "hours": 7.0847, "text": "Drawed the schematic, it was really hard because I did not find some IC-s and had to draw them myself, at first it had 56errors but i managed to fix it"}, {"post_id": 44558, "ts": "2026-08-10T12:13:50Z", "hours": 3.81, "text": "Finaly got a chance to use a scaner to scan the pcb, imported it into kicad ad fixed al the kholes location and the form of the pcb, the pcb form is now finished"}, {"post_id": 41488, "ts": "2026-08-05T18:46:23Z", "hours": 9.2803, "text": "Started building the pcb outlines and holes, unfortunatly lot of the holes arent on their places where they should be even if i mesure 10 times, at least the outline is finally the form i need and some of the holes ar on their places"}, {"post_id": 39986, "ts": "2026-08-03T10:31:36Z", "hours": 3.8394, "text": "Started mapping out the pcb so i can recreate it later, added 1more led to the prototype, tried to add 2more but they burned out"}, {"post_id": 13147, "ts": "2026-06-21T14:53:38Z", "hours": 4.7842, "text": "Finally completed the python code for the dashboard, you can find the file in my github repo"}, {"post_id": 2230, "ts": "2026-06-04T16:48:25Z", "hours": 0.3217, "text": "oda Octavia MK1 Dashboard Project 1. Hardware Progress Mapped out the Skoda Octavia MK1 cluster pinout (K.13+, K.15+, EPC, ABS, etc.) and designed the circuit for the VID29-05/JD62C854F stepper motor driver ICs. Soldered the prototype onto a perfboard, separating the 12V motor power from the 5V logic control. Secured the critical connections with hot glue for vibration resistance. 2. Software Development Built a PC simulator and control panel in Python using tkinter. The Challenge: After streamlining the code, the gauge needles lost their continuous movement and started snapping instantly to new values. The Fix: Solved this by implementing an asynchronous loop using window.after(16, animation_loop). It now updates at ~60 FPS, smoothly easing the current position toward the target value (moving 8% of the remaining distance per frame). Also fixed a quick syntax error in the UI dictionary styling."}]...
|
Title: Pc sim dashboard by @keledanko23 | Stardanc Title: Pc sim dashboard by @keledanko23 | Stardance
Devlogs:
oda Octavia MK1 Dashboard Project 1. Hardware Progress Mapped out the Skoda Octavia MK1 cluster pinout (K.13+, K.15+, EPC, ABS, etc.) and designed the circuit for the VID29-05/JD62C854F stepper motor driver ICs. Soldered the prototype onto a perfboard, separating the 12V motor power from the 5V logic control. Secured the critical connections with hot glue for vibration resistance. 2. Software Development Built a PC simulator and control panel in Python using tkinter. The Challenge: After streamlining the code, the gauge needles lost their continuous movement and started snapping instantly to new values. The Fix: Solved this by implementing an asynchronous loop using window.after(16, animation_loop). It now updates at ~60 FPS, smoothly easing the current position toward the target value (moving 8% of the remaining distance per frame). Also fixed a quick syntax error in the UI dictionary styling.
Finally completed the python code for the dashboard, you can find the file in my github repo
Started mapping out the pcb so i can recreate it later, added 1more led to the prototype, tried to add 2more but they burned out
Started building the pcb outlines and holes, unfortunatly lot of the holes arent on their places where they should be even if i mesure 10 times, at least the outline is finally the form i need and some of the holes ar on their places
Finaly got a chance to use a scaner to scan the pcb, imported it into kicad ad fixed al the kholes location and the form of the pcb, the pcb form is now finished
Drawed the schematic, it was really hard because I did not find some IC-s and had to draw them myself, at first it had 56errors but i managed to fix it
Added the components and conected most of the traces but I can´t make it cleaner, and i ran the DRC it said it has 250 errors and 110 alerts so i have a lot of work to do
Fixed the layout, changed some expensive IC-s to cheaper ones, almost finished
Finally finished the pcb, it´s ready for order, i will drop the files in the repo
Ships:
It was hard to guess the numbers, but how i said there will be continuing about the real hardware...
|
1793105322.550437
|
1793191722.550437
|
|
4213
|
My first slack bot! by @phu | Stardance
|
phu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @phu | Stardance
|
1792630313.55766
|
1793235113.55766
|
|
4214
|
My first slack bot! by @WilliamTreu | Stardance
|
WilliamTreu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @WilliamTreu | Stard Title: My first slack bot! by @WilliamTreu | Stardance...
|
1792493682.2649734
|
1793098482.2649734
|
|
4215
|
My awesome macropad! by @DonaldBaker | Stardance
|
DonaldBaker
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @DonaldBaker | Star Title: My awesome macropad! by @DonaldBaker | Stardance...
|
1792777776.8525805
|
1793382576.8525805
|
|
4216
|
MyMusicLibrary by @axeld | Stardance
|
axeld
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: MyMusicLibrary by @axeld | Stardance
|
1792705775.512238
|
1793310575.512238
|
|
4217
|
Canteen App by @Sayeeda | Stardance
|
Sayeeda
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Canteen App by @Sayeeda | Stardance
|
1792504090.076811
|
1793108890.076811
|
|
4218
|
ESP32 Game by @Vincent | Stardance
|
Vincent
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ESP32 Game by @Vincent | Stardance
|
1792795797.3839557
|
1793400597.3839557
|
|
4219
|
Remotely Operated Mining Vehicle by @Ch_Raghav | S Remotely Operated Mining Vehicle by @Ch_Raghav | Stardance...
|
Ch_Raghav
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Remotely Operated Mining Vehicle by @Ch_Rag Title: Remotely Operated Mining Vehicle by @Ch_Raghav | Stardance...
|
1792741765.8022718
|
1793346565.8022718
|
|
4220
|
My first slack bot! by @abhijay_potluri | Stardanc My first slack bot! by @abhijay_potluri | Stardance...
|
abhijay_potluri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @abhijay_potluri | S Title: My first slack bot! by @abhijay_potluri | Stardance...
|
1792803269.2724385
|
1793408069.2724385
|
|
4221
|
Hollow knife by @baluwaladaniyal | Stardance
|
baluwaladaniyal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hollow knife by @baluwaladaniyal | Stardanc Title: Hollow knife by @baluwaladaniyal | Stardance...
|
1792929007.6371098
|
1793793007.6371098
|
|
4222
|
Untitled project by @mishaagarwal06 | Stardance
|
mishaagarwal06
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @mishaagarwal06 | Stard Title: Untitled project by @mishaagarwal06 | Stardance...
|
1792900144.1817632
|
1793764144.1817632
|
|
4223
|
Untitled project by @adviksanghi | Stardance
|
adviksanghi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @adviksanghi | Stardanc Title: Untitled project by @adviksanghi | Stardance...
|
1792785172.6429362
|
1793389972.6429362
|
|
4224
|
My awesome macropad! by @bartoszkasyna | Stardance
|
bartoszkasyna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @bartoszkasyna | St Title: My awesome macropad! by @bartoszkasyna | Stardance...
|
1792950462.0945635
|
1793814462.0945635
|
|
4225
|
PuzzleLock by @Alexlikescoolthings | Stardance
|
Alexlikescoolthings
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: PuzzleLock by @Alexlikescoolthings | Starda Title: PuzzleLock by @Alexlikescoolthings | Stardance...
|
1792788877.6838553
|
1793393677.6838553
|
|
4226
|
Untitled by @kanishkv99 | Stardance
|
kanishkv99
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @kanishkv99 | Stardance
|
1792518895.0253992
|
1793123695.0253992
|
|
4227
|
Untitled by @WilliamTreu | Stardance
|
WilliamTreu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @WilliamTreu | Stardance
|
1792713087.3222988
|
1793317887.3222988
|
|
4228
|
My awesome macropad! by @Rishov_YT | Stardance
|
Rishov_YT
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Rishov_YT | Starda Title: My awesome macropad! by @Rishov_YT | Stardance...
|
1792511350.844924
|
1793116150.844924
|
|
4229
|
RC plane by @max_wang | Stardance
|
max_wang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: RC plane by @max_wang | Stardance
|
1792565458.6663427
|
1793170258.6663427
|
|
4230
|
Mac Pad with OLED :)) by @Alexlikescoolthings | St Mac Pad with OLED :)) by @Alexlikescoolthings | Stardance...
|
Alexlikescoolthings
|
0
|
3.63
|
0
|
[]
|
[{"post_id": 43097, "ts": "202 [{"post_id": 43097, "ts": "2026-08-08T05:41:27Z", "hours": 1.4572, "text": "I took out the OlED :( I liked it and I had a cool idea for it but I wanted to learn on shape first and making the extra hole for the OLED added some complications but hopefully there will be a V2! BUT THEN TRAGITY STRUCK…my computer died and I my onshape file got messed up :( here is my current situation: (I was almost done too :(("}, {"post_id": 18047, "ts": "2026-06-29T00:42:17Z", "hours": 1.6033, "text": "I have done almost all of the PCB routing anf noe i just need to finish the CAD. I have also run into a problem with Lapse/hacktime…Hacktime has not been recconizing the lapse reccording time soooo idk how to fix that but I will"}, {"post_id": 9496, "ts": "2026-06-15T20:59:41Z", "hours": 0.5703, "text": "Made the scamatic/PCB design and now Onshape :) It took me 3 youtube videos to get these 2 to the right dementions :P. I need to figure out how to move them now….hummm after dinner"}]...
|
Title: Mac Pad with OLED :)) by @Alexlikescoolthin Title: Mac Pad with OLED :)) by @Alexlikescoolthings | Stardance
Devlogs:
Made the scamatic/PCB design and now Onshape :) It took me 3 youtube videos to get these 2 to the right dementions :P. I need to figure out how to move them now….hummm after dinner
I have done almost all of the PCB routing anf noe i just need to finish the CAD. I have also run into a problem with Lapse/hacktime…Hacktime has not been recconizing the lapse reccording time soooo idk how to fix that but I will
I took out the OlED :( I liked it and I had a cool idea for it but I wanted to learn on shape first and making the extra hole for the OLED added some complications but hopefully there will be a V2! BUT THEN TRAGITY STRUCK…my computer died and I my onshape file got messed up :( here is my current situation: (I was almost done too :((...
|
1792518544.6929054
|
1793123344.6929054
|
|
4231
|
My first slack bot! by @warrenyi | Stardance
|
warrenyi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @warrenyi | Stardanc Title: My first slack bot! by @warrenyi | Stardance...
|
1792788887.2113118
|
1793393687.2113118
|
|
4232
|
My first slack bot! by @humaira | Stardance
|
humaira
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @humaira | Stardance
|
1792608570.2360501
|
1793213370.2360501
|
|
4233
|
Untitled project by @alicee | Stardance
|
alicee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @alicee | Stardance
|
1792680605.4327023
|
1793285405.4327023
|
|
4234
|
Project Phantom by @Rithish | Stardance
|
Rithish
|
0
|
33.06
|
0
|
[]
|
[{"post_id": 47611, "ts": "202 [{"post_id": 47611, "ts": "2026-08-15T16:52:57Z", "hours": 0.5003, "text": "Dev Log #40 hardware testing started today with sensors borrowed from my tutor. soldered header pins on the modules. tested 4 sensors in total and 3 of them worked: scd41 co2, vl53l0x tof, and bme680 all gave clean readings. the icm-20948 imu failed with an i2c begin error, not sure if its an address issue or if i broke it while soldering. calling it for tonight cause its late, will run an i2c scanner tmmm to check if the icm is alive."}, {"post_id": 47001, "ts": "2026-08-14T15:57:59Z", "hours": 0.4964, "text": "Dev Log #38 finallyy geting to the hardware partt had a few sensors without pins soo kinda soldered headers on them and also burnt my fingers….(first time lol)"}, {"post_id": 46365, "ts": "2026-08-13T15:16:27Z", "hours": 0.5, "text": "Dev Log #38 more changes on the website and alsoo made a personal website for me"}, {"post_id": 45811, "ts": "2026-08-12T15:15:07Z", "hours": 0.9167, "text": "Dev log #37 more changes to the website…this is getting boring"}, {"post_id": 45279, "ts": "2026-08-11T17:09:26Z", "hours": 0.4336, "text": "Dev Log #36 had a extra get in touch button soo fixed it and alsoo a bit of checking on lighthouse if our website is actually good ngll"}, {"post_id": 44456, "ts": "2026-08-10T06:42:03Z", "hours": 0.5669, "text": "Dev log #35 not much just editing bugs on the websitee"}, {"post_id": 43801, "ts": "2026-08-09T07:19:13Z", "hours": 0.9839, "text": "Dev Log #34 Made a applicant form for joining phantom tdyyy and also made a new page for terms hoping to see new members"}, {"post_id": 43133, "ts": "2026-08-08T07:14:52Z", "hours": 1.9783, "text": "Dev log #33 I promise this will be the final time i will be spending hours on the same website..i added more animations and interactive features added pervious members list and also our first flight vid have a look…until next time byeee"}, {"post_id": 42515, "ts": "2026-08-07T09:51:57Z", "hours": 4.0672, "text": "Dev log #32 spent 4 hours straight building out the AI side of the site and it was basically just me vs. a wall of bugs , the website kept glitching, logic broke everywhere, and then the deployment refused to cooperate for way too long. but after a lot of console staring and one very questionable fix, projectphantom.space is finally live. go take a look and if anything feels off, drop a suggestion below."}, {"post_id": 41932, "ts": "2026-08-06T13:38:24Z", "hours": 1.6503, "text": "Dev Log #31 soo yeahhh spent a lot of time building the ai part of the websitee and yeah it kept glichting out a ton of times and then it wont deploy, most of the time was spent on trying to deploy the site…i hope it looks cool"}, {"post_id": 41812, "ts": "2026-08-06T08:12:05Z", "hours": 0.9672, "text": "Dev Log #30 Took some resttt, needed it fr. Real talk tho…. when I first made this Stardance account I was on vacation, like fully hardware-less, so everything you guys have seen so far has just been the soft side, website stuff, socials, online grind. That’s about to flip. I’m finally back and about to start unpacking the actual hardware, the stuff I genuinely missed sooo much 🔧 give it about a week and you’ll start seeing real hardware content again, not just screens and code. Also… picked something up 👀 not saying what yet but it’s my favorite microcontroller, more on that in the next dev log. And once the website’s fully wrapped up, it’s hardware timeee. For real this time. Yippee 🚀✈️"}, {"post_id": 41435, "ts": "2026-08-05T17:24:25Z", "hours": 0.4133, "text": "Dev log #29 dove back into the hardware side today…..researching Matek flight controllers, fine-tuning the UAV build, and experimenting with Depron wing construction techniques for maximum structural rigidity and low weight ✈️ Decided to postpone the deep history and lore to the one of the upcoming dev log"}, {"post_id": 41427, "ts": "2026-08-05T16:54:55Z", "hours": 0.7336, "text": "Dev Log #28: Fixed the cursor styling, cleaned up the image placement, and finally aligned the navigation icon properly…..Officially requested indexing on Google Search Console andddd our site is officially queued up and ready to take over search results. I am finally back!!!!!! one of our upcoming dev log is going to be packed with full of lore and the deep history of this entire project from start to finish. Until then, I’m signing off……just landed after a 5-hour flight and I am hecka tired 😴✌️"}, {"post_id": 40589, "ts": "2026-08-04T07:30:45Z", "hours": 1.2225, "text": "Dev log #27 Finally got the official site submitted and verified! Claimed ownership on Search Console and got it officially queued up for Google indexing so our actual platform takes over search results. Also spent way too much time wrestling with the dynamic light/dark mode SVG favicon, the code is all set, but the scaling/viewBox is still slightly bugging out and cutting off the edges 💀but i need rest….."}, {"post_id": 40051, "ts": "2026-08-03T12:30:00Z", "hours": 0.3667, "text": "Dev Log #26 finally got a domainnnnnn lets goooo updating evrything and connected just added tehh assets foldr and filled in the place holders finally got a faceee"}, {"post_id": 39853, "ts": "2026-08-03T03:38:05Z", "hours": 0.4, "text": "Dev Log #25 fixed a bunch of website bugs today lol, the depth scroll text was showing a black screen bc the section height was wrong, also broke the whole nav animation with a null error, and the logo was way too smol so i made it bigger. small fixes but it looks way more professional now"}, {"post_id": 39615, "ts": "2026-08-02T18:29:47Z", "hours": 0.6167, "text": "Dev Log #24 Added the backed by section and then added the meet the team section just a a quick update"}, {"post_id": 38691, "ts": "2026-08-01T06:29:59Z", "hours": 0.7836, "text": "Dev Log#23: Just adding some animations and rewriting a few stuff so its professional."}, {"post_id": 38255, "ts": "2026-07-31T15:37:21Z", "hours": 0.3836, "text": "Dev log #22 did some changes to the website a lot more to go…will drop the link soon"}, {"post_id": 37584, "ts": "2026-07-30T12:41:41Z", "hours": 0.4836, "text": "Dev log #21 Got bored and started to overthink and realized I need a face for the project so why no make a website for project phantom and started to work on it for literally 20 mins and boom power cut here 😭👍 will continue as soon as it comes…."}, {"post_id": 37501, "ts": "2026-07-30T09:13:25Z", "hours": 0.3336, "text": "Dev Log #20 Just light work after doing and completing the schematics I wanted a bit of a break so I went ahead and decided to learn to cad….Did a bit of a search on that and download freecad time to learn that also….yeah, No break"}, {"post_id": 36955, "ts": "2026-07-29T11:30:03Z", "hours": 0.7, "text": "Dev Log #19 schematic finally locked and pushed to github. wiring, pinouts, diagram all there. looks like an actual thing now not just spaghetti everywhere. next is the real stuff. gotta code the teensy, build pid loops from scratch, and learn pcb design because breadboards are not it. need to turn this into something i can actually solder and fly. also sent out funding requests. just waiting and hoping something hits so i can stop simulating and actually get this in the air. 14 minutes once before. need way more than that. code next. then cad. then maybe the sky. we ll see."}, {"post_id": 36270, "ts": "2026-07-28T08:22:32Z", "hours": 1.7333, "text": "Dev Log #18 Circuit schematic is DONE. Well… mostly. After hours of wrestling with KiCad, net labels, wire spaghetti, and questioning my entire existence, I finally have ICM-20948, BME680, SCD40, VL53L0X, NRF24L01, M10-5883, MQ135, PMS5003, R12F receiver, all four servos, UBEC, and the Teensy 4.1 all placed and wired. Is it neat? Meh. Is it functional? Absolutely. The ESC and motor are still missing because honestly I got confused about whether the PWM wire powers the motor or if the battery does or if magic is involved. I’ll figure it out later. For now, Project Phantom’s brain is mapped out and I’m counting this as a win. Could be better, but could also be a lot worse."}, {"post_id": 35717, "ts": "2026-07-27T10:12:52Z", "hours": 0.9836, "text": "Dev Log #17 Just spent hours in KiCad and my schematic looks like a bowl of wire spaghetti. Wires crossing everywhere, labels floating around lost, and I just realized I’ve been drawing physical wires across the whole page when net labels exist. My brain is fried, my eyes hurt, and I’m pretty sure I connected GND to something that definitely isn’t ground. But you know what? I’m not starting over. I’m gonna fix this mess piece by piece……power symbols, clean labels, proper layout. Project Phantom didn’t come this far to quit on some green lines."}, {"post_id": 35667, "ts": "2026-07-27T08:24:45Z", "hours": 1.1503, "text": "Dev Log #16 KiCad is absolutely HECTIC bro. Spent the last few hours trying to wire up the ICM-20948 and BME680, net labels everywhere, I2C bus sharing, pull-ups, pull-downs, 3.3V this, 5V that… my brain is fried. I legit got a headache staring at green wires that refuse to connect to pins properly. Learned a ton though net labels and they are my new best friend, G (drag) »> M (move), and I2C is just one wire pretending to be many. Gonna take a break, touch some grass, then I’m locking back in and finishing this schematic. Project Phantom waits for no one… but my sanity does…."}, {"post_id": 35286, "ts": "2026-07-26T16:23:52Z", "hours": 1.2006, "text": "Dev Log #15 Telemetry board schematic is live. IMU, GNSS, air quality sensors, NRF24, RC receiver, all socketed and labeled. Looks like a proper flight computer on paper. In reality? Currently praying my I2C bus doesn’t explode from address conflicts and that I remembered which pin is 3.3V vs 5V before something starts smoking. Voltage divider for the MQ135 pending because apparently “close enough” isn’t how electronics work. Wiring starts tomorrow… or maybe I just rotate more labels and call it progress."}, {"post_id": 34388, "ts": "2026-07-25T02:18:49Z", "hours": 0.2836, "text": "Dev log #14 Research on BME680 and how it works and also MQ-135. Needed to know the basics before we take a big leap"}, {"post_id": 34095, "ts": "2026-07-24T15:58:57Z", "hours": 0.4333, "text": "Dev Log #13 Locked in the full pinout and header architecture for the Teensy 4.1 in KiCad today ,both 24-pin side headers are officially set up and ready to go. Decided against running a separate co-processor setup for now to keep the hardware stack streamlined and fast, letting the Teensy handle the whole flight and telemetry system directly. Shifted straight into the sensor array starting with the MPU6050 IMU. Instead of messing around with raw IC footprint files and internal silicon pins, mapped it cleanly using an 8-pin connector layout with proper I2C and interrupt net labels. Next step: wrapping up the rest of the sensor payload connections!"}, {"post_id": 33302, "ts": "2026-07-23T02:52:58Z", "hours": 0.5503, "text": "Dev Log #12 Focused on manually mapping out the Teensy 4.1 schematic headers and pinouts in KiCad today. It turned out to be way more time-consuming than expected ,especially sorting out the physical layout versus the pin numbering jumps. I definitely could have just downloaded a pre-made symbol from GitHub or online repositories, but doing it from scratch was worth the hassle to actually get hands-on and learn KiCad properly. Headers are locked in, wrapping up for today!"}, {"post_id": 33057, "ts": "2026-07-22T17:05:53Z", "hours": 0.5333, "text": "Dev Log #11 Digital infrastructure is officially sorted. Secured our X, YouTube, LinkedIn, and GitHub, and got the web landing page completely lined up. On paper, our brand ecosystem is fully live. In reality? Currently staring at a blank feed waiting for the algorithms to pick us up like it’s a high-stakes exam result. Engagement’s sitting at a solid zero…hope for the best"}, {"post_id": 32371, "ts": "2026-07-21T14:36:05Z", "hours": 0.4667, "text": "Dev Log #10: Still caught in the research spiral over whether to snag an Ender 3 V3 or a Bambu Lab A1. The Ender’s cheaper and tempting, but the A1’s auto flow calibration would save us so much pain when printing delicate LW-PLA wing profiles. Not that it matters right now—the debate is basically on pause while we sit around waiting for the wallet to stop reading $0."}, {"post_id": 31818, "ts": "2026-07-20T14:36:57Z", "hours": 0.9003, "text": "Dev Log #9: Hardware selection is officially locked in. After hunting down an absolute steal on an M10 GPS + compass module, settling on the Teensy 4.1, and getting the full FPV gear lined up, the core tech stack for this telemetry build is completely sorted on paper. In reality? I am currently staring at a checkout screen waiting on funding approval like it’s a high-stakes exam result. Wallet’s sitting at a solid zero balance right now……"}, {"post_id": 31265, "ts": "2026-07-19T15:15:05Z", "hours": 0.3669, "text": "Dev Log #8: While waiting for my components to ship, I spent today working out a cleaner way to handle the propulsion physics for horizontal cruise flight. By planning for a variable-pitch mechanism, the flight software can actively feather the unpowered blades to zero degrees so they align perfectly with the oncoming air currents. This cuts out the usual aerodynamic drag penalties completely, letting the platform cruise efficiently on a single motor like a standard plane while keeping the dual setup ready for vertical lift. Now, I’m jumping right back into KiCad to map out the extra control lines on the board!"}, {"post_id": 30540, "ts": "2026-07-18T06:21:25Z", "hours": 1.4672, "text": "Dev Log #7: With the master schematic layout finally taking shape, I took a massive step back to clean up and finalize our official BOM.md list for the GitHub repository. I stripped out all the fluctuating market price rates to keep the sheet clean and added a dedicated procurement summary tracking our immediate core prototyping items (the Pi 5, primary navigation modules, custom PCB fabrication, and the analog FPV kit). Now, we play the ultimate waiting game for procurement clearance before we can actually order the physical hardware components. Since we’re in limbo waiting on the parts, I’m currently working on the custom KiCad board layout design again after taking a much-needed short break lol. Time to shake off the confusion, map out the actual trace routing, and get these dual-row tracks perfect!"}, {"post_id": 30509, "ts": "2026-07-18T04:26:08Z", "hours": 0.5336, "text": "Devlog #6: This is my official first time using KiCad, and honestly, it’s a blast ,yet wildly confusing all at once. The fun part is definitely designing Project Phantom’s brain from scratch, mapping out how the Teensy 4.1 will route high-speed data to the ESP32 and command the long-range nRF24L01+ PA/LNA data link. The confusing part? KiCad’s quirks! Getting hit with random template errors, figuring out shortcuts, and learning how to mirror generic socket headers (Conn_01x24) with the X key just to keep connection points facing outwards has been a massive learning curve. But the parallel dual-row tracks for the Teensy are officially down, and the master schematic layout is finally coming to life!"}, {"post_id": 30038, "ts": "2026-07-17T09:24:33Z", "hours": 0.2836, "text": "Dev Log #5: The Backstory & How We Got HereIf you look at the timer on this project, it says 3 hours. Let’s be real ,I’ve been living and breathing this build way before I started tracking it on Stardance. The hardware sitting on my bench right now represents months of legacy testing, crashed foam, and troubleshooting. We started out testing baseline concepts on an Apprentice S15e trainer and an AtomRC Dolphin frame, proving out basic telemetry strings, tuning stock flight controllers, and making sure our environmental sensor array (BME680 and PMS5003) actually tracked data mid-air. Now, we are completely outgrowing the kit phase. The goal from here on out is 100% engineering sovereignty. We are moving away from pre-bought foam and stock autopilot systems to build a completely custom, scratch-printed LW-PLA airframe with carbon fiber structural spars. On the software side, I’m writing the custom flight firmware from absolute zero and tuning my own PID stabilization loops on a Teensy 4.1. We just finished mapping out the full market-rate upgraded BOM, integrated our flight validation video from LinkedIn into the main README, and locked down the co-processing vision stack specs (Raspberry Pi 5 + depth camera + global shutter industrial camera). The foundation is built. Time to torture myself with a million compiler errors and endless troubleshooting to make this scratch build fly. Let’s get to work."}, {"post_id": 30002, "ts": "2026-07-17T07:25:55Z", "hours": 1.3008, "text": "Just spent the last hour fixing up the docs and locking in the Stardance dashboard. The LinkedIn flight video is finally embedded right in the README so people can see the validation plane actually flying in the air with one click. I also made a clean BOM file from scratch to separate the gear on my bench from the upgrades I need to buy. I did some actual price digging on Alibaba and AliExpress to make the budget realistic, factoring in the true market cost of the Raspberry Pi 5, about 500 AED for the FPV kit, and adding a depth camera plus a global shutter industrial camera for the vision stack. The whole point here is complete engineering sovereignty. People think it is just a pre-bought foam kit, but I am doing it all from absolute zero with custom flight software, my own tuned PID loops, and a 100% scratch-printed LW-PLA airframe. Time to torture myself with a million compiler errors and endless troubleshooting, but honestly it is going to be incredibly fun."}, {"post_id": 29334, "ts": "2026-07-16T06:40:48Z", "hours": 0.5633, "text": "Product Research again…"}, {"post_id": 28124, "ts": "2026-07-14T06:38:37Z", "hours": 0.4333, "text": "Finding out ways to patent the custom aircraft design soo it belong to me lol ntg much"}, {"post_id": 28118, "ts": "2026-07-14T05:55:11Z", "hours": 0.3739, "text": "just mapping out the master BOM and looking up part specs. Sourcing everything for the flight controller stack and the environmental sensors so I know exactly what components I need to order next…..my wallets gone"}]...
|
Title: Project Phantom by @Rithish | Stardance
De Title: Project Phantom by @Rithish | Stardance
Devlogs:
just mapping out the master BOM and looking up part specs. Sourcing everything for the flight controller stack and the environmental sensors so I know exactly what components I need to order next…..my wallets gone
Finding out ways to patent the custom aircraft design soo it belong to me lol ntg much
Product Research again…
Just spent the last hour fixing up the docs and locking in the Stardance dashboard. The LinkedIn flight video is finally embedded right in the README so people can see the validation plane actually flying in the air with one click. I also made a clean BOM file from scratch to separate the gear on my bench from the upgrades I need to buy. I did some actual price digging on Alibaba and AliExpress to make the budget realistic, factoring in the true market cost of the Raspberry Pi 5, about 500 AED for the FPV kit, and adding a depth camera plus a global shutter industrial camera for the vision stack. The whole point here is complete engineering sovereignty. People think it is just a pre-bought foam kit, but I am doing it all from absolute zero with custom flight software, my own tuned PID loops, and a 100% scratch-printed LW-PLA airframe. Time to torture myself with a million compiler errors and endless troubleshooting, but honestly it is going to be incredibly fun.
Dev Log #5: The Backstory & How We Got HereIf you look at the timer on this project, it says 3 hours. Let’s be real ,I’ve been living and breathing this build way before I started tracking it on Stardance. The hardware sitting on my bench right now represents months of legacy testing, crashed foam, and troubleshooting. We started out testing baseline concepts on an Apprentice S15e trainer and an AtomRC Dolphin frame, proving out basic telemetry strings, tuning stock flight controllers, and making sure our environmental sensor array (BME680 and PMS5003) actually tracked data mid-air. Now, we are completely outgrowing the kit phase. The goal from here on out is 100% engineering sovereignty. We are moving away from pre-bought foam and stock autopilot systems to build a completely custom, scratch-printed LW-PLA airframe with carbon fiber structural spars. On the software side, I’m writing the custom flight firmware from absolute zero and tuning my own PID stabilization loops on a Teensy 4.1. We just finished mapping out the full market-rate upgraded BOM, integrated our flight validation video from LinkedIn into the main README, and locked down the co-processing vision stack specs (Raspberry Pi 5 + depth camera + global shutter industrial camera). The foundation is built. Time to torture myself with a million compiler errors and endless troubleshooting to make this scratch build fly. Let’s get to work.
Devlog #6: This is my official first time using KiCad, and honestly, it’s a blast ,yet wildly confusing all at once. The fun part is definitely designing Project Phantom’s brain from scratch, mapping out how the Teensy 4.1 will route high-speed data to the ESP32 and command the long-range nRF24L01+ PA/LNA data link. The confusing part? KiCad’s quirks! Getting hit with random template errors, figuring out shortcuts, and learning how to mirror generic socket headers (Conn_01x24) with the X key just to keep connection points facing outwards has been a massive learning curve. But the parallel dual-row tracks for the Teensy are officially down, and the master schematic layout is finally coming to life!
Dev Log #7: With the master schematic layout finally taking shape, I took a massive step back to clean up and finalize our official BOM.md list for the GitHub repository. I stripped out all the fluctuating market price rates to keep the sheet clean and added a dedicated procurement summary tracking our immediate core prototyping items (the Pi 5, primary navigation modules, custom PCB fabrication, and the analog FPV kit). Now, we play the ultimate waiting game for procurement clearance before we can actually order the physical hardware components. Since we’re in limbo waiting on the parts, I’m currently working on the custom KiCad board layout design again after taking a much-needed short break lol. Time to shake off the confusion, map out the actual trace routing, and get these dual-row tracks perfect!
Dev Log #8: While waiting for my components to ship, I spent today working out a cleaner way to handle the propulsion physics for horizontal cruise flight. By planning for a variable-pitch mechanism, the flight software can actively feather the unpowered blades to zero degrees so they align perfectly with the oncoming air currents. This cuts out the usual aerodynamic drag penalties completely, letting the platform cruise efficiently on a single motor like a standard plane while keeping the dual setup ready for vertical lift. Now, I’m jumping right back into KiCad to map out the extra control lines on the board!
Dev Log #9: Hardware selection is officially locked in. After hunting down an absolute steal on an M10 GPS + compass module, settling on the Teensy 4.1, and getting the full FPV gear lined up, the core tech stack for this telemetry build is completely sorted on paper. In reality? I am currently staring at a checkout screen waiting on funding approval like it’s a high-stakes exam result. Wallet’s sitting at a solid zero balance right now……
Dev Log #10: Still caught in the research spiral over whether to snag an Ender 3 V3 or a Bambu Lab A1. The Ender’s cheaper and tempting, but the A1’s auto flow calibration would save us so much pain when printing delicate LW-PLA wing profiles. Not that it matters right now—the debate is basically on pause while we sit around waiting for the wallet to stop reading $0.
Dev Log #11 Digital infrastructure is officially sorted. Secured our X, YouTube, LinkedIn, and GitHub, and got the web landing page completely lined up. On paper, our brand ecosystem is fully live. In reality? Currently staring at a blank feed waiting for the algorithms to pick us up like it’s a high-stakes exam result. Engagement’s sitting at a solid zero…hope for the best
Dev Log #12 Focused on manually mapping out the Teensy 4.1 schematic headers and pinouts in KiCad today. It turned out to be way more time-consuming than expected ,especially sorting out the physical layout versus the pin numbering jumps. I definitely could have just downloaded a pre-made symbol from GitHub or online repositories, but doing it from scratch was worth the hassle to actually get hands-on and learn KiCad properly. Headers are locked in, wrapping up for today!
Dev Log #13 Locked in the full pinout and header architecture for the Teensy 4.1 in KiCad today ,both 24-pin side headers are officially set up and ready to go. Decided against running a separate co-processor setup for now to keep the hardware stack streamlined and fast, letting the Teensy handle the whole flight and telemetry system directly. Shifted straight into the sensor array starting with the MPU6050 IMU. Instead of messing around with raw IC footprint files and internal silicon pins, mapped it cleanly using an 8-pin connector layout with proper I2C and interrupt net labels. Next step: wrapping up the rest of the sensor payload connections!
Dev log #14 Research on BME680 and how it works and also MQ-135. Needed to know the basics before we take a big leap
Dev Log #15 Telemetry board schematic is live. IMU, GNSS, air quality sensors, NRF24, RC receiver, all socketed and labeled. Looks like a proper flight computer on paper. In reality? Currently praying my I2C bus doesn’t explode from address conflicts and that I remembered which pin is 3.3V vs 5V before something starts smoking. Voltage divider for the MQ135 pending because apparently “close enough” isn’t how electronics work. Wiring starts tomorrow… or maybe I just rotate more labels and call it progress.
Dev Log #16 KiCad is absolutely HECTIC bro. Spent the last few hours trying to wire up the ICM-20948 and BME680, net labels everywhere, I2C bus sharing, pull-ups, pull-downs, 3.3V this, 5V that… my brain is fried. I legit got a headache staring at green wires that refuse to connect to pins properly. Learned a ton though net labels and they are my new best friend, G (drag) »> M (move), and I2C is just one wire pretending to be many. Gonna take a break, touch some grass, then I’m locking back in and finishing this schematic. Project Phantom waits for no one… but my sanity does….
Dev Log #17 Just spent hours in KiCad and my schematic looks like a bowl of wire spaghetti. Wires crossing everywhere, labels floating around lost, and I just realized I’ve been drawing physical wires across the whole page when net labels exist. My brain is fried, my eyes hurt, and I’m pretty sure I connected GND to something that definitely isn’t ground. But you know what? I’m not starting over. I’m gonna fix this mess piece by piece……power symbols, clean labels, proper layout. Project Phantom didn’t come this far to quit on some green lines.
Dev Log #18 Circuit schematic is DONE. Well… mostly. After hours of wrestling with KiCad, net labels, wire spaghetti, and questioning my entire existence, I finally have ICM-20948, BME680, SCD40, VL53L0X, NRF24L01, M10-5883, MQ135, PMS5003, R12F receiver, all four servos, UBEC, and the Teensy 4.1 all placed and wired. Is it neat? Meh. Is it functional? Absolutely. The ESC and motor are still missing because honestly I got confused about whether the PWM wire powers the motor or if the battery does or if magic is involved. I’ll figure it out later. For now, Project Phantom’s brain is mapped out and I’m counting this as a win. Could be better, but could also be a lot worse.
Dev Log #19 schematic finally locked and pushed to github. wiring, pinouts, diagram all there. looks like an actual thing now not just spaghetti everywhere. next is the real stuff. gotta code the teensy, build pid loops from scratch, and learn pcb design because breadboards are not it. need to turn this into something i can actually solder and fly. also sent out funding requests. just waiting and hoping something hits so i can stop simulating and actually get this in the air. 14 minutes once before. need way more than that. code next. then cad. then maybe the sky. we ll see.
Dev Log #20 Just light work after doing and completing the schematics I wanted a bit of a break so I went ahead and decided to learn to cad….Did a bit of a search on that and download freecad time to learn that also….yeah, No break
Dev log #21 Got bored and started to overthink and realized I need a face for the project so why no make a website for project phantom and started to work on it for literally 20 mins and boom power cut here 😭👍 will continue as soon as it comes….
Dev log #22 did some changes to the website a lot more to go…will drop the link soon
Dev Log#23: Just adding some animations and rewriting a few stuff so its professional.
Dev Log #24 Added the backed by section and then added the meet the team section just a a quick update
Dev Log #25 fixed a bunch of website bugs today lol, the depth scroll text was showing a black screen bc the section height was wrong, also broke the whole nav animation with a null error, and the logo was way too smol so i made it bigger. small fixes but it looks way more professional now
Dev Log #26 finally got a domainnnnnn lets goooo updating evrything and connected just added tehh assets foldr and filled in the place holders finally got a faceee
Dev log #27 Finally got the official site submitted and verified! Claimed ownership on Search Console and got it officially queued up for Google indexing so our actual platform takes over search results. Also spent way too much time wrestling with the dynamic light/dark mode SVG favicon, the code is all set, but the scaling/viewBox is still slightly bugging out and cutting off the edges 💀but i need rest…..
Dev Log #28: Fixed the cursor styling, cleaned up the image placement, and finally aligned the navigation icon properly…..Officially requested indexing on Google Search Console andddd our site is officially queued up and ready to take over search results. I am finally back!!!!!! one of our upcoming dev log is going to be packed with full of lore and the deep history of this entire project from start to finish. Until then, I’m signing off……just landed after a 5-hour flight and I am hecka tired 😴✌️
Dev log #29 dove back into the hardware side today…..researching Matek flight controllers, fine-tuning the UAV build, and experimenting with Depron wing construction techniques for maximum structural rigidity and low weight ✈️ Decided to postpone the deep history and lore to the one of the upcoming dev log
Dev Log #30 Took some resttt, needed it fr. Real talk tho…. when I first made this Stardance account I was on vacation, like fully hardware-less, so everything you guys have seen so far has just been the soft side, website stuff, socials, online grind. That’s about to flip. I’m finally back and about to start unpacking the actual hardware, the stuff I genuinely missed sooo much 🔧 give it about a week and you’ll start seeing real hardware content again, not just screens and code. Also… picked something up 👀 not saying what yet but it’s my favorite microcontroller, more on that in the next dev log. And once the website’s fully wrapped up, it’s hardware timeee. For real this time. Yippee 🚀✈️
Dev Log #31 soo yeahhh spent a lot of time building the ai part of the websitee and yeah it kept glichting out a ton of times and then it wont deploy, most of the time was spent on trying to deploy the site…i hope it looks cool
Dev log #32 spent 4 hours straight building out the AI side of the site and it was basically just me vs. a wall of bugs , the website kept glitching, logic broke everywhere, and then the deployment refused to cooperate for way too long. but after a lot of console staring and one very questionable fix, projectphantom.space is finally live. go take a look and if anything feels off, drop a suggestion below.
Dev log #33 I promise this will be the final time i will be spending hours on the same website..i added more animations and interactive features added pervious members list and also our first flight vid have a look…until next time byeee
Dev Log #34 Made a applicant form for joining phantom tdyyy and also made a new page for terms hoping to see new members
Dev log #35 not much just editing bugs on the websitee
Dev Log #36 had a extra get in touch button soo fixed it and alsoo a bit of checking on lighthouse if our website is actually good ngll
Dev log #37 more changes to the website…this is getting boring
Dev Log #38 more changes on the website and alsoo made a personal website for me
Dev Log #38 finallyy geting to the hardware partt had a few sensors without pins soo kinda soldered headers on them and also burnt my fingers….(first time lol)
Dev Log #40 hardware testing started today with sensors borrowed from my tutor. soldered header pins on the modules. tested 4 sensors in total and 3 of them worked: scd41 co2, vl53l0x tof, and bme680 all gave clean readings. the icm-20948 imu failed with an i2c begin error, not sure if its an address issue or if i broke it while soldering. calling it for tonight cause its late, will run an i2c scanner tmmm to check if the icm is alive....
|
1792543855.7126207
|
1793148655.7126207
|
|
4235
|
Terasong by @lollollolmymy | Stardance
|
lollollolmymy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Terasong by @lollollolmymy | Stardance
|
1792777666.983347
|
1793382466.983347
|
|
4236
|
Early Scan AI by @Angelo | Stardance
|
Angelo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Early Scan AI by @Angelo | Stardance
|
1792633978.6917026
|
1793238778.6917026
|
|
4237
|
My awesome macropad! by @ahmedk | Stardance
|
ahmedk
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ahmedk | Stardance
|
1792954083.9101253
|
1793818083.9101253
|
|
4238
|
red bull tracker by @neset | Stardance
|
neset
|
1
|
22.29
|
336
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-06T20:00:22Z", "hours": 22.0, "multiplier": 15.51, "payout": 336, "blessing": "neutral", "text": "this is a caffeine drink tracker allowing you to add and track your caffeine intake across multiple days. i wrote it using svelte and postgresql. this was one of my first projects that i wrote with svelte, so i learned quite a bit about it. i also did custom art and design for each of the drinks in figma.", "repo": "https://github.com/nesetkab/redbull", "demo": "https://redbull.nesetk.com"}]...
|
[{"post_id": 77666, "ts": "202 [{"post_id": 77666, "ts": "2026-10-07T19:35:28Z", "hours": 0.2911, "text": "bug fixes"}, {"post_id": 77399, "ts": "2026-10-06T19:58:44Z", "hours": 2.0128, "text": "ready to ship! added an intro explaining what this is added cookies so u can track ur own data made my data global for everyone to see minor bug fixes todo: add more drinks"}, {"post_id": 19639, "ts": "2026-07-01T00:46:56Z", "hours": 1.6789, "text": "more progress on ui, adding more drinks, polishing drink picker. currently on amtrack so very bad wifi"}, {"post_id": 18904, "ts": "2026-06-30T02:59:09Z", "hours": 2.9706, "text": "im highkey across the country but wtv working on makign picker ux way better look at this yummy anim"}, {"post_id": 16070, "ts": "2026-06-26T03:45:21Z", "hours": 1.8869, "text": "working on looks! statistics looks much better still a lot to do to finish it up, but i’m almost there"}, {"post_id": 15365, "ts": "2026-06-24T23:49:42Z", "hours": 0.5797, "text": "wowzers statistics tooltips need to fix the labels hitting each other $state() might be the best thing in the world"}, {"post_id": 15160, "ts": "2026-06-24T17:02:58Z", "hours": 0.585, "text": "statistics are a lot more prettyyyyy fixed mobile handling for statistics todo: add more drinks drink chooser ui ship!"}, {"post_id": 13894, "ts": "2026-06-22T19:36:41Z", "hours": 2.8711, "text": "LOTS done. changed how data is stored to allow for more drinks to be added added “caffeine” attribute in order to track my caffeine intake (addiction) added statistics in order to track how many redbulls im actually drinking began adding other drinks to do: finalize the UX of how drinks are chosen add more drinks! finish statistics to be more functional and look more pretty ship!"}, {"post_id": 12791, "ts": "2026-06-20T22:21:44Z", "hours": 1.43, "text": "new redbull designs that are more accurate to the real thing! fixed some ux bugs todo: make ui look better add monster? i love monster data analysis ship!"}, {"post_id": 12279, "ts": "2026-06-20T01:40:43Z", "hours": 0.5042, "text": "havent finished the data part yet but i want to make a dev log because look at how BEAUTIFUL the new icons look <3333"}, {"post_id": 12267, "ts": "2026-06-20T01:01:09Z", "hours": 1.1347, "text": "multi-submit works* improved ux a LOT, i really like these tilted incrementers i want to change it so that SF is a toggle rather than a diff redbull, to decrease scrolling (better ux) submitter is VERY chopped rn (that’s why there’s the asterisk) multi submit repeatedly adds the redbull into a list which works but is kind of chopped. also, SF toggle doesn’t rly work. once i restructure the picker, im going to design icons for plus, minus, and SF, improve ui/ux a bit more, and then add data statistics. after that, i think it’ll be good to ship !!!"}, {"post_id": 11668, "ts": "2026-06-19T00:38:31Z", "hours": 0.5356, "text": "added data sorting by day into the tracker! groups by today, yesterday, and then weekly. plan is to add day sorting within those weeks next. also, need to add a way to submit multiple of the same redbull without repeatedly submitting. also, adding statistics would be nice."}, {"post_id": 11048, "ts": "2026-06-18T02:29:21Z", "hours": 0.6739, "text": "today count works now. i wanna go eep but ill work on data analysis tmr"}, {"post_id": 11000, "ts": "2026-06-18T00:52:01Z", "hours": 1.2214, "text": "deleting works now. the beginnings of a viewer exists"}, {"post_id": 10916, "ts": "2026-06-17T21:50:28Z", "hours": 0.4422, "text": "finally added all of the red bull flavors, including the sugarfree ones"}, {"post_id": 10709, "ts": "2026-06-17T15:59:38Z", "hours": 3.16, "text": "i’m now able to choose a redbull and add it! red bulls are stored in a psql database which keeps track of the red bull name, whether its sugarfree or not, and the date it was submitted. todo: add more redbulls! make a more visual data viewer graphs to see my statistics host this so other ppl can see my stats"}]...
|
Title: red bull tracker by @neset | Stardance
Dev Title: red bull tracker by @neset | Stardance
Devlogs:
i’m now able to choose a redbull and add it! red bulls are stored in a psql database which keeps track of the red bull name, whether its sugarfree or not, and the date it was submitted. todo: add more redbulls! make a more visual data viewer graphs to see my statistics host this so other ppl can see my stats
finally added all of the red bull flavors, including the sugarfree ones
deleting works now. the beginnings of a viewer exists
today count works now. i wanna go eep but ill work on data analysis tmr
added data sorting by day into the tracker! groups by today, yesterday, and then weekly. plan is to add day sorting within those weeks next. also, need to add a way to submit multiple of the same redbull without repeatedly submitting. also, adding statistics would be nice.
multi-submit works* improved ux a LOT, i really like these tilted incrementers i want to change it so that SF is a toggle rather than a diff redbull, to decrease scrolling (better ux) submitter is VERY chopped rn (that’s why there’s the asterisk) multi submit repeatedly adds the redbull into a list which works but is kind of chopped. also, SF toggle doesn’t rly work. once i restructure the picker, im going to design icons for plus, minus, and SF, improve ui/ux a bit more, and then add data statistics. after that, i think it’ll be good to ship !!!
havent finished the data part yet but i want to make a dev log because look at how BEAUTIFUL the new icons look <3333
new redbull designs that are more accurate to the real thing! fixed some ux bugs todo: make ui look better add monster? i love monster data analysis ship!
LOTS done. changed how data is stored to allow for more drinks to be added added “caffeine” attribute in order to track my caffeine intake (addiction) added statistics in order to track how many redbulls im actually drinking began adding other drinks to do: finalize the UX of how drinks are chosen add more drinks! finish statistics to be more functional and look more pretty ship!
statistics are a lot more prettyyyyy fixed mobile handling for statistics todo: add more drinks drink chooser ui ship!
wowzers statistics tooltips need to fix the labels hitting each other $state() might be the best thing in the world
working on looks! statistics looks much better still a lot to do to finish it up, but i’m almost there
im highkey across the country but wtv working on makign picker ux way better look at this yummy anim
more progress on ui, adding more drinks, polishing drink picker. currently on amtrack so very bad wifi
ready to ship! added an intro explaining what this is added cookies so u can track ur own data made my data global for everyone to see minor bug fixes todo: add more drinks
bug fixes
Ships:
this is a caffeine drink tracker allowing you to add and track your caffeine intake across multiple days. i wrote it using svelte and postgresql. this was one of my first projects that i wrote with svelte, so i learned quite a bit about it. i also did custom art and design for each of the drinks in figma....
|
1793004709.6281958
|
1793091109.6281958
|
|
4239
|
Nothing by @inatlusnamor | Stardance
|
inatlusnamor
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Nothing by @inatlusnamor | Stardance
|
1792893191.694767
|
1793757191.694767
|
|
4240
|
Plai by @inatlusnamor | Stardance
|
inatlusnamor
|
0
|
4.16
|
0
|
[]
|
[{"post_id": 22354, "ts": "202 [{"post_id": 22354, "ts": "2026-07-04T19:48:47Z", "hours": 4.1553, "text": "Finished my case"}, {"post_id": 1957, "ts": "2026-06-04T06:24:59Z", "hours": 0.0, "text": "Learning How to make a pcb and will start to design one for myself!"}]...
|
Title: Plai by @inatlusnamor | Stardance
Devlogs: Title: Plai by @inatlusnamor | Stardance
Devlogs:
Learning How to make a pcb and will start to design one for myself!
Finished my case...
|
1792518766.6151237
|
1793123566.6151237
|
|
4241
|
My awesome macropad! by @aysha | Stardance
|
aysha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @aysha | Stardance
|
1792543653.5041115
|
1793148453.5041115
|
|
4242
|
U.R.P.M by @Wille_S | Stardance
|
Wille_S
|
0
|
2.96
|
0
|
[]
|
[{"post_id": 13663, "ts": "202 [{"post_id": 13663, "ts": "2026-06-22T12:45:29Z", "hours": 2.325, "text": "I orderd the pcb two weeks ago from AISLER and I´ve solderd the front side of the pcb, I´ll solder the backside and hopefully start testing tommorow and if everything goes as planed I will have a feild test on sunday"}, {"post_id": 818, "ts": "2026-06-02T14:29:42Z", "hours": 0.6364, "text": "Been working on V2.5, will order it in saturday"}]...
|
Title: U.R.P.M by @Wille_S | Stardance
Devlogs:
B Title: U.R.P.M by @Wille_S | Stardance
Devlogs:
Been working on V2.5, will order it in saturday
I orderd the pcb two weeks ago from AISLER and I´ve solderd the front side of the pcb, I´ll solder the backside and hopefully start testing tommorow and if everything goes as planed I will have a feild test on sunday...
|
1792745306.1961482
|
1793350106.1961482
|
|
4243
|
3D printed UPS by @vladm1 | Stardance
|
vladm1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 3D printed UPS by @vladm1 | Stardance
|
1792795778.7342882
|
1793400578.7342882
|
|
4244
|
My awesome macropad! by @fabledboneling | Stardanc My awesome macropad! by @fabledboneling | Stardance...
|
fabledboneling
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @fabledboneling | S Title: My awesome macropad! by @fabledboneling | Stardance...
|
1792619413.4434252
|
1793224213.4434252
|
|
4245
|
My first slack bot! by @aysha | Stardance
|
aysha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @aysha | Stardance
|
1792727489.2610826
|
1793332289.2610826
|
|
4246
|
Rocket Launch Controller for by @28neelmehta | Sta Rocket Launch Controller for by @28neelmehta | Stardance...
|
28neelmehta
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Rocket Launch Controller for by @28neelmeht Title: Rocket Launch Controller for by @28neelmehta | Stardance...
|
1792594284.6635275
|
1793199084.6635275
|
|
4247
|
Dungeon Dive by @Dari | Stardance
|
Dari
|
0
|
1.0
|
0
|
[]
|
[{"post_id": 13009, "ts": "202 [{"post_id": 13009, "ts": "2026-06-21T08:51:18Z", "hours": 0.0, "text": "I’ve added classes with basic stats and skills. Now I just have to make sure they actually do something… Up to this point, most of my time has been spent getting all the little visual things down, and so far, I think its turning out amazing! (The images used ARE AI Generated, I don’t have that kind of talent T-T)"}, {"post_id": 12213, "ts": "2026-06-19T22:44:59Z", "hours": 1.0, "text": "As of right now, there isn’t much to it, but soon enough, I will add a class selection screen, proper enemies, and a dice-based system. It’ll be AI-powered so there will be countless unique encounters."}]...
|
Title: Dungeon Dive by @Dari | Stardance
Devlogs: Title: Dungeon Dive by @Dari | Stardance
Devlogs:
As of right now, there isn’t much to it, but soon enough, I will add a class selection screen, proper enemies, and a dice-based system. It’ll be AI-powered so there will be countless unique encounters.
I’ve added classes with basic stats and skills. Now I just have to make sure they actually do something… Up to this point, most of my time has been spent getting all the little visual things down, and so far, I think its turning out amazing! (The images used ARE AI Generated, I don’t have that kind of talent T-T)...
|
1792921699.1801445
|
1793785699.1801445
|
|
4248
|
My first slack bot! by @Vaishnav | Stardance
|
Vaishnav
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Vaishnav | Stardanc Title: My first slack bot! by @Vaishnav | Stardance...
|
1792738515.4175985
|
1793343315.4175985
|
|
4249
|
M by @tinap | Stardance
|
tinap
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: M by @tinap | Stardance
|
1792633835.6289613
|
1793238635.6289613
|
|
4250
|
My first slack bot! by @Hongyu | Stardance
|
Hongyu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Hongyu | Stardance
|
1792529629.5060697
|
1793134429.5060697
|