|
35977
|
pideonwash website by @Lexx | Stardance
|
Lexx
|
0
|
46.31
|
0
|
[]
|
[{"post_id": 70730, "ts": "202 [{"post_id": 70730, "ts": "2026-09-19T17:39:52Z", "hours": 2.6106, "text": "Finalising the team page"}, {"post_id": 60754, "ts": "2026-09-03T10:13:41Z", "hours": 5.3256, "text": "V1.0 RELEASE DAY!! in the last two to three days we worked on finalizing everything and making sure we can publish everythin. We also made some brand new brand assets. Yesterday evening I finished configuring all the cloudflare tunnels. you can visit our website and everything there is to tell about us on pideonwash.com"}, {"post_id": 57650, "ts": "2026-08-29T21:14:57Z", "hours": 1.6183, "text": "random bug fixes almost time to get everything on the internet with our own domain just some very wierd and small little bugs along the way today"}, {"post_id": 56216, "ts": "2026-08-27T21:36:48Z", "hours": 4.2083, "text": "Part 04 of the casting call page rework. today i “finished” the backend. as well as worked on all the function I as an Admin wanna have and how i wanna get notified when someone registers. But i also now build the concept of the logic behind the registration pages."}, {"post_id": 55051, "ts": "2026-08-26T14:10:34Z", "hours": 4.3706, "text": "part 03 of the casting call page rework. today i implemented the feated from my team and redesigned/rethought how will go throu the form and the whole application prozess."}, {"post_id": 53931, "ts": "2026-08-24T17:09:18Z", "hours": 2.5769, "text": "DEVLOG Today I moved everything onto a dedicated Webserver. Consisting of an old Thinkpad running ZimaOS with a dedicated Ubuntu VM for the Webserver. So that i can soon actually start coding the backend logic. I also improved some small things that buged me. As well as a new feature on the hompage."}, {"post_id": 51009, "ts": "2026-08-20T14:28:45Z", "hours": 1.0661, "text": "part 02 of the casting call page rework. Today I “finished” the camera roll and the final screen of the application form as well as I worked out how the application system will be working once we publish."}, {"post_id": 50609, "ts": "2026-08-19T20:28:08Z", "hours": 3.0261, "text": "part 01 of the casting call page rework. Today i worked on the whole logic behind it and how it would make sense the build the form and the questions within."}, {"post_id": 41278, "ts": "2026-08-05T12:09:18Z", "hours": 1.5436, "text": "Made sure that the user really notices that we ARE searching for them"}, {"post_id": 40673, "ts": "2026-08-04T11:08:44Z", "hours": 1.1169, "text": "added UI/UX improvements and lightend up the background so that loading times are reduced"}, {"post_id": 40572, "ts": "2026-08-04T06:48:15Z", "hours": 2.5111, "text": "made the castingCall from prettier and added an external email sender in the background"}, {"post_id": 36241, "ts": "2026-07-28T06:14:20Z", "hours": 1.6653, "text": "figured out the initial Independent design language of Exire which is the first production of PIDEONWASH"}, {"post_id": 33382, "ts": "2026-07-23T08:34:39Z", "hours": 1.6306, "text": "added a new image window view effect (more when the real roll out is)"}, {"post_id": 32947, "ts": "2026-07-22T13:05:06Z", "hours": 0.8131, "text": "Temporär fix für das UX problem bei der characters page auf mobile usage"}, {"post_id": 32393, "ts": "2026-07-21T15:27:58Z", "hours": 0.8236, "text": "Codebase cleanup"}, {"post_id": 32369, "ts": "2026-07-21T14:33:27Z", "hours": 0.6547, "text": "minimal detail clean up, consistent design language"}, {"post_id": 32282, "ts": "2026-07-21T11:03:11Z", "hours": 3.4517, "text": "exire subjects page rework"}, {"post_id": 31319, "ts": "2026-07-19T16:49:37Z", "hours": 0.2792, "text": "made the new stats addition responsive"}, {"post_id": 31300, "ts": "2026-07-19T16:19:32Z", "hours": 1.3314, "text": "stats addition made to the backstage site"}, {"post_id": 31208, "ts": "2026-07-19T12:54:41Z", "hours": 0.6161, "text": "fixed the navigation of the project grid"}, {"post_id": 31148, "ts": "2026-07-19T09:59:01Z", "hours": 5.0719, "text": "a recent part on the homepage and several accessability updates"}]...
|
Title: pideonwash website by @Lexx | Stardance
De Title: pideonwash website by @Lexx | Stardance
Devlogs:
a recent part on the homepage and several accessability updates
fixed the navigation of the project grid
stats addition made to the backstage site
made the new stats addition responsive
exire subjects page rework
minimal detail clean up, consistent design language
Codebase cleanup
Temporär fix für das UX problem bei der characters page auf mobile usage
added a new image window view effect (more when the real roll out is)
figured out the initial Independent design language of Exire which is the first production of PIDEONWASH
made the castingCall from prettier and added an external email sender in the background
added UI/UX improvements and lightend up the background so that loading times are reduced
Made sure that the user really notices that we ARE searching for them
part 01 of the casting call page rework. Today i worked on the whole logic behind it and how it would make sense the build the form and the questions within.
part 02 of the casting call page rework. Today I “finished” the camera roll and the final screen of the application form as well as I worked out how the application system will be working once we publish.
DEVLOG Today I moved everything onto a dedicated Webserver. Consisting of an old Thinkpad running ZimaOS with a dedicated Ubuntu VM for the Webserver. So that i can soon actually start coding the backend logic. I also improved some small things that buged me. As well as a new feature on the hompage.
part 03 of the casting call page rework. today i implemented the feated from my team and redesigned/rethought how will go throu the form and the whole application prozess.
Part 04 of the casting call page rework. today i “finished” the backend. as well as worked on all the function I as an Admin wanna have and how i wanna get notified when someone registers. But i also now build the concept of the logic behind the registration pages.
random bug fixes almost time to get everything on the internet with our own domain just some very wierd and small little bugs along the way today
V1.0 RELEASE DAY!! in the last two to three days we worked on finalizing everything and making sure we can publish everythin. We also made some brand new brand assets. Yesterday evening I finished configuring all the cloudflare tunnels. you can visit our website and everything there is to tell about us on pideonwash.com
Finalising the team page...
|
1792676979.6149807
|
1793281779.6149807
|
|
10259
|
pid simulation by @thegreendino | Stardance
|
thegreendino
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pid simulation by @thegreendino | Stardance
|
1793271158.543686
|
1793875958.543686
|
|
28484
|
picopad by @mabba | Stardance
|
mabba
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: picopad by @mabba | Stardance
|
1793188390.3653524
|
1793793190.3653524
|
|
8641
|
picoboard by @deletethissoon | Stardance
|
deletethissoon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: picoboard by @deletethissoon | Stardance
|
1793267324.2358418
|
1793872124.2358418
|
|
66568
|
pico by @omi | Stardance
|
omi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pico by @omi | Stardance
|
1793101669.9081633
|
1793706469.9081633
|
|
17748
|
pico board by @afia | Stardance
|
afia
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pico board by @afia | Stardance
|
1792767002.0140903
|
1793371802.0140903
|
|
69811
|
pickupthecall by @adicoding-js | Stardance
|
adicoding-js
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pickupthecall by @adicoding-js | Stardance
|
1792860482.934659
|
1793465282.934659
|
|
46859
|
picker placerblob:https://stardance.hackclub.com/5 picker placerblob:https://stardance.hackclub.com/5afedd5a-b2ca-4254-bf11-ed8fe1ffd07c by @caesarm | Stardance...
|
caesarm
|
0
|
45.49
|
0
|
[]
|
[{"post_id": 82225, "ts": "202 [{"post_id": 82225, "ts": "2026-10-24T10:12:30Z", "hours": 9.8669, "text": "What’s new (v3.2?) This round was mostly optimization and electronics. I went back through the design and optimized it, then got most of the electronics into the CAD: the ESP32, the power side, and the E-stop. Electronics The power path is USB-C → PD trigger at 20V → buck down to 12V for the servo rail, with a separate little buck branching off before the E-stop to give the ESP32 its 5V. The E-stop is a latching mushroom button with two NC contacts, one cuts the servo rail, the other tells the ESP32 it got hit. Since it’s normally closed, a broken wire fails safe instead of leaving the arm live. Reality check (again..) The electronics aren’t perfect yet. A lot of the CAD models I pulled for the boards and components aren’t accurate, wrong dimensions, missing mounting holes, simplified shapes, so I already know I’ll have to redo some of the mounts and pockets once the real parts show up. At this point, I was expecting this lol. For now, everything’s placed close enough to plan around, and I’ll measure the real stuff and fix the models when hardware lands. Next up I’m planning to.. … Build! Swap out the inaccurate models once I have the parts in hand (and measure them myself if I have to) Keep chipping away at the tool-head standard and the 1:1/direct drive question, which are still waiting on hardware.. until next time."}, {"post_id": 69645, "ts": "2026-09-17T14:09:33Z", "hours": 9.9503, "text": "Hey v3. This round was all about getting the design closer to the final product, mainly the robot base and the swivel base assembly. A lot more is actually in the CAD now: screws, heat-set inserts, bushings, bearings, and servos. I also designed the parts that mount the main arm assembly to the swivel deck, and fixed a handful of my own design setbacks and assembly issues that only showed up once real hardware was in the model. The base, fully detailed From top to bottom, the stack is: the rotating deck with the mounts for the arm the top cover with the pocket for the J1 servo a hub plate the thrust roller bearing the deep groove ball bearing the 2:1 herringbone gear the housing, with a 608 bearing at the bottom for the gear shaft Every screw that goes into plastic lands in a brass heat-set insert instead of printed threads. PETG/ PLA threads strip after a few cycles, and this guy will probably get taken apart a lot during build prototyping, not to mention strength concerns. Modeling the actual screws also forced me to check head clearance, screw lengths, and whether an allen key or t-handle can even reach them once everything’s stacked. It was boring but worth it. The swivel deck is now the real interface between the base and the arm. The two J2 servos will sit on either side of the deck, and every arm pivot gets a bronze bushing as a cheap, replaceable wear surface. The pins and bushings carry the linkage loads, so the servos only have to supply torque instead of holding the arm up by their splines. I thought of direct driving just now, but it’s currently just a thought. Some setbacks: The coupling with the curved support linkage. After realizing some ROM by messing around a lot with the assembly, realized the front counterweight option I planned for had to go. To add, I moved the mounting towards the inside of the base instead of on the outside, which should give me some more movement liberty in the long term. The actual shape of the robot base. I rounded it out and focused on symmetry so I would have an easier time assembling. Converting to a circular shape and not just the simplest form also opened the gate for more equalized load bearing. Reality check !! I don’t have any of the hardware yet, so everything is designed off online CAD models. From experience, that’ll set me back once the real parts show up.. nothing is ever perfect without real references. Downloaded models are usually nominal or simplified. Heat-set insert hole sizes change by brand. Bearing fits depend on the printer. Some more boring stuff to do with tolerances and measurements So I’m trying to keep the critical interfaces easy to tweak, and once everything arrives I’ll print small fit tests before committing to full parts. Next up I’m planning to.. Give the arms the same treatment: pins, bushings, spacers, fasteners, the works; making it super functional.. and look super wicked. Double-check shoulder screw lengths against the bushing stacks. Update the BOM with the real fastener and insert counts. The tool-head standard and the 1:1/direct drive question are still on the list too, but those have to wait for hardware.. gabagoo."}, {"post_id": 60091, "ts": "2026-09-02T07:30:52Z", "hours": 12.4397, "text": "This is v2. What’s new I designed the full base assembly: outer shell, swivel bearing interface, and rotating deck. The waist joint (J1) driven by a 2:1 herringbone gear reduction off a STS3215. After research, I chose to use these motors with a 345:1 @12V on each, up to four motors total: one for the yaw, 2 powering the shoulder linkage (J2), and another for an eventual 4th DOF (J4) on the toolhead. This tiny motor already has a built in 12-bit encoder, which eliminates the need for an additional electronic part, aka additional point of failure. Nailed down the project’s actual design goal (see below — this matters more than it sounds) Started thinking seriously about tool-head modularity for the business end of the arm The base / waist joint I decided on herringbone gears since they self-cancels axial thrust; a straight spur or single-helical gear at this scale wants to walk sideways under load, herringbone doesn’t (that much). Plus, I’m 3D printing it, so machining manufacturing isn’t a concern (yet). I also use a deep groove ball bearing on the outside for smooth rotation and a thrust roller bearing on top to reduce my axial loads. Initially, I was planning to use opposing tapered roller bearing, but this approach is cheaper (and lighter..). For the 2:1 ratio, my main motivator was to get the least strain (and heat) on the only tiny motor carrying the weight of the entire robot (excluding payload). Using torque calculations, I realized that the 2:1 might be unnecessary and slow, so I already envision converting to a 1:1 or direct drive mechanism after seeing the arm in action. In the next iteration, I’ll tackle the modularity of the bearing base to be able to use an assortment of different sized bearings and sprockets, making it easier for anybody wanting to give the build a shot. My only concern is that this joint could be a silent generator of slop, which can hopefully be mitigated by the servo encoder. While most hobby arm projects chase 6 DOF because that’s what “real” robots have, I’m deliberately not doing that. It’s kind of overdone/ overrated, but it still amazingly effective. This robot has a different purpose. The actual goal: a cheap, consistently precise 3-DOF arm waist, shoulder, elbow, amazing to use by itself but increasingly more capable with added attachments/ accessories.. a bit like an Ender 3..lol. That’s the basis of the palletizing topology this guy was inspired by in the first place; those robots don’t need a wrist full of DOF to do useful, precise, and repeatable work, and one robot can be adjusted/ modified to perform a plethora of tasks. Precision, repeatability, and real world practicality is the actual metric I’m chasing, not DOF count. In my eyes, I don’t want to build this guy and be done with him, I want to get and learn the most of the robot, especially since he’ll be mostly plastic. For modularity, the tool end is the extensibility point Instead of building DOF into the arm, the plan is to build capability into swappable tool heads at the end effector. Same 3-DOF base arm, different job depending on what’s connected on. Next up I’m planning to.. Streamline the tool-head mounting standard design (connection pattern + electrical/pneumatic passthrough). Print the base and validate the herringbone mesh + swivel fit in (preferably in) PETG Get all 3 servos on the bus talking together and do a first coordinated move. There’s also some more stuff, but I can’t fit it all here lol.. until next time."}, {"post_id": 56206, "ts": "2026-08-27T21:08:46Z", "hours": 13.2308, "text": "This is v1 of the overall robot arm build, which is a 3 DOF antagonistic drive pick and placer, inspired by factory palletizing robots. It’s the first physical version of a linkage-driven arm I’ve been working on in SolidWorks. I already got a few issues with this version, just from looking at it on screen, but I’m going to 3D print it to see how it actually behaves in the real world before making changes. Design Approach I used existing automation robot references for primitive geometry; referenced from Fanuc, KUKA, and Panasonic industrial/palletizing robots. These companies have decades of field-proven arm geometry behind them, so rather than guessing at joint offsets and link ratios from scratch, I used their designs as a sanity check for what actually works in practice. I’m already researching their electronic work using different control options like CANBUS and EtherCAT to implement (at least one version) into this robot. For the largest (by volume) components (anything with organic-looking cutouts or holes) I ran SolidWorks’ topology optimization instead of hand-sketching lightening patterns. To make sure my studies were actually improving my design instead of making it worse, I cross referenced different parts across the industry (excavators, cranes, and other heavy equipment, since an excavator is what inspired me to create this robot) and used my knowledge in steel mechanics to see if a part would hold from a glance. I designed with FDM 3D printing’s strengths and weaknesses specifically in mind rather than just printing “machined part” geometry and expecting it not to break. At the same time, I kept track of which components are candidates to eventually remake in aluminum once the design is proven out, so the plastic-specific DFM choices don’t paint me into a corner for a metal version down the line. What’s Next Print V1 and put it through real motion /hand-stress testing to confirm (or rule out) the issues I’m already suspecting. Then, I’ll revise the design based on what breaks, binds, or flexes more than it should have. After, I’ll start on the electronics side, although I’m going in with limited parts on hand, so that’ll be its own challenge."}]...
|
Title: picker placerblob:https://stardance.hackclu Title: picker placerblob:https://stardance.hackclub.com/5afedd5a-b2ca-4254-bf11-ed8fe1ffd07c by @caesarm | Stardance
Devlogs:
This is v1 of the overall robot arm build, which is a 3 DOF antagonistic drive pick and placer, inspired by factory palletizing robots. It’s the first physical version of a linkage-driven arm I’ve been working on in SolidWorks. I already got a few issues with this version, just from looking at it on screen, but I’m going to 3D print it to see how it actually behaves in the real world before making changes. Design Approach I used existing automation robot references for primitive geometry; referenced from Fanuc, KUKA, and Panasonic industrial/palletizing robots. These companies have decades of field-proven arm geometry behind them, so rather than guessing at joint offsets and link ratios from scratch, I used their designs as a sanity check for what actually works in practice. I’m already researching their electronic work using different control options like CANBUS and EtherCAT to implement (at least one version) into this robot. For the largest (by volume) components (anything with organic-looking cutouts or holes) I ran SolidWorks’ topology optimization instead of hand-sketching lightening patterns. To make sure my studies were actually improving my design instead of making it worse, I cross referenced different parts across the industry (excavators, cranes, and other heavy equipment, since an excavator is what inspired me to create this robot) and used my knowledge in steel mechanics to see if a part would hold from a glance. I designed with FDM 3D printing’s strengths and weaknesses specifically in mind rather than just printing “machined part” geometry and expecting it not to break. At the same time, I kept track of which components are candidates to eventually remake in aluminum once the design is proven out, so the plastic-specific DFM choices don’t paint me into a corner for a metal version down the line. What’s Next Print V1 and put it through real motion /hand-stress testing to confirm (or rule out) the issues I’m already suspecting. Then, I’ll revise the design based on what breaks, binds, or flexes more than it should have. After, I’ll start on the electronics side, although I’m going in with limited parts on hand, so that’ll be its own challenge.
This is v2. What’s new I designed the full base assembly: outer shell, swivel bearing interface, and rotating deck. The waist joint (J1) driven by a 2:1 herringbone gear reduction off a STS3215. After research, I chose to use these motors with a 345:1 @12V on each, up to four motors total: one for the yaw, 2 powering the shoulder linkage (J2), and another for an eventual 4th DOF (J4) on the toolhead. This tiny motor already has a built in 12-bit encoder, which eliminates the need for an additional electronic part, aka additional point of failure. Nailed down the project’s actual design goal (see below — this matters more than it sounds) Started thinking seriously about tool-head modularity for the business end of the arm The base / waist joint I decided on herringbone gears since they self-cancels axial thrust; a straight spur or single-helical gear at this scale wants to walk sideways under load, herringbone doesn’t (that much). Plus, I’m 3D printing it, so machining manufacturing isn’t a concern (yet). I also use a deep groove ball bearing on the outside for smooth rotation and a thrust roller bearing on top to reduce my axial loads. Initially, I was planning to use opposing tapered roller bearing, but this approach is cheaper (and lighter..). For the 2:1 ratio, my main motivator was to get the least strain (and heat) on the only tiny motor carrying the weight of the entire robot (excluding payload). Using torque calculations, I realized that the 2:1 might be unnecessary and slow, so I already envision converting to a 1:1 or direct drive mechanism after seeing the arm in action. In the next iteration, I’ll tackle the modularity of the bearing base to be able to use an assortment of different sized bearings and sprockets, making it easier for anybody wanting to give the build a shot. My only concern is that this joint could be a silent generator of slop, which can hopefully be mitigated by the servo encoder. While most hobby arm projects chase 6 DOF because that’s what “real” robots have, I’m deliberately not doing that. It’s kind of overdone/ overrated, but it still amazingly effective. This robot has a different purpose. The actual goal: a cheap, consistently precise 3-DOF arm waist, shoulder, elbow, amazing to use by itself but increasingly more capable with added attachments/ accessories.. a bit like an Ender 3..lol. That’s the basis of the palletizing topology this guy was inspired by in the first place; those robots don’t need a wrist full of DOF to do useful, precise, and repeatable work, and one robot can be adjusted/ modified to perform a plethora of tasks. Precision, repeatability, and real world practicality is the actual metric I’m chasing, not DOF count. In my eyes, I don’t want to build this guy and be done with him, I want to get and learn the most of the robot, especially since he’ll be mostly plastic. For modularity, the tool end is the extensibility point Instead of building DOF into the arm, the plan is to build capability into swappable tool heads at the end effector. Same 3-DOF base arm, different job depending on what’s connected on. Next up I’m planning to.. Streamline the tool-head mounting standard design (connection pattern + electrical/pneumatic passthrough). Print the base and validate the herringbone mesh + swivel fit in (preferably in) PETG Get all 3 servos on the bus talking together and do a first coordinated move. There’s also some more stuff, but I can’t fit it all here lol.. until next time.
Hey v3. This round was all about getting the design closer to the final product, mainly the robot base and the swivel base assembly. A lot more is actually in the CAD now: screws, heat-set inserts, bushings, bearings, and servos. I also designed the parts that mount the main arm assembly to the swivel deck, and fixed a handful of my own design setbacks and assembly issues that only showed up once real hardware was in the model. The base, fully detailed From top to bottom, the stack is: the rotating deck with the mounts for the arm the top cover with the pocket for the J1 servo a hub plate the thrust roller bearing the deep groove ball bearing the 2:1 herringbone gear the housing, with a 608 bearing at the bottom for the gear shaft Every screw that goes into plastic lands in a brass heat-set insert instead of printed threads. PETG/ PLA threads strip after a few cycles, and this guy will probably get taken apart a lot during build prototyping, not to mention strength concerns. Modeling the actual screws also forced me to check head clearance, screw lengths, and whether an allen key or t-handle can even reach them once everything’s stacked. It was boring but worth it. The swivel deck is now the real interface between the base and the arm. The two J2 servos will sit on either side of the deck, and every arm pivot gets a bronze bushing as a cheap, replaceable wear surface. The pins and bushings carry the linkage loads, so the servos only have to supply torque instead of holding the arm up by their splines. I thought of direct driving just now, but it’s currently just a thought. Some setbacks: The coupling with the curved support linkage. After realizing some ROM by messing around a lot with the assembly, realized the front counterweight option I planned for had to go. To add, I moved the mounting towards the inside of the base instead of on the outside, which should give me some more movement liberty in the long term. The actual shape of the robot base. I rounded it out and focused on symmetry so I would have an easier time assembling. Converting to a circular shape and not just the simplest form also opened the gate for more equalized load bearing. Reality check !! I don’t have any of the hardware yet, so everything is designed off online CAD models. From experience, that’ll set me back once the real parts show up.. nothing is ever perfect without real references. Downloaded models are usually nominal or simplified. Heat-set insert hole sizes change by brand. Bearing fits depend on the printer. Some more boring stuff to do with tolerances and measurements So I’m trying to keep the critical interfaces easy to tweak, and once everything arrives I’ll print small fit tests before committing to full parts. Next up I’m planning to.. Give the arms the same treatment: pins, bushings, spacers, fasteners, the works; making it super functional.. and look super wicked. Double-check shoulder screw lengths against the bushing stacks. Update the BOM with the real fastener and insert counts. The tool-head standard and the 1:1/direct drive question are still on the list too, but those have to wait for hardware.. gabagoo.
What’s new (v3.2?) This round was mostly optimization and electronics. I went back through the design and optimized it, then got most of the electronics into the CAD: the ESP32, the power side, and the E-stop. Electronics The power path is USB-C → PD trigger at 20V → buck down to 12V for the servo rail, with a separate little buck branching off before the E-stop to give the ESP32 its 5V. The E-stop is a latching mushroom button with two NC contacts, one cuts the servo rail, the other tells the ESP32 it got hit. Since it’s normally closed, a broken wire fails safe instead of leaving the arm live. Reality check (again..) The electronics aren’t perfect yet. A lot of the CAD models I pulled for the boards and components aren’t accurate, wrong dimensions, missing mounting holes, simplified shapes, so I already know I’ll have to redo some of the mounts and pockets once the real parts show up. At this point, I was expecting this lol. For now, everything’s placed close enough to plan around, and I’ll measure the real stuff and fix the models when hardware lands. Next up I’m planning to.. … Build! Swap out the inaccurate models once I have the parts in hand (and measure them myself if I have to) Keep chipping away at the tool-head standard and the 1:1/direct drive question, which are still waiting on hardware.. until next time....
|
1793159321.499333
|
1793764121.499333
|
|
12606
|
pibble-bot by @brokenCart | Stardance
|
brokenCart
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pibble-bot by @brokenCart | Stardance
|
1792655676.8821642
|
1793260476.8821642
|
|
20367
|
piami by @damn | Stardance
|
damn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: piami by @damn | Stardance
|
1792742076.4003131
|
1793346876.4003131
|
|
70090
|
pia's ores by @Elia_Piagentini | Stardance
|
Elia_Piagentini
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pia's ores by @Elia_Piagentini | Starda Title: pia's ores by @Elia_Piagentini | Stardance...
|
1792958034.8245888
|
1793822034.8245888
|
|
71478
|
pia's ores by @Elia_Piagentini | Stardance
|
Elia_Piagentini
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pia's ores by @Elia_Piagentini | Starda Title: pia's ores by @Elia_Piagentini | Stardance...
|
1793026024.9703934
|
1793630824.9703934
|
|
47049
|
pi-gpt-search upgrade by @Yuzu | Stardance
|
Yuzu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pi-gpt-search upgrade by @Yuzu | Stardance
|
1793166517.9870193
|
1793771317.9870193
|
|
71453
|
pi's by @HELLOPI | Stardance
|
HELLOPI
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pi's by @HELLOPI | Stardance
|
1793015246.901443
|
1793620046.901443
|
|
43701
|
pi hosted website by @axel_swisher | Stardance
|
axel_swisher
|
0
|
1.59
|
0
|
[]
|
[{"post_id": 41779, "ts": "202 [{"post_id": 41779, "ts": "2026-08-06T05:35:28Z", "hours": 0.4469, "text": "dev log 3, i finished port forwarding 80 and did a little more work on the actual website. but I’m running into this problem where the website ‘takes to long to respond’ if i use the URL. it works fine when i connect locally with the pi’s Ip. this leads me to believe that somethings going wrong with either the domain provider or the port forwarding, so i checked on both and the seem fine. im at a little bit of a loss right now"}, {"post_id": 41135, "ts": "2026-08-05T04:36:16Z", "hours": 0.7919, "text": "i bought a domain and attached it to the raspberry pi and also made the pi easier to edit. i downloaded FileZilla before messing around in vs code to through together a little website that i put on the pi so people can see it locally"}, {"post_id": 40569, "ts": "2026-08-04T06:23:57Z", "hours": 0.3503, "text": "i configured my raspberry pi with the imager and added a text file named ‘ssh’. then plugged the pi into the wall and my router before logging into it through windows PowerShell on my computer where i updated the pi, installed and enabled Apache2. this let me test it to make sure the pi was actually hosting something locally so i can port forward it later"}]...
|
Title: pi hosted website by @axel_swisher | Starda Title: pi hosted website by @axel_swisher | Stardance
Devlogs:
i configured my raspberry pi with the imager and added a text file named ‘ssh’. then plugged the pi into the wall and my router before logging into it through windows PowerShell on my computer where i updated the pi, installed and enabled Apache2. this let me test it to make sure the pi was actually hosting something locally so i can port forward it later
i bought a domain and attached it to the raspberry pi and also made the pi easier to edit. i downloaded FileZilla before messing around in vs code to through together a little website that i put on the pi so people can see it locally
dev log 3, i finished port forwarding 80 and did a little more work on the actual website. but I’m running into this problem where the website ‘takes to long to respond’ if i use the URL. it works fine when i connect locally with the pi’s Ip. this leads me to believe that somethings going wrong with either the domain provider or the port forwarding, so i checked on both and the seem fine. im at a little bit of a loss right now...
|
1793235143.3453157
|
1793839943.3453157
|
|
69917
|
pi alphanumeriser by @RishitJain | Stardance
|
RishitJain
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pi alphanumeriser by @RishitJain | Stardanc Title: pi alphanumeriser by @RishitJain | Stardance...
|
1792957831.832811
|
1793562631.832811
|
|
46856
|
pi - web os by @NotSuspiciousProgrammer | Stardanc pi - web os by @NotSuspiciousProgrammer | Stardance...
|
NotSuspiciousProgrammer
|
2
|
9.0
|
24
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-14T00:06:08Z", "hours": 6.0, "multiplier": 3.5, "payout": 24, "blessing": "neutral", "text": "I made a PI-THEMED WEB-OS!! The most challenging part was the script for making “windows” draggable; I had to look through some tutorials for that. Either way, as a professional pi enthusiast, I’m pretty excited for this pi theme! As part of the WebOS2 Mission, I have more than three new features from what I submitted to WebOS1. Some of them include the Settings App, Bible App, and sound effects that say the next digit of pi each time you open/close an app. That part was very fun :P I hope you enjoy my Pi webOS! Please provide feedback on my project, whether you’re a pi enthusiast or not :)", "repo": "https://github.com/kpoovakan/piwebos", "demo": "https://kpoovakan.github.io/piwebos"}, {"ship_num": 2, "ts": "2026-08-11T23:36:39Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a pi-themed “operating system” that can run in a web browser! The hardest part for me was making the windows draggable, since I ran into some bugs even while following the guide. Thanks to some clarification in a W3Schools article, I managed to fix those bugs. I have some features in this OS that the guide doesn’t list, one which is the app that plays music. The other is the helpful text at the bottom of the screen (telling you where the apps can be opened!) that disappears when an app is opened. I enjoyed making this pi-themed “operating system”. I hope you enjoy exploring it!", "repo": "https://github.com/kpoovakan/piwebos", "demo": "https://kpoovakan.github.io/piwebos"}]...
|
[{"post_id": 67747, "ts": "202 [{"post_id": 67747, "ts": "2026-09-13T23:59:20Z", "hours": 1.6781, "text": "I updated my README! Now it has two images, a setup guide, and an organized table for my “apps”. There’s also a features list and a small credits section. I also went through my code and fixed all the bugs I could find. Time to ship!!"}, {"post_id": 66994, "ts": "2026-09-13T00:24:00Z", "hours": 3.9725, "text": "I added more apps to my webOS! Now it has a pi app, games, a web app, an e-mail redirect, a file manager, a notepad, a calculator, a Turbowarp redirect, a music app, YouTube, maps, a flight tracker redirect, a Bible app, and a settings app. The settings app lets you customize things like the time format and sound effect preferences."}, {"post_id": 45470, "ts": "2026-08-11T23:27:57Z", "hours": 0.8372, "text": "I added the content to my three applications! Now, there’s an app with stuff about pi, an app featuring my other coding projects, and a section to play popular classical piano pieces."}, {"post_id": 45452, "ts": "2026-08-11T22:21:00Z", "hours": 1.5489, "text": "I added more CSS styles and customization. I also made the “windows” draggable with JavaScript, and I added buttons to open and close the app placeholders. Next I’ll be adding things to the apps themselves!"}, {"post_id": 45398, "ts": "2026-08-11T20:32:05Z", "hours": 0.325, "text": "Added core code for my pi-themed web OS! I created a blue color palette for the CSS, added placeholder tags for what shall soon become the OS apps, and implemented a pi-themed background."}]...
|
Title: pi - web os by @NotSuspiciousProgrammer | S Title: pi - web os by @NotSuspiciousProgrammer | Stardance
Devlogs:
Added core code for my pi-themed web OS! I created a blue color palette for the CSS, added placeholder tags for what shall soon become the OS apps, and implemented a pi-themed background.
I added more CSS styles and customization. I also made the “windows” draggable with JavaScript, and I added buttons to open and close the app placeholders. Next I’ll be adding things to the apps themselves!
I added the content to my three applications! Now, there’s an app with stuff about pi, an app featuring my other coding projects, and a section to play popular classical piano pieces.
I added more apps to my webOS! Now it has a pi app, games, a web app, an e-mail redirect, a file manager, a notepad, a calculator, a Turbowarp redirect, a music app, YouTube, maps, a flight tracker redirect, a Bible app, and a settings app. The settings app lets you customize things like the time format and sound effect preferences.
I updated my README! Now it has two images, a setup guide, and an organized table for my “apps”. There’s also a features list and a small credits section. I also went through my code and fixed all the bugs I could find. Time to ship!!
Ships:
I made a pi-themed “operating system” that can run in a web browser! The hardest part for me was making the windows draggable, since I ran into some bugs even while following the guide. Thanks to some clarification in a W3Schools article, I managed to fix those bugs. I have some features in this OS that the guide doesn’t list, one which is the app that plays music. The other is the helpful text at the bottom of the screen (telling you where the apps can be opened!) that disappears when an app is opened. I enjoyed making this pi-themed “operating system”. I hope you enjoy exploring it!
I made a PI-THEMED WEB-OS!! The most challenging part was the script for making “windows” draggable; I had to look through some tutorials for that. Either way, as a professional pi enthusiast, I’m pretty excited for this pi theme! As part of the WebOS2 Mission, I have more than three new features from what I submitted to WebOS1. Some of them include the Settings App, Bible App, and sound effects that say the next digit of pi each time you open/close an app. That part was very fun :P I hope you enjoy my Pi webOS! Please provide feedback on my project, whether you’re a pi enthusiast or not :)...
|
1793134072.230333
|
1793220472.230333
|
|
55485
|
physispere by @napoleon | Stardance
|
napoleon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: physispere by @napoleon | Stardance
|
1793163130.700939
|
1793767930.700939
|
|
57473
|
physio therapy by @Guptaji | Stardance
|
Guptaji
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: physio therapy by @Guptaji | Stardance
|
1792709313.6988218
|
1793314113.6988218
|
|
58392
|
physics-minigame by @Rishav | Stardance
|
Rishav
|
1
|
5.0
|
23
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-14T04:19:26Z", "hours": 5.0, "multiplier": 4.24, "payout": 23, "blessing": "neutral", "text": "I had initially thought of creating the game using Godot software, and when the project didn’t work out, I grew frustrated after it actually crashed and I lost some of the resources I had hoped to use. After feeling somewhat bored, I found the motivation I needed to start writing some lines of code in order to develop a new physics minigame using Pygame. After I had completed my first 42 lines of code, I was pleasantly surprised to see my game move on. While pursuing this project, I also discovered just how crucial it is to follow the right indentation rules in Python programming, especially during debugging. Since then, I have successfully finished the game and added several different features to it, such as gravity, bouncing, many different kinds of balls, collision physics, a guessing game and two more minigames called Catch and Dodge.The accomplishment I am most proud of is the sports joke and milestone system. Real-life sports events provide meaning to the various levels of the score. I have tied the scores to various sports milestones such as RCB winning the 49-0 match, Barcelona losing to Bayern Munich, and Germany beating Brazil 7-1. Players will receive a message when a particular score is achieved, thus making the scoring system more interesting and unique. Another challenge was packing the entire game into an executable. I found out that I had two versions of Python installed on my PC. As a result, sometimes, pip and Python would be working with different installations. Even though Pygame was installed successfully, it kept disappearing when I was trying to compile the project. The issue was resolved by specifying the complete path of my command. What started as a failed attempt to make a Godot game turned into a finished Pygame project. While working on it, I have learned a lot about Python, debugging, physics, game making, and even solving the issues of packing the project into an executable.", "repo": "https://github.com/rishavjha8515-hub/physics-minigames", "demo": "https://github.com/rishavjha8515-hub/physics-minigames/releases/tag/v1.0.0"}]...
|
[{"post_id": 67852, "ts": "202 [{"post_id": 67852, "ts": "2026-09-14T04:05:56Z", "hours": 4.3267, "text": "In my second devlog, I have completed the entire game since my previous update. Various features have been implemented such as gravity, bouncing, different kinds of balls and collision physics, as well as determining the time needed for the guessing game, and two mini-games called Catch and Dodge. The most remarkable feature, in my opinion, is the sports joke/milestones system. In this system, I connected my scoring levels to real-life events, such as visiting RCB’s matches (49-10), Barcelona’s loss to Bayern Munich, and Germany’s win over Brazil (7-1). As a result, once a score has been reached, the game shows a related message. Packaging the whole game into an executable file was challenging, as I found out that I had two different Python installations on my computer. As a result, pip and Python send different signals according to the command, and pygame has installed successfully but has disappeared when I tried to build the project. I needed to use the full path to direct my commands to one Python installation."}, {"post_id": 65314, "ts": "2026-09-10T11:41:06Z", "hours": 1.105, "text": "First devlog Was going to make a game on gadot,but was unsuccessful,got fed up and steak was broken and stickers now lost which were upcoming.Gathered the courage to make a write few lines of codes for a new physics minigames i am working on since i was feeling pretty bored.wrote my first 42 lines of code and got this on pygame and learnt a lot of significance of the indentation during debugging"}]...
|
Title: physics-minigame by @Rishav | Stardance
De Title: physics-minigame by @Rishav | Stardance
Devlogs:
First devlog Was going to make a game on gadot,but was unsuccessful,got fed up and steak was broken and stickers now lost which were upcoming.Gathered the courage to make a write few lines of codes for a new physics minigames i am working on since i was feeling pretty bored.wrote my first 42 lines of code and got this on pygame and learnt a lot of significance of the indentation during debugging
In my second devlog, I have completed the entire game since my previous update. Various features have been implemented such as gravity, bouncing, different kinds of balls and collision physics, as well as determining the time needed for the guessing game, and two mini-games called Catch and Dodge. The most remarkable feature, in my opinion, is the sports joke/milestones system. In this system, I connected my scoring levels to real-life events, such as visiting RCB’s matches (49-10), Barcelona’s loss to Bayern Munich, and Germany’s win over Brazil (7-1). As a result, once a score has been reached, the game shows a related message. Packaging the whole game into an executable file was challenging, as I found out that I had two different Python installations on my computer. As a result, pip and Python send different signals according to the command, and pygame has installed successfully but has disappeared when I tried to build the project. I needed to use the full path to direct my commands to one Python installation.
Ships:
I had initially thought of creating the game using Godot software, and when the project didn’t work out, I grew frustrated after it actually crashed and I lost some of the resources I had hoped to use. After feeling somewhat bored, I found the motivation I needed to start writing some lines of code in order to develop a new physics minigame using Pygame. After I had completed my first 42 lines of code, I was pleasantly surprised to see my game move on. While pursuing this project, I also discovered just how crucial it is to follow the right indentation rules in Python programming, especially during debugging. Since then, I have successfully finished the game and added several different features to it, such as gravity, bouncing, many different kinds of balls, collision physics, a guessing game and two more minigames called Catch and Dodge.The accomplishment I am most proud of is the sports joke and milestone system. Real-life sports events provide meaning to the various levels of the score. I have tied the scores to various sports milestones such as RCB winning the 49-0 match, Barcelona losing to Bayern Munich, and Germany beating Brazil 7-1. Players will receive a message when a particular score is achieved, thus making the scoring system more interesting and unique. Another challenge was packing the entire game into an executable. I found out that I had two versions of Python installed on my PC. As a result, sometimes, pip and Python would be working with different installations. Even though Pygame was installed successfully, it kept disappearing when I was trying to compile the project. The issue was resolved by specifying the complete path of my command. What started as a failed attempt to make a Godot game turned into a finished Pygame project. While working on it, I have learned a lot about Python, debugging, physics, game making, and even solving the issues of packing the project into an executable....
|
1793152415.65796
|
1793238815.65796
|
|
26316
|
physical sandbox v1.0 by @Josh001 | Stardance
|
Josh001
|
0
|
0.89
|
0
|
[]
|
[{"post_id": 19026, "ts": "202 [{"post_id": 19026, "ts": "2026-06-30T06:10:10Z", "hours": 0.8922, "text": "4D AI Sandbox Engine 🪐 hey everyone, making my first post here. i’ve been working on a 4d ai sandbox prototype that takes a prompt, uses an llm to compile glsl code on the fly, and injects it straight into a live webgl runtime loop. What is running under the hood? GPGPU pipeline: all particle calculations are offloaded entirely to custom fragment shaders using texture buffers so the cpu doesn’t choke. Live rendering: currently pushing a 128x128 grid (16,384 nodes) completely smooth on localhost. Terminal stream: built a custom execution stream log on the bottom left to track engine boots and live mapping errors. What is the plan for v1.0? I want to turn this prototype into a practical tester for 3d assets. Next steps: Map the gpgpu coordinates into actual solid surfaces using three.js InstancedMesh . Build an exporter node so users can download the generated shapes as standard .gltf files. Finish the sidebar chart to track structural/physics stress metrics over time. P.S. — attached a screenshot of how the dashboard looks right now. let me know if anyone wants to geek out over gpu textures or shader pipelines!"}]...
|
Title: physical sandbox v1.0 by @Josh001 | Stardan Title: physical sandbox v1.0 by @Josh001 | Stardance
Devlogs:
4D AI Sandbox Engine 🪐 hey everyone, making my first post here. i’ve been working on a 4d ai sandbox prototype that takes a prompt, uses an llm to compile glsl code on the fly, and injects it straight into a live webgl runtime loop. What is running under the hood? GPGPU pipeline: all particle calculations are offloaded entirely to custom fragment shaders using texture buffers so the cpu doesn’t choke. Live rendering: currently pushing a 128x128 grid (16,384 nodes) completely smooth on localhost. Terminal stream: built a custom execution stream log on the bottom left to track engine boots and live mapping errors. What is the plan for v1.0? I want to turn this prototype into a practical tester for 3d assets. Next steps: Map the gpgpu coordinates into actual solid surfaces using three.js InstancedMesh . Build an exporter node so users can download the generated shapes as standard .gltf files. Finish the sidebar chart to track structural/physics stress metrics over time. P.S. — attached a screenshot of how the dashboard looks right now. let me know if anyone wants to geek out over gpu textures or shader pipelines!...
|
1793155820.8050008
|
1793760620.8050008
|
|
29461
|
phrieed by @shaikhabdullahwaseem17 | Stardance
|
shaikhabdullahwaseem17
|
0
|
10.27
|
0
|
[]
|
[{"post_id": 43488, "ts": "202 [{"post_id": 43488, "ts": "2026-08-08T19:44:22Z", "hours": 6.6972, "text": "Eyes soared :( BM engine was cracked , as a cherry on top , it’s just the starting - it would take days for one file , but yeah . It should be sweet!"}, {"post_id": 43231, "ts": "2026-08-08T11:33:57Z", "hours": 0.4372, "text": "wrote the read.me file"}, {"post_id": 43215, "ts": "2026-08-08T10:48:31Z", "hours": 1.0442, "text": "just finished the bckend code , it was alot of mass but i hope it will turn out great (i learned how to take an ss)"}, {"post_id": 42815, "ts": "2026-08-07T18:47:17Z", "hours": 1.7981, "text": "repository cleanup + FASTAPI foundation pushed. FIRST STAGE CLEANED UP ( ignore enjoy these random pics in the meanwhile as i cant take ss < ) )"}, {"post_id": 42626, "ts": "2026-08-07T13:29:10Z", "hours": 0.2942, "text": "a context engine for one tap multi step analysis and no ai slop . ik ik its crazy"}]...
|
Title: phrieed by @shaikhabdullahwaseem17 | Starda Title: phrieed by @shaikhabdullahwaseem17 | Stardance
Devlogs:
a context engine for one tap multi step analysis and no ai slop . ik ik its crazy
repository cleanup + FASTAPI foundation pushed. FIRST STAGE CLEANED UP ( ignore enjoy these random pics in the meanwhile as i cant take ss < ) )
just finished the bckend code , it was alot of mass but i hope it will turn out great (i learned how to take an ss)
wrote the read.me file
Eyes soared :( BM engine was cracked , as a cherry on top , it’s just the starting - it would take days for one file , but yeah . It should be sweet!...
|
1792673502.0323372
|
1793278302.0323372
|
|
19713
|
photon projector by @dylpickle | Stardance
|
dylpickle
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: photon projector by @dylpickle | Stardance
|
1793184471.6845946
|
1793789271.6845946
|
|
46263
|
photobooth site by @kaylawong | Stardance
|
kaylawong
|
0
|
0.69
|
0
|
[]
|
[{"post_id": 44448, "ts": "202 [{"post_id": 44448, "ts": "2026-08-10T06:22:54Z", "hours": 0.6919, "text": "I made the base of the website, with some buttons on the side and a way to capture photos. I am still trying to figure out how to get a different photo for each frame on the photostrip, so hopefully I can get to that. I want to later be able to make it so that people can download their photostrip and change the designs as well!"}]...
|
Title: photobooth site by @kaylawong | Stardance
Title: photobooth site by @kaylawong | Stardance
Devlogs:
I made the base of the website, with some buttons on the side and a way to capture photos. I am still trying to figure out how to get a different photo for each frame on the photostrip, so hopefully I can get to that. I want to later be able to make it so that people can download their photostrip and change the designs as well!...
|
1792658954.9436345
|
1793263754.9436345
|
|
28591
|
photobooth by @bella1000 | Stardance
|
bella1000
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: photobooth by @bella1000 | Stardance
|
1792619707.1273947
|
1793224507.1273947
|
|
51275
|
photo to text conveter by @HardikRumandla | Starda photo to text conveter by @HardikRumandla | Stardance...
|
HardikRumandla
|
0
|
0.37
|
0
|
[]
|
[{"post_id": 50151, "ts": "202 [{"post_id": 50151, "ts": "2026-08-19T08:01:27Z", "hours": 0.3675, "text": "new feature in my OS"}]...
|
Title: photo to text conveter by @HardikRumandla | Title: photo to text conveter by @HardikRumandla | Stardance
Devlogs:
new feature in my OS...
|
1792662907.0119274
|
1793267707.0119274
|
|
59185
|
photo effects by hands by @jesus | Stardance
|
jesus
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: photo effects by hands by @jesus | Stardanc Title: photo effects by hands by @jesus | Stardance...
|
1792788438.9354239
|
1793393238.9354239
|
|
31804
|
phoenix by @kaziuuu | Stardance
|
kaziuuu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: phoenix by @kaziuuu | Stardance
|
1793141743.7572787
|
1793746543.7572787
|
|
46590
|
philidor by @neset | Stardance
|
neset
|
0
|
10.74
|
0
|
[]
|
[{"post_id": 75495, "ts": "202 [{"post_id": 75495, "ts": "2026-09-30T09:04:05Z", "hours": 5.7981, "text": "OKAY so i kinda forgot to make updates… but here’s what ive done so far: ran hours of simulations to test draw rates of other existing bots made the framework so i can start training next: train the neural network!"}, {"post_id": 44985, "ts": "2026-08-11T03:31:00Z", "hours": 4.9386, "text": "LOTS of hours put in. in summary: made uci, which allows me to spin up instances of existing chess engines for verification & simulation made fastboard, a fork of pychess’s board class, which is much faster at checking for draws made a baseline “dumb” bot that looks at legal moves and sees which one would increase stockfish’s evaluation of a draw the most, then makes that move. made a game class that allows bots to play against each other. it takes ~70s for a game between the baseline “dumb” bot & stockfish made a pgn class that allows me to save what happened in a game and the result, which will help for data analysis down the line image is of a real chess match that my bots played, saved and then opened in lichess. you can see in the bottom right that it ended in a draw, which is a good thing"}]...
|
Title: philidor by @neset | Stardance
Devlogs:
LO Title: philidor by @neset | Stardance
Devlogs:
LOTS of hours put in. in summary: made uci, which allows me to spin up instances of existing chess engines for verification & simulation made fastboard, a fork of pychess’s board class, which is much faster at checking for draws made a baseline “dumb” bot that looks at legal moves and sees which one would increase stockfish’s evaluation of a draw the most, then makes that move. made a game class that allows bots to play against each other. it takes ~70s for a game between the baseline “dumb” bot & stockfish made a pgn class that allows me to save what happened in a game and the result, which will help for data analysis down the line image is of a real chess match that my bots played, saved and then opened in lichess. you can see in the bottom right that it ended in a draw, which is a good thing
OKAY so i kinda forgot to make updates… but here’s what ive done so far: ran hours of simulations to test draw rates of other existing bots made the framework so i can start training next: train the neural network!...
|
1792670009.065509
|
1793274809.065509
|
|
70065
|
pharmacy management system by @bdeekshaa28 | Stard pharmacy management system by @bdeekshaa28 | Stardance...
|
bdeekshaa28
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pharmacy management system by @bdeekshaa28 Title: pharmacy management system by @bdeekshaa28 | Stardance...
|
1792958005.39337
|
1793562805.39337
|
|
52695
|
phantom by @Oki3505F | Stardance
|
Oki3505F
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: phantom by @Oki3505F | Stardance
|
1792716766.188837
|
1793321566.188837
|
|
59210
|
phaipad by @blueheart | Stardance
|
blueheart
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: phaipad by @blueheart | Stardance
|
1792788706.8915799
|
1793393506.8915799
|
|
14156
|
pew pew 3000 by @Jade | Stardance
|
Jade
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pew pew 3000 by @Jade | Stardance
|
1792691386.6393988
|
1793296186.6393988
|
|
9136
|
petpad by @Arkfiler | Stardance
|
Arkfiler
|
0
|
0.82
|
0
|
[]
|
[{"post_id": 8893, "ts": "2026 [{"post_id": 8893, "ts": "2026-06-14T20:08:03Z", "hours": 0.8222, "text": "finish the PCB of my petpad i did not use it. But its a way to reduce pin.So u can include more part. https://kbd.news/Improved-square-matrix-1415.html"}]...
|
Title: petpad by @Arkfiler | Stardance
Devlogs:
f Title: petpad by @Arkfiler | Stardance
Devlogs:
finish the PCB of my petpad i did not use it. But its a way to reduce pin.So u can include more part. https://kbd.news/Improved-square-matrix-1415.html...
|
1793274936.4338005
|
1793879736.4338005
|
|
4789
|
petos paradox by @carol | Stardance
|
carol
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: petos paradox by @carol | Stardance
|
1792785233.5853693
|
1793390033.5853693
|
|
1366
|
petal by @psm | Stardance
|
psm
|
0
|
4.25
|
0
|
[]
|
[{"post_id": 17676, "ts": "202 [{"post_id": 17676, "ts": "2026-06-28T15:57:14Z", "hours": 0.5539, "text": "it doesn’t seem like i can delete my project but i hate writing devlogs and this whole website is Straight GPT so i quit"}, {"post_id": 4898, "ts": "2026-06-08T13:59:45Z", "hours": 3.6947, "text": "forgot to post a devlog earlier. i’m making Petal because I like Zig’s language features a lot more than JavaScript’s, but I still want to develop for the web efficiently. also, I think a more restricted, compiled language could create smaller & more efficient JavaScript bundles. i currently have a tokenizer, heavily based on Zig’s, with just enough tokens to start working on a parser/AST. corresponding commit: “fix overrunning file buffer”"}]...
|
Title: petal by @psm | Stardance
Devlogs:
forgot Title: petal by @psm | Stardance
Devlogs:
forgot to post a devlog earlier. i’m making Petal because I like Zig’s language features a lot more than JavaScript’s, but I still want to develop for the web efficiently. also, I think a more restricted, compiled language could create smaller & more efficient JavaScript bundles. i currently have a tokenizer, heavily based on Zig’s, with just enough tokens to start working on a parser/AST. corresponding commit: “fix overrunning file buffer”
it doesn’t seem like i can delete my project but i hate writing devlogs and this whole website is Straight GPT so i quit...
|
1792676974.2639084
|
1793281774.2639084
|
|
67066
|
pet-fiyan by @yourfiyan | Stardance
|
yourfiyan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pet-fiyan by @yourfiyan | Stardance
|
1793105620.7705193
|
1793710420.7705193
|
|
52266
|
pet link 11 by @lv11 | Stardance
|
lv11
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pet link 11 by @lv11 | Stardance
|
1792702355.8387685
|
1793307155.8387685
|
|
68770
|
pet hehe by @zaidabajwa | Stardance
|
zaidabajwa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pet hehe by @zaidabajwa | Stardance
|
1793126886.4649763
|
1793731686.4649763
|
|
67416
|
pet by @arhamgangwal | Stardance
|
arhamgangwal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pet by @arhamgangwal | Stardance
|
1793109219.6817095
|
1793973219.6817095
|
|
70983
|
pet by @Rishav | Stardance
|
Rishav
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pet by @Rishav | Stardance
|
1792716427.922639
|
1793321227.922639
|
|
68708
|
pet bird by @Quasar | Stardance
|
Quasar
|
0
|
1.55
|
0
|
[]
|
[{"post_id": 78802, "ts": "202 [{"post_id": 78802, "ts": "2026-10-11T17:17:50Z", "hours": 1.5506, "text": "working on movement"}]...
|
Title: pet bird by @Quasar | Stardance
Devlogs:
w Title: pet bird by @Quasar | Stardance
Devlogs:
working on movement...
|
1793123614.4302604
|
1793728414.4302604
|
|
56812
|
pesticides selector by @sohanv_1619 | Stardance
|
sohanv_1619
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pesticides selector by @sohanv_1619 | Stard Title: pesticides selector by @sohanv_1619 | Stardance...
|
1792680690.1617112
|
1793285490.1617112
|
|
69469
|
pesonal site by @Sepkatt | Stardance
|
Sepkatt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pesonal site by @Sepkatt | Stardance
|
1792853469.3991091
|
1793458269.3991091
|
|
52625
|
personla-website/portfolio by @folk0297 | Stardanc personla-website/portfolio by @folk0297 | Stardance...
|
folk0297
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: personla-website/portfolio by @folk0297 | S Title: personla-website/portfolio by @folk0297 | Stardance...
|
1792716479.0684638
|
1793321279.0684638
|
|
63729
|
personalsite by @Serra00 | Stardance
|
Serra00
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: personalsite by @Serra00 | Stardance
|
1793054923.5009155
|
1793659723.5009155
|
|
54776
|
personalized lightpad by @nacho | Stardance
|
nacho
|
0
|
1.31
|
0
|
[]
|
[{"post_id": 56563, "ts": "202 [{"post_id": 56563, "ts": "2026-08-28T11:25:44Z", "hours": 1.3075, "text": "i builded a simple 9 keys keyboardthat you can configure in the code. i am not sure about the code becuase i don’t know how to code so i spent tomuch timme reading pages and tutorials"}]...
|
Title: personalized lightpad by @nacho | Stardance Title: personalized lightpad by @nacho | Stardance
Devlogs:
i builded a simple 9 keys keyboardthat you can configure in the code. i am not sure about the code becuase i don’t know how to code so i spent tomuch timme reading pages and tutorials...
|
1792803226.8015344
|
1793408026.8015344
|
|
67402
|
personality quiz by @decaydelirium | Stardance
|
decaydelirium
|
0
|
0.93
|
0
|
[]
|
[{"post_id": 76048, "ts": "202 [{"post_id": 76048, "ts": "2026-10-02T05:45:18Z", "hours": 0.9308, "text": "Hey guys, Working on this, I’ve realized how repetitive the code can be. I’ve used methods to print out the answer choices automatically without manually writing the code, however, I’m stuck on how to asses the answer choices I’ll figure that out tomorrow, I’m heading to bed Anyway, that’s all peace"}]...
|
Title: personality quiz by @decaydelirium | Starda Title: personality quiz by @decaydelirium | Stardance
Devlogs:
Hey guys, Working on this, I’ve realized how repetitive the code can be. I’ve used methods to print out the answer choices automatically without manually writing the code, however, I’m stuck on how to asses the answer choices I’ll figure that out tomorrow, I’m heading to bed Anyway, that’s all peace...
|
1793109202.3974981
|
1793714002.3974981
|
|
34309
|
personalised productivity app by @memoriesmemory | personalised productivity app by @memoriesmemory | Stardance...
|
memoriesmemory
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: personalised productivity app by @memoriesm Title: personalised productivity app by @memoriesmemory | Stardance...
|
1792619705.4578507
|
1793224505.4578507
|
|
40826
|
personal_site by @spiderman17 | Stardance
|
spiderman17
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: personal_site by @spiderman17 | Stardance
|
1792777946.0020657
|
1793382746.0020657
|