|
10001
|
Untitled project by @an | Stardance
|
an
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @an | Stardance
|
1792766900.2158957
|
1793371700.2158957
|
|
10002
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792929155.7594144
|
1793793155.7594144
|
|
10003
|
My first slack bot! by @lemony-tater | Stardance
|
lemony-tater
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-07T22:00:59Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a basic slack bot using javascript. It can tell jokes, give cat facts, give usage guidance, and check connection and latency. The most difficult part was learning javascript as it was a new language to me. Try /lemon-help, /lemon-joke, /lemon-ping, and /lemon-catfact in slack.", "repo": "https://github.com/lemony-tater-tot/my-slackbot", "demo": "https://hackclub.enterprise.slack.com/archives/C0APH2MMHH7"}]...
|
[{"post_id": 4549, "ts": "2026 [{"post_id": 4549, "ts": "2026-06-07T21:53:32Z", "hours": 0.5728, "text": "Finishing up the commands"}]...
|
Title: My first slack bot! by @lemony-tater | Star Title: My first slack bot! by @lemony-tater | Stardance
Devlogs:
Finishing up the commands
Ships:
I made a basic slack bot using javascript. It can tell jokes, give cat facts, give usage guidance, and check connection and latency. The most difficult part was learning javascript as it was a new language to me. Try /lemon-help, /lemon-joke, /lemon-ping, and /lemon-catfact in slack....
|
1793278044.9750142
|
1793364444.9750142
|
|
10004
|
My awesome macropad! by @Karthik_Balasubramanian | My awesome macropad! by @Karthik_Balasubramanian | Stardance...
|
Karthik_Balasubramanian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Karthik_Balasubram Title: My awesome macropad! by @Karthik_Balasubramanian | Stardance...
|
1793472972.2199032
|
1794077772.2199032
|
|
10005
|
Raspberry Pi AI Camera by @rainope | Stardance
|
rainope
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-20T00:30:35Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Raspberry Pi 5 security camera using the IMX500 AI sensor for person detection and on-device face recognition, with a live web dashboard.", "repo": "https://github.com/eric-feng14/security_cam", "demo": ""}]...
|
[{"post_id": 31523, "ts": "202 [{"post_id": 31523, "ts": "2026-07-20T00:24:05Z", "hours": 0.8669, "text": "Just finished facial detection; added a simple database."}]...
|
Title: Raspberry Pi AI Camera by @rainope | Starda Title: Raspberry Pi AI Camera by @rainope | Stardance
Devlogs:
Just finished facial detection; added a simple database.
Ships:
Raspberry Pi 5 security camera using the IMX500 AI sensor for person detection and on-device face recognition, with a live web dashboard....
|
1793274537.1359072
|
1793360937.1359072
|
|
10006
|
Exoplanet Habitability by @KhushiJ | Stardance
|
KhushiJ
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Exoplanet Habitability by @KhushiJ | Starda Title: Exoplanet Habitability by @KhushiJ | Stardance...
|
1793217136.6074584
|
1793821936.6074584
|
|
10007
|
My first slack bot! by @Ayush_KS | Stardance
|
Ayush_KS
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Ayush_KS | Stardanc Title: My first slack bot! by @Ayush_KS | Stardance...
|
1793472689.2830312
|
1794077489.2830312
|
|
10008
|
London Underground Journey Planner by @tramcrazy | London Underground Journey Planner by @tramcrazy | Stardance...
|
tramcrazy
|
3
|
7.0
|
83
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-10T12:25:46Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "[The journey planner uses London Underground stations - if you don’t know any, why not try searching for King’s Cross St Pancras, Waterloo, Tottenham Court Road or Victoria? As you type, lots of suggestions will appear anyway.] In this ship I have redesigned part of the database logic to provide users with improved information on disruptions across the London Underground network. This was based on feedback from a user on my last ship - “One thing that could be improved is clarity on Disruptions and more details about them.” I decided to use a Java HashMap to pass the data about disruptions between different parts of my code, as this meant it was easier to add information on multiple disruptions affecting the same line whilst ensuring all this information was kept in the same place. I then implemented the Bootstrap tooltip system to dynamically generate tooltips for disrupted lines based on the data from the database. You can test this new feature by hovering over (on desktop) or tapping (on mobile) the names of any disrupted London Underground lines, in the top right corner of the page (on desktop) or in the menu (on mobile). You should see a bit of detail about each disruption e.g. “Minor Delays” or “Part Suspended”. I’m considering adding more detail to these but need to decide on a way to include more text in the UI in a way that looks nice! I also need to make more progress on how the line colours look in dark mode - the whole system is still much more usable in light mode! More updates coming soon. This is my London Underground Journey Planner, for planning journeys on the London Underground network! It uses a custom-built HTTP server, custom templating engine, and my own implementation of the A* pathfinding algorithm which took a while to get right! Just head to the website at https://journeyplanner.tramcrazy.com to give it a test! Much of the work for this project was done before Stardance, but since it started I have added a new file handling system, the recent journeys feature, improved line disruption information for users, and written more documentation.", "repo": "https://github.com/tramcrazy/JourneyPlanner-Public", "demo": "https://journeyplanner.tramcrazy.com"}, {"ship_num": 2, "ts": "2026-07-05T16:00:29Z", "hours": 4.0, "multiplier": 17.4, "payout": 70, "blessing": "neutral", "text": "To try the project go to the link (Try project button). The planner uses London Underground stations - if you don’t know any, why not try searching for King’s Cross St Pancras, Waterloo, Tottenham Court Road or Victoria? As you type, lots of suggestions will appear anyway. The homepage now shows your 5 most recent searches - this data is stored locally in your browser! In this ship I have built a ‘recent journeys’ feature which saves a user’s 5 most recent journeys in their browser (preserving user privacy) and allows them to easily access journeys they’ve taken before. This feature involved improving the database logic to improve multi-client functionality, and required a whole new client-side database system (using JavaScript’s IndexedDB) to store journey data, which meant I had to get familiar with more complicated asynchronous structures I hadn’t used before! To show users when they last took a journey, I saved the Unix timestamp of the journey request time in the local database and then compared this with the current time, using human-readable descriptions! This is the new version of my London Underground Journey Planner, for planning journeys on the London Underground network! It uses a custom-built HTTP server, custom templating engine, and my own implementation of the A* pathfinding algorithm which took a while to get right! Just head to the website at https://journeyplanner.tramcrazy.com to give it a test! Much of the work for this project was done before Stardance, but since it started I have added a new file handling system, the recent journeys feature and written more documentation.", "repo": "https://github.com/tramcrazy/JourneyPlanner-Public", "demo": "https://journeyplanner.tramcrazy.com"}, {"ship_num": 3, "ts": "2026-06-20T18:50:40Z", "hours": 2.0, "multiplier": 8.18, "payout": 13, "blessing": "neutral", "text": "This is the first public version of my London Underground Journey Planner, for planning journeys on the London Underground network! It uses a custom-built HTTP server, custom templating engine, and my own implementation of the A* pathfinding algorithm which took a while to get right! Just head to the website at https://journeyplanner.tramcrazy.com to give it a test! The dark theme still needs a bit of work as the colour contrast isn’t great - colour mode is done based on system theme. Note - there are only 2 hours of Hackatime because I have been working on this project for many months and only the more recent parts have been done during Stardance.", "repo": "https://github.com/tramcrazy/JourneyPlanner-Public", "demo": "https://journeyplanner.tramcrazy.com"}]...
|
[{"post_id": 44534, "ts": "202 [{"post_id": 44534, "ts": "2026-08-10T11:14:30Z", "hours": 1.2456, "text": "I am currently working on a range of updates based on your feedback in previous ships! The first new feature is more detailed information on disruptions on London Underground lines - I have decided to implement a tooltip feature so that you can find out what type of disruption is occurring by hovering over a line name in the disruptions area. This has turned out to be quite complicated to implement as I need to change the way I get data from the database - to start with I have built a new method for getting disruption data so that it provides specific information, and have formatted this as a Java HashMap so that it can be easily accessed by the methods which will eventually rely on it. Next I need to rewrite the logic for generating the actual HTML which forms the disruption section, and adding the tooltip functionality in the process."}, {"post_id": 22915, "ts": "2026-07-05T15:42:49Z", "hours": 0.3303, "text": "I have deployed the new version of the app to the server and cleared Cloudflare caches so that the new feature should be fully functional on all browsers!"}, {"post_id": 22884, "ts": "2026-07-05T14:46:31Z", "hours": 0.5536, "text": "I’ve finished the recent journeys feature and improved the database code so that it handles multiple clients properly! I used some custom logic to decide how to tell the user the time since they took a journey, based on how long ago it was."}, {"post_id": 22385, "ts": "2026-07-04T20:41:07Z", "hours": 0.8658, "text": "I’ve now (almost) fully implemented the first version of the recent journeys feature! The time you took the journey is still shown as a Unix timestamp - I just need to add some switch-case logic for choosing how to display the time in a human-friendly format! I had to implement a new API endpoint, /api/stationName , on the server so that I could get station names from the database but this is working now, and the client-side JavaScript reads from the locally stored database whenever the homepage loads, before grabbing the station names from the server and displaying everything in the table! The screenshot is the real app, not test data! I haven’t deployed it to the main server yet because I need to make the database handler a bit more robust to deal with the increased simultaneous requests, and I want to make the time element more user-friendly. Watch this space for more!"}, {"post_id": 22337, "ts": "2026-07-04T19:13:49Z", "hours": 0.3431, "text": "I’ve now fixed the logic for deleting old journeys, so a local IndexedDB stores the user’s five most recent journeys on their device, with the origin, destination and timestamp. Once the database table reaches five entries, the oldest one (based on the incrementing primary key) is automatically deleted so that we don’t clog up users’ storage space! Now I need to implement a backend lookup to find station names based on their IDs, so that I can implement the recent journeys UI component!"}, {"post_id": 21688, "ts": "2026-07-03T19:37:19Z", "hours": 1.935, "text": "I’ve been working on the frontend of the app as previously most of the effort had been on the backend! First of all I am adding a ‘recent journeys’ feature which will let users easily access journeys they’ve previously searched for. So that I don’t have to implement a login system, and to increase user privacy, I am storing the recent journey data in IndexedDB on the client side, so I have had to start implementing the logic for that. So far, I have managed to store the journey data but now need to fix the logic for deleting old journeys and filling the recent journeys UI component. Below is a prototype (with dummy data) of the recent journeys UI, let me know what you think! Based on rater feedback, it seems a bit tricky to use for people who aren’t familiar with London! The project uses Underground stations and not landmarks, so try typing a few letters to start searching… if you don’t know any, how about Liverpool Street or Paddington to get you started?"}, {"post_id": 12691, "ts": "2026-06-20T18:47:03Z", "hours": 0.6867, "text": "In this session I’ve been writing the README so that people who come to the GitHub repository have a better idea of how the project works and how all the code fits together, as well as how to compile it for themselves!"}, {"post_id": 12605, "ts": "2026-06-20T16:22:08Z", "hours": 0.8775, "text": "In this first session I have redesigned the file handling logic for my template HTML files and static assets! Previously I was using a standard Java file handler to open these and serve them to users over the TCP socket, but I have now used Java’s resource functionality so that I can bundle the templates and static files into an artefact for deployment to the server! I have also been working on configuring the server ready for deployment and have deployed my project on Hack Club Nest so that others can try out the system! Still lots of work to do on improving the database system and making the journey planning algorithm itself a bit more sensible, but I have improved search times by fixing the journey planning algorithm so that it functions as a full A* pathfinding algorithm. Note that before Stardance, I had already developed most of the code in the project and my aims are to improve the project and make it work better as an online service!"}]...
|
Title: London Underground Journey Planner by @tram Title: London Underground Journey Planner by @tramcrazy | Stardance
Devlogs:
In this first session I have redesigned the file handling logic for my template HTML files and static assets! Previously I was using a standard Java file handler to open these and serve them to users over the TCP socket, but I have now used Java’s resource functionality so that I can bundle the templates and static files into an artefact for deployment to the server! I have also been working on configuring the server ready for deployment and have deployed my project on Hack Club Nest so that others can try out the system! Still lots of work to do on improving the database system and making the journey planning algorithm itself a bit more sensible, but I have improved search times by fixing the journey planning algorithm so that it functions as a full A* pathfinding algorithm. Note that before Stardance, I had already developed most of the code in the project and my aims are to improve the project and make it work better as an online service!
In this session I’ve been writing the README so that people who come to the GitHub repository have a better idea of how the project works and how all the code fits together, as well as how to compile it for themselves!
I’ve been working on the frontend of the app as previously most of the effort had been on the backend! First of all I am adding a ‘recent journeys’ feature which will let users easily access journeys they’ve previously searched for. So that I don’t have to implement a login system, and to increase user privacy, I am storing the recent journey data in IndexedDB on the client side, so I have had to start implementing the logic for that. So far, I have managed to store the journey data but now need to fix the logic for deleting old journeys and filling the recent journeys UI component. Below is a prototype (with dummy data) of the recent journeys UI, let me know what you think! Based on rater feedback, it seems a bit tricky to use for people who aren’t familiar with London! The project uses Underground stations and not landmarks, so try typing a few letters to start searching… if you don’t know any, how about Liverpool Street or Paddington to get you started?
I’ve now fixed the logic for deleting old journeys, so a local IndexedDB stores the user’s five most recent journeys on their device, with the origin, destination and timestamp. Once the database table reaches five entries, the oldest one (based on the incrementing primary key) is automatically deleted so that we don’t clog up users’ storage space! Now I need to implement a backend lookup to find station names based on their IDs, so that I can implement the recent journeys UI component!
I’ve now (almost) fully implemented the first version of the recent journeys feature! The time you took the journey is still shown as a Unix timestamp - I just need to add some switch-case logic for choosing how to display the time in a human-friendly format! I had to implement a new API endpoint, /api/stationName , on the server so that I could get station names from the database but this is working now, and the client-side JavaScript reads from the locally stored database whenever the homepage loads, before grabbing the station names from the server and displaying everything in the table! The screenshot is the real app, not test data! I haven’t deployed it to the main server yet because I need to make the database handler a bit more robust to deal with the increased simultaneous requests, and I want to make the time element more user-friendly. Watch this space for more!
I’ve finished the recent journeys feature and improved the database code so that it handles multiple clients properly! I used some custom logic to decide how to tell the user the time since they took a journey, based on how long ago it was.
I have deployed the new version of the app to the server and cleared Cloudflare caches so that the new feature should be fully functional on all browsers!
I am currently working on a range of updates based on your feedback in previous ships! The first new feature is more detailed information on disruptions on London Underground lines - I have decided to implement a tooltip feature so that you can find out what type of disruption is occurring by hovering over a line name in the disruptions area. This has turned out to be quite complicated to implement as I need to change the way I get data from the database - to start with I have built a new method for getting disruption data so that it provides specific information, and have formatted this as a Java HashMap so that it can be easily accessed by the methods which will eventually rely on it. Next I need to rewrite the logic for generating the actual HTML which forms the disruption section, and adding the tooltip functionality in the process.
Ships:
This is the first public version of my London Underground Journey Planner, for planning journeys on the London Underground network! It uses a custom-built HTTP server, custom templating engine, and my own implementation of the A* pathfinding algorithm which took a while to get right! Just head to the website at https://journeyplanner.tramcrazy.com to give it a test! The dark theme still needs a bit of work as the colour contrast isn’t great - colour mode is done based on system theme. Note - there are only 2 hours of Hackatime because I have been working on this project for many months and only the more recent parts have been done during Stardance.
To try the project go to the link (Try project button). The planner uses London Underground stations - if you don’t know any, why not try searching for King’s Cross St Pancras, Waterloo, Tottenham Court Road or Victoria? As you type, lots of suggestions will appear anyway. The homepage now shows your 5 most recent searches - this data is stored locally in your browser! In this ship I have built a ‘recent journeys’ feature which saves a user’s 5 most recent journeys in their browser (preserving user privacy) and allows them to easily access journeys they’ve taken before. This feature involved improving the database logic to improve multi-client functionality, and required a whole new client-side database system (using JavaScript’s IndexedDB) to store journey data, which meant I had to get familiar with more complicated asynchronous structures I hadn’t used before! To show users when they last took a journey, I saved the Unix timestamp of the journey request time in the local database and then compared this with the current time, using human-readable descriptions! This is the new version of my London Underground Journey Planner, for planning journeys on the London Underground network! It uses a custom-built HTTP server, custom templating engine, and my own implementation of the A* pathfinding algorithm which took a while to get right! Just head to the website at https://journeyplanner.tramcrazy.com to give it a test! Much of the work for this project was done before Stardance, but since it started I have added a new file handling system, the recent journeys feature and written more documentation.
[The journey planner uses London Underground stations - if you don’t know any, why not try searching for King’s Cross St Pancras, Waterloo, Tottenham Court Road or Victoria? As you type, lots of suggestions will appear anyway.] In this ship I have redesigned part of the database logic to provide users with improved information on disruptions across the London Underground network. This was based on feedback from a user on my last ship - “One thing that could be improved is clarity on Disruptions and more details about them.” I decided to use a Java HashMap to pass the data about disruptions between different parts of my code, as this meant it was easier to add information on multiple disruptions affecting the same line whilst ensuring all this information was kept in the same place. I then implemented the Bootstrap tooltip system to dynamically generate tooltips for disrupted lines based on the data from the database. You can test this new feature by hovering over (on desktop) or tapping (on mobile) the names of any disrupted London Underground lines, in the top right corner of the page (on desktop) or in the menu (on mobile). You should see a bit of detail about each disruption e.g. “Minor Delays” or “Part Suspended”. I’m considering adding more detail to these but need to decide on a way to include more text in the UI in a way that looks nice! I also need to make more progress on how the line colours look in dark mode - the whole system is still much more usable in light mode! More updates coming soon. This is my London Underground Journey Planner, for planning journeys on the London Underground network! It uses a custom-built HTTP server, custom templating engine, and my own implementation of the A* pathfinding algorithm which took a while to get right! Just head to the website at https://journeyplanner.tramcrazy.com to give it a test! Much of the work for this project was done before Stardance, but since it started I have added a new file handling system, the recent journeys feature, improved line disruption information for users, and written more documentation....
|
1793267431.4014103
|
1793353831.4014103
|
|
10009
|
CV checker by @Jalal | Stardance
|
Jalal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CV checker by @Jalal | Stardance
|
1792792334.6714406
|
1793397134.6714406
|
|
10010
|
Untitled project by @papajek2137 | Stardance
|
papajek2137
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @papajek2137 | Stardanc Title: Untitled project by @papajek2137 | Stardance...
|
1793389893.8757975
|
1793994693.8757975
|
|
10011
|
Writing a Roblox Executor in Lua by @Bjarnos | Sta Writing a Roblox Executor in Lua by @Bjarnos | Stardance...
|
Bjarnos
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Writing a Roblox Executor in Lua by @Bjarno Title: Writing a Roblox Executor in Lua by @Bjarnos | Stardance...
|
1793234982.3232014
|
1793839782.3232014
|
|
10012
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792889624.0833514
|
1793753624.0833514
|
|
10013
|
apuestas deportivas by @usuario1crunchy | Stardanc apuestas deportivas by @usuario1crunchy | Stardance...
|
usuario1crunchy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: apuestas deportivas by @usuario1crunchy | S Title: apuestas deportivas by @usuario1crunchy | Stardance...
|
1793249327.5498633
|
1793854127.5498633
|
|
10014
|
Untitled by @brny | Stardance
|
brny
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @brny | Stardance
|
1792749025.5342739
|
1793353825.5342739
|
|
10015
|
My first slack bot! by @bakiran | Stardance
|
bakiran
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @bakiran | Stardance
|
1792796009.9728067
|
1793400809.9728067
|
|
10016
|
untitled fighting game by @brny | Stardance
|
brny
|
0
|
0.36
|
0
|
[]
|
[{"post_id": 3671, "ts": "2026 [{"post_id": 3671, "ts": "2026-06-06T18:33:53Z", "hours": 0.36, "text": "Untitled fighting game is a silly fighting game where you can fight against everything. It takes a lot of inspirtation from old roblox games. Im making it in godot and making it 3d, currently i made the player move and gave it an arm"}]...
|
Title: untitled fighting game by @brny | Stardance Title: untitled fighting game by @brny | Stardance
Devlogs:
Untitled fighting game is a silly fighting game where you can fight against everything. It takes a lot of inspirtation from old roblox games. Im making it in godot and making it 3d, currently i made the player move and gave it an arm...
|
1793461759.3167179
|
1794066559.3167179
|
|
10017
|
My awesome macropad! by @GoofyVedansh | Stardance
|
GoofyVedansh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @GoofyVedansh | Sta Title: My awesome macropad! by @GoofyVedansh | Stardance...
|
1793213551.8727725
|
1793818351.8727725
|
|
10018
|
my own personal website by @ryni | Stardance
|
ryni
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: my own personal website by @ryni | Stardanc Title: my own personal website by @ryni | Stardance...
|
1793289199.6833155
|
1793893999.6833155
|
|
10019
|
learn react by @ttiramisu | Stardance
|
ttiramisu
|
0
|
0.92
|
0
|
[]
|
[{"post_id": 3920, "ts": "2026 [{"post_id": 3920, "ts": "2026-06-07T01:09:27Z", "hours": 0.9158, "text": "working on learning react while making some bad ui designs for fun. no css yet though cuz i didnt have the time for it…."}]...
|
Title: learn react by @ttiramisu | Stardance
Devl Title: learn react by @ttiramisu | Stardance
Devlogs:
working on learning react while making some bad ui designs for fun. no css yet though cuz i didnt have the time for it…....
|
1793444016.322345
|
1794048816.322345
|
|
10020
|
Untitled project by @tintin | Stardance
|
tintin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @tintin | Stardance
|
1793386099.0911343
|
1793990899.0911343
|
|
10021
|
personal website by @orangishcat | Stardance
|
orangishcat
|
1
|
24.0
|
223
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-30T23:32:43Z", "hours": 24.0, "multiplier": 9.16, "payout": 223, "blessing": "neutral", "text": "My favorite project, and also the best one I’ve ever made! Please read my devlog for more details and easter eggs: https://orangishcat.neocities.org/blog/personal-website/", "repo": "https://github.com/orangishcat/orangishcat.github.io", "demo": "https://orangishcat.neocities.org/"}]...
|
[{"post_id": 37935, "ts": "202 [{"post_id": 37935, "ts": "2026-07-30T23:20:23Z", "hours": 4.6331, "text": "Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ Just some small changes since then. I’ve made the background less orange and instead blue. The orange theme was making the orange background look terrible, so I changed it to blue, which matches better with the color of a night sky. Updated the games list. As it turns out, there’s a lot of cool games out there! Added more links to the Links part of the sidebar."}, {"post_id": 29631, "ts": "2026-07-16T18:04:57Z", "hours": 4.1481, "text": "Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ everything is done!!! I added background art with the Moon and stars, and added my blog posts to the right sidebar! it took like an hour to debug all the issues with the MDX integration and UI layout, but it was mostly successful and super worth it!"}, {"post_id": 28554, "ts": "2026-07-14T21:34:02Z", "hours": 8.9608, "text": "Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ the website is pretty much done! All the content and whatnot is complete, I just need to add some blog posts to fill up the blog space!"}, {"post_id": 22210, "ts": "2026-07-04T15:57:11Z", "hours": 1.5711, "text": "Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ after spending like 15 hours drawing assets and staring at a wall trying to think of stuff, i have finally started coding. not all the assets are done yet, but i need to start coding so i don’t keep staring at a wall… anyway, ima talk about coding. css grid is so cool! you can do all sorts of layouts so easily, and tailwindcss + css grid tricks make developing quite a breeze. really cool stuff!"}, {"post_id": 4717, "ts": "2026-06-08T04:25:47Z", "hours": 5.0586, "text": "Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ First devlog! I’ve never made a personal website before, so I want to do it right. I’m planning to go heavy with lots of art and web design. This is my first time ever doing art, and I quickly decided to do pixel art as it’s a lot easier than digital painting. I’ve made a few assets and am planning to do a lot more! In the beginning it was quite rough and my drawings looked terrible, but after a few days it turned out much better than I was expecting, and I even applied some Minecraft building concepts! Like, for example: Outline first, then color, then details. The final result won’t look good if the shape isn’t right. Details are what turns a good Minecraft build (or drawing, in this case) great. Once you think you’re done, think about what details you could add. Then repeat. You should be able to do this a lot more times than you think, and it’s how you improve your technique. The cat asset below took ~20 revisions. Use a reference image, or multiple. Don’t reinvent the wheel. Learn basic color theory, it’s really useful. Other than that, it just took some creativity and some trial and error."}]...
|
Title: personal website by @orangishcat | Stardanc Title: personal website by @orangishcat | Stardance
Devlogs:
Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ First devlog! I’ve never made a personal website before, so I want to do it right. I’m planning to go heavy with lots of art and web design. This is my first time ever doing art, and I quickly decided to do pixel art as it’s a lot easier than digital painting. I’ve made a few assets and am planning to do a lot more! In the beginning it was quite rough and my drawings looked terrible, but after a few days it turned out much better than I was expecting, and I even applied some Minecraft building concepts! Like, for example: Outline first, then color, then details. The final result won’t look good if the shape isn’t right. Details are what turns a good Minecraft build (or drawing, in this case) great. Once you think you’re done, think about what details you could add. Then repeat. You should be able to do this a lot more times than you think, and it’s how you improve your technique. The cat asset below took ~20 revisions. Use a reference image, or multiple. Don’t reinvent the wheel. Learn basic color theory, it’s really useful. Other than that, it just took some creativity and some trial and error.
Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ after spending like 15 hours drawing assets and staring at a wall trying to think of stuff, i have finally started coding. not all the assets are done yet, but i need to start coding so i don’t keep staring at a wall… anyway, ima talk about coding. css grid is so cool! you can do all sorts of layouts so easily, and tailwindcss + css grid tricks make developing quite a breeze. really cool stuff!
Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ the website is pretty much done! All the content and whatnot is complete, I just need to add some blog posts to fill up the blog space!
Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ everything is done!!! I added background art with the Moon and stars, and added my blog posts to the right sidebar! it took like an hour to debug all the issues with the MDX integration and UI layout, but it was mostly successful and super worth it!
Hi voters! Stardance isn’t the greatest for devlogging art, so read my blog post instead! https://orangishcat.neocities.org/blog/personal-website/ Just some small changes since then. I’ve made the background less orange and instead blue. The orange theme was making the orange background look terrible, so I changed it to blue, which matches better with the color of a night sky. Updated the games list. As it turns out, there’s a lot of cool games out there! Added more links to the Links part of the sidebar.
Ships:
My favorite project, and also the best one I’ve ever made! Please read my devlog for more details and easter eggs: https://orangishcat.neocities.org/blog/personal-website/...
|
1793271071.2049718
|
1793357471.2049718
|
|
10022
|
My first slack bot! by @ere-erik | Stardance
|
ere-erik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @ere-erik | Stardanc Title: My first slack bot! by @ere-erik | Stardance...
|
1793213740.1270332
|
1793818540.1270332
|
|
10023
|
Devspace by @notaureith | Stardance
|
notaureith
|
0
|
2.03
|
0
|
[]
|
[{"post_id": 9287, "ts": "2026 [{"post_id": 9287, "ts": "2026-06-15T16:17:28Z", "hours": 0.4253, "text": "DEVLOG #3 The Future Starts Looking Real DevSpace is slowly turning from an idea into an actual platform. Today we worked on expanding the roadmap and planning features that make DevSpace feel more alive than a traditional IDE. Instead of just coding software, we want developers to feel like they are entering a digital workspace built for creativity, teamwork, and community. ->New roadmap ideas: AI-powered debugging assistant Shared live terminals Custom developer profiles Workspace themes & environments Community chill rooms One-click team setup system Smart notifications for teams We are also exploring smoother communication systems so developers can instantly jump into voice/video discussions while staying inside the coding environment. Biggest challenge: Balancing powerful features while keeping the software lightweight and fast."}, {"post_id": 7925, "ts": "2026-06-13T06:39:06Z", "hours": 0.5094, "text": "DEVLOG #2 Building the Collaboration System Today we focused on one of the biggest parts of DevSpace — real-time collaboration. The vision is simple: Developers should be able to join a workspace and instantly code, communicate, and collaborate without opening external apps. ->We started improving: Real-time syncing Shared workspace structure Voice room concepts Team collaboration flow Faster UI responsiveness One interesting idea we are exploring is workspace rooms similar to communication platforms, where developers can create project-based environments and collaborate live. Another focus is reducing distractions. Instead of switching tabs between coding and meetings, DevSpace keeps everything inside one ecosystem. Current Enhancements: Improved project workspace UI Better file syncing research Team room structure planning AI assistant workflow concepts Optimized desktop performance The goal is still the same: Make developers enjoy collaboration again."}, {"post_id": 5400, "ts": "2026-06-09T04:40:32Z", "hours": 1.0908, "text": "DEVLOG #1 — The Beginning of DevSpace DevSpace started with one simple idea , developers should not need 5 different apps just to work together. Right now people code on VS Code, communicate on Discord or Zoom, push on GitHub, and switch tabs constantly. We wanted to build a standalone software where everything exists in one place. A space where developers can code together in real time, join voice/video rooms instantly, use AI tools, collaborate on projects, and even chill with the community. Currently, we have started building the base architecture and experimenting with real-time collaboration systems. The biggest focus right now is creating a smooth coding experience while keeping communication features lightweight and fast. Inspired by modern devlog styles that showcase progress and vision step-by-step . •Current Focus ->Real-time collaboration ->Built-in communication ->AI developer tools ->Desktop software architecture ->Developer community experience"}]...
|
Title: Devspace by @notaureith | Stardance
Devlog Title: Devspace by @notaureith | Stardance
Devlogs:
DEVLOG #1 — The Beginning of DevSpace DevSpace started with one simple idea , developers should not need 5 different apps just to work together. Right now people code on VS Code, communicate on Discord or Zoom, push on GitHub, and switch tabs constantly. We wanted to build a standalone software where everything exists in one place. A space where developers can code together in real time, join voice/video rooms instantly, use AI tools, collaborate on projects, and even chill with the community. Currently, we have started building the base architecture and experimenting with real-time collaboration systems. The biggest focus right now is creating a smooth coding experience while keeping communication features lightweight and fast. Inspired by modern devlog styles that showcase progress and vision step-by-step . •Current Focus ->Real-time collaboration ->Built-in communication ->AI developer tools ->Desktop software architecture ->Developer community experience
DEVLOG #2 Building the Collaboration System Today we focused on one of the biggest parts of DevSpace — real-time collaboration. The vision is simple: Developers should be able to join a workspace and instantly code, communicate, and collaborate without opening external apps. ->We started improving: Real-time syncing Shared workspace structure Voice room concepts Team collaboration flow Faster UI responsiveness One interesting idea we are exploring is workspace rooms similar to communication platforms, where developers can create project-based environments and collaborate live. Another focus is reducing distractions. Instead of switching tabs between coding and meetings, DevSpace keeps everything inside one ecosystem. Current Enhancements: Improved project workspace UI Better file syncing research Team room structure planning AI assistant workflow concepts Optimized desktop performance The goal is still the same: Make developers enjoy collaboration again.
DEVLOG #3 The Future Starts Looking Real DevSpace is slowly turning from an idea into an actual platform. Today we worked on expanding the roadmap and planning features that make DevSpace feel more alive than a traditional IDE. Instead of just coding software, we want developers to feel like they are entering a digital workspace built for creativity, teamwork, and community. ->New roadmap ideas: AI-powered debugging assistant Shared live terminals Custom developer profiles Workspace themes & environments Community chill rooms One-click team setup system Smart notifications for teams We are also exploring smoother communication systems so developers can instantly jump into voice/video discussions while staying inside the coding environment. Biggest challenge: Balancing powerful features while keeping the software lightweight and fast....
|
1793163139.6331506
|
1793767939.6331506
|
|
10024
|
My first slack bot! by @rayanm | Stardance
|
rayanm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @rayanm | Stardance
|
1792756188.3409538
|
1793360988.3409538
|
|
10025
|
Drip-Boy by @leroyl6420 | Stardance
|
leroyl6420
|
0
|
1.26
|
0
|
[]
|
[{"post_id": 5312, "ts": "2026 [{"post_id": 5312, "ts": "2026-06-09T01:27:49Z", "hours": 0.515, "text": "I worked on the forearm case for my Drip-Boy today! I took measurements of my left forearm using a digital caliper, and I CAD-ed all the dimensions into a tube (with filleted edges). I’ll glue some padding on in real life. I incorporated two hinges on the back (you can’t see them in the image). You’ll need to insert two #6-32 screws for them to work. I fastened the Raspberry Pi case onto the bottom, though I need to CAD a release mechanism for it because I’d like to be able to put it in/take it out. I still need to figure out how to attach the screen and wiring."}, {"post_id": 4515, "ts": "2026-06-07T21:05:11Z", "hours": 0.7444, "text": "Hi! This is (my progress on) my project, Drip-Boy! Inspired by the Pip-Boy, it’ll be a portable Raspberry-Pi powered cyberdeck. So far, I just designed a case for the Raspberry Pi. I’m planning to CAD a forearm attachment for this, and then a flip-out screen + a keyboard!"}]...
|
Title: Drip-Boy by @leroyl6420 | Stardance
Devlog Title: Drip-Boy by @leroyl6420 | Stardance
Devlogs:
Hi! This is (my progress on) my project, Drip-Boy! Inspired by the Pip-Boy, it’ll be a portable Raspberry-Pi powered cyberdeck. So far, I just designed a case for the Raspberry Pi. I’m planning to CAD a forearm attachment for this, and then a flip-out screen + a keyboard!
I worked on the forearm case for my Drip-Boy today! I took measurements of my left forearm using a digital caliper, and I CAD-ed all the dimensions into a tube (with filleted edges). I’ll glue some padding on in real life. I incorporated two hinges on the back (you can’t see them in the image). You’ll need to insert two #6-32 screws for them to work. I fastened the Raspberry Pi case onto the bottom, though I need to CAD a release mechanism for it because I’d like to be able to put it in/take it out. I still need to figure out how to attach the screen and wiring....
|
1792752873.8413002
|
1793357673.8413002
|
|
10026
|
Astrophotography Tools by @jdszekeres | Stardance
|
jdszekeres
|
4
|
25.0
|
296
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-26T02:50:06Z", "hours": 6.0, "multiplier": 18.57, "payout": 106, "blessing": "neutral", "text": "In this ship, I: Finally got to fixing the UI, making it more space-themed (i.e stars on every page background with comets, zero-g floating cards, comsic latte color scheme) Added planets and other visible celestial objects to the FOV preview Made the Bortle Scale indicator work by building my own light pollution map from the CU Boulder VIIRS dataset Check out this photo of the moon I took!", "repo": "https://github.com/jdszekeres/astrophoto-tools", "demo": "https://astrophoto-tools.vercel.app/"}, {"ship_num": 2, "ts": "2026-08-14T04:48:00Z", "hours": 4.0, "multiplier": 18.98, "payout": 74, "blessing": "neutral", "text": "I added FOV preview and hyperfocal distance calculator tools to the site, as well as adding the Milky Way to the star chart. Lastly, I added a guide to help newer astrophotographers get comfortable with astrophotography. Here’s a photo I took of some star trails in the Dolomites.", "repo": "https://github.com/jdszekeres/astrophoto-tools", "demo": "https://astrophoto-tools.vercel.app/"}, {"ship_num": 3, "ts": "2026-07-10T00:22:25Z", "hours": 8.0, "multiplier": 6.68, "payout": 51, "blessing": "neutral", "text": "I added a star chart tool and a stacking calculator, as well as a recomended settings for major camera brands to my astrophotography tools PWA. One of my biggest challenges was the star chart generator. I wanted it to mirror other star charts with major stars and constellations. I spent a lot of time entering constellations by hand before realizing there was a dataset that already detailed exactly that. The photo below was taken using the info from these tools.", "repo": "https://github.com/jdszekeres/astrophoto-tools", "demo": "https://astrophoto-tools.vercel.app/"}, {"ship_num": 4, "ts": "2026-06-17T00:00:58Z", "hours": 7.0, "multiplier": 9.67, "payout": 65, "blessing": "neutral", "text": "I made a set of Astrophotography tools to use in the field. They include an equivalent exposure calculator, Bortle scale finder and reference, sun and moon position calculator, and 400 rule tool. They all work offline and are mobile PWA compatible.", "repo": "https://github.com/jdszekeres/astrophoto-tools", "demo": "https://astrophoto-tools.vercel.app/"}]...
|
[{"post_id": 54750, "ts": "202 [{"post_id": 54750, "ts": "2026-08-25T20:51:59Z", "hours": 0.6228, "text": "Add celestial objects to FOV preview Changelog 2a13b7a"}, {"post_id": 54703, "ts": "2026-08-25T19:32:54Z", "hours": 2.1147, "text": "I fixed the Bortle Scale by building my own light pollution map from scratch using a light pollution scattering kernel using the CU Boulder VIIRS dataset. Previously, the dataset I used didn’t have enough labels for each bortle scale and had country borders, which screwed with what the expected light pollution is."}, {"post_id": 52039, "ts": "2026-08-22T02:31:44Z", "hours": 1.6469, "text": "I’ve taken your feedback from the last ship and I’ve started work on a more space-y theme for this project. So far, I’ve switched up the color scheme to a dark blueish-purple and comsic latte (The average color of the universe). I also added a procderual starfield with comets in the background. Also, check out the homepage, the page cards also float around like they’re in microgravity!"}, {"post_id": 51910, "ts": "2026-08-21T20:20:31Z", "hours": 1.3114, "text": "I did a lot of space saving (pun intended) to reduce the offline cache size by about 0.7 Mb to 3.8 Mb by better compressing images and minifying code and JSON. I also had to do an emergency fix for mobile, where it wasn’t working on certain phones."}, {"post_id": 46707, "ts": "2026-08-14T04:43:59Z", "hours": 0.7883, "text": "Added a guide to Astrophotography tools to make it more beginner friendly."}, {"post_id": 46686, "ts": "2026-08-14T03:54:11Z", "hours": 1.1489, "text": "Added milky way to star chart! It looks kinda cool how it wraps off the page and it definitely wasn’t because it was too hard to remove it."}, {"post_id": 44083, "ts": "2026-08-09T16:37:45Z", "hours": 1.9692, "text": "I added a FOV preview, which shows how the 110 messier objects appear in photos based on your camera sensor size and lens focal length. It’s very useful for deep space imaging."}, {"post_id": 25614, "ts": "2026-07-10T00:19:31Z", "hours": 0.7542, "text": "I added final UI improvements ahead of shipping and reduced redundant code"}, {"post_id": 24540, "ts": "2026-07-08T05:06:40Z", "hours": 1.165, "text": "Added a stacking calculator to show how well a stack of images will look based on their signal to noise ratio"}, {"post_id": 24435, "ts": "2026-07-08T00:07:28Z", "hours": 0.3561, "text": "Did some compression work to bring the download size down from 16 MB to only 4 MB. Mostly compressing images, but also making a new catalog, reduced catalog for stars."}, {"post_id": 24421, "ts": "2026-07-07T23:27:02Z", "hours": 2.5344, "text": "So, it turns out I didn’t need to enter all those lines manually, there are saved files out there for it."}, {"post_id": 19001, "ts": "2026-06-30T05:07:42Z", "hours": 1.0906, "text": "I got more constellations (Hydra, Bootes) and added offical International Astronomy Union names when applicable"}, {"post_id": 18804, "ts": "2026-06-30T00:38:53Z", "hours": 0.6019, "text": "Ha, I added orion and aries. This took forever b/c orion has so many connections"}, {"post_id": 18698, "ts": "2026-06-29T21:42:10Z", "hours": 1.2553, "text": "I’m working on an offline star chart generator. I’ve been working with Astronomy Engine and the Yale Bright Stars Catalog to find the proper motion of the stars. I’ve only added the Big Dipper, but I plan add more of the 88 IAU constellations."}, {"post_id": 10320, "ts": "2026-06-16T23:58:16Z", "hours": 0.3439, "text": "I actually used my project. Here is a shot I took of Bishop Pass in the Eastern Sierra Nevada mountains."}, {"post_id": 5820, "ts": "2026-06-09T19:10:37Z", "hours": 0.7731, "text": "Worked on getting the project deployed to Vercel (A lot of headaches with relative and absolute paths)"}, {"post_id": 5265, "ts": "2026-06-08T23:46:36Z", "hours": 2.5844, "text": "Add redlight mode to prevent eyes from getting burned while adjusting to the dark"}, {"post_id": 4544, "ts": "2026-06-07T21:44:54Z", "hours": 1.5022, "text": "I spent way too much time debugging how to use the data from lightpollution.it to find the light pollution index at a coordinate. Turns out they were using an off-centered projection that I used ChatGPT to decode (x = (lon + 126.44) / 0.03382; y = (-20.28 * lat) + 1862.4;)"}, {"post_id": 3918, "ts": "2026-06-07T01:07:11Z", "hours": 1.5881, "text": "Created the equivalent exposures tool to calculate values for each part of the exposure triangle based on other values."}]...
|
Title: Astrophotography Tools by @jdszekeres | Sta Title: Astrophotography Tools by @jdszekeres | Stardance
Devlogs:
Created the equivalent exposures tool to calculate values for each part of the exposure triangle based on other values.
I spent way too much time debugging how to use the data from lightpollution.it to find the light pollution index at a coordinate. Turns out they were using an off-centered projection that I used ChatGPT to decode (x = (lon + 126.44) / 0.03382; y = (-20.28 * lat) + 1862.4;)
Add redlight mode to prevent eyes from getting burned while adjusting to the dark
Worked on getting the project deployed to Vercel (A lot of headaches with relative and absolute paths)
I actually used my project. Here is a shot I took of Bishop Pass in the Eastern Sierra Nevada mountains.
I’m working on an offline star chart generator. I’ve been working with Astronomy Engine and the Yale Bright Stars Catalog to find the proper motion of the stars. I’ve only added the Big Dipper, but I plan add more of the 88 IAU constellations.
Ha, I added orion and aries. This took forever b/c orion has so many connections
I got more constellations (Hydra, Bootes) and added offical International Astronomy Union names when applicable
So, it turns out I didn’t need to enter all those lines manually, there are saved files out there for it.
Did some compression work to bring the download size down from 16 MB to only 4 MB. Mostly compressing images, but also making a new catalog, reduced catalog for stars.
Added a stacking calculator to show how well a stack of images will look based on their signal to noise ratio
I added final UI improvements ahead of shipping and reduced redundant code
I added a FOV preview, which shows how the 110 messier objects appear in photos based on your camera sensor size and lens focal length. It’s very useful for deep space imaging.
Added milky way to star chart! It looks kinda cool how it wraps off the page and it definitely wasn’t because it was too hard to remove it.
Added a guide to Astrophotography tools to make it more beginner friendly.
I did a lot of space saving (pun intended) to reduce the offline cache size by about 0.7 Mb to 3.8 Mb by better compressing images and minifying code and JSON. I also had to do an emergency fix for mobile, where it wasn’t working on certain phones.
I’ve taken your feedback from the last ship and I’ve started work on a more space-y theme for this project. So far, I’ve switched up the color scheme to a dark blueish-purple and comsic latte (The average color of the universe). I also added a procderual starfield with comets in the background. Also, check out the homepage, the page cards also float around like they’re in microgravity!
I fixed the Bortle Scale by building my own light pollution map from scratch using a light pollution scattering kernel using the CU Boulder VIIRS dataset. Previously, the dataset I used didn’t have enough labels for each bortle scale and had country borders, which screwed with what the expected light pollution is.
Add celestial objects to FOV preview Changelog 2a13b7a
Ships:
I made a set of Astrophotography tools to use in the field. They include an equivalent exposure calculator, Bortle scale finder and reference, sun and moon position calculator, and 400 rule tool. They all work offline and are mobile PWA compatible.
I added a star chart tool and a stacking calculator, as well as a recomended settings for major camera brands to my astrophotography tools PWA. One of my biggest challenges was the star chart generator. I wanted it to mirror other star charts with major stars and constellations. I spent a lot of time entering constellations by hand before realizing there was a dataset that already detailed exactly that. The photo below was taken using the info from these tools.
I added FOV preview and hyperfocal distance calculator tools to the site, as well as adding the Milky Way to the star chart. Lastly, I added a guide to help newer astrophotographers get comfortable with astrophotography. Here’s a photo I took of some star trails in the Dolomites.
In this ship, I: Finally got to fixing the UI, making it more space-themed (i.e stars on every page background with comets, zero-g floating cards, comsic latte color scheme) Added planets and other visible celestial objects to the FOV preview Made the Bortle Scale indicator work by building my own light pollution map from the CU Boulder VIIRS dataset Check out this photo of the moon I took!...
|
1793321446.5310872
|
1793407846.5310872
|
|
10027
|
My awesome macropad! by @ASMO | Stardance
|
ASMO
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ASMO | Stardance
|
1792795916.703767
|
1793400716.703767
|
|
10028
|
My awesome macropad! by @deepuuu | Stardance
|
deepuuu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @deepuuu | Stardanc Title: My awesome macropad! by @deepuuu | Stardance...
|
1793299776.2067418
|
1793904576.2067418
|
|
10029
|
Untitled project by @JoshuaCortes | Stardance
|
JoshuaCortes
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @JoshuaCortes | Stardan Title: Untitled project by @JoshuaCortes | Stardance...
|
1793195339.7617357
|
1793800139.7617357
|
|
10030
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792892856.3576267
|
1793756856.3576267
|
|
10031
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792947077.077853
|
1793811077.077853
|
|
10032
|
Untitled project by @salah_kaifas29 | Stardance
|
salah_kaifas29
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @salah_kaifas29 | Stard Title: Untitled project by @salah_kaifas29 | Stardance...
|
1793188525.5579379
|
1793793325.5579379
|
|
10033
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792940065.3329587
|
1793804065.3329587
|
|
10034
|
jarvis by @ahmedelged2012 | Stardance
|
ahmedelged2012
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: jarvis by @ahmedelged2012 | Stardance
|
1793397331.71042
|
1794002131.71042
|
|
10035
|
My first slack bot! by @Roly_Poly | Stardance
|
Roly_Poly
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Roly_Poly | Stardan Title: My first slack bot! by @Roly_Poly | Stardance...
|
1793361300.496372
|
1793966100.496372
|
|
10036
|
My first slack bot! by @VelvynRose | Stardance
|
VelvynRose
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @VelvynRose | Starda Title: My first slack bot! by @VelvynRose | Stardance...
|
1793166667.3670855
|
1793771467.3670855
|
|
10037
|
Radio Tuner by @leroyl6420 | Stardance
|
leroyl6420
|
0
|
2.76
|
0
|
[]
|
[{"post_id": 42162, "ts": "202 [{"post_id": 42162, "ts": "2026-08-06T19:24:14Z", "hours": 1.5906, "text": "I finished the Radio Tuner’s PCB by sketching all the connections, and I coded all the firmware. It was confusing as this was my first time using QMK, but I got it all figured out eventually. I put all the firmware in the firmware folder in my repository, organized as they are in my files."}, {"post_id": 41555, "ts": "2026-08-05T20:50:51Z", "hours": 0.5333, "text": "I started my custom PCB! I am using an encoder, two buttons, and an OLED screen to made a radio frequency fidget device!"}, {"post_id": 41516, "ts": "2026-08-05T19:29:45Z", "hours": 0.6336, "text": "I made the tutorial HackPad! I didn’t yet customize it, I just wanted to see how to do things. It looks good, so I’m going to add encoders and stuff now."}]...
|
Title: Radio Tuner by @leroyl6420 | Stardance
Dev Title: Radio Tuner by @leroyl6420 | Stardance
Devlogs:
I made the tutorial HackPad! I didn’t yet customize it, I just wanted to see how to do things. It looks good, so I’m going to add encoders and stuff now.
I started my custom PCB! I am using an encoder, two buttons, and an OLED screen to made a radio frequency fidget device!
I finished the Radio Tuner’s PCB by sketching all the connections, and I coded all the firmware. It was confusing as this was my first time using QMK, but I got it all figured out eventually. I put all the firmware in the firmware folder in my repository, organized as they are in my files....
|
1793274871.8665235
|
1793879671.8665235
|
|
10038
|
Prometheus by @rishithc | Stardance
|
rishithc
|
1
|
154.99
|
82
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-07T15:56:14Z", "hours": 17.0, "multiplier": 5.0, "payout": 82, "blessing": "neutral", "text": "I made an autonomous drone. The most challenging part was the soldering. The soldering was quite hard for me and there were times where i burnt my hand", "repo": "https://github.com/rishith-c/Prometheus", "demo": ""}]...
|
[{"post_id": 29001, "ts": "202 [{"post_id": 29001, "ts": "2026-07-15T17:26:17Z", "hours": 10.9361, "text": "Devlog #18: A GREAT way to start working on your project again 😩 I’ve taken a break these past few days, realizing that a vacation exists for a reason! Today, however, I didn’t want to fall behind schedule. Since I also want grants to use a premium carbon fiber frame and all I need is to finish my PCB, I spent the day working in KiCad. Truth be told, the best way to learn is by doing—I thought the same about CAD, and I feel the same about PCB design. I made the executive decision to make a double-sided PCB rather than adding more layers, as it will be much simpler. Anyway, here are my final mockups."}, {"post_id": 23548, "ts": "2026-07-06T16:03:13Z", "hours": 9.0567, "text": "Devlog #17: I tested a lot tdy as well as designed new components I submitted my project, as is, to the Outpost fund, and I got some feedback. Mostly everything was good except for some issues with funding an NVDIA devkit :))), but the biggest issue was that I couldn’t buy a flight controller. In an devlog before, I mentioned and shows a picture of me designing a custom pcb, but I have not worked on that since. So today I fired up Kikad and designed layer 2 of my FC (easier, layer one has a lot of components that I need to import). I also spent a good chunk of today refining my 3d model, I used Air Shaper and SimScale and I aerodynamic tested all of the designs, I also asked claude for some ideas of how to make my .stls better. @vrunchil7 is da goat frfr he taught me how and what kikad is."}, {"post_id": 21535, "ts": "2026-07-03T15:40:49Z", "hours": 9.8875, "text": "Devlog #16: I probably should have done this earlier :( yea so while on vacation I decided to rework the weight and thrust ratios that the motors were producing with 11x7 props. I found out that my drone will not be able to fly SMOOTHLY. So I decided too look into why, one of the big reasons were that it was heavy, and two it wasn’t aerodynamic. So today I tried to kill two birds with one stone, (I also worked on my ML for a good portion of the time, but I feel this is more important). I ran digital wind tunnel tests and kept redesigning and testing until I landed on what I have now. I plan to make this out of carbon fiber which will be expensive, but ig that’s part of the process."}, {"post_id": 19917, "ts": "2026-07-01T11:05:00Z", "hours": 4.57, "text": "Devlog #15: training my own model wasn’t the move yea so training my own model wasnt the best idea. after hours of clicking through my webscraper’s image results and marking them, i ran a benchmark myself by putting on youtube videos of wildfires from a sky perspective. it saw the smoke in the distance and gave that as the fire, when the real fire was miles away. it also found the sun and clouds as a fire. so, false positives everywhere. so today i basically tested and worked with existing solutions instead, like this one: https://github.com/AlimTleuliyev/wildfire-detection , plus other open source alternatives on kaggle. but yea, overall today i felt retrogressed, and i’m thinking of going back to CV. This article also helped a lot https://www.mdpi.com/2571-6255/7/4/140 ."}, {"post_id": 19265, "ts": "2026-06-30T15:04:27Z", "hours": 9.0494, "text": "Devlog #14: building the dataset + training a tensorflow model spent today on the data side of fire detection, which is half the battle with ML. to train a model to recognize fire i need a solid labeled dataset, so first i built an image scraper. it crawls the web usinf breadth first search, going level by level through pages and pulling images as it goes. i used bidirectional bfs to expand the search from two fronts and cover more ground instead of just crawling one direction. ended up pulling a bunch of images, including a lot of tricky ones like trees and random orange stuff that a fire model could easily get confused by. then i built a small labeling tool to actually tag all of it. it shows me one image at a time, a tree, an orange object, an actual fire, and i just mark it as fire or no fire. way faster than sorting through folders by hand, and getting those confusing orange non-fire images labeled is exactly what stops the model from false triggering later. with some data labeled i started training a tensorflow model on it, mostly experimenting at this point to see how it behaves and what works. early days, but it’s a real step toward a model that actually learns what fire looks like instead of just matching colors. good progress on the part of this project."}, {"post_id": 18514, "ts": "2026-06-29T18:09:54Z", "hours": 18.7639, "text": "Devlog #13 : built a fire detection system for my drone’s Pi i genuinely lost my sanity working on ts (Everything is on gh) started on the payload for my autonomous quad: real time fire detection running on the Raspberry Pi. went classical CV with OpenCV instead of training a model. Since it has to run fully offline on the drone (no internet up there) so a heavy ML model was out. turns out you get pretty far with just color + motion. how it works: grabs the warm/bright pixels (orange/red/yellow in HSV, plus an R≥G≥B rule so it’s actually fire toned, not just bright) flicker analysis over a few frames. ts is the part that matters. real flame shimmers frame to frame, a static orange thing (a ball, a jacket, a sunset) doesn’t, so it won’t false trigger on every orange object it sees debounces over several frames so one noisy frame can’t trip it spits out a 0-100% confidence from area + flicker + persistence the two bits that do the work. color mask first: # warm/bright flame colors warm = cv2 . inRange ( hsv , ( 0 , sat_min , val_min ), ( 35 , 255 , 255 )) warm |= cv2 . inRange ( hsv , ( 170 , sat_min , val_min ), ( 179 , 255 , 255 )) # fire skews R >= G >= B with a real red lead, not just any bright pixel b , g , r = cv2 . split ( bgr . astype ( np . int16 )) order = (( r >= g ) & ( g >= b ) & ( r > 150 ) & (( r - b ) > 28 )). astype ( np . uint8 ) * 255 warm = cv2 . bitwise_and ( warm , order ) then the flicker check. just how much the fire region changed since last frame: diff = cv2 . absdiff ( mask , prev_mask ) flicker = np . count_nonzero ( diff ) / max ( fire_area , 1 ) # static orange object -> ~0 real flame -> way higher built a web dashboard for it too (Flask). same code runs on my laptop off the webcam to test, then goes straight on the Pi headless and i open it from my laptop browser over wifi. console sits calm/cyan while scanning, goes full red + pulsing + beeping the sec it locks fire. got live sliders to tune sensitivity so i’m not editing code every time. tested 4k fireplace video, locks on clean. waved random orange stuff it’s not certified or anything. classical CV WILL false trigger in harsh light so next: wire the “fire detected” event to grab the GPS coord off the flight controller and trigger a loiter so the drone marks the spot. btw if anyone’s done fire/smoke detection on a Pi 4 lmk if you went CV or tflite, curious what fps you got. 🫡"}, {"post_id": 16925, "ts": "2026-06-27T14:18:40Z", "hours": 11.3347, "text": "Devlog #12 : scrapped my CV code, went full YOLO ok!! so i went on a learning spree today and a LOT happened. ngl one of those days where you start the morning thinking you know stuff and end it realizing you knew nothing. ##i was doing my CV wrong so my old fire detection was classical CV, just color matching + flicker. cool little hack and it technically worked, but tbh it was way too fragile. anything orange in bright light could set it off, and it’s is supposed to fly on a drone in the sun, so that’s not happening. so i did the painful thing and scrapped the whole lot. felt bad deleting code that “worked” but it was never gonna be reliable enough out in the real world. went down the YOLO rabbit hole spent basically the whole day researching YOLO (you only look once, the object detection one). instead of me hand coding what fire “looks like” with color rules, the model actually learns it from examples. way more robust to lighting, angles, all the randome stuff a drone is gonna run into. got a basic YOLO model up and running. its rough rn but its already a different league from the color matching. side quest: mediapipe body tracking also messed around with mediapipe today as a practice project, tracked my own body/pose in real time. wasnt strictly for the drone, just wanted to get comfortable with actual CV pipelines and see how the landmark tracking works under the hood. hardware: turned my ceiling into a drone im on vacation so no real flying, but i still wanted to test from a drone’s POV. so i straight up taped a webcam to my ceiling pointing straight down. now i can test the CV from that top down birds eye angle, which is way closer to what the drone actually sees than my laptop cam pointed at my face. next up train the YOLO model on a proper fire dataset run it against the ceiling cam footage check fps on my laptop vs what i’ll realistically get on the Pi 🫡"}, {"post_id": 16627, "ts": "2026-06-27T01:24:09Z", "hours": 16.1558, "text": "Devlog #11: started the new CV code, deciding on the approach got through about half the CV code today, good progress on the rewrite. right now i’m deciding between two routes for the actual fire recognition: tensorflow + mobilenet-SSD — a proper deep learning object detector. heavier, but it actually learns what fire looks like, so it should handle different lighting and angles way better. regular opencv + a few libraries — lighter and simpler, runs easy on the Pi, but less robust. still weighing it. mobilenet-SSD is probably the stronger long term call since it generalizes better, but opencv is much lighter on the Pi, so i want to see what framerate i actually get before committing to either. next: benchmark both and pick one."}, {"post_id": 12308, "ts": "2026-06-20T02:48:00Z", "hours": 8.32, "text": "Devlog #10: motor test issues and a flight controller swap not gonna lie, things went downhill pretty fast today. i celebrated a bit early. all my motors spun fine on the individual motor test, so i figured i was basically there. then i hit “test all” and only 2 of the 4 motors spun. and it kept happening. i was sure it was a software/parameter thing at first, so i spent hours over the past few days going through ardupilot params trying to get all 4 to fire at once. couldn’t get it. every motor spins perfectly on its own, but only 2 ever spin on the test all. after sitting with it for a while, i’m pretty sure the issue comes down to the flight controller. i’d been running a cheap board that’s really built for fixed wing, and going through the ardupilot docs it just wasn’t the right fit for what i’m doing. so i’ve ordered a proper flight controller to swap in. the timing isn’t great. i leave for my trip the day after tomorrow, so for the next month i’m stuck on just the software side, no hardware. the new FC is on its way but realistically i can’t promise the drone actually flies until the end of july. bit of a setback, but at least i’ve got a direction now. onwards."}, {"post_id": 11790, "ts": "2026-06-19T05:52:36Z", "hours": 10.8169, "text": "Devlog #9: learning the AI side + designing a custom PCB really good, productive session today. spent the whole day learning. first half went into the machine learning side. since i want the algorithm to actually find and report fires properly, i went down a full rabbit hole on how AI works under the hood, neural networks, all of it. wanted to actually understand what’s going on instead of just copy pasting a model i don’t really get. second half i switched gears to hardware and started designing a PCB. right now my gps/compass, the SBC, and the ESC are all separate boards basically taped to a surface, which is messy and not great for an actual flying build. the plan is to get all of them onto one clean board instead. good mix of software and hardware today, feels like things are starting to come together."}, {"post_id": 11141, "ts": "2026-06-18T07:06:04Z", "hours": 4.8339, "text": "Devlog #8: it finally works oh my gosh. amazing and relieving day today. i’d been pretty down about this for a while. my motors just wouldn’t spin during the bench test, and i’d already ordered three ESCs, new motors, and new wires trying to fix it. none of it worked, so i returned all of it. today my new ESC finally showed up. i leave for india on sunday for a month, so these next few days are my only window to get any hardware done. so i sat down and meticulously (and painfully) soldered every joint, checking continuity with my multimeter over and over. a few connections literally fell apart while i was hooking up the wires, so i had to stop and resolder them. just wanted the wiring to be perfect this time. then the worst moment: i tested it and nothing worked. again. i was genuinely gutted. but then i noticed an orange cable just sitting there, not plugged in, and it clicked, that was the ground (GND). i connected the ESC ground to the FC ground, ran the motor test, and everything spun. all of it. no errors except some OSD stuff, which is just a missing SD card. massive relief. that one unplugged ground wire was the whole thing. next month in india i’ll be working on the code side of the drone, then test for flight again when i get back."}, {"post_id": 9775, "ts": "2026-06-16T06:54:09Z", "hours": 6.1247, "text": "Devlog #7: new ESC, somehow worse wow, rough day. got my new ESC in and resoldered every connection as cleanly as i could. but somehow it went the wrong way, instead of just one motor not working, now none of them work. so that’s fun. i’ve ordered another one. before i jump to blaming the flight controller this time, i want to go back through the wiring really meticulously and rule that out first. feels like it’s something small i keep missing. annoying timing too. i’m away from the 20th to the 20th, basically a month, so i’ll be forced to work on just the software side until i’m back. wish me luck pls."}, {"post_id": 7324, "ts": "2026-06-12T06:19:40Z", "hours": 4.2369, "text": "Devlog #6: down to a board problem today was a sad one. my new wires finally came and i swapped them all in, but the one motor still wouldn’t work. after that i’ve basically narrowed it down to a board problem. either i damaged the FC with my rough soldering, or it had some issue before i even started. so i’ve ordered a new board. i’m going on vacation soon, and i can only hope it arrives before i leave. if it doesn’t, i’ll be left to just improve, fine tune, and perfect the ML and software side until i’m back. not the day i wanted, but at least i think i know where the problem is now."}, {"post_id": 6395, "ts": "2026-06-10T19:14:57Z", "hours": 5.2294, "text": "Devlog #5: still chasing the one dead motor tested the drone with the battery again and the one motor still wouldn’t spin. while i was at it i calibrated most of the sensors, the accelerometer, GPS, and compass, so at least that side is sorted now. then i swapped the motor out again just to rule it out, and it still didn’t work. at this point i’m fairly sure it’s either an ESC problem or a wiring issue. my new wires come tomorrow, so i’ll be able to narrow it down properly and do what i can to fix it. slow progress, but i’m closing in on it."}, {"post_id": 6012, "ts": "2026-06-10T02:29:49Z", "hours": 8.6739, "text": "Devlog #4: chasing the dead motor + first autonomous code plugged in the battery and ran a test today, found a few bugs. the main one: one of the motors still wouldn’t work. so i went through it properly this time. resoldered all the connections, swapped in a known-working motor, still no spin. then i uncapped the battery pull going to that motor to check if it was a power issue, and still nothing. resoldered everything one more time, and it still wouldn’t spin. at that point i figured it has to be the bullet plug connectors, so i’ve ordered new ones. on the software side i actually made some progress, wrote some of the python autonomous flight code by SSHing into the raspberry pi. nice to move the code forward while the hardware’s still being stubborn."}, {"post_id": 4293, "ts": "2026-06-07T15:37:37Z", "hours": 9.2333, "text": "Devlog #3: designed and printed the entire drone chassis big hardware milestone today, i designed and 3d printed the entire drone chassis. did the whole design in onshape. spent a good while on the layout because the chassis has to hold everything: the flight controller, the ESC, the motor arms, the battery, the raspberry pi, and the gps/compass. i measured each component so i could put proper mounting holes and slots for all of them instead of just taping stuff to a plate. the motor arm spacing and overall geometry took the most back and forth, it has to be symmetric and square or the drone won’t fly right. M after a few tweaks to the model i sent it to the printer. next up is mounting everything onto it and starting the wiring."}, {"post_id": 3984, "ts": "2026-06-07T03:54:56Z", "hours": 6.7931, "text": "Designed and assembled the legs for my drone. I also soldered some electronic connections to the ESC (Electronic Speed Controller)."}, {"post_id": 3801, "ts": "2026-06-06T21:04:18Z", "hours": 0.8586, "text": "Devlog #1: designing and printing the arms kicking off a new project, an autonomous fire detecting and firefighting drone. the goal is a drone that can find and report fires on its own. starting with the hardware, so today i designed and printed the arms. did the design in onshape. the arms are carbon fiber tubes for the length and stiffness, paired with 3d printed plastic attachments that clamp onto the tubes and hold the motors out at the ends. carbon fiber keeps them light and rigid, which is exactly what you want for the arms, and the printed parts let me make mounts that actually fit my motors and bolt onto the frame. this session was mostly the build and assembly side, getting the carbon fiber pieces and the plastic attachments fitted together. feels good to have the first structural parts of the drone done. solid start, the skeleton’s starting to take shape."}]...
|
Title: Prometheus by @rishithc | Stardance
Devlog Title: Prometheus by @rishithc | Stardance
Devlogs:
Devlog #1: designing and printing the arms kicking off a new project, an autonomous fire detecting and firefighting drone. the goal is a drone that can find and report fires on its own. starting with the hardware, so today i designed and printed the arms. did the design in onshape. the arms are carbon fiber tubes for the length and stiffness, paired with 3d printed plastic attachments that clamp onto the tubes and hold the motors out at the ends. carbon fiber keeps them light and rigid, which is exactly what you want for the arms, and the printed parts let me make mounts that actually fit my motors and bolt onto the frame. this session was mostly the build and assembly side, getting the carbon fiber pieces and the plastic attachments fitted together. feels good to have the first structural parts of the drone done. solid start, the skeleton’s starting to take shape.
Designed and assembled the legs for my drone. I also soldered some electronic connections to the ESC (Electronic Speed Controller).
Devlog #3: designed and printed the entire drone chassis big hardware milestone today, i designed and 3d printed the entire drone chassis. did the whole design in onshape. spent a good while on the layout because the chassis has to hold everything: the flight controller, the ESC, the motor arms, the battery, the raspberry pi, and the gps/compass. i measured each component so i could put proper mounting holes and slots for all of them instead of just taping stuff to a plate. the motor arm spacing and overall geometry took the most back and forth, it has to be symmetric and square or the drone won’t fly right. M after a few tweaks to the model i sent it to the printer. next up is mounting everything onto it and starting the wiring.
Devlog #4: chasing the dead motor + first autonomous code plugged in the battery and ran a test today, found a few bugs. the main one: one of the motors still wouldn’t work. so i went through it properly this time. resoldered all the connections, swapped in a known-working motor, still no spin. then i uncapped the battery pull going to that motor to check if it was a power issue, and still nothing. resoldered everything one more time, and it still wouldn’t spin. at that point i figured it has to be the bullet plug connectors, so i’ve ordered new ones. on the software side i actually made some progress, wrote some of the python autonomous flight code by SSHing into the raspberry pi. nice to move the code forward while the hardware’s still being stubborn.
Devlog #5: still chasing the one dead motor tested the drone with the battery again and the one motor still wouldn’t spin. while i was at it i calibrated most of the sensors, the accelerometer, GPS, and compass, so at least that side is sorted now. then i swapped the motor out again just to rule it out, and it still didn’t work. at this point i’m fairly sure it’s either an ESC problem or a wiring issue. my new wires come tomorrow, so i’ll be able to narrow it down properly and do what i can to fix it. slow progress, but i’m closing in on it.
Devlog #6: down to a board problem today was a sad one. my new wires finally came and i swapped them all in, but the one motor still wouldn’t work. after that i’ve basically narrowed it down to a board problem. either i damaged the FC with my rough soldering, or it had some issue before i even started. so i’ve ordered a new board. i’m going on vacation soon, and i can only hope it arrives before i leave. if it doesn’t, i’ll be left to just improve, fine tune, and perfect the ML and software side until i’m back. not the day i wanted, but at least i think i know where the problem is now.
Devlog #7: new ESC, somehow worse wow, rough day. got my new ESC in and resoldered every connection as cleanly as i could. but somehow it went the wrong way, instead of just one motor not working, now none of them work. so that’s fun. i’ve ordered another one. before i jump to blaming the flight controller this time, i want to go back through the wiring really meticulously and rule that out first. feels like it’s something small i keep missing. annoying timing too. i’m away from the 20th to the 20th, basically a month, so i’ll be forced to work on just the software side until i’m back. wish me luck pls.
Devlog #8: it finally works oh my gosh. amazing and relieving day today. i’d been pretty down about this for a while. my motors just wouldn’t spin during the bench test, and i’d already ordered three ESCs, new motors, and new wires trying to fix it. none of it worked, so i returned all of it. today my new ESC finally showed up. i leave for india on sunday for a month, so these next few days are my only window to get any hardware done. so i sat down and meticulously (and painfully) soldered every joint, checking continuity with my multimeter over and over. a few connections literally fell apart while i was hooking up the wires, so i had to stop and resolder them. just wanted the wiring to be perfect this time. then the worst moment: i tested it and nothing worked. again. i was genuinely gutted. but then i noticed an orange cable just sitting there, not plugged in, and it clicked, that was the ground (GND). i connected the ESC ground to the FC ground, ran the motor test, and everything spun. all of it. no errors except some OSD stuff, which is just a missing SD card. massive relief. that one unplugged ground wire was the whole thing. next month in india i’ll be working on the code side of the drone, then test for flight again when i get back.
Devlog #9: learning the AI side + designing a custom PCB really good, productive session today. spent the whole day learning. first half went into the machine learning side. since i want the algorithm to actually find and report fires properly, i went down a full rabbit hole on how AI works under the hood, neural networks, all of it. wanted to actually understand what’s going on instead of just copy pasting a model i don’t really get. second half i switched gears to hardware and started designing a PCB. right now my gps/compass, the SBC, and the ESC are all separate boards basically taped to a surface, which is messy and not great for an actual flying build. the plan is to get all of them onto one clean board instead. good mix of software and hardware today, feels like things are starting to come together.
Devlog #10: motor test issues and a flight controller swap not gonna lie, things went downhill pretty fast today. i celebrated a bit early. all my motors spun fine on the individual motor test, so i figured i was basically there. then i hit “test all” and only 2 of the 4 motors spun. and it kept happening. i was sure it was a software/parameter thing at first, so i spent hours over the past few days going through ardupilot params trying to get all 4 to fire at once. couldn’t get it. every motor spins perfectly on its own, but only 2 ever spin on the test all. after sitting with it for a while, i’m pretty sure the issue comes down to the flight controller. i’d been running a cheap board that’s really built for fixed wing, and going through the ardupilot docs it just wasn’t the right fit for what i’m doing. so i’ve ordered a proper flight controller to swap in. the timing isn’t great. i leave for my trip the day after tomorrow, so for the next month i’m stuck on just the software side, no hardware. the new FC is on its way but realistically i can’t promise the drone actually flies until the end of july. bit of a setback, but at least i’ve got a direction now. onwards.
Devlog #11: started the new CV code, deciding on the approach got through about half the CV code today, good progress on the rewrite. right now i’m deciding between two routes for the actual fire recognition: tensorflow + mobilenet-SSD — a proper deep learning object detector. heavier, but it actually learns what fire looks like, so it should handle different lighting and angles way better. regular opencv + a few libraries — lighter and simpler, runs easy on the Pi, but less robust. still weighing it. mobilenet-SSD is probably the stronger long term call since it generalizes better, but opencv is much lighter on the Pi, so i want to see what framerate i actually get before committing to either. next: benchmark both and pick one.
Devlog #12 : scrapped my CV code, went full YOLO ok!! so i went on a learning spree today and a LOT happened. ngl one of those days where you start the morning thinking you know stuff and end it realizing you knew nothing. ##i was doing my CV wrong so my old fire detection was classical CV, just color matching + flicker. cool little hack and it technically worked, but tbh it was way too fragile. anything orange in bright light could set it off, and it’s is supposed to fly on a drone in the sun, so that’s not happening. so i did the painful thing and scrapped the whole lot. felt bad deleting code that “worked” but it was never gonna be reliable enough out in the real world. went down the YOLO rabbit hole spent basically the whole day researching YOLO (you only look once, the object detection one). instead of me hand coding what fire “looks like” with color rules, the model actually learns it from examples. way more robust to lighting, angles, all the randome stuff a drone is gonna run into. got a basic YOLO model up and running. its rough rn but its already a different league from the color matching. side quest: mediapipe body tracking also messed around with mediapipe today as a practice project, tracked my own body/pose in real time. wasnt strictly for the drone, just wanted to get comfortable with actual CV pipelines and see how the landmark tracking works under the hood. hardware: turned my ceiling into a drone im on vacation so no real flying, but i still wanted to test from a drone’s POV. so i straight up taped a webcam to my ceiling pointing straight down. now i can test the CV from that top down birds eye angle, which is way closer to what the drone actually sees than my laptop cam pointed at my face. next up train the YOLO model on a proper fire dataset run it against the ceiling cam footage check fps on my laptop vs what i’ll realistically get on the Pi 🫡
Devlog #13 : built a fire detection system for my drone’s Pi i genuinely lost my sanity working on ts (Everything is on gh) started on the payload for my autonomous quad: real time fire detection running on the Raspberry Pi. went classical CV with OpenCV instead of training a model. Since it has to run fully offline on the drone (no internet up there) so a heavy ML model was out. turns out you get pretty far with just color + motion. how it works: grabs the warm/bright pixels (orange/red/yellow in HSV, plus an R≥G≥B rule so it’s actually fire toned, not just bright) flicker analysis over a few frames. ts is the part that matters. real flame shimmers frame to frame, a static orange thing (a ball, a jacket, a sunset) doesn’t, so it won’t false trigger on every orange object it sees debounces over several frames so one noisy frame can’t trip it spits out a 0-100% confidence from area + flicker + persistence the two bits that do the work. color mask first: # warm/bright flame colors warm = cv2 . inRange ( hsv , ( 0 , sat_min , val_min ), ( 35 , 255 , 255 )) warm |= cv2 . inRange ( hsv , ( 170 , sat_min , val_min ), ( 179 , 255 , 255 )) # fire skews R >= G >= B with a real red lead, not just any bright pixel b , g , r = cv2 . split ( bgr . astype ( np . int16 )) order = (( r >= g ) & ( g >= b ) & ( r > 150 ) & (( r - b ) > 28 )). astype ( np . uint8 ) * 255 warm = cv2 . bitwise_and ( warm , order ) then the flicker check. just how much the fire region changed since last frame: diff = cv2 . absdiff ( mask , prev_mask ) flicker = np . count_nonzero ( diff ) / max ( fire_area , 1 ) # static orange object -> ~0 real flame -> way higher built a web dashboard for it too (Flask). same code runs on my laptop off the webcam to test, then goes straight on the Pi headless and i open it from my laptop browser over wifi. console sits calm/cyan while scanning, goes full red + pulsing + beeping the sec it locks fire. got live sliders to tune sensitivity so i’m not editing code every time. tested 4k fireplace video, locks on clean. waved random orange stuff it’s not certified or anything. classical CV WILL false trigger in harsh light so next: wire the “fire detected” event to grab the GPS coord off the flight controller and trigger a loiter so the drone marks the spot. btw if anyone’s done fire/smoke detection on a Pi 4 lmk if you went CV or tflite, curious what fps you got. 🫡
Devlog #14: building the dataset + training a tensorflow model spent today on the data side of fire detection, which is half the battle with ML. to train a model to recognize fire i need a solid labeled dataset, so first i built an image scraper. it crawls the web usinf breadth first search, going level by level through pages and pulling images as it goes. i used bidirectional bfs to expand the search from two fronts and cover more ground instead of just crawling one direction. ended up pulling a bunch of images, including a lot of tricky ones like trees and random orange stuff that a fire model could easily get confused by. then i built a small labeling tool to actually tag all of it. it shows me one image at a time, a tree, an orange object, an actual fire, and i just mark it as fire or no fire. way faster than sorting through folders by hand, and getting those confusing orange non-fire images labeled is exactly what stops the model from false triggering later. with some data labeled i started training a tensorflow model on it, mostly experimenting at this point to see how it behaves and what works. early days, but it’s a real step toward a model that actually learns what fire looks like instead of just matching colors. good progress on the part of this project.
Devlog #15: training my own model wasn’t the move yea so training my own model wasnt the best idea. after hours of clicking through my webscraper’s image results and marking them, i ran a benchmark myself by putting on youtube videos of wildfires from a sky perspective. it saw the smoke in the distance and gave that as the fire, when the real fire was miles away. it also found the sun and clouds as a fire. so, false positives everywhere. so today i basically tested and worked with existing solutions instead, like this one: https://github.com/AlimTleuliyev/wildfire-detection , plus other open source alternatives on kaggle. but yea, overall today i felt retrogressed, and i’m thinking of going back to CV. This article also helped a lot https://www.mdpi.com/2571-6255/7/4/140 .
Devlog #16: I probably should have done this earlier :( yea so while on vacation I decided to rework the weight and thrust ratios that the motors were producing with 11x7 props. I found out that my drone will not be able to fly SMOOTHLY. So I decided too look into why, one of the big reasons were that it was heavy, and two it wasn’t aerodynamic. So today I tried to kill two birds with one stone, (I also worked on my ML for a good portion of the time, but I feel this is more important). I ran digital wind tunnel tests and kept redesigning and testing until I landed on what I have now. I plan to make this out of carbon fiber which will be expensive, but ig that’s part of the process.
Devlog #17: I tested a lot tdy as well as designed new components I submitted my project, as is, to the Outpost fund, and I got some feedback. Mostly everything was good except for some issues with funding an NVDIA devkit :))), but the biggest issue was that I couldn’t buy a flight controller. In an devlog before, I mentioned and shows a picture of me designing a custom pcb, but I have not worked on that since. So today I fired up Kikad and designed layer 2 of my FC (easier, layer one has a lot of components that I need to import). I also spent a good chunk of today refining my 3d model, I used Air Shaper and SimScale and I aerodynamic tested all of the designs, I also asked claude for some ideas of how to make my .stls better. @vrunchil7 is da goat frfr he taught me how and what kikad is.
Devlog #18: A GREAT way to start working on your project again 😩 I’ve taken a break these past few days, realizing that a vacation exists for a reason! Today, however, I didn’t want to fall behind schedule. Since I also want grants to use a premium carbon fiber frame and all I need is to finish my PCB, I spent the day working in KiCad. Truth be told, the best way to learn is by doing—I thought the same about CAD, and I feel the same about PCB design. I made the executive decision to make a double-sided PCB rather than adding more layers, as it will be much simpler. Anyway, here are my final mockups.
Ships:
I made an autonomous drone. The most challenging part was the soldering. The soldering was quite hard for me and there were times where i burnt my hand...
|
1792875212.5828192
|
1793739212.5828192
|
|
10039
|
Mucize Doktor by @kax675 | Stardance
|
kax675
|
1
|
1.0
|
1
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-06T21:44:26Z", "hours": 1.0, "multiplier": 1.73, "payout": 1, "blessing": "neutral", "text": "I really wanted to make a real life example of a Turkish meme. I hope it gets attention on different platforms like the original meme.", "repo": "https://github.com/Kax675/mucize-doktor", "demo": "https://kax675.github.io/mucize-doktor/"}]...
|
[{"post_id": 3808, "ts": "2026 [{"post_id": 3808, "ts": "2026-06-06T21:15:41Z", "hours": 0.6342, "text": "The first working prototype! This is a parody re-make of the viral Turkish “Mucize Doktor Planet” meme in React and Three.js!"}]...
|
Title: Mucize Doktor by @kax675 | Stardance
Devlo Title: Mucize Doktor by @kax675 | Stardance
Devlogs:
The first working prototype! This is a parody re-make of the viral Turkish “Mucize Doktor Planet” meme in React and Three.js!
Ships:
I really wanted to make a real life example of a Turkish meme. I hope it gets attention on different platforms like the original meme....
|
1793256907.1622496
|
1793343307.1622496
|
|
10040
|
Alarm Clock by @laithh | Stardance
|
laithh
|
0
|
0.55
|
0
|
[]
|
[{"post_id": 4203, "ts": "2026 [{"post_id": 4203, "ts": "2026-06-07T13:07:18Z", "hours": 0.5542, "text": "I wanted to jump straight into coding since I have the basic build here (pico connected to buzzer lel),, but I think I might need to do more planning. What I’m probably going to do next is journal out how I want the alarm to work, figure out what connects to what, and maybe write some pseudo code on paper along w/ the diagram."}]...
|
Title: Alarm Clock by @laithh | Stardance
Devlogs Title: Alarm Clock by @laithh | Stardance
Devlogs:
I wanted to jump straight into coding since I have the basic build here (pico connected to buzzer lel),, but I think I might need to do more planning. What I’m probably going to do next is journal out how I want the alarm to work, figure out what connects to what, and maybe write some pseudo code on paper along w/ the diagram....
|
1793361292.8169413
|
1793966092.8169413
|
|
10041
|
Custom Wikipedia Page Generator by @eytangut | Sta Custom Wikipedia Page Generator by @eytangut | Stardance...
|
eytangut
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Custom Wikipedia Page Generator by @eytangu Title: Custom Wikipedia Page Generator by @eytangut | Stardance...
|
1793188079.7496052
|
1793792879.7496052
|
|
10042
|
Deep Focus by @RomanticTinkerer | Stardance
|
RomanticTinkerer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Deep Focus by @RomanticTinkerer | Stardance
|
1793306856.8214462
|
1793911656.8214462
|
|
10043
|
CoolCompanion by @Gamer123 | Stardance
|
Gamer123
|
0
|
43.13
|
0
|
[]
|
[{"post_id": 75081, "ts": "202 [{"post_id": 75081, "ts": "2026-09-29T02:53:21Z", "hours": 3.44, "text": "Dev Log #12 Its done! All that is left is to film the video and get it submitted before the closing date…. I may have taken a break that was about a month long…"}, {"post_id": 35072, "ts": "2026-07-26T08:10:01Z", "hours": 4.5008, "text": "Dev Log #11 GOOD NEWS THE PERF BOARDS WORKED! So it took me a long time to get the perf boards to work but now they work! So now i got to finish the firmware and finish the soldering for the temp sensor"}, {"post_id": 34455, "ts": "2026-07-25T05:44:05Z", "hours": 1.4992, "text": "Dev Log #10 So i got my new boards, Minus the air bubbles under the solder pads, I tried them and the same design flaw remains, Now I’m going to perf board, if this doesn’t work then i got to get even more creative for this. Or if i can find out the flaw exactly then ill redesign PCB’s"}, {"post_id": 31096, "ts": "2026-07-19T06:59:06Z", "hours": 3.3553, "text": "Dev Log #9 More problems, so during my process of getting a board to work so i can finish software, i discovered a design error and i cant track back exactly what the problem is however its causing major issues, so now back to the drawing board…"}, {"post_id": 30494, "ts": "2026-07-18T03:35:26Z", "hours": 1.0167, "text": "Dev Log #8 Slightly more interesting news, So i received my new boards from oshpark and started soldering however then i noticed that the solder mask was not fully cured on the boards and have since contacted support and now it is in the works of getting me replacements.. For now im going to try and use a pcb from the previous manufacturer to try and get a working prototype again so i can continue work on software."}, {"post_id": 23322, "ts": "2026-07-06T06:24:48Z", "hours": 4.6553, "text": "Dev Log #7 Well…. Sad news… The PCB that i had designed and had printed and i was assembling… Somehow the trace broke internally. I verified it with a multimeter that the 5v rail was not functioning properly and took the necessary troubleshooting steps. This all happened when i was working on the code, Not really sure how it broke but now i have decided to make a few changes to the board pad sizes for easier soldering on this version, and to get it from a new manufacture. Time to wait for shipping again, Wish me luck! (Also the code i am making is coming along well!)"}, {"post_id": 19847, "ts": "2026-07-01T07:46:33Z", "hours": 10.4306, "text": "Dev Log #6 After much much time, I finally received the parts and got to soldering… unfortunately i messed up one of the boards…. But i tried again with the parts i had left over, and it works! all that is missing is the fan being connected but im waiting to build software before that! Thank you for sticking along with me on this journey hopefully it can be done soon! (And yes i did have to do some repairs on the circuit design as the cheap board pads broke)"}, {"post_id": 11750, "ts": "2026-06-19T04:12:23Z", "hours": 3.9244, "text": "Dev Log #5 It’s almost done, everyone! The model has been completed, the circuitry is done, and the PCB is finished. All that is left is to assemble it all together (sanding 3D prints, soldering, etc.) Looking forward to showing my progress. All the parts should be in my hands in about a week or so. See you then!"}, {"post_id": 10497, "ts": "2026-06-17T07:42:22Z", "hours": 5.1117, "text": "Dev Log #4 Work and more work, Over the last day or so i have been working on the PCB, after forgetting to add the temperature sensor to the test circuit i went back and added that as well, the PCB is almost complete all is left is routing the traces and some last finishing touches, here is a rundown of what has been done so far across the project Completed sketches; Completed Test Circuitry; 90% Completion of the 3D model; 85% Completion of the PCB; Overall project: ~75%"}, {"post_id": 9549, "ts": "2026-06-15T22:32:17Z", "hours": 1.2525, "text": "Dev Log #3 Major Major progress has been made so far; the circuit has been tested and is working, showing the current fan RPM and the ability to change the fan speed via the rotary encoder. It is only on breadboards; however, the next step is PCB design, then finishing the model!"}, {"post_id": 7775, "ts": "2026-06-13T00:03:11Z", "hours": 2.7378, "text": "Dev Log #2 In the past several days, I have been working on the enclosure for the whole device, With it being close to 90% done, with the only left to do is finish the circuit then make sure it will all fit inside. The “CoolCompanion” is one more step towards revolutionizing your way of cooling."}, {"post_id": 5461, "ts": "2026-06-09T08:03:59Z", "hours": 1.205, "text": "We ALL have this problem! No matter if you are at home or at the office, we ALL have this problem! The problem I am talking about? Well, I mean a very simple one: being too hot and making you uncomfortable. Normal fans? They may work just fine; however, they are not smart. They don’t know when you are comfortable, and they don’t know how annoying they may be. As someone who lives in Las Vegas, Nevada, where temperatures can reach past a hundred degrees Fahrenheit (~38 degrees Celsius), I believe that I am very experienced in this topic and well equipped to make a solution to this problem. No matter where you may live, this may help you. And the solution? Sensors and the ability to tune your fan to your preferences! This includes: a temperature sensor a rotary encoder an LCD/OLED screen This means you can tune your fan to turn on and off whenever it gets too hot, no more fighting over turning the fan on and off manually, and the ability to change fan speed allows you to make sure the fan doesn’t get too loud or simply so it doesn’t mess up your hair (totally no personal experience in this) Within my first hour of this project, I have worked on getting measurements and working on designs for my project, inspired by a classic desktop fan."}]...
|
Title: CoolCompanion by @Gamer123 | Stardance
Dev Title: CoolCompanion by @Gamer123 | Stardance
Devlogs:
We ALL have this problem! No matter if you are at home or at the office, we ALL have this problem! The problem I am talking about? Well, I mean a very simple one: being too hot and making you uncomfortable. Normal fans? They may work just fine; however, they are not smart. They don’t know when you are comfortable, and they don’t know how annoying they may be. As someone who lives in Las Vegas, Nevada, where temperatures can reach past a hundred degrees Fahrenheit (~38 degrees Celsius), I believe that I am very experienced in this topic and well equipped to make a solution to this problem. No matter where you may live, this may help you. And the solution? Sensors and the ability to tune your fan to your preferences! This includes: a temperature sensor a rotary encoder an LCD/OLED screen This means you can tune your fan to turn on and off whenever it gets too hot, no more fighting over turning the fan on and off manually, and the ability to change fan speed allows you to make sure the fan doesn’t get too loud or simply so it doesn’t mess up your hair (totally no personal experience in this) Within my first hour of this project, I have worked on getting measurements and working on designs for my project, inspired by a classic desktop fan.
Dev Log #2 In the past several days, I have been working on the enclosure for the whole device, With it being close to 90% done, with the only left to do is finish the circuit then make sure it will all fit inside. The “CoolCompanion” is one more step towards revolutionizing your way of cooling.
Dev Log #3 Major Major progress has been made so far; the circuit has been tested and is working, showing the current fan RPM and the ability to change the fan speed via the rotary encoder. It is only on breadboards; however, the next step is PCB design, then finishing the model!
Dev Log #4 Work and more work, Over the last day or so i have been working on the PCB, after forgetting to add the temperature sensor to the test circuit i went back and added that as well, the PCB is almost complete all is left is routing the traces and some last finishing touches, here is a rundown of what has been done so far across the project Completed sketches; Completed Test Circuitry; 90% Completion of the 3D model; 85% Completion of the PCB; Overall project: ~75%
Dev Log #5 It’s almost done, everyone! The model has been completed, the circuitry is done, and the PCB is finished. All that is left is to assemble it all together (sanding 3D prints, soldering, etc.) Looking forward to showing my progress. All the parts should be in my hands in about a week or so. See you then!
Dev Log #6 After much much time, I finally received the parts and got to soldering… unfortunately i messed up one of the boards…. But i tried again with the parts i had left over, and it works! all that is missing is the fan being connected but im waiting to build software before that! Thank you for sticking along with me on this journey hopefully it can be done soon! (And yes i did have to do some repairs on the circuit design as the cheap board pads broke)
Dev Log #7 Well…. Sad news… The PCB that i had designed and had printed and i was assembling… Somehow the trace broke internally. I verified it with a multimeter that the 5v rail was not functioning properly and took the necessary troubleshooting steps. This all happened when i was working on the code, Not really sure how it broke but now i have decided to make a few changes to the board pad sizes for easier soldering on this version, and to get it from a new manufacture. Time to wait for shipping again, Wish me luck! (Also the code i am making is coming along well!)
Dev Log #8 Slightly more interesting news, So i received my new boards from oshpark and started soldering however then i noticed that the solder mask was not fully cured on the boards and have since contacted support and now it is in the works of getting me replacements.. For now im going to try and use a pcb from the previous manufacturer to try and get a working prototype again so i can continue work on software.
Dev Log #9 More problems, so during my process of getting a board to work so i can finish software, i discovered a design error and i cant track back exactly what the problem is however its causing major issues, so now back to the drawing board…
Dev Log #10 So i got my new boards, Minus the air bubbles under the solder pads, I tried them and the same design flaw remains, Now I’m going to perf board, if this doesn’t work then i got to get even more creative for this. Or if i can find out the flaw exactly then ill redesign PCB’s
Dev Log #11 GOOD NEWS THE PERF BOARDS WORKED! So it took me a long time to get the perf boards to work but now they work! So now i got to finish the firmware and finish the soldering for the temp sensor
Dev Log #12 Its done! All that is left is to film the video and get it submitted before the closing date…. I may have taken a break that was about a month long…...
|
1793397242.5899458
|
1794002042.5899458
|
|
10044
|
Space Flight Simulator: Decompiled by @HumanGarbag Space Flight Simulator: Decompiled by @HumanGarbageBag | Stardance...
|
HumanGarbageBag
|
1
|
11.0
|
39
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-15T18:56:52Z", "hours": 11.0, "multiplier": 3.53, "payout": 39, "blessing": "neutral", "text": "This is a full decompile/port of Space Flight simulator. building for windows, and webgl work for sure, it is unknown if linux or other build options work. it was really hard to learn how to decompile and port unity games.", "repo": "https://github.com/ytrewq000/Space-Flight-Simulator-Decompiled/", "demo": "https://dooble.gay/SFS"}]...
|
[{"post_id": 29036, "ts": "202 [{"post_id": 29036, "ts": "2026-07-15T18:04:21Z", "hours": 9.0292, "text": "ITS FINALLY DONE, see it on https://dooble.gay/SFS . took a long break from programming but we so back"}, {"post_id": 3848, "ts": "2026-06-06T22:20:38Z", "hours": 1.4742, "text": "I FIXED IT, IM SO HAPPY. the issue was the parts shader, i had to decompile it with uscsandbox. its so close to done, i hope i am able to get credit for my 41 hours spent on this"}, {"post_id": 3662, "ts": "2026-06-06T18:16:50Z", "hours": 0.5353, "text": "Fixing this GODDAMN BUG THAT DOESNT RENDER THE ICONS IN BUILD MODE"}]...
|
Title: Space Flight Simulator: Decompiled by @Huma Title: Space Flight Simulator: Decompiled by @HumanGarbageBag | Stardance
Devlogs:
Fixing this GODDAMN BUG THAT DOESNT RENDER THE ICONS IN BUILD MODE
I FIXED IT, IM SO HAPPY. the issue was the parts shader, i had to decompile it with uscsandbox. its so close to done, i hope i am able to get credit for my 41 hours spent on this
ITS FINALLY DONE, see it on https://dooble.gay/SFS . took a long break from programming but we so back
Ships:
This is a full decompile/port of Space Flight simulator. building for windows, and webgl work for sure, it is unknown if linux or other build options work. it was really hard to learn how to decompile and port unity games....
|
1793440393.6349802
|
1793526793.6349802
|
|
10045
|
My first slack bot! by @julian_arenfors | Stardanc My first slack bot! by @julian_arenfors | Stardance...
|
julian_arenfors
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @julian_arenfors | S Title: My first slack bot! by @julian_arenfors | Stardance...
|
1792777660.0892966
|
1793382460.0892966
|
|
10046
|
My first slack bot! by @iliya28 | Stardance
|
iliya28
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @iliya28 | Stardance
|
1793199086.9046774
|
1793803886.9046774
|
|
10047
|
Untitled by @oliverchew | Stardance
|
oliverchew
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @oliverchew | Stardance
|
1793401001.8968284
|
1794005801.8968284
|
|
10048
|
Prog B by @Prog_Smiler | Stardance
|
Prog_Smiler
|
1
|
4.16
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-24T12:48:44Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Hi there, i made a chat bot named prog b. works fully on voice commands and can do some cool stuff.", "repo": "https://github.com/Prog-Smiler/Prog-B", "demo": "https://github.com/Prog-Smiler/Prog-B/releases"}]...
|
[{"post_id": 26038, "ts": "202 [{"post_id": 26038, "ts": "2026-07-10T16:50:22Z", "hours": 0.5672, "text": "Fixed some simple bugs. This might be the last devlog for prog b."}, {"post_id": 15403, "ts": "2026-06-25T01:16:02Z", "hours": 0.5972, "text": "Made some changes to progb and now it has a downloadable file through github releases and now it is cross platform."}, {"post_id": 15024, "ts": "2026-06-24T12:28:02Z", "hours": 1.4358, "text": "Made a gui and few small improvements in the code"}, {"post_id": 14551, "ts": "2026-06-23T18:28:48Z", "hours": 0.8242, "text": "So again rewrote the code from scratch. working on prog b’s voice using edge_tts"}, {"post_id": 11004, "ts": "2026-06-18T01:00:30Z", "hours": 0.7781, "text": "So i been working on the voice recognition for the Prog B."}]...
|
Title: Prog B by @Prog_Smiler | Stardance
Devlogs Title: Prog B by @Prog_Smiler | Stardance
Devlogs:
So i been working on the voice recognition for the Prog B.
So again rewrote the code from scratch. working on prog b’s voice using edge_tts
Made a gui and few small improvements in the code
Made some changes to progb and now it has a downloadable file through github releases and now it is cross platform.
Fixed some simple bugs. This might be the last devlog for prog b.
Ships:
Hi there, i made a chat bot named prog b. works fully on voice commands and can do some cool stuff....
|
1793317728.154663
|
1793404128.154663
|
|
10049
|
calender by @ewdsfsfdsdfdfsfdsfds | Stardance
|
ewdsfsfdsdfdfsfdsfds
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: calender by @ewdsfsfdsdfdfsfdsfds | Stardan Title: calender by @ewdsfsfdsdfdfsfdsfds | Stardance...
|
1793339413.8686657
|
1793944213.8686657
|
|
10050
|
My awesome macropad! by @Alebouo | Stardance
|
Alebouo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Alebouo | Stardanc Title: My awesome macropad! by @Alebouo | Stardance...
|
1792752616.4069154
|
1793357416.4069154
|