|
7094
|
loadstone by @alexarthur | Stardance
|
alexarthur
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: loadstone by @alexarthur | Stardance
|
1793566477.137715
|
1794171277.137715
|
|
54062
|
New Page by @tiyas | Stardance
|
tiyas
|
1
|
12.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-28T05:38:17Z", "hours": 12.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "i have used many ‘new page’ extensions, but i have always faced a problem, all of them provide the option to choose which search engine you want to use , but its not handy to change the search engine again and again. and for dev people its so irritating, so i made it, you have all search engines in left side, you can search in any of them as per your need. and it also have a monthly calendar and a clock and mit rss news fetcher, it will update daily, and keep you updated too…", "repo": "https://github.com/Tiyasbanerjee/New-Page", "demo": "https://tiyasbanerjee.github.io/New-Page/"}]...
|
[{"post_id": 56413, "ts": "202 [{"post_id": 56413, "ts": "2026-08-28T05:32:42Z", "hours": 0.5728, "text": "i have fixed some bugs ,and some styling issues, now it looks great, and ready to use, and i am shipping it now."}, {"post_id": 56394, "ts": "2026-08-28T04:43:28Z", "hours": 0.3911, "text": "i fixed it, now news is showing properly."}, {"post_id": 55743, "ts": "2026-08-27T18:34:45Z", "hours": 2.0158, "text": "Now the search bars are working, but the news api’s are not working properly…."}, {"post_id": 55134, "ts": "2026-08-26T16:28:29Z", "hours": 2.2278, "text": "i have added the clock and the search bars. next i will add the news feed, weather report , and the search logic , and a section to add your favorite apps."}, {"post_id": 55028, "ts": "2026-08-26T13:41:53Z", "hours": 0.7411, "text": "added a new section where news will be shown, and also made it show image of the day from nasa as the background image…"}, {"post_id": 54707, "ts": "2026-08-25T19:38:38Z", "hours": 2.0497, "text": "i have finished making the calendar… it was a tough time… because i had spend extra half hour because i saw a wrong calendar and thinking that aug has 29 days… after using 200% of my brain i at last find out my code was correct, i was mistaking…"}, {"post_id": 54547, "ts": "2026-08-25T15:59:36Z", "hours": 1.6264, "text": "Now I am building a calendar from scratch.. seems like my brain will be roasted while doing this…"}, {"post_id": 54301, "ts": "2026-08-25T07:46:00Z", "hours": 1.9564, "text": "i have set up vite. and now configing the github deploy stuffs.. i have also make the html and css a bit, like the main wallpaper and 2 sections. at first i was building it from my mind, but when i saw the guide i understood it uses vit, and github deploy , so i had to spend time understanding those things…"}]...
|
Title: New Page by @tiyas | Stardance
Devlogs:
i Title: New Page by @tiyas | Stardance
Devlogs:
i have set up vite. and now configing the github deploy stuffs.. i have also make the html and css a bit, like the main wallpaper and 2 sections. at first i was building it from my mind, but when i saw the guide i understood it uses vit, and github deploy , so i had to spend time understanding those things…
Now I am building a calendar from scratch.. seems like my brain will be roasted while doing this…
i have finished making the calendar… it was a tough time… because i had spend extra half hour because i saw a wrong calendar and thinking that aug has 29 days… after using 200% of my brain i at last find out my code was correct, i was mistaking…
added a new section where news will be shown, and also made it show image of the day from nasa as the background image…
i have added the clock and the search bars. next i will add the news feed, weather report , and the search logic , and a section to add your favorite apps.
Now the search bars are working, but the news api’s are not working properly….
i fixed it, now news is showing properly.
i have fixed some bugs ,and some styling issues, now it looks great, and ready to use, and i am shipping it now.
Ships:
i have used many ‘new page’ extensions, but i have always faced a problem, all of them provide the option to choose which search engine you want to use , but its not handy to change the search engine again and again. and for dev people its so irritating, so i made it, you have all search engines in left side, you can search in any of them as per your need. and it also have a monthly calendar and a clock and mit rss news fetcher, it will update daily, and keep you updated too…...
|
1793566475.8996007
|
1793652875.8996007
|
|
16225
|
Frictionless by @orenkravets | Stardance
|
orenkravets
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @orenkravets | Stardance
|
1793566475.016965
|
1794171275.016965
|
|
37815
|
My very own WebOS by @andrewdetroyer | Stardance
|
andrewdetroyer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @andrewdetroyer | Star Title: My very own WebOS by @andrewdetroyer | Stardance...
|
1793566474.117043
|
1794171274.117043
|
|
38252
|
3d printer enclosure by @Dwil | Stardance
|
Dwil
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 3d printer enclosure by @Dwil | Stardance
|
1793566473.2222748
|
1794171273.2222748
|
|
24995
|
My first slack bot! by @imranbelhaj89 | Stardance
|
imranbelhaj89
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @imranbelhaj89 | Sta Title: My first slack bot! by @imranbelhaj89 | Stardance...
|
1793566472.3102136
|
1794171272.3102136
|
|
7567
|
Printful Preview Generator by @jdszekeres | Starda Printful Preview Generator by @jdszekeres | Stardance...
|
jdszekeres
|
1
|
3.31
|
30
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-06T00:36:53Z", "hours": 3.0, "multiplier": 10.69, "payout": 30, "blessing": "neutral", "text": "I made a Chrome extension that allows you to create embeddable entries for Printable Quick Stores on any other website hosting platform.", "repo": "https://github.com/jdszekeres/printful_preview_generator", "demo": "https://github.com/jdszekeres/printful_preview_generator/releases"}]...
|
[{"post_id": 6251, "ts": "2026 [{"post_id": 6251, "ts": "2026-06-10T14:39:20Z", "hours": 0.3111, "text": "Debbuged an issue where products were not listed in a production environment"}, {"post_id": 3159, "ts": "2026-06-06T00:32:30Z", "hours": 0.5197, "text": "Polishing touches: CSS styling, logo, etc"}, {"post_id": 2936, "ts": "2026-06-05T20:53:05Z", "hours": 1.0892, "text": "Added the ability to preview what the generated HTML looks like before having to download it"}, {"post_id": 2878, "ts": "2026-06-05T19:22:41Z", "hours": 0.2981, "text": "Got the ability to add different product endings to the custom html"}, {"post_id": 2819, "ts": "2026-06-05T17:20:25Z", "hours": 0.99, "text": "I created a content script to pull data from the site and a popup window to read data and display it, although unformatted right now."}]...
|
Title: Printful Preview Generator by @jdszekeres | Title: Printful Preview Generator by @jdszekeres | Stardance
Devlogs:
I created a content script to pull data from the site and a popup window to read data and display it, although unformatted right now.
Got the ability to add different product endings to the custom html
Added the ability to preview what the generated HTML looks like before having to download it
Polishing touches: CSS styling, logo, etc
Debbuged an issue where products were not listed in a production environment
Ships:
I made a Chrome extension that allows you to create embeddable entries for Printable Quick Stores on any other website hosting platform....
|
1793566471.1410546
|
1793652871.1410546
|
|
385
|
Untitled project by @manjumusei | Stardance
|
manjumusei
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @manjumusei | Stardance
|
1793566470.274943
|
1794171270.274943
|
|
32610
|
super screen shotter by @im_best | Stardance
|
im_best
|
0
|
22.55
|
0
|
[]
|
[{"post_id": 46192, "ts": "202 [{"post_id": 46192, "ts": "2026-08-13T07:49:52Z", "hours": 6.8122, "text": "I’m currently improving basic controls, such as the button, rect, color, and Font classes. Then I extracted the SVG icon pack from snow-shot. At first, I planned to use Skia’s SVG module to handle them, but after several attempts, I gave up on using Skia for SVG processing and switched to resvg, because Skia kept having compilation issues. I used AI to help me integrate resvg. vcpkg cannot properly handle Skia’s SVG module, which is really a frustrating issue."}, {"post_id": 41783, "ts": "2026-08-06T05:41:23Z", "hours": 8.0531, "text": "I completed a window class, so now I can easily create and manage windows. I finally wrote a program that supports multiple windows! Then I used this window class to implement a settings page window, though I haven’t written much content for it yet. I had AI help introduce a Rust project so my program can retrieve the current system accent color and whether dark mode is enabled, allowing my windows to automatically switch colors based on the system theme. Additionally, I fixed a small bug where the tray icon wasn’t displaying properly."}, {"post_id": 35614, "ts": "2026-07-27T04:36:11Z", "hours": 1.9064, "text": "Completed and tested the multilingual system lang class and fix some bugs"}, {"post_id": 29007, "ts": "2026-07-15T17:28:53Z", "hours": 0.9597, "text": "Enhanced the hotkey class to facilitate conversion between keycodes and strings; added functionality to the log class to print integer arrays."}, {"post_id": 28970, "ts": "2026-07-15T16:19:29Z", "hours": 4.8192, "text": "I did some foundational work, such as configuring the system, setting up the logging system, and creating classes for parsing hotkeys. Then I ran tests, and all modules seem to be working fine."}]...
|
Title: super screen shotter by @im_best | Stardanc Title: super screen shotter by @im_best | Stardance
Devlogs:
I did some foundational work, such as configuring the system, setting up the logging system, and creating classes for parsing hotkeys. Then I ran tests, and all modules seem to be working fine.
Enhanced the hotkey class to facilitate conversion between keycodes and strings; added functionality to the log class to print integer arrays.
Completed and tested the multilingual system lang class and fix some bugs
I completed a window class, so now I can easily create and manage windows. I finally wrote a program that supports multiple windows! Then I used this window class to implement a settings page window, though I haven’t written much content for it yet. I had AI help introduce a Rust project so my program can retrieve the current system accent color and whether dark mode is enabled, allowing my windows to automatically switch colors based on the system theme. Additionally, I fixed a small bug where the tray icon wasn’t displaying properly.
I’m currently improving basic controls, such as the button, rect, color, and Font classes. Then I extracted the SVG icon pack from snow-shot. At first, I planned to use Skia’s SVG module to handle them, but after several attempts, I gave up on using Skia for SVG processing and switched to resvg, because Skia kept having compilation issues. I used AI to help me integrate resvg. vcpkg cannot properly handle Skia’s SVG module, which is really a frustrating issue....
|
1793566469.1169982
|
1794171269.1169982
|
|
25065
|
stellax by @Samriddhi | Stardance
|
Samriddhi
|
0
|
1.7
|
0
|
[]
|
[{"post_id": 16338, "ts": "202 [{"post_id": 16338, "ts": "2026-06-26T16:05:21Z", "hours": 1.6986, "text": "Devlog 1 — Building my first astronomy project 🌠Starting a project called Stellax. I want to understand astronomy data properly, not just study it in theory. So I’m building a web app that uses real star data and turns it into tables + graphs. Right now it’s just the beginning — folders, setup, and figuring out what the structure should look like.I have the perfect plan of how it should look like at the end. I’m going step by step and learning as I break things. First goal: get a working star dataset on the screen."}]...
|
Title: stellax by @Samriddhi | Stardance
Devlogs: Title: stellax by @Samriddhi | Stardance
Devlogs:
Devlog 1 — Building my first astronomy project 🌠Starting a project called Stellax. I want to understand astronomy data properly, not just study it in theory. So I’m building a web app that uses real star data and turns it into tables + graphs. Right now it’s just the beginning — folders, setup, and figuring out what the structure should look like.I have the perfect plan of how it should look like at the end. I’m going step by step and learning as I break things. First goal: get a working star dataset on the screen....
|
1793566468.2317374
|
1794171268.2317374
|
|
20908
|
SanePlan by @ethan_soh | Stardance
|
ethan_soh
|
0
|
80.93
|
0
|
[]
|
[{"post_id": 11995, "ts": "202 [{"post_id": 11995, "ts": "2026-06-19T15:55:34Z", "hours": 6.3756, "text": "So I made the landing a whole lot better and i fixed a few login bugs."}, {"post_id": 10665, "ts": "2026-06-17T15:04:40Z", "hours": 74.5514, "text": "Okay I made the main site. The landing is horrible so that is what I will do next."}]...
|
Title: SanePlan by @ethan_soh | Stardance
Devlogs Title: SanePlan by @ethan_soh | Stardance
Devlogs:
Okay I made the main site. The landing is horrible so that is what I will do next.
So I made the landing a whole lot better and i fixed a few login bugs....
|
1793566467.3316367
|
1794171267.3316367
|
|
20290
|
Colloborative Gym Tracking by @HarshPenguin | Star Colloborative Gym Tracking by @HarshPenguin | Stardance...
|
HarshPenguin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Colloborative Gym Tracking by @HarshPenguin Title: Colloborative Gym Tracking by @HarshPenguin | Stardance...
|
1793566466.4597368
|
1794171266.4597368
|
|
35263
|
Untitled project by @kria | Stardance
|
kria
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @kria | Stardance
|
1793566465.5488303
|
1794171265.5488303
|
|
19759
|
SmartBite by @vividha_tksj0147 | Stardance
|
vividha_tksj0147
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SmartBite by @vividha_tksj0147 | Stardance
|
1793566464.675169
|
1794171264.675169
|
|
14233
|
Fastfind by @Alec2 | Stardance
|
Alec2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fastfind by @Alec2 | Stardance
|
1793566463.7632236
|
1794171263.7632236
|
|
49435
|
Gold Digger by @ahmdesmaill | Stardance
|
ahmdesmaill
|
1
|
5.0
|
8
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-17T20:29:41Z", "hours": 5.0, "multiplier": 1.6, "payout": 8, "blessing": "neutral", "text": "I created the Backend for this Gold Digger website to learn more about Node.js. Implementing all this at first was kinda pain at first as I had to constantly switch between different files. I also built an algorithm to generate gold prices instead of using external APIs so it’s fake. I didn’t use an external API because they have long update-times (more than 10 minutes while I update the price every 2 seconds). I guess building a thing without a Framework like Express.js makes you appreciate Frameworks more! Please rate this project more based on the Backend code rather than the website’s idea/frontend. Thank you!", "repo": "https://github.com/ahmdesmaill/gold-digger", "demo": "https://golddigger.ahmdesmaill.hackclub.app/"}]...
|
[{"post_id": 49174, "ts": "202 [{"post_id": 49174, "ts": "2026-08-17T20:17:25Z", "hours": 0.2947, "text": "Final Devlog!! Just deployed the website on Hack Club Nest (using PM2) and created the README file"}, {"post_id": 49139, "ts": "2026-08-17T19:28:23Z", "hours": 1.7092, "text": "Devlog #4! I finally added the ability to invest in (fake) gold. It was pretty tough because I had to constantly switch between frontend code, backend, and utility functions. You set the amount you want to invest in British pounds then it’ll send a POST request to the backend and the backend will log the purchase in a record file. Next step should be adding final touches and shipping!"}, {"post_id": 48687, "ts": "2026-08-17T06:08:49Z", "hours": 1.4189, "text": "Devlog #3!! Yesterday I: Implemented a small fake algorithm to generate gold prices (basically it starts with an initial realistic price and then it modifies the price overtime) Updated gold prices live on the Frontend using SSE (Server-Sent Events) I wrote a very organized code which I’m proud of!"}, {"post_id": 48267, "ts": "2026-08-16T15:55:33Z", "hours": 0.7514, "text": "Devlog #2 The backend is now working!! I created a Node.js http server & implemented the serve static function, which simply serves static files based on the URL. I also learnt about the Node.js –watch flag, which makes the development experience a lot better!"}, {"post_id": 48072, "ts": "2026-08-16T11:08:15Z", "hours": 0.7919, "text": "Devlog #1 Sooooo I’m basically learning Node.js backend and I’m creating a backend (serving static files, handling requests, etc) for this Gold Digger frontend. Stay tuned!"}]...
|
Title: Gold Digger by @ahmdesmaill | Stardance
De Title: Gold Digger by @ahmdesmaill | Stardance
Devlogs:
Devlog #1 Sooooo I’m basically learning Node.js backend and I’m creating a backend (serving static files, handling requests, etc) for this Gold Digger frontend. Stay tuned!
Devlog #2 The backend is now working!! I created a Node.js http server & implemented the serve static function, which simply serves static files based on the URL. I also learnt about the Node.js –watch flag, which makes the development experience a lot better!
Devlog #3!! Yesterday I: Implemented a small fake algorithm to generate gold prices (basically it starts with an initial realistic price and then it modifies the price overtime) Updated gold prices live on the Frontend using SSE (Server-Sent Events) I wrote a very organized code which I’m proud of!
Devlog #4! I finally added the ability to invest in (fake) gold. It was pretty tough because I had to constantly switch between frontend code, backend, and utility functions. You set the amount you want to invest in British pounds then it’ll send a POST request to the backend and the backend will log the purchase in a record file. Next step should be adding final touches and shipping!
Final Devlog!! Just deployed the website on Hack Club Nest (using PM2) and created the README file
Ships:
I created the Backend for this Gold Digger website to learn more about Node.js. Implementing all this at first was kinda pain at first as I had to constantly switch between different files. I also built an algorithm to generate gold prices instead of using external APIs so it’s fake. I didn’t use an external API because they have long update-times (more than 10 minutes while I update the price every 2 seconds). I guess building a thing without a Framework like Express.js makes you appreciate Frameworks more! Please rate this project more based on the Backend code rather than the website’s idea/frontend. Thank you!...
|
1793566462.5442905
|
1793652862.5442905
|
|
13918
|
My very own WebOS by @RishiRaj | Stardance
|
RishiRaj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @RishiRaj | Stardance
|
1793566461.6365693
|
1794171261.6365693
|
|
17479
|
Untitled by @Suspicons | Stardance
|
Suspicons
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Suspicons | Stardance
|
1793566460.7308464
|
1794171260.7308464
|
|
26783
|
Combat Robot by @Alex_Angheluta | Stardance
|
Alex_Angheluta
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Combat Robot by @Alex_Angheluta | Stardance
|
1793566459.820269
|
1794171259.820269
|
|
27210
|
Mega plotter by @Evan-Gan | Stardance
|
Evan-Gan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mega plotter by @Evan-Gan | Stardance
|
1793566458.9463286
|
1794171258.9463286
|
|
32742
|
My own site! by @BenjaminJ | Stardance
|
BenjaminJ
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @BenjaminJ | Stardance
|
1793566458.0682433
|
1794171258.0682433
|
|
49430
|
STADIAPULSE by @jithendra | Stardance
|
jithendra
|
1
|
7.57
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-17T17:50:44Z", "hours": 7.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I built STADIAPULSE, a smart stadium platform for the FIFA World Cup 2026 that connects fans and organizers in real time using Gemini 1.5 and Firebase. The biggest challenge was pulling off instant, zero-latency sync between the organizer’s safety actions and the fan’s app, while engineering transparent, explainable AI (XAI) reasoning for crowd emergencies instead of relying on a black-box chatbot. I’m most proud of the live bridge trigger—where an organizer can broadcast a bottleneck alert with a single click to instantly reroute fans through accessible, step-free paths around crowded plazas. To test it out, just toggle between the Fan and Organizer views: simulate a gate bottleneck in the Command Cockpit, hit “Broadcast Emergency Alert,” and watch the Fan Portal immediately pop up the warning banner and update the 2D blueprint pathfinder to bypass the congestion.", "repo": "https://github.com/jithendrasahoo3-bit/Stdium_Sync", "demo": "https://stadiapulse.vercel.app/"}]...
|
[{"post_id": 50243, "ts": "202 [{"post_id": 50243, "ts": "2026-08-19T12:04:48Z", "hours": 0.2936, "text": "I have worked to improve the answering cable for Gemini and route tracking through the stadium map visuals and detailed explanation for route advise and own i am working to improve the route optimization."}, {"post_id": 49646, "ts": "2026-08-18T15:18:27Z", "hours": 0.2744, "text": "Set up the global real-time synchronization backend on Firebase (stadium instance) to power instant event propagation between organizer command actions and the client app."}, {"post_id": 49063, "ts": "2026-08-17T17:34:58Z", "hours": 7.2947, "text": "Built the high-contrast dark mode Organizer Command Cockpit, featuring real-time occupancy metrics (48,675 / 82,500) and the Explainable AI (XAI) Advisory Engine. When Gate D4 breached its 90% structural threshold at 93%, the Gemini backend automatically reasoned through historical density patterns, flagged a medium-risk cascade, and generated a one-click multilingual emergency broadcast directive for the security lead."}]...
|
Title: STADIAPULSE by @jithendra | Stardance
Devl Title: STADIAPULSE by @jithendra | Stardance
Devlogs:
Built the high-contrast dark mode Organizer Command Cockpit, featuring real-time occupancy metrics (48,675 / 82,500) and the Explainable AI (XAI) Advisory Engine. When Gate D4 breached its 90% structural threshold at 93%, the Gemini backend automatically reasoned through historical density patterns, flagged a medium-risk cascade, and generated a one-click multilingual emergency broadcast directive for the security lead.
Set up the global real-time synchronization backend on Firebase (stadium instance) to power instant event propagation between organizer command actions and the client app.
I have worked to improve the answering cable for Gemini and route tracking through the stadium map visuals and detailed explanation for route advise and own i am working to improve the route optimization.
Ships:
I built STADIAPULSE, a smart stadium platform for the FIFA World Cup 2026 that connects fans and organizers in real time using Gemini 1.5 and Firebase. The biggest challenge was pulling off instant, zero-latency sync between the organizer’s safety actions and the fan’s app, while engineering transparent, explainable AI (XAI) reasoning for crowd emergencies instead of relying on a black-box chatbot. I’m most proud of the live bridge trigger—where an organizer can broadcast a bottleneck alert with a single click to instantly reroute fans through accessible, step-free paths around crowded plazas. To test it out, just toggle between the Fan and Organizer views: simulate a gate bottleneck in the Command Cockpit, hit “Broadcast Emergency Alert,” and watch the Fan Portal immediately pop up the warning banner and update the 2D blueprint pathfinder to bypass the congestion....
|
1793566456.9047546
|
1793652856.9047546
|
|
27157
|
Bionic Butterfly by @leonardomflores107 | Stardanc Bionic Butterfly by @leonardomflores107 | Stardance...
|
leonardomflores107
|
0
|
2.05
|
0
|
[]
|
[{"post_id": 40241, "ts": "202 [{"post_id": 40241, "ts": "2026-08-03T17:16:47Z", "hours": 2.05, "text": "Devlog 1 Planning and CAD designing. For my project I’m making a butterfly from copper(for the body and wings), thin wire(in order to pull the wings up and down maybe even giving them a wider motion), an Arduino Nano (for the brains), Mirco servo that will attach to the wires. Right now i’ve been designing the shape that i’ll be molding the copper into on OnShape. Seeing how i’ll get everything on there aswell. There will also be LEDs connected to it to give it a futuristic look i’m mixing it also with an older mechanical look. The whole thing will go on a stand you can turn on like a lamp and i am seeing if i make it more complicated by adding a nob for speed and or brightness."}]...
|
Title: Bionic Butterfly by @leonardomflores107 | S Title: Bionic Butterfly by @leonardomflores107 | Stardance
Devlogs:
Devlog 1 Planning and CAD designing. For my project I’m making a butterfly from copper(for the body and wings), thin wire(in order to pull the wings up and down maybe even giving them a wider motion), an Arduino Nano (for the brains), Mirco servo that will attach to the wires. Right now i’ve been designing the shape that i’ll be molding the copper into on OnShape. Seeing how i’ll get everything on there aswell. There will also be LEDs connected to it to give it a futuristic look i’m mixing it also with an older mechanical look. The whole thing will go on a stand you can turn on like a lamp and i am seeing if i make it more complicated by adding a nob for speed and or brightness....
|
1793566455.7551723
|
1794171255.7551723
|
|
1492
|
Graphing Calculator Website by @srikara | Stardanc Graphing Calculator Website by @srikara | Stardance...
|
srikara
|
0
|
16.15
|
0
|
[]
|
[{"post_id": 36324, "ts": "202 [{"post_id": 36324, "ts": "2026-07-28T11:36:01Z", "hours": 16.1531, "text": "Worked on half of the website"}]...
|
Title: Graphing Calculator Website by @srikara | S Title: Graphing Calculator Website by @srikara | Stardance
Devlogs:
Worked on half of the website...
|
1793566454.8287928
|
1794171254.8287928
|
|
58067
|
My own site! by @Sameer23 | Stardance
|
Sameer23
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-05T05:02:33Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made my portfolio. I am just a teenager and a beginner in coding.", "repo": "https://github.com/imskyyyy5/website", "demo": "https://incredible-empanada-52f7da.netlify.app/"}]...
|
[{"post_id": 61459, "ts": "202 [{"post_id": 61459, "ts": "2026-09-04T12:03:04Z", "hours": 0.6878, "text": "My site is finally ready"}]...
|
Title: My own site! by @Sameer23 | Stardance
Devl Title: My own site! by @Sameer23 | Stardance
Devlogs:
My site is finally ready
Ships:
I made my portfolio. I am just a teenager and a beginner in coding....
|
1793566453.6614375
|
1793652853.6614375
|
|
33559
|
Rover by @leojl | Stardance
|
leojl
|
0
|
44.33
|
0
|
[]
|
[{"post_id": 45353, "ts": "202 [{"post_id": 45353, "ts": "2026-08-11T19:06:41Z", "hours": 2.0436, "text": "August 7 & 10 Fully wired new rover including unintentionally learning how to make a motor smoke 💥. Tested all new pieces out and made a program so that every subsystem is controllable from my keyboard The final test day is Wednesday afternoon which is pretty concerning since I just got every part to work and now I need to make it autonomous but just got to believe. Both of these days where pretty lazy but all of Friday was spent wiring everything. The first new thing I tested was the pivot and I didn’t realize that the intake motor would hit the corner so I kept trying to turn it and it drew so many amps that it started to smoke and got incredibly hot. But I just shaved down the chassis and that fixed it. Everything else including the intake and flywheel motors were fine but then the breakout board didn’t work. This was because an aluminum chip had fallen onto the chip on the board and shorted it so I just switched it out. Today was spent troubleshooting errors and really testing everything out with the new wiring. A couple of the problems I faced were because I hadn’t stripped some wires enough so that the splitters I used would work. Also that some wires weren’t long enough so I used extenders. I also used CodeX to help me write some code so that I could control everything from my computer manually."}, {"post_id": 42468, "ts": "2026-08-07T06:58:39Z", "hours": 3.4394, "text": "August 5 & 6 I spent most of Wednesday just waiting for the sheet metal pieces so I thought I’d bundle these two days together Wednesday I finished designing and printing the inner guide rails to funnel the balls into the flywheel. Attached motors, wheels, and pillow bearings to the chassis. Then today I attached the flywheel subsystem to the intake frame which I later mounted onto the chassis through the pivot motor. Before the sheet metal arrived yesterday I spent time finishing the design of the inner guide rails and the arm that would attach to the servo that blocked the balls from escaping through the turned off flywheels as it drives. I got my idea from a pinball arm with a wider rounded back end and a smaller rounder front end so that the tennis balls may not get stuck when they open. This is the only electronic I am left to test. Once the sheet metal arrived I started to attach all wheel motors and wheels to the new chassis. I had to deburr the holes for the motors a bit since they were too small but I got it done before the end of the day. Almost all of today was spending building and assembling. I started by attaching the pivot motor to the chassis and the pillow bearing on the opposite wall. I then mounted the flywheels onto the intake frame and tested them out. They spun pretty fast around 2000 rpm but did have to be angled quite high to launch far. Then I spent a lot of time mounting the intake onto the pivot motor and chassis. I struggled a bit with getting the screws on since there were so small gaps to fit them in. Lastly I mounted the inner guide rails. I then tested the pivot motor at 16rpm and it worked great, being able to turn the whole intake easily and with it locking position when it is not moving. The intake motor though is 80rpm and it is too slow for the intake as it seems to just push away the balls so I bought a 160rpm motor to try and fix that. First thing tomorrow is doing the wiring and putting some rubber on the intake rollers."}, {"post_id": 41157, "ts": "2026-08-05T05:59:49Z", "hours": 0.7667, "text": "August 4 Assembled flywheel shafts, connected flywheel motors to relays, and assembled flywheel structure. Modeled and 3D printed guide rails for the inside of the intake. Disassembled old rover and laid out pieces for new rover. Since all of the parts for the flywheel subsystem finished printing overnight I assembled it first thing today. I got all the bearings, collars, wheels, and pulleys on the shaft and put them onto the top plate. I then soldered both of the motors onto a relay of their own then then the motor negatives onto the battery’s. I had to expand the splitters attached to the batteries so that there would be enough ports to power everything. The sheet metal parts got delayed again and would be complete tommorow and thankfully the test day got moved back for the final time. Honestly this manufacturer the parts have been sent to is not great and I could probably find a better option. Lastly, I finished modeling the guide rails that go inside the intake so that I can attach a servo onto them and have an arm that blocks the balls entering the flywheel before then. I left them 3D printing overnight so that tomorrow I can assemble everything. Tomorrow will be only an assembly day hopefully with a bit more testing the lidar."}, {"post_id": 40609, "ts": "2026-08-04T08:23:57Z", "hours": 7.345, "text": "June 31 & August 3 Didn’t do too much Friday so posted this together Fully finished flywheel and intake CAD. Printed most pieces using PLA and TPU. Assembled Flywheel shafts. Made a basic Lidar program All of Friday was spent finalizing the model for the Flywheel and intake including the top support plate that would hold both Flywheel motors and give the Flywheel shafts a bearing on the top as they have on the bottom. I also started to print most of the small pieces like the shaft collars, inserts for the bearings to make them fit the hex shaft, and spacers for the flywheel shafts. There were some struggles with printing for a bit but I figured out that flow calibration needed to be done every time which wasn’t true before but whatever works works. Since the TPU was even more iffy I only printed two rollers which I left overnight. Monday I was able to talk with a person in the aerospace industry and visited a company nearby which gave me a better idea of what a hard tech company is looking for in applicants. Then I started to assemble the Flywheel shafts though I was missing some 3D printed pieces so I also got everything printed today. But the sheet metal hadn’t arrived so I couldn’t do too much after this so I started to use the lidar. Thankfully the deadline was pushed to tomorrow. I connected the lidar with the Raspberry Pi and used CodeX to help me write a basic program that would display what it sees while excluding a .25 meter range since I just had it in the chassis which was blocking it seeing 360 degrees. In the next few days I hope to integrate this with the camera and IMU to at least get the cone slalom autonomous soon."}, {"post_id": 38046, "ts": "2026-07-31T07:15:19Z", "hours": 4.2669, "text": "June 30 So so close to fully modeling out 3D printed pieces for the Flywheel/Intake Subsystem. 3D printed out some test pieces with slight difficulties. Cut hex shafts semi-straight to length according to the CAD model. Finally ordered 2D Lidar. Like yesterday’s devlog, today was mainly a modeling day with getting the collars, spacers, inserts, and belt pulleys on the shafts. I also designed a top support plate which will also be where the motors are attached, which I’ll work on tomorrow. While I worked on the CAD I had printing some test shaft collars and inserts for the flywheels. Printing these items ultimately was due to how long it would take for real metal ones to ship and with the deadline being tomorrow there wasn’t much time. But there were some issues in printing today possibly due to using brand new filament and I might have refilled it wrong. After fully modeling out how the shaft of the flywheels would look like I cut them out of a stock ½” hex shaft at 4” long each. I also cut out the shafts for the intakes at 8.25” long each. Yet I don’t think it will be done by tomorrow afternoon as I’m still unsure when the cut and bent sheet metal will be done and it will take a while to print every piece needed. Lastly I bought a 2D Lidar so that next week I can give the robot true vision with it being able to always know where the cones are not just based on how tall they are in the video feed."}, {"post_id": 37729, "ts": "2026-07-30T17:13:37Z", "hours": 3.6, "text": "June 29 Almost fully modeled flywheel, adjusted pivot holes, made holes in chassis, ordered chassis and the rest of flywheel parts. Sorry forgot to upload this devlog yesterday Today was only a CAD day. I spent the first few minutes writing down what I needed to model today which included modifying the drivetrain chassis so that the pivot system can be attached and drawing out the holes for the flywheels on the intake so that we can order both pieces. I started by making the holes for the pillow bearings which would be on the opposite side of the pivot motor. Then placed my drawing from yesterday of how the flywheels would look like onto the far end of the intake. I made holes into the intake of where the bearings would go, then added some motor mount holes on the side of it, and finally some holes to add a guide rail inside the intake itself. Also since the flywheels would have a pretty small amount of clearance I added some holes into the wall of the intake to allow for it to increase in diameter when spinning quickly so that it wouldn’t hit the wall. Lastly, I started to fully model what the flywheel would look like including the bearings, shaft, flex wheels, and belt pulleys. I still need to adjust the length of the shaft and get the motors in the right positions. It also needs a few more constraints as seen in the video of it pivoting."}, {"post_id": 36873, "ts": "2026-07-29T07:09:03Z", "hours": 1.3167, "text": "June 28 Plus a 1.5x sped up video from yesterday’s test day with a cool flip Fully printed new wheels and assembled them. Kept modifying IMU dead reckoning program. Modeled and printed motor mounts for flywheel test. I had left printing the three new wheel rims I needed for the new hubs but unfortunately it ran out of black filament half way through the night, so I needed to switch over to gray filament this morning. Eventually they printed and turned out good enough, so I started taking off the old rims from the tires and it was as much of a struggle as putting them on or more. I had to rip off the outer part of the rim but after a couple hours I got them done. The next part that needed some tweaking was the dead reckoning program as like before it lost where it was after not seeing a cone. Today I used CodeX to make it so that the robot keeps tracking where it was using the accelerometer on the IMU to determine where it is from the cones but now it didn’t remember the last distance from the cones before it didn’t see them so it was way off. This is something that will take a lot more modifying with just the IMU and camera so like I said before it might just be easier to get a lidar system, which I’ll think over tomorrow. Lastly, I modeled out how far apart every component of the flywheel system has to be so that tomorrow I can cut holes into an extra piece of sheet metal and model it before ordering the actual sheet metal. Based on the model I 3D printed a motor mount bracket to support where the motor should be. The next test date is this Friday and it will not be moved so the intake, pivot, and flywheels will probably not be completely done by then which sucks."}, {"post_id": 36243, "ts": "2026-07-28T06:26:06Z", "hours": 3.8836, "text": "June 24 & 27 Bought necessary items for flywheels and pivot system. Tested the new IMU to detect distance from the nearest cone by giving it set positions of the cones. Modeled pivot system and ordered more pieces for it. Printed new rims for new hubs. I didn’t do much Friday so I coupled these two together Friday morning was mostly spent buying pieces for the flywheel shooter and pivot system for the intake and flywheels. I bought a strong enough worm gear motor to only use it on one side and just use a bearing on the other side. Since for the flywheels it would be easier for each to have their own motor I bought two 775 DC motors that I would gear down to ~2,000 RPM. Tomorrow I hope to test them. Since the IMU arrived I thought I might be able to use it and set cone coordinates to always have true room coordinates and Dead Reckon on that. A small problem that I encounter right now is that after the cones are out of sight the calculated distance between the IMU and the cone doesn’t change until it sees the cones again. To fix this I might try to get the ratio of what increase of the IMU value is equal to an inch and base it on that or possible by a cheap 2D lidar system. New hubs arrived so I quickly modified the wheel rim CAD and printed them. Now they don’t need as much force to put the tire on. Lastly I designed how and where the high torque worm gear motor would attach onto the intake through hubs and what the other side would look like including pillow bearings and a shaft."}, {"post_id": 34157, "ts": "2026-07-24T17:46:06Z", "hours": 1.1169, "text": "June 23 I know this is a day late, I just forgot to post yesterday. Soldered broken 3 phase motor wire back together. Rearranged electronics and wires to lessen the stress on the wires. Calculated necessary motor strength to pivot the intake mechanism. Again the test date got pushed back a day but this gave more time to fix some issues like the ripped motor wire. I was able to solder it back together by taking the motor apart and finding where the wire broke. I applied some shrinkwrap onto the wire and then a bigger shrinkwrap to join all three wires so that they share the stress if bent. The reason the wired broke was likely due to it rubbing against the back section of the chassis when the front section pivots. I did some wire management so that this wouldn’t happen, which also made the rover look a bit nicer. After a bit of driving the rover making sure that the new wire arrangement worked, I learnt how to calculate torque and how to compare that to servos. Initially I thought that servos would work as the intake would only have to pivot around 30॰, but after the calculations it would be necessary to use a linkage since servos within our price range would be too weak. So I looked into worm gear motors with ultra low rpm, around 15 rpm, which would hopefully provide enough torque to rotate the intake. The test date also got pushed to tomorrow so the IMU, which arrives tomorrow, would give us a better way to dead reckon."}, {"post_id": 33366, "ts": "2026-07-23T07:07:01Z", "hours": 1.3167, "text": "June 22 Added more support braces to metal chassis. Rearranged electronics to make room for an intake and worked on autonomous cone slalom. One wire of a wheel motor tore off and needs to be replaced or repaired. From yesterday’s few tests driving the rover at speeds above 25% the chassis seemed to bend inwards, especially with the new 8” inch wheels. So I designed braces that would go on the back section of the chassis and made a piece to link both L- support braces. While the supports printed I rearranged the electronics onto most one side of the chassis in order to fit the intake in the middle. Since the next test date got moved to Thursday I had more time to try and get the rover to do the cone slalom autonomously. A majority of the time spent was adjusting values like what percentage of the cone should be on the screen before it stopped turning. I later decided after a couple hours of not much luck to switch over to dead reckoning. I had CodeX make me a program to record and replay inputs which worked semi consistently but varied a lot since I couldn’t start the rover in the exact same position. After running the dead reckoning multiple times I saw that one wheel wasn’t really spinning. I looked into this and realized that one of the 3 phase motor wires has come off the motor. I’ll try and repair it tomorrow but it may not be possible. So for Thursday the rover might just need to run off three motors"}, {"post_id": 32825, "ts": "2026-07-22T06:57:21Z", "hours": 5.3867, "text": "June 21 The slight shift of the hubs from the motor shaft was troubleshooted for the first half of the day. The second half was spent working on the autonomous slalom through cones, with it being able to go around one for now. I started off the day by assessing what had gone wrong previously and found that I should focus on the wheels slipping off the motor shaft if I wanted the rover to clear the obstacle course and hill by Wednesday. I spent a lot of my time designing new hubs but I found that the main issue for why the hubs slipped off was that the Loctite on the screw holes had not dried yet. So I wasted too much time on this but I did learn how to make drawings to send to manufacturers. The second half of the day was spent using CodeX to make a program to go around the cone with a camera attached to the Raspberry Pi. A majority of this process was testing values like what percentage or where on the screen the cone should be in order to start turning. I was eventually able to get it to go around one cone but it would target the third cone in the slalom before the second one. I definitely want to work more on this tomorrow. Another task for tomorrow is designing and printing support braces for the aluminum chassis which saw some bending especially when turning. (I made the turning back to standard tank drive as the set screws were as big of an issue)"}, {"post_id": 29766, "ts": "2026-07-16T21:15:33Z", "hours": 9.8508, "text": "Rover V1 Features - Metal Chassis The chassis is made up of .06-inch aluminum cut in 4 pieces and a central connector so that the position of the front two wheels can rotate when only one wheel drives over an obstacle. The back section is riveted together connecting the two L-channels with a top plate and pillow bearings and a shaft are used to connect the front and back section. - Wheels The rim of the wheels are fully 3D printed and are modified GoBilda Rhino Wheels upscaled to approximately 5 inches in diameter. 3D printing allowed for the wheel to slide on easily as the modified hole would easily fit onto the shaft of the motor. Neoprene rubber was then glued onto the outside of the wheel to provide friction and grip when driving up a flat angled hill. Each wheel is directly connected to a motor. -Power System The Raspberry Pi 5 is powered using a portable battery pack, while the motors are powered using a 14V 4S LiPo battery. Using a power splitter, all four ESCs, each connected to a motor, are connected to the Pi using a PCA9685 breakout board. The breakout board’s logic is powered by the Raspberry Pi. -Software (Done completely by AI) The rover is controlled using the keyboard of a computer connected to the Raspberry Pi. It is currently configured to tank drive with configurable throttle by sending different signals to the ESCs. -Housings Each electronic component has its own 3D printed housing with access to the necessary ports so that the pins do not directly touch the metal chassis. Issues & Fixes -The ESCs purchased are unidirectional and therefore the rover is not able to drive backwards and turning is really wide Bidirectional ESCs have been bought and should allow for a true tank drive -Since the motors spin really fast, the inner part of the 3D printed wheel has loosened and now practically free spins on the motor shaft as the PLA is really weak and has shaved down. Metal hubs will be screwed into the new printed wheels so that it will not matter whether it shaves off some of the plastic due to the fast rotation. This will require reprinting the wheels with holes in them that align with the hub. -Since the course is really dusty, the rubber on the tires picked it all up. This reduced the friction on the wheels and did not allow the rover to drive up a steep hill. New bigger treaded tires that have to be inflated and are made of a different material should lessen this issue. The inner rim would have to be remodeled to fit these new tires. -The front U-shaped piece where the front two motors are attached is thin and flimsy, so the wheels bow out and affect the angle at which the wheel hits the floor. 3D printed brackets in the corners give stability to the chassis so that it does not bend. Next Subsystem -Intake & Outtake It will use multiple rows of rollers that push the balls further back into the rover where they will eventually funnel into a fast-spinning flywheel. This subsystem will be able to pivot using a motor in order to increase the angle at which the ball is launched at. -Elevation This is still unconfirmed, but one possibility is using switchable magnets in order to climb on a magnetic pole. Another possibility is using a cascade lift attached to the pivoting intake to raise a hook and then pull itself up."}]...
|
Title: Rover by @leojl | Stardance
Devlogs:
Rover Title: Rover by @leojl | Stardance
Devlogs:
Rover V1 Features - Metal Chassis The chassis is made up of .06-inch aluminum cut in 4 pieces and a central connector so that the position of the front two wheels can rotate when only one wheel drives over an obstacle. The back section is riveted together connecting the two L-channels with a top plate and pillow bearings and a shaft are used to connect the front and back section. - Wheels The rim of the wheels are fully 3D printed and are modified GoBilda Rhino Wheels upscaled to approximately 5 inches in diameter. 3D printing allowed for the wheel to slide on easily as the modified hole would easily fit onto the shaft of the motor. Neoprene rubber was then glued onto the outside of the wheel to provide friction and grip when driving up a flat angled hill. Each wheel is directly connected to a motor. -Power System The Raspberry Pi 5 is powered using a portable battery pack, while the motors are powered using a 14V 4S LiPo battery. Using a power splitter, all four ESCs, each connected to a motor, are connected to the Pi using a PCA9685 breakout board. The breakout board’s logic is powered by the Raspberry Pi. -Software (Done completely by AI) The rover is controlled using the keyboard of a computer connected to the Raspberry Pi. It is currently configured to tank drive with configurable throttle by sending different signals to the ESCs. -Housings Each electronic component has its own 3D printed housing with access to the necessary ports so that the pins do not directly touch the metal chassis. Issues & Fixes -The ESCs purchased are unidirectional and therefore the rover is not able to drive backwards and turning is really wide Bidirectional ESCs have been bought and should allow for a true tank drive -Since the motors spin really fast, the inner part of the 3D printed wheel has loosened and now practically free spins on the motor shaft as the PLA is really weak and has shaved down. Metal hubs will be screwed into the new printed wheels so that it will not matter whether it shaves off some of the plastic due to the fast rotation. This will require reprinting the wheels with holes in them that align with the hub. -Since the course is really dusty, the rubber on the tires picked it all up. This reduced the friction on the wheels and did not allow the rover to drive up a steep hill. New bigger treaded tires that have to be inflated and are made of a different material should lessen this issue. The inner rim would have to be remodeled to fit these new tires. -The front U-shaped piece where the front two motors are attached is thin and flimsy, so the wheels bow out and affect the angle at which the wheel hits the floor. 3D printed brackets in the corners give stability to the chassis so that it does not bend. Next Subsystem -Intake & Outtake It will use multiple rows of rollers that push the balls further back into the rover where they will eventually funnel into a fast-spinning flywheel. This subsystem will be able to pivot using a motor in order to increase the angle at which the ball is launched at. -Elevation This is still unconfirmed, but one possibility is using switchable magnets in order to climb on a magnetic pole. Another possibility is using a cascade lift attached to the pivoting intake to raise a hook and then pull itself up.
June 21 The slight shift of the hubs from the motor shaft was troubleshooted for the first half of the day. The second half was spent working on the autonomous slalom through cones, with it being able to go around one for now. I started off the day by assessing what had gone wrong previously and found that I should focus on the wheels slipping off the motor shaft if I wanted the rover to clear the obstacle course and hill by Wednesday. I spent a lot of my time designing new hubs but I found that the main issue for why the hubs slipped off was that the Loctite on the screw holes had not dried yet. So I wasted too much time on this but I did learn how to make drawings to send to manufacturers. The second half of the day was spent using CodeX to make a program to go around the cone with a camera attached to the Raspberry Pi. A majority of this process was testing values like what percentage or where on the screen the cone should be in order to start turning. I was eventually able to get it to go around one cone but it would target the third cone in the slalom before the second one. I definitely want to work more on this tomorrow. Another task for tomorrow is designing and printing support braces for the aluminum chassis which saw some bending especially when turning. (I made the turning back to standard tank drive as the set screws were as big of an issue)
June 22 Added more support braces to metal chassis. Rearranged electronics to make room for an intake and worked on autonomous cone slalom. One wire of a wheel motor tore off and needs to be replaced or repaired. From yesterday’s few tests driving the rover at speeds above 25% the chassis seemed to bend inwards, especially with the new 8” inch wheels. So I designed braces that would go on the back section of the chassis and made a piece to link both L- support braces. While the supports printed I rearranged the electronics onto most one side of the chassis in order to fit the intake in the middle. Since the next test date got moved to Thursday I had more time to try and get the rover to do the cone slalom autonomously. A majority of the time spent was adjusting values like what percentage of the cone should be on the screen before it stopped turning. I later decided after a couple hours of not much luck to switch over to dead reckoning. I had CodeX make me a program to record and replay inputs which worked semi consistently but varied a lot since I couldn’t start the rover in the exact same position. After running the dead reckoning multiple times I saw that one wheel wasn’t really spinning. I looked into this and realized that one of the 3 phase motor wires has come off the motor. I’ll try and repair it tomorrow but it may not be possible. So for Thursday the rover might just need to run off three motors
June 23 I know this is a day late, I just forgot to post yesterday. Soldered broken 3 phase motor wire back together. Rearranged electronics and wires to lessen the stress on the wires. Calculated necessary motor strength to pivot the intake mechanism. Again the test date got pushed back a day but this gave more time to fix some issues like the ripped motor wire. I was able to solder it back together by taking the motor apart and finding where the wire broke. I applied some shrinkwrap onto the wire and then a bigger shrinkwrap to join all three wires so that they share the stress if bent. The reason the wired broke was likely due to it rubbing against the back section of the chassis when the front section pivots. I did some wire management so that this wouldn’t happen, which also made the rover look a bit nicer. After a bit of driving the rover making sure that the new wire arrangement worked, I learnt how to calculate torque and how to compare that to servos. Initially I thought that servos would work as the intake would only have to pivot around 30॰, but after the calculations it would be necessary to use a linkage since servos within our price range would be too weak. So I looked into worm gear motors with ultra low rpm, around 15 rpm, which would hopefully provide enough torque to rotate the intake. The test date also got pushed to tomorrow so the IMU, which arrives tomorrow, would give us a better way to dead reckon.
June 24 & 27 Bought necessary items for flywheels and pivot system. Tested the new IMU to detect distance from the nearest cone by giving it set positions of the cones. Modeled pivot system and ordered more pieces for it. Printed new rims for new hubs. I didn’t do much Friday so I coupled these two together Friday morning was mostly spent buying pieces for the flywheel shooter and pivot system for the intake and flywheels. I bought a strong enough worm gear motor to only use it on one side and just use a bearing on the other side. Since for the flywheels it would be easier for each to have their own motor I bought two 775 DC motors that I would gear down to ~2,000 RPM. Tomorrow I hope to test them. Since the IMU arrived I thought I might be able to use it and set cone coordinates to always have true room coordinates and Dead Reckon on that. A small problem that I encounter right now is that after the cones are out of sight the calculated distance between the IMU and the cone doesn’t change until it sees the cones again. To fix this I might try to get the ratio of what increase of the IMU value is equal to an inch and base it on that or possible by a cheap 2D lidar system. New hubs arrived so I quickly modified the wheel rim CAD and printed them. Now they don’t need as much force to put the tire on. Lastly I designed how and where the high torque worm gear motor would attach onto the intake through hubs and what the other side would look like including pillow bearings and a shaft.
June 28 Plus a 1.5x sped up video from yesterday’s test day with a cool flip Fully printed new wheels and assembled them. Kept modifying IMU dead reckoning program. Modeled and printed motor mounts for flywheel test. I had left printing the three new wheel rims I needed for the new hubs but unfortunately it ran out of black filament half way through the night, so I needed to switch over to gray filament this morning. Eventually they printed and turned out good enough, so I started taking off the old rims from the tires and it was as much of a struggle as putting them on or more. I had to rip off the outer part of the rim but after a couple hours I got them done. The next part that needed some tweaking was the dead reckoning program as like before it lost where it was after not seeing a cone. Today I used CodeX to make it so that the robot keeps tracking where it was using the accelerometer on the IMU to determine where it is from the cones but now it didn’t remember the last distance from the cones before it didn’t see them so it was way off. This is something that will take a lot more modifying with just the IMU and camera so like I said before it might just be easier to get a lidar system, which I’ll think over tomorrow. Lastly, I modeled out how far apart every component of the flywheel system has to be so that tomorrow I can cut holes into an extra piece of sheet metal and model it before ordering the actual sheet metal. Based on the model I 3D printed a motor mount bracket to support where the motor should be. The next test date is this Friday and it will not be moved so the intake, pivot, and flywheels will probably not be completely done by then which sucks.
June 29 Almost fully modeled flywheel, adjusted pivot holes, made holes in chassis, ordered chassis and the rest of flywheel parts. Sorry forgot to upload this devlog yesterday Today was only a CAD day. I spent the first few minutes writing down what I needed to model today which included modifying the drivetrain chassis so that the pivot system can be attached and drawing out the holes for the flywheels on the intake so that we can order both pieces. I started by making the holes for the pillow bearings which would be on the opposite side of the pivot motor. Then placed my drawing from yesterday of how the flywheels would look like onto the far end of the intake. I made holes into the intake of where the bearings would go, then added some motor mount holes on the side of it, and finally some holes to add a guide rail inside the intake itself. Also since the flywheels would have a pretty small amount of clearance I added some holes into the wall of the intake to allow for it to increase in diameter when spinning quickly so that it wouldn’t hit the wall. Lastly, I started to fully model what the flywheel would look like including the bearings, shaft, flex wheels, and belt pulleys. I still need to adjust the length of the shaft and get the motors in the right positions. It also needs a few more constraints as seen in the video of it pivoting.
June 30 So so close to fully modeling out 3D printed pieces for the Flywheel/Intake Subsystem. 3D printed out some test pieces with slight difficulties. Cut hex shafts semi-straight to length according to the CAD model. Finally ordered 2D Lidar. Like yesterday’s devlog, today was mainly a modeling day with getting the collars, spacers, inserts, and belt pulleys on the shafts. I also designed a top support plate which will also be where the motors are attached, which I’ll work on tomorrow. While I worked on the CAD I had printing some test shaft collars and inserts for the flywheels. Printing these items ultimately was due to how long it would take for real metal ones to ship and with the deadline being tomorrow there wasn’t much time. But there were some issues in printing today possibly due to using brand new filament and I might have refilled it wrong. After fully modeling out how the shaft of the flywheels would look like I cut them out of a stock ½” hex shaft at 4” long each. I also cut out the shafts for the intakes at 8.25” long each. Yet I don’t think it will be done by tomorrow afternoon as I’m still unsure when the cut and bent sheet metal will be done and it will take a while to print every piece needed. Lastly I bought a 2D Lidar so that next week I can give the robot true vision with it being able to always know where the cones are not just based on how tall they are in the video feed.
June 31 & August 3 Didn’t do too much Friday so posted this together Fully finished flywheel and intake CAD. Printed most pieces using PLA and TPU. Assembled Flywheel shafts. Made a basic Lidar program All of Friday was spent finalizing the model for the Flywheel and intake including the top support plate that would hold both Flywheel motors and give the Flywheel shafts a bearing on the top as they have on the bottom. I also started to print most of the small pieces like the shaft collars, inserts for the bearings to make them fit the hex shaft, and spacers for the flywheel shafts. There were some struggles with printing for a bit but I figured out that flow calibration needed to be done every time which wasn’t true before but whatever works works. Since the TPU was even more iffy I only printed two rollers which I left overnight. Monday I was able to talk with a person in the aerospace industry and visited a company nearby which gave me a better idea of what a hard tech company is looking for in applicants. Then I started to assemble the Flywheel shafts though I was missing some 3D printed pieces so I also got everything printed today. But the sheet metal hadn’t arrived so I couldn’t do too much after this so I started to use the lidar. Thankfully the deadline was pushed to tomorrow. I connected the lidar with the Raspberry Pi and used CodeX to help me write a basic program that would display what it sees while excluding a .25 meter range since I just had it in the chassis which was blocking it seeing 360 degrees. In the next few days I hope to integrate this with the camera and IMU to at least get the cone slalom autonomous soon.
August 4 Assembled flywheel shafts, connected flywheel motors to relays, and assembled flywheel structure. Modeled and 3D printed guide rails for the inside of the intake. Disassembled old rover and laid out pieces for new rover. Since all of the parts for the flywheel subsystem finished printing overnight I assembled it first thing today. I got all the bearings, collars, wheels, and pulleys on the shaft and put them onto the top plate. I then soldered both of the motors onto a relay of their own then then the motor negatives onto the battery’s. I had to expand the splitters attached to the batteries so that there would be enough ports to power everything. The sheet metal parts got delayed again and would be complete tommorow and thankfully the test day got moved back for the final time. Honestly this manufacturer the parts have been sent to is not great and I could probably find a better option. Lastly, I finished modeling the guide rails that go inside the intake so that I can attach a servo onto them and have an arm that blocks the balls entering the flywheel before then. I left them 3D printing overnight so that tomorrow I can assemble everything. Tomorrow will be only an assembly day hopefully with a bit more testing the lidar.
August 5 & 6 I spent most of Wednesday just waiting for the sheet metal pieces so I thought I’d bundle these two days together Wednesday I finished designing and printing the inner guide rails to funnel the balls into the flywheel. Attached motors, wheels, and pillow bearings to the chassis. Then today I attached the flywheel subsystem to the intake frame which I later mounted onto the chassis through the pivot motor. Before the sheet metal arrived yesterday I spent time finishing the design of the inner guide rails and the arm that would attach to the servo that blocked the balls from escaping through the turned off flywheels as it drives. I got my idea from a pinball arm with a wider rounded back end and a smaller rounder front end so that the tennis balls may not get stuck when they open. This is the only electronic I am left to test. Once the sheet metal arrived I started to attach all wheel motors and wheels to the new chassis. I had to deburr the holes for the motors a bit since they were too small but I got it done before the end of the day. Almost all of today was spending building and assembling. I started by attaching the pivot motor to the chassis and the pillow bearing on the opposite wall. I then mounted the flywheels onto the intake frame and tested them out. They spun pretty fast around 2000 rpm but did have to be angled quite high to launch far. Then I spent a lot of time mounting the intake onto the pivot motor and chassis. I struggled a bit with getting the screws on since there were so small gaps to fit them in. Lastly I mounted the inner guide rails. I then tested the pivot motor at 16rpm and it worked great, being able to turn the whole intake easily and with it locking position when it is not moving. The intake motor though is 80rpm and it is too slow for the intake as it seems to just push away the balls so I bought a 160rpm motor to try and fix that. First thing tomorrow is doing the wiring and putting some rubber on the intake rollers.
August 7 & 10 Fully wired new rover including unintentionally learning how to make a motor smoke 💥. Tested all new pieces out and made a program so that every subsystem is controllable from my keyboard The final test day is Wednesday afternoon which is pretty concerning since I just got every part to work and now I need to make it autonomous but just got to believe. Both of these days where pretty lazy but all of Friday was spent wiring everything. The first new thing I tested was the pivot and I didn’t realize that the intake motor would hit the corner so I kept trying to turn it and it drew so many amps that it started to smoke and got incredibly hot. But I just shaved down the chassis and that fixed it. Everything else including the intake and flywheel motors were fine but then the breakout board didn’t work. This was because an aluminum chip had fallen onto the chip on the board and shorted it so I just switched it out. Today was spent troubleshooting errors and really testing everything out with the new wiring. A couple of the problems I faced were because I hadn’t stripped some wires enough so that the splitters I used would work. Also that some wires weren’t long enough so I used extenders. I also used CodeX to help me write some code so that I could control everything from my computer manually....
|
1793566452.3771503
|
1794171252.3771503
|
|
14567
|
Escape Space! by @random_user | Stardance
|
random_user
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Escape Space! by @random_user | Stardance
|
1793566450.1096003
|
1794171250.1096003
|
|
33979
|
CleanDrop by @omarhossdev | Stardance
|
omarhossdev
|
0
|
2.08
|
0
|
[]
|
[{"post_id": 31458, "ts": "202 [{"post_id": 31458, "ts": "2026-07-19T20:40:57Z", "hours": 0.7442, "text": "Devlog 2: Beautiful sharing Form I designed a beautiful form to upload a file and share it. The form is not fully functional yet but I’m gonna finish it soon to be ready for production, till now it just redirects to a new dynamic page which will be used later to share the file between devices :) I also plan to create a label for password instead of keeping it floated, I think that would be better. Next Step Add form validation Store the encrypted password in user’s storage Ask for password when someone visits this link Create a private secure room using PeerJS between devices who are connected with password Add password try limits to 3, so if someone entered the password wrong in the dynamic page then he should be banned from it. Stay Tuned 🚀"}, {"post_id": 31327, "ts": "2026-07-19T17:02:45Z", "hours": 1.3367, "text": "Devlog #1: Launching CleanDrop The Big Idea I am building CleanDrop, which is a web app that let’s you send files from device to another even beyond the borders just using a web browser 🫰. The main goal is to let people share files for fully free with privacy between devices. Why I’m building this Sharing a high-quality video or photo between an iPhone and a Windows PC, or an Android and a Mac, is a nightmare. AirDrop only loves Apple devices. Quick Share is built for Android and Windows. Mainstream options (like emailing yourself or uploading to WhatsApp) crush your files, ruining the quality with heavy compression. We shouldn’t have to sign up for cloud storage subscriptions just to move a file across our own desks or to our friends. Also when using current popular tools our data is on a centralized server… which is a big deal for privacy. More features are coming ..🤫 My Tech Stack Frontend Framework: Preact.js (A feather-light, high-performance alternative to React) Language: TypeScript (For safe, robust, and bug-free code) Styling: Tailwind CSS (For a highly polished, gorgeous consumer-grade UI) Routing: Preact Iso (A tiny, preact router) Signaling Server: Hono on Node.js/Bun (For lightning-fast WebSocket rooms) P2P Engine: PeerJS (Simplifying WebRTC data channels) Why this? Because I want to make sure the website works same everywhere on all devices either it’s old OR modern. What I Got Done Till Now Repo created and pushed to GitHub. Split the frontend (port 5173) and the backend (port 3000) in folders Implement WebSocket foundation in Hono Connect the client (frontend) with WebSocket Test it with multiple clients What’s Next 🎯 I will start implementing PeerJS to bridge the clients together and establish our very first secure, peer-to-peer data channel. Stay updated! 🚀"}]...
|
Title: CleanDrop by @omarhossdev | Stardance
Devl Title: CleanDrop by @omarhossdev | Stardance
Devlogs:
Devlog #1: Launching CleanDrop The Big Idea I am building CleanDrop, which is a web app that let’s you send files from device to another even beyond the borders just using a web browser 🫰. The main goal is to let people share files for fully free with privacy between devices. Why I’m building this Sharing a high-quality video or photo between an iPhone and a Windows PC, or an Android and a Mac, is a nightmare. AirDrop only loves Apple devices. Quick Share is built for Android and Windows. Mainstream options (like emailing yourself or uploading to WhatsApp) crush your files, ruining the quality with heavy compression. We shouldn’t have to sign up for cloud storage subscriptions just to move a file across our own desks or to our friends. Also when using current popular tools our data is on a centralized server… which is a big deal for privacy. More features are coming ..🤫 My Tech Stack Frontend Framework: Preact.js (A feather-light, high-performance alternative to React) Language: TypeScript (For safe, robust, and bug-free code) Styling: Tailwind CSS (For a highly polished, gorgeous consumer-grade UI) Routing: Preact Iso (A tiny, preact router) Signaling Server: Hono on Node.js/Bun (For lightning-fast WebSocket rooms) P2P Engine: PeerJS (Simplifying WebRTC data channels) Why this? Because I want to make sure the website works same everywhere on all devices either it’s old OR modern. What I Got Done Till Now Repo created and pushed to GitHub. Split the frontend (port 5173) and the backend (port 3000) in folders Implement WebSocket foundation in Hono Connect the client (frontend) with WebSocket Test it with multiple clients What’s Next 🎯 I will start implementing PeerJS to bridge the clients together and establish our very first secure, peer-to-peer data channel. Stay updated! 🚀
Devlog 2: Beautiful sharing Form I designed a beautiful form to upload a file and share it. The form is not fully functional yet but I’m gonna finish it soon to be ready for production, till now it just redirects to a new dynamic page which will be used later to share the file between devices :) I also plan to create a label for password instead of keeping it floated, I think that would be better. Next Step Add form validation Store the encrypted password in user’s storage Ask for password when someone visits this link Create a private secure room using PeerJS between devices who are connected with password Add password try limits to 3, so if someone entered the password wrong in the dynamic page then he should be banned from it. Stay Tuned 🚀...
|
1793566447.931493
|
1794171247.931493
|
|
40343
|
Personal Website by @kripusek | Stardance
|
kripusek
|
2
|
1.33
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-28T13:44:17Z", "hours": 0.0, "multiplier": 1.12, "payout": 0, "blessing": "neutral", "text": "edited the readme so it actually matters now, it seems I have shipped it a second time before but it must have glitched and not shipped", "repo": "https://github.com/kripusek/stardance-personal-site", "demo": "https://kripusek.github.io/stardance-personal-site/"}, {"ship_num": 2, "ts": "2026-07-27T18:03:25Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a personal website. It was Very Very fun but also pretty challenging. It definitly was a learning experience for me.", "repo": "https://github.com/kripusek/stardance-personal-site", "demo": "https://kripusek.github.io/stardance-personal-site/"}]...
|
[{"post_id": 38926, "ts": "202 [{"post_id": 38926, "ts": "2026-08-01T15:00:40Z", "hours": 0.3333, "text": "I have added more ways to contact me on my website (:"}, {"post_id": 36311, "ts": "2026-07-28T10:54:14Z", "hours": 0.2678, "text": "Quick fix for the website, I have expanded my README and I have added a footer on the bottom of the website"}, {"post_id": 35920, "ts": "2026-07-27T17:51:39Z", "hours": 1.2881, "text": "I think I might have finished the website :D"}]...
|
Title: Personal Website by @kripusek | Stardance
Title: Personal Website by @kripusek | Stardance
Devlogs:
I think I might have finished the website :D
Quick fix for the website, I have expanded my README and I have added a footer on the bottom of the website
I have added more ways to contact me on my website (:
Ships:
I made a personal website. It was Very Very fun but also pretty challenging. It definitly was a learning experience for me.
edited the readme so it actually matters now, it seems I have shipped it a second time before but it must have glitched and not shipped...
|
1793566446.7317917
|
1793652846.7317917
|
|
10670
|
My awesome macropad! by @soraitsuri | Stardance
|
soraitsuri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @soraitsuri | Stard Title: My awesome macropad! by @soraitsuri | Stardance...
|
1793566442.445416
|
1794171242.445416
|
|
59589
|
grandMA/MagicQ macro pad by @Lexy | Stardance
|
Lexy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: grandMA/MagicQ macro pad by @Lexy | Stardan Title: grandMA/MagicQ macro pad by @Lexy | Stardance...
|
1793566441.5524719
|
1794171241.5524719
|
|
3451
|
Desmos Art by @haz | Stardance
|
haz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Desmos Art by @haz | Stardance
|
1793566440.6380944
|
1794171240.6380944
|
|
59588
|
My awesome macropad! by @tasnime | Stardance
|
tasnime
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tasnime | Stardanc Title: My awesome macropad! by @tasnime | Stardance...
|
1793566439.7368772
|
1794171239.7368772
|
|
55029
|
My awesome macropad! by @Akshobhya | Stardance
|
Akshobhya
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-25T14:08:33Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a Macropad. This was the very first time I am doing something", "repo": "https://github.com/Akshu307-afk/HackPad-Macropad", "demo": ""}]...
|
[{"post_id": 81849, "ts": "202 [{"post_id": 81849, "ts": "2026-10-22T18:33:07Z", "hours": 3.4594, "text": "I just finished my rep and the firmware."}, {"post_id": 81778, "ts": "2026-10-22T13:42:33Z", "hours": 0.4581, "text": "I am currently working on HackPad. I have completed the PCB design, 3d Model and the firmware."}]...
|
Title: My awesome macropad! by @Akshobhya | Starda Title: My awesome macropad! by @Akshobhya | Stardance
Devlogs:
I am currently working on HackPad. I have completed the PCB design, 3d Model and the firmware.
I just finished my rep and the firmware.
Ships:
I made a Macropad. This was the very first time I am doing something...
|
1793566438.5715582
|
1793652838.5715582
|
|
59587
|
High Powered Rocket by @HudsonRR | Stardance
|
HudsonRR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: High Powered Rocket by @HudsonRR | Stardanc Title: High Powered Rocket by @HudsonRR | Stardance...
|
1793566437.662401
|
1794171237.662401
|
|
18349
|
Emu2Pwn by @CloverTech1105 | Stardance
|
CloverTech1105
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Emu2Pwn by @CloverTech1105 | Stardance
|
1793566436.7829852
|
1794171236.7829852
|
|
59585
|
PantheonYAML by @Minetrio1256 | Stardance
|
Minetrio1256
|
0
|
1.39
|
0
|
[]
|
[{"post_id": 65671, "ts": "202 [{"post_id": 65671, "ts": "2026-09-10T23:43:13Z", "hours": 0.3531, "text": "Devlog #3 Project elements loading"}, {"post_id": 65087, "ts": "2026-09-09T23:42:12Z", "hours": 0.395, "text": "Devlog #2 I added the projects parser. A project is a collection of elements under a namespace. It currently stores configured projects to be loaded. Next step is loading the project-elements.yaml of each project which contains the paths for each type of element to be loaded, note that this is being done in the bootstrap phase for registry access."}, {"post_id": 64500, "ts": "2026-09-08T22:57:46Z", "hours": 0.6428, "text": "Devlog #1 the following screenshot contains what I plan to implement to be able to be loaded via YAML"}]...
|
Title: PantheonYAML by @Minetrio1256 | Stardance
Title: PantheonYAML by @Minetrio1256 | Stardance
Devlogs:
Devlog #1 the following screenshot contains what I plan to implement to be able to be loaded via YAML
Devlog #2 I added the projects parser. A project is a collection of elements under a namespace. It currently stores configured projects to be loaded. Next step is loading the project-elements.yaml of each project which contains the paths for each type of element to be loaded, note that this is being done in the bootstrap phase for registry access.
Devlog #3 Project elements loading...
|
1793566435.8593905
|
1794171235.8593905
|
|
59584
|
My awesome macropad! by @Kratharth024 | Stardance
|
Kratharth024
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Kratharth024 | Sta Title: My awesome macropad! by @Kratharth024 | Stardance...
|
1793566434.9816813
|
1794171234.9816813
|
|
59582
|
Bookworm by @maram_heikal | Stardance
|
maram_heikal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Bookworm by @maram_heikal | Stardance
|
1793566434.1142852
|
1794171234.1142852
|
|
59581
|
Sam by @SmarakMahiuddin | Stardance
|
SmarakMahiuddin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Sam by @SmarakMahiuddin | Stardance
|
1793566433.2018785
|
1794171233.2018785
|
|
4162
|
zkFog: Referee-Less Fog of War Chess by @kev | Sta zkFog: Referee-Less Fog of War Chess by @kev | Stardance...
|
kev
|
0
|
1.77
|
0
|
[]
|
[{"post_id": 44259, "ts": "202 [{"post_id": 44259, "ts": "2026-08-09T21:49:26Z", "hours": 1.7703, "text": "Hey Hack Clubbers! I’m building zkFog , a website that lets you play fog-of-war chess without a trusted server. In fog chess you only see the squares your pieces can move to, and normally a server hides the rest of the board and everyone trusts it. I’m replacing that server with zero-knowledge proofs so that each player’s view is secret to only them, not even the server, and cryptography proves that the moves are legal. ~2 hours in: built a 6x6 Los Alamos chess UI to keep implementation simple for now. Using Bun + Vite + Biome , and chessgroundx for the UI. I also added a bit of CSS to emulate the snappiness of chess.com’s UI. I’ve also coded from scratch the engine that determines move legality (the dots that show up when you drag a piece)."}]...
|
Title: zkFog: Referee-Less Fog of War Chess by @ke Title: zkFog: Referee-Less Fog of War Chess by @kev | Stardance
Devlogs:
Hey Hack Clubbers! I’m building zkFog , a website that lets you play fog-of-war chess without a trusted server. In fog chess you only see the squares your pieces can move to, and normally a server hides the rest of the board and everyone trusts it. I’m replacing that server with zero-knowledge proofs so that each player’s view is secret to only them, not even the server, and cryptography proves that the moves are legal. ~2 hours in: built a 6x6 Los Alamos chess UI to keep implementation simple for now. Using Bun + Vite + Biome , and chessgroundx for the UI. I also added a bit of CSS to emulate the snappiness of chess.com’s UI. I’ve also coded from scratch the engine that determines move legality (the dots that show up when you drag a piece)....
|
1793566432.2969542
|
1794171232.2969542
|
|
59580
|
My awesome macropad! by @chetan_devabhaktuni | Sta My awesome macropad! by @chetan_devabhaktuni | Stardance...
|
chetan_devabhaktuni
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @chetan_devabhaktun Title: My awesome macropad! by @chetan_devabhaktuni | Stardance...
|
1793566431.4011538
|
1794171231.4011538
|
|
35672
|
My own site! by @UN1V3RSE | Stardance
|
UN1V3RSE
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @UN1V3RSE | Stardance
|
1793566430.4973676
|
1794171230.4973676
|
|
45886
|
DeskPet by @Cherish9 | Stardance
|
Cherish9
|
1
|
7.08
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-19T14:27:53Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Building a smart “DeskPet” companion with Arduino & Python! It tracks my daily water intake, monitors room temperature and humidity to tell me when to open a window, and keeps my desk healthy.", "repo": "https://github.com/Cherish-everything/DeskPet-A-well-being-assistant", "demo": ""}]...
|
[{"post_id": 76106, "ts": "202 [{"post_id": 76106, "ts": "2026-10-02T10:22:33Z", "hours": 1.9503, "text": "Build an enclosure on freecad! Honestly it was my first time building an enclosure with the pcb model, it wasn’t too bad actually. And I’m getting used to cad now. My next update would be probably cleaning up my code and organizing my repository for this"}, {"post_id": 75830, "ts": "2026-10-01T08:53:01Z", "hours": 1.1331, "text": "I’m working on a schematic for deskpet, this is like my second PCB design project, next session I will work on the pcb itself!"}, {"post_id": 50326, "ts": "2026-08-19T14:26:25Z", "hours": 0.31, "text": "Just logging the time I spent debugging a bit and documenting the project for the demo video"}, {"post_id": 47404, "ts": "2026-08-15T10:00:45Z", "hours": 1.3736, "text": "I’m finalizing my deskpet v1: just a simple working prototype since this project is intended as a learning project so I won’t expand on it too much. Today I got it to take water intake logs through a button you press and it reminds you to open a window or drink water while you’re working. Initially wanted to add a screen but I ran out of jumper wires:/ Flipping hell I missspelled deskpet on lapse so the hardware part isn’t recorded aka about 15 minutes of me debugging a button only to find out it was faulty"}, {"post_id": 44463, "ts": "2026-08-10T07:13:46Z", "hours": 1.0239, "text": "Tried adding music to the buzzer lol and added a water sensor to remind to drink"}, {"post_id": 43814, "ts": "2026-08-09T07:47:40Z", "hours": 0.9183, "text": "The code + prototype circuit. My first time using these sensors for an actual project!"}]...
|
Title: DeskPet by @Cherish9 | Stardance
Devlogs:
Title: DeskPet by @Cherish9 | Stardance
Devlogs:
The code + prototype circuit. My first time using these sensors for an actual project!
Tried adding music to the buzzer lol and added a water sensor to remind to drink
I’m finalizing my deskpet v1: just a simple working prototype since this project is intended as a learning project so I won’t expand on it too much. Today I got it to take water intake logs through a button you press and it reminds you to open a window or drink water while you’re working. Initially wanted to add a screen but I ran out of jumper wires:/ Flipping hell I missspelled deskpet on lapse so the hardware part isn’t recorded aka about 15 minutes of me debugging a button only to find out it was faulty
Just logging the time I spent debugging a bit and documenting the project for the demo video
I’m working on a schematic for deskpet, this is like my second PCB design project, next session I will work on the pcb itself!
Build an enclosure on freecad! Honestly it was my first time building an enclosure with the pcb model, it wasn’t too bad actually. And I’m getting used to cad now. My next update would be probably cleaning up my code and organizing my repository for this
Ships:
Building a smart “DeskPet” companion with Arduino & Python! It tracks my daily water intake, monitors room temperature and humidity to tell me when to open a window, and keeps my desk healthy....
|
1793566429.318828
|
1793652829.318828
|
|
59579
|
info about AI OS by @brandonz | Stardance
|
brandonz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: info about AI OS by @brandonz | Stardance
|
1793566428.414798
|
1794171228.414798
|
|
37324
|
Test by @NamanS | Stardance
|
NamanS
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Test by @NamanS | Stardance
|
1793566427.5440593
|
1794171227.5440593
|
|
59578
|
My Hackpad by @Sandhana | Stardance
|
Sandhana
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My Hackpad by @Sandhana | Stardance
|
1793566426.6704533
|
1794171226.6704533
|
|
23731
|
Gaming Cowboy Belt-Buckle by @aruta_b_p | Stardanc Gaming Cowboy Belt-Buckle by @aruta_b_p | Stardance...
|
aruta_b_p
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Gaming Cowboy Belt-Buckle by @aruta_b_p | S Title: Gaming Cowboy Belt-Buckle by @aruta_b_p | Stardance...
|
1793566425.8094528
|
1794171225.8094528
|
|
38100
|
Home Blinds by @Bober | Stardance
|
Bober
|
0
|
2.61
|
0
|
[]
|
[{"post_id": 32578, "ts": "202 [{"post_id": 32578, "ts": "2026-07-21T21:00:23Z", "hours": 2.61, "text": "Recall & Sketch For the past ~2h I created a basic sketch of algorithm that I will use and also recalled basics of C++ syntax. Thx for reading one sentence xD (Btw graph was made in excalidraw)"}]...
|
Title: Home Blinds by @Bober | Stardance
Devlogs: Title: Home Blinds by @Bober | Stardance
Devlogs:
Recall & Sketch For the past ~2h I created a basic sketch of algorithm that I will use and also recalled basics of C++ syntax. Thx for reading one sentence xD (Btw graph was made in excalidraw)...
|
1793566424.9198425
|
1794171224.9198425
|
|
59576
|
My Portfolio!!! by @MeggerBuilder | Stardance
|
MeggerBuilder
|
0
|
0.49
|
0
|
[]
|
[{"post_id": 66729, "ts": "202 [{"post_id": 66729, "ts": "2026-09-12T16:54:54Z", "hours": 0.4903, "text": "We all start from somewhere"}]...
|
Title: My Portfolio!!! by @MeggerBuilder | Stardan Title: My Portfolio!!! by @MeggerBuilder | Stardance
Devlogs:
We all start from somewhere...
|
1793566424.0246892
|
1794171224.0246892
|