|
59379
|
My awesome macropad! by @manansharma0604009 | Star My awesome macropad! by @manansharma0604009 | Stardance...
|
manansharma0604009
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @manansharma0604009 Title: My awesome macropad! by @manansharma0604009 | Stardance...
|
1792795938.201472
|
1793400738.201472
|
|
59380
|
My awesome macropad! by @Stiven | Stardance
|
Stiven
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Stiven | Stardance
|
1792795939.050948
|
1793400739.050948
|
|
20961
|
My very own WebOS by @Eswara | Stardance
|
Eswara
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Eswara | Stardance
|
1792795939.9049618
|
1793400739.9049618
|
|
59381
|
Argus by @jackr4bbit | Stardance
|
jackr4bbit
|
0
|
14.3
|
0
|
[]
|
[{"post_id": 63538, "ts": "202 [{"post_id": 63538, "ts": "2026-09-07T13:38:38Z", "hours": 14.2997, "text": "Devlog #1 I’m making a server where you can add cameras from different protocols, view them from a web dashboard (like MotionEye’s, but better), route each input to an output, record, and have real-world things happen when things happen in your camera. I’ve worked 14 hours so far, but I was planning to ship Argus to Macondo, which doesn’t require devlogs, so I’m losing 4 hours now (Don’t ask what the video is in the screenshot; I found some random HLS test feed 💀) Protocols What I’ve written so far (Stardance doesn’t support task lists apparently): Input ☑︎RTMP(S) ☑︎RTSP(S) ☐WebRTC / WHEP ☐SRT ☑︎HLS ☑︎MJPEG ☐MPEG-DASH ☐WHIP ☐HTTP Progressive ☐HomeKit ☐MSE ☐Command (custom) ☐Web client Output ☐RTMP(S) ☐RTSP(S) ☑︎WebRTC / WHEP ☐SRT ☐HLS ☑︎MJPEG ☐MPEG-DASH ☐WHIP ☐HTTP Progressive ☐HomeKit ☐MSE Recording Always Never On trigger (with manual button) Triggers Triggers are actions that take place when something happens. Triggers are supplied by extensions. Triggers can start/stop recordings or take actions provided by extensions. Some examples: Start recording when a specific cat walks into the room Stop recording when I arrive home Send me a notification (via a Pushcuts webhook) when somebody walks onto my porch (a zone) Extensions People can make extensions that can Add triggers Add trigger actions Add source and output protocols Add overlays to recordings, dashboard views, and outputs (like a box around a person) Extensions that come pre-installed include: Motion detection Anywhere In a zone Face/person recognition Detection Anywhere In a zone Add a name Emotion Groups of people Overlay (box, name, emotion, and certainty) Email and webhook (trigger actions) Custom Overlays You can add text/images including Timestamps Protocol Custom text Animals Detection Anywhere In a zone Species Color Add a name Overlay"}]...
|
Title: Argus by @jackr4bbit | Stardance
Devlogs:
Title: Argus by @jackr4bbit | Stardance
Devlogs:
Devlog #1 I’m making a server where you can add cameras from different protocols, view them from a web dashboard (like MotionEye’s, but better), route each input to an output, record, and have real-world things happen when things happen in your camera. I’ve worked 14 hours so far, but I was planning to ship Argus to Macondo, which doesn’t require devlogs, so I’m losing 4 hours now (Don’t ask what the video is in the screenshot; I found some random HLS test feed 💀) Protocols What I’ve written so far (Stardance doesn’t support task lists apparently): Input ☑︎RTMP(S) ☑︎RTSP(S) ☐WebRTC / WHEP ☐SRT ☑︎HLS ☑︎MJPEG ☐MPEG-DASH ☐WHIP ☐HTTP Progressive ☐HomeKit ☐MSE ☐Command (custom) ☐Web client Output ☐RTMP(S) ☐RTSP(S) ☑︎WebRTC / WHEP ☐SRT ☐HLS ☑︎MJPEG ☐MPEG-DASH ☐WHIP ☐HTTP Progressive ☐HomeKit ☐MSE Recording Always Never On trigger (with manual button) Triggers Triggers are actions that take place when something happens. Triggers are supplied by extensions. Triggers can start/stop recordings or take actions provided by extensions. Some examples: Start recording when a specific cat walks into the room Stop recording when I arrive home Send me a notification (via a Pushcuts webhook) when somebody walks onto my porch (a zone) Extensions People can make extensions that can Add triggers Add trigger actions Add source and output protocols Add overlays to recordings, dashboard views, and outputs (like a box around a person) Extensions that come pre-installed include: Motion detection Anywhere In a zone Face/person recognition Detection Anywhere In a zone Add a name Emotion Groups of people Overlay (box, name, emotion, and certainty) Email and webhook (trigger actions) Custom Overlays You can add text/images including Timestamps Protocol Custom text Animals Detection Anywhere In a zone Species Color Add a name Overlay...
|
1792795940.7596657
|
1793400740.7596657
|
|
3896
|
EDF drone by @ivanstiner58 | Stardance
|
ivanstiner58
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: EDF drone by @ivanstiner58 | Stardance
|
1792795941.6098611
|
1793400741.6098611
|
|
20116
|
Pad[6k2R] by @YashKash | Stardance
|
YashKash
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Pad[6k2R] by @YashKash | Stardance
|
1792795942.4225638
|
1793400742.4225638
|
|
39787
|
ZIMGo by @RP_Circulo | Stardance
|
RP_Circulo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ZIMGo by @RP_Circulo | Stardance
|
1792795943.2768104
|
1793400743.2768104
|
|
59382
|
My own site! by @jaloloddinurazaliyev | Stardance
|
jaloloddinurazaliyev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @jaloloddinurazaliyev | Sta Title: My own site! by @jaloloddinurazaliyev | Stardance...
|
1792795944.1266532
|
1793400744.1266532
|
|
21883
|
Untitled by @jhlequang | Stardance
|
jhlequang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @jhlequang | Stardance
|
1792795944.9945579
|
1793400744.9945579
|
|
29958
|
Porfolio Website by @Nipun_Dhawan | Stardance
|
Nipun_Dhawan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Porfolio Website by @Nipun_Dhawan | Stardan Title: Porfolio Website by @Nipun_Dhawan | Stardance...
|
1792795945.851105
|
1793400745.851105
|
|
59383
|
Untitled project by @lukee | Stardance
|
lukee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @lukee | Stardance
|
1792795946.6890106
|
1793400746.6890106
|
|
8825
|
My awesome macropad! by @Sheikh_Anas | Stardance
|
Sheikh_Anas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Sheikh_Anas | Star Title: My awesome macropad! by @Sheikh_Anas | Stardance...
|
1792795947.5262203
|
1793400747.5262203
|
|
59384
|
My awesome macropad! by @luaptsur | Stardance
|
luaptsur
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @luaptsur | Stardan Title: My awesome macropad! by @luaptsur | Stardance...
|
1792795948.3827589
|
1793400748.3827589
|
|
27289
|
My first slack bot! by @Jayshu | Stardance
|
Jayshu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Jayshu | Stardance
|
1792795949.2427223
|
1793400749.2427223
|
|
26388
|
WarioWare Game by @PalPatel | Stardance
|
PalPatel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @PalPatel | Stardance
|
1792795950.0875864
|
1793400750.0875864
|
|
59385
|
My bot by @lukee | Stardance
|
lukee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My bot by @lukee | Stardance
|
1792795950.949955
|
1793400750.949955
|
|
4529
|
The Crashing MacroPad! by @Blueberry2619 | Stardan The Crashing MacroPad! by @Blueberry2619 | Stardance...
|
Blueberry2619
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The Crashing MacroPad! by @Blueberry2619 | Title: The Crashing MacroPad! by @Blueberry2619 | Stardance...
|
1792795951.8077369
|
1793400751.8077369
|
|
59386
|
My very own WebOS by @senthilnathan_arun | Stardan My very own WebOS by @senthilnathan_arun | Stardance...
|
senthilnathan_arun
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @senthilnathan_arun | Title: My very own WebOS by @senthilnathan_arun | Stardance...
|
1792795952.6848269
|
1793400752.6848269
|
|
15455
|
My awesome macropad! by @ria_mukundan | Stardance
|
ria_mukundan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ria_mukundan | Sta Title: My awesome macropad! by @ria_mukundan | Stardance...
|
1792795953.5443277
|
1793400753.5443277
|
|
3700
|
Manufacturing Shop Slackbot by @rensinna | Stardan Manufacturing Shop Slackbot by @rensinna | Stardance...
|
rensinna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Manufacturing Shop Slackbot by @rensinna | Title: Manufacturing Shop Slackbot by @rensinna | Stardance...
|
1792795954.3912342
|
1793400754.3912342
|
|
59387
|
Koi by @Koi-II | Stardance
|
Koi-II
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Koi by @Koi-II | Stardance
|
1792795955.2289753
|
1793400755.2289753
|
|
59389
|
Slackbot by @ganga_pranav | Stardance
|
ganga_pranav
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Slackbot by @ganga_pranav | Stardance
|
1792795956.073852
|
1793400756.073852
|
|
23022
|
TennisIQ by @shivrajtennis | Stardance
|
shivrajtennis
|
0
|
5.77
|
0
|
[]
|
[{"post_id": 64818, "ts": "202 [{"post_id": 64818, "ts": "2026-09-09T14:28:01Z", "hours": 2.9547, "text": "Finished TennisIQ prototype 2, with better web designing, and more efficient AI coach."}, {"post_id": 13061, "ts": "2026-06-21T11:21:31Z", "hours": 1.4394, "text": "TennisIQ Devlog 2 🎾Big day.TennisIQ is starting to feel like a real product instead of a side project. Shipped today✅ Restored premium v5 UI✅ Preserved Quick Mode + Deep Mode✅ Match Logging + Compare mode✅ Delete Match feature✅ Tournament Planner✅ Budget Dashboard✅ UTR Target Calculator✅ AI Coach v2✅ Video Recommendations based on real match weaknessesImportant ruleNo fake data.No demo players. No hardcoded tournaments.No made-up match stats.Everything is generated from actual user input and logged matches.AI Coach v2The coach now analyzes:First Serve InFirst Serve WonSecond Serve WonReturn WonUnforced ErrorsWinnersDouble FaultsNet PointsThen it gives:Biggest weaknesses. Why they matterDrillsTraining focusEstimated UTR impactRelevant training videosCurrent TennisIQ stack🎾 Match Analytics🧠 AI Coaching🎯 UTR Target Planning💰 Tournament Budgeting📊 Benchmark Comparisons🎥 Video RecommendationsEverything runs locally with Next.js and TypeScript.Still a lot to build, but this is the first version that feels like something I’d actually use as a competitive junior player."}, {"post_id": 12968, "ts": "2026-06-21T06:58:27Z", "hours": 1.3728, "text": "TennisIQ v5 is alive and running.🎾 Today was chaos. I migrated TennisIQ from my old v4 interface to a cleaner v5 design and spent most of the day fixing Next.js, TypeScript and Copilot-generated bugs. Added / Working Integrated TennisIQ v5 UI Tournament Planner UTR Target Calculator groundwork AI Coach framework Video recommendation system groundwork Hackatime integration Match deletion feature (in progress) Biggest challenges Unicode escape errors Merge conflicts inside VS Code Runtime crashes from undefined objects Restoring functionality after migrating from v4 Next goals Restore Quick Mode and Deep Analysis Finish Delete Match AI Coach with training videos Smarter UTR improvement plans Better dark mode and UI polish TennisIQ is an AI-powered competitive tennis analytics platform that helps players track matches, analyze weaknesses, plan tournaments, and improve toward their UTR goals. Still lots to build, but today was the first day the new version actually ran end-to-end 🚀"}]...
|
Title: TennisIQ by @shivrajtennis | Stardance
Dev Title: TennisIQ by @shivrajtennis | Stardance
Devlogs:
TennisIQ v5 is alive and running.🎾 Today was chaos. I migrated TennisIQ from my old v4 interface to a cleaner v5 design and spent most of the day fixing Next.js, TypeScript and Copilot-generated bugs. Added / Working Integrated TennisIQ v5 UI Tournament Planner UTR Target Calculator groundwork AI Coach framework Video recommendation system groundwork Hackatime integration Match deletion feature (in progress) Biggest challenges Unicode escape errors Merge conflicts inside VS Code Runtime crashes from undefined objects Restoring functionality after migrating from v4 Next goals Restore Quick Mode and Deep Analysis Finish Delete Match AI Coach with training videos Smarter UTR improvement plans Better dark mode and UI polish TennisIQ is an AI-powered competitive tennis analytics platform that helps players track matches, analyze weaknesses, plan tournaments, and improve toward their UTR goals. Still lots to build, but today was the first day the new version actually ran end-to-end 🚀
TennisIQ Devlog 2 🎾Big day.TennisIQ is starting to feel like a real product instead of a side project. Shipped today✅ Restored premium v5 UI✅ Preserved Quick Mode + Deep Mode✅ Match Logging + Compare mode✅ Delete Match feature✅ Tournament Planner✅ Budget Dashboard✅ UTR Target Calculator✅ AI Coach v2✅ Video Recommendations based on real match weaknessesImportant ruleNo fake data.No demo players. No hardcoded tournaments.No made-up match stats.Everything is generated from actual user input and logged matches.AI Coach v2The coach now analyzes:First Serve InFirst Serve WonSecond Serve WonReturn WonUnforced ErrorsWinnersDouble FaultsNet PointsThen it gives:Biggest weaknesses. Why they matterDrillsTraining focusEstimated UTR impactRelevant training videosCurrent TennisIQ stack🎾 Match Analytics🧠 AI Coaching🎯 UTR Target Planning💰 Tournament Budgeting📊 Benchmark Comparisons🎥 Video RecommendationsEverything runs locally with Next.js and TypeScript.Still a lot to build, but this is the first version that feels like something I’d actually use as a competitive junior player.
Finished TennisIQ prototype 2, with better web designing, and more efficient AI coach....
|
1792795956.8916478
|
1793400756.8916478
|
|
59390
|
My first slack bot! by @meti | Stardance
|
meti
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @meti | Stardance
|
1792795957.7422073
|
1793400757.7422073
|
|
37246
|
Abacus by @kshitijvats1023 | Stardance
|
kshitijvats1023
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Abacus by @kshitijvats1023 | Stardance
|
1792795958.589615
|
1793400758.589615
|
|
18612
|
Frictionless by @packetspoofer | Stardance
|
packetspoofer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @packetspoofer | Stardance
|
1792795959.442366
|
1793400759.442366
|
|
59391
|
Lights Out by @abdulahad | Stardance
|
abdulahad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Lights Out by @abdulahad | Stardance
|
1792795960.262183
|
1793400760.262183
|
|
22592
|
My very own WebOS by @subhh | Stardance
|
subhh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @subhh | Stardance
|
1792795961.196282
|
1793400761.196282
|
|
59392
|
webos by @ganga_pranav | Stardance
|
ganga_pranav
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: webos by @ganga_pranav | Stardance
|
1792795962.0423143
|
1793400762.0423143
|
|
59393
|
My first slack bot! by @Cosmic_Utkarsh | Stardance
|
Cosmic_Utkarsh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Cosmic_Utkarsh | St Title: My first slack bot! by @Cosmic_Utkarsh | Stardance...
|
1792795962.9025538
|
1793400762.9025538
|
|
3016
|
The hoopdream by @sanjithy123 | Stardance
|
sanjithy123
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The hoopdream by @sanjithy123 | Stardance
|
1792795963.7608466
|
1793400763.7608466
|
|
59394
|
luke os by @lukee | Stardance
|
lukee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: luke os by @lukee | Stardance
|
1792795964.5901732
|
1793400764.5901732
|
|
18280
|
My very own WebOS by @keshavmenon11 | Stardance
|
keshavmenon11
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @keshavmenon11 | Stard Title: My very own WebOS by @keshavmenon11 | Stardance...
|
1792795965.4505045
|
1793400765.4505045
|
|
59395
|
Untitled project by @ben_ofir_sarid | Stardance
|
ben_ofir_sarid
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @ben_ofir_sarid | Stard Title: Untitled project by @ben_ofir_sarid | Stardance...
|
1792795966.296121
|
1793400766.296121
|
|
26852
|
My awesome macropad! by @polchen2012 | Stardance
|
polchen2012
|
0
|
0.31
|
0
|
[]
|
[{"post_id": 17580, "ts": "202 [{"post_id": 17580, "ts": "2026-06-28T13:03:38Z", "hours": 0.3111, "text": "I’m writing the code for my keyboard."}]...
|
Title: My awesome macropad! by @polchen2012 | Star Title: My awesome macropad! by @polchen2012 | Stardance
Devlogs:
I’m writing the code for my keyboard....
|
1792795967.1256406
|
1793400767.1256406
|
|
1049
|
Hexapod-HomeAssistent by @thebiker_cat | Stardance
|
thebiker_cat
|
0
|
20.89
|
0
|
[]
|
[{"post_id": 12825, "ts": "202 [{"post_id": 12825, "ts": "2026-06-21T00:11:33Z", "hours": 8.0814, "text": "Completed Goals I have reached a few goals and managed to complete a few challenges that I was afraid of. There are actually two important steps I have completed. Build Update First, I managed to finish the raw Hexapod build (a few electronic parts are still missing, but I mean the body). Code Improvements Secondly, I made a few improvements to control a Hexapod leg with coordinates (we also had a problem with our C++ header files that my friend has, thank goodness, solved). So now we are really able to control a real leg with coordinates. Movement Test Another big feature where I laid my focus was a first movement test. I already implemented this feature. I tried to program the tripod gait. I hope that it’ll work, because I wasn’t able to test it until now like I mentioned above, I hadn’t had the time to include some electronic parts in the Hexapod build. What’s Next? I suppose my next big step will be to actually get the robot to walk, so that my friend can finish his important tests and start to implement other movement features, because he is already really hyped for that. We’ll maybe also start with some kind of a control system, but I think that this will take us a little more time and it will be a while yet before we actually get started with that."}, {"post_id": 10235, "ts": "2026-06-16T21:18:35Z", "hours": 8.32, "text": "Progress Since my last devlog, I’ve made great progress. I’ve been looking into inverse kinematics quite a bit and I was pretty successful. I managed to derive formulas for my calculations with a few drawings. I also started to build my robot. Actually, I’ve managed to build up one leg. The leg consists of three joints, each controlled by a servo motor. Implementation Furthermore, my last step was to put my equations into code, so I wrote a test program. Now I am able to convert the angles into coordinates and I can move the leg with coordinates wherever I want. Challenges The biggest challenge so far has been getting the math right for the inverse kinematics, but once I drew the leg and did my calculations on paper, everything came together pretty quickly. What’s next? My next actions would be to make some movement tests. I will try to make a first walking test and see how stable the leg performs. After that, the plan is to build the remaining legs and work on coordinating them together."}, {"post_id": 6733, "ts": "2026-06-11T08:32:11Z", "hours": 4.4881, "text": "I started the Hexapod project by creating a project file structure and tried to implement the first functions for a leg of the Hexapod. It’s a bit difficult right now, because I am still waiting for my project hardware to arrive. So because I couldn’t really start to build the robot, and it was also difficult to start programming it, I started with a few servo tests with buttons and a potentiometer so that I would at least do something to better understand how servo engines work. My next step (when my hardware has arrived) would be to build the robot or at least a leg and try to figure out the kinematics and movement of it and implement it."}]...
|
Title: Hexapod-HomeAssistent by @thebiker_cat | St Title: Hexapod-HomeAssistent by @thebiker_cat | Stardance
Devlogs:
I started the Hexapod project by creating a project file structure and tried to implement the first functions for a leg of the Hexapod. It’s a bit difficult right now, because I am still waiting for my project hardware to arrive. So because I couldn’t really start to build the robot, and it was also difficult to start programming it, I started with a few servo tests with buttons and a potentiometer so that I would at least do something to better understand how servo engines work. My next step (when my hardware has arrived) would be to build the robot or at least a leg and try to figure out the kinematics and movement of it and implement it.
Progress Since my last devlog, I’ve made great progress. I’ve been looking into inverse kinematics quite a bit and I was pretty successful. I managed to derive formulas for my calculations with a few drawings. I also started to build my robot. Actually, I’ve managed to build up one leg. The leg consists of three joints, each controlled by a servo motor. Implementation Furthermore, my last step was to put my equations into code, so I wrote a test program. Now I am able to convert the angles into coordinates and I can move the leg with coordinates wherever I want. Challenges The biggest challenge so far has been getting the math right for the inverse kinematics, but once I drew the leg and did my calculations on paper, everything came together pretty quickly. What’s next? My next actions would be to make some movement tests. I will try to make a first walking test and see how stable the leg performs. After that, the plan is to build the remaining legs and work on coordinating them together.
Completed Goals I have reached a few goals and managed to complete a few challenges that I was afraid of. There are actually two important steps I have completed. Build Update First, I managed to finish the raw Hexapod build (a few electronic parts are still missing, but I mean the body). Code Improvements Secondly, I made a few improvements to control a Hexapod leg with coordinates (we also had a problem with our C++ header files that my friend has, thank goodness, solved). So now we are really able to control a real leg with coordinates. Movement Test Another big feature where I laid my focus was a first movement test. I already implemented this feature. I tried to program the tripod gait. I hope that it’ll work, because I wasn’t able to test it until now like I mentioned above, I hadn’t had the time to include some electronic parts in the Hexapod build. What’s Next? I suppose my next big step will be to actually get the robot to walk, so that my friend can finish his important tests and start to implement other movement features, because he is already really hyped for that. We’ll maybe also start with some kind of a control system, but I think that this will take us a little more time and it will be a while yet before we actually get started with that....
|
1792795967.97154
|
1793400767.97154
|
|
59398
|
My own site! by @sarahfelix | Stardance
|
sarahfelix
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @sarahfelix | Stardance
|
1792795968.821409
|
1793400768.821409
|
|
98
|
Untitled by @Fantamomo | Stardance
|
Fantamomo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Fantamomo | Stardance
|
1792795971.7599013
|
1793400771.7599013
|
|
59399
|
EGGG by @Frosty_Joe | Stardance
|
Frosty_Joe
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: EGGG by @Frosty_Joe | Stardance
|
1792795972.603686
|
1793400772.603686
|
|
16799
|
3D engine in terminal by @Sudsy | Stardance
|
Sudsy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 3D engine in terminal by @Sudsy | Stardance
|
1792795973.4594922
|
1793400773.4594922
|
|
25774
|
My awesome macropad! by @Phlin | Stardance
|
Phlin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Phlin | Stardance
|
1792795974.2892888
|
1793400774.2892888
|
|
20782
|
My first slack bot! by @AlanoudAlassaf | Stardance
|
AlanoudAlassaf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @AlanoudAlassaf | St Title: My first slack bot! by @AlanoudAlassaf | Stardance...
|
1792795975.1441555
|
1793400775.1441555
|
|
22048
|
Frictionless by @andrii_kladov | Stardance
|
andrii_kladov
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @andrii_kladov | Stardance
|
1792795975.9852438
|
1793400775.9852438
|
|
28521
|
Car Wash simulator by @vishnu-kintali | Stardance
|
vishnu-kintali
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Car Wash simulator by @vishnu-kintali | Sta Title: Car Wash simulator by @vishnu-kintali | Stardance...
|
1792795976.8407795
|
1793400776.8407795
|
|
37906
|
Untitled by @uz7 | Stardance
|
uz7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @uz7 | Stardance
|
1792795977.6805418
|
1793400777.6805418
|
|
7088
|
Hsoj.is-a.dev by @Hsoj | Stardance
|
Hsoj
|
0
|
7.19
|
0
|
[]
|
[{"post_id": 76109, "ts": "202 [{"post_id": 76109, "ts": "2026-10-02T10:26:34Z", "hours": 7.1914, "text": "After 7 hours of locked-in coding, ….I think I am about halfway(??) done with this project. Here are the things I did: I went with the retro/terminal look for my site. I like to doomscroll unique looking sites in my free time, so I was very excited when I finally started making my own. I learned a lot about tailwind css while designing it. To the point that I can now confidently write tailwind classes without looking at the docs. I made 3 color palettes (and a switcher). I couldn’t decide between them, so I thought why not just make a color palette switcher on the site. And that’s what I did. I added a music player …because why not :) I also added a guestbook feature Credits to https://guestbooks.meadow.cafe/ for enabling me to add this feature I deployed the site using cloudflare pages I just want to say that Cloudflare Pages suck! I spent an hour just trying to get it to deploy correctly. (Why is it not as easy as Vercel??) Though I guess that was why I chose it because I had no experience in it before. My next TODO’s: Finish the Blog Rendering Feature for the Blogs Page Add the Projects Cards for the Projects Page PS: Nevermind the “I am 18 years old” part of the site. I won’t actually turn 18 until November lol. PPS: You can visit the site @ https://hsoj-is-a-dev.pages.dev/"}]...
|
Title: Hsoj.is-a.dev by @Hsoj | Stardance
Devlogs Title: Hsoj.is-a.dev by @Hsoj | Stardance
Devlogs:
After 7 hours of locked-in coding, ….I think I am about halfway(??) done with this project. Here are the things I did: I went with the retro/terminal look for my site. I like to doomscroll unique looking sites in my free time, so I was very excited when I finally started making my own. I learned a lot about tailwind css while designing it. To the point that I can now confidently write tailwind classes without looking at the docs. I made 3 color palettes (and a switcher). I couldn’t decide between them, so I thought why not just make a color palette switcher on the site. And that’s what I did. I added a music player …because why not :) I also added a guestbook feature Credits to https://guestbooks.meadow.cafe/ for enabling me to add this feature I deployed the site using cloudflare pages I just want to say that Cloudflare Pages suck! I spent an hour just trying to get it to deploy correctly. (Why is it not as easy as Vercel??) Though I guess that was why I chose it because I had no experience in it before. My next TODO’s: Finish the Blog Rendering Feature for the Blogs Page Add the Projects Cards for the Projects Page PS: Nevermind the “I am 18 years old” part of the site. I won’t actually turn 18 until November lol. PPS: You can visit the site @ https://hsoj-is-a-dev.pages.dev/...
|
1792795978.5264335
|
1793400778.5264335
|
|
4138
|
My awesome macropad! by @turtleshellprc | Stardanc My awesome macropad! by @turtleshellprc | Stardance...
|
turtleshellprc
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @turtleshellprc | S Title: My awesome macropad! by @turtleshellprc | Stardance...
|
1792795979.3647327
|
1793400779.3647327
|
|
5595
|
CERES - Weedkiller Bot by @minjajo | Stardance
|
minjajo
|
0
|
26.24
|
0
|
[]
|
[{"post_id": 16082, "ts": "202 [{"post_id": 16082, "ts": "2026-06-26T04:24:38Z", "hours": 2.6081, "text": "CERES MK2: Devlog 14 What’s New: The robot has been assembled, and the electronics have been all wired up! I’ve attached a video of the gearbox working below. In the next devlog, ill show a video of the entire robot. The issue regarding the gears slipping has been resolved with the new gears that I’ve designed. The main issue now is that the wheels themselves are slipping on the axle. I’m realizing now that I should have gone with a hexagonal axle instead of a circular one like I have. I’ll have to re-design the wheels so that they properly grip these axles What’s Next: The next step is program the robot to turn, as it can already go forward and backwards, and then also re-design the wheels so that they stop slipping when the motors are running."}, {"post_id": 13829, "ts": "2026-06-22T17:39:48Z", "hours": 1.4167, "text": "CERES MK2: Devlog 13 What’s New: I’ve put together the mechanical aspects of the main robot! The robot has finally come together in real life, and it looks amazing. I assembled all four motor gearboxes, mounted them onto the frame along with the axle mounts, and then attached the wheels. Current Issues: Currently, the wheels themselves are holding onto the axles quite well, but because the axles are threaded rods (instead of a hexagonal rod), the gear in the gearbox begins to slip when there is a high torque load on the robot. What’s Next: I’m going to fix this gear slipping issue by redesigning the gears to have perpendicular screws in order to grip the threaded rod perfectly. I’ll have to take apart the robot and re-do the gearbox to attach these new gears."}, {"post_id": 13230, "ts": "2026-06-21T17:42:16Z", "hours": 1.5028, "text": "CERES MK2: Devlog 12 What’s New: I’ve put together the first gearbox assembly! I was able to properly mount the motor to the gearbox, along with the gears themselves and the ball bearings on both the gearbox and the red axle mount shown in the picture below. Everything appears to be coming together great right now. The gears sit together flushly without any issues, and the motor is able to drive the axle well. What’s Next: The next step is to finish up the other three gearboxes, and then I can mount the rest of the body panels onto the robot before wiring up the electronics!"}, {"post_id": 11031, "ts": "2026-06-18T01:53:55Z", "hours": 0.7125, "text": "CERES MK2: Devlog 11 What’s New: Unfortunately, I’ve been a bit busy lately, and I have not been able to make much progress on the robot. That should change soon though! As for whats new, I’ve just been cleaning up the design of the robot, and I’ve worked on setting up the Raspberry Pi. What’s Next: The next step is likely to start actually looking into how the robot will be able to identify weeds via camera vision, as well as how the pump-tank system will look!"}, {"post_id": 8099, "ts": "2026-06-13T14:54:17Z", "hours": 8.4683, "text": "CERES MK2: Devlog 10 What’s New: I made a couple of changes to the CAD design (which I will showcase in the next devlog), and I also began soldering the motors to the wires in preparation of setting them up with the motor drivers. As the 3d printed parts start getting ready, I’ve been attaching them to the aluminum frame, as seen below Currently, the biggest issue with the assembly of the robot is the difficulty that comes with ensuring that the T-slot nuts are inserted and held in the exact position necessary to mount the body panels. I attempted to compensate for this earlier in the design process by designing v-slot liners, but they did not work properly as they were not able to hold the T-slot nuts effectively. What’s Next: The next step in the project is to work on setting up the Raspberry Pi, which I have not yet done. I also want to test out the ESP32 with the motors and Joy-Con soon."}, {"post_id": 7146, "ts": "2026-06-11T22:43:16Z", "hours": 1.2517, "text": "CERES MK2: Devlog 9 What’s New: I designed a Raspberry Pi camera module mount and housing, in order to accommodate the image recognition software on the raspberry Pi. I’ve begun to print out all the CAD components, so I’ll be able to add onto the (already assembled) aluminum frame soon. I’ve also begun to work on a rudimentary system to control the weed robot via a Nintendo Switch Joy-con in order to test its capabilities before paring it with the Raspberry pi. To use the Joy-Con with the esp32, I used a library called BluePads32, and it allows for a connection between an esp32 and any controller. It was relatively easy to set up due to there being in-depth documentation on the library. You can visit the documentation here if you’d like to try it yourself! What’s Next: The next step in the project, while the 3d printed components are printing, is to start soldering and wiring up the motors to the motor drivers, and start experimenting with serial communication between the ESP and Raspberry Pi"}, {"post_id": 5796, "ts": "2026-06-09T18:33:59Z", "hours": 1.65, "text": "CERES MK2: Devlog 8 What’s New: Today, I designed multiple new body panels on the robot in order to properly house the electronics from the elements. In addition, I’ve begun the physical construction of the robot’s frame, which I’ve attached below The biggest hurdle today was assembling the frame for sure. Because I was using sliding v-rail T-nuts instead of the insertable type, I would have to partially dismantle the frame every time I have to add any panels or mounts. What’s Next: I WILL start working on the code for the ESP32 next time, as I’ve been putting it off for a while now. I’ll also start physically wiring up the ESP32 with the placeholder L298n drivers so that I can test the robot."}, {"post_id": 5336, "ts": "2026-06-09T02:19:26Z", "hours": 1.1714, "text": "CERES MK2: Devlog 7 What’s New: Because I completely overhauled the design of the bot (Mk2), I started re-designing the lower casing that protects the electronics and motors from the elements! I also used this opportunity to redesign the way the two separate plates (of the casing) fit together in order to allow for both easier assembly and better overall durability. Some Other Things: I had to redesign the wheels as well to accomodate the new 5mm threaded rods that I plan to use for the axles. I also changed up the color scheme plan - I’m going for a more modern, high tech aesthetic. What’s Next: I have yet to implement the electronics into the Mk2, and the design is purely mechanical right now. I have to design the mounts for the RPI, esp32, motor drivers, and etc. I also want to start designing the PCB for the bot so that the motor drivers are integrated directly with the ESP32."}, {"post_id": 5097, "ts": "2026-06-08T19:44:56Z", "hours": 2.2703, "text": "CERES MK2: Devlog 6 What’s New: I decided to completely overhaul the design of the robot and essentially start from scratch. In the initial iteration, the entire weight of the robot was resting on the motor’s shaft/axle. In this new design, I’ve pivoted towards a gearbox design that will allow for the weight of the robot to rest on 4 axles instead of the motor itself. So far, I have only designed the gearbox itself as well as the mounts for the axles to sit on. This ensures the longevity of the robot as the wheels are no longer directly attached to the motors. The gearbox itself uses two gears, with a 1:1 gear ratio as I did not want to change the RPM output of the wheel, as I felt that the 100rpm provided by the motors was sufficient in terms of both torque and speed. The gearbox mounts to the frame using 4 sliding T-nuts and M5 screws. The axle itself is an M5 threaded rod, and the rod sits on 3 ball bearings with an inner diameter of 5mm to rotate freely. What’s Next: I’ll have to redesign a majority of the body panels, as well as the wheels themselves. I’ll likely do that before I move onto designing new mounts for the electronics."}, {"post_id": 4408, "ts": "2026-06-07T18:43:06Z", "hours": 0.7697, "text": "Whats new: Designed and implemented V-slot rail sliders for the robot frame. This is done for easier assembly, as it no longer requires the precise positioning the the T-nuts when assembling and mounting body panels for the frame. I also made some small aesthetic design adjustments I faced some issues with the alignment of the lower body panel and the frame. For some reason, they’re not aligning even though I believe all my measurements are correct. I have yet to resolve the issue, so I’ll have to save that for next time. Whats Next: The CAD/frame/body panels are done for the most part. There are some issues (like mentioned above) that still need to be fixed, and there are a few adjustments I still want to make. The next step will be to move on to the code for the ESP32, so that the robot can be controlled manually. After that, I’ll start designing a PCB to integrate the components better."}, {"post_id": 3999, "ts": "2026-06-07T04:30:11Z", "hours": 0.7769, "text": "I designed custom v-slot liners for the aluminum extrusions, allowing for easier assembly of the body panels."}, {"post_id": 3082, "ts": "2026-06-05T23:45:19Z", "hours": 0.7706, "text": "I altered the locations where the motor drivers and raspberry pi are mounted so that they have more protection from the weather. I also fixed the issues with the tire mirroring (which can be seen in the previous iterations) and I designed the top cover to allow for the electronics to be more accessible."}, {"post_id": 2338, "ts": "2026-06-04T19:38:34Z", "hours": 1.5733, "text": "I’ve been printing out and assembling the wheels and tires of the Weedkiller bot. The tires are printed in 95A TPU. I’ve also been re-doing the layout of the electronics on the robot, which I’ll post later."}, {"post_id": 1608, "ts": "2026-06-03T19:00:46Z", "hours": 0.685, "text": "I’ve updated the color scheme of the Weed-killing robot to look more agricultural. I also finished desigining the mounting holes for the lower housing plate and designed mounts for the raspberry pi and motor drivers as well. I’ll start off by using L298n drivers and I hope to eventually start using my own PCB that incorporates an esp32 module and a H-bridge motor driver."}, {"post_id": 1105, "ts": "2026-06-02T22:40:16Z", "hours": 0.6089, "text": "Say hello to the Weedkiller bot! I’ve yet to name it, but I’m currently working on its outer shell/casing so that it can be weatherproof."}]...
|
Title: CERES - Weedkiller Bot by @minjajo | Starda Title: CERES - Weedkiller Bot by @minjajo | Stardance
Devlogs:
Say hello to the Weedkiller bot! I’ve yet to name it, but I’m currently working on its outer shell/casing so that it can be weatherproof.
I’ve updated the color scheme of the Weed-killing robot to look more agricultural. I also finished desigining the mounting holes for the lower housing plate and designed mounts for the raspberry pi and motor drivers as well. I’ll start off by using L298n drivers and I hope to eventually start using my own PCB that incorporates an esp32 module and a H-bridge motor driver.
I’ve been printing out and assembling the wheels and tires of the Weedkiller bot. The tires are printed in 95A TPU. I’ve also been re-doing the layout of the electronics on the robot, which I’ll post later.
I altered the locations where the motor drivers and raspberry pi are mounted so that they have more protection from the weather. I also fixed the issues with the tire mirroring (which can be seen in the previous iterations) and I designed the top cover to allow for the electronics to be more accessible.
I designed custom v-slot liners for the aluminum extrusions, allowing for easier assembly of the body panels.
Whats new: Designed and implemented V-slot rail sliders for the robot frame. This is done for easier assembly, as it no longer requires the precise positioning the the T-nuts when assembling and mounting body panels for the frame. I also made some small aesthetic design adjustments I faced some issues with the alignment of the lower body panel and the frame. For some reason, they’re not aligning even though I believe all my measurements are correct. I have yet to resolve the issue, so I’ll have to save that for next time. Whats Next: The CAD/frame/body panels are done for the most part. There are some issues (like mentioned above) that still need to be fixed, and there are a few adjustments I still want to make. The next step will be to move on to the code for the ESP32, so that the robot can be controlled manually. After that, I’ll start designing a PCB to integrate the components better.
CERES MK2: Devlog 6 What’s New: I decided to completely overhaul the design of the robot and essentially start from scratch. In the initial iteration, the entire weight of the robot was resting on the motor’s shaft/axle. In this new design, I’ve pivoted towards a gearbox design that will allow for the weight of the robot to rest on 4 axles instead of the motor itself. So far, I have only designed the gearbox itself as well as the mounts for the axles to sit on. This ensures the longevity of the robot as the wheels are no longer directly attached to the motors. The gearbox itself uses two gears, with a 1:1 gear ratio as I did not want to change the RPM output of the wheel, as I felt that the 100rpm provided by the motors was sufficient in terms of both torque and speed. The gearbox mounts to the frame using 4 sliding T-nuts and M5 screws. The axle itself is an M5 threaded rod, and the rod sits on 3 ball bearings with an inner diameter of 5mm to rotate freely. What’s Next: I’ll have to redesign a majority of the body panels, as well as the wheels themselves. I’ll likely do that before I move onto designing new mounts for the electronics.
CERES MK2: Devlog 7 What’s New: Because I completely overhauled the design of the bot (Mk2), I started re-designing the lower casing that protects the electronics and motors from the elements! I also used this opportunity to redesign the way the two separate plates (of the casing) fit together in order to allow for both easier assembly and better overall durability. Some Other Things: I had to redesign the wheels as well to accomodate the new 5mm threaded rods that I plan to use for the axles. I also changed up the color scheme plan - I’m going for a more modern, high tech aesthetic. What’s Next: I have yet to implement the electronics into the Mk2, and the design is purely mechanical right now. I have to design the mounts for the RPI, esp32, motor drivers, and etc. I also want to start designing the PCB for the bot so that the motor drivers are integrated directly with the ESP32.
CERES MK2: Devlog 8 What’s New: Today, I designed multiple new body panels on the robot in order to properly house the electronics from the elements. In addition, I’ve begun the physical construction of the robot’s frame, which I’ve attached below The biggest hurdle today was assembling the frame for sure. Because I was using sliding v-rail T-nuts instead of the insertable type, I would have to partially dismantle the frame every time I have to add any panels or mounts. What’s Next: I WILL start working on the code for the ESP32 next time, as I’ve been putting it off for a while now. I’ll also start physically wiring up the ESP32 with the placeholder L298n drivers so that I can test the robot.
CERES MK2: Devlog 9 What’s New: I designed a Raspberry Pi camera module mount and housing, in order to accommodate the image recognition software on the raspberry Pi. I’ve begun to print out all the CAD components, so I’ll be able to add onto the (already assembled) aluminum frame soon. I’ve also begun to work on a rudimentary system to control the weed robot via a Nintendo Switch Joy-con in order to test its capabilities before paring it with the Raspberry pi. To use the Joy-Con with the esp32, I used a library called BluePads32, and it allows for a connection between an esp32 and any controller. It was relatively easy to set up due to there being in-depth documentation on the library. You can visit the documentation here if you’d like to try it yourself! What’s Next: The next step in the project, while the 3d printed components are printing, is to start soldering and wiring up the motors to the motor drivers, and start experimenting with serial communication between the ESP and Raspberry Pi
CERES MK2: Devlog 10 What’s New: I made a couple of changes to the CAD design (which I will showcase in the next devlog), and I also began soldering the motors to the wires in preparation of setting them up with the motor drivers. As the 3d printed parts start getting ready, I’ve been attaching them to the aluminum frame, as seen below Currently, the biggest issue with the assembly of the robot is the difficulty that comes with ensuring that the T-slot nuts are inserted and held in the exact position necessary to mount the body panels. I attempted to compensate for this earlier in the design process by designing v-slot liners, but they did not work properly as they were not able to hold the T-slot nuts effectively. What’s Next: The next step in the project is to work on setting up the Raspberry Pi, which I have not yet done. I also want to test out the ESP32 with the motors and Joy-Con soon.
CERES MK2: Devlog 11 What’s New: Unfortunately, I’ve been a bit busy lately, and I have not been able to make much progress on the robot. That should change soon though! As for whats new, I’ve just been cleaning up the design of the robot, and I’ve worked on setting up the Raspberry Pi. What’s Next: The next step is likely to start actually looking into how the robot will be able to identify weeds via camera vision, as well as how the pump-tank system will look!
CERES MK2: Devlog 12 What’s New: I’ve put together the first gearbox assembly! I was able to properly mount the motor to the gearbox, along with the gears themselves and the ball bearings on both the gearbox and the red axle mount shown in the picture below. Everything appears to be coming together great right now. The gears sit together flushly without any issues, and the motor is able to drive the axle well. What’s Next: The next step is to finish up the other three gearboxes, and then I can mount the rest of the body panels onto the robot before wiring up the electronics!
CERES MK2: Devlog 13 What’s New: I’ve put together the mechanical aspects of the main robot! The robot has finally come together in real life, and it looks amazing. I assembled all four motor gearboxes, mounted them onto the frame along with the axle mounts, and then attached the wheels. Current Issues: Currently, the wheels themselves are holding onto the axles quite well, but because the axles are threaded rods (instead of a hexagonal rod), the gear in the gearbox begins to slip when there is a high torque load on the robot. What’s Next: I’m going to fix this gear slipping issue by redesigning the gears to have perpendicular screws in order to grip the threaded rod perfectly. I’ll have to take apart the robot and re-do the gearbox to attach these new gears.
CERES MK2: Devlog 14 What’s New: The robot has been assembled, and the electronics have been all wired up! I’ve attached a video of the gearbox working below. In the next devlog, ill show a video of the entire robot. The issue regarding the gears slipping has been resolved with the new gears that I’ve designed. The main issue now is that the wheels themselves are slipping on the axle. I’m realizing now that I should have gone with a hexagonal axle instead of a circular one like I have. I’ll have to re-design the wheels so that they properly grip these axles What’s Next: The next step is program the robot to turn, as it can already go forward and backwards, and then also re-design the wheels so that they stop slipping when the motors are running....
|
1792795980.205542
|
1793400780.205542
|
|
13976
|
Shoe Brand Website by @Chris_Cheng | Stardance
|
Chris_Cheng
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Shoe Brand Website by @Chris_Cheng | Starda Title: Shoe Brand Website by @Chris_Cheng | Stardance...
|
1792795981.3625407
|
1793400781.3625407
|
|
8778
|
Untitled by @williamta | Stardance
|
williamta
|
0
|
0.43
|
0
|
[]
|
[{"post_id": 2893, "ts": "2026 [{"post_id": 2893, "ts": "2026-06-05T19:57:24Z", "hours": 0.4308, "text": "1st Log For this log I have set up my AI agent and have downloaded the needs like docker. The setting up included coding and using the terminal for most of the set up."}]...
|
Title: Untitled by @williamta | Stardance
Devlogs Title: Untitled by @williamta | Stardance
Devlogs:
1st Log For this log I have set up my AI agent and have downloaded the needs like docker. The setting up included coding and using the terminal for most of the set up....
|
1792795982.201494
|
1793400782.201494
|