|
68804
|
playground by @benji_mcshane | Stardance
|
benji_mcshane
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @benji_mcshane | Stardance
|
1793126952.7229202
|
1793731752.7229202
|
|
69504
|
playground by @breanna | Stardance
|
breanna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @breanna | Stardance
|
1792857061.2648509
|
1793461861.2648509
|
|
72251
|
playground by @brocantbeseries | Stardance
|
brocantbeseries
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @brocantbeseries | Stardance
|
1793432844.2077615
|
1794037644.2077615
|
|
69061
|
playground by @buraibenceb2026 | Stardance
|
buraibenceb2026
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @buraibenceb2026 | Stardance
|
1793130495.29424
|
1793735295.29424
|
|
68683
|
playground by @clover313 | Stardance
|
clover313
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @clover313 | Stardance
|
1793123578.529525
|
1793728378.529525
|
|
69351
|
playground by @devitulika037 | Stardance
|
devitulika037
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @devitulika037 | Stardance
|
1793130921.1692817
|
1793735721.1692817
|
|
68922
|
playground by @fathima | Stardance
|
fathima
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @fathima | Stardance
|
1793127181.1149755
|
1793731981.1149755
|
|
72110
|
playground by @hacker14 | Stardance
|
hacker14
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @hacker14 | Stardance
|
1793382454.8706496
|
1793987254.8706496
|
|
70477
|
playground by @harsh_2310 | Stardance
|
harsh_2310
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @harsh_2310 | Stardance
|
1793015270.5212243
|
1793620070.5212243
|
|
70075
|
playground by @imamaahmad | Stardance
|
imamaahmad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @imamaahmad | Stardance
|
1792958014.6051714
|
1793562814.6051714
|
|
72331
|
playground by @imranahmad | Stardance
|
imranahmad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @imranahmad | Stardance
|
1793447234.4200685
|
1794052034.4200685
|
|
67133
|
playground by @javedmevati680 | Stardance
|
javedmevati680
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @javedmevati680 | Stardance
|
1793105722.6228719
|
1793710522.6228719
|
|
70708
|
playground by @kavith-kamalesh | Stardance
|
kavith-kamalesh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @kavith-kamalesh | Stardance
|
1793224502.6652691
|
1793829302.6652691
|
|
67725
|
playground by @kayacrv | Stardance
|
kayacrv
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @kayacrv | Stardance
|
1793112865.353521
|
1793717665.353521
|
|
69532
|
playground by @linjiaqi090304 | Stardance
|
linjiaqi090304
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @linjiaqi090304 | Stardance
|
1792857084.9603817
|
1793461884.9603817
|
|
70056
|
playground by @lowkeey | Stardance
|
lowkeey
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @lowkeey | Stardance
|
1792957990.093493
|
1793562790.093493
|
|
69547
|
playground by @matteo_viggiani | Stardance
|
matteo_viggiani
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @matteo_viggiani | Stardance
|
1792857109.548207
|
1793461909.548207
|
|
68898
|
playground by @michelabrahamvarghese | Stardance
|
michelabrahamvarghese
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-17T06:43:29Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "It was vey easy", "repo": "https://github.com/Peonix1/My-desktop-pet", "demo": "https://peonix1.itch.io/cat-pet"}]...
|
[{"post_id": 78514, "ts": "202 [{"post_id": 78514, "ts": "2026-10-11T01:44:25Z", "hours": 1.4742, "text": "Code"}]...
|
Title: playground by @michelabrahamvarghese | Star Title: playground by @michelabrahamvarghese | Stardance
Devlogs:
Code
Ships:
It was vey easy...
|
1793354029.5384037
|
1793440429.5384037
|
|
67981
|
playground by @mistryvivaan | Stardance
|
mistryvivaan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @mistryvivaan | Stardance
|
1793116293.1911275
|
1793721093.1911275
|
|
68540
|
playground by @rohana | Stardance
|
rohana
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @rohana | Stardance
|
1793123372.6511161
|
1793728172.6511161
|
|
72365
|
playground by @roushanarman7 | Stardance
|
roushanarman7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @roushanarman7 | Stardance
|
1793454429.6937313
|
1794059229.6937313
|
|
68865
|
playground by @ruhaankazmi | Stardance
|
ruhaankazmi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @ruhaankazmi | Stardance
|
1793127053.8556316
|
1793731853.8556316
|
|
67704
|
playground by @seeyon | Stardance
|
seeyon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @seeyon | Stardance
|
1793112829.3294628
|
1793717629.3294628
|
|
66966
|
playground by @sharmasri | Stardance
|
sharmasri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @sharmasri | Stardance
|
1793105472.5706956
|
1793710272.5706956
|
|
68862
|
playground by @slyfier | Stardance
|
slyfier
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @slyfier | Stardance
|
1793127050.059164
|
1793731850.059164
|
|
72210
|
playground by @synameta | Stardance
|
synameta
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @synameta | Stardance
|
1793414835.8279824
|
1794019635.8279824
|
|
68357
|
playground by @tito_hippert | Stardance
|
tito_hippert
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @tito_hippert | Stardance
|
1793120018.4493864
|
1793724818.4493864
|
|
70779
|
playground by @utkarsh_priyadarshi8 | Stardance
|
utkarsh_priyadarshi8
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @utkarsh_priyadarshi8 | Stard Title: playground by @utkarsh_priyadarshi8 | Stardance...
|
1793267573.330102
|
1793872373.330102
|
|
70772
|
playground by @websrp | Stardance
|
websrp
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @websrp | Stardance
|
1793267565.6762629
|
1793872365.6762629
|
|
71878
|
playground by @xuri | Stardance
|
xuri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @xuri | Stardance
|
1793270836.3004928
|
1793875636.3004928
|
|
71973
|
playground stuff by @nytro | Stardance
|
nytro
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground stuff by @nytro | Stardance
|
1793321226.2075438
|
1793926026.2075438
|
|
71974
|
playground stuff by @nytro | Stardance
|
nytro
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground stuff by @nytro | Stardance
|
1793321227.1085267
|
1793926027.1085267
|
|
71975
|
playground stuff by @nytro | Stardance
|
nytro
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground stuff by @nytro | Stardance
|
1793321227.9809167
|
1793926027.9809167
|
|
24758
|
playin with optics by @awildfire | Stardance
|
awildfire
|
0
|
9.04
|
0
|
[]
|
[{"post_id": 19387, "ts": "202 [{"post_id": 19387, "ts": "2026-06-30T18:02:38Z", "hours": 1.7603, "text": "I took a break from looking at hardware for about. 6 hours, got back to it and solved the problem 0-0. this is why it’s good to take breaks lol. Retested it on an arduino nano and it did refuse to go to zero. Not sure what was up with that, the code was fine though. That board has also been through a bit. Got to working on the design for the boxes to hold the mirrors and diffraction grating."}, {"post_id": 18477, "ts": "2026-06-29T17:18:38Z", "hours": 1.3, "text": "more painting plus breadboarding: painting was fine, easy, peaceful. Breadboarding??? I have pretty good troubleshooting skills, but also my stuff doesn’t work half the time due to faulty parts, or wiring, or.. code, etc. I started with a stepper motor that hadn’t been through the depths, and a corresponding driver. Tried one set of code, no input from the pot was working, swapped out the pot for one I know works from using it in a separate project. No luck, stepper motor I know works because it was moving during the first test. Just didn’t change speed. Stepper driver also works I’m pretty sure because it did light up as the motor moved. 2 things down. Swapped the board since most of mine are off brand and a little suspicious. Used a board I know works from a previous project that also used pot analog input. Swapped code for a move with pot (location) code, checked libraries, updated no issues. Swapped the breadboard, honestly still don’t trust the one I grabbed. Though it looks… okay. I will also check the rails (no corrosion!) could be a wire issue. I need to grab my multimeter… but um… the probes on that are also broken. Or well one is. I feel like I’m playing murder investigator and I’m personally not a fan. 😮💨 I also set up serial monitor and tried a couple things and I just simply get 14. Okay. 14. Okay."}, {"post_id": 17763, "ts": "2026-06-28T18:09:42Z", "hours": 2.2839, "text": "tolerance will be the death of me: redesign one showed me that my tolerance was off, and that the area at the top to screw things in was simply too small for the printer and therefore also would not be very stable. Re did that design for version 3 and did tolerance for 0.1 mm… which should have been good (spoiler it still didn’t fit i rechecked my measurements I guess the printer simply needs more tolerance.) but it was not. I did add the upper area and made it 5 mm across on all sides. then added reinforcement pillars because after maybe 20 min of fanagaling the loft function, I still had some odd spaces that would not be stable so… pillar stability it is. Which after printing? looks fine and is acceptable in my mind. Though, because of the part that still didn’t fit with tolerance I did chop it off because I didn’t want to make another version right at that moment. (11pm) I used a Dremel and the circular blade bit. Doing my best to not injure myself and also had my safety glasses on wowie! After chopping some stuff off and then testing it, the idea works, tested then with holding together the preemptive lens holders and also works pretty well. the holder with no lenses will not be used, but the 0.55 and 0.1 will be. I might be able to improve them somehow but IDK yet. Biggest hard part is getting. them. to stay on? That’s a problem for later and horrible evil cad design. Also painted the outsides black to absorb stray light while the insides stay white to reflect light. bulb collator v3 (will be updated later)"}, {"post_id": 16014, "ts": "2026-06-26T00:10:40Z", "hours": 1.1669, "text": "got the v1 collector off the printer and took a looksee, tolerance was… almost there. I’ll probably do a little more next time for the clamp. The main issue was that the lip of the bulb holder and the starting curve of the collector were simply too close. An extended region of about another 10 mm in height should fix the problem plus I’ll change the sides to go up straight… ish? not the curved version. Plus, needs more clamps and or a better method of attachment after grtting it around. wait. So. I may be silly. I could print it all in one go… because i can slide it in…. oh… my… getting it to stay i could use pins somehow. Unsure. The sides will also need to be much thicker in order to be able to mount the lenses on, but this was a good test of concept! I’m pretty happy with it all things considered about 2 hours for a print and a couple of mishaps but came out ok. I’m not super deep into printing settings yet so if you have recommendations… lmk."}, {"post_id": 14802, "ts": "2026-06-24T01:24:40Z", "hours": 2.0667, "text": "fighting with CAD, I don’t usually use OnShape since at my school we used inventor, but that requires a license and so far onshape has not been too bad. I may download fusion later but just haven’t gotten to all that. I got a clamp set up designed for around the bulb housing and I have an idea in mind but modeling it is a little harder then expected. As per usual, with CAD. I also don’t often use assemblies so I might have to look up a couple of videos on that as well. I added tolerance and I’m hoping when I give it a test print it should be ok, but knowing 3D printing there might be something wrong at some point. I’m trying to design it in a way that it can be printed facing up with minimal supports. Hopefully! (these are the measurements of the insides of the lenses)"}, {"post_id": 14582, "ts": "2026-06-23T19:03:56Z", "hours": 0.4667, "text": "gathering supplies and taking measurements !!! I have three microscope / camera attachments I am going to try and make a secondary attachment for to test with a lightbulb as a finer beam source of light"}]...
|
Title: playin with optics by @awildfire | Stardanc Title: playin with optics by @awildfire | Stardance
Devlogs:
gathering supplies and taking measurements !!! I have three microscope / camera attachments I am going to try and make a secondary attachment for to test with a lightbulb as a finer beam source of light
fighting with CAD, I don’t usually use OnShape since at my school we used inventor, but that requires a license and so far onshape has not been too bad. I may download fusion later but just haven’t gotten to all that. I got a clamp set up designed for around the bulb housing and I have an idea in mind but modeling it is a little harder then expected. As per usual, with CAD. I also don’t often use assemblies so I might have to look up a couple of videos on that as well. I added tolerance and I’m hoping when I give it a test print it should be ok, but knowing 3D printing there might be something wrong at some point. I’m trying to design it in a way that it can be printed facing up with minimal supports. Hopefully! (these are the measurements of the insides of the lenses)
got the v1 collector off the printer and took a looksee, tolerance was… almost there. I’ll probably do a little more next time for the clamp. The main issue was that the lip of the bulb holder and the starting curve of the collector were simply too close. An extended region of about another 10 mm in height should fix the problem plus I’ll change the sides to go up straight… ish? not the curved version. Plus, needs more clamps and or a better method of attachment after grtting it around. wait. So. I may be silly. I could print it all in one go… because i can slide it in…. oh… my… getting it to stay i could use pins somehow. Unsure. The sides will also need to be much thicker in order to be able to mount the lenses on, but this was a good test of concept! I’m pretty happy with it all things considered about 2 hours for a print and a couple of mishaps but came out ok. I’m not super deep into printing settings yet so if you have recommendations… lmk.
tolerance will be the death of me: redesign one showed me that my tolerance was off, and that the area at the top to screw things in was simply too small for the printer and therefore also would not be very stable. Re did that design for version 3 and did tolerance for 0.1 mm… which should have been good (spoiler it still didn’t fit i rechecked my measurements I guess the printer simply needs more tolerance.) but it was not. I did add the upper area and made it 5 mm across on all sides. then added reinforcement pillars because after maybe 20 min of fanagaling the loft function, I still had some odd spaces that would not be stable so… pillar stability it is. Which after printing? looks fine and is acceptable in my mind. Though, because of the part that still didn’t fit with tolerance I did chop it off because I didn’t want to make another version right at that moment. (11pm) I used a Dremel and the circular blade bit. Doing my best to not injure myself and also had my safety glasses on wowie! After chopping some stuff off and then testing it, the idea works, tested then with holding together the preemptive lens holders and also works pretty well. the holder with no lenses will not be used, but the 0.55 and 0.1 will be. I might be able to improve them somehow but IDK yet. Biggest hard part is getting. them. to stay on? That’s a problem for later and horrible evil cad design. Also painted the outsides black to absorb stray light while the insides stay white to reflect light. bulb collator v3 (will be updated later)
more painting plus breadboarding: painting was fine, easy, peaceful. Breadboarding??? I have pretty good troubleshooting skills, but also my stuff doesn’t work half the time due to faulty parts, or wiring, or.. code, etc. I started with a stepper motor that hadn’t been through the depths, and a corresponding driver. Tried one set of code, no input from the pot was working, swapped out the pot for one I know works from using it in a separate project. No luck, stepper motor I know works because it was moving during the first test. Just didn’t change speed. Stepper driver also works I’m pretty sure because it did light up as the motor moved. 2 things down. Swapped the board since most of mine are off brand and a little suspicious. Used a board I know works from a previous project that also used pot analog input. Swapped code for a move with pot (location) code, checked libraries, updated no issues. Swapped the breadboard, honestly still don’t trust the one I grabbed. Though it looks… okay. I will also check the rails (no corrosion!) could be a wire issue. I need to grab my multimeter… but um… the probes on that are also broken. Or well one is. I feel like I’m playing murder investigator and I’m personally not a fan. 😮💨 I also set up serial monitor and tried a couple things and I just simply get 14. Okay. 14. Okay.
I took a break from looking at hardware for about. 6 hours, got back to it and solved the problem 0-0. this is why it’s good to take breaks lol. Retested it on an arduino nano and it did refuse to go to zero. Not sure what was up with that, the code was fine though. That board has also been through a bit. Got to working on the design for the boxes to hold the mirrors and diffraction grating....
|
1793238574.1412144
|
1793843374.1412144
|
|
27793
|
playing chess through a CNN by @advay_awesomer | S playing chess through a CNN by @advay_awesomer | Stardance...
|
advay_awesomer
|
1
|
76.0
|
161
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-28T18:32:11Z", "hours": 55.0, "multiplier": 16.14, "payout": 161, "blessing": "neutral", "text": "Made chesscnn — a chess engine that picks its moves from a convolutional neural network instead of hand-written rules, AlphaZero-style. The net (PyTorch, a residual tower with two heads) looks at the board as a stack of 19 image-like planes and outputs both a move-probability map and a single “who’s winning” score. A PUCT Monte-Carlo Tree Search then uses those to actually play. There’s a CLI and a Streamlit web app where you can play it and watch its eval bar, its predicted line, and a heatmap of where it wants to move. Challenging: encoding chess moves for the network was the rabbit hole — every possible move has to map to one of 4,672 output slots (the 8×8×73 scheme), and promotions/castling/en-passant all have edge cases. I round-tripped 219k moves to prove the mapping never collides. The other hard part was getting it to play well without a giant training run — a freshly-initialized net plays nonsense, so I blend the network’s evaluation with a classical hand-crafted one and let the search do the heavy lifting. Proud of: it plays real openings out of the box (it’ll walk into a Ruy Lopez or a Pirc), it found a tactic in testing (won a hanging queen), and it went 0 losses across 14 games vs a random-mover. ~9,000 lines of Python with 53 passing tests, and a full training stack (self-play → replay buffer → trainer → arena/Elo) if you want to make it stronger. To test it: clone github.com/advaycode/CNN1, pip install -r requirements-app.txt, then streamlit run chesscnn/app.py and play it in your browser.", "repo": "https://github.com/advaycode/CNN1", "demo": "https://advaycode.github.io/CNN1/"}]...
|
[{"post_id": 39672, "ts": "202 [{"post_id": 39672, "ts": "2026-08-02T20:02:37Z", "hours": 21.0, "text": "designing some more model architecture"}, {"post_id": 17779, "ts": "2026-06-28T18:29:53Z", "hours": 55.0, "text": "The entire architecture for the machine learning model"}]...
|
Title: playing chess through a CNN by @advay_aweso Title: playing chess through a CNN by @advay_awesomer | Stardance
Devlogs:
The entire architecture for the machine learning model
designing some more model architecture
Ships:
Made chesscnn — a chess engine that picks its moves from a convolutional neural network instead of hand-written rules, AlphaZero-style. The net (PyTorch, a residual tower with two heads) looks at the board as a stack of 19 image-like planes and outputs both a move-probability map and a single “who’s winning” score. A PUCT Monte-Carlo Tree Search then uses those to actually play. There’s a CLI and a Streamlit web app where you can play it and watch its eval bar, its predicted line, and a heatmap of where it wants to move. Challenging: encoding chess moves for the network was the rabbit hole — every possible move has to map to one of 4,672 output slots (the 8×8×73 scheme), and promotions/castling/en-passant all have edge cases. I round-tripped 219k moves to prove the mapping never collides. The other hard part was getting it to play well without a giant training run — a freshly-initialized net plays nonsense, so I blend the network’s evaluation with a classical hand-crafted one and let the search do the heavy lifting. Proud of: it plays real openings out of the box (it’ll walk into a Ruy Lopez or a Pirc), it found a tactic in testing (won a hanging queen), and it went 0 losses across 14 games vs a random-mover. ~9,000 lines of Python with 53 passing tests, and a full training stack (self-play → replay buffer → trainer → arena/Elo) if you want to make it stronger. To test it: clone github.com/advaycode/CNN1, pip install -r requirements-app.txt, then streamlit run chesscnn/app.py and play it in your browser....
|
1792882076.1522121
|
1793746076.1522121
|
|
67926
|
playlist by @vittorioprivitera02 | Stardance
|
vittorioprivitera02
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playlist by @vittorioprivitera02 | Stardanc Title: playlist by @vittorioprivitera02 | Stardance...
|
1793116214.40397
|
1793721014.40397
|
|
5965
|
playlore.app by @mattliepins | Stardance
|
mattliepins
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playlore.app by @mattliepins | Stardance
|
1792795747.4351249
|
1793400547.4351249
|
|
57179
|
pleasedon'tdestroymyears by @The_Blue_Reverber pleasedon'tdestroymyears by @The_Blue_Reverberation | Stardance...
|
The_Blue_Reverberation
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pleasedon'tdestroymyears by @The_Blue_R Title: pleasedon'tdestroymyears by @The_Blue_Reverberation | Stardance...
|
1793422050.0499883
|
1794026850.0499883
|
|
23166
|
plexity.tools by @OrangJaguar | Stardance
|
OrangJaguar
|
1
|
4.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-01T04:25:53Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Full-stack personal dashboard that rebuilds 16+ everyday productivity tools from scratch into a unified system — task manager, calendar, grade tracker, live stock workspace, college planner, and more — all connected through a shared data layer and navigated through a single command bar and AI assistant.", "repo": "https://github.com/OrangJaguar/Plexity", "demo": "https://plexity.tools/"}]...
|
[{"post_id": 19573, "ts": "202 [{"post_id": 19573, "ts": "2026-06-30T22:13:51Z", "hours": 4.4089, "text": "Plexity — Devlog 01 I have a problem. Whenever I open my laptop to get stuff done, I immediately end up with 6 tabs open before I’ve done anything. One for tasks, one for my calendar, one to organize my college application workspace, one because I wanted to check a stock real quick, and one for a GPA calculator I found on some random website in 2023 and never closed. You know the feeling. So I built Plexity — a full-stack personal dashboard that just… has everything built exactly how I think works the best and looks the best. One shell, one place, command bar at the top. that’s it. What is it actually Plexity is a unified productivity OS with 16+ tools built from scratch , all connected through a shared data layer. Not a Notion clone, not an AI wrapper. Just tools I actually use, rebuilt the way I want them. Here’s what’s inside right now: Dashboard — your home base, everything at a glance Tasks — natural language date parsing (type “due friday” and it figures it out) Calendar — actually connected to your tasks and deadlines Grades — GPA tracker with per-course breakdowns Goals — long-term tracking, not just to-dos Journal — private, clean, no distractions Focus — timer, nothing else Calculator — with real math rendering via KaTeX PDF Tools — in-browser, no upload-to-some-random-site required Profile — A personal reference hub for your identity, background, context, links, etc. Stocks — live workspace for quick lookups College — college planning tools (this one’s personal) Lists — simple, fast list-making Units — unit converter Typing — typing speed practice Passwords — local password manager Catalog — browse everything from one place The whole thing is navigated through a single command bar. Hit a shortcut, type what you want, open it. It felt weird to use at first and now I can’t imagine going back. What I’ve been building Honestly… everything at once, which is probably not the smartest way to ship but here we are. The part I’m most proud of right now is how the tools actually talk to each other. Your tasks show up in your calendar. Your goals connect to your to-do list. it’s not just 16 isolated pages — there’s a shared data layer underneath holding it together. Getting that right took longer than I expected. The command bar was also a whole thing to build. Parsing natural language dates with chrono-node , routing commands to the right tool, making it feel instant — there were a lot of small details that had to line up before it felt good. Now it does. The stocks tool is one of my favorites because it’s the one I find myself opening randomly throughout the day. Live lookups, clean workspace, no clutter — just the data you want without the noise of a full brokerage UI. Built it for myself and it turned out really clean. Tech React + Vite + Tailwind + Zustand + TanStack Query + Base44 for the backend. Kept it lean on purpose — no unnecessary abstractions, just the tools that made the most sense. It’s Open Source The whole thing is on GitHub — github.com/OrangJaguar/Plexity . Still a side project, always free, no AI features, no paywall. Live at plexity.tools . More tools coming. More devlogs coming. Just wanted to get this first one out. — Sanskar"}]...
|
Title: plexity.tools by @OrangJaguar | Stardance
Title: plexity.tools by @OrangJaguar | Stardance
Devlogs:
Plexity — Devlog 01 I have a problem. Whenever I open my laptop to get stuff done, I immediately end up with 6 tabs open before I’ve done anything. One for tasks, one for my calendar, one to organize my college application workspace, one because I wanted to check a stock real quick, and one for a GPA calculator I found on some random website in 2023 and never closed. You know the feeling. So I built Plexity — a full-stack personal dashboard that just… has everything built exactly how I think works the best and looks the best. One shell, one place, command bar at the top. that’s it. What is it actually Plexity is a unified productivity OS with 16+ tools built from scratch , all connected through a shared data layer. Not a Notion clone, not an AI wrapper. Just tools I actually use, rebuilt the way I want them. Here’s what’s inside right now: Dashboard — your home base, everything at a glance Tasks — natural language date parsing (type “due friday” and it figures it out) Calendar — actually connected to your tasks and deadlines Grades — GPA tracker with per-course breakdowns Goals — long-term tracking, not just to-dos Journal — private, clean, no distractions Focus — timer, nothing else Calculator — with real math rendering via KaTeX PDF Tools — in-browser, no upload-to-some-random-site required Profile — A personal reference hub for your identity, background, context, links, etc. Stocks — live workspace for quick lookups College — college planning tools (this one’s personal) Lists — simple, fast list-making Units — unit converter Typing — typing speed practice Passwords — local password manager Catalog — browse everything from one place The whole thing is navigated through a single command bar. Hit a shortcut, type what you want, open it. It felt weird to use at first and now I can’t imagine going back. What I’ve been building Honestly… everything at once, which is probably not the smartest way to ship but here we are. The part I’m most proud of right now is how the tools actually talk to each other. Your tasks show up in your calendar. Your goals connect to your to-do list. it’s not just 16 isolated pages — there’s a shared data layer underneath holding it together. Getting that right took longer than I expected. The command bar was also a whole thing to build. Parsing natural language dates with chrono-node , routing commands to the right tool, making it feel instant — there were a lot of small details that had to line up before it felt good. Now it does. The stocks tool is one of my favorites because it’s the one I find myself opening randomly throughout the day. Live lookups, clean workspace, no clutter — just the data you want without the noise of a full brokerage UI. Built it for myself and it turned out really clean. Tech React + Vite + Tailwind + Zustand + TanStack Query + Base44 for the backend. Kept it lean on purpose — no unnecessary abstractions, just the tools that made the most sense. It’s Open Source The whole thing is on GitHub — github.com/OrangJaguar/Plexity . Still a side project, always free, no AI features, no paywall. Live at plexity.tools . More tools coming. More devlogs coming. Just wanted to get this first one out. — Sanskar
Ships:
Full-stack personal dashboard that rebuilds 16+ everyday productivity tools from scratch into a unified system — task manager, calendar, grade tracker, live stock workspace, college planner, and more — all connected through a shared data layer and navigated through a single command bar and AI assistant....
|
1793252905.3669794
|
1793339305.3669794
|
|
28931
|
ploot by @yay | Stardance
|
yay
|
1
|
21.0
|
257
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-27T04:44:39Z", "hours": 21.0, "multiplier": 12.18, "payout": 257, "blessing": "neutral", "text": "this is ploot, an ai powered planner that helps you allocate time to your tasks. you drag your availability on the calendar, write down your tasks in the rich text editor, then it gives you an editable calendar that you can export to a real calendar app(.ics format)! this was my first time making an app like this, so i used a bit of ai in the debugging process, especially for small things that i didn’t notice. there were a lot of challenges, but some of the especially annoying ones were the models returning errors, having signup errors, and timezone mismatches. what i really like about this is that its actually usable in my daily life :D its not something i make and then leave to rot, and is really useful for my indecisiveness. things to note beforehand: its passwordless and uses magic link login, is very slow in loading events(so pls be patient), and the generated schedules are not saved into a database or anything so once you refresh the page they’re gone. also (this probably wont happen) but you might get ratelimited", "repo": "https://github.com/nxzeh727/ploot", "demo": "https://ploot1.vercel.app"}]...
|
[{"post_id": 74296, "ts": "202 [{"post_id": 74296, "ts": "2026-09-27T04:18:39Z", "hours": 4.8806, "text": "ploot devlog #3 :D i added a modifications section so that you can modify your schedule to how you would want it to be. i also changed the ai models so that it would be better and cleaned up remaining bugs. its almost ready to ship! :D"}, {"post_id": 62279, "ts": "2026-09-05T15:58:02Z", "hours": 6.3167, "text": "devlog #2 :D i fixed the ui :D and also got rid of a bunch of bugs related to scheduling and signup/login i also added a dashboard but theres nothing in it so far there are still some problems though, since the ai doesn’t generate schedules half the time. after this, i mostly plan on adding a modification part for the schedule, a place to save the calendar and check it, and some stuff in the dashboard. :D I’m also planning on upgrading the text place into a proper todo-list thanks for reading :D"}, {"post_id": 42754, "ts": "2026-08-07T17:03:52Z", "hours": 9.8656, "text": "ploot devlog #1: so far, I’ve added a lot of things: the basic funciton(a calendar where you select the times available, a somewhat formatted editor where you can put what you need to do for that day, and an AI schedule generated from these pieces of information). i also created authentication(using maigc link only). initially, i stored the events and resulting schedule in a json, but i changed the inputs and put them into a database, and then converted the resulting schedule into .ics format so you can download it. as of right now, its a bit ugly, but that will be fixed in the future!"}]...
|
Title: ploot by @yay | Stardance
Devlogs:
ploot d Title: ploot by @yay | Stardance
Devlogs:
ploot devlog #1: so far, I’ve added a lot of things: the basic funciton(a calendar where you select the times available, a somewhat formatted editor where you can put what you need to do for that day, and an AI schedule generated from these pieces of information). i also created authentication(using maigc link only). initially, i stored the events and resulting schedule in a json, but i changed the inputs and put them into a database, and then converted the resulting schedule into .ics format so you can download it. as of right now, its a bit ugly, but that will be fixed in the future!
devlog #2 :D i fixed the ui :D and also got rid of a bunch of bugs related to scheduling and signup/login i also added a dashboard but theres nothing in it so far there are still some problems though, since the ai doesn’t generate schedules half the time. after this, i mostly plan on adding a modification part for the schedule, a place to save the calendar and check it, and some stuff in the dashboard. :D I’m also planning on upgrading the text place into a proper todo-list thanks for reading :D
ploot devlog #3 :D i added a modifications section so that you can modify your schedule to how you would want it to be. i also changed the ai models so that it would be better and cleaned up remaining bugs. its almost ready to ship! :D
Ships:
this is ploot, an ai powered planner that helps you allocate time to your tasks. you drag your availability on the calendar, write down your tasks in the rich text editor, then it gives you an editable calendar that you can export to a real calendar app(.ics format)! this was my first time making an app like this, so i used a bit of ai in the debugging process, especially for small things that i didn’t notice. there were a lot of challenges, but some of the especially annoying ones were the models returning errors, having signup errors, and timezone mismatches. what i really like about this is that its actually usable in my daily life :D its not something i make and then leave to rot, and is really useful for my indecisiveness. things to note beforehand: its passwordless and uses magic link login, is very slow in loading events(so pls be patient), and the generated schedules are not saved into a database or anything so once you refresh the page they’re gone. also (this probably wont happen) but you might get ratelimited...
|
1793346539.5513885
|
1793432939.5513885
|
|
46005
|
pls by @ImLuke | Stardance
|
ImLuke
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pls by @ImLuke | Stardance
|
1792929117.9720204
|
1793793117.9720204
|
|
37813
|
pls delete by @SkilledBtLzy | Stardance
|
SkilledBtLzy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pls delete by @SkilledBtLzy | Stardance
|
1792741883.2618878
|
1793346683.2618878
|
|
20524
|
plustwo by @pinetree182 | Stardance
|
pinetree182
|
0
|
0.0
|
0
|
[]
|
[{"post_id": 19542, "ts": "202 [{"post_id": 19542, "ts": "2026-06-30T21:21:32Z", "hours": 0.0, "text": "I set up a little webpage with a stopwatch in the center, which you can start and stop with the spacebar. I’ll work on adding time logging and average calculation in the next devlog"}]...
|
Title: plustwo by @pinetree182 | Stardance
Devlog Title: plustwo by @pinetree182 | Stardance
Devlogs:
I set up a little webpage with a stopwatch in the center, which you can start and stop with the spacebar. I’ll work on adding time logging and average calculation in the next devlog...
|
1792928870.7285337
|
1793792870.7285337
|
|
691
|
pluto1 by @ardelle54321 | Stardance
|
ardelle54321
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pluto1 by @ardelle54321 | Stardance
|
1793382498.6997206
|
1793987298.6997206
|
|
684
|
pluto1! by @sal2x | Stardance
|
sal2x
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pluto1! by @sal2x | Stardance
|
1793231361.369066
|
1793836161.369066
|
|
44486
|
pmot by @muhayyo | Stardance
|
muhayyo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pmot by @muhayyo | Stardance
|
1793278078.171883
|
1793882878.171883
|
|
44609
|
pngladiators by @_ | Stardance
|
_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pngladiators by @_ | Stardance
|
1793285584.6756468
|
1793890384.6756468
|
|
13856
|
pocket MP3 player by @jjuanito4373 | Stardance
|
jjuanito4373
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pocket MP3 player by @jjuanito4373 | Starda Title: pocket MP3 player by @jjuanito4373 | Stardance...
|
1792734815.92609
|
1793339615.92609
|
|
48607
|
pocket size synthesizer by @Hummelkoenig | Stardan pocket size synthesizer by @Hummelkoenig | Stardance...
|
Hummelkoenig
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pocket size synthesizer by @Hummelkoenig | Title: pocket size synthesizer by @Hummelkoenig | Stardance...
|
1792907372.564235
|
1793771372.564235
|
|
35982
|
pocketlabos by @shrr | Stardance
|
shrr
|
0
|
8.27
|
0
|
[]
|
[{"post_id": 36162, "ts": "202 [{"post_id": 36162, "ts": "2026-07-28T02:23:05Z", "hours": 2.6467, "text": "DEVLOG #2 Finally started building the first real application for Pocket Lab OS: Pixel Painter. The goal wasn’t to make a full art program straight away, but to create a solid first version that fits naturally into the desktop. I built the interface directly inside the existing app window instead of creating a separate page, keeping everything consistent with the rest of the operating system. Most of the work went into setting up the drawing canvas, toolbar, colour palette, and making sure the application matched the Pocket Lab OS aesthetic. I also spent some time wiring everything into the existing desktop so the app opens inside its own window rather than breaking the overall OS experience. As always, a surprising amount of time went into debugging. A few small CSS and JavaScript issues prevented parts of the interface from loading correctly, and I also fixed some asset paths while getting the app integrated into the project structure. Pixel Painter is now officially the first functional app inside Pocket Lab OS. Next, I want to keep expanding the operating system by building out the Microscope Viewer and Experiment Log so the desktop starts feeling like a complete digital biology workstation."}, {"post_id": 35307, "ts": "2026-07-26T17:01:00Z", "hours": 5.6203, "text": "DEVLOG #1 Spent today building the foundation of Pocket Lab OS. I finished writing the HTML structure for the desktop, including the top bar, desktop icons, taskbar, and placeholder windows for each app. I then moved on to the CSS, where I set up the overall colour palette using CSS variables, styled the desktop layout with Flexbox, designed the application windows, and switched the title bar controls to a macOS-inspired style. I also added hover animations for the desktop icons and built the initial taskbar layout. Finally, I connected everything with JavaScript. Application windows can now open, close, minimize, maximize, be dragged around the desktop, and automatically appear in the taskbar when opened. I also added a live clock and a simple window stacking system using z-index. Ended the session debugging a file path issue that prevented the CSS and JavaScript from loading. After fixing the links, the desktop framework finally came to life. Next up: create the custom pixel-art assets and start building the individual applications.."}]...
|
Title: pocketlabos by @shrr | Stardance
Devlogs:
Title: pocketlabos by @shrr | Stardance
Devlogs:
DEVLOG #1 Spent today building the foundation of Pocket Lab OS. I finished writing the HTML structure for the desktop, including the top bar, desktop icons, taskbar, and placeholder windows for each app. I then moved on to the CSS, where I set up the overall colour palette using CSS variables, styled the desktop layout with Flexbox, designed the application windows, and switched the title bar controls to a macOS-inspired style. I also added hover animations for the desktop icons and built the initial taskbar layout. Finally, I connected everything with JavaScript. Application windows can now open, close, minimize, maximize, be dragged around the desktop, and automatically appear in the taskbar when opened. I also added a live clock and a simple window stacking system using z-index. Ended the session debugging a file path issue that prevented the CSS and JavaScript from loading. After fixing the links, the desktop framework finally came to life. Next up: create the custom pixel-art assets and start building the individual applications..
DEVLOG #2 Finally started building the first real application for Pocket Lab OS: Pixel Painter. The goal wasn’t to make a full art program straight away, but to create a solid first version that fits naturally into the desktop. I built the interface directly inside the existing app window instead of creating a separate page, keeping everything consistent with the rest of the operating system. Most of the work went into setting up the drawing canvas, toolbar, colour palette, and making sure the application matched the Pocket Lab OS aesthetic. I also spent some time wiring everything into the existing desktop so the app opens inside its own window rather than breaking the overall OS experience. As always, a surprising amount of time went into debugging. A few small CSS and JavaScript issues prevented parts of the interface from loading correctly, and I also fixed some asset paths while getting the app integrated into the project structure. Pixel Painter is now officially the first functional app inside Pocket Lab OS. Next, I want to keep expanding the operating system by building out the Microscope Viewer and Experiment Log so the desktop starts feeling like a complete digital biology workstation....
|
1793292954.7957625
|
1793897754.7957625
|