|
52965
|
octopus search by @willexists | Stardance
|
willexists
|
1
|
4.0
|
31
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-29T18:30:09Z", "hours": 4.0, "multiplier": 8.92, "payout": 31, "blessing": "neutral", "text": "this is a little app i made to solve some problems i’ve had with windows. the file system is too slow, it takes too long to get to the calculator app (exit your app, go to the start menu, search it up, open it, type stuff in…), and spotlight search not being a thing sadly. so i made spotlight search. yay! also you can install the app everything https://www.voidtools.com/support/everything/ to speed up the app, it uses some libraries from it to speed things up :D", "repo": "https://github.com/ooowillexistsooo/octopus", "demo": "https://octo.willexists.space/"}]...
|
[{"post_id": 57536, "ts": "202 [{"post_id": 57536, "ts": "2026-08-29T18:25:03Z", "hours": 0.7278, "text": "it appears i am ready to ship! also i decided to make it frictionless because why not i like achievements it makes me feel like i’ve done something important in my life"}, {"post_id": 57474, "ts": "2026-08-29T17:04:26Z", "hours": 0.3653, "text": "you have no clue how mind-boggling fixing this was i mean it took only like 20 minutes but the research afougiosbgdf"}, {"post_id": 56925, "ts": "2026-08-28T23:07:04Z", "hours": 1.5861, "text": "added file search"}, {"post_id": 52498, "ts": "2026-08-22T17:18:14Z", "hours": 0.8383, "text": "i made a thing so you can search on your computer for stuff and it shows up now"}]...
|
Title: octopus search by @willexists | Stardance
Title: octopus search by @willexists | Stardance
Devlogs:
i made a thing so you can search on your computer for stuff and it shows up now
added file search
you have no clue how mind-boggling fixing this was i mean it took only like 20 minutes but the research afougiosbgdf
it appears i am ready to ship! also i decided to make it frictionless because why not i like achievements it makes me feel like i’ve done something important in my life
Ships:
this is a little app i made to solve some problems i’ve had with windows. the file system is too slow, it takes too long to get to the calculator app (exit your app, go to the start menu, search it up, open it, type stuff in…), and spotlight search not being a thing sadly. so i made spotlight search. yay! also you can install the app everything https://www.voidtools.com/support/everything/ to speed up the app, it uses some libraries from it to speed things up :D...
|
1793480083.2822053
|
1793566483.2822053
|
|
43736
|
od by @davidcourseshub | Stardance
|
davidcourseshub
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: od by @davidcourseshub | Stardance
|
1793235189.9982862
|
1793839989.9982862
|
|
21598
|
oesk by @arch64 | Stardance
|
arch64
|
0
|
5.25
|
0
|
[]
|
[{"post_id": 13294, "ts": "202 [{"post_id": 13294, "ts": "2026-06-21T19:21:34Z", "hours": 3.3231, "text": "Today i worked on more IDS features and a terminal cli with an ai integrated to it to access the tools and added kubernetes, docker crio, system services, and custom service status monitoring status and logs combined all smartly managed when a sudden change, shutdown or not expected logs happen it gets sent to AI to examine it and then reported back."}, {"post_id": 11564, "ts": "2026-06-18T21:03:22Z", "hours": 1.9233, "text": "🚀 Devlog #01 | Building oesk SIEM : An Autonomous, AI-Driven SIEM Agent in C++20 Hey everyone, I have been working on a root-level intrusion detection and security monitoring agent, designed for linux environments. The goal is to move away from rigid, signature-based detection and leverage low-level kernel diagnostics coupled with asynchronous AI reasoning. Here is a quick breakdown of what’s currently under the hood:1. Low-Level Process Integrity Monitoring Running with strict root privileges, oesk constantly audits the /proc filesystem. It inspects symlinks for all active processes. If a binary is modified in memory or removed from the disk while running, Linux appends a “deleted” marker to the symlink. The agent catches this instantly, flagging potential process masquerading or hijacking attempts. Asynchronous Gemini 3.5 Flash Integration To prevent security telemetry from blocking the main system threads, all AI operations run completely out-of-band using C++20 standard concurrency (std::async/std::future). When an anomaly is triggered, the structured payload is pushed to the Gemini 3.5 Flash model. Safety Settings Bypassed (OFF): Crucial for security tools, ensuring the LLM doesn’t falsely censor raw attack logs or exploit footprints. Reasoning Level Set to MEDIUM: Forces the model to perform deeper, step-by-step chain-of-thought analysis before rendering a verdict. Grounding via Google Search: The AI can actively execute live web queries to verify emerging zero-days or check known malicious IP threat intelligence. Real-Time Telemetry & Next.js Synchronization The agent features a dynamic terminal logger that formats alert streams with ANSI escape colors mapped to the AI’s determined severity level (LOW to CRITICAL). Simultaneously, a background worker thread leverages libcurl to pipe the structured JSON results to a remote Next.js dashboard endpoint via non-blocking POST requests for live visualization. In the coming days i want to switch to local LLM models for privacy."}]...
|
Title: oesk by @arch64 | Stardance
Devlogs:
🚀 Dev Title: oesk by @arch64 | Stardance
Devlogs:
🚀 Devlog #01 | Building oesk SIEM : An Autonomous, AI-Driven SIEM Agent in C++20 Hey everyone, I have been working on a root-level intrusion detection and security monitoring agent, designed for linux environments. The goal is to move away from rigid, signature-based detection and leverage low-level kernel diagnostics coupled with asynchronous AI reasoning. Here is a quick breakdown of what’s currently under the hood:1. Low-Level Process Integrity Monitoring Running with strict root privileges, oesk constantly audits the /proc filesystem. It inspects symlinks for all active processes. If a binary is modified in memory or removed from the disk while running, Linux appends a “deleted” marker to the symlink. The agent catches this instantly, flagging potential process masquerading or hijacking attempts. Asynchronous Gemini 3.5 Flash Integration To prevent security telemetry from blocking the main system threads, all AI operations run completely out-of-band using C++20 standard concurrency (std::async/std::future). When an anomaly is triggered, the structured payload is pushed to the Gemini 3.5 Flash model. Safety Settings Bypassed (OFF): Crucial for security tools, ensuring the LLM doesn’t falsely censor raw attack logs or exploit footprints. Reasoning Level Set to MEDIUM: Forces the model to perform deeper, step-by-step chain-of-thought analysis before rendering a verdict. Grounding via Google Search: The AI can actively execute live web queries to verify emerging zero-days or check known malicious IP threat intelligence. Real-Time Telemetry & Next.js Synchronization The agent features a dynamic terminal logger that formats alert streams with ANSI escape colors mapped to the AI’s determined severity level (LOW to CRITICAL). Simultaneously, a background worker thread leverages libcurl to pipe the structured JSON results to a remote Next.js dashboard endpoint via non-blocking POST requests for live visualization. In the coming days i want to switch to local LLM models for privacy.
Today i worked on more IDS features and a terminal cli with an ai integrated to it to access the tools and added kubernetes, docker crio, system services, and custom service status monitoring status and logs combined all smartly managed when a sudden change, shutdown or not expected logs happen it gets sent to AI to examine it and then reported back....
|
1793368477.5384185
|
1793973277.5384185
|
|
20214
|
off grid lora mesh node by @Abhay | Stardance
|
Abhay
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: off grid lora mesh node by @Abhay | Stardan Title: off grid lora mesh node by @Abhay | Stardance...
|
1792784952.5413837
|
1793389752.5413837
|
|
35255
|
off road autonomous rc car by @mateomatt360 | Star off road autonomous rc car by @mateomatt360 | Stardance...
|
mateomatt360
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: off road autonomous rc car by @mateomatt360 Title: off road autonomous rc car by @mateomatt360 | Stardance...
|
1793270886.9000666
|
1793875686.9000666
|
|
60637
|
off the map by @Lucashble | Stardance
|
Lucashble
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: off the map by @Lucashble | Stardance
|
1793036924.5277357
|
1793641724.5277357
|
|
21987
|
off-road autonomous robot by @leila | Stardance
|
leila
|
0
|
173.99
|
0
|
[]
|
[{"post_id": 79978, "ts": "202 [{"post_id": 79978, "ts": "2026-08-13T00:00:00Z", "hours": 7.0, "text": "ok so from here on we just started placing the robots at different places trying to show what they could do if the washboard didnt always destroy their runs Exhibition 1: Team Big Fish and THE HILL … for our first exhibition, the other team set up the robot before the hill and took some stabs and speeding their way over it. in the end, none of the attempts made it, but i have video of the third one where they got so close that one of the wheels drove onto the other side of the hill and kept the robot there, until their driver let go of the throttle and let it down. it was super cool!! Exhibition 2: Team 10 and THE HOOK finally it was time for my teammates magnum opus of the past two weeks to be revealed and truly tested, and that of course was THE CLIMB!!!! and by the climb i mean a big pink plastic hook on the end of a measuring tape roll taken out of its case that we lovingly call “the bomb” (because it WILL explode if not handled properly). like i said a while ago though, the climb didnt have enough force to pull up the robot, but thats fine! theres still partial points for hooking, so all this exhibition really was was the hook rising at an almost comedically slow pace, before i carefully drove the robot over to the bar (as to not fold over the tape from the velocity) and gingerly brought the hook down on it. and everybody clapped! Exhibition 3: Team Big Fish and THE DUNK aka they used their shooter. it was super cool actually! they have a whole system with conveyor belt squeezing balls forward from above a slanted metal sheet, with flywheels at the end that can block balls for storage purposes until the gate is opened and the conveyor belts are forwarded to shoot them! it was suprisingly good and consistent, shooting from behind the second-to-last line. i wish we could do that… its okay they dont have a climb so we’re better and that was pretty much it! this experience has been so incredibly helpful for my learning and for me in general, and it really was(😢) one of the most fun times of my life. i dont even think i could near catalogue how much fun i had and how many things i learned. i really cant put it into words. thank you lucas, carlos, jade, maanya, patrick, alfonso, and trina for making this what it was, and of course thank you big zrl for sponsoring my attendance. if you’re reviewing this project, i recommend looking at devlogs further down if you’re missing context. the photos should hopefully help see the progression as well (if i can get those uploaded…) i leave you with 3 photos: the state of the robot right before i turned it off for the last time, the absolute state of our whiteboard after we used for brainstorming, and a last minute photo of the hallway i knew i would never walk again. happy hack clubbing!"}, {"post_id": 79977, "ts": "2026-08-12T00:00:00Z", "hours": 7.0, "text": "ladies, gentlemen, and my beautiful enbies * ITS TIME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *(ok so i admit this entry was written days later cause i had to go to school next day so my memory is foggy but! its still cool :3) basically the first half of the day (before everyone came in) was spent finalizing somethings we’d waved off earlier, like cable management and wiring in general, especially the motor wires were dangerously close to the suspension rods and a bunch of other things like that power and attaching the battery, since we really needed to keep the batteries charged properly to prevent the pi being underpowered and the battery needed to be held on with something a little less flimsy than straight up velcro 😭 THE GOD DAMN SET SCREWS HOLY TUNA THESE THINGS WILL NOT STAY TIGHT NO MATTER WHAT WE ARE NEVER GOING UP THAT HILL AGAIN ISTG (subtle foreshadowing) keeping the kill switch always accessible from the top and attaching it with a little more than tape and prayers making sure the wheels are attached properly and wont jut out weirdly as it has in the past, throwing the driving off balance as it getting the climb to actually work which is lowk a lost cause but we ball praying theres something we can do about the intake situation 😭🙏 among much more of course, the time eventually came when people started arriving (like alfonso, shoutout my goat) including a whole lot of parents. we started by showing them our robots as we made some final tweaks, like making sure the pi wouldnt fall off of our beautiful, incredibly complex attachment scheme (velcro mounting strips) until it finally happened… COMPETITION START‼️ so the way this ended up going is that each team alternated runs, usually getting progressively further (keyword usually …) Run 1: Team Big Fish (not us) their first run didn’t go too bad!! their ball intake was suprisingly functional (and by suprisingly i mean at all) (better than us tho) and they were almost able to get around the cones autonomously without hitting one! however, when it came to the washboard, it didnt really work out… their bot very quickly got stuck on a pipe and was ill equipped to unstuck itself, ending the first run. Run 2: Team 10 (US!!!!!!!!‼️!!!!!) also not too bad somehow!!!!!!!!!! of course there was no ball intake so we just drove over them, but we were able to slowly but surely get past the slalom with wide margins and very very slow turns in place. as for the washboard though, our run wasnt much better… i took the robot off of the ramp at the start rather fast, making sure to turn up the throttle limit in the hopes it would get us over a few obstacles. spoiler alert: it didnt. we pretty quickly just crashed into a full cinder block, bending the sheet metal base and unsurprisingly making it hard to continue the run! but whatever it was not too bad for a first attempt Run 3: Team Big Fish this one was probably their best! the ball intake was great, and they were able to carry them all through a perfect no-hit slalom! unfortunately, a similar fate to last time met them at the washboard. third times the charm hopefully… Run 4: Team 10 although the robot was slightly banged up now, it was still totally good to go! this slalom attempt was not nearly as graceful, and that certainly applies to the washboard too: i turned up the throttle limit more on the ramp and really just sent it, only to get stuck on top of that cinderblock instead of past it. fun stuff!"}, {"post_id": 79976, "ts": "2026-08-11T00:00:00Z", "hours": 7.0, "text": "and i call it frickmas cause THE COMPETITIONS TOMORROW OMG OMG OMG OMG OK SO here’s what on the agenda: making sure the set screws dont destroy themselves on the field getting the climb attached and making sure it maintains enough torque to actually pull the robot figuring out some sort of system for intake lining up all the suspension to prevent it from getting stuck, damaging the metal, or crapping out on the washboard section making sure the pi mount, buck converter, code, suspension actuation, and every other subsystem actually work testing!!! lots of testing of all of everything!!!!!!! for the first one, my partner had already spent so long on the set screws so some testing was all it took to see that they were fine, and that was enough cause they were not really going to get any better. my other partner finally got around to actually finishing up the climb and attaching it to the front of the bot. good news: it hooks! bad news: it doesn’t even remotely pull back! luckily, the rules still gove points for hook but no lift, so we decided to leave it there since his effort could be best spent elsewhere with this little time left the intake system was determined to be pretty much a dud by the end of the day, cause of course cardboard couldn’t really carry anything, and we didn’t have time to design something better since the last system fully failed lining up the suspension was pretty easy, just took a bit of manual adjustment and a good amount of testing on the field each of these were kind of annoying to address but i have a feeling itll be rather important at the end of the day (which is basically how long until handling all the wiring and subsystems took us) lastly for the testing, we just drove like a bunch of times! honestly the runs went like okayish ig, we rarely made it past the washboard and of course NEVER made it over the hill ever since we did it first a couple weeks ago. otherwise though, the robot was stable the entire time and didnt have any weird glitches or hardware malfunctions (thank god we taped down the battery this time) so we were good(ish) to go! below is basically what our final robot is gonna look like (minus the climb)"}, {"post_id": 79974, "ts": "2026-08-10T00:00:00Z", "hours": 7.0, "text": "OKAY it is time to get down to business we do NOT have much time. first order of business was looking at the TPU wheels reflect printed! they had come in while i was gone, and compared to our flywheels they were actually suprisingly good (although they lowk had their heads blown shmoove off (the tops were weirdly disconnected and ripped off)). most of all, our wheels were much too stiff and theirs were relatively soft, so we decided to go with theirs. we’d also gotten metal parts back from lucas; unfortunately, lucas’ parts were cut kinda incorrectly and for whatever reason the machine shop didn’t make them!! so, i spent today primarily trying to figure out how to do intake while one partner was working on (OF COURSE) retightening and loctite-ing the set screws and the other partner was working on finishing/testing the climb with a smaller motor he bought online over my hiatus. and by figuring out the intake, i mean taping a cardboard box to the bottom of the robot and letting it flap down while desperately PRAYING that the balls go in. i was also driving around a bunch trying to figure out why the robot was still really struggling to take turns, especially on the foam. eventually i had the insight that the friction on the wheels was simply too much, and Lucas came up with the idea of wrapping tape around the wheels to reduce it!! after that it was insane how well it drove and took turns, especially off of the foam floor. i lowk drove it around for like 45 mins straight it was so insanely fun to see something we made acting like a real machine, cause it was driving at a quality i could actually expect in like a real product! it was so cool and gratifying :3 of course i forgot to get a picture of video of it, which i have a feeling im gonna regret…"}, {"post_id": 79971, "ts": "2026-08-04T00:00:00Z", "hours": 7.0, "text": "okay so like i said last entry ill be leaving for three days, which means that i had to finish up some things today! i decided at this point that we were not going to able to mount a plate in the front for the intake (rip that idea and the whole bunch of filament we wasted on it 😭) so i spent the entire day pivoting on that idea and making the articulated suspension!!!! this was a really cool idea i talked with carlos about for like an hour, although we were thinking about only servos for suspension. this time around, i modified those servo mounts to place the head of of the edge of the main plate and used a bit of kevlar string Trina donated (ty Trina!) and tied it to the servo head and around the wheels hub. this means that when the servo is drawn up, the string pulls on the wheel, compresses the spring, and brings the robot down. for context, there is an 8 inch height requirement* that we had yet to succesfully get under. by that i mean the robot was like 11in. so, to get around that, these servo mounts could effectively deactivate the suspension at will, not only making driving more stable in the ball collection phase, but also actually getting under the height requirement! (since it was only a starting height requirement, we were allowed to expand after) anyways i made one mount, tested it, it didnt fully work, designed another and printed two of them, codexed while that was printing, tested one (it worked perfectly), printed 2 more, codexed the code for different states and positions for the servos and configuration stuff ofc, assembled the rest, tested all 4 of them out at the same time, actually tied good knots, and it was done by the end of the day!! im really proud of finishing this subsytem in one day before i left, it was suprisingly fun to see the robot dancing and doing pushups as it drove. and honestly, i think today really gave me that feeling of how incredible it is to see something like this just come to life, the way i feel when i make progress on a good coding project. i lowk want a 3d printer now… maybe that radish jam money could really come in handy……."}, {"post_id": 79970, "ts": "2026-08-03T00:00:00Z", "hours": 7.0, "text": "i am gonna be gone wednesday, thursday, and friday this week due to my schools orientation happening right before CalTech’s WiSTEM (which i am indeed going to :3), both of which are on weekdays. thus, with the intake challenge pushed even further to this wednesday (marking a full week delay), i will need to spend some time getting our existing systems to a good place and helping my partners with whatever they need over today and tomorrow before im gone. that being said, we did very little locking in today (hence calling it the dawn) because we had both a speaker and a tour!! Will Heltsley, former VP of Propulsion of SpaceX and an insanely knowledgable engineer, talked to us about different engineering concepts and some strategies for finding a stable job and a community of like-minded nerds that are fun to work beside. i asked a few questions about working with teams (because this program has shown me that it’ll be a very valuable skill to learn), especially since Will has done everything from working on a 3-person team to managing a group of 350 engineers. he was really helpful!! we also got to tour another startup, Forge Atomics, and it was awesome to see the inner workings of a company that is just getting of the ground! they had a really cool concept and i loved their mission, which in talking to one of the co-founders (Rex the goat) i learned was one of the most important things in finding a team that is going to work well: your missions need to align. also i learned from both mentors that, unless you plan on doing something research heavy like quantum computing, you should NOT get a PhD. guess what i want to do!"}, {"post_id": 79969, "ts": "2026-07-31T00:00:00Z", "hours": 7.0, "text": "okay this day was an experience fs. the start of the day was relatively normal, i was working a bit on ball detection while my partners assembled the intake/outtake thingy, and all of a sudden the pi turns off . this happened before when the power draw was low and peripherals were connected, so i just took out the camera and turned it on. yup, works fine. ok so lets plug the camera in while its on and it turns off . odd, looks like its probably some random bug or connection issue, so i just unplugged it, reseated it, and restarted the Pi. and it doesnt even turn on. ok, well theres another port. idk whats going on, but maybe thatll fix it? nothing. theres spare cables, lets try those ig? nope. ok what the hell the camera must be broken, so lets try a spare camera. doesnt turn on. ok what the actual ****???? lets try it on their robot and then theirs doesnt turn on either . at this point i am positively destroyed and fuming, luckily we have some very good food coming from a place nearby called the melt, so hopefully having a nice gooey cheesesteak can help me calm down, lock in, and figure out whats going on. big mistake. an hour passes. the adults have put on a movie, a fast and furious movie. you dont feel delirious, nor subdued, but simply off. its almost as if you are both more aware of your environment and slowly less aware of yourself. an hour passes. the car noises are still going. focus was a lost cause. one adult is stretching on the floor. the other is sitting at a table, still watching. you’re on the floor too. you’re not getting anything done. it was a lost cause anyways. an hour passes. carlos is sleeping on the slanted wooden plank of the hill. jade is lying on the floor and staring straight up. somehow your partner is locked in. the car noises continue. you are two inches away from meeting God, before you start laughing. shes laughing too, as well as your partner. presumably at carlos. sanity was a lost cause, and you lost it four and a half hours ago. cant believe its somehow 3:30. long story short, we slowly went insane with tokyo drift in the background as i pulled my hair out from the pi frying our cameras and the movie making it hard to focus, while one of my partners locked in to an unprecedented level, one just watched the movie casually, and the rest of us went crazy for no particular reason at all. this was a wild day (hence why im writing this the day after) never eating at the melt again bruh 😭"}, {"post_id": 79968, "ts": "2026-07-30T00:00:00Z", "hours": 7.0, "text": "I FORGOT TO PUT THE PRINT PLATE IN THE PRINTER YESTERDAY GOD DAMN IT 😭😭😭😭😭 its fine. ok so today was generally pretty mundane BUT!!! WE DROVE UP THE HILL LITERALLY ONCE!!!!! just on a whim my partner decided to go full power up the hill after my other partner had just loctited every set screw to see if we could make it, and we did!!!!!!!!!!!!!!!!!!!!!! …….unfortunately……… nobody filmed it…………………………….. -# god damn it…………………………. it was really cool though! i think it represents that we’re really nearing a functionally useful robot and that were actually overcoming the challenges that have plagued us for like weeks anyways heres a picture of our bot looking super duper cool"}, {"post_id": 79967, "ts": "2026-07-29T00:00:00Z", "hours": 7.0, "text": "so my GOATED teammate whose shall not be named figured out the TPU problem: the printer just wasnt strong enough to feed it in! i honestly have some doubt that that was THE problem, considering how easy the solution is (just unspool a bunch of filament onto the ground), but whatever we ball‼️ anyways the first third of today was spent working on that servo mount and arms CAD file i mentioned before as my partners finished up cutting the shafts and legs for the new tensioners. i also got the tensioners printed, but that was pretty quick since its just a few ~1x0.5” pieces the second third was spent doing the assembly for all the pieces, since we had to take apart each leg completely, and then go down the assembly line to put it together. i was responsible for putting on the tensioners and then the motors with these really handy alligator clips Carlos graciously gave us that allowed me to get short screws into holes that were far into the leg. then, once the motor is attached, my partner would attach the wheel and get the belt on there. i think he used some like dark magic cause the belt was really hard to get on before it was tensioned, idek how he did it now… my other partner would then put on the insert, bearings, and shaft for attaching the leg to the chassis. once we were done, we all spent some time getting the legs on the chassis but we didnt finish. i rushed to start the flywheel TPU print we designed a while ago before we left and spent the rest of the day on… THE SPACE X TOUR!!!!!!!!!!!!!!!!!!!!!!!!!! we got to go to spacex and have a little tour with one of patricks friends!!!!!!!!!! it was really really really cool, the facility was huge and we such a bunch of fuel tanks, satellites, an engine actively being built, and a phased antenna array. that last thing nerdsniped me so hard, and because Simon (one of our “tour guides”) was an engineer that worked on the Starlink user terminals (which also had the same type of antenna array as the Starlink satellites) i was able to ask a bunch of questions about it. apparently, they both have a bunch of antenna put together and arranged such that, by controlling the phase of the signal coming through each of the ~50 antennae, can focus on a narrow beam of EMF waves and effectively filter out signal to only a specific Starlink satellite in the sky. super cool!!!! no photo(s) cause we weren’t allowed to take any but its chill"}, {"post_id": 79966, "ts": "2026-07-28T00:00:00Z", "hours": 7.0, "text": "the TPU arrived! guess what though: it lowk doesnt work with the X1c (our printer)!!!!!!! we refined the design for the flywheel a bit, but after figuring out the TPU settings in the printer, our test prints didn’t work at all. at some point, it just seems to run out of filament (usually before the first layer finishes) and leaves these dots of plastic where its supposed to be entirely filled in. no TPU ig!! my teammates spent most of the day figuring out where to cut holes for the tensioner and then actually drilling those holes for the eventual assembly (prob tomorrow). it looked really sucky cause the hacksaw is time-consuming and lowk rather annoying, especially when we need to cut 3 shafts into like 12 pieces, so thank you teammates that was very nice 🙏 i spent the whole rest of the day on the CAD for the articulated arms that we’re gonna have in front and on top of the entire robot, and i designed a servo mount that’ll keep the servos attached to the robot at the exact height we need them to be to make a plate that hits the ground, settles at a nice angle, holds the flywheels, and all the while still fits on the print bed. i tried to print one of those mounts but after like 5 prints that failed on the first layer, the only succesful print ran out of filament on the second to last layer 😭 its lowk chill though cause it looks kinda cool so im gonna keep it attached is the lowk awesome lowk cooked servo mount that i lowk made and printed lowk"}, {"post_id": 79965, "ts": "2026-07-27T00:00:00Z", "hours": 7.0, "text": "GUESS WHAT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! the belt is skipping. turns out the belt needs to be tensioned to not yknow skip horribly. any real torque that the wheel experiences back on it, including the torque inherently present in turning with tank drive (which is really high cause we have really grippy wheels and their laid out in a rectangle), makes the belt slip on the teeth and not drive the tire at all, leaving the motor spinning but the robot not moving. basically, we’re gonna need a tensioner to slot into the legs. in other news, we still have to get intake/outtake working by friday hopefully. i’ve ordered TPU filament online and got on of my teammates to start on a design for a flywheel that has a PLA hub and TPU tire, maybe we’ll print it tomorrow? although one good thing about this is that the robot looks super cool awesome now (source: see below)"}, {"post_id": 79964, "ts": "2026-07-24T00:00:00Z", "hours": 7.0, "text": "the parts came! literally all of today was spent assembling the drive system as my partners were drilling the holes and cutting the shafts for the wheels, pivots, and spring dowels. we’ve unfortunately found out that the belt drives skip kind of a lot, so hopefully this doesn’t cause issues with driving under torque when we get to that… (i swear if this is foreshadowing) we also went out to Reflect Orbital today!! seeing the mirrors was incredibly cool, and the material they made it out of felt really interesting. something about its very small thickness (2.8 microns!!) made it feel like it was barely on your finger if you weren’t looking at it. In addition, I talked to one of the software engineers (shoutout Alfonso) about how they get the software done, including things like: Double buffering updates (seemingly called ABing) to make sure that no update permanently breaks the system Using the Yocto project to make a custom Linux kernel for their embedded systems Monolithic applications vs. a more service based approach that also goes hand in hand with… Error handling and making sure that something like an illegal instruction won’t crash your expensive space satellite Testing with the ground-sat (all of the components on the real satellite connected together on a table in a room) and an approach that involves uploading the changed code to the ground-sat every night and running a whole test suite to make sure none of the changes broke anything and that they (hopefully) achieved what they were written for overall it was pretty damn cool you should check out Reflect :3 below is one of the legs, and as you can see theres a whole belt going from the motor to the wheel!"}, {"post_id": 79963, "ts": "2026-07-23T00:00:00Z", "hours": 7.0, "text": "guess what THE BEARINGS AND SHAFTS GOT DELAYED!!!! YAAAAAAAAAAAYYYYY its fine. we spent today CADing and printing new designs for both the leg inserts and one piece of the rod-ends, and i think they’re in a pretty good place (for not having the actual components needed). I also did some testing with the ball/cone detection and came to the conclusion that it simply sucks and just isn’t good enough, so I got Codex to give me suggestions for an overhaul and I picked which approach would be the best to go for. The demo it produced for me using new shape detection and differentiating objects from its surroundings (in camera space) was so bad that I’ve decided on a completely different approach altogether: ML!! I got it to do another overhaul that would add a mode to the existing code that allowed camera snapshots to be taken and put in a folder with a press of a button on the controller. Then, it made a tool that could be run on my laptop that would bring the images up one by one, I would mark balls and cones on there, and then that data would be used to train an ONNX model (with ROCM acceleration on my Radeon 890M iGPU, of course) that could then be uploaded onto the Pi and ran as the new detection backend!! we’ll see if it works, cause I did all this at the end of the day and had no time to gather training data (of course i came up with this after two days of having very little to do)."}, {"post_id": 79949, "ts": "2026-07-22T00:00:00Z", "hours": 8.0169, "text": "7/21 - EVERYTHING GOT DELAYED VERY BAD NEWS: every single thing we needed to order for the drive train and suspension got delayed by a day 😭 anyways completely unrelated but the second competition is being moved to thursday, cause we cant drive through the course with literally 0 suspension the first 2 hours of today was spent rushing out an onshape sketch to get our metal legs cut by Lucas cause he (reasonably enough) wanted the drawing by 11 before he left the shop. i had to remember how to do drawings, with a lottt of help from carlos. unfortunately, i forgot the holes for the spring on the top so we’ll have to figure that eventually. i also forgot to put holes that would make screwing in the motor remotely possible but lucas the GOAT put those in for us. could not appreciate it more we might be lowk cooked now, cause the bearings say they’re gonna arrive thursday night so we may not even have the robot driving again until next week 😭😭 that being said we ball‼️ also ill be posting a devlog every weekday now cause i need to journal every day anyways attached below are 2 of the legs we got cut with the motors on them"}, {"post_id": 79948, "ts": "2026-07-22T00:00:00Z", "hours": 0.5692, "text": "7/22 - not much we can do about it much of today was spent moping about how everything would be arriving tonight (and of course the belts are arriving tomorrow night, one of the parts that is literally necessary to drive the thing at all). so much of today was spent just trying to design, cad, and otherwise figure out details for the legs before we actually had the components necessary to make them. i spent some time with one of my teammates figuring out where specifically the springs for the legs are gonna go, and he made a quick 3d printed rod-end that’ll hold in the shaft that acts as the spring dowel. we also planned out where we could put the legs’ pivot point on the chassis and just generally planned every element of assembly that we could. this also involved figuring out last second that i had no idea how we were gonna mount the springs and chassis on the leg at all and that my teammates didn’t know too much either, but its cool we figured it out and started the print by the end of the day 👍 attached: us figuring out where we’re gonna mount both the leg and the spring on the chassis and me drawing the top view of all the drive train stuff going on inside the leg (ignore my horrible handwriting its the board i swear)"}, {"post_id": 79960, "ts": "2026-07-20T00:00:00Z", "hours": 7.0, "text": "almost all of today was spent discussing and weighing different suspension designs and drive train implementations, culminating us in finally buying some parts and basically finishing out our $1000 budget from the start of the program to the end of this week. we settled on the 4 independent legs early, so the options were between: mounting the motor on the chassis on the same pivot point as the leg itself mounting the motor on the chassis and using a u-joint articulated axle mounting the motor high up on the leg and using a belt drive eventually we arrived on that last option because the other ones didnt really pose a benefit that was worth the complexity they would introduce (especially the first one) towards the end of the day, we ordered all the parts we needed to install it hopefully over tomorrow and wednesday also! we finished printing the finalized(…) wheel design so now we have four rigidly attached and bead-locked wheels+tires!! turns out the robot is like significantly faster than we thought so uhhh throttle limit is gonna have to be pretty low for a bit. below is a sample of our mad drawings (mostly mine 😭) trying to figure out how the hell this thing is gonna work"}, {"post_id": 79959, "ts": "2026-07-17T00:00:00Z", "hours": 7.0, "text": "my day was spent entirely on programming two things: the controls - i (codex) spent a bunch of time setting up: the tank controls to individually drive each motor making the motor channels and configuration set in environment variables, and making a shell script that loads those environment variables from a shell script, enters the py venv, and runs the program adding different modes/states to the program and a radial menu to switch between them (all in a TUI by the way) adding a throttle limit and button presses to change it on the fly adding a button to start driving and making it so that every unrecognized button press stops it as a safety measure it wasnt alllll codex tho, i came up with the all ideas for these and usually gave rather specific details for how i wanted them implemented i also worked on the ball detection , which mostly involved sitting down and just adjusting parameters until the detection was like maybe almost passable, adding (asking codex to) add new parameters when the existing ones didn’t encompass the mistaks the detector was making. needless to say this lowk took a while but we’re in a good place rn i think!!! we have a moving robot with some kinda maybe working ball detection, which is like half of the first phase (the easiest part). so were slightly cooked but still yay it works!!"}, {"post_id": 79958, "ts": "2026-07-16T00:00:00Z", "hours": 7.0, "text": "ok sooooo turned out the wheels actually highkey sucked. the shaft was circular, so of course the motor didn’t rotate it well (its a d-shaft motor so its shaft output has a chunk taken out of it), but even once we added the d-shaft it just turned the hole circular by itself anyways 😭 luckily Lucas told us about these things called shaft hubs that dig in to the shaft with set screws and provide screw holes perpendicular to the shaft that can be a lot better at transferring the rotational power without yknow slipping. so we bought those on amazon ofc! but still the assembly went really well!! all the ports worked together, including the motor holes on the legs, and we were able to put the pi on top and connect all the electronics, eventually getting the motors actually moving while in the air by the end of the day! (with a lot lot of codexing ofc) this is what the robot btw!! its super duper duper cool isnt it :3"}, {"post_id": 79957, "ts": "2026-07-15T00:00:00Z", "hours": 7.0, "text": "by that i mean we cut holes in a cardboard box, screwed the motors into them, stuck the wheels on, and codexed like no tomorrow until the motors somehow worked (THANK YOU SO MUCH LUCAS and also gpt luna), but our stupid dingy two-wheeled cardboard box actually moved! baby steps i swear ok but more important we’ve actually designed a metal base for the robot!! its literally a flat metal sheet with holes cut in it + 2 bent sheet metal pieces with motor holes cut out in them but! we learned about onshape a bunch more, the process of sheet metal modeling, and especially how to work with a machine shop. you heard that right, we’re getting our parts sent to a machine shop!!!! im really excited to see this piece come to life after we bumbled around on an onshape tab for like 3 hours trying to design it, i have a feeling its gonna be really cool. oh also were getting it tomorrow afternoon yay!!!! attached is that slightly cooked “robot”"}, {"post_id": 79956, "ts": "2026-07-14T00:00:00Z", "hours": 7.0, "text": "luckily the tires were able to arrive this morning, so Jade (one of the adults at the program) brought them in and we got to designing + 3d printing wheels for them! luckily we have full access to a bambu lab x1 carbon here, so we took some lessons from Carlos (one of the mentors) in Onshape and tried to design a preliminary wheel. of course it didnt fit cause we have no idea how to use calipers seemingly, but the second attempt actually worked pretty well! you could try to turn the tire and stop the wheel, and it wouldnt move unless you put a lot of force. we left a shaft hole in it ofc so we can put it on the motors when we recieve them tomorrow. very awesome very cool!!"}, {"post_id": 79950, "ts": "2026-07-14T00:00:00Z", "hours": 4.4017, "text": "so i may have forgotten to make a project when we started this a week ago but! the motors and camera are all connected successfully to the pi and it has a gh repo set up with a Codex’d ball/cone detector that automatically drives the motors (or manually with a usb xbox controller clone). all we need now is for the sheet metal chassis we designed friday to arrive and the bidirectional ESCs we ordered to replace the small and kinda inconsistent generic ESCs we have now"}, {"post_id": 79955, "ts": "2026-07-13T00:00:00Z", "hours": 7.0, "text": "we’ve finally formed our real groups! i got placed with two dudes, one my age and the other surprisingly young for the caliber of challenge we had ahead we also got $1000 to spend at our discretion for the next two weeks!!!!!🤑!!!!!!! we immediately made an amazon account and ordered some fundamental stuff, like: a controller! i just bought a cheap usb xbox controller clone, since we dont really need quality but we do need a reliable connection that works on startup. most importantly, motors!!!! this took a lot lot lot of deliberation (the whole day basically) and talking to our motors, but we eventually decided on these Maxynos planetary gear motors cause they have really good torque, theyre not too expensive, and we can easily buy some ESCs to connect to them. speaking off… ESCs and power distribution cables: this constisted of the motor speed controllers that were very specifically bought for their XT60 plugs, and then 3 splitter cables (2 2-way and 1 3-way) to distribute the power to each of the 4 motors and the pi as well. battery: at the advice of Lucas, one of our mentors who clearly knows a lot about projects like this, recommended Spektrum smart batteries so we bought a few of those + a brand smart charger for both teams 5V converter: to feed battery power to the Pi without literally kabooming it up (and to connect it in the first place). tires: we spent a lot of time on this decision! once again, lucas came in clutch suggesting rc car crawlers wheels because they have a lot of friction but also are very bendy. plus they have listed dimensions and a lip to attach a “bead-locked” wheel to, so we can just design our own wheel and put it in once it arrives and that was the day! whole lot of money spent for sure but its fineeeeeee (probably) (hopefully)"}, {"post_id": 79954, "ts": "2026-07-10T00:00:00Z", "hours": 7.0, "text": "one of my partners had already been working on a ball detection demo over the last couple of days that worked with their laptop camera, so i (Codex) took some time to add a picamera2 backend along with the existing opencv2 one and getting the code actually uploaded to the pi. there were a bunch of issues with libraries and venvs and maintaining stable input and output to and from the pi, but eventually we got some kind of a demo working. we had to plug in the pi’s power supply in the corner of the room and partially covered by like 20 chairs, but the ball detection kind of almost maybe worked a bit! one problem was that they made the program assuming manual mouse input for initially cataloging the different colored balls under those lighting conditions, but that had to be removed because there was no good way to have mouse input and realtime monitor output for the pi *and we certainly wouldn’t have that on the course itself)"}, {"post_id": 79953, "ts": "2026-07-09T00:00:00Z", "hours": 7.0, "text": "the start of the day was spent with all of us drawing our ideas for how we’d design a robot that could complete the course and then discussing what we drew, which was pretty helpful since i changed my design a few times based on what other people drew. i spent some time trying to get the IMX708 camera they bought to connect, which of course took the entire day 😭 the problem was that i was plugging it into port zero but the line in /boot/firmware/config.txt was dtoverlay=imx708 . of course it was supposed to be include cam0 to specify it was plugged into port 0 and not the apparent default of port 1(?!?). but whatever, i got the camera plugged in and showing stills by the end of the day"}, {"post_id": 79952, "ts": "2026-07-08T00:00:00Z", "hours": 7.0, "text": "finished setting up the Pis (finally), despite the train of issues that tried to stop us: the first problem was that the college wifi required sign in, so setting it up headless wasnt working. i tried to use lynx , but the website required js on its sign-in page(??) so i couldnt do that. i tried to use my tether (basically a hotspot but without hotspot data) but wpa_supplicant wasn’t authenticating properly. i tried to use my real hotspot, but the wifi didn’t work with that either. on a whim i switched to 2.4GHz and WPA2 and it worked magically? of course rpi connect still didn’t work and ssh wasn’t allowed over my hotspot for some reason so i just had them buy us a monitor, reformatted with a desktop installed, and plugged in a usb mouse and keyboard to authenticate manually. of course ssh is blocked on the school wifi (what im using now), but rpi connect works enough. that was pretty much the entire day though, the only other thing i did was getting a git repository set up on the pi"}, {"post_id": 79951, "ts": "2026-07-07T00:00:00Z", "hours": 7.0, "text": "we met each other, got a look at the course, and all drove the RC car through it one at a time. we also made accounts and signed up for Onshape and ChatGPT Plus, then Patrick showed us how to use Codex since that’s how we’ll be “coding” the entire project. another classmate and i then proceeded to spend the rest of the day setting up the Raspberry Pis that we’re going to use as our robots’ brains (we didn’t finish that day) attaached is a picture of that rc car"}]...
|
Title: off-road autonomous robot by @leila | Stard Title: off-road autonomous robot by @leila | Stardance
Devlogs:
we met each other, got a look at the course, and all drove the RC car through it one at a time. we also made accounts and signed up for Onshape and ChatGPT Plus, then Patrick showed us how to use Codex since that’s how we’ll be “coding” the entire project. another classmate and i then proceeded to spend the rest of the day setting up the Raspberry Pis that we’re going to use as our robots’ brains (we didn’t finish that day) attaached is a picture of that rc car
finished setting up the Pis (finally), despite the train of issues that tried to stop us: the first problem was that the college wifi required sign in, so setting it up headless wasnt working. i tried to use lynx , but the website required js on its sign-in page(??) so i couldnt do that. i tried to use my tether (basically a hotspot but without hotspot data) but wpa_supplicant wasn’t authenticating properly. i tried to use my real hotspot, but the wifi didn’t work with that either. on a whim i switched to 2.4GHz and WPA2 and it worked magically? of course rpi connect still didn’t work and ssh wasn’t allowed over my hotspot for some reason so i just had them buy us a monitor, reformatted with a desktop installed, and plugged in a usb mouse and keyboard to authenticate manually. of course ssh is blocked on the school wifi (what im using now), but rpi connect works enough. that was pretty much the entire day though, the only other thing i did was getting a git repository set up on the pi
the start of the day was spent with all of us drawing our ideas for how we’d design a robot that could complete the course and then discussing what we drew, which was pretty helpful since i changed my design a few times based on what other people drew. i spent some time trying to get the IMX708 camera they bought to connect, which of course took the entire day 😭 the problem was that i was plugging it into port zero but the line in /boot/firmware/config.txt was dtoverlay=imx708 . of course it was supposed to be include cam0 to specify it was plugged into port 0 and not the apparent default of port 1(?!?). but whatever, i got the camera plugged in and showing stills by the end of the day
one of my partners had already been working on a ball detection demo over the last couple of days that worked with their laptop camera, so i (Codex) took some time to add a picamera2 backend along with the existing opencv2 one and getting the code actually uploaded to the pi. there were a bunch of issues with libraries and venvs and maintaining stable input and output to and from the pi, but eventually we got some kind of a demo working. we had to plug in the pi’s power supply in the corner of the room and partially covered by like 20 chairs, but the ball detection kind of almost maybe worked a bit! one problem was that they made the program assuming manual mouse input for initially cataloging the different colored balls under those lighting conditions, but that had to be removed because there was no good way to have mouse input and realtime monitor output for the pi *and we certainly wouldn’t have that on the course itself)
we’ve finally formed our real groups! i got placed with two dudes, one my age and the other surprisingly young for the caliber of challenge we had ahead we also got $1000 to spend at our discretion for the next two weeks!!!!!🤑!!!!!!! we immediately made an amazon account and ordered some fundamental stuff, like: a controller! i just bought a cheap usb xbox controller clone, since we dont really need quality but we do need a reliable connection that works on startup. most importantly, motors!!!! this took a lot lot lot of deliberation (the whole day basically) and talking to our motors, but we eventually decided on these Maxynos planetary gear motors cause they have really good torque, theyre not too expensive, and we can easily buy some ESCs to connect to them. speaking off… ESCs and power distribution cables: this constisted of the motor speed controllers that were very specifically bought for their XT60 plugs, and then 3 splitter cables (2 2-way and 1 3-way) to distribute the power to each of the 4 motors and the pi as well. battery: at the advice of Lucas, one of our mentors who clearly knows a lot about projects like this, recommended Spektrum smart batteries so we bought a few of those + a brand smart charger for both teams 5V converter: to feed battery power to the Pi without literally kabooming it up (and to connect it in the first place). tires: we spent a lot of time on this decision! once again, lucas came in clutch suggesting rc car crawlers wheels because they have a lot of friction but also are very bendy. plus they have listed dimensions and a lip to attach a “bead-locked” wheel to, so we can just design our own wheel and put it in once it arrives and that was the day! whole lot of money spent for sure but its fineeeeeee (probably) (hopefully)
so i may have forgotten to make a project when we started this a week ago but! the motors and camera are all connected successfully to the pi and it has a gh repo set up with a Codex’d ball/cone detector that automatically drives the motors (or manually with a usb xbox controller clone). all we need now is for the sheet metal chassis we designed friday to arrive and the bidirectional ESCs we ordered to replace the small and kinda inconsistent generic ESCs we have now
luckily the tires were able to arrive this morning, so Jade (one of the adults at the program) brought them in and we got to designing + 3d printing wheels for them! luckily we have full access to a bambu lab x1 carbon here, so we took some lessons from Carlos (one of the mentors) in Onshape and tried to design a preliminary wheel. of course it didnt fit cause we have no idea how to use calipers seemingly, but the second attempt actually worked pretty well! you could try to turn the tire and stop the wheel, and it wouldnt move unless you put a lot of force. we left a shaft hole in it ofc so we can put it on the motors when we recieve them tomorrow. very awesome very cool!!
by that i mean we cut holes in a cardboard box, screwed the motors into them, stuck the wheels on, and codexed like no tomorrow until the motors somehow worked (THANK YOU SO MUCH LUCAS and also gpt luna), but our stupid dingy two-wheeled cardboard box actually moved! baby steps i swear ok but more important we’ve actually designed a metal base for the robot!! its literally a flat metal sheet with holes cut in it + 2 bent sheet metal pieces with motor holes cut out in them but! we learned about onshape a bunch more, the process of sheet metal modeling, and especially how to work with a machine shop. you heard that right, we’re getting our parts sent to a machine shop!!!! im really excited to see this piece come to life after we bumbled around on an onshape tab for like 3 hours trying to design it, i have a feeling its gonna be really cool. oh also were getting it tomorrow afternoon yay!!!! attached is that slightly cooked “robot”
ok sooooo turned out the wheels actually highkey sucked. the shaft was circular, so of course the motor didn’t rotate it well (its a d-shaft motor so its shaft output has a chunk taken out of it), but even once we added the d-shaft it just turned the hole circular by itself anyways 😭 luckily Lucas told us about these things called shaft hubs that dig in to the shaft with set screws and provide screw holes perpendicular to the shaft that can be a lot better at transferring the rotational power without yknow slipping. so we bought those on amazon ofc! but still the assembly went really well!! all the ports worked together, including the motor holes on the legs, and we were able to put the pi on top and connect all the electronics, eventually getting the motors actually moving while in the air by the end of the day! (with a lot lot of codexing ofc) this is what the robot btw!! its super duper duper cool isnt it :3
my day was spent entirely on programming two things: the controls - i (codex) spent a bunch of time setting up: the tank controls to individually drive each motor making the motor channels and configuration set in environment variables, and making a shell script that loads those environment variables from a shell script, enters the py venv, and runs the program adding different modes/states to the program and a radial menu to switch between them (all in a TUI by the way) adding a throttle limit and button presses to change it on the fly adding a button to start driving and making it so that every unrecognized button press stops it as a safety measure it wasnt alllll codex tho, i came up with the all ideas for these and usually gave rather specific details for how i wanted them implemented i also worked on the ball detection , which mostly involved sitting down and just adjusting parameters until the detection was like maybe almost passable, adding (asking codex to) add new parameters when the existing ones didn’t encompass the mistaks the detector was making. needless to say this lowk took a while but we’re in a good place rn i think!!! we have a moving robot with some kinda maybe working ball detection, which is like half of the first phase (the easiest part). so were slightly cooked but still yay it works!!
almost all of today was spent discussing and weighing different suspension designs and drive train implementations, culminating us in finally buying some parts and basically finishing out our $1000 budget from the start of the program to the end of this week. we settled on the 4 independent legs early, so the options were between: mounting the motor on the chassis on the same pivot point as the leg itself mounting the motor on the chassis and using a u-joint articulated axle mounting the motor high up on the leg and using a belt drive eventually we arrived on that last option because the other ones didnt really pose a benefit that was worth the complexity they would introduce (especially the first one) towards the end of the day, we ordered all the parts we needed to install it hopefully over tomorrow and wednesday also! we finished printing the finalized(…) wheel design so now we have four rigidly attached and bead-locked wheels+tires!! turns out the robot is like significantly faster than we thought so uhhh throttle limit is gonna have to be pretty low for a bit. below is a sample of our mad drawings (mostly mine 😭) trying to figure out how the hell this thing is gonna work
7/22 - not much we can do about it much of today was spent moping about how everything would be arriving tonight (and of course the belts are arriving tomorrow night, one of the parts that is literally necessary to drive the thing at all). so much of today was spent just trying to design, cad, and otherwise figure out details for the legs before we actually had the components necessary to make them. i spent some time with one of my teammates figuring out where specifically the springs for the legs are gonna go, and he made a quick 3d printed rod-end that’ll hold in the shaft that acts as the spring dowel. we also planned out where we could put the legs’ pivot point on the chassis and just generally planned every element of assembly that we could. this also involved figuring out last second that i had no idea how we were gonna mount the springs and chassis on the leg at all and that my teammates didn’t know too much either, but its cool we figured it out and started the print by the end of the day 👍 attached: us figuring out where we’re gonna mount both the leg and the spring on the chassis and me drawing the top view of all the drive train stuff going on inside the leg (ignore my horrible handwriting its the board i swear)
7/21 - EVERYTHING GOT DELAYED VERY BAD NEWS: every single thing we needed to order for the drive train and suspension got delayed by a day 😭 anyways completely unrelated but the second competition is being moved to thursday, cause we cant drive through the course with literally 0 suspension the first 2 hours of today was spent rushing out an onshape sketch to get our metal legs cut by Lucas cause he (reasonably enough) wanted the drawing by 11 before he left the shop. i had to remember how to do drawings, with a lottt of help from carlos. unfortunately, i forgot the holes for the spring on the top so we’ll have to figure that eventually. i also forgot to put holes that would make screwing in the motor remotely possible but lucas the GOAT put those in for us. could not appreciate it more we might be lowk cooked now, cause the bearings say they’re gonna arrive thursday night so we may not even have the robot driving again until next week 😭😭 that being said we ball‼️ also ill be posting a devlog every weekday now cause i need to journal every day anyways attached below are 2 of the legs we got cut with the motors on them
guess what THE BEARINGS AND SHAFTS GOT DELAYED!!!! YAAAAAAAAAAAYYYYY its fine. we spent today CADing and printing new designs for both the leg inserts and one piece of the rod-ends, and i think they’re in a pretty good place (for not having the actual components needed). I also did some testing with the ball/cone detection and came to the conclusion that it simply sucks and just isn’t good enough, so I got Codex to give me suggestions for an overhaul and I picked which approach would be the best to go for. The demo it produced for me using new shape detection and differentiating objects from its surroundings (in camera space) was so bad that I’ve decided on a completely different approach altogether: ML!! I got it to do another overhaul that would add a mode to the existing code that allowed camera snapshots to be taken and put in a folder with a press of a button on the controller. Then, it made a tool that could be run on my laptop that would bring the images up one by one, I would mark balls and cones on there, and then that data would be used to train an ONNX model (with ROCM acceleration on my Radeon 890M iGPU, of course) that could then be uploaded onto the Pi and ran as the new detection backend!! we’ll see if it works, cause I did all this at the end of the day and had no time to gather training data (of course i came up with this after two days of having very little to do).
the parts came! literally all of today was spent assembling the drive system as my partners were drilling the holes and cutting the shafts for the wheels, pivots, and spring dowels. we’ve unfortunately found out that the belt drives skip kind of a lot, so hopefully this doesn’t cause issues with driving under torque when we get to that… (i swear if this is foreshadowing) we also went out to Reflect Orbital today!! seeing the mirrors was incredibly cool, and the material they made it out of felt really interesting. something about its very small thickness (2.8 microns!!) made it feel like it was barely on your finger if you weren’t looking at it. In addition, I talked to one of the software engineers (shoutout Alfonso) about how they get the software done, including things like: Double buffering updates (seemingly called ABing) to make sure that no update permanently breaks the system Using the Yocto project to make a custom Linux kernel for their embedded systems Monolithic applications vs. a more service based approach that also goes hand in hand with… Error handling and making sure that something like an illegal instruction won’t crash your expensive space satellite Testing with the ground-sat (all of the components on the real satellite connected together on a table in a room) and an approach that involves uploading the changed code to the ground-sat every night and running a whole test suite to make sure none of the changes broke anything and that they (hopefully) achieved what they were written for overall it was pretty damn cool you should check out Reflect :3 below is one of the legs, and as you can see theres a whole belt going from the motor to the wheel!
GUESS WHAT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! the belt is skipping. turns out the belt needs to be tensioned to not yknow skip horribly. any real torque that the wheel experiences back on it, including the torque inherently present in turning with tank drive (which is really high cause we have really grippy wheels and their laid out in a rectangle), makes the belt slip on the teeth and not drive the tire at all, leaving the motor spinning but the robot not moving. basically, we’re gonna need a tensioner to slot into the legs. in other news, we still have to get intake/outtake working by friday hopefully. i’ve ordered TPU filament online and got on of my teammates to start on a design for a flywheel that has a PLA hub and TPU tire, maybe we’ll print it tomorrow? although one good thing about this is that the robot looks super cool awesome now (source: see below)
the TPU arrived! guess what though: it lowk doesnt work with the X1c (our printer)!!!!!!! we refined the design for the flywheel a bit, but after figuring out the TPU settings in the printer, our test prints didn’t work at all. at some point, it just seems to run out of filament (usually before the first layer finishes) and leaves these dots of plastic where its supposed to be entirely filled in. no TPU ig!! my teammates spent most of the day figuring out where to cut holes for the tensioner and then actually drilling those holes for the eventual assembly (prob tomorrow). it looked really sucky cause the hacksaw is time-consuming and lowk rather annoying, especially when we need to cut 3 shafts into like 12 pieces, so thank you teammates that was very nice 🙏 i spent the whole rest of the day on the CAD for the articulated arms that we’re gonna have in front and on top of the entire robot, and i designed a servo mount that’ll keep the servos attached to the robot at the exact height we need them to be to make a plate that hits the ground, settles at a nice angle, holds the flywheels, and all the while still fits on the print bed. i tried to print one of those mounts but after like 5 prints that failed on the first layer, the only succesful print ran out of filament on the second to last layer 😭 its lowk chill though cause it looks kinda cool so im gonna keep it attached is the lowk awesome lowk cooked servo mount that i lowk made and printed lowk
so my GOATED teammate whose shall not be named figured out the TPU problem: the printer just wasnt strong enough to feed it in! i honestly have some doubt that that was THE problem, considering how easy the solution is (just unspool a bunch of filament onto the ground), but whatever we ball‼️ anyways the first third of today was spent working on that servo mount and arms CAD file i mentioned before as my partners finished up cutting the shafts and legs for the new tensioners. i also got the tensioners printed, but that was pretty quick since its just a few ~1x0.5” pieces the second third was spent doing the assembly for all the pieces, since we had to take apart each leg completely, and then go down the assembly line to put it together. i was responsible for putting on the tensioners and then the motors with these really handy alligator clips Carlos graciously gave us that allowed me to get short screws into holes that were far into the leg. then, once the motor is attached, my partner would attach the wheel and get the belt on there. i think he used some like dark magic cause the belt was really hard to get on before it was tensioned, idek how he did it now… my other partner would then put on the insert, bearings, and shaft for attaching the leg to the chassis. once we were done, we all spent some time getting the legs on the chassis but we didnt finish. i rushed to start the flywheel TPU print we designed a while ago before we left and spent the rest of the day on… THE SPACE X TOUR!!!!!!!!!!!!!!!!!!!!!!!!!! we got to go to spacex and have a little tour with one of patricks friends!!!!!!!!!! it was really really really cool, the facility was huge and we such a bunch of fuel tanks, satellites, an engine actively being built, and a phased antenna array. that last thing nerdsniped me so hard, and because Simon (one of our “tour guides”) was an engineer that worked on the Starlink user terminals (which also had the same type of antenna array as the Starlink satellites) i was able to ask a bunch of questions about it. apparently, they both have a bunch of antenna put together and arranged such that, by controlling the phase of the signal coming through each of the ~50 antennae, can focus on a narrow beam of EMF waves and effectively filter out signal to only a specific Starlink satellite in the sky. super cool!!!! no photo(s) cause we weren’t allowed to take any but its chill
I FORGOT TO PUT THE PRINT PLATE IN THE PRINTER YESTERDAY GOD DAMN IT 😭😭😭😭😭 its fine. ok so today was generally pretty mundane BUT!!! WE DROVE UP THE HILL LITERALLY ONCE!!!!! just on a whim my partner decided to go full power up the hill after my other partner had just loctited every set screw to see if we could make it, and we did!!!!!!!!!!!!!!!!!!!!!! …….unfortunately……… nobody filmed it…………………………….. -# god damn it…………………………. it was really cool though! i think it represents that we’re really nearing a functionally useful robot and that were actually overcoming the challenges that have plagued us for like weeks anyways heres a picture of our bot looking super duper cool
okay this day was an experience fs. the start of the day was relatively normal, i was working a bit on ball detection while my partners assembled the intake/outtake thingy, and all of a sudden the pi turns off . this happened before when the power draw was low and peripherals were connected, so i just took out the camera and turned it on. yup, works fine. ok so lets plug the camera in while its on and it turns off . odd, looks like its probably some random bug or connection issue, so i just unplugged it, reseated it, and restarted the Pi. and it doesnt even turn on. ok, well theres another port. idk whats going on, but maybe thatll fix it? nothing. theres spare cables, lets try those ig? nope. ok what the hell the camera must be broken, so lets try a spare camera. doesnt turn on. ok what the actual ****???? lets try it on their robot and then theirs doesnt turn on either . at this point i am positively destroyed and fuming, luckily we have some very good food coming from a place nearby called the melt, so hopefully having a nice gooey cheesesteak can help me calm down, lock in, and figure out whats going on. big mistake. an hour passes. the adults have put on a movie, a fast and furious movie. you dont feel delirious, nor subdued, but simply off. its almost as if you are both more aware of your environment and slowly less aware of yourself. an hour passes. the car noises are still going. focus was a lost cause. one adult is stretching on the floor. the other is sitting at a table, still watching. you’re on the floor too. you’re not getting anything done. it was a lost cause anyways. an hour passes. carlos is sleeping on the slanted wooden plank of the hill. jade is lying on the floor and staring straight up. somehow your partner is locked in. the car noises continue. you are two inches away from meeting God, before you start laughing. shes laughing too, as well as your partner. presumably at carlos. sanity was a lost cause, and you lost it four and a half hours ago. cant believe its somehow 3:30. long story short, we slowly went insane with tokyo drift in the background as i pulled my hair out from the pi frying our cameras and the movie making it hard to focus, while one of my partners locked in to an unprecedented level, one just watched the movie casually, and the rest of us went crazy for no particular reason at all. this was a wild day (hence why im writing this the day after) never eating at the melt again bruh 😭
i am gonna be gone wednesday, thursday, and friday this week due to my schools orientation happening right before CalTech’s WiSTEM (which i am indeed going to :3), both of which are on weekdays. thus, with the intake challenge pushed even further to this wednesday (marking a full week delay), i will need to spend some time getting our existing systems to a good place and helping my partners with whatever they need over today and tomorrow before im gone. that being said, we did very little locking in today (hence calling it the dawn) because we had both a speaker and a tour!! Will Heltsley, former VP of Propulsion of SpaceX and an insanely knowledgable engineer, talked to us about different engineering concepts and some strategies for finding a stable job and a community of like-minded nerds that are fun to work beside. i asked a few questions about working with teams (because this program has shown me that it’ll be a very valuable skill to learn), especially since Will has done everything from working on a 3-person team to managing a group of 350 engineers. he was really helpful!! we also got to tour another startup, Forge Atomics, and it was awesome to see the inner workings of a company that is just getting of the ground! they had a really cool concept and i loved their mission, which in talking to one of the co-founders (Rex the goat) i learned was one of the most important things in finding a team that is going to work well: your missions need to align. also i learned from both mentors that, unless you plan on doing something research heavy like quantum computing, you should NOT get a PhD. guess what i want to do!
okay so like i said last entry ill be leaving for three days, which means that i had to finish up some things today! i decided at this point that we were not going to able to mount a plate in the front for the intake (rip that idea and the whole bunch of filament we wasted on it 😭) so i spent the entire day pivoting on that idea and making the articulated suspension!!!! this was a really cool idea i talked with carlos about for like an hour, although we were thinking about only servos for suspension. this time around, i modified those servo mounts to place the head of of the edge of the main plate and used a bit of kevlar string Trina donated (ty Trina!) and tied it to the servo head and around the wheels hub. this means that when the servo is drawn up, the string pulls on the wheel, compresses the spring, and brings the robot down. for context, there is an 8 inch height requirement* that we had yet to succesfully get under. by that i mean the robot was like 11in. so, to get around that, these servo mounts could effectively deactivate the suspension at will, not only making driving more stable in the ball collection phase, but also actually getting under the height requirement! (since it was only a starting height requirement, we were allowed to expand after) anyways i made one mount, tested it, it didnt fully work, designed another and printed two of them, codexed while that was printing, tested one (it worked perfectly), printed 2 more, codexed the code for different states and positions for the servos and configuration stuff ofc, assembled the rest, tested all 4 of them out at the same time, actually tied good knots, and it was done by the end of the day!! im really proud of finishing this subsytem in one day before i left, it was suprisingly fun to see the robot dancing and doing pushups as it drove. and honestly, i think today really gave me that feeling of how incredible it is to see something like this just come to life, the way i feel when i make progress on a good coding project. i lowk want a 3d printer now… maybe that radish jam money could really come in handy…….
OKAY it is time to get down to business we do NOT have much time. first order of business was looking at the TPU wheels reflect printed! they had come in while i was gone, and compared to our flywheels they were actually suprisingly good (although they lowk had their heads blown shmoove off (the tops were weirdly disconnected and ripped off)). most of all, our wheels were much too stiff and theirs were relatively soft, so we decided to go with theirs. we’d also gotten metal parts back from lucas; unfortunately, lucas’ parts were cut kinda incorrectly and for whatever reason the machine shop didn’t make them!! so, i spent today primarily trying to figure out how to do intake while one partner was working on (OF COURSE) retightening and loctite-ing the set screws and the other partner was working on finishing/testing the climb with a smaller motor he bought online over my hiatus. and by figuring out the intake, i mean taping a cardboard box to the bottom of the robot and letting it flap down while desperately PRAYING that the balls go in. i was also driving around a bunch trying to figure out why the robot was still really struggling to take turns, especially on the foam. eventually i had the insight that the friction on the wheels was simply too much, and Lucas came up with the idea of wrapping tape around the wheels to reduce it!! after that it was insane how well it drove and took turns, especially off of the foam floor. i lowk drove it around for like 45 mins straight it was so insanely fun to see something we made acting like a real machine, cause it was driving at a quality i could actually expect in like a real product! it was so cool and gratifying :3 of course i forgot to get a picture of video of it, which i have a feeling im gonna regret…
and i call it frickmas cause THE COMPETITIONS TOMORROW OMG OMG OMG OMG OK SO here’s what on the agenda: making sure the set screws dont destroy themselves on the field getting the climb attached and making sure it maintains enough torque to actually pull the robot figuring out some sort of system for intake lining up all the suspension to prevent it from getting stuck, damaging the metal, or crapping out on the washboard section making sure the pi mount, buck converter, code, suspension actuation, and every other subsystem actually work testing!!! lots of testing of all of everything!!!!!!! for the first one, my partner had already spent so long on the set screws so some testing was all it took to see that they were fine, and that was enough cause they were not really going to get any better. my other partner finally got around to actually finishing up the climb and attaching it to the front of the bot. good news: it hooks! bad news: it doesn’t even remotely pull back! luckily, the rules still gove points for hook but no lift, so we decided to leave it there since his effort could be best spent elsewhere with this little time left the intake system was determined to be pretty much a dud by the end of the day, cause of course cardboard couldn’t really carry anything, and we didn’t have time to design something better since the last system fully failed lining up the suspension was pretty easy, just took a bit of manual adjustment and a good amount of testing on the field each of these were kind of annoying to address but i have a feeling itll be rather important at the end of the day (which is basically how long until handling all the wiring and subsystems took us) lastly for the testing, we just drove like a bunch of times! honestly the runs went like okayish ig, we rarely made it past the washboard and of course NEVER made it over the hill ever since we did it first a couple weeks ago. otherwise though, the robot was stable the entire time and didnt have any weird glitches or hardware malfunctions (thank god we taped down the battery this time) so we were good(ish) to go! below is basically what our final robot is gonna look like (minus the climb)
ladies, gentlemen, and my beautiful enbies * ITS TIME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *(ok so i admit this entry was written days later cause i had to go to school next day so my memory is foggy but! its still cool :3) basically the first half of the day (before everyone came in) was spent finalizing somethings we’d waved off earlier, like cable management and wiring in general, especially the motor wires were dangerously close to the suspension rods and a bunch of other things like that power and attaching the battery, since we really needed to keep the batteries charged properly to prevent the pi being underpowered and the battery needed to be held on with something a little less flimsy than straight up velcro 😭 THE GOD DAMN SET SCREWS HOLY TUNA THESE THINGS WILL NOT STAY TIGHT NO MATTER WHAT WE ARE NEVER GOING UP THAT HILL AGAIN ISTG (subtle foreshadowing) keeping the kill switch always accessible from the top and attaching it with a little more than tape and prayers making sure the wheels are attached properly and wont jut out weirdly as it has in the past, throwing the driving off balance as it getting the climb to actually work which is lowk a lost cause but we ball praying theres something we can do about the intake situation 😭🙏 among much more of course, the time eventually came when people started arriving (like alfonso, shoutout my goat) including a whole lot of parents. we started by showing them our robots as we made some final tweaks, like making sure the pi wouldnt fall off of our beautiful, incredibly complex attachment scheme (velcro mounting strips) until it finally happened… COMPETITION START‼️ so the way this ended up going is that each team alternated runs, usually getting progressively further (keyword usually …) Run 1: Team Big Fish (not us) their first run didn’t go too bad!! their ball intake was suprisingly functional (and by suprisingly i mean at all) (better than us tho) and they were almost able to get around the cones autonomously without hitting one! however, when it came to the washboard, it didnt really work out… their bot very quickly got stuck on a pipe and was ill equipped to unstuck itself, ending the first run. Run 2: Team 10 (US!!!!!!!!‼️!!!!!) also not too bad somehow!!!!!!!!!! of course there was no ball intake so we just drove over them, but we were able to slowly but surely get past the slalom with wide margins and very very slow turns in place. as for the washboard though, our run wasnt much better… i took the robot off of the ramp at the start rather fast, making sure to turn up the throttle limit in the hopes it would get us over a few obstacles. spoiler alert: it didnt. we pretty quickly just crashed into a full cinder block, bending the sheet metal base and unsurprisingly making it hard to continue the run! but whatever it was not too bad for a first attempt Run 3: Team Big Fish this one was probably their best! the ball intake was great, and they were able to carry them all through a perfect no-hit slalom! unfortunately, a similar fate to last time met them at the washboard. third times the charm hopefully… Run 4: Team 10 although the robot was slightly banged up now, it was still totally good to go! this slalom attempt was not nearly as graceful, and that certainly applies to the washboard too: i turned up the throttle limit more on the ramp and really just sent it, only to get stuck on top of that cinderblock instead of past it. fun stuff!
ok so from here on we just started placing the robots at different places trying to show what they could do if the washboard didnt always destroy their runs Exhibition 1: Team Big Fish and THE HILL … for our first exhibition, the other team set up the robot before the hill and took some stabs and speeding their way over it. in the end, none of the attempts made it, but i have video of the third one where they got so close that one of the wheels drove onto the other side of the hill and kept the robot there, until their driver let go of the throttle and let it down. it was super cool!! Exhibition 2: Team 10 and THE HOOK finally it was time for my teammates magnum opus of the past two weeks to be revealed and truly tested, and that of course was THE CLIMB!!!! and by the climb i mean a big pink plastic hook on the end of a measuring tape roll taken out of its case that we lovingly call “the bomb” (because it WILL explode if not handled properly). like i said a while ago though, the climb didnt have enough force to pull up the robot, but thats fine! theres still partial points for hooking, so all this exhibition really was was the hook rising at an almost comedically slow pace, before i carefully drove the robot over to the bar (as to not fold over the tape from the velocity) and gingerly brought the hook down on it. and everybody clapped! Exhibition 3: Team Big Fish and THE DUNK aka they used their shooter. it was super cool actually! they have a whole system with conveyor belt squeezing balls forward from above a slanted metal sheet, with flywheels at the end that can block balls for storage purposes until the gate is opened and the conveyor belts are forwarded to shoot them! it was suprisingly good and consistent, shooting from behind the second-to-last line. i wish we could do that… its okay they dont have a climb so we’re better and that was pretty much it! this experience has been so incredibly helpful for my learning and for me in general, and it really was(😢) one of the most fun times of my life. i dont even think i could near catalogue how much fun i had and how many things i learned. i really cant put it into words. thank you lucas, carlos, jade, maanya, patrick, alfonso, and trina for making this what it was, and of course thank you big zrl for sponsoring my attendance. if you’re reviewing this project, i recommend looking at devlogs further down if you’re missing context. the photos should hopefully help see the progression as well (if i can get those uploaded…) i leave you with 3 photos: the state of the robot right before i turned it off for the last time, the absolute state of our whiteboard after we used for brainstorming, and a last minute photo of the hallway i knew i would never walk again. happy hack clubbing!...
|
1792752594.3365576
|
1793357394.3365576
|
|
33549
|
off-roading autonomous rover by @maanya_madan | St off-roading autonomous rover by @maanya_madan | Stardance...
|
maanya_madan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: off-roading autonomous rover by @maanya_mad Title: off-roading autonomous rover by @maanya_madan | Stardance...
|
1792749294.8259482
|
1793354094.8259482
|
|
72119
|
offbranded streamdeck by @lightzcreatz | Stardance
|
lightzcreatz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: offbranded streamdeck by @lightzcreatz | St Title: offbranded streamdeck by @lightzcreatz | Stardance...
|
1793389634.6134317
|
1793994434.6134317
|
|
31932
|
officerdwnOS by @officerdwn | Stardance
|
officerdwn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: officerdwnOS by @officerdwn | Stardance
|
1793451346.2055953
|
1794056146.2055953
|
|
7699
|
official renderlight keyboard by @lazerkat | Stard official renderlight keyboard by @lazerkat | Stardance...
|
lazerkat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: official renderlight keyboard by @lazerkat Title: official renderlight keyboard by @lazerkat | Stardance...
|
1793476479.9187765
|
1794081279.9187765
|
|
56886
|
offline game time pass game by @deba | Stardance
|
deba
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: offline game time pass game by @deba | Star Title: offline game time pass game by @deba | Stardance...
|
1793404267.5886323
|
1794009067.5886323
|
|
4177
|
offline mini gaming console by @shyamks1828 | Star offline mini gaming console by @shyamks1828 | Stardance...
|
shyamks1828
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-26T06:20:41Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I am making a retro games gameboy of sorts. its not completed yet. I just wanna spread a product that helps kill time offline for very cheap. I will be upgrading certain aspects like power source and be adding more games and interactive interface. any suggestion reac out to me.", "repo": "https://github.com/coderrcboy/arduino-game-boy", "demo": ""}]...
|
[{"post_id": 15680, "ts": "202 [{"post_id": 15680, "ts": "2026-06-25T14:23:29Z", "hours": 0.3833, "text": "this is iteration 1 . please gimme feedbacks. i will be reworking the case design. also there are some glitches in the code pls do advice after trying it out."}, {"post_id": 12880, "ts": "2026-06-21T03:12:48Z", "hours": 0.4092, "text": "Hi guys im trying to revive nostalgia by making a gameboy like console with arduino nano to play classic retro games am still coding first game. i am visualising a final gameboy with many game options which u can choose from menu."}, {"post_id": 8691, "ts": "2026-06-14T13:14:07Z", "hours": 0.2947, "text": "Hi guys Im working on a mini arduino nano console of sorts where you can play simple retro offline anywhere. My goal in thus community is to publish projects that spread joy! Hope to take this to completion amidst my hectic school schedule!"}]...
|
Title: offline mini gaming console by @shyamks1828 Title: offline mini gaming console by @shyamks1828 | Stardance
Devlogs:
Hi guys Im working on a mini arduino nano console of sorts where you can play simple retro offline anywhere. My goal in thus community is to publish projects that spread joy! Hope to take this to completion amidst my hectic school schedule!
Hi guys im trying to revive nostalgia by making a gameboy like console with arduino nano to play classic retro games am still coding first game. i am visualising a final gameboy with many game options which u can choose from menu.
this is iteration 1 . please gimme feedbacks. i will be reworking the case design. also there are some glitches in the code pls do advice after trying it out.
Ships:
I am making a retro games gameboy of sorts. its not completed yet. I just wanna spread a product that helps kill time offline for very cheap. I will be upgrading certain aspects like power source and be adding more games and interactive interface. any suggestion reac out to me....
|
1792878505.5100656
|
1793742505.5100656
|
|
69048
|
offload by @pch | Stardance
|
pch
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: offload by @pch | Stardance
|
1793130475.8533878
|
1793735275.8533878
|
|
59366
|
oggy000 by @tahsinraiyan330 | Stardance
|
tahsinraiyan330
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-07T12:11:51Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Actually, I can not build the full slack bot. I can not un it for 24/7", "repo": "https://github.com/tahsinraiyan330/newwsss", "demo": "https://app.slack.com/client/E09V59WQY1E/C0P5NE354?_gl=1*rrz3ch*_gcl_au*MTUwODY5NzUyMi4xNzg3MzYyODI5"}]...
|
[{"post_id": 63503, "ts": "202 [{"post_id": 63503, "ts": "2026-09-07T12:07:35Z", "hours": 0.6742, "text": "I have built the slack bot but can not run it for 24/7"}]...
|
Title: oggy000 by @tahsinraiyan330 | Stardance
De Title: oggy000 by @tahsinraiyan330 | Stardance
Devlogs:
I have built the slack bot but can not run it for 24/7
Ships:
Actually, I can not build the full slack bot. I can not un it for 24/7...
|
1793314097.5690234
|
1793400497.5690234
|
|
46079
|
ok by @dysonc2010 | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ok by @dysonc2010 | Stardance
|
1793368210.5852528
|
1793973010.5852528
|
|
23774
|
old by @DefinitelyACoder | Stardance
|
DefinitelyACoder
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: old by @DefinitelyACoder | Stardance
|
1793332045.9066722
|
1793936845.9066722
|
|
45803
|
oled refillable hourglass by @ck | Stardance
|
ck
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: oled refillable hourglass by @ck | Stardanc Title: oled refillable hourglass by @ck | Stardance...
|
1793357421.916664
|
1793962221.916664
|
|
25547
|
olivOS by @opu314 | Stardance
|
opu314
|
1
|
8.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-19T14:09:06Z", "hours": 8.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What I Made 🐰: olivOS, a bunny-themed webOS that reflects my passions, interests, and life Features 😲: Topbar with live clock 🕐 Bottom bar with desktop icons to select on first click, and open on the second Draggable (click and hold on the Handle text), closable (click on Close), and overlapping windows (click 🖲 a window to bring it forward!) Easter Egg 🐣: text that changes colour when you hover over it! Try to find it 😄 Multiple Apps 🖥: Welcome: intro to olivOS About me: introduction about me! Blog 📝: entries about my experiences, with a sidebar for selection Fun Facts: random fun fact generator:) Find out more information by reading my project’s README, on github: https://github.com/OliviaSYS/olivOS !! Try My Project 👉: https://oliviasys.github.io/olivOS/ !! Challenges 🎢(this project was not as simple as I thought, but it was quite fun to build!): I’m not an expert at CSS and JS, so I sometimes made mistakes in my code, forcing me to do some debugging at the end of each programming session. I didn’t know that you had to have a “border-style” attribute in order for the borders to appear, so I spent a lot of time trying to fix this, until I decided to use the simpler “border” attribute and figured it out! variable names for js array confused with variable names for css id. some classes that I had at the beginning, when some js functions didn’t exist, were not removed afterwards after following the tutorial, I had to spend a lot of time cleaning up my code because I was not sure which parts to delete during the process:(. however, I read over my code slowly and realized that I didn’t need specific functions for each window, only the general one:))) finally, the guide had a lot of css styles embedded in html tags, so I found it a bit hard for me to follow it because I wanted different css. What I’m Proud of ✨: learning how to make a webOS after 8 hours of working hard and coding! 🎉 discovering how to load content programmatically making my own personal themes using CSS, as well as my personal fun fact generator app! :))) Credits: Hack Club JamHacks Tutorial!! Btw thank you StarDance and Hack Club for this amazing opportunity!", "repo": "https://github.com/OliviaSYS/olivOS", "demo": "https://oliviasys.github.io/olivOS/"}]...
|
[{"post_id": 70541, "ts": "202 [{"post_id": 70541, "ts": "2026-09-19T10:26:01Z", "hours": 0.595, "text": "Finished README.md! Read the image below or go directly to my project github: https://github.com/OliviaSYS/olivOS"}, {"post_id": 70513, "ts": "2026-09-19T09:36:53Z", "hours": 2.8794, "text": "Major Updates: Added a blog (following the “Create Your First App” part of the JamHacks WebOS guide) ~ added some css transitions for the left sidebar for personalization! Hoping to add a posting feature in the future:) Created a div for the bottom bar, to store all the desktop app icons! Minor Updates: Again, changed/added a LOT of css! Ex. my “generate a fun fact” button, borders (initially, i had all the border-weight, border-style, border-color attributes separate, but i combined them into one border attribute to make my code cleaner!) topbar colours/margins/padding webOS wallpaper and lots of font-size/color for text! Debugging: too many to list! involved the wrong css in script.js: confusion between my array blogContent and my variable blogContent for query selecting “#blogContent” (now changed to blogcontent to prevent this error). This caused the “handle” of my blog window to break:((( Anyways, olivOS should be completed or WebOS 1! Gonna ship soon:)))"}, {"post_id": 69969, "ts": "2026-09-18T04:30:51Z", "hours": 1.5267, "text": "Finally, I decided to add some (kind of random) css in order to make sure my code worked. For example, I added padding, position, colors, and align indicators to various elements. An issue I struggled with was: —–flex-direction: column, which was supposed to be the case for my windows, but I discovered that I had a duplicate: —–.window { —––flex-direction: row; —–} which was my bug! I realized that there was a significant number of bugs in my code - i put the —–“selected” class manually when i wasn’t supposed to, i forgot a dot/period before —–”/images…” and i also had —–dragElement(element.id) instead of —–dragElement(screen). Now, my handle actually works, and it flashes turquoise when it is selected!"}, {"post_id": 69471, "ts": "2026-09-17T03:57:38Z", "hours": 0.9003, "text": "I added a fun facts window as my first personalized/advanced app! This used the normal style of a fun fact generator - a button and text. When I customize all my css, I’m hoping to add a border for the fun fact container in order for the size to be constant. Btw, I previously had all my fun facts in an html list, but then in order for it to be a random generator, I moved the strings to a javascript array and had to make sure my code wasn’t (displayfunfact is an id): —–displayfunfact.textContent, but: —–displayfunfact.innerHTML. That way my and tags would work! In the end, this worked out well:)"}, {"post_id": 68962, "ts": "2026-09-16T03:49:42Z", "hours": 0.5867, "text": "After following the guide, I realized that I had many bugs inside my code-it was really disorganized! I took some time to fix it by putting all of the app icons inside a “#desktopapps” div, as well as the windows inside “#windows”. In addition, I fixed some of my js, which originally had specific open and close operations for my “welcome window”. However, I now generalized those functions for all types of windows instead. <:~:> now it works a lot better! :))"}, {"post_id": 68499, "ts": "2026-09-15T07:06:16Z", "hours": 1.3689, "text": "Completed Pt.I, II, and III of the guide! However, I didn’t really focus on the aesthetics (css) aspect of my WebOS; instead writing mostly HTML and some JS for closing and opening windows, and also the clock, which you can see in the top right corner. I’m finally starting this project:)"}]...
|
Title: olivOS by @opu314 | Stardance
Devlogs:
Com Title: olivOS by @opu314 | Stardance
Devlogs:
Completed Pt.I, II, and III of the guide! However, I didn’t really focus on the aesthetics (css) aspect of my WebOS; instead writing mostly HTML and some JS for closing and opening windows, and also the clock, which you can see in the top right corner. I’m finally starting this project:)
After following the guide, I realized that I had many bugs inside my code-it was really disorganized! I took some time to fix it by putting all of the app icons inside a “#desktopapps” div, as well as the windows inside “#windows”. In addition, I fixed some of my js, which originally had specific open and close operations for my “welcome window”. However, I now generalized those functions for all types of windows instead. <:~:> now it works a lot better! :))
I added a fun facts window as my first personalized/advanced app! This used the normal style of a fun fact generator - a button and text. When I customize all my css, I’m hoping to add a border for the fun fact container in order for the size to be constant. Btw, I previously had all my fun facts in an html list, but then in order for it to be a random generator, I moved the strings to a javascript array and had to make sure my code wasn’t (displayfunfact is an id): —–displayfunfact.textContent, but: —–displayfunfact.innerHTML. That way my and tags would work! In the end, this worked out well:)
Finally, I decided to add some (kind of random) css in order to make sure my code worked. For example, I added padding, position, colors, and align indicators to various elements. An issue I struggled with was: —–flex-direction: column, which was supposed to be the case for my windows, but I discovered that I had a duplicate: —–.window { —––flex-direction: row; —–} which was my bug! I realized that there was a significant number of bugs in my code - i put the —–“selected” class manually when i wasn’t supposed to, i forgot a dot/period before —–”/images…” and i also had —–dragElement(element.id) instead of —–dragElement(screen). Now, my handle actually works, and it flashes turquoise when it is selected!
Major Updates: Added a blog (following the “Create Your First App” part of the JamHacks WebOS guide) ~ added some css transitions for the left sidebar for personalization! Hoping to add a posting feature in the future:) Created a div for the bottom bar, to store all the desktop app icons! Minor Updates: Again, changed/added a LOT of css! Ex. my “generate a fun fact” button, borders (initially, i had all the border-weight, border-style, border-color attributes separate, but i combined them into one border attribute to make my code cleaner!) topbar colours/margins/padding webOS wallpaper and lots of font-size/color for text! Debugging: too many to list! involved the wrong css in script.js: confusion between my array blogContent and my variable blogContent for query selecting “#blogContent” (now changed to blogcontent to prevent this error). This caused the “handle” of my blog window to break:((( Anyways, olivOS should be completed or WebOS 1! Gonna ship soon:)))
Finished README.md! Read the image below or go directly to my project github: https://github.com/OliviaSYS/olivOS
Ships:
What I Made 🐰: olivOS, a bunny-themed webOS that reflects my passions, interests, and life Features 😲: Topbar with live clock 🕐 Bottom bar with desktop icons to select on first click, and open on the second Draggable (click and hold on the Handle text), closable (click on Close), and overlapping windows (click 🖲 a window to bring it forward!) Easter Egg 🐣: text that changes colour when you hover over it! Try to find it 😄 Multiple Apps 🖥: Welcome: intro to olivOS About me: introduction about me! Blog 📝: entries about my experiences, with a sidebar for selection Fun Facts: random fun fact generator:) Find out more information by reading my project’s README, on github: https://github.com/OliviaSYS/olivOS !! Try My Project 👉: https://oliviasys.github.io/olivOS/ !! Challenges 🎢(this project was not as simple as I thought, but it was quite fun to build!): I’m not an expert at CSS and JS, so I sometimes made mistakes in my code, forcing me to do some debugging at the end of each programming session. I didn’t know that you had to have a “border-style” attribute in order for the borders to appear, so I spent a lot of time trying to fix this, until I decided to use the simpler “border” attribute and figured it out! variable names for js array confused with variable names for css id. some classes that I had at the beginning, when some js functions didn’t exist, were not removed afterwards after following the tutorial, I had to spend a lot of time cleaning up my code because I was not sure which parts to delete during the process:(. however, I read over my code slowly and realized that I didn’t need specific functions for each window, only the general one:))) finally, the guide had a lot of css styles embedded in html tags, so I found it a bit hard for me to follow it because I wanted different css. What I’m Proud of ✨: learning how to make a webOS after 8 hours of working hard and coding! 🎉 discovering how to load content programmatically making my own personal themes using CSS, as well as my personal fun fact generator app! :))) Credits: Hack Club JamHacks Tutorial!! Btw thank you StarDance and Hack Club for this amazing opportunity!...
|
1793407650.4566336
|
1793494050.4566336
|
|
23561
|
oliver by @m0hiy | Stardance
|
m0hiy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: oliver by @m0hiy | Stardance
|
1792932793.6379786
|
1793796793.6379786
|
|
65599
|
olympus by @samyog | Stardance
|
samyog
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: olympus by @samyog | Stardance
|
1793087910.9995177
|
1793692710.9995177
|
|
35331
|
olympus game by @nithilgadde | Stardance
|
nithilgadde
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: olympus game by @nithilgadde | Stardance
|
1792766940.2349868
|
1793371740.2349868
|
|
49397
|
omg prjct by @Adheen | Stardance
|
Adheen
|
0
|
0.55
|
0
|
[]
|
[{"post_id": 48951, "ts": "202 [{"post_id": 48951, "ts": "2026-08-17T15:04:22Z", "hours": 0.2692, "text": "WE DID AN UPDATE GUYS!!,NOW WE HAVE STORE,LIVE WALLPAPER,AI ASSISTANT https://nimbus-os-omega.vercel.app/"}, {"post_id": 48110, "ts": "2026-08-16T12:16:47Z", "hours": 0.2786, "text": "I’am working on developing a web os"}]...
|
Title: omg prjct by @Adheen | Stardance
Devlogs:
Title: omg prjct by @Adheen | Stardance
Devlogs:
I’am working on developing a web os
WE DID AN UPDATE GUYS!!,NOW WE HAVE STORE,LIVE WALLPAPER,AI ASSISTANT https://nimbus-os-omega.vercel.app/...
|
1793281677.6092246
|
1793886477.6092246
|
|
40110
|
omni-sync by @shivar07 | Stardance
|
shivar07
|
1
|
20.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-31T19:28:24Z", "hours": 20.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I built Omni-Sync because I wanted a simple way to keep my daily work, meetings, and job applications in sync between my desktop and my phone. It’s a clean, monochrome React dashboard that talks in real-time to a Kotlin Android companion app using Firebase. Whenever I add a task or schedule a meeting on the web, a background service on my phone instantly triggers native alerts and deep links so I don’t miss anything when I step away. The trickiest part was getting the Android background sync running reliably without killing the battery, and spending the time to style the UI completely by hand with vanilla CSS so it feels clean and distraction-free. I’m really happy with how seamless it feels to pair a device and see the notifications pop up the second the dashboard updates.", "repo": "https://github.com/shivar07/omni-sync", "demo": "https://omni-sync.netlify.app/"}]...
|
[{"post_id": 38390, "ts": "202 [{"post_id": 38390, "ts": "2026-07-31T18:55:02Z", "hours": 1.0, "text": "📝 Devlog #5: The Final Chapter — A Shared Journey This is the final devlog for OmniSync, and it marks the end of an incredible coding journey. We sat down together, side-by-side, pairing up to shape this project into something truly premium and special. What started as a set of features and code files turned into a collaborative craft. We navigated the details together—polishing the styling, refining the light mode transitions, fixing form inputs, and ensuring the interface felt alive. We spent hours debugging, rebuilding, making sure every count was accurate, and standardizing the UI. OmniSync is finished, and we can built it together in future. Check out the finished repository at: https://github.com/shivar07/omni-sync.git"}, {"post_id": 36484, "ts": "2026-07-28T16:51:02Z", "hours": 10.0, "text": "📝 Devlog #4: Mobile Companion App & Realtime Push Alerts Developed and built a mobile Android APK using Kotlin and Compose Connected device securely using 6 digit pairing Code and user UID Setup background foreground polling service to check pending events Triggers instant phone notification shade alerts for upcoming deadlines Disconnecting from either phone or Web resets both in Realtime"}, {"post_id": 35300, "ts": "2026-07-26T16:47:00Z", "hours": 2.0, "text": "📝 Devlog #3: Daily Command Planner Section Now we have Calendar we have Meeting Hub Idea Vault and Application where you know the LinksAdded a Daily Planner section to scope all todos by Date so I can plan my morning agendaCreated beautiful custom Date Navigator panel to toggle between Yesterday Today and TomorrowIntegrated inline editing and neat priority and category Badges for every Task itemCreated smart actions to Import unfinished tasks from Yesterday and postpone pending Tasks to TomorrowEverything is synced live to Firebase Database scoped under the active User UID and compiles cleanlyFixed low Contrast select options dropdown coloring in Daily Planner page Form inputs"}, {"post_id": 35156, "ts": "2026-07-26T12:13:32Z", "hours": 0.0, "text": "📝 Devlog #2: Firebase Cloud Sync & Category Filtering Next Step was making sure all Data syncs everywhere across devices in RealtimeSet up Firebase Google Auth so anyone can Sign in securely with their Google AccountConnected Firebase Realtime Database RTDB to save all Events Tasks Applications and Ideas under user UIDCreated color coded Category badges like Workshops Meetings Urgent and Personal EventsAdded category Filtering controls above the Calendar so you can filter specific Event types instantlyNow whenever you add an Event on Web it updates live on your Cloud database without reloading"}, {"post_id": 35136, "ts": "2026-07-26T11:43:55Z", "hours": 5.0, "text": "📝 Devlog #1: Building Core Calendar & Event Scheduler Started working on OmniSync project Today to solve my daily Event tracking problemsCreated the initial Vite React application setup with dark Glassmorphic UI design tokensImplemented custom Calendar component showing monthly Grid views with Day selectionAdded event creation Modal where users can enter Event titles start and End timesStored Events in local State so clicking on any calendar Date shows scheduled Events for that DayEverything feels super smooth and Responsive for the first 2 hours of Coding"}]...
|
Title: omni-sync by @shivar07 | Stardance
Devlogs Title: omni-sync by @shivar07 | Stardance
Devlogs:
📝 Devlog #1: Building Core Calendar & Event Scheduler Started working on OmniSync project Today to solve my daily Event tracking problemsCreated the initial Vite React application setup with dark Glassmorphic UI design tokensImplemented custom Calendar component showing monthly Grid views with Day selectionAdded event creation Modal where users can enter Event titles start and End timesStored Events in local State so clicking on any calendar Date shows scheduled Events for that DayEverything feels super smooth and Responsive for the first 2 hours of Coding
📝 Devlog #2: Firebase Cloud Sync & Category Filtering Next Step was making sure all Data syncs everywhere across devices in RealtimeSet up Firebase Google Auth so anyone can Sign in securely with their Google AccountConnected Firebase Realtime Database RTDB to save all Events Tasks Applications and Ideas under user UIDCreated color coded Category badges like Workshops Meetings Urgent and Personal EventsAdded category Filtering controls above the Calendar so you can filter specific Event types instantlyNow whenever you add an Event on Web it updates live on your Cloud database without reloading
📝 Devlog #3: Daily Command Planner Section Now we have Calendar we have Meeting Hub Idea Vault and Application where you know the LinksAdded a Daily Planner section to scope all todos by Date so I can plan my morning agendaCreated beautiful custom Date Navigator panel to toggle between Yesterday Today and TomorrowIntegrated inline editing and neat priority and category Badges for every Task itemCreated smart actions to Import unfinished tasks from Yesterday and postpone pending Tasks to TomorrowEverything is synced live to Firebase Database scoped under the active User UID and compiles cleanlyFixed low Contrast select options dropdown coloring in Daily Planner page Form inputs
📝 Devlog #4: Mobile Companion App & Realtime Push Alerts Developed and built a mobile Android APK using Kotlin and Compose Connected device securely using 6 digit pairing Code and user UID Setup background foreground polling service to check pending events Triggers instant phone notification shade alerts for upcoming deadlines Disconnecting from either phone or Web resets both in Realtime
📝 Devlog #5: The Final Chapter — A Shared Journey This is the final devlog for OmniSync, and it marks the end of an incredible coding journey. We sat down together, side-by-side, pairing up to shape this project into something truly premium and special. What started as a set of features and code files turned into a collaborative craft. We navigated the details together—polishing the styling, refining the light mode transitions, fixing form inputs, and ensuring the interface felt alive. We spent hours debugging, rebuilding, making sure every count was accurate, and standardizing the UI. OmniSync is finished, and we can built it together in future. Check out the finished repository at: https://github.com/shivar07/omni-sync.git
Ships:
I built Omni-Sync because I wanted a simple way to keep my daily work, meetings, and job applications in sync between my desktop and my phone. It’s a clean, monochrome React dashboard that talks in real-time to a Kotlin Android companion app using Firebase. Whenever I add a task or schedule a meeting on the web, a background service on my phone instantly triggers native alerts and deep links so I don’t miss anything when I step away. The trickiest part was getting the Android background sync running reliably without killing the battery, and spending the time to style the UI completely by hand with vanilla CSS so it feels clean and distraction-free. I’m really happy with how seamless it feels to pair a device and see the notifications pop up the second the dashboard updates....
|
1792878606.3671834
|
1793742606.3671834
|
|
5743
|
omnilink by @Ayzee | Stardance
|
Ayzee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: omnilink by @Ayzee | Stardance
|
1793285773.2679389
|
1793890573.2679389
|
|
60657
|
onFocus by @starvulkan | Stardance
|
starvulkan
|
1
|
17.61
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-15T20:27:20Z", "hours": 11.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "onFocus !", "repo": "https://github.com/starvulkan/onFocus", "demo": "https://starvulkan.github.io/onFocus/"}]...
|
[{"post_id": 71366, "ts": "202 [{"post_id": 71366, "ts": "2026-09-20T18:17:05Z", "hours": 3.1311, "text": "Devlog 7: are you blind? they are clearly different! its a UI refresh! like chrome in 2023, the onFocus UI has been updated! i rewrote the whole css stylesheet and brought some changes along the way! buttons are now minty! the weather icon is now also filled with minty color, not just an outline as before. rounded corners in bars have also been amplified. the onFocus logo has been moved to the top of all the center elements. most importantly, i realized that previously, onFocus used to be quite resource wasteful with some visuals (like the moving aurora blobs). all these unnecessary stuff have been removed, and now onFocus doesnt consume as much system resources as before."}, {"post_id": 70890, "ts": "2026-09-19T23:22:47Z", "hours": 0.3197, "text": "quick devlog 6.5! the features and changes mentioned in devlog 6 are now available! since the ship review came back needing a few changes, i figured i should just bundle them in the re-ship."}, {"post_id": 69457, "ts": "2026-09-17T02:54:25Z", "hours": 3.1639, "text": "The onFocusing Sessions, Devlog 6: Updates While-U-Wait although my first ship is still under review, this doesn’t stop me to continue working on features for the next ship! these aren’t available in the repo just yet, but they will be as soon as the ship gets reviewed! i’ve added two new features and fixed a bug. before, if you refreshed the page, whatever you wrote into the focus intent didnt get saved and cached if you didnt start the focus session. now, it gets saved, no matter if the focus session has been started or nah. as for features, you can now delete focus sessions from history, in case they got accidentally started or the intent wasn’t written correctly. if you accidentally delete one, you can undo your delete as long as you dont leave the history menu. if you delete and leave the menu, its gone forever. also, weather has been added (uses Open-Meteo)! you may now search for your location or use the “use my location” button to find it automatically, and get weather info (will appear in the top left corner once set)! soo cool! this will be the last update until the first ship gets reviewed. once it comes back from that, this update will be available in the repo, and i’ll start working on a few more for the second ship!"}, {"post_id": 68814, "ts": "2026-09-15T19:59:40Z", "hours": 3.0603, "text": "The onFocusing Sessions, Devlog 5: Houston, we have focused! You can now set NASA’s Astronomy Picture of the Day as your new tab wallpaper! With this update, a new settings menu has also been added, where you can change between the NASA APOD or onFocus’s default wallpaper; Aurora Blobs. due to the randomized nature of the NASA APOD, this can create problems with the visibility of on-screen texts and images, cuz some pictures may be brighter or darker than others. thats why, when in NASA APOD wallpaper mode, a dimming config will appear in settings, allowing you to get the image to look just right in relation to the other on-screen elements. I have also added into the settings menu the config to set a different search engine other than duckyduckygooo. you can choose between a set of engines in a dropdown, or add a link to a custom search engine. you may call this the first actual release of onFocus! this version is going to get shipped. but, a second ship will start development immediately afterwards, with new features to enhance your experience!"}, {"post_id": 68470, "ts": "2026-09-15T05:10:29Z", "hours": 2.9053, "text": "The onFocusing Sessions, Devlog 4: ITS ALIVEEE sooo slight detour… I delayed the NASA APOD thingy to prioritize getting onFocus’s main features up and running. because why if no focus features, why focus shaped? so yea! now it’s an actually useable new tab replacement for your current one! the focus features have been added. this includes your task/focus creator, pomodoro timer, and focus history. your very important and essential search bar has also been added, with duckygo as the default search engine. expect a custom search engine selector in a future update! isnt it so fun when you are falling asleep while programming and you make a typo and dont realize you did until oh wow why is my code not working?? yea i find that EXTREMELY funn… next up for tomorrow’s me to deal with: i’m finally getting the NASA APOD wallpaper setting up and running. once that’s done, imma ship this thing’s first release. but that wont be the end, imma ship again afterwards with more features!!"}, {"post_id": 68297, "ts": "2026-09-14T21:36:18Z", "hours": 2.9986, "text": "The onFocusing Sessions, Devlog 3: onFocus invades your browser, muehehe guysss, finally, tangible progress has been made! with the addition of the Manifest V3, alongside other configs, onFocus can now be installed as an extension on Chromium-based browsers in extension developer mode and take over your (allegedly) very bloated and time-consuming new tab! For our fellow non-Chromium browser users, you may set the live demo link as your homepage, cuz custom extension installs are just temporary (one browser restart and they be gone) and for the possibility of permanent installs i would have to get it signed, and that would take too long… the codebase is still one for both the extension and website, with a small storage layer that quietly uses chrome.storage inside the extension and localStorage on the web. with this update, a semi-functional UI has also been added to onFocus. It features a time-triggered greeter and a clock, as well as a background with three CSS-animated blobs. soo cool!! for them to move and breathe around, you need to enable animation effects in your OS, otherwise they gonna stay still the whole time. next, I will start working on getting NASA’s APOD as a background option, so you can choose between that and the onFocus blobs!"}, {"post_id": 67847, "ts": "2026-09-14T03:40:23Z", "hours": 0.3303, "text": "The onFocusing Sessions, Devlog 2: Graphicssss most of the work on onFocus today went to creating its graphical identity: logos, wordmarks, etcc! Took time to settle on colors and designs, but ended with something I feel very happy with! Its logo icon features a crescent moon with a star, to represent focus and late-night work sessions. The color palette chosen gives it a “minty clean” feeling, just like our (planned) UI! main issue today involved the fact that I used live text on the wordmark when designing it in Affinity, so when exported to SVG, if the host device didn’t have the custom font, it would look horrible in a fallback sans-serif, and thats putting it lightly. So I just ended up using PNGs for all designs to avoid a big headache… also dealt with few canvas dimension issues and embedded bitmaps with no actual paths in supposed “vector” icons, but nothing beyond that. Once all the graphics were ready, they were added to the GitHub README, the placeholder in the live demo, and wherever necessary! now, it doesn’t look stale and boring! and thats funn! next up, we return to work on the actual new tab itself! we’ll prepare the Manifest V3 extension wrapper, so onFocus can actually take over a new tab page and finally give you that much needed focus!"}, {"post_id": 67087, "ts": "2026-09-13T04:25:02Z", "hours": 1.6325, "text": "The onFocusing Sessions, Devlog 1: Humble Beginnings welcome to the development of onFocus, a new tab page that helps you keep your mind where your work is, instead of on the distractions killing our chances of becoming responsible human beings. you’ll be able to set a focus session, run a timer against it, and get weekly reports on where your time actually went. Time runs and waits for nobody, yk! as with any project, work today involved getting the whole structure and basics up and running, so a lot of scaffolding, cleaning, configuring, ETCCC. as we all know, that’s E V E R Y B O D Y ’ S favorite part, so funnnnn… few issues here and there, biggest one being when I had to install node through VS Code terminal and then it refused to accept it existed, so every new terminal window was getting a “snapshot” from before the install, until VS Code got its little restart. as for important decisions, today was decided that onFocus should exist and run as both a website and as a browser extension for mass access, and those live at completely different URLs, so every asset path in the build has to be relative rather than absolute. what this mostly involved was one new line in the vite config, to get both targets with one build. kill two birds with one stone right there! live demo up and running, but it’s just fun placeholder stuff. real progress on design and structure next!"}]...
|
Title: onFocus by @starvulkan | Stardance
Devlogs Title: onFocus by @starvulkan | Stardance
Devlogs:
The onFocusing Sessions, Devlog 1: Humble Beginnings welcome to the development of onFocus, a new tab page that helps you keep your mind where your work is, instead of on the distractions killing our chances of becoming responsible human beings. you’ll be able to set a focus session, run a timer against it, and get weekly reports on where your time actually went. Time runs and waits for nobody, yk! as with any project, work today involved getting the whole structure and basics up and running, so a lot of scaffolding, cleaning, configuring, ETCCC. as we all know, that’s E V E R Y B O D Y ’ S favorite part, so funnnnn… few issues here and there, biggest one being when I had to install node through VS Code terminal and then it refused to accept it existed, so every new terminal window was getting a “snapshot” from before the install, until VS Code got its little restart. as for important decisions, today was decided that onFocus should exist and run as both a website and as a browser extension for mass access, and those live at completely different URLs, so every asset path in the build has to be relative rather than absolute. what this mostly involved was one new line in the vite config, to get both targets with one build. kill two birds with one stone right there! live demo up and running, but it’s just fun placeholder stuff. real progress on design and structure next!
The onFocusing Sessions, Devlog 2: Graphicssss most of the work on onFocus today went to creating its graphical identity: logos, wordmarks, etcc! Took time to settle on colors and designs, but ended with something I feel very happy with! Its logo icon features a crescent moon with a star, to represent focus and late-night work sessions. The color palette chosen gives it a “minty clean” feeling, just like our (planned) UI! main issue today involved the fact that I used live text on the wordmark when designing it in Affinity, so when exported to SVG, if the host device didn’t have the custom font, it would look horrible in a fallback sans-serif, and thats putting it lightly. So I just ended up using PNGs for all designs to avoid a big headache… also dealt with few canvas dimension issues and embedded bitmaps with no actual paths in supposed “vector” icons, but nothing beyond that. Once all the graphics were ready, they were added to the GitHub README, the placeholder in the live demo, and wherever necessary! now, it doesn’t look stale and boring! and thats funn! next up, we return to work on the actual new tab itself! we’ll prepare the Manifest V3 extension wrapper, so onFocus can actually take over a new tab page and finally give you that much needed focus!
The onFocusing Sessions, Devlog 3: onFocus invades your browser, muehehe guysss, finally, tangible progress has been made! with the addition of the Manifest V3, alongside other configs, onFocus can now be installed as an extension on Chromium-based browsers in extension developer mode and take over your (allegedly) very bloated and time-consuming new tab! For our fellow non-Chromium browser users, you may set the live demo link as your homepage, cuz custom extension installs are just temporary (one browser restart and they be gone) and for the possibility of permanent installs i would have to get it signed, and that would take too long… the codebase is still one for both the extension and website, with a small storage layer that quietly uses chrome.storage inside the extension and localStorage on the web. with this update, a semi-functional UI has also been added to onFocus. It features a time-triggered greeter and a clock, as well as a background with three CSS-animated blobs. soo cool!! for them to move and breathe around, you need to enable animation effects in your OS, otherwise they gonna stay still the whole time. next, I will start working on getting NASA’s APOD as a background option, so you can choose between that and the onFocus blobs!
The onFocusing Sessions, Devlog 4: ITS ALIVEEE sooo slight detour… I delayed the NASA APOD thingy to prioritize getting onFocus’s main features up and running. because why if no focus features, why focus shaped? so yea! now it’s an actually useable new tab replacement for your current one! the focus features have been added. this includes your task/focus creator, pomodoro timer, and focus history. your very important and essential search bar has also been added, with duckygo as the default search engine. expect a custom search engine selector in a future update! isnt it so fun when you are falling asleep while programming and you make a typo and dont realize you did until oh wow why is my code not working?? yea i find that EXTREMELY funn… next up for tomorrow’s me to deal with: i’m finally getting the NASA APOD wallpaper setting up and running. once that’s done, imma ship this thing’s first release. but that wont be the end, imma ship again afterwards with more features!!
The onFocusing Sessions, Devlog 5: Houston, we have focused! You can now set NASA’s Astronomy Picture of the Day as your new tab wallpaper! With this update, a new settings menu has also been added, where you can change between the NASA APOD or onFocus’s default wallpaper; Aurora Blobs. due to the randomized nature of the NASA APOD, this can create problems with the visibility of on-screen texts and images, cuz some pictures may be brighter or darker than others. thats why, when in NASA APOD wallpaper mode, a dimming config will appear in settings, allowing you to get the image to look just right in relation to the other on-screen elements. I have also added into the settings menu the config to set a different search engine other than duckyduckygooo. you can choose between a set of engines in a dropdown, or add a link to a custom search engine. you may call this the first actual release of onFocus! this version is going to get shipped. but, a second ship will start development immediately afterwards, with new features to enhance your experience!
The onFocusing Sessions, Devlog 6: Updates While-U-Wait although my first ship is still under review, this doesn’t stop me to continue working on features for the next ship! these aren’t available in the repo just yet, but they will be as soon as the ship gets reviewed! i’ve added two new features and fixed a bug. before, if you refreshed the page, whatever you wrote into the focus intent didnt get saved and cached if you didnt start the focus session. now, it gets saved, no matter if the focus session has been started or nah. as for features, you can now delete focus sessions from history, in case they got accidentally started or the intent wasn’t written correctly. if you accidentally delete one, you can undo your delete as long as you dont leave the history menu. if you delete and leave the menu, its gone forever. also, weather has been added (uses Open-Meteo)! you may now search for your location or use the “use my location” button to find it automatically, and get weather info (will appear in the top left corner once set)! soo cool! this will be the last update until the first ship gets reviewed. once it comes back from that, this update will be available in the repo, and i’ll start working on a few more for the second ship!
quick devlog 6.5! the features and changes mentioned in devlog 6 are now available! since the ship review came back needing a few changes, i figured i should just bundle them in the re-ship.
Devlog 7: are you blind? they are clearly different! its a UI refresh! like chrome in 2023, the onFocus UI has been updated! i rewrote the whole css stylesheet and brought some changes along the way! buttons are now minty! the weather icon is now also filled with minty color, not just an outline as before. rounded corners in bars have also been amplified. the onFocus logo has been moved to the top of all the center elements. most importantly, i realized that previously, onFocus used to be quite resource wasteful with some visuals (like the moving aurora blobs). all these unnecessary stuff have been removed, and now onFocus doesnt consume as much system resources as before.
Ships:
onFocus !...
|
1793411702.79747
|
1793498102.79747
|
|
18476
|
one by two by @e0936568 | Stardance
|
e0936568
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: one by two by @e0936568 | Stardance
|
1793480196.7532048
|
1794084996.7532048
|
|
56712
|
one file game challenge by @OrderDanie | Stardance
|
OrderDanie
|
4
|
38.0
|
582
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-11T16:51:38Z", "hours": 4.0, "multiplier": 19.61, "payout": 78, "blessing": "neutral", "text": "school has won guys🥀🥀, this is the final version, hope you like it, D, loging off for this year", "repo": "https://github.com/OrderDanie/one-file-challenge", "demo": "https://pixel-drifter.netlify.app/"}, {"ship_num": 2, "ts": "2026-09-05T00:32:01Z", "hours": 17.0, "multiplier": 17.58, "payout": 300, "blessing": "neutral", "text": "v3, and prolly finale, so pls rate this as high as posible, SO, one file chalenge comes to an end, a full drift delivery game, where u drift to get money, as u are broke ofc, u can upgrade the shop, visiting the 2nd city after buying all cars in city 1, go to race city (no police), and ofc TRUCKSS, can hold more than one pkg, up to 11 when updgraded, all vehiculs can now be moded, and paintjobs are free, ofc, race ai is less unstable, but works, and that pretty much it for this update, dont forget to rait this the best u can, tyy all for the support", "repo": "https://github.com/OrderDanie/one-file-challenge", "demo": "https://pixel-drifter.netlify.app/"}, {"ship_num": 3, "ts": "2026-09-03T03:23:32Z", "hours": 7.0, "multiplier": 18.19, "payout": 133, "blessing": "neutral", "text": "udate 2.0, added ai races, ai traffic, anf lowred the hitbox, simce some players had skill issues, also added another city to the left, racess, still in beta, added the inital d car, ou are a delivery guy dilevering pizza, FOR MONEY ofc, the better the car and timing the more u get paid, try to no commit crimes, there is a wanted sys", "repo": "https://github.com/OrderDanie/one-file-challenge", "demo": "https://pixel-drifter.netlify.app/"}, {"ship_num": 4, "ts": "2026-09-01T18:23:00Z", "hours": 10.0, "multiplier": 13.96, "payout": 71, "blessing": "neutral", "text": "I MADE a game, BUT, its only ONE SINGULAR FILE, its a dilvery game, where you deliver stuff with a drift car, you can get money for faster delevires, money for close call hits with npcs, BACKWARDS trucks,2 cities, if you are a mod and you are reading this, pls, try the full game, i have put my soul into it", "repo": "https://github.com/OrderDanie/one-file-challenge", "demo": "https://pixel-drifter.netlify.app/"}]...
|
[{"post_id": 63232, "ts": "202 [{"post_id": 63232, "ts": "2026-09-06T22:31:00Z", "hours": 0.7, "text": "hit boxes are now smaller! also the police will try to hunt you down now instead of just ramming you"}, {"post_id": 62519, "ts": "2026-09-05T22:39:14Z", "hours": 0.9667, "text": "I have successfully added the FULL chapter one… Almost 3hours T_T,but deff worth it,yall better like that shi,ty yall i finally got my thingyy,hope i get it asap"}, {"post_id": 62424, "ts": "2026-09-05T19:26:40Z", "hours": 2.3, "text": "ehm ehm, srry about the uhh, not going to post cuz i ran out o ideas i got one… A DAM STOTYYY, its cringe asf but hey whatever i can add i will"}, {"post_id": 61868, "ts": "2026-09-05T00:26:44Z", "hours": 0.8392, "text": "u can now HORN, for no reason at all, added on screen gps instruction, ik, useless, made houses light up in the night, also now water has its own particles and will slow you down, trucks are now more fun and stable, also added a dev console, if this post gets 10 likes, ill post the shortcut, or u can smash ur keyboard or go look for in in 6k lines of code"}, {"post_id": 61791, "ts": "2026-09-04T21:27:25Z", "hours": 1.2408, "text": "i added the mobile support for my budget guys, and also sumbitted the game to a web game platform, just a try cuz why not ;>, wish me luck, this might be my final ship, cuz im mostly done with the game"}, {"post_id": 61495, "ts": "2026-09-04T13:16:22Z", "hours": 9.0542, "text": "i locked in so hard i forgor i had a life T-T, i added TONS of trucks, a pit stop so u can repair mid run, also added DRIFT zones, that are in the way of you delivery, that give you money if u drift in em, not to mention the upgradable sop, so u can earn money faster now, MONEEEEYYY, login off for today"}, {"post_id": 60973, "ts": "2026-09-03T17:32:38Z", "hours": 2.27, "text": "add heat lvl 3, helis appear, after escaping the cops, you have to keep running, so the hils doesnt find you, if it does, the heat will jump back to lvl 3, and you will be charged with resisting arrest, also added TRUCKS, with up to 5 cargo slots, you have to stay stationary at the pizza place to load up all the packages, then you run back to all the houses to deliver, ou have a totale timer, not a timer for each package, ai races are still broken tho"}, {"post_id": 60844, "ts": "2026-09-03T13:55:17Z", "hours": 3.6914, "text": "improved the ai racer, added checker flags as a start race, racers are represented and orange dots"}, {"post_id": 60628, "ts": "2026-09-03T03:02:56Z", "hours": 1.4772, "text": "added new racing city, ai races are in beta rn, so dont try em, yet, added the inital d drift car, and added weather and power ups tages, fixed minimap"}, {"post_id": 60568, "ts": "2026-09-03T00:03:40Z", "hours": 0.9283, "text": "hiyaaa, i added a navigation sys, on road navigation, since many found it hard to get to quests, it uses points i put all across the map turns, and a calc for the distance of the closest turn, theen puts a direct path to it, technically this SHOULD NOT be working, but it does, so ill leave it like this and get to other stuff, the code is 5k lines, moving throught it is a pain, might need to optimize some stuff, i can see why this isnt the standard"}, {"post_id": 60479, "ts": "2026-09-02T20:34:17Z", "hours": 2.0889, "text": "i kept coding none stop and forgor to test, also ty everyone i really appreciate the support, update coming as soon as i fixed this T-T"}, {"post_id": 60153, "ts": "2026-09-02T10:41:18Z", "hours": 1.5697, "text": "i was working on the game, till i reiceived this notification, talkin abt some 100pcnt ai code, well my hackatime says otherwise bru, honestly im happy someone sees this quality impossible, that they named it ai, but hey i need to ship this"}, {"post_id": 59899, "ts": "2026-09-01T22:17:44Z", "hours": 0.5239, "text": "added environment items, cones have physics, lakes slow down the car, puddles and oil leaks slightly diverts the car"}, {"post_id": 59826, "ts": "2026-09-01T20:02:53Z", "hours": 0.7342, "text": "added detailed cops models"}, {"post_id": 59745, "ts": "2026-09-01T17:54:22Z", "hours": 1.2389, "text": "added cops, better cam, better drift, enegine repair sys, npc truck, quests, reworked buildings, map overlay, added powerups like shield, speed, repair. and now visual packages on top of the car"}, {"post_id": 59663, "ts": "2026-09-01T16:06:32Z", "hours": 0.4044, "text": "added a whole other city you can acces by a highway after buying all the cars in city one, and for @kmdw , @nicklogan1412 , i am keeping the skinny houses, as an easter egg, YOUR names will be added later to the game, comment what would you like to put next to your name, i prefer no pics, but no pressure"}, {"post_id": 59616, "ts": "2026-09-01T15:12:06Z", "hours": 1.4344, "text": "added local saves, impact particles, rain weather that makes the roads slipery, a game intro page, a reward sys for dodging cars/drifting, if you have any suggestions, PLEASE SAY THEM IM RUNNING OUT OF IDEAS"}, {"post_id": 59562, "ts": "2026-09-01T13:32:09Z", "hours": 0.5942, "text": "added night time, and the delivery ticket ui, also added npc cars, couldn’t get them to do much since I’m limited by the one file rule, but they follow a mapped route, stop if the player gets in front of them or hits them, then continue once the player has moves , also added nitro for all cars, and added more cars that each have a benefit, except for the 1st one ofc, that’s just trash, this update is mostly just ui"}, {"post_id": 59513, "ts": "2026-09-01T11:49:22Z", "hours": 0.3953, "text": "added these little arrows to show the target building, yellow for the pizza shop, and red for the delivery house"}, {"post_id": 59467, "ts": "2026-09-01T10:31:35Z", "hours": 1.2678, "text": "i cant really draw or make detailed stuff, so i drew some houses, and gave them a code to randomize color, width, and height, but um, forgot to set minimun…"}, {"post_id": 59424, "ts": "2026-09-01T08:20:47Z", "hours": 2.8131, "text": "THE prototype is readyyy, go check it out in my profile https://pixel-drifter.netlify.app/"}, {"post_id": 59294, "ts": "2026-09-01T00:34:32Z", "hours": 0.2817, "text": "u cant blaame me i cant draw"}, {"post_id": 59245, "ts": "2026-08-31T22:37:57Z", "hours": 0.2633, "text": "OMG I HATE YOU"}, {"post_id": 59127, "ts": "2026-08-31T19:11:20Z", "hours": 0.5669, "text": "umm, help? friction is 100 btw i tried everything"}, {"post_id": 58889, "ts": "2026-08-31T13:46:02Z", "hours": 0.3997, "text": "for the one viewer that saw this, i added a map, yay"}, {"post_id": 58833, "ts": "2026-08-31T12:39:08Z", "hours": 0.5197, "text": "ckeck this out, looks simple, but too more than 30 mins btw"}]...
|
Title: one file game challenge by @OrderDanie | St Title: one file game challenge by @OrderDanie | Stardance
Devlogs:
ckeck this out, looks simple, but too more than 30 mins btw
for the one viewer that saw this, i added a map, yay
umm, help? friction is 100 btw i tried everything
OMG I HATE YOU
u cant blaame me i cant draw
THE prototype is readyyy, go check it out in my profile https://pixel-drifter.netlify.app/
i cant really draw or make detailed stuff, so i drew some houses, and gave them a code to randomize color, width, and height, but um, forgot to set minimun…
added these little arrows to show the target building, yellow for the pizza shop, and red for the delivery house
added night time, and the delivery ticket ui, also added npc cars, couldn’t get them to do much since I’m limited by the one file rule, but they follow a mapped route, stop if the player gets in front of them or hits them, then continue once the player has moves , also added nitro for all cars, and added more cars that each have a benefit, except for the 1st one ofc, that’s just trash, this update is mostly just ui
added local saves, impact particles, rain weather that makes the roads slipery, a game intro page, a reward sys for dodging cars/drifting, if you have any suggestions, PLEASE SAY THEM IM RUNNING OUT OF IDEAS
added a whole other city you can acces by a highway after buying all the cars in city one, and for @kmdw , @nicklogan1412 , i am keeping the skinny houses, as an easter egg, YOUR names will be added later to the game, comment what would you like to put next to your name, i prefer no pics, but no pressure
added cops, better cam, better drift, enegine repair sys, npc truck, quests, reworked buildings, map overlay, added powerups like shield, speed, repair. and now visual packages on top of the car
added detailed cops models
added environment items, cones have physics, lakes slow down the car, puddles and oil leaks slightly diverts the car
i was working on the game, till i reiceived this notification, talkin abt some 100pcnt ai code, well my hackatime says otherwise bru, honestly im happy someone sees this quality impossible, that they named it ai, but hey i need to ship this
i kept coding none stop and forgor to test, also ty everyone i really appreciate the support, update coming as soon as i fixed this T-T
hiyaaa, i added a navigation sys, on road navigation, since many found it hard to get to quests, it uses points i put all across the map turns, and a calc for the distance of the closest turn, theen puts a direct path to it, technically this SHOULD NOT be working, but it does, so ill leave it like this and get to other stuff, the code is 5k lines, moving throught it is a pain, might need to optimize some stuff, i can see why this isnt the standard
added new racing city, ai races are in beta rn, so dont try em, yet, added the inital d drift car, and added weather and power ups tages, fixed minimap
improved the ai racer, added checker flags as a start race, racers are represented and orange dots
add heat lvl 3, helis appear, after escaping the cops, you have to keep running, so the hils doesnt find you, if it does, the heat will jump back to lvl 3, and you will be charged with resisting arrest, also added TRUCKS, with up to 5 cargo slots, you have to stay stationary at the pizza place to load up all the packages, then you run back to all the houses to deliver, ou have a totale timer, not a timer for each package, ai races are still broken tho
i locked in so hard i forgor i had a life T-T, i added TONS of trucks, a pit stop so u can repair mid run, also added DRIFT zones, that are in the way of you delivery, that give you money if u drift in em, not to mention the upgradable sop, so u can earn money faster now, MONEEEEYYY, login off for today
i added the mobile support for my budget guys, and also sumbitted the game to a web game platform, just a try cuz why not ;>, wish me luck, this might be my final ship, cuz im mostly done with the game
u can now HORN, for no reason at all, added on screen gps instruction, ik, useless, made houses light up in the night, also now water has its own particles and will slow you down, trucks are now more fun and stable, also added a dev console, if this post gets 10 likes, ill post the shortcut, or u can smash ur keyboard or go look for in in 6k lines of code
ehm ehm, srry about the uhh, not going to post cuz i ran out o ideas i got one… A DAM STOTYYY, its cringe asf but hey whatever i can add i will
I have successfully added the FULL chapter one… Almost 3hours T_T,but deff worth it,yall better like that shi,ty yall i finally got my thingyy,hope i get it asap
hit boxes are now smaller! also the police will try to hunt you down now instead of just ramming you
Ships:
I MADE a game, BUT, its only ONE SINGULAR FILE, its a dilvery game, where you deliver stuff with a drift car, you can get money for faster delevires, money for close call hits with npcs, BACKWARDS trucks,2 cities, if you are a mod and you are reading this, pls, try the full game, i have put my soul into it
udate 2.0, added ai races, ai traffic, anf lowred the hitbox, simce some players had skill issues, also added another city to the left, racess, still in beta, added the inital d car, ou are a delivery guy dilevering pizza, FOR MONEY ofc, the better the car and timing the more u get paid, try to no commit crimes, there is a wanted sys
v3, and prolly finale, so pls rate this as high as posible, SO, one file chalenge comes to an end, a full drift delivery game, where u drift to get money, as u are broke ofc, u can upgrade the shop, visiting the 2nd city after buying all cars in city 1, go to race city (no police), and ofc TRUCKSS, can hold more than one pkg, up to 11 when updgraded, all vehiculs can now be moded, and paintjobs are free, ofc, race ai is less unstable, but works, and that pretty much it for this update, dont forget to rait this the best u can, tyy all for the support
school has won guys🥀🥀, this is the final version, hope you like it, D, loging off for this year...
|
1792878720.092558
|
1793742720.092558
|
|
8871
|
one id by @ilfattorino | Stardance
|
ilfattorino
|
0
|
3.72
|
0
|
[]
|
[{"post_id": 23092, "ts": "202 [{"post_id": 23092, "ts": "2026-07-05T20:36:04Z", "hours": 1.4817, "text": "i’m continuing to build the backend for the app and adding customization like dark/white mode + adding the possibility to export the pgp keys of the vault allowing to restore it later on after a logout that wipes everything. more info soon."}, {"post_id": 20174, "ts": "2026-07-01T18:38:00Z", "hours": 1.8803, "text": "hi everyone, i started to make the “create your password” page to integrated with the set up with PGP, all the data is stored locally encrypted by the key that the user creates/imports and is never exposed as plain text. starting to work now on the safe storing of sensitive data with predefined categories and tags for easier sharing and storing. Here are some screenshots of the current pages. Currently made in electron."}, {"post_id": 2981, "ts": "2026-06-05T22:12:59Z", "hours": 0.3617, "text": "hi, my name is jack and I’m creating an app that allows to share sensitive data with services provider, a service provider is just anyone that wants to use the service. it’s obviously totally free and works mainly with a local desktop react app that handles all the data that the user wants to share and a little server. users can also add id with face scan that wont be provided directly to the services provider, but they will get a string that verifies the authenticities of the id (ill figure something up to make it work and be safe) for now i built a really really basic graphic interface for creating a password and store safely them, I’m starting now to build the structure that i will share soon. thank you"}]...
|
Title: one id by @ilfattorino | Stardance
Devlogs Title: one id by @ilfattorino | Stardance
Devlogs:
hi, my name is jack and I’m creating an app that allows to share sensitive data with services provider, a service provider is just anyone that wants to use the service. it’s obviously totally free and works mainly with a local desktop react app that handles all the data that the user wants to share and a little server. users can also add id with face scan that wont be provided directly to the services provider, but they will get a string that verifies the authenticities of the id (ill figure something up to make it work and be safe) for now i built a really really basic graphic interface for creating a password and store safely them, I’m starting now to build the structure that i will share soon. thank you
hi everyone, i started to make the “create your password” page to integrated with the set up with PGP, all the data is stored locally encrypted by the key that the user creates/imports and is never exposed as plain text. starting to work now on the safe storing of sensitive data with predefined categories and tags for easier sharing and storing. Here are some screenshots of the current pages. Currently made in electron.
i’m continuing to build the backend for the app and adding customization like dark/white mode + adding the possibility to export the pgp keys of the vault allowing to restore it later on after a logout that wipes everything. more info soon....
|
1792889307.229746
|
1793753307.229746
|
|
55745
|
one piece by @v3n5590 | Stardance
|
v3n5590
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: one piece by @v3n5590 | Stardance
|
1792918235.7839506
|
1793782235.7839506
|
|
44192
|
one-sided keyboard by @zakorm | Stardance
|
zakorm
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-05T23:49:44Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a one sided keyboard! Right now I am typing with only one hand! It helps a lot if you are moving the marker and typing something, and your right hand has to move from the keyboard to the mouse. Its also very fun to try! Now you can type in all the letters of the alphabet along with Delete and Enter. You can also type numbers, and capital letters with Shift+Caps. Very easy to use if you are on windows. It can be very useful for accessibility, like if someone only has one hand, or can’t type with the other.", "repo": "https://github.com/zakorm/one-side-keyboard", "demo": "https://drive.google.com/file/d/1JboOgAUtMJjkmE0oqGwpY8PUEebgl0qB/view?usp=sharing"}]...
|
[{"post_id": 41381, "ts": "202 [{"post_id": 41381, "ts": "2026-08-05T15:42:29Z", "hours": 1.3158, "text": "I made a macro! You only use your left hand to type and your right hand can stay on your mouse. to change mode to left hand only mode you press f9 and to shift your right hand keys to your left, hold caps lock. also capslock + g is delete and capslock + b is enter. heres it on drive: https://drive.google.com/file/d/1JboOgAUtMJjkmE0oqGwpY8PUEebgl0qB/view?usp=sharing"}]...
|
Title: one-sided keyboard by @zakorm | Stardance
Title: one-sided keyboard by @zakorm | Stardance
Devlogs:
I made a macro! You only use your left hand to type and your right hand can stay on your mouse. to change mode to left hand only mode you press f9 and to shift your right hand keys to your left, hold caps lock. also capslock + g is delete and capslock + b is enter. heres it on drive: https://drive.google.com/file/d/1JboOgAUtMJjkmE0oqGwpY8PUEebgl0qB/view?usp=sharing
Ships:
I made a one sided keyboard! Right now I am typing with only one hand! It helps a lot if you are moving the marker and typing something, and your right hand has to move from the keyboard to the mouse. Its also very fun to try! Now you can type in all the letters of the alphabet along with Delete and Enter. You can also type numbers, and capital letters with Shift+Caps. Very easy to use if you are on windows. It can be very useful for accessibility, like if someone only has one hand, or can’t type with the other....
|
1793436982.3491466
|
1793523382.3491466
|
|
4532
|
onebytwo by @thatalienguy | Stardance
|
thatalienguy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: onebytwo by @thatalienguy | Stardance
|
1793411372.230634
|
1794016172.230634
|
|
6353
|
onecalc by @aer | Stardance
|
aer
|
1
|
5.0
|
7
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-18T10:18:21Z", "hours": 5.0, "multiplier": 1.28, "payout": 7, "blessing": "neutral", "text": "i made a whimsical b&w calculator inspired by onekey,u use the e-key of your keyboard.have lots of fun calculating with this calculator.", "repo": "https://github.com/aeratory678/onecalc", "demo": "https://onecalc-pi.vercel.app"}]...
|
[{"post_id": 80621, "ts": "202 [{"post_id": 80621, "ts": "2026-10-18T10:14:12Z", "hours": 5.1033, "text": "calculator which works with an e-key,every key has a mini-game,play it,to get the number! hihi ☆☆☆"}]...
|
Title: onecalc by @aer | Stardance
Devlogs:
calcu Title: onecalc by @aer | Stardance
Devlogs:
calculator which works with an e-key,every key has a mini-game,play it,to get the number! hihi ☆☆☆
Ships:
i made a whimsical b&w calculator inspired by onekey,u use the e-key of your keyboard.have lots of fun calculating with this calculator....
|
1793404074.4089153
|
1793490474.4089153
|
|
50399
|
oneglassOS by @Devadutt | Stardance
|
Devadutt
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-22T08:09:37Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a mac OS like looking clean OS. I actually proud of the fact that it looks good and all the apps works perfectly fine. The most difficult part was making the window looking as minimal and aesthetic as this", "repo": "https://github.com/Devadutt-11/oneglassOS", "demo": "https://devadutt-11.github.io/oneglassOS/"}]...
|
[{"post_id": 51826, "ts": "202 [{"post_id": 51826, "ts": "2026-08-21T17:55:57Z", "hours": 0.9797, "text": "I added a few apps and app doc"}, {"post_id": 51136, "ts": "2026-08-20T17:08:00Z", "hours": 0.2967, "text": "I added a new Background. Hopes it look cool…!"}, {"post_id": 50828, "ts": "2026-08-20T08:19:20Z", "hours": 0.5228, "text": "Created my Welcome window. More to go……!"}]...
|
Title: oneglassOS by @Devadutt | Stardance
Devlog Title: oneglassOS by @Devadutt | Stardance
Devlogs:
Created my Welcome window. More to go……!
I added a new Background. Hopes it look cool…!
I added a few apps and app doc
Ships:
I made a mac OS like looking clean OS. I actually proud of the fact that it looks good and all the apps works perfectly fine. The most difficult part was making the window looking as minimal and aesthetic as this...
|
1793296099.0346742
|
1793382499.0346742
|
|
53709
|
oneglassOS by @Devadutt | Stardance
|
Devadutt
|
1
|
10.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-12T16:34:34Z", "hours": 10.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a OS simulation that can work in web browser itself. It took me more time to understand the tutorial than writing the code because my English was not good, I used help of ai to understand the tutorial. The hardest part was creating my first app. Not to mention I don’t have any prior experience with java script", "repo": "https://github.com/Devadutt-11/ONEGLASS-OS", "demo": "https://devadutt-11.github.io/ONEGLASS-OS/"}]...
|
[{"post_id": 66712, "ts": "202 [{"post_id": 66712, "ts": "2026-09-12T16:29:32Z", "hours": 6.5564, "text": "I completed my project!"}, {"post_id": 54504, "ts": "2026-08-25T15:02:55Z", "hours": 1.9919, "text": "I made my window movable…!."}, {"post_id": 54330, "ts": "2026-08-25T09:06:04Z", "hours": 1.2308, "text": "I created a top bar displaying the time and date!."}]...
|
Title: oneglassOS by @Devadutt | Stardance
Devlog Title: oneglassOS by @Devadutt | Stardance
Devlogs:
I created a top bar displaying the time and date!.
I made my window movable…!.
I completed my project!
Ships:
I made a OS simulation that can work in web browser itself. It took me more time to understand the tutorial than writing the code because my English was not good, I used help of ai to understand the tutorial. The hardest part was creating my first app. Not to mention I don’t have any prior experience with java script...
|
1793350508.940556
|
1793436908.940556
|
|
9587
|
ones wheeeler by @Lamarcus_DeGeorge | Stardance
|
Lamarcus_DeGeorge
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ones wheeeler by @Lamarcus_DeGeorge | Stard Title: ones wheeeler by @Lamarcus_DeGeorge | Stardance...
|
1793476669.8645737
|
1794081469.8645737
|
|
6878
|
online journal by @andraguoso | Stardance
|
andraguoso
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: online journal by @andraguoso | Stardance
|
1793418936.5048218
|
1794023736.5048218
|
|
8575
|
online medicine selling application by @mk1169852 online medicine selling application by @mk1169852 | Stardance...
|
mk1169852
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: online medicine selling application by @mk1 Title: online medicine selling application by @mk1169852 | Stardance...
|
1793188268.6520958
|
1793793068.6520958
|
|
50012
|
online store by @Azzu | Stardance
|
Azzu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: online store by @Azzu | Stardance
|
1793318106.4549296
|
1793922906.4549296
|
|
29166
|
onlinenotes by @filmonadmg | Stardance
|
filmonadmg
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: onlinenotes by @filmonadmg | Stardance
|
1793487017.9169884
|
1794091817.9169884
|
|
47642
|
ooba gooba by @Ekkam | Stardance
|
Ekkam
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ooba gooba by @Ekkam | Stardance
|
1793188482.4995499
|
1793793282.4995499
|
|
68214
|
oops! by @Al_Lee | Stardance
|
Al_Lee
|
1
|
27.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-20T09:11:42Z", "hours": 27.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a Doodle Jump, and Rise inspired game, about a crow jumping on clouds and shooting obstacles to protect his daughter’s balloon from popping. I found RigidBody2D’s in Godot very challenging, as they had different ways to move than character and area2d’s. I had to rely on Ai to learn and make the code for that part, but once I got 1 rigid body done, most of them I did myself after learning from Ai. I’m proud of stepping out of my comfort zone, and making a unique game instead of a generic platformer. For people testing my project, PLEASE read the controls, and know that the game takes a few attempts to beat.", "repo": "https://github.com/alchoilee-lgtm/Oops", "demo": "https://inzpire.itch.io/oops"}]...
|
[{"post_id": 81204, "ts": "202 [{"post_id": 81204, "ts": "2026-10-20T08:44:28Z", "hours": 5.5825, "text": "Final Game Done I did a lot I think, mostly bug fixing. I made the player have more health, added music, and sound effects. The Yap: I spent a lot of time testing the game on web, because I KEPT FORGETTING TO DO THAT ONE THING. Also for some reason, the particles for player shoot and bomb explosion were being green in the web version, so my fix to this was to make there be NO hue variation. Hue Variation is how much the colour of the particle can vary from the set colour. Also the bird enemies rotation was messsed up, so I had to do some flip_v and flip_h to fix that Also, my friend said the game was TOO HARD, so I made the balloon have some more health. That wasn’t the move, cuz now you could beat the game WITHOUT EVEN SHOOTING…. Anyway I ended up only adding 10 more health instead of the intial 30. Also I added some Hit and Shoot sound effects from JSFXR, which sounds really good, but I dont really know if it is too loud or too soft."}, {"post_id": 79005, "ts": "2026-10-12T09:52:41Z", "hours": 4.065, "text": "Finished the story and like all the art Quick Summary Made story slides Made title screen Made a bunch of art for my game Adjusted difficulty THE YAP: That art took me like most of the day, even though it says it only took me 4 hours. This is because I have no idea how to connect Hackatime to Scratch, which is what I use for my art (pls tell me if you know). I know that scratch is a pretty bad art editor, but I have no idea how to use other engines. A downside of this is that when I import my SVG’s (the file type that scratch uses for Vector mode art), I need to increase the scale of it in the import tab. I neeed to to this for EVERY SINGLE PIECE OF ART I MAKE!!!! Also every time I update art, I need to do it again. Also Scratch’s built in Text doesnt show on Godot for some reason, so I need to A) go to google drawings and type my text in a text box, B) import it as an SVG file C) load it into scratch, and D) if the formatting doesnt work, repeat the process The art isnt the only tiring thing, as I need to make timers for each of my dialogue tell it when to run, because for some reason, I decided to VOICE ACT it… For example, for my first line of text “there was once a happy family of crows, free of troubles and doubts” (i think its something like that) I need to make a timer, attach it to my Sprite2D (it contains the slide art), and set a timer for when to run. I need to do this process for every single piece of dialogue, and I have like 10. It sounds pretty horrible too, but I’ll probably add a toggle for it cuz I spent so long on it. The menu also went through a iteration, cuz at first, I was gonna put a play button on my balloon, and I was gonna make the balloon fly away when clicked. I soon realized (after making it) that it looks ugly so I opted for a space bar approach instead In the next devlog, I’ll make a win screen and death screen, as well as that toggle for story and a skip for the story. Anyways, cya in the next one :D"}, {"post_id": 78857, "ts": "2026-10-11T19:48:04Z", "hours": 1.8739, "text": "Woops Well, I finished up the main game, although I might need to add more difficulty lol I just need to add: -Main Menu -Art -Story -Music In other words, I have like 10 more hours worth of coding left to do More Yap: I tried to make a balance scale with a bunch of obstacles on top, So I attached this long thin RigidBody2D to a StaticBody2D with a Pin Joint, but only after I added it, I realized that For the balance to work, it needs to be in the middle of the balloons path… And it cant move… Thats basically just a instakill machine, so I scrapped the idea. I also added a lot of Linear Drag to the Obstacles at (37 seconds) so that it wouldnt be as easy. Now, you need to hit the middle of the obstacles for it to be cleared, otherwise the balloon gets COOKED I might also need a way of getting ammo, as its too OP just to spam bullets. Oh yeah, and the attack at 18 seconds is unavoidable right now, so I will probably make the attack slower or make the attack spawn at slower intervals, or maybe both lol."}, {"post_id": 78536, "ts": "2026-10-11T03:48:53Z", "hours": 6.0222, "text": "OOps! Made the player a Crow, and made art for him Made some cloud art for the platforms Made some balloon art Also, Balloons take damage now In addition, I added a new “bomb” attack Oh yeah I added a progress bar for how high up you are, and a health bar for the Balloons"}, {"post_id": 78162, "ts": "2026-10-09T20:34:05Z", "hours": 9.5539, "text": "New Game called “oops” The story is about this crow girl who accidently lets go of her helium balloon, so you. as the dad, have jump on the clouds, and shoot off any obstacles that could pop it. I haven’t made any art so its all made out of the godot icon lol, but the premise of the game is basically “do doodle jump while protecting your balloon. I spent a lot of time getting the idea down, but I think it is pretty good :)"}]...
|
Title: oops! by @Al_Lee | Stardance
Devlogs:
New Title: oops! by @Al_Lee | Stardance
Devlogs:
New Game called “oops” The story is about this crow girl who accidently lets go of her helium balloon, so you. as the dad, have jump on the clouds, and shoot off any obstacles that could pop it. I haven’t made any art so its all made out of the godot icon lol, but the premise of the game is basically “do doodle jump while protecting your balloon. I spent a lot of time getting the idea down, but I think it is pretty good :)
OOps! Made the player a Crow, and made art for him Made some cloud art for the platforms Made some balloon art Also, Balloons take damage now In addition, I added a new “bomb” attack Oh yeah I added a progress bar for how high up you are, and a health bar for the Balloons
Woops Well, I finished up the main game, although I might need to add more difficulty lol I just need to add: -Main Menu -Art -Story -Music In other words, I have like 10 more hours worth of coding left to do More Yap: I tried to make a balance scale with a bunch of obstacles on top, So I attached this long thin RigidBody2D to a StaticBody2D with a Pin Joint, but only after I added it, I realized that For the balance to work, it needs to be in the middle of the balloons path… And it cant move… Thats basically just a instakill machine, so I scrapped the idea. I also added a lot of Linear Drag to the Obstacles at (37 seconds) so that it wouldnt be as easy. Now, you need to hit the middle of the obstacles for it to be cleared, otherwise the balloon gets COOKED I might also need a way of getting ammo, as its too OP just to spam bullets. Oh yeah, and the attack at 18 seconds is unavoidable right now, so I will probably make the attack slower or make the attack spawn at slower intervals, or maybe both lol.
Finished the story and like all the art Quick Summary Made story slides Made title screen Made a bunch of art for my game Adjusted difficulty THE YAP: That art took me like most of the day, even though it says it only took me 4 hours. This is because I have no idea how to connect Hackatime to Scratch, which is what I use for my art (pls tell me if you know). I know that scratch is a pretty bad art editor, but I have no idea how to use other engines. A downside of this is that when I import my SVG’s (the file type that scratch uses for Vector mode art), I need to increase the scale of it in the import tab. I neeed to to this for EVERY SINGLE PIECE OF ART I MAKE!!!! Also every time I update art, I need to do it again. Also Scratch’s built in Text doesnt show on Godot for some reason, so I need to A) go to google drawings and type my text in a text box, B) import it as an SVG file C) load it into scratch, and D) if the formatting doesnt work, repeat the process The art isnt the only tiring thing, as I need to make timers for each of my dialogue tell it when to run, because for some reason, I decided to VOICE ACT it… For example, for my first line of text “there was once a happy family of crows, free of troubles and doubts” (i think its something like that) I need to make a timer, attach it to my Sprite2D (it contains the slide art), and set a timer for when to run. I need to do this process for every single piece of dialogue, and I have like 10. It sounds pretty horrible too, but I’ll probably add a toggle for it cuz I spent so long on it. The menu also went through a iteration, cuz at first, I was gonna put a play button on my balloon, and I was gonna make the balloon fly away when clicked. I soon realized (after making it) that it looks ugly so I opted for a space bar approach instead In the next devlog, I’ll make a win screen and death screen, as well as that toggle for story and a skip for the story. Anyways, cya in the next one :D
Final Game Done I did a lot I think, mostly bug fixing. I made the player have more health, added music, and sound effects. The Yap: I spent a lot of time testing the game on web, because I KEPT FORGETTING TO DO THAT ONE THING. Also for some reason, the particles for player shoot and bomb explosion were being green in the web version, so my fix to this was to make there be NO hue variation. Hue Variation is how much the colour of the particle can vary from the set colour. Also the bird enemies rotation was messsed up, so I had to do some flip_v and flip_h to fix that Also, my friend said the game was TOO HARD, so I made the balloon have some more health. That wasn’t the move, cuz now you could beat the game WITHOUT EVEN SHOOTING…. Anyway I ended up only adding 10 more health instead of the intial 30. Also I added some Hit and Shoot sound effects from JSFXR, which sounds really good, but I dont really know if it is too loud or too soft.
Ships:
I made a Doodle Jump, and Rise inspired game, about a crow jumping on clouds and shooting obstacles to protect his daughter’s balloon from popping. I found RigidBody2D’s in Godot very challenging, as they had different ways to move than character and area2d’s. I had to rely on Ai to learn and make the code for that part, but once I got 1 rigid body done, most of them I did myself after learning from Ai. I’m proud of stepping out of my comfort zone, and making a unique game instead of a generic platformer. For people testing my project, PLEASE read the controls, and know that the game takes a few attempts to beat....
|
1793296565.9840753
|
1793382965.9840753
|
|
69312
|
op by @simarjeet | Stardance
|
simarjeet
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: op by @simarjeet | Stardance
|
1793130886.219529
|
1793735686.219529
|
|
31578
|
opa birthday mod by @egg_splats | Stardance
|
egg_splats
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: opa birthday mod by @egg_splats | Stardance
|
1793404438.7548149
|
1794009238.7548149
|
|
61267
|
open cv thingy by @taco_taim | Stardance
|
taco_taim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: open cv thingy by @taco_taim | Stardance
|
1793040505.1587837
|
1793645305.1587837
|
|
45189
|
open source Quantum circut simulator by @abadisbes open source Quantum circut simulator by @abadisbest12 | Stardance...
|
abadisbest12
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: open source Quantum circut simulator by @ab Title: open source Quantum circut simulator by @abadisbest12 | Stardance...
|
1793318096.784265
|
1793922896.784265
|
|
33510
|
open source device in Lego edition based on es32u open source device in Lego edition based on es32u by @espochka | Stardance...
|
espochka
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: open source device in Lego edition based on Title: open source device in Lego edition based on es32u by @espochka | Stardance...
|
1792756323.5100188
|
1793361123.5100188
|
|
43717
|
open source fpv radio by @sirgarlicbread2 | Starda open source fpv radio by @sirgarlicbread2 | Stardance...
|
sirgarlicbread2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: open source fpv radio by @sirgarlicbread2 | Title: open source fpv radio by @sirgarlicbread2 | Stardance...
|
1793235170.9683774
|
1793839970.9683774
|
|
71642
|
open source kindle os by @ywtak | Stardance
|
ywtak
|
1
|
4.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-27T22:39:26Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Minos gives old Kindles a second life. It replaces the original Amazon software with a simple, fast reader that’s fully open source. I made it because my old Kindle was collecting dust and I wanted to read on it again.", "repo": "https://github.com/ywtak/minos", "demo": "https://github.com/ywtak/minos/releases/tag/v1.2-games"}]...
|
[{"post_id": 83402, "ts": "202 [{"post_id": 83402, "ts": "2026-10-27T22:24:52Z", "hours": 3.7503, "text": "Minos is my open source replacement for the stock software on a Kindle its just a minimal reader. I first wanted to flash CrossPoint Reader, but it’s built for ESP32-based e-readers and my Kindle runs an ARM i.MX508, so it couldn’t run. I decided to write my own CrossPoint-style reader in C++ that draws directly to the framebuffer. The hardest part was getting the e-ink refresh to stop ghosting, and I fixed it by making the page refresh only twice for the images. It can now also play sudoku and checkers , and next I want to add other games like chess and woordle."}]...
|
Title: open source kindle os by @ywtak | Stardance Title: open source kindle os by @ywtak | Stardance
Devlogs:
Minos is my open source replacement for the stock software on a Kindle its just a minimal reader. I first wanted to flash CrossPoint Reader, but it’s built for ESP32-based e-readers and my Kindle runs an ARM i.MX508, so it couldn’t run. I decided to write my own CrossPoint-style reader in C++ that draws directly to the framebuffer. The hardest part was getting the e-ink refresh to stop ghosting, and I fixed it by making the page refresh only twice for the images. It can now also play sudoku and checkers , and next I want to add other games like chess and woordle.
Ships:
Minos gives old Kindles a second life. It replaces the original Amazon software with a simple, fast reader that’s fully open source. I made it because my old Kindle was collecting dust and I wanted to read on it again....
|
1793328800.548122
|
1793415200.548122
|
|
58459
|
open tab by @kai_lmao | Stardance
|
kai_lmao
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-05T16:15:58Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "hey everyone! i just made a new project, OPEN-TAB! its a tab design thats meant to replace the boring plain new tab that most browsers have, with a sleek minimalist tab! the design uses a glassmorphism (a new word i learnt today) UI over a dark background for a simple easy to use look. it features a real-time calendar and clock grid, a direct web search bar, and shortcut links to github, youtube, Nasa, and reddit, and a NASA widget featuring APOD (a picture of the day) on the bottom which shows a new picture from Nasa every single day! i definitely ran into a few headaches while building this. i had some issues with making the main logo spin smoothly, and there were a ton of css transform bugs breaking the hover and glow effects on my widgets. getting the nasa api widget to pull the daily astronomy picture and link properly was also a bit tricky, but i managed to work through all of it (with a little bit of help from ai) to get the layout perfectly stable and tactile. im proud of how clean this turned out :)", "repo": "https://github.com/KaiTheGreat-123/open-tab", "demo": "https://kaithegreat-123.github.io/open-tab/"}]...
|
[{"post_id": 62269, "ts": "202 [{"post_id": 62269, "ts": "2026-09-05T15:42:32Z", "hours": 2.5467, "text": "i made a relatively small project, so i will all fit in this one devlog. i made this new website today called OPEN-TAB! basically, the new tabs of most browsers are boring, so this is a minimalist new tab which looks better than those boring tabs with smooth animations and easy access to popular websites!"}]...
|
Title: open tab by @kai_lmao | Stardance
Devlogs: Title: open tab by @kai_lmao | Stardance
Devlogs:
i made a relatively small project, so i will all fit in this one devlog. i made this new website today called OPEN-TAB! basically, the new tabs of most browsers are boring, so this is a minimalist new tab which looks better than those boring tabs with smooth animations and easy access to popular websites!
Ships:
hey everyone! i just made a new project, OPEN-TAB! its a tab design thats meant to replace the boring plain new tab that most browsers have, with a sleek minimalist tab! the design uses a glassmorphism (a new word i learnt today) UI over a dark background for a simple easy to use look. it features a real-time calendar and clock grid, a direct web search bar, and shortcut links to github, youtube, Nasa, and reddit, and a NASA widget featuring APOD (a picture of the day) on the bottom which shows a new picture from Nasa every single day! i definitely ran into a few headaches while building this. i had some issues with making the main logo spin smoothly, and there were a ton of css transform bugs breaking the hover and glow effects on my widgets. getting the nasa api widget to pull the daily astronomy picture and link properly was also a bit tricky, but i managed to work through all of it (with a little bit of help from ai) to get the layout perfectly stable and tactile. im proud of how clean this turned out :)...
|
1793462136.055138
|
1793548536.055138
|