|
30915
|
Character-level MLP language model by @Azwad | Sta Character-level MLP language model by @Azwad | Stardance...
|
Azwad
|
0
|
0.29
|
0
|
[]
|
[{"post_id": 22733, "ts": "202 [{"post_id": 22733, "ts": "2026-07-05T09:50:38Z", "hours": 0.2853, "text": "it is basically makemore part 4 graphs"}]...
|
Title: Character-level MLP language model by @Azwa Title: Character-level MLP language model by @Azwad | Stardance
Devlogs:
it is basically makemore part 4 graphs...
|
1793238865.3154955
|
1793843665.3154955
|
|
48690
|
My own site! by @Shubh311 | Stardance
|
Shubh311
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @Shubh311 | Stardance
|
1793238864.442269
|
1793843664.442269
|
|
48689
|
My awesome macropad! by @Jonathan_JoeStar | Starda My awesome macropad! by @Jonathan_JoeStar | Stardance...
|
Jonathan_JoeStar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Jonathan_JoeStar | Title: My awesome macropad! by @Jonathan_JoeStar | Stardance...
|
1793238863.5039103
|
1793843663.5039103
|
|
48688
|
My awesome macropad! by @MARIAPPAN | Stardance
|
MARIAPPAN
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @MARIAPPAN | Starda Title: My awesome macropad! by @MARIAPPAN | Stardance...
|
1793238862.6213615
|
1793843662.6213615
|
|
48686
|
Astral x by @chivessh | Stardance
|
chivessh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Astral x by @chivessh | Stardance
|
1793238861.7068884
|
1793843661.7068884
|
|
48685
|
My awesome macropad! by @chivessh | Stardance
|
chivessh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @chivessh | Stardan Title: My awesome macropad! by @chivessh | Stardance...
|
1793238860.8294225
|
1793843660.8294225
|
|
2265
|
Bean2Space (DIY Rocket) by @TGA25dev | Stardance
|
TGA25dev
|
0
|
44.29
|
0
|
[]
|
[{"post_id": 74447, "ts": "202 [{"post_id": 74447, "ts": "2026-09-27T12:09:07Z", "hours": 1.2717, "text": "Devlog # 15 What’s new ? Parachute ! I’ve worked an hour on the parachute design and I think it came pretty good, I’ve tested it from a very low altitude and it seems to work well so I’m pretty happy with it. It’s made out of a tyvek security suit and I’ve used nylon cables for the lines."}, {"post_id": 74412, "ts": "2026-09-27T10:36:40Z", "hours": 1.1864, "text": "Devlog #14.1 What’s new ? Nothing really important in this devlog tbh, again lot’s of tests in the code, debugging and trying new things (that didn’t worked..) I’ve also replaced the imu temperature value in the live telemetry by the mcu temperature because it’s a more important value to know and monitor. Cool things are coming! (like the parachute design )"}, {"post_id": 73492, "ts": "2026-09-25T07:23:31Z", "hours": 2.6869, "text": "Devlog #14 What’s new ? I’ve been working mainly on software those days, I had a few issues with the program running on battery, once it was started I couldn’t connect it again with the cable. To fix that I’ve added another main script that runs when the chip is powered on and adds a timer to et me interrupt boot sequence if needed. Then, I’ve worked on a collector for the ground station whose role is to grab the data of the other esp32 by serial and save it to a csv file (it can then be readed by the dashboard for example) Due to the collector needing a new telemetry parsing structure I’ve also updated how telemetry sequences are written and printed in the ground station main file Also, I’ve been doing some tests with the state detection algorithm to try if it detected well the different flight states (I literally threw the electronics in the air and almost smashed them on the ground, but it’s ok at least it worked well) See you for the next devlog!"}, {"post_id": 70864, "ts": "2026-09-19T21:49:22Z", "hours": 3.7017, "text": "Devlog #13 What’s new ? A lot of work today as I’ve finished the soldering part!! Now the flight computer is done and mounted into the 3D printed sled, it was my first time soldering like that and I think it came pretty decent (though cable management looks horrible to me). The only thing that didn’t work when I powered it was the led, I spent a long time trying to understand what was wrong to finally realize that I had fried it… I replaced it with a new one and the issue was solved! (also changed the color by the way) Appart from soldering I’ve also added a setting to disable buzzer or led on startup and an internal temperature watchdog to monitor the temperature and prevent the chip from overheating What’s next ? As I said earlier the project is almost finished! Yet I still need to add a few more features, fix some bugs and print the last parts"}, {"post_id": 70602, "ts": "2026-09-19T13:03:41Z", "hours": 3.0914, "text": "Devlog #12 Wow it’s really been a while since last devlog.. so ? What’s new ? Well I’ve been working on a dasboard for the rocket, it uses Streamlit to display data and gathers data from a csv file that is saved on the computer. csv file is written by a local script that uses serial to catch data from the ground station via usb-c I’ve also been improving CAD model a little bit, that includes fillets for the fins and modifications to the instruments rack Also fixed a bug where calibration offsets weren’t applied properly, optimized some code and tried a lot of things in the main script. What’s next ? Last week I’ve started soldering the components to the perfboard so Lapse devlog is coming very soon, I’m planning to finish this in a few days Once soldering is done I will test out the software in “real” conditions and print the missing parts of the rocket Stay tuned ! ✨"}, {"post_id": 55639, "ts": "2026-08-27T16:28:56Z", "hours": 4.0294, "text": "Devlog #11 What’s new? I initially planned on adding an SD Card module but after fighting with it for almost two hours I couldn’t get it to work, it uses SPI but I don’t know why it refused cooperate.. Then I improved the wireless transmission system by adding sequence numbers and the rocket state to the packets. Everything was working fine until it totally stopped working. I spent another hour trying to debug only to finally plug the external antenas into both ESPs which fixed the issue.. Finally I’ve moved the rocket state detection to a separate module so the main file remains clean and is easier to debug What’s next? Now that those issues are solved I’m going to create a nice dashboard I will run on my computer to display live data charts and logs, I don’t know how I’m going to design it but hopefully it will look great On the screenshot you can see on the left logs from the rocket and on the right the live data that is pulled from the ground station by serial connection."}, {"post_id": 53065, "ts": "2026-08-23T13:58:43Z", "hours": 1.4889, "text": "Devlog #10 What’s new ? First of all I now have the missing funds to complete the project, that’s pretty insane and I’m really happy and proud about it Second, I’v been working again on the external pods as the measurements for the camera were wrong and it didn’t fitted at all. I’m going to print that part to test it out but it should now be fixed."}, {"post_id": 47185, "ts": "2026-08-14T22:02:08Z", "hours": 3.4086, "text": "Devlog #9.2 What’s new ? Some tweaks on CAD README ! I’v spent quite a lot of time writing the readme file, hope it’s good! I’v added several sections with a lot of details and renders from Fusion."}, {"post_id": 41273, "ts": "2026-08-05T11:52:29Z", "hours": 0.4667, "text": "Devlog #9.1 What’s new ? I’v added a mount for the shock cord, I will put a screw and attach the cord to it. the screw will go in those holes. Both mounts will be printed separately and then glued with expoxy On the bottom of the engine stage I’v also added 4 holes to attach the cord to"}, {"post_id": 41245, "ts": "2026-08-05T10:25:58Z", "hours": 1.9014, "text": "Devlog #9 What’s new ? CAD: I’v updated the top cover of the trigger system box because the new fire button I’v chose needed a bigger hole Wirings: I’v made two schematics, one for the flight computer on wokwi and another for the trigger station on draw.io. Took me a bit of time to understand how to create both diagrams since it’s the first time I use those websites but I think it came pretty good. What’s nex ? First I’m gonna address some issues I’v seen on the design especially in the engine stage Then when it’s done I’ll double check my BOM file is correct and I will probably submit for funding"}, {"post_id": 40804, "ts": "2026-08-04T15:43:03Z", "hours": 4.6297, "text": "Devlog #8 What’s new ? This time I’v designed the component’s sled/rack: The sled will first slide in the main tube and then be attached using 4 M3 screws as you can see on both sides (I’ll also use 4 other screws to secure the soldering board on the rack itself.) I will then add heat inserts when building. On the other side of the sled the lipo battery will be secured using velcro straps. And on the middle I’v added 2 “windows” for cable management. As you can see I’v also added 3 holes (the triangle pattern) on the main tube, they’r static port holes and will be used to ensure the pressure inside the rocket is the same as outside (for the pressure sensor to get correct data) EDIT: I just realized I forgot to upload the screenshot showing that and now I can’t… What’s next ? I think I might now submit the project for funding as I am missing some critical pieces to build the rocket. I’ll also probably tweak some things in the design and log a few hours more. After than I will continue to code the flight computer. Stay tuned! 🚀"}, {"post_id": 38862, "ts": "2026-08-01T12:57:15Z", "hours": 5.9436, "text": "Devlog #7 What’s new ? I worked a lot on CAD for the past 10h of work, lot’s of headaches because of the pods (and because I forgot to hit record on lapse) but here’s what I made : It took me a lot of time to work on the pods because I couldn’t find a good aerodynamic design. So I designed it, re-designed it and re-re-redisigned it. Finally I have something working though it’s not perfect, I should tweak some things to make it even better. I also worked on designing the ground trigger system, basically it’s a box that will host the batteries to ignite the rocket, a security lock with a key and the fire button. It wasn’t very hard but it also took me a bit of time to find the correct diameters for the components. What’s next ? Well I think I will polish the designs perhaps add new things and fix some others, once thats done I will submit for funding to get the rest of the components I need. Stay tuned!"}, {"post_id": 27079, "ts": "2026-07-12T09:53:23Z", "hours": 1.1592, "text": "Devlog #6 What’s new ? The rocket has now a state tracking system, what this does is that it takes the altitude, calculates the velocity and then deduces the rocket’s state (iddle, in flight, descending etc etc..) It took me some time to understand how velocity could be used and calculated and I also had to implement smpoothing systems to prevent the noise from the sensors to give me weird values I’v also added a “demo mode”, it simulates fake telemetry (altitude) so I can test the status tracking system What’s next ? Well I don’t really know, I’v been strugling with live logs and I don’t really know how I could implement that, I’ll see what’s missing and what I can do to improve the rocket Below is a screenshot of the terminal’s output, because I’m not going to take another picture of the harware as nothing really changed.. I’ll try to do better next devlog!"}, {"post_id": 19365, "ts": "2026-06-30T17:17:45Z", "hours": 1.9311, "text": "Devlog #5 CAD!! Well so today I opened Fusion360 and entirely remodeled all the parts of the rocket. I had mesh files from OpenRocket but I needed to turn them into solid shapes. I will probably have to spend more time on Fusion because I’m not sure the shoulder for the main stage is well designed and will fit properly. Also, I might need to design something to keep the engine inside the tube so it doesn’t move."}, {"post_id": 16833, "ts": "2026-06-27T10:23:39Z", "hours": 1.815, "text": "Devlog #4 What’s new On each run the rocket is now assigned a random flight number for better identification (also added in transmitted packets, you’l see later why) Zombie connections are now killed before starting everything to prevent issues with unclosed sockets Clock chip frequency has been reduced (the esp is heating a lot I need to find why and fix the performances..) I’v added new telemetry packet flags to distinguish between telemetry and messages (I’ll probably forward live logs from the rocket to the ground station using that) What’s coming Well, pretty much everything I said before (performances, live logs, telemetry saving in csv files, charts..) Also going to try to start the CAD in Fusion360"}, {"post_id": 15646, "ts": "2026-06-25T13:22:40Z", "hours": 2.2681, "text": "Devlog #3 What’s new I was looking at the telemetry data and noticed relative pressure mesurement was uncorrect so I fixed it (took me a moment to understand why..) - Also fixed gyro x value calculation that was wrong Now the main chip broadcasts it’s telemetry so it can be read by the other chip on the ground I’v added new buttons to the dashboard to stop Wifi and start ESPNow transmission Anddd last but not least, the rocket has now an internal clock which is for now used as timestamp when packets are sent What’s on the picture The “ground station” (white cable) which is an ESP32 C3 My breadboard with all the components which will be in the rocket (just noticed buzzer cable was disconnected)"}, {"post_id": 15539, "ts": "2026-06-25T08:01:32Z", "hours": 1.2831, "text": "Devlog #2 What’s new I’v started working on live wireless transmission so I could have live data transmission from the rocket to a ground station (another ESP32). I can now broadcast data from the rocket and it’s read by the ground station. I’v added new options on the dashboard, I can now remotely start the calibration process – it will be useful on ground before the launch And now ? Now I am going to improve the dashboard by addind new options and probably telemetry Probably going to cleanup some code and put things in other files for better readability"}, {"post_id": 12518, "ts": "2026-06-20T13:17:26Z", "hours": 2.0281, "text": "1st devlog! Made basic CAD in OpenRocket software to design the rocket’s body and fins. It helped me understanding how aerodynamics will affect the rocket during the flight Started the software part, I use Python paired with a XIAO ESP32 S3 as main flight computer. I also have a BMP280 and an MPU6050 as main flight instruments. I’v added getter functions for telemetry and setters for calibration. Also added the main file with a startup function and wifi manager for wireless ground control."}]...
|
Title: Bean2Space (DIY Rocket) by @TGA25dev | Star Title: Bean2Space (DIY Rocket) by @TGA25dev | Stardance
Devlogs:
1st devlog! Made basic CAD in OpenRocket software to design the rocket’s body and fins. It helped me understanding how aerodynamics will affect the rocket during the flight Started the software part, I use Python paired with a XIAO ESP32 S3 as main flight computer. I also have a BMP280 and an MPU6050 as main flight instruments. I’v added getter functions for telemetry and setters for calibration. Also added the main file with a startup function and wifi manager for wireless ground control.
Devlog #2 What’s new I’v started working on live wireless transmission so I could have live data transmission from the rocket to a ground station (another ESP32). I can now broadcast data from the rocket and it’s read by the ground station. I’v added new options on the dashboard, I can now remotely start the calibration process – it will be useful on ground before the launch And now ? Now I am going to improve the dashboard by addind new options and probably telemetry Probably going to cleanup some code and put things in other files for better readability
Devlog #3 What’s new I was looking at the telemetry data and noticed relative pressure mesurement was uncorrect so I fixed it (took me a moment to understand why..) - Also fixed gyro x value calculation that was wrong Now the main chip broadcasts it’s telemetry so it can be read by the other chip on the ground I’v added new buttons to the dashboard to stop Wifi and start ESPNow transmission Anddd last but not least, the rocket has now an internal clock which is for now used as timestamp when packets are sent What’s on the picture The “ground station” (white cable) which is an ESP32 C3 My breadboard with all the components which will be in the rocket (just noticed buzzer cable was disconnected)
Devlog #4 What’s new On each run the rocket is now assigned a random flight number for better identification (also added in transmitted packets, you’l see later why) Zombie connections are now killed before starting everything to prevent issues with unclosed sockets Clock chip frequency has been reduced (the esp is heating a lot I need to find why and fix the performances..) I’v added new telemetry packet flags to distinguish between telemetry and messages (I’ll probably forward live logs from the rocket to the ground station using that) What’s coming Well, pretty much everything I said before (performances, live logs, telemetry saving in csv files, charts..) Also going to try to start the CAD in Fusion360
Devlog #5 CAD!! Well so today I opened Fusion360 and entirely remodeled all the parts of the rocket. I had mesh files from OpenRocket but I needed to turn them into solid shapes. I will probably have to spend more time on Fusion because I’m not sure the shoulder for the main stage is well designed and will fit properly. Also, I might need to design something to keep the engine inside the tube so it doesn’t move.
Devlog #6 What’s new ? The rocket has now a state tracking system, what this does is that it takes the altitude, calculates the velocity and then deduces the rocket’s state (iddle, in flight, descending etc etc..) It took me some time to understand how velocity could be used and calculated and I also had to implement smpoothing systems to prevent the noise from the sensors to give me weird values I’v also added a “demo mode”, it simulates fake telemetry (altitude) so I can test the status tracking system What’s next ? Well I don’t really know, I’v been strugling with live logs and I don’t really know how I could implement that, I’ll see what’s missing and what I can do to improve the rocket Below is a screenshot of the terminal’s output, because I’m not going to take another picture of the harware as nothing really changed.. I’ll try to do better next devlog!
Devlog #7 What’s new ? I worked a lot on CAD for the past 10h of work, lot’s of headaches because of the pods (and because I forgot to hit record on lapse) but here’s what I made : It took me a lot of time to work on the pods because I couldn’t find a good aerodynamic design. So I designed it, re-designed it and re-re-redisigned it. Finally I have something working though it’s not perfect, I should tweak some things to make it even better. I also worked on designing the ground trigger system, basically it’s a box that will host the batteries to ignite the rocket, a security lock with a key and the fire button. It wasn’t very hard but it also took me a bit of time to find the correct diameters for the components. What’s next ? Well I think I will polish the designs perhaps add new things and fix some others, once thats done I will submit for funding to get the rest of the components I need. Stay tuned!
Devlog #8 What’s new ? This time I’v designed the component’s sled/rack: The sled will first slide in the main tube and then be attached using 4 M3 screws as you can see on both sides (I’ll also use 4 other screws to secure the soldering board on the rack itself.) I will then add heat inserts when building. On the other side of the sled the lipo battery will be secured using velcro straps. And on the middle I’v added 2 “windows” for cable management. As you can see I’v also added 3 holes (the triangle pattern) on the main tube, they’r static port holes and will be used to ensure the pressure inside the rocket is the same as outside (for the pressure sensor to get correct data) EDIT: I just realized I forgot to upload the screenshot showing that and now I can’t… What’s next ? I think I might now submit the project for funding as I am missing some critical pieces to build the rocket. I’ll also probably tweak some things in the design and log a few hours more. After than I will continue to code the flight computer. Stay tuned! 🚀
Devlog #9 What’s new ? CAD: I’v updated the top cover of the trigger system box because the new fire button I’v chose needed a bigger hole Wirings: I’v made two schematics, one for the flight computer on wokwi and another for the trigger station on draw.io. Took me a bit of time to understand how to create both diagrams since it’s the first time I use those websites but I think it came pretty good. What’s nex ? First I’m gonna address some issues I’v seen on the design especially in the engine stage Then when it’s done I’ll double check my BOM file is correct and I will probably submit for funding
Devlog #9.1 What’s new ? I’v added a mount for the shock cord, I will put a screw and attach the cord to it. the screw will go in those holes. Both mounts will be printed separately and then glued with expoxy On the bottom of the engine stage I’v also added 4 holes to attach the cord to
Devlog #9.2 What’s new ? Some tweaks on CAD README ! I’v spent quite a lot of time writing the readme file, hope it’s good! I’v added several sections with a lot of details and renders from Fusion.
Devlog #10 What’s new ? First of all I now have the missing funds to complete the project, that’s pretty insane and I’m really happy and proud about it Second, I’v been working again on the external pods as the measurements for the camera were wrong and it didn’t fitted at all. I’m going to print that part to test it out but it should now be fixed.
Devlog #11 What’s new? I initially planned on adding an SD Card module but after fighting with it for almost two hours I couldn’t get it to work, it uses SPI but I don’t know why it refused cooperate.. Then I improved the wireless transmission system by adding sequence numbers and the rocket state to the packets. Everything was working fine until it totally stopped working. I spent another hour trying to debug only to finally plug the external antenas into both ESPs which fixed the issue.. Finally I’ve moved the rocket state detection to a separate module so the main file remains clean and is easier to debug What’s next? Now that those issues are solved I’m going to create a nice dashboard I will run on my computer to display live data charts and logs, I don’t know how I’m going to design it but hopefully it will look great On the screenshot you can see on the left logs from the rocket and on the right the live data that is pulled from the ground station by serial connection.
Devlog #12 Wow it’s really been a while since last devlog.. so ? What’s new ? Well I’ve been working on a dasboard for the rocket, it uses Streamlit to display data and gathers data from a csv file that is saved on the computer. csv file is written by a local script that uses serial to catch data from the ground station via usb-c I’ve also been improving CAD model a little bit, that includes fillets for the fins and modifications to the instruments rack Also fixed a bug where calibration offsets weren’t applied properly, optimized some code and tried a lot of things in the main script. What’s next ? Last week I’ve started soldering the components to the perfboard so Lapse devlog is coming very soon, I’m planning to finish this in a few days Once soldering is done I will test out the software in “real” conditions and print the missing parts of the rocket Stay tuned ! ✨
Devlog #13 What’s new ? A lot of work today as I’ve finished the soldering part!! Now the flight computer is done and mounted into the 3D printed sled, it was my first time soldering like that and I think it came pretty decent (though cable management looks horrible to me). The only thing that didn’t work when I powered it was the led, I spent a long time trying to understand what was wrong to finally realize that I had fried it… I replaced it with a new one and the issue was solved! (also changed the color by the way) Appart from soldering I’ve also added a setting to disable buzzer or led on startup and an internal temperature watchdog to monitor the temperature and prevent the chip from overheating What’s next ? As I said earlier the project is almost finished! Yet I still need to add a few more features, fix some bugs and print the last parts
Devlog #14 What’s new ? I’ve been working mainly on software those days, I had a few issues with the program running on battery, once it was started I couldn’t connect it again with the cable. To fix that I’ve added another main script that runs when the chip is powered on and adds a timer to et me interrupt boot sequence if needed. Then, I’ve worked on a collector for the ground station whose role is to grab the data of the other esp32 by serial and save it to a csv file (it can then be readed by the dashboard for example) Due to the collector needing a new telemetry parsing structure I’ve also updated how telemetry sequences are written and printed in the ground station main file Also, I’ve been doing some tests with the state detection algorithm to try if it detected well the different flight states (I literally threw the electronics in the air and almost smashed them on the ground, but it’s ok at least it worked well) See you for the next devlog!
Devlog #14.1 What’s new ? Nothing really important in this devlog tbh, again lot’s of tests in the code, debugging and trying new things (that didn’t worked..) I’ve also replaced the imu temperature value in the live telemetry by the mcu temperature because it’s a more important value to know and monitor. Cool things are coming! (like the parachute design )
Devlog # 15 What’s new ? Parachute ! I’ve worked an hour on the parachute design and I think it came pretty good, I’ve tested it from a very low altitude and it seems to work well so I’m pretty happy with it. It’s made out of a tyvek security suit and I’ve used nylon cables for the lines....
|
1793238859.5300665
|
1793843659.5300665
|
|
48684
|
Frictionless by @abuesai | Stardance
|
abuesai
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @abuesai | Stardance
|
1793238858.5924447
|
1793843658.5924447
|
|
31202
|
80s themed photobooth by @lozza | Stardance
|
lozza
|
0
|
2.79
|
0
|
[]
|
[{"post_id": 26368, "ts": "202 [{"post_id": 26368, "ts": "2026-07-11T03:36:58Z", "hours": 2.0531, "text": "I have made a basic outline of the functioning parts of the photobooth. I do not know why it took so long to make. Next steps is to refine the functioning parts of the photobooth (buttons and structure), before designing/implementing the 80s aspect of the photobooth."}, {"post_id": 23412, "ts": "2026-07-06T10:57:15Z", "hours": 0.7408, "text": "The start of something new -"}]...
|
Title: 80s themed photobooth by @lozza | Stardance Title: 80s themed photobooth by @lozza | Stardance
Devlogs:
The start of something new -
I have made a basic outline of the functioning parts of the photobooth. I do not know why it took so long to make. Next steps is to refine the functioning parts of the photobooth (buttons and structure), before designing/implementing the 80s aspect of the photobooth....
|
1793238857.689083
|
1793843657.689083
|
|
48683
|
Frictionless by @Liann | Stardance
|
Liann
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @Liann | Stardance
|
1793238856.807342
|
1793843656.807342
|
|
48682
|
My own site! by @moulipraful | Stardance
|
moulipraful
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @moulipraful | Stardance
|
1793238855.927303
|
1793843655.927303
|
|
5598
|
My awesome macropad! by @ethankow | Stardance
|
ethankow
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ethankow | Stardan Title: My awesome macropad! by @ethankow | Stardance...
|
1793238855.032759
|
1793843655.032759
|
|
48681
|
My awesome macropad! by @Ayushrana | Stardance
|
Ayushrana
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Ayushrana | Starda Title: My awesome macropad! by @Ayushrana | Stardance...
|
1793238854.134263
|
1793843654.134263
|
|
48680
|
My awesome macropad! by @AaromalPanicker | Stardan My awesome macropad! by @AaromalPanicker | Stardance...
|
AaromalPanicker
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @AaromalPanicker | Title: My awesome macropad! by @AaromalPanicker | Stardance...
|
1793238853.1515615
|
1793843653.1515615
|
|
13830
|
My awesome macropad! by @Mxhi | Stardance
|
Mxhi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Mxhi | Stardance
|
1793238850.225443
|
1793843650.225443
|
|
21672
|
Untitled by @Ak_45 | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Ak_45 | Stardance
|
1793238847.8438506
|
1793843647.8438506
|
|
48679
|
My own site! by @NewItzzFlame | Stardance
|
NewItzzFlame
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @NewItzzFlame | Stardance
|
1793238846.9663548
|
1793843646.9663548
|
|
17252
|
My first slack bot! by @sougata | Stardance
|
sougata
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @sougata | Stardance
|
1793238846.060074
|
1793843646.060074
|
|
48678
|
My own site! by @kendralegrand | Stardance
|
kendralegrand
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @kendralegrand | Stardance
|
1793238845.1623209
|
1793843645.1623209
|
|
48677
|
A hospital registration by @shriyansh08 | Stardanc A hospital registration by @shriyansh08 | Stardance...
|
shriyansh08
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A hospital registration by @shriyansh08 | S Title: A hospital registration by @shriyansh08 | Stardance...
|
1793238844.2760174
|
1793843644.2760174
|
|
48676
|
My own site! by @sparklingwater | Stardance
|
sparklingwater
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @sparklingwater | Stardance
|
1793238841.7136772
|
1793843641.7136772
|
|
26474
|
DesicCat by @salmorejo | Stardance
|
salmorejo
|
0
|
46.88
|
0
|
[]
|
[{"post_id": 34850, "ts": "202 [{"post_id": 34850, "ts": "2026-07-25T21:41:32Z", "hours": 2.4597, "text": "Devlog 5: Hardware test Just a quick update. I’ve created this test PCB that has everything integrated; it works correctly, and I haven’t detected any errors in it or in the code during testing. However, the results are rather disappointing… The chamber doesn’t reach the target temperature within the required time. I’ve concluded that to fix this, I need to change how the heat is generated and distributed. I’ll have an update soon on how I’m going to redesign it."}, {"post_id": 33109, "ts": "2026-07-22T18:46:59Z", "hours": 23.57, "text": "Devlog 4: Final touches to the software (fr this time) First of all, here’s the GitHub repository for you to check out. I’m finally happy with the code, and now I’m going to move to the CAD design. It’s been a while since I posted a devlog because I wanted to have it almost finished before doing so. Since I’m doing a speedrun and want to finish this as soon as possible (there are some interesting new projects coming up 👀), I’m going to give a quick recap: Now the interface automatically detects if it’s in DEMO mode by checking whether you’re on the GitHub link or if the URL includes ?demo. The physical version is fully operational, and I’m already testing it in real-world scenarios (it’s not ready to show off yet). It now detects your browser’s language and adjusts automatically (it’s only in English and Spanish, and, ngl ,it’s done with AI) and you can configure the lenguage in the code. Fixed some minor bugs and improved the overall experience. There’s now a functional GitHub page (I think) with a README in progress. Another important point is that there were no security measures. Now it detects sensor failures, thermal runaways, as well as hardcoded blocks and unusual backend traffic. Both the web version and the offline version detect these issues. These are basic measures, but they’re quite necessary. I’ve done some testing with cat litter, and it has potential. I still have to finish the README and all the parts, but I’m getting closer and closer to shipping it. For the next devlog, I’ll show a physical test of how it works. P.S.: I hope you like DesicCat (it’s a mix of “desiccant” and “cat”, in case you didn’t get it ), and I PROMISE you that the images aren’t AI-generated, I actually made them myself, but I lowkey suck at graphical design."}, {"post_id": 25357, "ts": "2026-07-09T16:28:43Z", "hours": 14.8467, "text": "Devlog 3: Final touches to the software I’ve finished the part I like the least (I like them all, but this is the one I like the least ), which is the programming and getting everything ready to tackle the most interesting part of the hardware. I’ve been pretty busy these past few days, so I’ve made only minor progress, but I finally finished the following: The interface is now much nicer and easier to understand, since the structure has been completely overhauled and the design has been streamlined (Claude might have had something to do with that ). Now with 🆒 graphs! I’ve reviewed the code for the ESP32 and fixed some security issues related to Wi-Fi credentials. I’ve also optimized some parts responsible for handling the web interface data, with a little help since I’d never done this before. Now, since the web interface is much more resource-intensive, it’s not directly embedded in the C++ code that’s compiled onto the ESP32, which saves memory and frees up space for other, more important processes. Here’s an example of how I’ve been doing it so far: //Cpp stuff// const char HTML_PAGE[] PROGMEM = R\"rawhtml( <!DOCTYPE html><html> <title>Amazing HTML page</title> <body> <h1>Incredible Title</h1> <p>Wonderful Paragraph.</p> </body> </html> )rawhtml; //Rest of the code// Now, instead, I have the three files: index.html, style.css, and scrypt.js, and I use PlatformIO (the same tool used for Marlin firmware on 3D printers ) to save them directly to the ESP32 without needing to compile them with the rest of the code. There is now also an offline version. The ESP32 tries to connect to the last Wi-Fi network it was connected to, and if that network doesn’t exist or it’s the first time it’s connecting, you can enter new credentials. If it goes a certain amount of time without connecting to any network, it switches to offline mode and is controlled entirely by hardware. To complete the project (or at least the items on my to-do list) I need to do the following: Demonstrate a proof of concept showing how the cat litter is used in the project (which is one of the project’s key features, and I haven’t done anything with it yet ) Write a proper README to make it easier to use Make the GitHub repository public so you can test it Make the hardware even easier to use by reducing the controls to two buttons Design the parts to be printed and put everything together I think that’s it… I’m going to keep doing it my own way until I finish it, but if anyone is interested, I’d be happy to tell them or do whatever they ask of me!"}, {"post_id": 17903, "ts": "2026-06-28T20:47:17Z", "hours": 4.2569, "text": "Optimization and interface upgrades Just minor changes. I’ve tried to change the interface, but I’m very inexperienced with HTML, so it might just stay the way it was. I’m probably going to focus on the project itself; creating a good interface is NOT my strength. 🥶 -Code: 65% -Hardware: 20%"}, {"post_id": 17262, "ts": "2026-06-27T23:52:45Z", "hours": 1.7508, "text": "Preliminary tests and other initial steps The idea is fully developed and it’s all in my head; now I just need to bring it to life… So far, I’ve only run a few physical tests on the ESP32, identifying some bugs that I’ll have to fix. The web interface is fully operational and bug-free, but it needs to be improved to make it more visually appealing. All the logic seems correct, but there are still some security vulnerabilities. -Code: 65% -Hardware: 20%"}]...
|
Title: DesicCat by @salmorejo | Stardance
Devlogs Title: DesicCat by @salmorejo | Stardance
Devlogs:
Preliminary tests and other initial steps The idea is fully developed and it’s all in my head; now I just need to bring it to life… So far, I’ve only run a few physical tests on the ESP32, identifying some bugs that I’ll have to fix. The web interface is fully operational and bug-free, but it needs to be improved to make it more visually appealing. All the logic seems correct, but there are still some security vulnerabilities. -Code: 65% -Hardware: 20%
Optimization and interface upgrades Just minor changes. I’ve tried to change the interface, but I’m very inexperienced with HTML, so it might just stay the way it was. I’m probably going to focus on the project itself; creating a good interface is NOT my strength. 🥶 -Code: 65% -Hardware: 20%
Devlog 3: Final touches to the software I’ve finished the part I like the least (I like them all, but this is the one I like the least ), which is the programming and getting everything ready to tackle the most interesting part of the hardware. I’ve been pretty busy these past few days, so I’ve made only minor progress, but I finally finished the following: The interface is now much nicer and easier to understand, since the structure has been completely overhauled and the design has been streamlined (Claude might have had something to do with that ). Now with 🆒 graphs! I’ve reviewed the code for the ESP32 and fixed some security issues related to Wi-Fi credentials. I’ve also optimized some parts responsible for handling the web interface data, with a little help since I’d never done this before. Now, since the web interface is much more resource-intensive, it’s not directly embedded in the C++ code that’s compiled onto the ESP32, which saves memory and frees up space for other, more important processes. Here’s an example of how I’ve been doing it so far: //Cpp stuff// const char HTML_PAGE[] PROGMEM = R"rawhtml( <!DOCTYPE html><html> <title>Amazing HTML page</title> <body> <h1>Incredible Title</h1> <p>Wonderful Paragraph.</p> </body> </html> )rawhtml; //Rest of the code// Now, instead, I have the three files: index.html, style.css, and scrypt.js, and I use PlatformIO (the same tool used for Marlin firmware on 3D printers ) to save them directly to the ESP32 without needing to compile them with the rest of the code. There is now also an offline version. The ESP32 tries to connect to the last Wi-Fi network it was connected to, and if that network doesn’t exist or it’s the first time it’s connecting, you can enter new credentials. If it goes a certain amount of time without connecting to any network, it switches to offline mode and is controlled entirely by hardware. To complete the project (or at least the items on my to-do list) I need to do the following: Demonstrate a proof of concept showing how the cat litter is used in the project (which is one of the project’s key features, and I haven’t done anything with it yet ) Write a proper README to make it easier to use Make the GitHub repository public so you can test it Make the hardware even easier to use by reducing the controls to two buttons Design the parts to be printed and put everything together I think that’s it… I’m going to keep doing it my own way until I finish it, but if anyone is interested, I’d be happy to tell them or do whatever they ask of me!
Devlog 4: Final touches to the software (fr this time) First of all, here’s the GitHub repository for you to check out. I’m finally happy with the code, and now I’m going to move to the CAD design. It’s been a while since I posted a devlog because I wanted to have it almost finished before doing so. Since I’m doing a speedrun and want to finish this as soon as possible (there are some interesting new projects coming up 👀), I’m going to give a quick recap: Now the interface automatically detects if it’s in DEMO mode by checking whether you’re on the GitHub link or if the URL includes ?demo. The physical version is fully operational, and I’m already testing it in real-world scenarios (it’s not ready to show off yet). It now detects your browser’s language and adjusts automatically (it’s only in English and Spanish, and, ngl ,it’s done with AI) and you can configure the lenguage in the code. Fixed some minor bugs and improved the overall experience. There’s now a functional GitHub page (I think) with a README in progress. Another important point is that there were no security measures. Now it detects sensor failures, thermal runaways, as well as hardcoded blocks and unusual backend traffic. Both the web version and the offline version detect these issues. These are basic measures, but they’re quite necessary. I’ve done some testing with cat litter, and it has potential. I still have to finish the README and all the parts, but I’m getting closer and closer to shipping it. For the next devlog, I’ll show a physical test of how it works. P.S.: I hope you like DesicCat (it’s a mix of “desiccant” and “cat”, in case you didn’t get it ), and I PROMISE you that the images aren’t AI-generated, I actually made them myself, but I lowkey suck at graphical design.
Devlog 5: Hardware test Just a quick update. I’ve created this test PCB that has everything integrated; it works correctly, and I haven’t detected any errors in it or in the code during testing. However, the results are rather disappointing… The chamber doesn’t reach the target temperature within the required time. I’ve concluded that to fix this, I need to change how the heat is generated and distributed. I’ll have an update soon on how I’m going to redesign it....
|
1793238840.4663973
|
1793843640.4663973
|
|
27073
|
OpenStatusPage by @samthedevde | Stardance
|
samthedevde
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: OpenStatusPage by @samthedevde | Stardance
|
1793238839.6020608
|
1793843639.6020608
|
|
27953
|
Project Med by @manayp | Stardance
|
manayp
|
0
|
9.69
|
0
|
[]
|
[{"post_id": 26108, "ts": "202 [{"post_id": 26108, "ts": "2026-07-10T18:12:20Z", "hours": 0.3339, "text": "Fixed few issues (minor)"}, {"post_id": 19769, "ts": "2026-07-01T04:50:00Z", "hours": 2.2506, "text": "I fixed and tested a bunch of stuff until I asked Claude to fix one sizing issue, but instead it changed everything, which was a huge issue but I fixed it. Then the graphs (especially the mini ones) were super squashed so that had to be fixed too. The README is finally done because I added screenshots and acknowledgements. The UI looks great despite some issues."}, {"post_id": 19635, "ts": "2026-07-01T00:35:24Z", "hours": 3.2928, "text": "Currently I finished the website overall but testing it has been a headache because it is not running and the screen is white… I tried to resolve this with Claude, Github Copilot, and EVEN Chatgpt but none of them could really figure out whats going on so I think it is because of my browsing system so I will need to figure something out. I also worked on my README and completed it ALMOST."}, {"post_id": 18928, "ts": "2026-06-30T03:18:23Z", "hours": 0.3375, "text": "I built a good enough logo using Canva for my product and I also tested the product and found out that there was a LOT of errors and I am going to fix it now in upcoming recordings so STAY TUNED. Plus I added stimulated data for testing."}, {"post_id": 18896, "ts": "2026-06-30T02:54:24Z", "hours": 0.6517, "text": "Claude also helped me a lot and so did Github Copilot: CSS Variables — I set up –primary and other custom variables at the top of the file so I can change one color in one place and have it update everywhere. No more hunting through 50 random lines.100vh — For the activation screen, I used min-height: 100vh so it always fills the full screen height. vh just means “viewport height,” so 100vh = the whole screen.em and rem — When I used em, it scales based on the parent’s font size (like 1em = same size, 1.5em = 1.5× bigger). rem is more predictable because it always uses the root font size instead of the parent.inline-block — I used inline-block for elements that needed to sit next to each other but still have proper width and height. It’s basically the middle ground between inline and block.Flexbox — I used flexbox to lay things out cleanly in rows or columns, like the stat cards and the nav tabs. Way easier than messing with floats.CSS classes for show/hide — Instead of writing display: none in JavaScript everywhere, I just toggled a .hidden class. CSS handles the hiding, JS just switches the class.Activation screen background color — I can change the activation screen’s background by setting background-color on #activation-screen or .overlay in the CSS. I can make it any color or even a gradient. THERE was a lot of errors when I was typing but that was fixed. A big thing is that I also used OneCompilor tool which helped me compile my code and test it before showing it to claude which approved or disapproved it and then I carried on from there."}, {"post_id": 18866, "ts": "2026-06-30T02:03:18Z", "hours": 1.5356, "text": "You have covered topics such as the concept of the IIFE and how it must be enclosed, the distinction between null and 0, what exactly linearSlope, stdDev, classifyTrend and analyzeEntries do, and how Groq API relates to your application through the web browser via your API key. You spotted and corrected some bugs, including the issue with duplicate IDs, typographical error such as entried vs entries, and the discrepancy between escapeHtml and escapeHTML. You came up with your own designs of < 35 || > 42 for flagging temperatures and 40-180 for heart rate, as well as AI safety rules. Not bad for one session! I was a bit confused in a bunch of aspect but that’s fine because Claude and Github Copilot helped a lot and really changed my way of coding and it also taught me stuff like Standard Deviation and moreee."}, {"post_id": 18762, "ts": "2026-06-29T23:22:34Z", "hours": 1.2917, "text": "I am working on the Html and JS part of my project and my goal is basically to make a medical device with hardware to help people with ai insights but currently I am doing the coding and trying to put stimulated data and more."}]...
|
Title: Project Med by @manayp | Stardance
Devlogs Title: Project Med by @manayp | Stardance
Devlogs:
I am working on the Html and JS part of my project and my goal is basically to make a medical device with hardware to help people with ai insights but currently I am doing the coding and trying to put stimulated data and more.
You have covered topics such as the concept of the IIFE and how it must be enclosed, the distinction between null and 0, what exactly linearSlope, stdDev, classifyTrend and analyzeEntries do, and how Groq API relates to your application through the web browser via your API key. You spotted and corrected some bugs, including the issue with duplicate IDs, typographical error such as entried vs entries, and the discrepancy between escapeHtml and escapeHTML. You came up with your own designs of < 35 || > 42 for flagging temperatures and 40-180 for heart rate, as well as AI safety rules. Not bad for one session! I was a bit confused in a bunch of aspect but that’s fine because Claude and Github Copilot helped a lot and really changed my way of coding and it also taught me stuff like Standard Deviation and moreee.
Claude also helped me a lot and so did Github Copilot: CSS Variables — I set up –primary and other custom variables at the top of the file so I can change one color in one place and have it update everywhere. No more hunting through 50 random lines.100vh — For the activation screen, I used min-height: 100vh so it always fills the full screen height. vh just means “viewport height,” so 100vh = the whole screen.em and rem — When I used em, it scales based on the parent’s font size (like 1em = same size, 1.5em = 1.5× bigger). rem is more predictable because it always uses the root font size instead of the parent.inline-block — I used inline-block for elements that needed to sit next to each other but still have proper width and height. It’s basically the middle ground between inline and block.Flexbox — I used flexbox to lay things out cleanly in rows or columns, like the stat cards and the nav tabs. Way easier than messing with floats.CSS classes for show/hide — Instead of writing display: none in JavaScript everywhere, I just toggled a .hidden class. CSS handles the hiding, JS just switches the class.Activation screen background color — I can change the activation screen’s background by setting background-color on #activation-screen or .overlay in the CSS. I can make it any color or even a gradient. THERE was a lot of errors when I was typing but that was fixed. A big thing is that I also used OneCompilor tool which helped me compile my code and test it before showing it to claude which approved or disapproved it and then I carried on from there.
I built a good enough logo using Canva for my product and I also tested the product and found out that there was a LOT of errors and I am going to fix it now in upcoming recordings so STAY TUNED. Plus I added stimulated data for testing.
Currently I finished the website overall but testing it has been a headache because it is not running and the screen is white… I tried to resolve this with Claude, Github Copilot, and EVEN Chatgpt but none of them could really figure out whats going on so I think it is because of my browsing system so I will need to figure something out. I also worked on my README and completed it ALMOST.
I fixed and tested a bunch of stuff until I asked Claude to fix one sizing issue, but instead it changed everything, which was a huge issue but I fixed it. Then the graphs (especially the mini ones) were super squashed so that had to be fixed too. The README is finally done because I added screenshots and acknowledgements. The UI looks great despite some issues.
Fixed few issues (minor)...
|
1793238838.4229524
|
1793843638.4229524
|
|
48674
|
Python project 1 by @saatvik_270211 | Stardance
|
saatvik_270211
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Python project 1 by @saatvik_270211 | Stard Title: Python project 1 by @saatvik_270211 | Stardance...
|
1793238837.5252264
|
1793843637.5252264
|
|
24421
|
My awesome macropad! by @ivannaa | Stardance
|
ivannaa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ivannaa | Stardanc Title: My awesome macropad! by @ivannaa | Stardance...
|
1793238836.6479516
|
1793843636.6479516
|
|
48673
|
Frictionless by @jaykartheek | Stardance
|
jaykartheek
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @jaykartheek | Stardance
|
1793238835.7653968
|
1793843635.7653968
|
|
600
|
BambuCast by @PianoMan0 | Stardance
|
PianoMan0
|
0
|
1.41
|
0
|
[]
|
[{"post_id": 24997, "ts": "202 [{"post_id": 24997, "ts": "2026-07-08T22:01:36Z", "hours": 1.4097, "text": "Just posting this to get my payout"}]...
|
Title: BambuCast by @PianoMan0 | Stardance
Devlog Title: BambuCast by @PianoMan0 | Stardance
Devlogs:
Just posting this to get my payout...
|
1793238834.8343585
|
1793843634.8343585
|
|
48672
|
My awesome macropad! by @Devanshladha | Stardance
|
Devanshladha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Devanshladha | Sta Title: My awesome macropad! by @Devanshladha | Stardance...
|
1793238833.93402
|
1793843633.93402
|
|
8307
|
Maia Chess Bot by @magic_ | Stardance
|
magic_
|
0
|
0.5
|
0
|
[]
|
[{"post_id": 5212, "ts": "2026 [{"post_id": 5212, "ts": "2026-06-08T22:26:48Z", "hours": 0.5033, "text": "1st devlog - Used AI to create a baseplate for the chess bot. Includes: Chess, including special moves, bitboards, legal move generator, and a bot that plays randomized moves. Also made a github workflow for automating releases."}]...
|
Title: Maia Chess Bot by @magic_ | Stardance
Devl Title: Maia Chess Bot by @magic_ | Stardance
Devlogs:
1st devlog - Used AI to create a baseplate for the chess bot. Includes: Chess, including special moves, bitboards, legal move generator, and a bot that plays randomized moves. Also made a github workflow for automating releases....
|
1793238833.0190706
|
1793843633.0190706
|
|
15084
|
My very own WebOS by @Jude | Stardance
|
Jude
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Jude | Stardance
|
1793238832.1187203
|
1793843632.1187203
|
|
48671
|
My first slack bot! by @kitty | Stardance
|
kitty
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @kitty | Stardance
|
1793238831.1943004
|
1793843631.1943004
|
|
48670
|
My very own WebOS by @Rijan | Stardance
|
Rijan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Rijan | Stardance
|
1793238830.2653806
|
1793843630.2653806
|
|
48669
|
My own site! by @vercelapp105 | Stardance
|
vercelapp105
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @vercelapp105 | Stardance
|
1793238829.3752599
|
1793843629.3752599
|
|
48668
|
ASC II Font creator by @hacker123 | Stardance
|
hacker123
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ASC II Font creator by @hacker123 | Stardan Title: ASC II Font creator by @hacker123 | Stardance...
|
1793238828.4852467
|
1793843628.4852467
|
|
48667
|
My awesome macropad! by @Anvesh | Stardance
|
Anvesh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Anvesh | Stardance
|
1793238827.5758615
|
1793843627.5758615
|
|
38395
|
My own site! by @bilisaassefa | Stardance
|
bilisaassefa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @bilisaassefa | Stardance
|
1793238826.6772084
|
1793843626.6772084
|
|
48666
|
My awesome macropad! by @ivoriacy | Stardance
|
ivoriacy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ivoriacy | Stardan Title: My awesome macropad! by @ivoriacy | Stardance...
|
1793238825.7605739
|
1793843625.7605739
|
|
48664
|
Frictionless by @visheshpawar | Stardance
|
visheshpawar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @visheshpawar | Stardance
|
1793238824.8496888
|
1793843624.8496888
|
|
16895
|
Youtube Subscriber Count by @shaur1021 | Stardance
|
shaur1021
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Youtube Subscriber Count by @shaur1021 | St Title: Youtube Subscriber Count by @shaur1021 | Stardance...
|
1793238823.9714942
|
1793843623.9714942
|
|
48663
|
DIY Simple Speaker by @vik | Stardance
|
vik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DIY Simple Speaker by @vik | Stardance
|
1793238823.075902
|
1793843623.075902
|
|
4266
|
My first slack bot! by @noxi | Stardance
|
noxi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @noxi | Stardance
|
1793238822.1795123
|
1793843622.1795123
|
|
21648
|
My first slack bot! by @aaryav_naruto | Stardance
|
aaryav_naruto
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @aaryav_naruto | Sta Title: My first slack bot! by @aaryav_naruto | Stardance...
|
1793238821.2925568
|
1793843621.2925568
|
|
48662
|
DragonPad by @NamelessGuy69 | Stardance
|
NamelessGuy69
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DragonPad by @NamelessGuy69 | Stardance
|
1793238820.4052553
|
1793843620.4052553
|
|
24176
|
My first slack bot! by @gayatrii | Stardance
|
gayatrii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @gayatrii | Stardanc Title: My first slack bot! by @gayatrii | Stardance...
|
1793238819.5076478
|
1793843619.5076478
|
|
48661
|
DragonPad by @NamelessGuy69 | Stardance
|
NamelessGuy69
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DragonPad by @NamelessGuy69 | Stardance
|
1793238818.5813184
|
1793843618.5813184
|
|
48660
|
Piano Teacher by @hacker123 | Stardance
|
hacker123
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Piano Teacher by @hacker123 | Stardance
|
1793238817.7070837
|
1793843617.7070837
|
|
9771
|
My awesome macropad! by @benjjiii | Stardance
|
benjjiii
|
0
|
0.61
|
0
|
[]
|
[{"post_id": 3491, "ts": "2026 [{"post_id": 3491, "ts": "2026-06-06T13:34:24Z", "hours": 0.6111, "text": "first option i got dont know if i really want to do this."}]...
|
Title: My awesome macropad! by @benjjiii | Stardan Title: My awesome macropad! by @benjjiii | Stardance
Devlogs:
first option i got dont know if i really want to do this....
|
1793238815.3071172
|
1793843615.3071172
|
|
48659
|
Birthday Sky by @msmcclelland37 | Stardance
|
msmcclelland37
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Birthday Sky by @msmcclelland37 | Stardance
|
1793238813.663258
|
1793843613.663258
|
|
28791
|
My own site! by @fulin | Stardance
|
fulin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @fulin | Stardance
|
1793238812.4179628
|
1793843612.4179628
|