|
3901
|
My awesome macropad! by @vixyahsar | Stardance
|
vixyahsar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @vixyahsar | Starda Title: My awesome macropad! by @vixyahsar | Stardance...
|
1792727632.2423892
|
1793332432.2423892
|
|
3902
|
My first slack bot! by @H3CK0R | Stardance
|
H3CK0R
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @H3CK0R | Stardance
|
1792796005.7255263
|
1793400805.7255263
|
|
3903
|
Untitled by @smantrala14 | Stardance
|
smantrala14
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @smantrala14 | Stardance
|
1792590621.2745132
|
1793195421.2745132
|
|
3904
|
My awesome macropad! by @toomuchadoaboutnothing | My awesome macropad! by @toomuchadoaboutnothing | Stardance...
|
toomuchadoaboutnothing
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @toomuchadoaboutnot Title: My awesome macropad! by @toomuchadoaboutnothing | Stardance...
|
1792569134.600191
|
1793173934.600191
|
|
3905
|
Trashy AI by @raviv_pelman | Stardance
|
raviv_pelman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Trashy AI by @raviv_pelman | Stardance
|
1792658883.0483682
|
1793263683.0483682
|
|
3906
|
Untitled by @prisha | Stardance
|
prisha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @prisha | Stardance
|
1792810097.4766462
|
1793414897.4766462
|
|
3907
|
My awesome macropad! by @krem | Stardance
|
krem
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @krem | Stardance
|
1792522515.931496
|
1793127315.931496
|
|
3908
|
My awesome macropad! by @c0mrade | Stardance
|
c0mrade
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @c0mrade | Stardanc Title: My awesome macropad! by @c0mrade | Stardance...
|
1792792099.8015618
|
1793396899.8015618
|
|
3909
|
My awesome macropad! by @alexa | Stardance
|
alexa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @alexa | Stardance
|
1792529649.9490707
|
1793134449.9490707
|
|
3910
|
My awesome macropad! by @mason | Stardance
|
mason
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @mason | Stardance
|
1792709424.7790127
|
1793314224.7790127
|
|
3911
|
My awesome macropad! by @leron_nov | Stardance
|
leron_nov
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @leron_nov | Starda Title: My awesome macropad! by @leron_nov | Stardance...
|
1792651798.914396
|
1793256598.914396
|
|
3912
|
Untitled project by @mina | Stardance
|
mina
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @mina | Stardance
|
1792554583.4541245
|
1793159383.4541245
|
|
3913
|
My first slack bot! by @max_grauel | Stardance
|
max_grauel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @max_grauel | Starda Title: My first slack bot! by @max_grauel | Stardance...
|
1792536585.612825
|
1793141385.612825
|
|
3914
|
My first slack bot! by @Sparrow216 | Stardance
|
Sparrow216
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Sparrow216 | Starda Title: My first slack bot! by @Sparrow216 | Stardance...
|
1792731049.3763742
|
1793335849.3763742
|
|
3915
|
My awesome macropad! by @rykerj | Stardance
|
rykerj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @rykerj | Stardance
|
1792529262.6680696
|
1793134062.6680696
|
|
3916
|
My first slack bot! by @pravin | Stardance
|
pravin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @pravin | Stardance
|
1792619511.4729598
|
1793224311.4729598
|
|
3917
|
Untitled project by @joeroo99 | Stardance
|
joeroo99
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @joeroo99 | Stardance
|
1792770539.532859
|
1793375339.532859
|
|
3918
|
Bookturfs by @SenthilKumar | Stardance
|
SenthilKumar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Bookturfs by @SenthilKumar | Stardance
|
1792684100.9253666
|
1793288900.9253666
|
|
3919
|
My awesome macropad! by @vishnu | Stardance
|
vishnu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @vishnu | Stardance
|
1792806650.4770958
|
1793411450.4770958
|
|
3920
|
Hacky the Hackpad by @Amayas | Stardance
|
Amayas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hacky the Hackpad by @Amayas | Stardance
|
1792695281.1848354
|
1793300081.1848354
|
|
3921
|
My awesome macropad! by @parrotos95 | Stardance
|
parrotos95
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @parrotos95 | Stard Title: My awesome macropad! by @parrotos95 | Stardance...
|
1792497068.8726926
|
1793101868.8726926
|
|
3922
|
cosnap by @youngzheimer | Stardance
|
youngzheimer
|
0
|
9.55
|
0
|
[]
|
[{"post_id": 9749, "ts": "2026 [{"post_id": 9749, "ts": "2026-06-16T05:26:32Z", "hours": 4.7889, "text": "many things login&signup page design fixed session logic a bit many thing with event"}, {"post_id": 4755, "ts": "2026-06-08T06:29:59Z", "hours": 2.2228, "text": "made signup & login & session w/ JWT and RTR"}, {"post_id": 821, "ts": "2026-06-02T14:36:52Z", "hours": 1.7575, "text": "making form from json schema"}, {"post_id": 594, "ts": "2026-06-02T02:45:58Z", "hours": 0.7789, "text": "example DB values for testing"}]...
|
Title: cosnap by @youngzheimer | Stardance
Devlog Title: cosnap by @youngzheimer | Stardance
Devlogs:
example DB values for testing
making form from json schema
made signup & login & session w/ JWT and RTR
many things login&signup page design fixed session logic a bit many thing with event...
|
1792803281.214417
|
1793408081.214417
|
|
3923
|
My first slack bot! by @Noelle | Stardance
|
Noelle
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Noelle | Stardance
|
1792533075.864792
|
1793137875.864792
|
|
3924
|
My first slack bot! by @dxrkinfuser44 | Stardance
|
dxrkinfuser44
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @dxrkinfuser44 | Sta Title: My first slack bot! by @dxrkinfuser44 | Stardance...
|
1792698550.2468429
|
1793303350.2468429
|
|
3925
|
AI Powered Criminal Activity Detection Through Sen AI Powered Criminal Activity Detection Through Sensor-less Sensing by @vvishal0507 | Stardance...
|
vvishal0507
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI Powered Criminal Activity Detection Thro Title: AI Powered Criminal Activity Detection Through Sensor-less Sensing by @vvishal0507 | Stardance...
|
1792774208.5548244
|
1793379008.5548244
|
|
3926
|
Butterfly To Do List by @lenny121957869 | Stardanc Butterfly To Do List by @lenny121957869 | Stardance...
|
lenny121957869
|
0
|
0.36
|
0
|
[]
|
[{"post_id": 3794, "ts": "2026 [{"post_id": 3794, "ts": "2026-06-06T20:57:51Z", "hours": 0.365, "text": "I am making a to-do list that, as you complete your tasks, goes from egg to larvae to pupa to butterfly! You must start with 4 or more tasks for the day, so it can cycle through all the stages. As for right now, I’ve barely created the files and linked my js to my html. But, I did learn how to properly commit changes, so that’s a plus! More updates coming soon!"}]...
|
Title: Butterfly To Do List by @lenny121957869 | S Title: Butterfly To Do List by @lenny121957869 | Stardance
Devlogs:
I am making a to-do list that, as you complete your tasks, goes from egg to larvae to pupa to butterfly! You must start with 4 or more tasks for the day, so it can cycle through all the stages. As for right now, I’ve barely created the files and linked my js to my html. But, I did learn how to properly commit changes, so that’s a plus! More updates coming soon!...
|
1792803013.5567687
|
1793407813.5567687
|
|
3927
|
Go-Go Gadget Arm by @Jaydenjiang | Stardance
|
Jaydenjiang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Go-Go Gadget Arm by @Jaydenjiang | Stardanc Title: Go-Go Gadget Arm by @Jaydenjiang | Stardance...
|
1792723661.0383153
|
1793328461.0383153
|
|
3928
|
hydra by @hamstermind | Stardance
|
hamstermind
|
0
|
2.03
|
0
|
[]
|
[{"post_id": 18101, "ts": "202 [{"post_id": 18101, "ts": "2026-06-29T03:14:22Z", "hours": 1.0833, "text": "im trying to use any many ender 3 parts as possible in this build so im using all the plates on the x gantry for the belted z axis it took a lot of work with the coping saw and bending parts off but they are ready!"}, {"post_id": 7226, "ts": "2026-06-12T01:58:38Z", "hours": 0.5283, "text": "Modeled the first part! The, umm, feet"}, {"post_id": 6640, "ts": "2026-06-11T04:00:35Z", "hours": 0.4181, "text": "Hydra devlog 1 Currently drawing the design of where I want everything to go. General ideas triple belted z axis mgn9 rails for x and y corexy gantry for high speeds wooden, markerboard enclosure due to ease of lasercutting and low price I plan on taking an unusual approach by putting the x and y axis motors in the front along the with the belt tensioners will be printed mostly in carbon fiber petg electronics will be mounted and arrraged neatly in bottom compartment what next I want to start assembling a basic frame from the old aluminum extrusions to model from and test with, using pla for initial prints I hope at the end of this project I can build a printer that is more reliable than its predecessors"}]...
|
Title: hydra by @hamstermind | Stardance
Devlogs: Title: hydra by @hamstermind | Stardance
Devlogs:
Hydra devlog 1 Currently drawing the design of where I want everything to go. General ideas triple belted z axis mgn9 rails for x and y corexy gantry for high speeds wooden, markerboard enclosure due to ease of lasercutting and low price I plan on taking an unusual approach by putting the x and y axis motors in the front along the with the belt tensioners will be printed mostly in carbon fiber petg electronics will be mounted and arrraged neatly in bottom compartment what next I want to start assembling a basic frame from the old aluminum extrusions to model from and test with, using pla for initial prints I hope at the end of this project I can build a printer that is more reliable than its predecessors
Modeled the first part! The, umm, feet
im trying to use any many ender 3 parts as possible in this build so im using all the plates on the x gantry for the belted z axis it took a lot of work with the coping saw and bending parts off but they are ready!...
|
1792504339.5519788
|
1793109139.5519788
|
|
3929
|
My first slack bot! by @saiful | Stardance
|
saiful
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @saiful | Stardance
|
1792500519.047387
|
1793105319.047387
|
|
3930
|
LC (Low Cost) Star Tracker by @Advay | Stardance
|
Advay
|
0
|
3.81
|
0
|
[]
|
[{"post_id": 46017, "ts": "202 [{"post_id": 46017, "ts": "2026-08-12T21:57:49Z", "hours": 1.2217, "text": "DEVLOG 003 I worked a lot on the equatorial wedge, researching it on YouTube and the internet, and I made a pretty solid base design. I think it will be a pretty stable mount. I have decided not to implement the fine adjustment screws. After seeing a YouTube video, I can simply use NINA star-guided polar alignment, since it is not supposed to be such a portable mount. I also decided that I will 3d print a curved slot holder in the back, that will screw onto the base eq wedge, and have a slot shaped to match the radius of the wedge’s circle, so I can support the backside evenly, when the telescope is mounted. I also organized the Onshape files, and started a notebook. Initially for the eq wedge, I wanted it to just be one single bar in the middle, as it would be simpler. I decided to provide adequate support for the back side of the RA Axis that is sticking out, I would need a curved profile section, like shown in the OG Star Tracker V2. This would provide good stability even for heavier payloads. Next session I will work much more on the details of the smaller parts, and also order the pulleys and rods and things, to begin making it and getting rough estimates in real life."}, {"post_id": 41049, "ts": "2026-08-05T00:19:45Z", "hours": 1.5583, "text": "DEVLOG 002 Worked on the initial design for the declination axis for the star tracker. My goal for this section of the tracker is to be much more compact and lightweight, since the RA axis will rotate it, and we want to minimize the load on the RA axis to allow more of its strength to be used by the telescope. I made a very simple outer frame, with the posts in the center rather than a traditional simple box design, to make room for the large 80-tooth pulleys. I think this design is quite innovative, as it really compacts everything together, with the first two stages on one simple axis, and the third and final 80-tooth pulley is sitting on the other side of the frame, where the telescope itself will be attached to. I also did the major task of deciding which bearing to use, and I settled on the simple, standard F695ZZ Flanged Ball Bearings. They have a 13mm OD, which would allow me to drill the proper-sized hole into the aluminum extrusion and press fit it, and then either use specialized Loctite glue or some kind of 3d printed fasteners to hold the bearings in place. This is also a very cost-effective solution as 20 bearings only cost $15 on Amazon with fast shipping, which will help stay in the $100 budget. I also assembled the complete assembly with both axes attached together, to which I will attach the EQ wedge. I have also decided that this EQ wedge wil have built in screw adjustment system, so I can get super super accurate polar alignment using NINA’s or other software’s 3 point polar alignment. Im still not totally sure if I can add a polar laser or scope to take this tracker out away from home, because that would be very helpful for travel. The next major thing to do for the next session will be to get the proper belt length estimates and properly lengthen the aluminum extrusions to get the correctly sized RA and DEC axes. I will also do lots of math calculations about possibly increasing to 8mm shafts, if possible, if the extra thickness will really help or not, and if the extra cost is worth it. I will also work on the whole EQ wedge and make the screw adjustment, with the proper mounting solution to my current tripod."}, {"post_id": 24463, "ts": "2026-07-08T01:17:27Z", "hours": 1.0333, "text": "DEVLOG 001 Worked on initial CAD for the Right Ascension Axis. I created a simple aluminum extrusion frame to get a super simple base design created. The aluminum extrusions are currently 10cm long, and I made a simple estimate for the length of the steel rods to be at 8cm for fitting the pulley spacings correctly. One major achievement, was I found an incredibly good place to put the stepper motor. I placed it inbetween the four 80 tooth gear, perfectly inbetween without contacting any surface. This also allows me to slide it back and forth, to adjust tension for that specific belt loop. For the other loops, I will try to come up with a simple tensioning method, as well as bearings for the next work session. Thank you."}]...
|
Title: LC (Low Cost) Star Tracker by @Advay | Star Title: LC (Low Cost) Star Tracker by @Advay | Stardance
Devlogs:
DEVLOG 001 Worked on initial CAD for the Right Ascension Axis. I created a simple aluminum extrusion frame to get a super simple base design created. The aluminum extrusions are currently 10cm long, and I made a simple estimate for the length of the steel rods to be at 8cm for fitting the pulley spacings correctly. One major achievement, was I found an incredibly good place to put the stepper motor. I placed it inbetween the four 80 tooth gear, perfectly inbetween without contacting any surface. This also allows me to slide it back and forth, to adjust tension for that specific belt loop. For the other loops, I will try to come up with a simple tensioning method, as well as bearings for the next work session. Thank you.
DEVLOG 002 Worked on the initial design for the declination axis for the star tracker. My goal for this section of the tracker is to be much more compact and lightweight, since the RA axis will rotate it, and we want to minimize the load on the RA axis to allow more of its strength to be used by the telescope. I made a very simple outer frame, with the posts in the center rather than a traditional simple box design, to make room for the large 80-tooth pulleys. I think this design is quite innovative, as it really compacts everything together, with the first two stages on one simple axis, and the third and final 80-tooth pulley is sitting on the other side of the frame, where the telescope itself will be attached to. I also did the major task of deciding which bearing to use, and I settled on the simple, standard F695ZZ Flanged Ball Bearings. They have a 13mm OD, which would allow me to drill the proper-sized hole into the aluminum extrusion and press fit it, and then either use specialized Loctite glue or some kind of 3d printed fasteners to hold the bearings in place. This is also a very cost-effective solution as 20 bearings only cost $15 on Amazon with fast shipping, which will help stay in the $100 budget. I also assembled the complete assembly with both axes attached together, to which I will attach the EQ wedge. I have also decided that this EQ wedge wil have built in screw adjustment system, so I can get super super accurate polar alignment using NINA’s or other software’s 3 point polar alignment. Im still not totally sure if I can add a polar laser or scope to take this tracker out away from home, because that would be very helpful for travel. The next major thing to do for the next session will be to get the proper belt length estimates and properly lengthen the aluminum extrusions to get the correctly sized RA and DEC axes. I will also do lots of math calculations about possibly increasing to 8mm shafts, if possible, if the extra thickness will really help or not, and if the extra cost is worth it. I will also work on the whole EQ wedge and make the screw adjustment, with the proper mounting solution to my current tripod.
DEVLOG 003 I worked a lot on the equatorial wedge, researching it on YouTube and the internet, and I made a pretty solid base design. I think it will be a pretty stable mount. I have decided not to implement the fine adjustment screws. After seeing a YouTube video, I can simply use NINA star-guided polar alignment, since it is not supposed to be such a portable mount. I also decided that I will 3d print a curved slot holder in the back, that will screw onto the base eq wedge, and have a slot shaped to match the radius of the wedge’s circle, so I can support the backside evenly, when the telescope is mounted. I also organized the Onshape files, and started a notebook. Initially for the eq wedge, I wanted it to just be one single bar in the middle, as it would be simpler. I decided to provide adequate support for the back side of the RA Axis that is sticking out, I would need a curved profile section, like shown in the OG Star Tracker V2. This would provide good stability even for heavier payloads. Next session I will work much more on the details of the smaller parts, and also order the pulleys and rods and things, to begin making it and getting rough estimates in real life....
|
1792543750.5637982
|
1793148550.5637982
|
|
3931
|
ARAS by @Viraj | Stardance
|
Viraj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ARAS by @Viraj | Stardance
|
1792507941.7513359
|
1793112741.7513359
|
|
3932
|
Drone Frame by @gabewhigham | Stardance
|
gabewhigham
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Drone Frame by @gabewhigham | Stardance
|
1792770540.3754883
|
1793375340.3754883
|
|
3933
|
My first slack bot! by @fio_c247 | Stardance
|
fio_c247
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @fio_c247 | Stardanc Title: My first slack bot! by @fio_c247 | Stardance...
|
1792482490.093167
|
1793087290.093167
|
|
3934
|
My first slack bot! by @m4n_1 | Stardance
|
m4n_1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @m4n_1 | Stardance
|
1792727635.6728542
|
1793332435.6728542
|
|
3935
|
Untitled project by @ner | Stardance
|
ner
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @ner | Stardance
|
1792608525.8786373
|
1793213325.8786373
|
|
3936
|
My awesome macropad! by @Luz | Stardance
|
Luz
|
0
|
1.89
|
0
|
[]
|
[{"post_id": 9011, "ts": "2026 [{"post_id": 9011, "ts": "2026-06-15T01:03:06Z", "hours": 0.7311, "text": "I finally finished making the outer part of the macropad, now i just need to work on the firmware!"}, {"post_id": 8930, "ts": "2026-06-14T21:00:22Z", "hours": 0.8494, "text": "I started working on the case for the macropad. I had trouble with the extruding the parts and keeping them all into different things so I had to move around that. Now I am going to figure out how to add the spaces for the buttons, especially since I want them in a rather different way than what the guide is organizing them as."}, {"post_id": 8317, "ts": "2026-06-13T20:41:03Z", "hours": 0.3047, "text": "So right now I finished making the schematic, and I am working on the PCB editor to finish the digital part, the goal is that I finish it today. The little macropad will be used to play videogames (hopefully it helps me become better) that’s why I added 8 buttons, maybe I will add a usb port so I can connect it to my computer."}]...
|
Title: My awesome macropad! by @Luz | Stardance
D Title: My awesome macropad! by @Luz | Stardance
Devlogs:
So right now I finished making the schematic, and I am working on the PCB editor to finish the digital part, the goal is that I finish it today. The little macropad will be used to play videogames (hopefully it helps me become better) that’s why I added 8 buttons, maybe I will add a usb port so I can connect it to my computer.
I started working on the case for the macropad. I had trouble with the extruding the parts and keeping them all into different things so I had to move around that. Now I am going to figure out how to add the spaces for the buttons, especially since I want them in a rather different way than what the guide is organizing them as.
I finally finished making the outer part of the macropad, now i just need to work on the firmware!...
|
1792544001.0684185
|
1793148801.0684185
|
|
3937
|
My awesome macropad! by @Azra | Stardance
|
Azra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Azra | Stardance
|
1792514880.1265187
|
1793119680.1265187
|
|
3938
|
Patch Notes by @late-parrot | Stardance
|
late-parrot
|
0
|
1.35
|
0
|
[]
|
[{"post_id": 11665, "ts": "202 [{"post_id": 11665, "ts": "2026-06-19T00:28:49Z", "hours": 1.3456, "text": "Basic movement and tileset I implemented a simple movement system based off of a previous game, and set up a tileset so that I could build and test levels. I Also added some CC0 assets for testing purposes (I’ll change the assets later–I don’t really think they fit the style I’m going for) and set up the Hackatime extension. No actual gameplay mechanics yet, but I’ll do some testing and create some soon. I’m planning to implement sets of rules that change for each run, and the player will have to figure out how the rules work in order to progress and complete the run."}]...
|
Title: Patch Notes by @late-parrot | Stardance
De Title: Patch Notes by @late-parrot | Stardance
Devlogs:
Basic movement and tileset I implemented a simple movement system based off of a previous game, and set up a tileset so that I could build and test levels. I Also added some CC0 assets for testing purposes (I’ll change the assets later–I don’t really think they fit the style I’m going for) and set up the Hackatime extension. No actual gameplay mechanics yet, but I’ll do some testing and create some soon. I’m planning to implement sets of rules that change for each run, and the player will have to figure out how the rules work in order to progress and complete the run....
|
1792518546.4251328
|
1793123346.4251328
|
|
3939
|
My very useful macropad! by @adhyan2810 | Stardanc My very useful macropad! by @adhyan2810 | Stardance...
|
adhyan2810
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very useful macropad! by @adhyan2810 | S Title: My very useful macropad! by @adhyan2810 | Stardance...
|
1792914678.5456185
|
1793778678.5456185
|
|
3940
|
Tokn - A CLI TOTP app by @nautrw | Stardance
|
nautrw
|
1
|
19.0
|
303
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-24T21:02:33Z", "hours": 19.0, "multiplier": 15.96, "payout": 303, "blessing": "neutral", "text": "My project is a CLI app that generates TOTP (Time-based one-time password) codes for authentication to other apps. I built this to make it easier for me and perhaps others when logging in to apps that require TOTP, as reaching for my phone was annoying. To make it secure, I also implemented password encryption to make it safer. Along the way, I learned about the basics of encryption, UI/UX design, and building real projects. I think I will come back to this at some point in the future and improve it even more.", "repo": "https://github.com/nautrw/tokn", "demo": "https://pypi.org/project/tokn-nautrw"}]...
|
[{"post_id": 15298, "ts": "202 [{"post_id": 15298, "ts": "2026-06-24T20:58:37Z", "hours": 1.4864, "text": "After quite some time of tinkering, I was able to publish my project on PyPI. In the process, I also wrote a readme and recorded a live demo. I believe I can ship now."}, {"post_id": 15213, "ts": "2026-06-24T18:36:38Z", "hours": 1.9061, "text": "I have polished the get command to make it somewhat more obvious to the user which of the two codes to use based on the amount of time the current one has left. Also, I made it expand the path so as to allow ~ in the QR code image path."}, {"post_id": 12911, "ts": "2026-06-21T04:25:28Z", "hours": 1.5864, "text": "I figured out how to fix this bug where it would ask the user for the password regardless of whether they used the –help flag or not. This was because I was handling that logic inside the CLI command group, which is how I make the subcommands, but also runs every time a subcommand is run. I fixed this by using a custom decorator for the commands. This will generally be much more flexible because now I can have commands that don’t require a password."}, {"post_id": 9639, "ts": "2026-06-16T01:28:25Z", "hours": 0.2931, "text": "The add command will now check for existing keys by comparing the issuer and label."}, {"post_id": 9628, "ts": "2026-06-16T01:05:49Z", "hours": 1.6739, "text": "Nothing too major, as I haven’t had much time to work on the project. Instead of always requiring a subcommand when running the add command, it will default to QR code because that is the most common. Then, the option to add just a normal secret key is –code, and, now, I implemented just getting from an URI. Also, I made it so that the QR and URI inputs will allow the user to override the output because they generally come with the issuer and label."}, {"post_id": 7258, "ts": "2026-06-12T03:23:19Z", "hours": 0.4025, "text": "I have started working on improving the overall UX of the app. Instead of an init command, it will automatically detect if the user is a new user and run a sort of wizard. It’s still a little wonky, and I will fix that tomorrow, but when it is done the app will be much easier to use."}, {"post_id": 7230, "ts": "2026-06-12T02:02:19Z", "hours": 0.7092, "text": "I have split the add command into QR and just a regular raw secret key. The QR option only asks for the image path, because the URI should contain the issuer and label. This should increase clarity for the user because it won’t change the arguments passed to the command based on a flag as it did before."}, {"post_id": 7210, "ts": "2026-06-12T01:14:50Z", "hours": 3.1306, "text": "I switched to using a pyproject.toml file because this will be getting published sometime, and I will probably also use poetry. For the sake of compatibility with the other established TOTP apps, as well as to use the full extent of the TOTP URIs (they contain the issuer and account name already), I decided to divide the keys into issuers and accounts under those issuers. I will work on redesigning the add command to do this. Progress!"}, {"post_id": 6314, "ts": "2026-06-10T17:02:28Z", "hours": 0.985, "text": "I added a way to get the secret key from a QR code image to make it easier for the user to use. Previously they would have to scan the image themselves and get the code."}, {"post_id": 5966, "ts": "2026-06-09T23:57:41Z", "hours": 0.8367, "text": "I have polished some of the prompts. The keys file is also stored in a platform-agnostic way (on Linux it will be stored in ~/.local/share/tokn, but on Windows is another location)."}, {"post_id": 5762, "ts": "2026-06-09T17:41:18Z", "hours": 1.7889, "text": "Since last time: The init command initializes a new keys file; I would’ve just made it automatically initiate the process upon any command, but it would’ve made things like the get command a little wonky The list command lists all the keys The passwd command (not shown) changes the password The rm command removes a key I have added input validation to most of the commands now, and I found out how to do aliases I still need to polish some things, specially the consistency of the vocabulary (keys, services, etc.) and the prompts"}, {"post_id": 5622, "ts": "2026-06-09T14:28:30Z", "hours": 1.165, "text": "I got the basics of the app working! I can add new secrets and then retrieve them. I decided to show the next code because it doesn’t update automatically (it is meant to be a CLI app), so this will help if the code has a few seconds left. The password also takes a few seconds to verify, so this will prevent having to run it over and over. The next feature is data validation, as it is very basic right now."}, {"post_id": 5126, "ts": "2026-06-08T20:16:31Z", "hours": 2.625, "text": "I have the encryption working, so now I can grab the password salt, make the password hash from that, and use it to decrypt the other part of the file. I wrote this little test to showcase it, the key is generated and then I can encrypt and decrypt the file. Next thing to work on is storing the secret keys."}, {"post_id": 604, "ts": "2026-06-02T03:13:51Z", "hours": 0.4314, "text": "I can generate basic TOTPs now! This is currently with a random key, but soon I will add files to store the keys."}]...
|
Title: Tokn - A CLI TOTP app by @nautrw | Stardanc Title: Tokn - A CLI TOTP app by @nautrw | Stardance
Devlogs:
I can generate basic TOTPs now! This is currently with a random key, but soon I will add files to store the keys.
I have the encryption working, so now I can grab the password salt, make the password hash from that, and use it to decrypt the other part of the file. I wrote this little test to showcase it, the key is generated and then I can encrypt and decrypt the file. Next thing to work on is storing the secret keys.
I got the basics of the app working! I can add new secrets and then retrieve them. I decided to show the next code because it doesn’t update automatically (it is meant to be a CLI app), so this will help if the code has a few seconds left. The password also takes a few seconds to verify, so this will prevent having to run it over and over. The next feature is data validation, as it is very basic right now.
Since last time: The init command initializes a new keys file; I would’ve just made it automatically initiate the process upon any command, but it would’ve made things like the get command a little wonky The list command lists all the keys The passwd command (not shown) changes the password The rm command removes a key I have added input validation to most of the commands now, and I found out how to do aliases I still need to polish some things, specially the consistency of the vocabulary (keys, services, etc.) and the prompts
I have polished some of the prompts. The keys file is also stored in a platform-agnostic way (on Linux it will be stored in ~/.local/share/tokn, but on Windows is another location).
I added a way to get the secret key from a QR code image to make it easier for the user to use. Previously they would have to scan the image themselves and get the code.
I switched to using a pyproject.toml file because this will be getting published sometime, and I will probably also use poetry. For the sake of compatibility with the other established TOTP apps, as well as to use the full extent of the TOTP URIs (they contain the issuer and account name already), I decided to divide the keys into issuers and accounts under those issuers. I will work on redesigning the add command to do this. Progress!
I have split the add command into QR and just a regular raw secret key. The QR option only asks for the image path, because the URI should contain the issuer and label. This should increase clarity for the user because it won’t change the arguments passed to the command based on a flag as it did before.
I have started working on improving the overall UX of the app. Instead of an init command, it will automatically detect if the user is a new user and run a sort of wizard. It’s still a little wonky, and I will fix that tomorrow, but when it is done the app will be much easier to use.
Nothing too major, as I haven’t had much time to work on the project. Instead of always requiring a subcommand when running the add command, it will default to QR code because that is the most common. Then, the option to add just a normal secret key is –code, and, now, I implemented just getting from an URI. Also, I made it so that the QR and URI inputs will allow the user to override the output because they generally come with the issuer and label.
The add command will now check for existing keys by comparing the issuer and label.
I figured out how to fix this bug where it would ask the user for the password regardless of whether they used the –help flag or not. This was because I was handling that logic inside the CLI command group, which is how I make the subcommands, but also runs every time a subcommand is run. I fixed this by using a custom decorator for the commands. This will generally be much more flexible because now I can have commands that don’t require a password.
I have polished the get command to make it somewhat more obvious to the user which of the two codes to use based on the amount of time the current one has left. Also, I made it expand the path so as to allow ~ in the QR code image path.
After quite some time of tinkering, I was able to publish my project on PyPI. In the process, I also wrote a readme and recorded a live demo. I believe I can ship now.
Ships:
My project is a CLI app that generates TOTP (Time-based one-time password) codes for authentication to other apps. I built this to make it easier for me and perhaps others when logging in to apps that require TOTP, as reaching for my phone was annoying. To make it secure, I also implemented password encryption to make it safer. Along the way, I learned about the basics of encryption, UI/UX design, and building real projects. I think I will come back to this at some point in the future and improve it even more....
|
1792997598.4573865
|
1793083998.4573865
|
|
3941
|
My first slack bot! by @anisht245 | Stardance
|
anisht245
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-02T05:27:55Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a bot for the Hack Club Slack. It is called stardance bot. This bot can give the nasa picture of the day and tell jokes. The most challenging part was getting the inital code going. After this part, I will able to go through the process much easier. Making the app 24/7 was pretty hard, but after some googling, I got past that issue. I am most proud of the end result. Seeing it work makes me very happy. People should know the commands such as /sd-help, /sd-nasa, /sd-joke, and /sd-ping before using my bot.", "repo": "https://github.com/anishtiwari0518-spec/stardance-bot/tree/master", "demo": "https://app.slack.com/client/E09V59WQY1E/C0AFG0XGGMP"}]...
|
[{"post_id": 652, "ts": "2026- [{"post_id": 652, "ts": "2026-06-02T05:24:14Z", "hours": 0.4878, "text": "I just finished my first slack bot. Go check it out in the Hack Club slack. To activate it, type /sd-help to see all the commands you can try"}, {"post_id": 595, "ts": "2026-06-02T02:47:54Z", "hours": 0.2894, "text": "I am currently worked on my first slack bot the replies with pong, fetches NASA’s picture of the day, a programming hoke, and can list the available commands"}]...
|
Title: My first slack bot! by @anisht245 | Stardan Title: My first slack bot! by @anisht245 | Stardance
Devlogs:
I am currently worked on my first slack bot the replies with pong, fetches NASA’s picture of the day, a programming hoke, and can list the available commands
I just finished my first slack bot. Go check it out in the Hack Club slack. To activate it, type /sd-help to see all the commands you can try
Ships:
I made a bot for the Hack Club Slack. It is called stardance bot. This bot can give the nasa picture of the day and tell jokes. The most challenging part was getting the inital code going. After this part, I will able to go through the process much easier. Making the app 24/7 was pretty hard, but after some googling, I got past that issue. I am most proud of the end result. Seeing it work makes me very happy. People should know the commands such as /sd-help, /sd-nasa, /sd-joke, and /sd-ping before using my bot....
|
1793091067.5864258
|
1793177467.5864258
|
|
3942
|
Untitled project by @Olorin | Stardance
|
Olorin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Olorin | Stardance
|
1792806678.0814095
|
1793411478.0814095
|
|
3943
|
Game elements for the iq game by @OpenAir_Company Game elements for the iq game by @OpenAir_Company | Stardance...
|
OpenAir_Company
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-11T02:45:38Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a printable VEX IQ unique game element - a shooting game!", "repo": "https://github.com/Trittler-w/VEX-IQ-game-elements", "demo": ""}]...
|
[{"post_id": 6607, "ts": "2026 [{"post_id": 6607, "ts": "2026-06-11T02:37:51Z", "hours": 0.8169, "text": "Devlog: Modeling VEX IQ Game Elements Project: VEX IQ Custom Game Elements Software: Onshape Status: Part Modeling Phase Progress Update: Today’s focus was on drafting the core interactive pieces for the VEX IQ project. The individual parts are coming together nicely, and I’ve established a solid foundation for the final assembly. What I’ve Built So Far: Target Discs: Modeled two large blue discs and one smaller yellow disc. They feature clean central mounting holes and recessed inner faces, typical for VEX IQ structural mounting. Textured Rollers/Rods: Created two long, blue cylindrical elements with distinct horizontal ridges. The texturing turned out well and should visually simulate grip for robot intakes or roller mechanisms. The Container: Drafted a basic, open-top rectangular bin (light blue). Based on the project scope, this will likely serve as the holding area for the game balls. Workspace Organization: To keep the project modular and easy to navigate, the document is organized into specific part studios. You can see the workflow mapped out in the bottom tabs: separating “Balls,” “Big targets,” “Targets to be unlocked,” and the “Box of balls.” This setup is making iteration on individual pieces much cleaner. Next Steps: Transition over to the Assembly 1 tab to begin mating these components together. Establish the mechanical constraints (rotational, fastened, etc.) between the textured rods, the discs, and their eventual mounting frames. Finalize the modeling in the “Balls” tab to ensure they scale correctly with the open-top box."}]...
|
Title: Game elements for the iq game by @OpenAir_C Title: Game elements for the iq game by @OpenAir_Company | Stardance
Devlogs:
Devlog: Modeling VEX IQ Game Elements Project: VEX IQ Custom Game Elements Software: Onshape Status: Part Modeling Phase Progress Update: Today’s focus was on drafting the core interactive pieces for the VEX IQ project. The individual parts are coming together nicely, and I’ve established a solid foundation for the final assembly. What I’ve Built So Far: Target Discs: Modeled two large blue discs and one smaller yellow disc. They feature clean central mounting holes and recessed inner faces, typical for VEX IQ structural mounting. Textured Rollers/Rods: Created two long, blue cylindrical elements with distinct horizontal ridges. The texturing turned out well and should visually simulate grip for robot intakes or roller mechanisms. The Container: Drafted a basic, open-top rectangular bin (light blue). Based on the project scope, this will likely serve as the holding area for the game balls. Workspace Organization: To keep the project modular and easy to navigate, the document is organized into specific part studios. You can see the workflow mapped out in the bottom tabs: separating “Balls,” “Big targets,” “Targets to be unlocked,” and the “Box of balls.” This setup is making iteration on individual pieces much cleaner. Next Steps: Transition over to the Assembly 1 tab to begin mating these components together. Establish the mechanical constraints (rotational, fastened, etc.) between the textured rods, the discs, and their eventual mounting frames. Finalize the modeling in the “Balls” tab to ensure they scale correctly with the open-top box.
Ships:
I made a printable VEX IQ unique game element - a shooting game!...
|
1792986571.7186556
|
1793072971.7186556
|
|
3944
|
My awesome macropad! by @derped | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @derped | Stardance
|
1792655437.003354
|
1793260237.003354
|
|
3945
|
idk by @theLegend | Stardance
|
theLegend
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: idk by @theLegend | Stardance
|
1792752582.8025622
|
1793357382.8025622
|
|
3946
|
My awesome macropad! by @kyarpi | Stardance
|
kyarpi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @kyarpi | Stardance
|
1792695135.6819904
|
1793299935.6819904
|
|
3947
|
My awesome macropad! by @jin | Stardance
|
jin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @jin | Stardance
|
1792551258.536218
|
1793156058.536218
|
|
3948
|
My awesome macropad! by @jellycorn | Stardance
|
jellycorn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @jellycorn | Starda Title: My awesome macropad! by @jellycorn | Stardance...
|
1792644887.9000225
|
1793249687.9000225
|
|
3949
|
Orbit by @c0mrade | Stardance
|
c0mrade
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Orbit by @c0mrade | Stardance
|
1792525947.2669158
|
1793130747.2669158
|
|
3950
|
1st Discord Bot Iteration by @kyarpi | Stardance
|
kyarpi
|
0
|
3.74
|
0
|
[]
|
[{"post_id": 1179, "ts": "2026 [{"post_id": 1179, "ts": "2026-06-03T01:14:52Z", "hours": 3.7375, "text": "This will be my first short devlog. I created a basic Discord application that does some commands such as play tic-tac-toe and rock, paper, scissors! Nothing too crazy but, what else should I add to it?"}]...
|
Title: 1st Discord Bot Iteration by @kyarpi | Star Title: 1st Discord Bot Iteration by @kyarpi | Stardance
Devlogs:
This will be my first short devlog. I created a basic Discord application that does some commands such as play tic-tac-toe and rock, paper, scissors! Nothing too crazy but, what else should I add to it?...
|
1792734886.4580467
|
1793339686.4580467
|