|
7825
|
test by @SparrowTaillet | Stardance
|
SparrowTaillet
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: test by @SparrowTaillet | Stardance
|
1793408204.5870101
|
1794013004.5870101
|
|
7826
|
My awesome macropad! by @Frederic | Stardance
|
Frederic
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Frederic | Stardan Title: My awesome macropad! by @Frederic | Stardance...
|
1793206314.4369373
|
1793811114.4369373
|
|
7827
|
My awesome macropad! by @amara_chaker4 | Stardance
|
amara_chaker4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @amara_chaker4 | St Title: My awesome macropad! by @amara_chaker4 | Stardance...
|
1793436916.25116
|
1794041716.25116
|
|
7828
|
My awesome macropad! by @shivank | Stardance
|
shivank
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @shivank | Stardanc Title: My awesome macropad! by @shivank | Stardance...
|
1792911215.460007
|
1793775215.460007
|
|
7829
|
My awesome macropad! by @amara_chaker15 | Stardanc My awesome macropad! by @amara_chaker15 | Stardance...
|
amara_chaker15
|
0
|
8.54
|
0
|
[]
|
[{"post_id": 39289, "ts": "202 [{"post_id": 39289, "ts": "2026-08-02T05:13:34Z", "hours": 2.5672, "text": "It’s been a very long time since I wrote my last devlog, and I’ve worked through a lot of my project. I finished the final design for my PCB and Hackpad case, learned how to get the 3d models of components to show up in KiCad, and began to write the code. I made lots of changes to everything and am really happy I’m almost done with the project and can’t wait to see the final result."}, {"post_id": 18269, "ts": "2026-06-29T11:16:21Z", "hours": 2.3678, "text": "I’ve moved on to the hardest part of this project personally. I’ve used CAD for the hackpad earlier, but it was much simpler, especially because there were only 3 switches. I worked to get the placement right, and there’s still a lot for me to finalise. I also need to learn how to render and make it seem like the components are already there. I feel like it’d be easier for me to do that."}, {"post_id": 17531, "ts": "2026-06-28T11:07:50Z", "hours": 0.5336, "text": "I wanted to add in a drawing on my pcb before i started to design the case for it. I decided to draw a rocketship with my last name in the middle. i just need to make it less to the side and i can start doing my case."}, {"post_id": 17416, "ts": "2026-06-28T05:46:11Z", "hours": 0.5836, "text": "Making my PCB design neater and changing up its format."}, {"post_id": 13489, "ts": "2026-06-22T02:41:43Z", "hours": 0.4619, "text": "I decided to restart my project. I struggled with the matrix wiring in the schematic but managed to figure it out by looking at other peoples schematic designs. I decided to add in another switch, a rotary encoder, an oled screen and 2 leds into my macropad. Doing the PCB now and doing the wiring is a struggle."}, {"post_id": 6124, "ts": "2026-06-10T09:29:57Z", "hours": 0.3, "text": "thinking of restarting from scratch because i want the project to be more unique and cool"}, {"post_id": 6074, "ts": "2026-06-10T06:35:27Z", "hours": 0.3333, "text": "working on case design in Fusion 360. struggled with figuring out all the tools and stuff, but got there in the end. Extruding everything and putting the plate on top of the base was a struggle, not gonna lie."}, {"post_id": 6067, "ts": "2026-06-10T06:11:09Z", "hours": 0.6, "text": "posting my pcb design again because i can’t see it on my other devlog."}, {"post_id": 4820, "ts": "2026-06-08T10:12:24Z", "hours": 0.7975, "text": "I’ve been trying to figure out how to use KiCad for my project. So far, I’ve done the schematic and pcb. For my first-ever project, I want it to be simple. So only 3 keys on the macropad and that’s it."}]...
|
Title: My awesome macropad! by @amara_chaker15 | S Title: My awesome macropad! by @amara_chaker15 | Stardance
Devlogs:
I’ve been trying to figure out how to use KiCad for my project. So far, I’ve done the schematic and pcb. For my first-ever project, I want it to be simple. So only 3 keys on the macropad and that’s it.
posting my pcb design again because i can’t see it on my other devlog.
working on case design in Fusion 360. struggled with figuring out all the tools and stuff, but got there in the end. Extruding everything and putting the plate on top of the base was a struggle, not gonna lie.
thinking of restarting from scratch because i want the project to be more unique and cool
I decided to restart my project. I struggled with the matrix wiring in the schematic but managed to figure it out by looking at other peoples schematic designs. I decided to add in another switch, a rotary encoder, an oled screen and 2 leds into my macropad. Doing the PCB now and doing the wiring is a struggle.
Making my PCB design neater and changing up its format.
I wanted to add in a drawing on my pcb before i started to design the case for it. I decided to draw a rocketship with my last name in the middle. i just need to make it less to the side and i can start doing my case.
I’ve moved on to the hardest part of this project personally. I’ve used CAD for the hackpad earlier, but it was much simpler, especially because there were only 3 switches. I worked to get the placement right, and there’s still a lot for me to finalise. I also need to learn how to render and make it seem like the components are already there. I feel like it’d be easier for me to do that.
It’s been a very long time since I wrote my last devlog, and I’ve worked through a lot of my project. I finished the final design for my PCB and Hackpad case, learned how to get the 3d models of components to show up in KiCad, and began to write the code. I made lots of changes to everything and am really happy I’m almost done with the project and can’t wait to see the final result....
|
1793256880.3709376
|
1793861680.3709376
|
|
7830
|
A.S.T.R.A. by @carlitos_miguel0922 | Stardance
|
carlitos_miguel0922
|
0
|
5.25
|
0
|
[]
|
[{"post_id": 39690, "ts": "202 [{"post_id": 39690, "ts": "2026-08-02T20:34:11Z", "hours": 3.8861, "text": "Came back. After a long time away, working on my college application, working, and enjoying my summer vacation, I am back. Today I am posting my progress in the UI. Throughout this frontend development time, I have done a lot and struggled a lot. The main problems were connecting the two ends and starting the FastAPI server due to some code issues. Now I have finally done most of it, including the frontend Mission Control, parameters, telemetry, and live flight updates. The next step is to design the 3D Solar map, the paths, and finally the AI advisor so that it can manipulate the mission, give advice, and basically act like a Jarvis AI. After the first demo is completed, I will then move on to the hardware development, which consists of a vision-based hand-gesture tracker to replace the mouse in a more interactive system. I actually already have such a system, using YOLO-based code. Talking about improvements, I would change the UI into a website-like page with a more intuitive layout so that it will have all the necessary systems on fewer pages. I would really appreciate any suggestions on how you would like the UI to look. Wait for the next devlog for the Demo."}, {"post_id": 5876, "ts": "2026-06-09T20:39:01Z", "hours": 1.36, "text": "Update: In the past days I have been working on the next steps for ASTRA. Today I made the section which will be used to recreate historical missions such as Apollo 11 and 13. Another achievement is the new system which does not follow the same pattern for each destination, but depending on the destination fuel, max payload, radiation exposure, and other mission parameters change accordingly."}]...
|
Title: A.S.T.R.A. by @carlitos_miguel0922 | Starda Title: A.S.T.R.A. by @carlitos_miguel0922 | Stardance
Devlogs:
Update: In the past days I have been working on the next steps for ASTRA. Today I made the section which will be used to recreate historical missions such as Apollo 11 and 13. Another achievement is the new system which does not follow the same pattern for each destination, but depending on the destination fuel, max payload, radiation exposure, and other mission parameters change accordingly.
Came back. After a long time away, working on my college application, working, and enjoying my summer vacation, I am back. Today I am posting my progress in the UI. Throughout this frontend development time, I have done a lot and struggled a lot. The main problems were connecting the two ends and starting the FastAPI server due to some code issues. Now I have finally done most of it, including the frontend Mission Control, parameters, telemetry, and live flight updates. The next step is to design the 3D Solar map, the paths, and finally the AI advisor so that it can manipulate the mission, give advice, and basically act like a Jarvis AI. After the first demo is completed, I will then move on to the hardware development, which consists of a vision-based hand-gesture tracker to replace the mouse in a more interactive system. I actually already have such a system, using YOLO-based code. Talking about improvements, I would change the UI into a website-like page with a more intuitive layout so that it will have all the necessary systems on fewer pages. I would really appreciate any suggestions on how you would like the UI to look. Wait for the next devlog for the Demo....
|
1793458307.7147665
|
1794063107.7147665
|
|
7833
|
Youth and contemporary development (YCD) Cameroon Youth and contemporary development (YCD) Cameroon for GBHS OBALA students. by @Ndiforkangoh-Marouf-Kenyui | Stardance...
|
Ndiforkangoh-Marouf-Kenyui
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Youth and contemporary development (YCD) Ca Title: Youth and contemporary development (YCD) Cameroon for GBHS OBALA students. by @Ndiforkangoh-Marouf-Kenyui | Stardance...
|
1793638073.7406168
|
1794242873.7406168
|
|
7834
|
Vibe Game by @horatiu_budai | Stardance
|
horatiu_budai
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Vibe Game by @horatiu_budai | Stardance
|
1793177401.9770248
|
1793782201.9770248
|
|
7835
|
Av-cat by @curlq | Stardance
|
curlq
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Av-cat by @curlq | Stardance
|
1793573284.0063481
|
1794178084.0063481
|
|
7836
|
LLM (Lua Library Mediocrity) by @Lunairye | Starda LLM (Lua Library Mediocrity) by @Lunairye | Stardance...
|
Lunairye
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: LLM (Lua Library Mediocrity) by @Lunairye | Title: LLM (Lua Library Mediocrity) by @Lunairye | Stardance...
|
1793314210.8335767
|
1793919010.8335767
|
|
7837
|
My awesome macropad! by @maxEbon | Stardance
|
maxEbon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @maxEbon | Stardanc Title: My awesome macropad! by @maxEbon | Stardance...
|
1793184725.4751687
|
1793789525.4751687
|
|
7838
|
Untitled by @KA_777 | Stardance
|
KA_777
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @KA_777 | Stardance
|
1793357615.7143357
|
1793962415.7143357
|
|
7839
|
My awesome macropad! by @abc_saunderz | Stardance
|
abc_saunderz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @abc_saunderz | Sta Title: My awesome macropad! by @abc_saunderz | Stardance...
|
1793454812.9277768
|
1794059612.9277768
|
|
7840
|
CrashLink by @GhOsT_ | Stardance
|
GhOsT_
|
0
|
24.0
|
0
|
[]
|
[{"post_id": 8937, "ts": "2026 [{"post_id": 8937, "ts": "2026-06-14T21:06:44Z", "hours": 2.0, "text": "Devlog - 7 so finally I am done with all this pcb designing thing exported the files into gerbers,png,step file type next steps push these files to github repo submit project for grant on stardance Thank you for your attention to this matter -GhOsT"}, {"post_id": 8422, "ts": "2026-06-14T00:11:21Z", "hours": 6.0, "text": "Dev log-6 Finally done with PCB design of relay node and vehicle node. yet to push design files on github. It becomes hard to route manually for me so i end up doing autoroute in the end. I used reference design from datasheets to make it easy for me to follow and make this pcb design. next steps -PCB Design for Gatewaynode -Push all files to github -Start designing Enclosure for each node"}, {"post_id": 8064, "ts": "2026-06-13T13:56:36Z", "hours": 2.0, "text": "Devlog -5 Turns out my last PCB design for vehicle node had many flaws. No filtering near power inputs No SIM socket for GSM module 😭(the classic blunder) Power regulation issues(using external buck converters while i could design it on my own) Assumption of using 2S Li-ion would be minimum necessity . So far I have fixed the followings Power regulation for GSM,GPS,ESP,MPU,LoRa Added sim socket(working on its connection) Next steps Connect SIM Socket Add power key circuit Add Reset button for GSM Figure out if anything else to add for GSM Make relay node schematics Make GatewayNode schematics"}, {"post_id": 7747, "ts": "2026-06-12T22:50:16Z", "hours": 4.0, "text": "Was working on documentation part of the project did some changes in README.md file and spent a lot of time in making BOM it took time to find out components and there prices required to prepare BOM."}, {"post_id": 4631, "ts": "2026-06-08T00:50:41Z", "hours": 6.0, "text": "PCB Designing and Documentation. Rearranged schematics for Vehicle Node. Revised PCB design for Vechile Node. 3.Made schematics for Relay Node. Designed PCB for Relay Node. Added files ( gerber , pcb image, schematics pdf) to repo."}, {"post_id": 3076, "ts": "2026-06-05T23:37:31Z", "hours": 3.0, "text": "designed schematics and pcb for vehicle node( not a final design..it need some more work)"}, {"post_id": 2694, "ts": "2026-06-05T12:03:55Z", "hours": 1.0, "text": "working on code part and setting up github repo made 3 code files for 3 Nodes added basic structure of each files(setup and loop function) added crash detection function in vehicle node next- make schematics & update READ.md"}]...
|
Title: CrashLink by @GhOsT_ | Stardance
Devlogs:
Title: CrashLink by @GhOsT_ | Stardance
Devlogs:
working on code part and setting up github repo made 3 code files for 3 Nodes added basic structure of each files(setup and loop function) added crash detection function in vehicle node next- make schematics & update READ.md
designed schematics and pcb for vehicle node( not a final design..it need some more work)
PCB Designing and Documentation. Rearranged schematics for Vehicle Node. Revised PCB design for Vechile Node. 3.Made schematics for Relay Node. Designed PCB for Relay Node. Added files ( gerber , pcb image, schematics pdf) to repo.
Was working on documentation part of the project did some changes in README.md file and spent a lot of time in making BOM it took time to find out components and there prices required to prepare BOM.
Devlog -5 Turns out my last PCB design for vehicle node had many flaws. No filtering near power inputs No SIM socket for GSM module 😭(the classic blunder) Power regulation issues(using external buck converters while i could design it on my own) Assumption of using 2S Li-ion would be minimum necessity . So far I have fixed the followings Power regulation for GSM,GPS,ESP,MPU,LoRa Added sim socket(working on its connection) Next steps Connect SIM Socket Add power key circuit Add Reset button for GSM Figure out if anything else to add for GSM Make relay node schematics Make GatewayNode schematics
Dev log-6 Finally done with PCB design of relay node and vehicle node. yet to push design files on github. It becomes hard to route manually for me so i end up doing autoroute in the end. I used reference design from datasheets to make it easy for me to follow and make this pcb design. next steps -PCB Design for Gatewaynode -Push all files to github -Start designing Enclosure for each node
Devlog - 7 so finally I am done with all this pcb designing thing exported the files into gerbers,png,step file type next steps push these files to github repo submit project for grant on stardance Thank you for your attention to this matter -GhOsT...
|
1792918421.8760757
|
1793782421.8760757
|
|
7841
|
Untitled by @abc_saunderz | Stardance
|
abc_saunderz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @abc_saunderz | Stardance
|
1793238723.2528875
|
1793843523.2528875
|
|
7842
|
My first slack bot! by @insaf | Stardance
|
insaf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @insaf | Stardance
|
1793141673.1290588
|
1793746473.1290588
|
|
7843
|
EMG Signal Recorder by @yaasshh | Stardance
|
yaasshh
|
0
|
10.16
|
0
|
[]
|
[{"post_id": 23494, "ts": "202 [{"post_id": 23494, "ts": "2026-07-06T14:51:24Z", "hours": 9.0856, "text": "It’s a wonderful day. I feel like I am completely finished with this project—or at least finished to some extent—because I still need to get the PCB, solder everything, and test it properly. However, I’ve done as much as I can to the best of my abilities for now. I am definitely proud of the work that led me here. It has been close to 50 hours of work over a month. It was a long month with a lot of school and personal things going on, but I powered through it. I made a lot of mistakes and had to redo the entire thing twice, which led me to a breaking point at one stage, but I pushed through and I’m proud of that. I have checked everything and gone through all the materials. Regarding the next steps: PCB Manufacturing After the discount, this will be around $20–$30. I am hoping to get funding for that. Individual Parts The rest of the money will be for the components. I’ll get those from AliExpress or somewhere similar where I can buy in bulk for very cheap. I’m not opting for Digi-Key because I was having a lot of trouble going through their system. On AliExpress, I can get most of what I need for around 60–80 AED (approximately $25). Buying in bulk means I can keep extra parts for other projects, which will reduce the funding I need later on. All the PCB files, schematics, and Gerber files have been pushed to GitHub. I’m hoping to get the funding as soon as possible so I can start working on this ASAP. I am really looking forward to the next project, which should include the sensor itself. The faster this gets done, the sooner I can start working on that next project much more efficiently. P.S. Basically, I have put close to or above 50 hours of work into this project over a month of work, averaging almost two hours every day. I’m proud of this, and for those who don’t believe me, everything is documented on Macondo (the Hack Club challenge). You are free to view the journals over there. However, I will also be adding a journal.md to my GitHub in a bit. Not right now, though, as I am severely burned out from this project. I need to start a new project and put my mind to something else for a while. I hope I get the funding for this because I really want to move on to the actual hardware aspect, start soldering, and actually test it out. I will be using this in multiple other projects as well. So yeah, thank you for reading."}, {"post_id": 6147, "ts": "2026-06-10T10:30:11Z", "hours": 1.0794, "text": "So first Dev-Post, I am building a signal recorder for electromyography (EMG) signals, which are essentially the electrical impulses that muscles produce when you contract or relax. I am recording those signals through electrodes on an arm that will be connected to a circuit I am currently working on. My plan is to: Create and test the circuit Convert it into a PCB that I can manufacture to be quite small Integrate it into a bunch of my own projects Make it open source so other people can use it in the future So far, two stages have been completed: Stage Zero: 2.5V bias circuit Stage 1: INA (instrumentation amplifier) circuit and setup Stage 2: 20Hz notch filter"}]...
|
Title: EMG Signal Recorder by @yaasshh | Stardance Title: EMG Signal Recorder by @yaasshh | Stardance
Devlogs:
So first Dev-Post, I am building a signal recorder for electromyography (EMG) signals, which are essentially the electrical impulses that muscles produce when you contract or relax. I am recording those signals through electrodes on an arm that will be connected to a circuit I am currently working on. My plan is to: Create and test the circuit Convert it into a PCB that I can manufacture to be quite small Integrate it into a bunch of my own projects Make it open source so other people can use it in the future So far, two stages have been completed: Stage Zero: 2.5V bias circuit Stage 1: INA (instrumentation amplifier) circuit and setup Stage 2: 20Hz notch filter
It’s a wonderful day. I feel like I am completely finished with this project—or at least finished to some extent—because I still need to get the PCB, solder everything, and test it properly. However, I’ve done as much as I can to the best of my abilities for now. I am definitely proud of the work that led me here. It has been close to 50 hours of work over a month. It was a long month with a lot of school and personal things going on, but I powered through it. I made a lot of mistakes and had to redo the entire thing twice, which led me to a breaking point at one stage, but I pushed through and I’m proud of that. I have checked everything and gone through all the materials. Regarding the next steps: PCB Manufacturing After the discount, this will be around $20–$30. I am hoping to get funding for that. Individual Parts The rest of the money will be for the components. I’ll get those from AliExpress or somewhere similar where I can buy in bulk for very cheap. I’m not opting for Digi-Key because I was having a lot of trouble going through their system. On AliExpress, I can get most of what I need for around 60–80 AED (approximately $25). Buying in bulk means I can keep extra parts for other projects, which will reduce the funding I need later on. All the PCB files, schematics, and Gerber files have been pushed to GitHub. I’m hoping to get the funding as soon as possible so I can start working on this ASAP. I am really looking forward to the next project, which should include the sensor itself. The faster this gets done, the sooner I can start working on that next project much more efficiently. P.S. Basically, I have put close to or above 50 hours of work into this project over a month of work, averaging almost two hours every day. I’m proud of this, and for those who don’t believe me, everything is documented on Macondo (the Hack Club challenge). You are free to view the journals over there. However, I will also be adding a journal.md to my GitHub in a bit. Not right now, though, as I am severely burned out from this project. I need to start a new project and put my mind to something else for a while. I hope I get the funding for this because I really want to move on to the actual hardware aspect, start soldering, and actually test it out. I will be using this in multiple other projects as well. So yeah, thank you for reading....
|
1792947162.9260356
|
1793811162.9260356
|
|
7844
|
My awesome macropad! by @banangler | Stardance
|
banangler
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @banangler | Starda Title: My awesome macropad! by @banangler | Stardance...
|
1793386162.4870758
|
1793990962.4870758
|
|
7845
|
My first slack bot! by @Elina | Stardance
|
Elina
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Elina | Stardance
|
1793155677.1357284
|
1793760477.1357284
|
|
7846
|
My awesome macropad! by @Violet_F | Stardance
|
Violet_F
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Violet_F | Stardan Title: My awesome macropad! by @Violet_F | Stardance...
|
1793519802.2367694
|
1794124602.2367694
|
|
7847
|
Untitled by @Nelstar | Stardance
|
Nelstar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Nelstar | Stardance
|
1793231641.163797
|
1793836441.163797
|
|
7849
|
Pencil and Paper by @saventv | Stardance
|
saventv
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Pencil and Paper by @saventv | Stardance
|
1793234956.3745642
|
1793839756.3745642
|
|
7850
|
Scrolling Window Manager by @saventv | Stardance
|
saventv
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Scrolling Window Manager by @saventv | Star Title: Scrolling Window Manager by @saventv | Stardance...
|
1793181339.9295893
|
1793786139.9295893
|
|
7851
|
PORTY by @atharva123aa | Stardance
|
atharva123aa
|
0
|
0.25
|
0
|
[]
|
[{"post_id": 5431, "ts": "2026 [{"post_id": 5431, "ts": "2026-06-09T06:20:33Z", "hours": 0.2525, "text": "The main support backend for my app gully cricket tracker bot also used data .json to support it"}]...
|
Title: PORTY by @atharva123aa | Stardance
Devlogs Title: PORTY by @atharva123aa | Stardance
Devlogs:
The main support backend for my app gully cricket tracker bot also used data .json to support it...
|
1792900219.3635428
|
1793764219.3635428
|
|
7852
|
Untitled project by @shauli | Stardance
|
shauli
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @shauli | Stardance
|
1793476363.6018322
|
1794081163.6018322
|
|
7853
|
Untitled by @GhOsT_ | Stardance
|
GhOsT_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @GhOsT_ | Stardance
|
1793181360.2683945
|
1793786160.2683945
|
|
7855
|
RoamingBlock by @CoolV3 | Stardance
|
CoolV3
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: RoamingBlock by @CoolV3 | Stardance
|
1793206574.7780027
|
1793811374.7780027
|
|
7856
|
nexcards by @ekamwadhwa2004 | Stardance
|
ekamwadhwa2004
|
0
|
0.3
|
0
|
[]
|
[{"post_id": 11248, "ts": "202 [{"post_id": 11248, "ts": "2026-06-18T12:22:32Z", "hours": 0.3, "text": "i have started this project for more than a week but wasnt able to work on it but i had done the schematic but couldnt upload the devlog because of 15 min code limitation but yeah the schematic is done i used a rp2040 for the brain, mcp73831 for the power and battery management, an oled panel, a few switced and a usb c port with 16 pins wait a sec i can’t add time for how much i worked on it i spent about 3 hours including research and pcb design"}]...
|
Title: nexcards by @ekamwadhwa2004 | Stardance
De Title: nexcards by @ekamwadhwa2004 | Stardance
Devlogs:
i have started this project for more than a week but wasnt able to work on it but i had done the schematic but couldnt upload the devlog because of 15 min code limitation but yeah the schematic is done i used a rp2040 for the brain, mcp73831 for the power and battery management, an oled panel, a few switced and a usb c port with 16 pins wait a sec i can’t add time for how much i worked on it i spent about 3 hours including research and pcb design...
|
1793490623.8998623
|
1794095423.8998623
|
|
7857
|
My first slack bot! by @thanEay | Stardance
|
thanEay
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @thanEay | Stardance
|
1793555239.2496262
|
1794160039.2496262
|
|
7858
|
My first slack bot! by @dhruvkamble154 | Stardance
|
dhruvkamble154
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @dhruvkamble154 | St Title: My first slack bot! by @dhruvkamble154 | Stardance...
|
1793559496.623015
|
1794164296.623015
|
|
7859
|
My awesome macropad! by @10jneely | Stardance
|
10jneely
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @10jneely | Stardan Title: My awesome macropad! by @10jneely | Stardance...
|
1793397209.078998
|
1794002009.078998
|
|
7860
|
x44 by @heisenberg | Stardance
|
heisenberg
|
0
|
44.8
|
0
|
[]
|
[{"post_id": 60229, "ts": "202 [{"post_id": 60229, "ts": "2026-09-02T13:51:16Z", "hours": 11.7039, "text": "Devlog 6 Continuing x44 after 2 months. I was very busy with school work. Coming back to it after a long time, i am seeing that my initial design had the Rust build worker doing too much. The CF Worker pushed a job to a queue and sent a ping to the VPS over HTTP. The Rust build worker then had to authenticate against CF’s REST API, pull the queue message, execute the build, upload artifacts to R2, and acknowledge the message. This over complicated the system. The Architectural Change Instead of the rust build worker pulling jobs queues after the ping, I made the control-plane worker both queue producer and queue consumer. Now the Pipeline Looks like this:- When a project is created or a git push occurs the Worker records a queued row in D1 and pushes the build configuration into the queue. The Worker then takes 1 job from the queue and send the build configuration to the Rust build worker, If a build is running CF natively waits for it to be acknowledged-no custom logic for it Then the Rust build worker finally runs the build and upload the build output to R2.[I acknowledge the job even if the build fails to prevent retry loops] No frontend changes, see my IDE"}, {"post_id": 30109, "ts": "2026-07-17T12:54:56Z", "hours": 5.2083, "text": "Devlog 5 I finished the /new-project page and wrote some types. While testing I found a major bug, that if a build request comes to the build-worker while a build is running then the output files gets overwritten, resulting in a broken deployment. I could fix it by having the outputs of the build on separate folders and uploading them one by one. But this approach wasn’t utilising the queues. I will change the structure to something like this, [Github Webhook/Initial Deploy] -> [Control-plane] -> [Cloudflare Queue] -> [control-plane queue handler] -> this sends the build details to the build-worker after building it will update the status of the deployment. This was i don’t have to manage concurrency my self I am spending a lot of time in styling. hope it looks good :?) Nexxt Building what I just explained. Improve the bland dashboard."}, {"post_id": 27080, "ts": "2026-07-12T10:00:23Z", "hours": 10.2703, "text": "Devlog 4 - Build the structure of the dashboard Just build the layout of the dashboard and created a new page for creating new projects[design inspired by cloudflare]. You might be thinking that this should not take 10 hours and you are right. My first thought was to not to create a new page but a dialog box. But the combobox I used for selecting repo was not registering the clicks, i was working with keyboard tho. After trying to debug a lot, I asked AI why it was not working as intended. Because I had both base-ui and radix-ui wasted 4 hours on it and ended up creating a new page altogether Next: Complete the /new-project page Connect the builder with the backend Add a detail page for projects"}, {"post_id": 20740, "ts": "2026-07-02T13:01:51Z", "hours": 9.2825, "text": "Devlog #3 Changes Made the landing page for x44. Tho it was mostly generated by AI, I did the authentication and styling for the button. Set-up drizzle orm and wrote the schema for the database. Authentication(used better-auth) The problems I faced I tried to make my own authentication system, and realised after more than two hours of work that there is still a lot of work to be done to make it secure. And i can use that time to add more features. So I switched to better-auth it was a great decision according to me. And if you are in search of an authentication framework I recommend you to check better-auth once them have amazing documentation. To initialise better-auth in cf worker, I first needed to initialse drizzle and it requires a D1 instance which in only available in the context of a request. So I made a getAuth function const getAuth = ( ctx : Context ) => { const db = drizzle ( ctx . env . DB , { schema }) const auth = betterAuth ({ database : drizzleAdapter ( db , { provider : \" sqlite \" , schema })}) return auth } Currently working on dashboard(this is not by AI) If you have any suggestion please comment, and you can view the system architecture in the previous devlog[i am not yet sure about the subdomain routing part, so that is not drawn]. ✌️"}, {"post_id": 13592, "ts": "2026-06-22T08:32:27Z", "hours": 4.3369, "text": "This commit was a big one. The build-worker finally got a proper API layer, added Axum with an auth middleware so only authorized clients can trigger builds. The whole flow is now queue-driven: the worker pulls jobs from Cloudflare Queues, runs the Docker build, uploads output to R2, and acknowledges the message. Feels way more production ready. Also spun up the monorepo structure properly. Added apps/control-plane (Cloudflare Worker), apps/website (Vite frontend), and packages/db-schema for shared types. pnpm workspaces are configured, root package.json has a dev:backend script. Basic .gitignore in place. The most frustrating thing was that the Cloudflare Queue send function is not working. I’ve spent hours trying to debug it, messages aren’t showing up on the CF dashboard at all. The pull/ack endpoints seem fine, but pushing messages into the queue is a dead end. Hoping that actually deploying the control-plane worker might fix it,maybe it’s a local dev environment issue with wrangler. Either way, this is the main blocker right now. If anyone has hit this, I’d love to hear how you solved it. Git commit: https://github.com/xxeisenberg/x44/commit/9b1669bd7e935043367ba32c2abadc1428f80596"}, {"post_id": 5363, "ts": "2026-06-09T03:11:41Z", "hours": 3.995, "text": "I have built the docker image that will build the code and a rust program that will run the docker container and upload the build output to Cloudflare R2."}]...
|
Title: x44 by @heisenberg | Stardance
Devlogs:
I Title: x44 by @heisenberg | Stardance
Devlogs:
I have built the docker image that will build the code and a rust program that will run the docker container and upload the build output to Cloudflare R2.
This commit was a big one. The build-worker finally got a proper API layer, added Axum with an auth middleware so only authorized clients can trigger builds. The whole flow is now queue-driven: the worker pulls jobs from Cloudflare Queues, runs the Docker build, uploads output to R2, and acknowledges the message. Feels way more production ready. Also spun up the monorepo structure properly. Added apps/control-plane (Cloudflare Worker), apps/website (Vite frontend), and packages/db-schema for shared types. pnpm workspaces are configured, root package.json has a dev:backend script. Basic .gitignore in place. The most frustrating thing was that the Cloudflare Queue send function is not working. I’ve spent hours trying to debug it, messages aren’t showing up on the CF dashboard at all. The pull/ack endpoints seem fine, but pushing messages into the queue is a dead end. Hoping that actually deploying the control-plane worker might fix it,maybe it’s a local dev environment issue with wrangler. Either way, this is the main blocker right now. If anyone has hit this, I’d love to hear how you solved it. Git commit: https://github.com/xxeisenberg/x44/commit/9b1669bd7e935043367ba32c2abadc1428f80596
Devlog #3 Changes Made the landing page for x44. Tho it was mostly generated by AI, I did the authentication and styling for the button. Set-up drizzle orm and wrote the schema for the database. Authentication(used better-auth) The problems I faced I tried to make my own authentication system, and realised after more than two hours of work that there is still a lot of work to be done to make it secure. And i can use that time to add more features. So I switched to better-auth it was a great decision according to me. And if you are in search of an authentication framework I recommend you to check better-auth once them have amazing documentation. To initialise better-auth in cf worker, I first needed to initialse drizzle and it requires a D1 instance which in only available in the context of a request. So I made a getAuth function const getAuth = ( ctx : Context ) => { const db = drizzle ( ctx . env . DB , { schema }) const auth = betterAuth ({ database : drizzleAdapter ( db , { provider : " sqlite " , schema })}) return auth } Currently working on dashboard(this is not by AI) If you have any suggestion please comment, and you can view the system architecture in the previous devlog[i am not yet sure about the subdomain routing part, so that is not drawn]. ✌️
Devlog 4 - Build the structure of the dashboard Just build the layout of the dashboard and created a new page for creating new projects[design inspired by cloudflare]. You might be thinking that this should not take 10 hours and you are right. My first thought was to not to create a new page but a dialog box. But the combobox I used for selecting repo was not registering the clicks, i was working with keyboard tho. After trying to debug a lot, I asked AI why it was not working as intended. Because I had both base-ui and radix-ui wasted 4 hours on it and ended up creating a new page altogether Next: Complete the /new-project page Connect the builder with the backend Add a detail page for projects
Devlog 5 I finished the /new-project page and wrote some types. While testing I found a major bug, that if a build request comes to the build-worker while a build is running then the output files gets overwritten, resulting in a broken deployment. I could fix it by having the outputs of the build on separate folders and uploading them one by one. But this approach wasn’t utilising the queues. I will change the structure to something like this, [Github Webhook/Initial Deploy] -> [Control-plane] -> [Cloudflare Queue] -> [control-plane queue handler] -> this sends the build details to the build-worker after building it will update the status of the deployment. This was i don’t have to manage concurrency my self I am spending a lot of time in styling. hope it looks good :?) Nexxt Building what I just explained. Improve the bland dashboard.
Devlog 6 Continuing x44 after 2 months. I was very busy with school work. Coming back to it after a long time, i am seeing that my initial design had the Rust build worker doing too much. The CF Worker pushed a job to a queue and sent a ping to the VPS over HTTP. The Rust build worker then had to authenticate against CF’s REST API, pull the queue message, execute the build, upload artifacts to R2, and acknowledge the message. This over complicated the system. The Architectural Change Instead of the rust build worker pulling jobs queues after the ping, I made the control-plane worker both queue producer and queue consumer. Now the Pipeline Looks like this:- When a project is created or a git push occurs the Worker records a queued row in D1 and pushes the build configuration into the queue. The Worker then takes 1 job from the queue and send the build configuration to the Rust build worker, If a build is running CF natively waits for it to be acknowledged-no custom logic for it Then the Rust build worker finally runs the build and upload the build output to R2.[I acknowledge the job even if the build fails to prevent retry loops] No frontend changes, see my IDE...
|
1793357350.9687378
|
1793962150.9687378
|
|
7861
|
Casino Simulator by @number1codingfan | Stardance
|
number1codingfan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Casino Simulator by @number1codingfan | Sta Title: Casino Simulator by @number1codingfan | Stardance...
|
1793231470.4591386
|
1793836270.4591386
|
|
7862
|
Scrabbly by @Hsoj | Stardance
|
Hsoj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Scrabbly by @Hsoj | Stardance
|
1793598753.2775686
|
1794462753.2775686
|
|
7863
|
Untitled project by @antony | Stardance
|
antony
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @antony | Stardance
|
1792925674.1627514
|
1793789674.1627514
|
|
7865
|
Mechanical/Balance Scale by @jinen | Stardance
|
jinen
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mechanical/Balance Scale by @jinen | Starda Title: Mechanical/Balance Scale by @jinen | Stardance...
|
1793447527.9531827
|
1794052327.9531827
|
|
7866
|
quadpad by @Cret | Stardance
|
Cret
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: quadpad by @Cret | Stardance
|
1793173707.0283258
|
1793778507.0283258
|
|
7867
|
Untitled project by @yessa | Stardance
|
yessa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @yessa | Stardance
|
1793508650.058266
|
1794113450.058266
|
|
7868
|
HE Synth by @heian | Stardance
|
heian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: HE Synth by @heian | Stardance
|
1792921742.8590372
|
1793785742.8590372
|
|
7869
|
My first slack bot! by @MightBeIvan | Stardance
|
MightBeIvan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @MightBeIvan | Stard Title: My first slack bot! by @MightBeIvan | Stardance...
|
1793537796.6693115
|
1794142596.6693115
|
|
7870
|
Futuristic Gaming Dashboard UI Concept by @Abd-ul- Futuristic Gaming Dashboard UI Concept by @Abd-ul-Hussain | Stardance...
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Futuristic Gaming Dashboard UI Concept by @ Title: Futuristic Gaming Dashboard UI Concept by @Abd-ul-Hussain | Stardance...
|
1793328516.6190891
|
1793933316.6190891
|
|
7871
|
Untitled project by @madushankarajapaksha999 | Sta Untitled project by @madushankarajapaksha999 | Stardance...
|
madushankarajapaksha999
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @madushankarajapaksha99 Title: Untitled project by @madushankarajapaksha999 | Stardance...
|
1793235221.1653626
|
1793840021.1653626
|
|
7872
|
My first slack bot! by @ecclestonkatie153 | Starda My first slack bot! by @ecclestonkatie153 | Stardance...
|
ecclestonkatie153
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @ecclestonkatie153 | Title: My first slack bot! by @ecclestonkatie153 | Stardance...
|
1793400921.911343
|
1794005721.911343
|
|
7873
|
75-days challenge by @insaf | Stardance
|
insaf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 75-days challenge by @insaf | Stardance
|
1793566556.3163235
|
1794171356.3163235
|
|
7874
|
My first slack bot! by @vaiga | Stardance
|
vaiga
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @vaiga | Stardance
|
1793443742.6951592
|
1794048542.6951592
|
|
7875
|
Blackjack Calculator by @heian | Stardance
|
heian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Blackjack Calculator by @heian | Stardance
|
1792907435.4080193
|
1793771435.4080193
|
|
7877
|
Homemade Welder by @river | Stardance
|
river
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Homemade Welder by @river | Stardance
|
1793509015.7359579
|
1794113815.7359579
|
|
7878
|
HexZero by @kamix | Stardance
|
kamix
|
0
|
6.28
|
0
|
[]
|
[{"post_id": 10871, "ts": "202 [{"post_id": 10871, "ts": "2026-06-17T20:31:26Z", "hours": 2.8272, "text": "The bot now has a brain I just made a commit implementing the neural network, that will be used to guide the MCTS I created a few days ago. The role of the NN in AlphaZero is really huge - it takes in the current position and predicts the probability for each move to be played, and how good or bad the position is for the current player. As you can see from the screenshot, the NN is implemented in Python (PyTorch), but the MCTS is made in C++. You can probably guess it took quite a bit of time to get those two working together, but I think I got it under control. Next up is the training loop for the NN"}, {"post_id": 7981, "ts": "2026-06-13T09:48:55Z", "hours": 1.8531, "text": "The search engine for HexZero is complete! Over the last few days, I’ve been implementing Monte Carlo Tree Search, which is the algorithm AlphaZero uses to explore possible moves. Since HeXO has a two-move turns, I had to make some modifications from the original approach, but I think I finally got it working! With the C++ MCTS implementation complete, the next goal for the project is to make the neural network, that will guide the MCTS on which moves are worth exploring in the first place."}, {"post_id": 6360, "ts": "2026-06-10T18:19:13Z", "hours": 1.6028, "text": "Made some pretty good progress working on the training environment for my AlphaZero for HeXO today For those curious: AlphaZero is an ML program by DeepMind, that was able to master complex games like chess, go and shogi with no human input HeXO is a hexagonal tic-tac-toe variant, with a “connect 6” win condition"}]...
|
Title: HexZero by @kamix | Stardance
Devlogs:
Mad Title: HexZero by @kamix | Stardance
Devlogs:
Made some pretty good progress working on the training environment for my AlphaZero for HeXO today For those curious: AlphaZero is an ML program by DeepMind, that was able to master complex games like chess, go and shogi with no human input HeXO is a hexagonal tic-tac-toe variant, with a “connect 6” win condition
The search engine for HexZero is complete! Over the last few days, I’ve been implementing Monte Carlo Tree Search, which is the algorithm AlphaZero uses to explore possible moves. Since HeXO has a two-move turns, I had to make some modifications from the original approach, but I think I finally got it working! With the C++ MCTS implementation complete, the next goal for the project is to make the neural network, that will guide the MCTS on which moves are worth exploring in the first place.
The bot now has a brain I just made a commit implementing the neural network, that will be used to guide the MCTS I created a few days ago. The role of the NN in AlphaZero is really huge - it takes in the current position and predicts the probability for each move to be played, and how good or bad the position is for the current player. As you can see from the screenshot, the NN is implemented in Python (PyTorch), but the MCTS is made in C++. You can probably guess it took quite a bit of time to get those two working together, but I think I got it under control. Next up is the training loop for the NN...
|
1793317731.9786227
|
1793922531.9786227
|
|
7879
|
The Solar Electric Auto-Stabilized Glider by @Madh The Solar Electric Auto-Stabilized Glider by @Madhanraj | Stardance...
|
Madhanraj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The Solar Electric Auto-Stabilized Glider b Title: The Solar Electric Auto-Stabilized Glider by @Madhanraj | Stardance...
|
1792918469.1714187
|
1793782469.1714187
|
|
7881
|
Linesick DAW by @smatt | Stardance
|
smatt
|
0
|
0.73
|
0
|
[]
|
[{"post_id": 2882, "ts": "2026 [{"post_id": 2882, "ts": "2026-06-05T19:38:45Z", "hours": 0.7292, "text": "just set up everything (i think) for the project. it was pretty awkward, and i’m kind of afraid to ask for feedback, which is a shame, but i’ll get to it hopefully. i also hope nobody looks at the git commit history - i’ve written some things i’m not particularly proud of… :’D oh, also, nothing is working, well, besides the build. ;-;"}]...
|
Title: Linesick DAW by @smatt | Stardance
Devlogs Title: Linesick DAW by @smatt | Stardance
Devlogs:
just set up everything (i think) for the project. it was pretty awkward, and i’m kind of afraid to ask for feedback, which is a shame, but i’ll get to it hopefully. i also hope nobody looks at the git commit history - i’ve written some things i’m not particularly proud of… :’D oh, also, nothing is working, well, besides the build. ;-;...
|
1793534043.092626
|
1794138843.092626
|