|
4263
|
Untitled by @float | Stardance
|
float
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @float | Stardance
|
1792554636.4342053
|
1793159436.4342053
|
|
4264
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792882310.4807417
|
1793746310.4807417
|
|
4265
|
My first slack bot! by @Duaasif | Stardance
|
Duaasif
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Duaasif | Stardance
|
1793177435.2302563
|
1793782235.2302563
|
|
4266
|
My first slack bot! by @noxi | Stardance
|
noxi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @noxi | Stardance
|
1792561879.0548892
|
1793166679.0548892
|
|
4267
|
Comms Bridge by @amronos | Stardance
|
amronos
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Comms Bridge by @amronos | Stardance
|
1792939727.1961164
|
1793803727.1961164
|
|
4268
|
Space by @Tc | Stardance
|
Tc
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Space by @Tc | Stardance
|
1793145241.056728
|
1793750041.056728
|
|
4269
|
EagleEye Attendance by @ShahMohsin | Stardance
|
ShahMohsin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: EagleEye Attendance by @ShahMohsin | Starda Title: EagleEye Attendance by @ShahMohsin | Stardance...
|
1792734432.9078987
|
1793339232.9078987
|
|
4270
|
Untitled project by @Ihsan | Stardance
|
Ihsan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Ihsan | Stardance
|
1792738335.1723022
|
1793343135.1723022
|
|
4271
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792889256.9841182
|
1793753256.9841182
|
|
4272
|
Hobby OS in Pure C and bits of Asm by @thejudgefro Hobby OS in Pure C and bits of Asm by @thejudgefromhell | Stardance...
|
thejudgefromhell
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hobby OS in Pure C and bits of Asm by @thej Title: Hobby OS in Pure C and bits of Asm by @thejudgefromhell | Stardance...
|
1792619678.222368
|
1793224478.222368
|
|
4273
|
Quadruped Robot by @Anonymas_Doge | Stardance
|
Anonymas_Doge
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Quadruped Robot by @Anonymas_Doge | Stardan Title: Quadruped Robot by @Anonymas_Doge | Stardance...
|
1792612417.0313509
|
1793217217.0313509
|
|
4276
|
Camera Based Cat Detector by @reetncosine | Starda Camera Based Cat Detector by @reetncosine | Stardance...
|
reetncosine
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Camera Based Cat Detector by @reetncosine | Title: Camera Based Cat Detector by @reetncosine | Stardance...
|
1792633637.578843
|
1793238437.578843
|
|
4277
|
The Tag Writer by @devovo | Stardance
|
devovo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The Tag Writer by @devovo | Stardance
|
1793137794.2450347
|
1793742594.2450347
|
|
4278
|
My awesome macropad! by @Thing6 | Stardance
|
Thing6
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Thing6 | Stardance
|
1792554825.7130044
|
1793159625.7130044
|
|
4280
|
website by @ajmal | Stardance
|
ajmal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: website by @ajmal | Stardance
|
1793177340.5275164
|
1793782140.5275164
|
|
4281
|
Hexo-Launcher by @fedi41 | Stardance
|
fedi41
|
0
|
10.36
|
0
|
[]
|
[{"post_id": 4310, "ts": "2026 [{"post_id": 4310, "ts": "2026-06-07T15:54:59Z", "hours": 2.5561, "text": "Refactoring the pattern pad viewmodel… Added an edit screen."}, {"post_id": 3655, "ts": "2026-06-06T18:06:41Z", "hours": 1.1758, "text": "Added a new tab for the app screen . Also spent too much time refactoring the code."}, {"post_id": 3496, "ts": "2026-06-06T13:43:13Z", "hours": 1.3981, "text": "Added a pattern trail :)"}, {"post_id": 3414, "ts": "2026-06-06T10:27:49Z", "hours": 2.2803, "text": "Working on pattern-pad trails This has taken me toooo long to make, but now I have a canvas behind my pattern-pad! (later I will be rendering all the “pattern trails” on this canvas)"}, {"post_id": 3359, "ts": "2026-06-06T07:42:45Z", "hours": 1.2044, "text": "Added a simple digital clock to the launcher. Next up: add pattern pad trail ui tweaks"}, {"post_id": 2725, "ts": "2026-06-05T13:50:27Z", "hours": 0.5283, "text": "Small design changes for my launcher. Next, I will add a digital clock!"}, {"post_id": 2612, "ts": "2026-06-05T07:21:52Z", "hours": 1.2186, "text": "working on better drag/press detection for my android launcher."}]...
|
Title: Hexo-Launcher by @fedi41 | Stardance
Devlo Title: Hexo-Launcher by @fedi41 | Stardance
Devlogs:
working on better drag/press detection for my android launcher.
Small design changes for my launcher. Next, I will add a digital clock!
Added a simple digital clock to the launcher. Next up: add pattern pad trail ui tweaks
Working on pattern-pad trails This has taken me toooo long to make, but now I have a canvas behind my pattern-pad! (later I will be rendering all the “pattern trails” on this canvas)
Added a pattern trail :)
Added a new tab for the app screen . Also spent too much time refactoring the code.
Refactoring the pattern pad viewmodel… Added an edit screen....
|
1793029756.481288
|
1793634556.481288
|
|
4284
|
My first slack bot! by @Shavin | Stardance
|
Shavin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Shavin | Stardance
|
1792731217.427809
|
1793336017.427809
|
|
4285
|
My awesome macropad! by @Ahmaad | Stardance
|
Ahmaad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Ahmaad | Stardance
|
1792612422.5249074
|
1793217222.5249074
|
|
4286
|
projection mapping by @ayushi_m | Stardance
|
ayushi_m
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: projection mapping by @ayushi_m | Stardance
|
1792727341.2027576
|
1793332141.2027576
|
|
4287
|
wsb tracker by @cookie | Stardance
|
cookie
|
0
|
5.37
|
0
|
[]
|
[{"post_id": 2484, "ts": "2026 [{"post_id": 2484, "ts": "2026-06-05T00:10:48Z", "hours": 1.3375, "text": "spent a while today trying to actually apply and get a reddit api key (harder than i expected)"}, {"post_id": 1623, "ts": "2026-06-03T19:14:13Z", "hours": 4.0328, "text": "started working on learning the api :)"}]...
|
Title: wsb tracker by @cookie | Stardance
Devlogs Title: wsb tracker by @cookie | Stardance
Devlogs:
started working on learning the api :)
spent a while today trying to actually apply and get a reddit api key (harder than i expected)...
|
1792655370.8457673
|
1793260170.8457673
|
|
4288
|
My first slack bot! by @abhinavgowridevi | Stardan My first slack bot! by @abhinavgowridevi | Stardance...
|
abhinavgowridevi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @abhinavgowridevi | Title: My first slack bot! by @abhinavgowridevi | Stardance...
|
1792763265.2897317
|
1793368065.2897317
|
|
4289
|
PGN File Parser by @nikooo | Stardance
|
nikooo
|
0
|
10.85
|
0
|
[]
|
[{"post_id": 2011, "ts": "2026 [{"post_id": 2011, "ts": "2026-06-04T09:12:56Z", "hours": 10.8483, "text": "Finished the lexer + uploaded git repo to github!"}]...
|
Title: PGN File Parser by @nikooo | Stardance
Dev Title: PGN File Parser by @nikooo | Stardance
Devlogs:
Finished the lexer + uploaded git repo to github!...
|
1792615926.2501776
|
1793220726.2501776
|
|
4290
|
My awesome macropad! by @mem601591 | Stardance
|
mem601591
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @mem601591 | Starda Title: My awesome macropad! by @mem601591 | Stardance...
|
1792659016.7628236
|
1793263816.7628236
|
|
4291
|
My awesome macropad! by @samnitr_vep013 | Stardanc My awesome macropad! by @samnitr_vep013 | Stardance...
|
samnitr_vep013
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @samnitr_vep013 | S Title: My awesome macropad! by @samnitr_vep013 | Stardance...
|
1793184467.1993926
|
1793789267.1993926
|
|
4292
|
My awesome macropad! by @thies | Stardance
|
thies
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @thies | Stardance
|
1792687671.2404058
|
1793292471.2404058
|
|
4293
|
My awesome macropad! by @sqnder_ | Stardance
|
sqnder_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sqnder_ | Stardanc Title: My awesome macropad! by @sqnder_ | Stardance...
|
1792612257.2754407
|
1793217057.2754407
|
|
4294
|
Clock App by @DudefromMars | Stardance
|
DudefromMars
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Clock App by @DudefromMars | Stardance
|
1792795929.6632938
|
1793400729.6632938
|
|
4295
|
My awesome macropad! by @zoe | Stardance
|
zoe
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zoe | Stardance
|
1792608657.1733623
|
1793213457.1733623
|
|
4296
|
Transformer Swarm Simulation by @AaritDixit | Star Transformer Swarm Simulation by @AaritDixit | Stardance...
|
AaritDixit
|
0
|
0.54
|
0
|
[]
|
[{"post_id": 1947, "ts": "2026 [{"post_id": 1947, "ts": "2026-06-04T06:08:30Z", "hours": 0.5422, "text": "Today I ran my first “simulation”, determining whether random search or a custom gossip-based system would be ideal for locating survivors. Turns out…if the detection method itself is so generous that drones can just stumble on survivors, it doesn’t matter how optimized your search pattern is; it won’t show significant improvement over searching randomly. Huh, well that won’t be a problem in real-world testing, that much I know."}]...
|
Title: Transformer Swarm Simulation by @AaritDixit Title: Transformer Swarm Simulation by @AaritDixit | Stardance
Devlogs:
Today I ran my first “simulation”, determining whether random search or a custom gossip-based system would be ideal for locating survivors. Turns out…if the detection method itself is so generous that drones can just stumble on survivors, it doesn’t matter how optimized your search pattern is; it won’t show significant improvement over searching randomly. Huh, well that won’t be a problem in real-world testing, that much I know....
|
1792655692.0554771
|
1793260492.0554771
|
|
4297
|
My first slack bot! by @DudefromMars | Stardance
|
DudefromMars
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @DudefromMars | Star Title: My first slack bot! by @DudefromMars | Stardance...
|
1792604983.516222
|
1793209783.516222
|
|
4298
|
Skylite - RC plane by @kkb | Stardance
|
kkb
|
0
|
9.36
|
0
|
[]
|
[{"post_id": 48819, "ts": "202 [{"post_id": 48819, "ts": "2026-08-17T11:10:47Z", "hours": 1.1472, "text": "Skylite - BOM I will be submitting for funding of the parts!!! BOM - Link (let me know via a comment if it doesnt work (it should)) Finished up the Bill of materials and i also just changed the github made it look better e.c.t Things i had to think about today I made sure all the parts fit and worked with each other connectors brands e.c.t. I have fully committed to ELRS (ExpressLRS for the radio) I have considered battery weight vs power and how that will affect the aircraft and also considered the weight of the aircraft and the power produced by the motor."}, {"post_id": 47752, "ts": "2026-08-15T21:48:36Z", "hours": 1.1283, "text": "Devlog! Today i worked on some essential pieces of design for the LiteSky airframe! I have created 1)A battery holder to stop it moving around and affecting weight in flight 2) A wing strut that will go between the pieces of depron foam to give it support and also that Clarck Y airfoil shape 3) A internal bulkhead this strengthens the inside of the cabin for landings and help everything stay connected. Design bits: You will notice how the wing strut and the bulkhead have cutouts in them this is to reduce the weight as much as possible. I had to be careful that i didnt weaken the integrity of the pieces so that they can complete what they are designed for. The battery tray holder was especially designed for reusable cable ties to thread through and under the battery holder. You may have to use 2 ties depending on battery size. But the holder has a specific under channel to allow the tie to sit flush with the plastic and being allowed to be glued down inside the aircraft."}, {"post_id": 47181, "ts": "2026-08-14T21:50:33Z", "hours": 0.6339, "text": "Worked on the place where the components will go and how they will be wired togethor. Things i had to think about: Spacing out components and sitting the heavier ones in the correct location for weight and balance. I had to think about the CG (centre of gravity) this should be at the peak thickness of the wing or in my case 3cm from the leading edge. Also had to think about components getting hot and allowing them enough airflow. And also what fastening system to use for the hatch to access the battery… Magnets… a bit heavy Tape….. a bit weak Ziptie…… impractical A 3d printed locking mechanism!!!"}, {"post_id": 46958, "ts": "2026-08-14T15:14:59Z", "hours": 3.0853, "text": "I need a name for this project comment below Rc plane - Final design!!!! Woah that took a while lol. You can scroll through the images to see it in progress and then the finished model. I have finished itteration 1 of the final design for the Rc plane! The only things i expect to change now to this model is maybe a couple of diameters but apart from that i think all of the major work for the design is done. These are the things i ‘researched’ and conssidered during the design proccess 1 The wing type For a rc plane lift is important aswell as simplicity when making this it is hard to make wing designs that fold and bend this is why i have chossen the ’Clark Y aerofoil design. This design is used on GA (general aviation - small planes like cessna e.c.t) and is also extremely common in other RC planes. 2 I have also considered the DIMMENSIONS for this aircraft The wing is 50cm long and 10cm wide and in person it will be 1.2 cm thick (at the thickest point) The horizontal stabilizer (the mini wing at the back) Is 7.5 cm on each side so 15cm in total The cabin/fuselage is 37.5 cm 75% of the wingspan And out all important target weight is under 250g 3 WING DESIGN It is a high wing design for stability in the air and is normally considered the easiest design to fly. It is 12% of chord which is 1.2cm max thickness at the biggest point The Peak of the thickness will be 3cm behind the leading edge (front of the wing) 4 THE CABIN The cabin is designed to be 4cm along and 5cm height to allow for LiPo batteries recivers and ESC (Speed controller - flight computer) 5 LANDING GEAR The landing gear is in a traditional tail dragger design with a rear wheel The stance of the gear will be at a forward and downward anfle so the wheels sit slightly ahead of the wings leading edge to prevent flipping over also to absorb max impact without breaking As well as the gear i am going to test belly landings (landings with no gear) they have to be preformed on something soft grass for example. But because the plane is so light belly landings should not be an issue."}, {"post_id": 46286, "ts": "2026-08-13T12:35:51Z", "hours": 1.4839, "text": "Improving git hub for rc plane adding component diagrams e.c.t Sorry i havent posted in a while, any suggestions pls leave a comment i will try to post more frequently now!"}, {"post_id": 4458, "ts": "2026-06-07T19:41:35Z", "hours": 0.5786, "text": "Rc Servo Holder"}, {"post_id": 3383, "ts": "2026-06-06T08:51:21Z", "hours": 0.7203, "text": "Servo System For parachute"}, {"post_id": 2872, "ts": "2026-06-05T19:09:39Z", "hours": 0.585, "text": "Control horn for control surfaces and quick mockup of vague idea of what plane will look like.👍"}]...
|
Title: Skylite - RC plane by @kkb | Stardance
Dev Title: Skylite - RC plane by @kkb | Stardance
Devlogs:
Control horn for control surfaces and quick mockup of vague idea of what plane will look like.👍
Servo System For parachute
Rc Servo Holder
Improving git hub for rc plane adding component diagrams e.c.t Sorry i havent posted in a while, any suggestions pls leave a comment i will try to post more frequently now!
I need a name for this project comment below Rc plane - Final design!!!! Woah that took a while lol. You can scroll through the images to see it in progress and then the finished model. I have finished itteration 1 of the final design for the Rc plane! The only things i expect to change now to this model is maybe a couple of diameters but apart from that i think all of the major work for the design is done. These are the things i ‘researched’ and conssidered during the design proccess 1 The wing type For a rc plane lift is important aswell as simplicity when making this it is hard to make wing designs that fold and bend this is why i have chossen the ’Clark Y aerofoil design. This design is used on GA (general aviation - small planes like cessna e.c.t) and is also extremely common in other RC planes. 2 I have also considered the DIMMENSIONS for this aircraft The wing is 50cm long and 10cm wide and in person it will be 1.2 cm thick (at the thickest point) The horizontal stabilizer (the mini wing at the back) Is 7.5 cm on each side so 15cm in total The cabin/fuselage is 37.5 cm 75% of the wingspan And out all important target weight is under 250g 3 WING DESIGN It is a high wing design for stability in the air and is normally considered the easiest design to fly. It is 12% of chord which is 1.2cm max thickness at the biggest point The Peak of the thickness will be 3cm behind the leading edge (front of the wing) 4 THE CABIN The cabin is designed to be 4cm along and 5cm height to allow for LiPo batteries recivers and ESC (Speed controller - flight computer) 5 LANDING GEAR The landing gear is in a traditional tail dragger design with a rear wheel The stance of the gear will be at a forward and downward anfle so the wheels sit slightly ahead of the wings leading edge to prevent flipping over also to absorb max impact without breaking As well as the gear i am going to test belly landings (landings with no gear) they have to be preformed on something soft grass for example. But because the plane is so light belly landings should not be an issue.
Worked on the place where the components will go and how they will be wired togethor. Things i had to think about: Spacing out components and sitting the heavier ones in the correct location for weight and balance. I had to think about the CG (centre of gravity) this should be at the peak thickness of the wing or in my case 3cm from the leading edge. Also had to think about components getting hot and allowing them enough airflow. And also what fastening system to use for the hatch to access the battery… Magnets… a bit heavy Tape….. a bit weak Ziptie…… impractical A 3d printed locking mechanism!!!
Devlog! Today i worked on some essential pieces of design for the LiteSky airframe! I have created 1)A battery holder to stop it moving around and affecting weight in flight 2) A wing strut that will go between the pieces of depron foam to give it support and also that Clarck Y airfoil shape 3) A internal bulkhead this strengthens the inside of the cabin for landings and help everything stay connected. Design bits: You will notice how the wing strut and the bulkhead have cutouts in them this is to reduce the weight as much as possible. I had to be careful that i didnt weaken the integrity of the pieces so that they can complete what they are designed for. The battery tray holder was especially designed for reusable cable ties to thread through and under the battery holder. You may have to use 2 ties depending on battery size. But the holder has a specific under channel to allow the tie to sit flush with the plastic and being allowed to be glued down inside the aircraft.
Skylite - BOM I will be submitting for funding of the parts!!! BOM - Link (let me know via a comment if it doesnt work (it should)) Finished up the Bill of materials and i also just changed the github made it look better e.c.t Things i had to think about today I made sure all the parts fit and worked with each other connectors brands e.c.t. I have fully committed to ELRS (ExpressLRS for the radio) I have considered battery weight vs power and how that will affect the aircraft and also considered the weight of the aircraft and the power produced by the motor....
|
1793152505.145045
|
1793757305.145045
|
|
4299
|
My awesome macropad! by @Dorapakoda | Stardance
|
Dorapakoda
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Dorapakoda | Stard Title: My awesome macropad! by @Dorapakoda | Stardance...
|
1792533087.960158
|
1793137887.960158
|
|
4300
|
My first slack bot! by @tomer_shamiaben | Stardanc My first slack bot! by @tomer_shamiaben | Stardance...
|
tomer_shamiaben
|
0
|
0.27
|
0
|
[]
|
[{"post_id": 684, "ts": "2026- [{"post_id": 684, "ts": "2026-06-02T07:37:59Z", "hours": 0.2672, "text": "code for the slack bot that once a day use a meme api generator to send memes if you type /meme"}]...
|
Title: My first slack bot! by @tomer_shamiaben | S Title: My first slack bot! by @tomer_shamiaben | Stardance
Devlogs:
code for the slack bot that once a day use a meme api generator to send memes if you type /meme...
|
1793149012.9413235
|
1793753812.9413235
|
|
4301
|
My first slack bot! by @Bella | Stardance
|
Bella
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Bella | Stardance
|
1792569110.9578233
|
1793173910.9578233
|
|
4302
|
My first slack bot! by @k0hu | Stardance
|
k0hu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @k0hu | Stardance
|
1792673549.9635546
|
1793278349.9635546
|
|
4303
|
My first slack bot! by @satvikhardat | Stardance
|
satvikhardat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @satvikhardat | Star Title: My first slack bot! by @satvikhardat | Stardance...
|
1792914718.7674246
|
1793778718.7674246
|
|
4304
|
Casper by @ATPigxter | Stardance
|
ATPigxter
|
0
|
7.13
|
0
|
[]
|
[{"post_id": 12220, "ts": "202 [{"post_id": 12220, "ts": "2026-06-19T22:55:22Z", "hours": 2.2169, "text": "Dev Blog 6 Since the last dev blog I have “finished” routing all the traces for the PCB for my auto-positioning telescope. All the traces are in, but I need to go back through and double check for any errors with track width. Now the work on the PCB is like 90% done."}, {"post_id": 10843, "ts": "2026-06-17T19:47:44Z", "hours": 2.7406, "text": "Dev Blog 5 Began layout on the PCB. I started out by laying components for each section individually and then moving them all together. I’m pretty happy with the final result, but after tracing is done and I tripple check everthing, I’m sure some stuff will have to be moved."}, {"post_id": 7242, "ts": "2026-06-12T02:33:46Z", "hours": 1.3528, "text": "Dev Blog 4 Today I spent an hour and tweny minutes going over and checking my schematic for the PCB I am making which has a microcontroller, motor drivers and more. I checked over the schematic in a few ways, I put the schematic into claude and asked it for errors, I also manually looked through datasheets of the parts, and I researched more into the parts I was using. Here was the big things I changed. To get code uploaded to the microcontroller I was previously using a chip to convert a USB signal into UART, which the microcontroller can read. The UART line for communication I was using was also shared by the raspberry pi, which complicated the design. To fix it I took out the USB and the USB to UART chip and decided to flash code to the microcontroller through the Pi. This simplified the PCB a lot. I found out that the 5V to 3V3 chip I was using is kind of outdated and lacked modern features. So I swapped it to a better one and got that wired up in the schematic. The rest of the fixes were all minor changed to other components."}, {"post_id": 2504, "ts": "2026-06-05T01:07:12Z", "hours": 0.3, "text": "Dev Blog #3 Today I spent about 2-3 hours adding 3D models and fixing footprints for the PCB control board for Casper the auto positioning telescope. The picture attached is off all the parts on the board, but nothing is in the right spot yet. At first I got into the flow using digikey’s database as well as Mouser Electronic’s website to find 3D models and footprints. I figured out how to upload the footprints/models to KiCad and got most of them all in, the plan I had in the previous dev blog worked and adding the 3D models helped with fixing a few of the footprints. When I came back to working on it later I noticed that a bunch of my work had vanished. After a bit of investigating I found that when a 3D model or footprint is uploaded to KiCad it locates it through the path of where the file is stored. When I had tried to organize the mess of files on my computer after downloading all the footprints/models, the paths changed so KiCad could not find them. This meant I had to go back and redo a lot of work, this time making sure the files were stored in a more permanent place. After that everything seems fine. Next step will be to layout and make traces for the actual PCB."}, {"post_id": 1730, "ts": "2026-06-03T22:09:30Z", "hours": 0.2525, "text": "Dev Blog #2 I spend about 2 hours working on the next step in making my control board PCB. I spend the time adding footprints of all the components into KiCad. This took a lot of time because it was a lot of searching through datasheets, digikey, and the KiCad footprint editor making sure all the components are correct. The hardest part was trying to make sure the exact parts would fit the footprint, but I figured out a better way of going about it would be to use the 3D models provided on the part page of each component to check if the footprints are correct because I can visualy see if they will fit. The next step for the PCB will be adding the 3D models, or at least confirming the ones in KiCad already are the right ones. This step is not only important to confirm the footprints are correct but also for later when I design the enclosure for mounting the board to the telescope."}, {"post_id": 1041, "ts": "2026-06-02T20:46:34Z", "hours": 0.2683, "text": "Hi, the project I’m working on right now is Casper. Casper is a modified 6’’ dobsonian telescope that can automatically point itself at a planet or other celestial body. Besides a lot of research what I have done so far is make the schematic for the control board PCB. The control board includes a STM32 microcontroller, stepper motor drivers, Raspberry Pi Zero, and much more. I made it all in KiCad so the time does not log but I spent roughly 7-8 hours on making it. How I went about making it this is I started out selecting the integrated circuits (ICs) I would use for each part of the board. I need a microcontroller, stepper motor drivers, buck converter, and a LDO. Once I knew those parts I looked at the datasheet to find the standard application circuit and followed that pretty closely, with some modifications. Next steps are to start laying out the components for the actual board and make traces to connect them all."}]...
|
Title: Casper by @ATPigxter | Stardance
Devlogs:
Title: Casper by @ATPigxter | Stardance
Devlogs:
Hi, the project I’m working on right now is Casper. Casper is a modified 6’’ dobsonian telescope that can automatically point itself at a planet or other celestial body. Besides a lot of research what I have done so far is make the schematic for the control board PCB. The control board includes a STM32 microcontroller, stepper motor drivers, Raspberry Pi Zero, and much more. I made it all in KiCad so the time does not log but I spent roughly 7-8 hours on making it. How I went about making it this is I started out selecting the integrated circuits (ICs) I would use for each part of the board. I need a microcontroller, stepper motor drivers, buck converter, and a LDO. Once I knew those parts I looked at the datasheet to find the standard application circuit and followed that pretty closely, with some modifications. Next steps are to start laying out the components for the actual board and make traces to connect them all.
Dev Blog #2 I spend about 2 hours working on the next step in making my control board PCB. I spend the time adding footprints of all the components into KiCad. This took a lot of time because it was a lot of searching through datasheets, digikey, and the KiCad footprint editor making sure all the components are correct. The hardest part was trying to make sure the exact parts would fit the footprint, but I figured out a better way of going about it would be to use the 3D models provided on the part page of each component to check if the footprints are correct because I can visualy see if they will fit. The next step for the PCB will be adding the 3D models, or at least confirming the ones in KiCad already are the right ones. This step is not only important to confirm the footprints are correct but also for later when I design the enclosure for mounting the board to the telescope.
Dev Blog #3 Today I spent about 2-3 hours adding 3D models and fixing footprints for the PCB control board for Casper the auto positioning telescope. The picture attached is off all the parts on the board, but nothing is in the right spot yet. At first I got into the flow using digikey’s database as well as Mouser Electronic’s website to find 3D models and footprints. I figured out how to upload the footprints/models to KiCad and got most of them all in, the plan I had in the previous dev blog worked and adding the 3D models helped with fixing a few of the footprints. When I came back to working on it later I noticed that a bunch of my work had vanished. After a bit of investigating I found that when a 3D model or footprint is uploaded to KiCad it locates it through the path of where the file is stored. When I had tried to organize the mess of files on my computer after downloading all the footprints/models, the paths changed so KiCad could not find them. This meant I had to go back and redo a lot of work, this time making sure the files were stored in a more permanent place. After that everything seems fine. Next step will be to layout and make traces for the actual PCB.
Dev Blog 4 Today I spent an hour and tweny minutes going over and checking my schematic for the PCB I am making which has a microcontroller, motor drivers and more. I checked over the schematic in a few ways, I put the schematic into claude and asked it for errors, I also manually looked through datasheets of the parts, and I researched more into the parts I was using. Here was the big things I changed. To get code uploaded to the microcontroller I was previously using a chip to convert a USB signal into UART, which the microcontroller can read. The UART line for communication I was using was also shared by the raspberry pi, which complicated the design. To fix it I took out the USB and the USB to UART chip and decided to flash code to the microcontroller through the Pi. This simplified the PCB a lot. I found out that the 5V to 3V3 chip I was using is kind of outdated and lacked modern features. So I swapped it to a better one and got that wired up in the schematic. The rest of the fixes were all minor changed to other components.
Dev Blog 5 Began layout on the PCB. I started out by laying components for each section individually and then moving them all together. I’m pretty happy with the final result, but after tracing is done and I tripple check everthing, I’m sure some stuff will have to be moved.
Dev Blog 6 Since the last dev blog I have “finished” routing all the traces for the PCB for my auto-positioning telescope. All the traces are in, but I need to go back through and double check for any errors with track width. Now the work on the PCB is like 90% done....
|
1792594084.3606422
|
1793198884.3606422
|
|
4305
|
My awesome macropad! by @ramroopp26 | Stardance
|
ramroopp26
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ramroopp26 | Stard Title: My awesome macropad! by @ramroopp26 | Stardance...
|
1792536604.6011076
|
1793141404.6011076
|
|
4306
|
Debaterandgamer by @Automat | Stardance
|
Automat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Debaterandgamer by @Automat | Stardance
|
1793177288.9258225
|
1793782088.9258225
|
|
4307
|
My awesome macropad! by @k0hu | Stardance
|
k0hu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @k0hu | Stardance
|
1792601375.8895326
|
1793206175.8895326
|
|
4308
|
Water Demand Forecasting by @itznolex | Stardance
|
itznolex
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Water Demand Forecasting by @itznolex | Sta Title: Water Demand Forecasting by @itznolex | Stardance...
|
1792651930.2579432
|
1793256730.2579432
|
|
4310
|
My awesome macropad! by @davidondrej | Stardance
|
davidondrej
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @davidondrej | Star Title: My awesome macropad! by @davidondrej | Stardance...
|
1792705764.6560824
|
1793310564.6560824
|
|
4311
|
My awesome macropad! by @ro-bin | Stardance
|
ro-bin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ro-bin | Stardance
|
1792554766.8545551
|
1793159566.8545551
|
|
4312
|
website by @jacob6855 | Stardance
|
jacob6855
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: website by @jacob6855 | Stardance
|
1792533229.5989113
|
1793138029.5989113
|
|
4313
|
Silo IT Terminal by @yassen | Stardance
|
yassen
|
0
|
1.02
|
0
|
[]
|
[{"post_id": 1018, "ts": "2026 [{"post_id": 1018, "ts": "2026-06-02T20:12:59Z", "hours": 0.4947, "text": "Deploying the Silo IT Terminal 24/7 What I built today: I completely overhauled my Slack bot into The Silo IT Terminal (v1.0)—an immersive, dystopian mainframe inspired by the sci-fi series Silo. After writing a baseline script, I ran into some classic Git sync roadblocks and local drive space issues, but I pushed through, cleaned up my repository, and successfully deployed it to the cloud! ✨ Core Features Implemented: status: Displays a sub-level mechanical diagnostics readout (steam levels, fan efficiency) wrapped in clean markdown. outside: A text monitor that detects forbidden phrases. If a citizen mentions the exterior landscape, it fires back a stylized Slack Block Kit UI card flagging a Pact Violation. scavenge: Built a Role-Based Access Control (RBAC) layer. It checks the user’s unique Slack Member ID. If anyone else searches for artifacts, access is denied. If I use it, it bypasses the system to retrieve a randomized, forbidden pre-historic relic."}, {"post_id": 914, "ts": "2026-06-02T17:31:13Z", "hours": 0.525, "text": "Hey everyone! Just built my very first Slack bot, and unlike the rest of us, this one isn’t slacking off—it’s running 24/7 directly out of my Windsurf editor! 💻⚡️ I wanted to do something cooler than just a basic “Hello World” bot, so I’m turning it into an interactive system inspired by the Silo TV series. Right now, it mimics an ancient underground IT terminal embedded in the deep down of the Silo. Upcoming features: 📋 System Diagnostics: Type @Bot status to get live readouts of the 144 levels, steam pressure, and sensor status. ⚠️ Judicial Overrides: Try asking about the “Outside” and the bot will flag you for a Level 1 infraction against the Pact. 🛠️ A role-based permission system recognizing the Head of IT vs. standard citizens. 🧹 A moderation system where you can sentence rule-breakers to “Go out for a cleaning.” 📦 A “Relic Archive” database where users can scavenge for forbidden artifacts from the before-times. “In the event of a failed terminal, please contact the Head of IT. Do not look through the lens.” 👁️📟"}]...
|
Title: Silo IT Terminal by @yassen | Stardance
De Title: Silo IT Terminal by @yassen | Stardance
Devlogs:
Hey everyone! Just built my very first Slack bot, and unlike the rest of us, this one isn’t slacking off—it’s running 24/7 directly out of my Windsurf editor! 💻⚡️ I wanted to do something cooler than just a basic “Hello World” bot, so I’m turning it into an interactive system inspired by the Silo TV series. Right now, it mimics an ancient underground IT terminal embedded in the deep down of the Silo. Upcoming features: 📋 System Diagnostics: Type @Bot status to get live readouts of the 144 levels, steam pressure, and sensor status. ⚠️ Judicial Overrides: Try asking about the “Outside” and the bot will flag you for a Level 1 infraction against the Pact. 🛠️ A role-based permission system recognizing the Head of IT vs. standard citizens. 🧹 A moderation system where you can sentence rule-breakers to “Go out for a cleaning.” 📦 A “Relic Archive” database where users can scavenge for forbidden artifacts from the before-times. “In the event of a failed terminal, please contact the Head of IT. Do not look through the lens.” 👁️📟
Deploying the Silo IT Terminal 24/7 What I built today: I completely overhauled my Slack bot into The Silo IT Terminal (v1.0)—an immersive, dystopian mainframe inspired by the sci-fi series Silo. After writing a baseline script, I ran into some classic Git sync roadblocks and local drive space issues, but I pushed through, cleaned up my repository, and successfully deployed it to the cloud! ✨ Core Features Implemented: status: Displays a sub-level mechanical diagnostics readout (steam levels, fan efficiency) wrapped in clean markdown. outside: A text monitor that detects forbidden phrases. If a citizen mentions the exterior landscape, it fires back a stylized Slack Block Kit UI card flagging a Pact Violation. scavenge: Built a Role-Based Access Control (RBAC) layer. It checks the user’s unique Slack Member ID. If anyone else searches for artifacts, access is denied. If I use it, it bypasses the system to retrieve a randomized, forbidden pre-historic relic....
|
1792612115.6963148
|
1793216915.6963148
|
|
4314
|
A game by @M126014M | Stardance
|
M126014M
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A game by @M126014M | Stardance
|
1792673257.4981573
|
1793278057.4981573
|
|
4315
|
My first slack bot! by @Vicky_dee | Stardance
|
Vicky_dee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Vicky_dee | Stardan Title: My first slack bot! by @Vicky_dee | Stardance...
|
1793159580.6230462
|
1793764380.6230462
|
|
4316
|
My first slack bot! by @david136 | Stardance
|
david136
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @david136 | Stardanc Title: My first slack bot! by @david136 | Stardance...
|
1792803277.7859633
|
1793408077.7859633
|
|
4317
|
My awesome macropad! by @roshaniraj | Stardance
|
roshaniraj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @roshaniraj | Stard Title: My awesome macropad! by @roshaniraj | Stardance...
|
1792738382.3350034
|
1793343182.3350034
|
|
4318
|
HeliStudy by @helipop | Stardance
|
helipop
|
0
|
19.27
|
0
|
[]
|
[{"post_id": 4920, "ts": "2026 [{"post_id": 4920, "ts": "2026-06-08T14:53:14Z", "hours": 3.9089, "text": "I’ve added this view for users to select what they wanna view. I might also be listing the tags the user has created. I don’t know why it took me this long, but I really did take forever to debug weird things… I had to proofread my code like so many times due to the funny task type conflicts."}, {"post_id": 4264, "ts": "2026-06-07T14:53:27Z", "hours": 2.5278, "text": "I’ve added a context menu to the tasks :> I took 2.5 hours to get this devlog out bc the wrath of Xcode’s compiler type safety checker hit me in the face and I had to wrestle it for 2 hours, it’s clearly shown on github"}, {"post_id": 4006, "ts": "2026-06-07T04:45:55Z", "hours": 2.5767, "text": "Took me FOREVER to refactor the code so that it uses an observable class to reduce the @State variable spam. But, now the code feels SO MUCH cleaner. Oh I’ve finally added functionality behind the save button in the edit view :> Idk why I just can’t style the Exit button properly tho, gonna be fixing that soon."}, {"post_id": 2734, "ts": "2026-06-05T14:20:29Z", "hours": 1.5717, "text": "I’ve refactored the code and also added an init so that the TaskEditorView will show the details of the task"}, {"post_id": 2172, "ts": "2026-06-04T14:54:51Z", "hours": 2.8964, "text": "Aight. I’ve finally. Added. A UI for the user to edit the task. It’s just the UI though, I still have to complete the backend. This really took longer than expected because I had to wrestle with the Navigation Stack and VStack that I put, then I realised that I could have just put a Group around all my code… Then I had to refactor my code to support my enum bc I wanted to have 3 modes and have type safety (bc who knows what I would do in the future idk)"}, {"post_id": 1313, "ts": "2026-06-03T07:16:31Z", "hours": 2.9244, "text": "BRO WHY DID THIS TAKE SO LONG Ok so I wanted to copy the animation when the shortcut is edited in the iOS shortcuts app but ended up taking forever to debug it. Now, with the animation done, I will work on the TaskCardDetails and make it so that the user will be able to edit the task, and view stuff 😬😬 (Hope it won’t take too long) I’ve also rearranged the order that the Form components will show up ↓"}, {"post_id": 825, "ts": "2026-06-02T14:45:48Z", "hours": 2.3203, "text": "I wanted to get some colours for the tasks, so I spent some time on Coolors to gamble (AHEM) for good colours, and also get a suitable dark mode colour. I also had to do a lot of debugging with the datatypes SwiftData stores and enum protocols 😭."}, {"post_id": 674, "ts": "2026-06-02T07:11:26Z", "hours": 0.54, "text": "I’ve learnt and added a LazyVGrid for my task view so that I can show cards in a manner like the shortcuts app on iOS"}]...
|
Title: HeliStudy by @helipop | Stardance
Devlogs: Title: HeliStudy by @helipop | Stardance
Devlogs:
I’ve learnt and added a LazyVGrid for my task view so that I can show cards in a manner like the shortcuts app on iOS
I wanted to get some colours for the tasks, so I spent some time on Coolors to gamble (AHEM) for good colours, and also get a suitable dark mode colour. I also had to do a lot of debugging with the datatypes SwiftData stores and enum protocols 😭.
BRO WHY DID THIS TAKE SO LONG Ok so I wanted to copy the animation when the shortcut is edited in the iOS shortcuts app but ended up taking forever to debug it. Now, with the animation done, I will work on the TaskCardDetails and make it so that the user will be able to edit the task, and view stuff 😬😬 (Hope it won’t take too long) I’ve also rearranged the order that the Form components will show up ↓
Aight. I’ve finally. Added. A UI for the user to edit the task. It’s just the UI though, I still have to complete the backend. This really took longer than expected because I had to wrestle with the Navigation Stack and VStack that I put, then I realised that I could have just put a Group around all my code… Then I had to refactor my code to support my enum bc I wanted to have 3 modes and have type safety (bc who knows what I would do in the future idk)
I’ve refactored the code and also added an init so that the TaskEditorView will show the details of the task
Took me FOREVER to refactor the code so that it uses an observable class to reduce the @State variable spam. But, now the code feels SO MUCH cleaner. Oh I’ve finally added functionality behind the save button in the edit view :> Idk why I just can’t style the Exit button properly tho, gonna be fixing that soon.
I’ve added a context menu to the tasks :> I took 2.5 hours to get this devlog out bc the wrath of Xcode’s compiler type safety checker hit me in the face and I had to wrestle it for 2 hours, it’s clearly shown on github
I’ve added this view for users to select what they wanna view. I might also be listing the tags the user has created. I don’t know why it took me this long, but I really did take forever to debug weird things… I had to proofread my code like so many times due to the funny task type conflicts....
|
1793163195.835684
|
1793767995.835684
|