|
13001
|
Egg by @Milton | Stardance
|
Milton
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Egg by @Milton | Stardance
|
1793278191.3545182
|
1793882991.3545182
|
|
13002
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792936214.2201192
|
1793800214.2201192
|
|
13003
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792947018.7408893
|
1793811018.7408893
|
|
13004
|
bye by @Ajay22 | Stardance
|
Ajay22
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: bye by @Ajay22 | Stardance
|
1792936391.1424332
|
1793800391.1424332
|
|
13005
|
noth by @Ajay22 | Stardance
|
Ajay22
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: noth by @Ajay22 | Stardance
|
1792925578.6847036
|
1793789578.6847036
|
|
13006
|
Toluene by @smatt | Stardance
|
smatt
|
0
|
44.88
|
0
|
[]
|
[{"post_id": 39800, "ts": "202 [{"post_id": 39800, "ts": "2026-08-03T00:58:30Z", "hours": 6.395, "text": "my safe pointer let me down ;-; turns out i cant use the WindowSafe class so easily. the destructor gets called when an instance needs to be relocated in a vector… now i’m using shared_ptr s again, because i found where the object slicing was happening before! besides troubles with that, i made many writing functions, like hline , or box , or fill . i can also move around with move ! the mainwin has its own instance so i have to handle less edge cases. i also changed names so they are consistent. before i handled echoing and console input with curses.h functions, so i added mine for Tui . there are a bunch more details, but i don’t wanna yap, because they’re not important. what’s important is that i think these functions work, but not in this screenshot!"}, {"post_id": 36765, "ts": "2026-07-29T01:06:33Z", "hours": 2.7853, "text": "drawing and safety? i’ve made drawing functions so tui windows draw in order and properly get their draw() member called! i’ve also put window pointers inside a class which makes sure to delete the pointer AND SET IT TO nullptr when the class is destructed. as a cherry on top InputEvent s have a new bool valid (by default 0) so i know if an input is empty because of an error, or actually means something. i hope it will serve its purpose for now! i also had this neat little bug. ncurses may or may not have encountered an error, but i’m not sure ’cuz of the TESTING!!!!’s…"}, {"post_id": 34405, "ts": "2026-07-25T02:48:52Z", "hours": 3.1603, "text": "rendering and… GDB. today i implemented rendering for tui, tried cleaning up code and documentation, and had trouble with using shared_ptr s to store window references. no lifetime guarantee anymore… i replaced them with regular pointers instead, and ill just give them to the tui, which will also delete them. good for temporary popups and constant visuals! copies or instances within the tui aren’t so robust… i gotta admit though. figuring out shared_ptr s slice classes took me way. too. LONG. in the image below you can see an accurate depiction of how i felt doing that! … in more detail though, i intend the tui to store pointers which point to dynamically allocated windows made with new . however, the pointers will be inside a class, and though the class allows full access to the pointer, the destructor makes sure to delete the store pointer. dynamically allocated windows are good because temporary, unimportant windows (like popups, or a dropdown) can be created locally and just added to the tui, they don’t have to be kept in members or vectors, and they’ll stay alive!! yippers! but if you want a pointer in a member or vector, thats no problem! this is much easier than hacky solutions with shared_ptr s, or instances, let alone copies in the tui… all of that though, just to allow classes which inherit Toluene::Window to override base functions. i think it will be okay, though! woah, uh, this is a bit of a long devlog. it… may be because i’m really unsure whether this “ creative ” solution will work… and cuz i’m angry. and tired"}, {"post_id": 33804, "ts": "2026-07-24T01:05:52Z", "hours": 2.5347, "text": "got windows (as in text boxes) for the tui working. should’ve been like 20 more lines in a couple of minutes, ended up falling into endless debugging hell. call stack did not help one bit. nor did the decompiled library and assembly code. pro tip: always use make_shared() to make shared_ptrs."}, {"post_id": 32668, "ts": "2026-07-21T23:40:48Z", "hours": 3.7739, "text": "so… i have been feeling really demotivated for a long time now, and so i did very little work. mainly because it turns out planning out software is really damn hard, and structuring, and everything is really hard to wrap my head around it. i also have some more personal stuff, like loneliness, to deal with, but that’s not important what IS important is that i know how ill make tui work, and i’ve done a bit of cleaning up, making core stuff, and added more features. they’re minor though i have very little to show, so ill just show a bit of code"}, {"post_id": 15361, "ts": "2026-06-24T23:40:47Z", "hours": 2.9361, "text": "started work on making the text user interface do something. ncurses is a pain to work with, but i managed to get wide characters working too! also, i learnt you can put parameter names in header files… so imma do that now. in the screenshot below you can see unicode working!… and the code is beautiful ."}, {"post_id": 14475, "ts": "2026-06-23T16:36:55Z", "hours": 3.8183, "text": "i spent time in Slovenia, visiting stuff like Vintgar gorge and Planica zipline. boohoo, could’ve used that time for toluene 😒 ok to be fair vintgar is beautiful in retrospect luckily i had my laptop! i cleaned up a lot of code, mostly relating to the audio backend, and now im starting with the tui… and im struggling really hard (just look at the time). … but it’s fine! ill probably handle it…"}, {"post_id": 12233, "ts": "2026-06-19T23:34:56Z", "hours": 1.4408, "text": "SOUND! this program officially makes sound! after looking at raw disassembles, library code and trying out random c++ nonsense, it’s worth it! my audio streams work (although very barebones), and i quickly made a funny sound with interaction :D"}, {"post_id": 12132, "ts": "2026-06-19T20:31:26Z", "hours": 1.5475, "text": "??? i have been trying to get the audio streams to start, but i get some really weird runtime exceptions, or aborts, or something? im trying to debug the issues, but..?"}, {"post_id": 11655, "ts": "2026-06-19T00:10:58Z", "hours": 3.9061, "text": "did a lot of work! a lot of annoying work . its 2:10am . two git commits, for things like making casts, and opening/closing audio stream stuff. i also fixed a function to get audio devices, which was a pain. i can (maybe) successfully open an audio stream with my wrapper!- but it doesn’t make sound yet, gotta add that. my code for everything is a mess, and it’s getting worse, but i’ll get to it one day! before that, here’s a demonstration of some kinda (albeit empty) audio stream coming into existence:"}, {"post_id": 10635, "ts": "2026-06-17T14:22:10Z", "hours": 3.1517, "text": "i am COMPLETELY rethinking my knowledge of c++. i thought i had an idea of what references, or pointers were, and how i should use them, but ive been struggling and procrastinating the last few days because of how confused i am. this is just PAIN! ive done close to NOTHING!"}, {"post_id": 8277, "ts": "2026-06-13T19:23:25Z", "hours": 4.1017, "text": "first tangible progress! modified the inner workings, but you can also now choose a wanted audio api and it will detect devices! making it wasn’t too smooth, seems my c++ knowledge is rustier than i thought… the linker didn’t like what i was doing, especially with constructors and destructors. nonetheless, here is an actual recording of something working :D"}, {"post_id": 7067, "ts": "2026-06-11T20:46:19Z", "hours": 5.3308, "text": "spent 3h tugging with cmake, trying to get it to cooperate, contemplated giving up on libraries altogether, and wanted to just give up on the idea of cross-platform as well. ncurses is a curse. wanted to get help, but too socially anxious to actually ask stuff, and the only time i sent anything i was ignored ;-; . writing the wrapper for a backend audio engine was annoying, i wanna work with RtAudio, but in case i ever wanna switch, i wanna make it easy for myself. unfortunately, that includes a lot of writing, and learning headers, which is something i didnt know i didnt know. i can work with this for now though. heres a successful build message with nice code above :D"}]...
|
Title: Toluene by @smatt | Stardance
Devlogs:
spe Title: Toluene by @smatt | Stardance
Devlogs:
spent 3h tugging with cmake, trying to get it to cooperate, contemplated giving up on libraries altogether, and wanted to just give up on the idea of cross-platform as well. ncurses is a curse. wanted to get help, but too socially anxious to actually ask stuff, and the only time i sent anything i was ignored ;-; . writing the wrapper for a backend audio engine was annoying, i wanna work with RtAudio, but in case i ever wanna switch, i wanna make it easy for myself. unfortunately, that includes a lot of writing, and learning headers, which is something i didnt know i didnt know. i can work with this for now though. heres a successful build message with nice code above :D
first tangible progress! modified the inner workings, but you can also now choose a wanted audio api and it will detect devices! making it wasn’t too smooth, seems my c++ knowledge is rustier than i thought… the linker didn’t like what i was doing, especially with constructors and destructors. nonetheless, here is an actual recording of something working :D
i am COMPLETELY rethinking my knowledge of c++. i thought i had an idea of what references, or pointers were, and how i should use them, but ive been struggling and procrastinating the last few days because of how confused i am. this is just PAIN! ive done close to NOTHING!
did a lot of work! a lot of annoying work . its 2:10am . two git commits, for things like making casts, and opening/closing audio stream stuff. i also fixed a function to get audio devices, which was a pain. i can (maybe) successfully open an audio stream with my wrapper!- but it doesn’t make sound yet, gotta add that. my code for everything is a mess, and it’s getting worse, but i’ll get to it one day! before that, here’s a demonstration of some kinda (albeit empty) audio stream coming into existence:
??? i have been trying to get the audio streams to start, but i get some really weird runtime exceptions, or aborts, or something? im trying to debug the issues, but..?
SOUND! this program officially makes sound! after looking at raw disassembles, library code and trying out random c++ nonsense, it’s worth it! my audio streams work (although very barebones), and i quickly made a funny sound with interaction :D
i spent time in Slovenia, visiting stuff like Vintgar gorge and Planica zipline. boohoo, could’ve used that time for toluene 😒 ok to be fair vintgar is beautiful in retrospect luckily i had my laptop! i cleaned up a lot of code, mostly relating to the audio backend, and now im starting with the tui… and im struggling really hard (just look at the time). … but it’s fine! ill probably handle it…
started work on making the text user interface do something. ncurses is a pain to work with, but i managed to get wide characters working too! also, i learnt you can put parameter names in header files… so imma do that now. in the screenshot below you can see unicode working!… and the code is beautiful .
so… i have been feeling really demotivated for a long time now, and so i did very little work. mainly because it turns out planning out software is really damn hard, and structuring, and everything is really hard to wrap my head around it. i also have some more personal stuff, like loneliness, to deal with, but that’s not important what IS important is that i know how ill make tui work, and i’ve done a bit of cleaning up, making core stuff, and added more features. they’re minor though i have very little to show, so ill just show a bit of code
got windows (as in text boxes) for the tui working. should’ve been like 20 more lines in a couple of minutes, ended up falling into endless debugging hell. call stack did not help one bit. nor did the decompiled library and assembly code. pro tip: always use make_shared() to make shared_ptrs.
rendering and… GDB. today i implemented rendering for tui, tried cleaning up code and documentation, and had trouble with using shared_ptr s to store window references. no lifetime guarantee anymore… i replaced them with regular pointers instead, and ill just give them to the tui, which will also delete them. good for temporary popups and constant visuals! copies or instances within the tui aren’t so robust… i gotta admit though. figuring out shared_ptr s slice classes took me way. too. LONG. in the image below you can see an accurate depiction of how i felt doing that! … in more detail though, i intend the tui to store pointers which point to dynamically allocated windows made with new . however, the pointers will be inside a class, and though the class allows full access to the pointer, the destructor makes sure to delete the store pointer. dynamically allocated windows are good because temporary, unimportant windows (like popups, or a dropdown) can be created locally and just added to the tui, they don’t have to be kept in members or vectors, and they’ll stay alive!! yippers! but if you want a pointer in a member or vector, thats no problem! this is much easier than hacky solutions with shared_ptr s, or instances, let alone copies in the tui… all of that though, just to allow classes which inherit Toluene::Window to override base functions. i think it will be okay, though! woah, uh, this is a bit of a long devlog. it… may be because i’m really unsure whether this “ creative ” solution will work… and cuz i’m angry. and tired
drawing and safety? i’ve made drawing functions so tui windows draw in order and properly get their draw() member called! i’ve also put window pointers inside a class which makes sure to delete the pointer AND SET IT TO nullptr when the class is destructed. as a cherry on top InputEvent s have a new bool valid (by default 0) so i know if an input is empty because of an error, or actually means something. i hope it will serve its purpose for now! i also had this neat little bug. ncurses may or may not have encountered an error, but i’m not sure ’cuz of the TESTING!!!!’s…
my safe pointer let me down ;-; turns out i cant use the WindowSafe class so easily. the destructor gets called when an instance needs to be relocated in a vector… now i’m using shared_ptr s again, because i found where the object slicing was happening before! besides troubles with that, i made many writing functions, like hline , or box , or fill . i can also move around with move ! the mainwin has its own instance so i have to handle less edge cases. i also changed names so they are consistent. before i handled echoing and console input with curses.h functions, so i added mine for Tui . there are a bunch more details, but i don’t wanna yap, because they’re not important. what’s important is that i think these functions work, but not in this screenshot!...
|
1793278387.4259596
|
1793883187.4259596
|
|
13007
|
bye by @Ajay22 | Stardance
|
Ajay22
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: bye by @Ajay22 | Stardance
|
1792914829.329646
|
1793778829.329646
|
|
13008
|
PulseFlow AI by @Vedant_Daga | Stardance
|
Vedant_Daga
|
1
|
16.0
|
134
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-01T15:53:55Z", "hours": 6.0, "multiplier": 19.07, "payout": 134, "blessing": "blessed", "text": "# PulseFlow-AI — A Live Hospital Digital Twin + AI Ops Copilot ## What I Made Basically it's a live \"digital twin\" of a hospital. You watch patients move through the ER, labs, imaging, ICU and wards in real time, and it's all running on a simulation engine (FastAPI + WebSockets) that streams the state to the frontend constantly. On top of that I built an AI copilot that spots bottlenecks and actually recommends staffing changes using OR-Tools optimization + Holt-Winters forecasting. There's also a sandbox where you can throw crises at it (flu outbreak, CT scanner dying, mass casualty) and watch the hospital react. Plus it does shift handoff reports and tracks high-risk patients with AI care plans. The main thing I cared about was making it actually feel like real medical software, not a hackathon toy. So I built the whole UI around a design contract based on HIPAA, FDA Title 21 CFR Part 11 and WCAG 2.1. PHI is hidden by default, there's an auto-logout timer, status is never just a color, and I ripped out every glow/gradient/animation so it's calm to look at on a long shift. Full dark/light mode too. ## What Was Challenging The real-time stuff, honestly. Keeping the frontend in sync with a simulation that never stops updating, over WebSockets, without it lagging or flickering, was a pain. The AI optimization was also tough, getting OR-Tools to give recommendations that actually made sense and then explaining them in plain English. And the dark mode almost killed me lol. All my status cards were hardcoded to light colors so dark mode looked HORRIBLE, and I had to rebuild the entire color system on CSS variable tokens to fix it (213 replacements). ## What I'm Proud Of That it genuinely doesn't feel like a toy. It feels like something you could actually stick in a hospital ops room. Running the copilot, getting a real recommendation, hitting \"Implement\" and watching the metrics actually move is so satisfying. And the compliance stuff isn't just for looks, every choice actually ties back to a real medical standard. ## How To Test It Just open the link and you're in, no setup needed. If you'd rather run it yourself, download everything and follow the instructions in the README. Once you're in, easiest thing is to hit **\"Auto Demo\"** in the sidebar, it's a 1-click walkthrough of the whole thing. After that go trigger a crisis in the **Sandbox** and flip to the **Command Center** to watch it hit the floor plan, run the **AI Copilot** and click Implement to see the numbers move, and toggle dark/light mode in the top right.", "repo": "https://github.com/DagaVedant/PulseFlow-AI", "demo": "https://pulse-flow-mjilr4qso-dagavedants-projects.vercel.app/command-center"}]...
|
[{"post_id": 23508, "ts": "202 [{"post_id": 23508, "ts": "2026-07-06T15:05:31Z", "hours": 0.0, "text": "got everything read to be shipped added pictures updated README with new info cleaned up repo updated project description updated viewing link"}, {"post_id": 23254, "ts": "2026-07-06T03:08:57Z", "hours": 4.0, "text": "largest update yet what i built: removed the entire liquid-glass ui, glass, gradients, cursive headings, wallpaper animations- deleted all the older theme that was AI slop made a clean new navy theme that IIII coded myself- its a flat design, with a nice navy blue background,and some cool fonts like space grotesk and jetbrains mono removed the digital-twin page because it wasn’t even needed anymore fixed a nav bar bug and cleaned up the readme to match all the new changes wrote a run.py that boots backend and frontend together in one command instead of like 10000 commands deleted a bunch of unused old images and docs also removed all the old random things too what broke: basically two times the app wasnt loading at all…it ended up being some old runs that didnt leave the port how i fixed it just killed the programs and restarted everything"}, {"post_id": 22625, "ts": "2026-07-05T05:33:27Z", "hours": 0.0, "text": "big decision no more vibecoding so basically im creating a new basic design because i dont want to make everything look vibecoded its going to be very simple, minimalistic, and just really tabular im going to slowly make it look better as I get better at coding everything myself unlike the previous liquid glass design where I made the design and it was implemented using AI"}, {"post_id": 22318, "ts": "2026-07-04T18:40:50Z", "hours": 0.0, "text": "Quick Fixes revised README demo link and Stardance “Try It Link” rewrote all the devlogs to match my style (mods can you create a way for me to update my ship message from before to show all the new features I added)"}, {"post_id": 22265, "ts": "2026-07-04T17:21:57Z", "hours": 1.0, "text": "What I built: fully remade each page to match the design. Its like a really APPLEish looking liquid glass vibe, an animated background (kinda like the iMac, but a bit different), updated the frosted sidebar look, and made the cool glass cards everywhere command center, patient flow, staffing, clinical, ai insights, and labs were running on fake data before this, so now they run on the backend websocket operations, copilot, and sandbox got the same glass restyle as the others, but it was a lot more work to get the buttons and all the other functions to work properly and actually communicate with the backend changed the 9 sidebar icons from the design, to text tabs, and made the one ur on a greenish color and made them all black instead of gray animated the wallpaperrrrrrrrrrrrrrrr (definitely my favorite part) fully removed all the old files, and cleaned up dead weight and made everything cleaner fixed up the gitignore, ruff_cache was only ignored at the root before, now it’s ignored everywhere it shows up (backend, frontend, root). added coverage/, .turbo/, and *.tmp What broke: when i made the first animation, it was extremely slow and it was wayyy to subtle and i could barely tell if it was moving my second attempt made it look way to active and hectic third try was perfect How I fixed it: rewrote the keyframes with bigger swings and rotation on a ~2.5s loop for the dramatic version, then pulled it back about a third once it felt like too much."}, {"post_id": 21221, "ts": "2026-07-03T01:36:12Z", "hours": 2.0, "text": "what i built picked the new look for the entire website. MacOS Liquid Glass vibes instead of the old clinical AI generated design did it entirely in figma, no code yet, just comps- built out command center as the first full mockup: floating glass panels, frosted cards, gradient canvas behind everything instead of a flat background…LOOKS STRAIGHT OUT OF APPLE HQ trusttttt pulled in a cursive treatment for the wordmark and a tuffff color palette this page is kinda like a reference page yk. Basically imma use this page and then figure out how each of the next few pages are gonna look like## what broke nothing broke since there’s no implementation yet- the actual friction was getting figma to fake something it doesn’t really do natively. so basically Figma doesn’t have a liquid glass feeling or even a backdrop blur refraction type of thing, so to get the cards to look like the PERFECT APPLE FROSTED GLASS, instead of the boring looking like kinda transparent kinda not white box how i fixed it basically kinda faked the entire blur by creating a duplicate of the background behind each of the cards instead of just using the transparency feature. the blur by layering a blurred duplicate of the background behind each card. thats kinda how I got that frosted apple glass type instead of a weird semi-transparent glass look kept a saturated gradient underneath (THE STANDARD IMAC BACKGROUND) so the glass has something to actually pick up color from i basically spent like 30 mins slowly adjusting the opacity by eye until it looked like the goated apple liquid glass look next step is turning this into real webpage instead of just a figma mockup design stages 1. original ui (brown) the starting point. flat, clinical, warm-brown/cream tones with a green accent. it was functional but looked really AI and generic. It didn’t feel like me or anything that I would personally build. 2. first sketch (white) this one was mainly like a way for me to figure out how to lay all the elements out while still keeping that abstract vibe that I like. (HEAVILY BASING IT OFF OF APPLE) . I also cleaned some things up, made it more minimalistic, and made everything to a light/cream. basically, I wanted it to look more and more like an apple product so that it has the clean , sleek design that I love about MacOs. 3. final design (blue, liquid glass) this is my final design. I completely gave up on making it white/cream and decided to make it what I want (A LOT OF BLUE AND THE CLASSIC IMAC BACKGROUND). I made everything with that like liquid glass/frosted effect and basically just built off of the IMAC standard display, MacOS vibes and like the apple minimalism and basically took A LOTTTT OF INSPO from Apple"}, {"post_id": 20815, "ts": "2026-07-02T14:57:21Z", "hours": 3.0, "text": "What I built: gated every REST route under /api/v1 behind one shared bearer token, checked once at the router level so it covers simulation, hospital, and ai endpoints without repeating myself. /health stays open on purpose, load balancers need that. gated the websocket too. ?token= checked before the connection even gets accepted, so trigger_event, update_config, add_bottleneck, remove_bottleneck can’t touch live sim state from some random unauthenticated client anymore. SECRET_KEY finally does something. used to just sit there unreferenced, now it’s the actual credential, and it’s got the startup check it was missing, refuses to boot in production if it’s still the default. also went and built full JWT login with viewer/operator roles along the way, then looked at it and went nah, overkill for a demo hospital sim, and reverted back to the simple shared-secret version. kept the actual gate though, that’s the part that mattered. What broke: first version closed unauthenticated websocket connections with code 4401, except that happens before accept(), and turns out you can’t send a close frame on a connection that was never accepted. so it actually shows up as a plain HTTP 403 on the handshake, not 4401 like the docstring said. wire behavior just didn’t match what I wrote down. also, local dev was quietly broken and I didn’t notice for a bit: the backend’s real default SECRET_KEY didn’t match what .env.example said it was, so a fresh clone would 401 on literally everything out of the box. How I fixed it: checked the 403-vs-4401 thing wasn’t actually a bug, just how Starlette handles closing a connection pre-accept. confirmed it with a real client hitting it with no token, still blocks fine, just not with the close code I expected. left it as-is and fixed the docs instead of chasing a non-issue. for the env mismatch, just made .env.example, .env.local, and the actual python default all agree, then ran the whole thing end to end again, no token, wrong token, right token, until 401s and 200s landed exactly where they should."}, {"post_id": 20047, "ts": "2026-07-01T15:38:03Z", "hours": 2.0, "text": "made pulseflow actually look like medical software so basically before all of this, the entire app looked like a mess of dark neon video game stuff. basically it was a mess of glowing things, random gradients, and felt more like a game then a hospital platform. instead of just redesigning it, i made a design.md file first and actually looked into references like hipaa, fda title 21 cfr part 11, and wcag 2.1. pretty much every design choice came from those what actually changed got rid of all the glow, gradients, and unnecessary animations nurses are already tired during long shifts. they need to read information fast, not watch things moving around. everything respects prefers-reduced-motion now phi is masked by default patient names, dobs, mrns, and other sensitive info all go through a privacymask component and stay hidden until a clinician chooses to reveal them. keeps patient data safe added a visible auto-logout timer the session timeout is always shown in the top bar so clinicians know exactly how much time is left before they’re logged out automatically to protect patient data status is never just color anymore every status uses an icon, text label, and color together, so it’s still easy to understand redesigned critical alerts instead of giant glowing red warnings, they’re now banners that clearly explain what’s wrong without being distracting added dark mode everything works in both light and dark mode without changing how the interface feels. the annoying part dark mode looked terrible a lot of the status cards were hardcoded with light colors like bg-amber-50 , so they ended up looking like pale cream boxes sitting on dark background ended up reworking the entire color system instead of hardcoding colors, i moved every color to css variable tokens ( safe , flag , crit ) so each one automatically changes between light and dark mode. that ended up being 213 replacements across the whole project (it was a LOTTT of work) picked better colors. i went with warm off-white and warm charcoal instead of pure white and pure black so it doesn’t hurt your eyes"}, {"post_id": 5003, "ts": "2026-06-08T17:30:30Z", "hours": 3.0, "text": "PULSEFLOW AI IS FINALLY LIVE Just deployed the full stack today (backend is on Render and frontend is on Vercel). The backend was so easy to get running, only took 10ish mins. MIGHT have forgot that Optional wasn’t imported in the config.py. The frontend was SO MUCH HARDER OMG! first, Vercel blocked the deploy three times because of Next.js 15.0.3 had security vulnerabilities. i just updated to 15.3.3 (this didnt work because it had its own CVE). after that i tried using next@lastest, but then i needed ESLint 9, which broke the entire dependency tree. I used ^15 so npm resolves the latest patched 15.x without jumping major versions. Four deploys, two CVEs, one peer dependency conflict. ahhh this was painful BUT, IT FINALLY WORKS SO IT WAS WORTH IT!!!! (image shows it running on vercel)"}]...
|
Title: PulseFlow AI by @Vedant_Daga | Stardance
D Title: PulseFlow AI by @Vedant_Daga | Stardance
Devlogs:
PULSEFLOW AI IS FINALLY LIVE Just deployed the full stack today (backend is on Render and frontend is on Vercel). The backend was so easy to get running, only took 10ish mins. MIGHT have forgot that Optional wasn’t imported in the config.py. The frontend was SO MUCH HARDER OMG! first, Vercel blocked the deploy three times because of Next.js 15.0.3 had security vulnerabilities. i just updated to 15.3.3 (this didnt work because it had its own CVE). after that i tried using next@lastest, but then i needed ESLint 9, which broke the entire dependency tree. I used ^15 so npm resolves the latest patched 15.x without jumping major versions. Four deploys, two CVEs, one peer dependency conflict. ahhh this was painful BUT, IT FINALLY WORKS SO IT WAS WORTH IT!!!! (image shows it running on vercel)
made pulseflow actually look like medical software so basically before all of this, the entire app looked like a mess of dark neon video game stuff. basically it was a mess of glowing things, random gradients, and felt more like a game then a hospital platform. instead of just redesigning it, i made a design.md file first and actually looked into references like hipaa, fda title 21 cfr part 11, and wcag 2.1. pretty much every design choice came from those what actually changed got rid of all the glow, gradients, and unnecessary animations nurses are already tired during long shifts. they need to read information fast, not watch things moving around. everything respects prefers-reduced-motion now phi is masked by default patient names, dobs, mrns, and other sensitive info all go through a privacymask component and stay hidden until a clinician chooses to reveal them. keeps patient data safe added a visible auto-logout timer the session timeout is always shown in the top bar so clinicians know exactly how much time is left before they’re logged out automatically to protect patient data status is never just color anymore every status uses an icon, text label, and color together, so it’s still easy to understand redesigned critical alerts instead of giant glowing red warnings, they’re now banners that clearly explain what’s wrong without being distracting added dark mode everything works in both light and dark mode without changing how the interface feels. the annoying part dark mode looked terrible a lot of the status cards were hardcoded with light colors like bg-amber-50 , so they ended up looking like pale cream boxes sitting on dark background ended up reworking the entire color system instead of hardcoding colors, i moved every color to css variable tokens ( safe , flag , crit ) so each one automatically changes between light and dark mode. that ended up being 213 replacements across the whole project (it was a LOTTT of work) picked better colors. i went with warm off-white and warm charcoal instead of pure white and pure black so it doesn’t hurt your eyes
What I built: gated every REST route under /api/v1 behind one shared bearer token, checked once at the router level so it covers simulation, hospital, and ai endpoints without repeating myself. /health stays open on purpose, load balancers need that. gated the websocket too. ?token= checked before the connection even gets accepted, so trigger_event, update_config, add_bottleneck, remove_bottleneck can’t touch live sim state from some random unauthenticated client anymore. SECRET_KEY finally does something. used to just sit there unreferenced, now it’s the actual credential, and it’s got the startup check it was missing, refuses to boot in production if it’s still the default. also went and built full JWT login with viewer/operator roles along the way, then looked at it and went nah, overkill for a demo hospital sim, and reverted back to the simple shared-secret version. kept the actual gate though, that’s the part that mattered. What broke: first version closed unauthenticated websocket connections with code 4401, except that happens before accept(), and turns out you can’t send a close frame on a connection that was never accepted. so it actually shows up as a plain HTTP 403 on the handshake, not 4401 like the docstring said. wire behavior just didn’t match what I wrote down. also, local dev was quietly broken and I didn’t notice for a bit: the backend’s real default SECRET_KEY didn’t match what .env.example said it was, so a fresh clone would 401 on literally everything out of the box. How I fixed it: checked the 403-vs-4401 thing wasn’t actually a bug, just how Starlette handles closing a connection pre-accept. confirmed it with a real client hitting it with no token, still blocks fine, just not with the close code I expected. left it as-is and fixed the docs instead of chasing a non-issue. for the env mismatch, just made .env.example, .env.local, and the actual python default all agree, then ran the whole thing end to end again, no token, wrong token, right token, until 401s and 200s landed exactly where they should.
what i built picked the new look for the entire website. MacOS Liquid Glass vibes instead of the old clinical AI generated design did it entirely in figma, no code yet, just comps- built out command center as the first full mockup: floating glass panels, frosted cards, gradient canvas behind everything instead of a flat background…LOOKS STRAIGHT OUT OF APPLE HQ trusttttt pulled in a cursive treatment for the wordmark and a tuffff color palette this page is kinda like a reference page yk. Basically imma use this page and then figure out how each of the next few pages are gonna look like## what broke nothing broke since there’s no implementation yet- the actual friction was getting figma to fake something it doesn’t really do natively. so basically Figma doesn’t have a liquid glass feeling or even a backdrop blur refraction type of thing, so to get the cards to look like the PERFECT APPLE FROSTED GLASS, instead of the boring looking like kinda transparent kinda not white box how i fixed it basically kinda faked the entire blur by creating a duplicate of the background behind each of the cards instead of just using the transparency feature. the blur by layering a blurred duplicate of the background behind each card. thats kinda how I got that frosted apple glass type instead of a weird semi-transparent glass look kept a saturated gradient underneath (THE STANDARD IMAC BACKGROUND) so the glass has something to actually pick up color from i basically spent like 30 mins slowly adjusting the opacity by eye until it looked like the goated apple liquid glass look next step is turning this into real webpage instead of just a figma mockup design stages 1. original ui (brown) the starting point. flat, clinical, warm-brown/cream tones with a green accent. it was functional but looked really AI and generic. It didn’t feel like me or anything that I would personally build. 2. first sketch (white) this one was mainly like a way for me to figure out how to lay all the elements out while still keeping that abstract vibe that I like. (HEAVILY BASING IT OFF OF APPLE) . I also cleaned some things up, made it more minimalistic, and made everything to a light/cream. basically, I wanted it to look more and more like an apple product so that it has the clean , sleek design that I love about MacOs. 3. final design (blue, liquid glass) this is my final design. I completely gave up on making it white/cream and decided to make it what I want (A LOT OF BLUE AND THE CLASSIC IMAC BACKGROUND). I made everything with that like liquid glass/frosted effect and basically just built off of the IMAC standard display, MacOS vibes and like the apple minimalism and basically took A LOTTTT OF INSPO from Apple
What I built: fully remade each page to match the design. Its like a really APPLEish looking liquid glass vibe, an animated background (kinda like the iMac, but a bit different), updated the frosted sidebar look, and made the cool glass cards everywhere command center, patient flow, staffing, clinical, ai insights, and labs were running on fake data before this, so now they run on the backend websocket operations, copilot, and sandbox got the same glass restyle as the others, but it was a lot more work to get the buttons and all the other functions to work properly and actually communicate with the backend changed the 9 sidebar icons from the design, to text tabs, and made the one ur on a greenish color and made them all black instead of gray animated the wallpaperrrrrrrrrrrrrrrr (definitely my favorite part) fully removed all the old files, and cleaned up dead weight and made everything cleaner fixed up the gitignore, ruff_cache was only ignored at the root before, now it’s ignored everywhere it shows up (backend, frontend, root). added coverage/, .turbo/, and *.tmp What broke: when i made the first animation, it was extremely slow and it was wayyy to subtle and i could barely tell if it was moving my second attempt made it look way to active and hectic third try was perfect How I fixed it: rewrote the keyframes with bigger swings and rotation on a ~2.5s loop for the dramatic version, then pulled it back about a third once it felt like too much.
Quick Fixes revised README demo link and Stardance “Try It Link” rewrote all the devlogs to match my style (mods can you create a way for me to update my ship message from before to show all the new features I added)
big decision no more vibecoding so basically im creating a new basic design because i dont want to make everything look vibecoded its going to be very simple, minimalistic, and just really tabular im going to slowly make it look better as I get better at coding everything myself unlike the previous liquid glass design where I made the design and it was implemented using AI
largest update yet what i built: removed the entire liquid-glass ui, glass, gradients, cursive headings, wallpaper animations- deleted all the older theme that was AI slop made a clean new navy theme that IIII coded myself- its a flat design, with a nice navy blue background,and some cool fonts like space grotesk and jetbrains mono removed the digital-twin page because it wasn’t even needed anymore fixed a nav bar bug and cleaned up the readme to match all the new changes wrote a run.py that boots backend and frontend together in one command instead of like 10000 commands deleted a bunch of unused old images and docs also removed all the old random things too what broke: basically two times the app wasnt loading at all…it ended up being some old runs that didnt leave the port how i fixed it just killed the programs and restarted everything
got everything read to be shipped added pictures updated README with new info cleaned up repo updated project description updated viewing link
Ships:
# PulseFlow-AI — A Live Hospital Digital Twin + AI Ops Copilot ## What I Made Basically it's a live "digital twin" of a hospital. You watch patients move through the ER, labs, imaging, ICU and wards in real time, and it's all running on a simulation engine (FastAPI + WebSockets) that streams the state to the frontend constantly. On top of that I built an AI copilot that spots bottlenecks and actually recommends staffing changes using OR-Tools optimization + Holt-Winters forecasting. There's also a sandbox where you can throw crises at it (flu outbreak, CT scanner dying, mass casualty) and watch the hospital react. Plus it does shift handoff reports and tracks high-risk patients with AI care plans. The main thing I cared about was making it actually feel like real medical software, not a hackathon toy. So I built the whole UI around a design contract based on HIPAA, FDA Title 21 CFR Part 11 and WCAG 2.1. PHI is hidden by default, there's an auto-logout timer, status is never just a color, and I ripped out every glow/gradient/animation so it's calm to look at on a long shift. Full dark/light mode too. ## What Was Challenging The real-time stuff, honestly. Keeping the frontend in sync with a simulation that never stops updating, over WebSockets, without it lagging or flickering, was a pain. The AI optimization was also tough, getting OR-Tools to give recommendations that actually made sense and then explaining them in plain English. And the dark mode almost killed me lol. All my status cards were hardcoded to light colors so dark mode looked HORRIBLE, and I had to rebuild the entire color system on CSS variable tokens to fix it (213 replacements). ## What I'm Proud Of That it genuinely doesn't feel like a toy. It feels like something you could actually stick in a hospital ops room. Running the copilot, getting a real recommendation, hitting "Implement" and watching the metrics actually move is so satisfying. And the compliance stuff isn't just for looks, every choice actually ties back to a real medical standard. ## How To Test It Just open the link and you're in, no setup needed. If you'd rather run it yourself, download everything and follow the instructions in the README. Once you're in, easiest thing is to hit **"Auto Demo"** in the sidebar, it's a 1-click walkthrough of the whole thing. After that go trigger a crisis in the **Sandbox** and flip to the **Command Center** to watch it hit the floor plan, run the **AI Copilot** and click Implement to see the numbers move, and toggle dark/light mode in the top right....
|
1792882048.1551743
|
1793746048.1551743
|
|
13009
|
Drone building by @erenege1 | Stardance
|
erenege1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Drone building by @erenege1 | Stardance
|
1793494118.7059364
|
1794098918.7059364
|
|
13010
|
doomscroll engine by @mewo | Stardance
|
mewo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: doomscroll engine by @mewo | Stardance
|
1793479803.0142298
|
1794084603.0142298
|
|
13011
|
Untitled project by @nora_test999 | Stardance
|
nora_test999
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @nora_test999 | Stardan Title: Untitled project by @nora_test999 | Stardance...
|
1793152442.955842
|
1793757242.955842
|
|
13012
|
My first slack bot! by @beens | Stardance
|
beens
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @beens | Stardance
|
1793184889.8318045
|
1793789689.8318045
|
|
13013
|
Goofy-Goober by @LPcomix123 | Stardance
|
LPcomix123
|
1
|
4.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-21T21:42:52Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Over the past few days, I have been making a slack bot along with the stardance guide. I have learned how to code basic slack bots in node.js, and how to securely store and use bot and app tokens and api keys in a .env. Some commands include (but not limited to): /goofy-goober-ranfact which gives you a random fact, and: /goofy-goober-wotd which gives you the word of the day.", "repo": "https://github.com/LPcomix123/Goofy-Goober", "demo": "https://app.slack.com/client/E09V59WQY1E/C0P5NE354?skip_today=1"}]...
|
[{"post_id": 81647, "ts": "202 [{"post_id": 81647, "ts": "2026-10-21T21:28:23Z", "hours": 3.6494, "text": "Over the last few days, I have been developing a node.js slack bot by following the stardance mission and guide."}]...
|
Title: Goofy-Goober by @LPcomix123 | Stardance
De Title: Goofy-Goober by @LPcomix123 | Stardance
Devlogs:
Over the last few days, I have been developing a node.js slack bot by following the stardance mission and guide.
Ships:
Over the past few days, I have been making a slack bot along with the stardance guide. I have learned how to code basic slack bots in node.js, and how to securely store and use bot and app tokens and api keys in a .env. Some commands include (but not limited to): /goofy-goober-ranfact which gives you a random fact, and: /goofy-goober-wotd which gives you the word of the day....
|
1793408177.3642628
|
1793494577.3642628
|
|
13014
|
My first slack bot! by @varun303108 | Stardance
|
varun303108
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @varun303108 | Stard Title: My first slack bot! by @varun303108 | Stardance...
|
1792803156.8972476
|
1793407956.8972476
|
|
13015
|
Untitled project by @StrictScone226 | Stardance
|
StrictScone226
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @StrictScone226 | Stard Title: Untitled project by @StrictScone226 | Stardance...
|
1793181034.1376557
|
1793785834.1376557
|
|
13016
|
WebOS by @noaht | Stardance
|
noaht
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WebOS by @noaht | Stardance
|
1793202716.759268
|
1793807516.759268
|
|
13017
|
Cube Defense by @Dark-Tiger | Stardance
|
Dark-Tiger
|
0
|
8.8
|
0
|
[]
|
[{"post_id": 5530, "ts": "2026 [{"post_id": 5530, "ts": "2026-06-09T10:41:19Z", "hours": 8.8033, "text": "🧊Devlog - 1 The first devlog. Hello this is my first devlog. Cube Defense is my Godot Tower Defense Game. Some of the things that I added are: Main menu that doesn’t even fully work The Cube Enemies Health Attacking very basic Camera I hope to be back for a second devlog soon with even more features."}]...
|
Title: Cube Defense by @Dark-Tiger | Stardance
De Title: Cube Defense by @Dark-Tiger | Stardance
Devlogs:
🧊Devlog - 1 The first devlog. Hello this is my first devlog. Cube Defense is my Godot Tower Defense Game. Some of the things that I added are: Main menu that doesn’t even fully work The Cube Enemies Health Attacking very basic Camera I hope to be back for a second devlog soon with even more features....
|
1793281882.1917043
|
1793886682.1917043
|
|
13018
|
My awesome macropad! by @wardenscove | Stardance
|
wardenscove
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @wardenscove | Star Title: My awesome macropad! by @wardenscove | Stardance...
|
1793288954.2581558
|
1793893754.2581558
|
|
13019
|
Overlooker by @alfinchalson | Stardance
|
alfinchalson
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Overlooker by @alfinchalson | Stardance
|
1793483507.844145
|
1794088307.844145
|
|
13020
|
My Operating System by @nishythefishy43 | Stardanc My Operating System by @nishythefishy43 | Stardance...
|
nishythefishy43
|
0
|
1.42
|
0
|
[]
|
[{"post_id": 10663, "ts": "202 [{"post_id": 10663, "ts": "2026-06-17T15:04:01Z", "hours": 1.1303, "text": "Made the window able to move, close, and open. The logic for the window was being really annoying because I didn’t define the element constant. It worked finally at least. I’m going to add some other windows so that the OS doesn’t just have the welcome screen and top bar."}, {"post_id": 7575, "ts": "2026-06-12T17:42:35Z", "hours": 0.2922, "text": "First devlog for my OS, currently only have the homepage and top bar done. The clock in the top bar was really messing me up, but I finally got it working. I’m planning on making the webpage fully functioning before adding asthetics to it."}]...
|
Title: My Operating System by @nishythefishy43 | S Title: My Operating System by @nishythefishy43 | Stardance
Devlogs:
First devlog for my OS, currently only have the homepage and top bar done. The clock in the top bar was really messing me up, but I finally got it working. I’m planning on making the webpage fully functioning before adding asthetics to it.
Made the window able to move, close, and open. The logic for the window was being really annoying because I didn’t define the element constant. It worked finally at least. I’m going to add some other windows so that the OS doesn’t just have the welcome screen and top bar....
|
1793354051.0804498
|
1793958851.0804498
|
|
13021
|
Mental health buddy by @fadded66 | Stardance
|
fadded66
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mental health buddy by @fadded66 | Stardanc Title: Mental health buddy by @fadded66 | Stardance...
|
1792799632.8518076
|
1793404432.8518076
|
|
13022
|
Hybrid Control Architecture for S.E.U. Mitigation Hybrid Control Architecture for S.E.U. Mitigation by @Manyata_Patel11 | Stardance...
|
Manyata_Patel11
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hybrid Control Architecture for S.E.U. Miti Title: Hybrid Control Architecture for S.E.U. Mitigation by @Manyata_Patel11 | Stardance...
|
1793249486.443249
|
1793854286.443249
|
|
13023
|
ESP32 Web-Chat by @Kirill | Stardance
|
Kirill
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ESP32 Web-Chat by @Kirill | Stardance
|
1793318025.0996141
|
1793922825.0996141
|
|
13024
|
AI by @muditbhadada | Stardance
|
muditbhadada
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI by @muditbhadada | Stardance
|
1793472595.8850706
|
1794077395.8850706
|
|
13025
|
manus by @swasti | Stardance
|
swasti
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: manus by @swasti | Stardance
|
1793159511.650928
|
1793764311.650928
|
|
13026
|
F1 telemetry by @asvlh44 | Stardance
|
asvlh44
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: F1 telemetry by @asvlh44 | Stardance
|
1793472803.9282463
|
1794077603.9282463
|
|
13027
|
My awesome macropad! by @Stardancing_Twinkler | St My awesome macropad! by @Stardancing_Twinkler | Stardance...
|
Stardancing_Twinkler
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Stardancing_Twinkl Title: My awesome macropad! by @Stardancing_Twinkler | Stardance...
|
1793141249.9535677
|
1793746049.9535677
|
|
13028
|
My first slack bot! by @varun303108 | Stardance
|
varun303108
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @varun303108 | Stard Title: My first slack bot! by @varun303108 | Stardance...
|
1793551744.940307
|
1794156544.940307
|
|
13029
|
My first slack bot! by @Pihu | Stardance
|
Pihu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Pihu | Stardance
|
1793332633.005644
|
1793937433.005644
|
|
13030
|
3 axis rotating robot arm by @didimare_25 | Starda 3 axis rotating robot arm by @didimare_25 | Stardance...
|
didimare_25
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 3 axis rotating robot arm by @didimare_25 | Title: 3 axis rotating robot arm by @didimare_25 | Stardance...
|
1793386395.147696
|
1793991195.147696
|
|
13031
|
My very own WebOS by @bhandarisaira9 | Stardance
|
bhandarisaira9
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @bhandarisaira9 | Star Title: My very own WebOS by @bhandarisaira9 | Stardance...
|
1793371657.5651233
|
1793976457.5651233
|
|
13032
|
My awesome macropad! by @laamforsure | Stardance
|
laamforsure
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @laamforsure | Star Title: My awesome macropad! by @laamforsure | Stardance...
|
1793191865.6310608
|
1793796665.6310608
|
|
13033
|
Antwar by @4lvaret | Stardance
|
4lvaret
|
0
|
0.93
|
0
|
[]
|
[{"post_id": 5664, "ts": "2026 [{"post_id": 5664, "ts": "2026-06-09T15:21:18Z", "hours": 0.2881, "text": "changed logic to use numpy instead, over 15x performance gain according to unprofessional testing (left is old, right is new)"}, {"post_id": 4934, "ts": "2026-06-08T15:29:50Z", "hours": 0.6431, "text": "uhh yeah i finished it it was quick i should do stuff aside from reading documentation"}]...
|
Title: Antwar by @4lvaret | Stardance
Devlogs:
uh Title: Antwar by @4lvaret | Stardance
Devlogs:
uhh yeah i finished it it was quick i should do stuff aside from reading documentation
changed logic to use numpy instead, over 15x performance gain according to unprofessional testing (left is old, right is new)...
|
1793159506.9445658
|
1793764306.9445658
|
|
13034
|
My awesome macropad! by @HamdanAsad | Stardance
|
HamdanAsad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @HamdanAsad | Stard Title: My awesome macropad! by @HamdanAsad | Stardance...
|
1793382780.3457103
|
1793987580.3457103
|
|
13035
|
My very own WebOS by @I_got_this | Stardance
|
I_got_this
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @I_got_this | Stardanc Title: My very own WebOS by @I_got_this | Stardance...
|
1793134307.1363392
|
1793739107.1363392
|
|
13036
|
CogniVue by @Mathis | Stardance
|
Mathis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CogniVue by @Mathis | Stardance
|
1793328990.3012016
|
1793933790.3012016
|
|
13037
|
Untitled by @NotSap | Stardance
|
NotSap
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @NotSap | Stardance
|
1792903824.0496652
|
1793767824.0496652
|
|
13038
|
discord bot for soundboard by @Thijmen | Stardance
|
Thijmen
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: discord bot for soundboard by @Thijmen | St Title: discord bot for soundboard by @Thijmen | Stardance...
|
1793425789.8533187
|
1794030589.8533187
|
|
13039
|
My very own WebOS by @albertphu3 | Stardance
|
albertphu3
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @albertphu3 | Stardanc Title: My very own WebOS by @albertphu3 | Stardance...
|
1793393586.551767
|
1793998386.551767
|
|
13040
|
weebOS by @4lvaret | Stardance
|
4lvaret
|
0
|
2.22
|
0
|
[]
|
[{"post_id": 5080, "ts": "2026 [{"post_id": 5080, "ts": "2026-06-08T19:22:09Z", "hours": 0.945, "text": "got my other app, proxy, working altogether now! (deployed on another location however)"}, {"post_id": 5046, "ts": "2026-06-08T18:23:35Z", "hours": 0.6114, "text": "part 3"}, {"post_id": 4978, "ts": "2026-06-08T17:00:23Z", "hours": 0.6608, "text": "so i have done part 1 and part 2"}]...
|
Title: weebOS by @4lvaret | Stardance
Devlogs:
so Title: weebOS by @4lvaret | Stardance
Devlogs:
so i have done part 1 and part 2
part 3
got my other app, proxy, working altogether now! (deployed on another location however)...
|
1793494532.7745283
|
1794099332.7745283
|
|
13041
|
Tumor Classification by @MiguelF-AI | Stardance
|
MiguelF-AI
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Tumor Classification by @MiguelF-AI | Stard Title: Tumor Classification by @MiguelF-AI | Stardance...
|
1793515676.4300463
|
1794120476.4300463
|
|
13042
|
Reins by @simon_j | Stardance
|
simon_j
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Reins by @simon_j | Stardance
|
1793166663.5967002
|
1793771463.5967002
|
|
13043
|
My awesome macropad! by @MikeUp | Stardance
|
MikeUp
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @MikeUp | Stardance
|
1793177334.6965523
|
1793782134.6965523
|
|
13044
|
My very own WebOS by @austinblass | Stardance
|
austinblass
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @austinblass | Stardan Title: My very own WebOS by @austinblass | Stardance...
|
1793372047.2421937
|
1793976847.2421937
|
|
13045
|
DevBlock by @VibeSlayer | Stardance
|
VibeSlayer
|
0
|
1.45
|
0
|
[]
|
[{"post_id": 5880, "ts": "2026 [{"post_id": 5880, "ts": "2026-06-09T20:47:55Z", "hours": 1.4511, "text": "Devlog #1 Ahh, today was really tiring, but I’m honestly very proud of myself. After two days of constant struggle, redesigning, fixing mistakes, and learning KiCad properly, I finally finished the PCB design for DevBlock. DevBlock is a compact developer macropad with 4 keys, an OLED display, and a rotary encoder switch. The hardest part was definitely getting everything to look clean and making the DevBlock logo work on the PCB — you don’t know how much I struggled with that lmao. Tomorrow’s (i mean today’s cz its 2AM lmao i m a nightowl trust) plan is to design a clean case for it. That’s probably going to be another big struggle because I’m not very good at 3D modelling yet, but let’s see how it goes. For now, I’m happy with the progress. Good night!"}]...
|
Title: DevBlock by @VibeSlayer | Stardance
Devlog Title: DevBlock by @VibeSlayer | Stardance
Devlogs:
Devlog #1 Ahh, today was really tiring, but I’m honestly very proud of myself. After two days of constant struggle, redesigning, fixing mistakes, and learning KiCad properly, I finally finished the PCB design for DevBlock. DevBlock is a compact developer macropad with 4 keys, an OLED display, and a rotary encoder switch. The hardest part was definitely getting everything to look clean and making the DevBlock logo work on the PCB — you don’t know how much I struggled with that lmao. Tomorrow’s (i mean today’s cz its 2AM lmao i m a nightowl trust) plan is to design a clean case for it. That’s probably going to be another big struggle because I’m not very good at 3D modelling yet, but let’s see how it goes. For now, I’m happy with the progress. Good night!...
|
1793253090.4315255
|
1793857890.4315255
|
|
13046
|
My first slack bot! by @pando67 | Stardance
|
pando67
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @pando67 | Stardance
|
1792799423.3454285
|
1793404223.3454285
|
|
13047
|
SlackBot (with 0%experience) by @Srirangan | Stard SlackBot (with 0%experience) by @Srirangan | Stardance...
|
Srirangan
|
0
|
0.65
|
0
|
[]
|
[{"post_id": 10996, "ts": "202 [{"post_id": 10996, "ts": "2026-06-18T00:49:38Z", "hours": 0.3006, "text": "I have cleared all code in my index.js file and trying to recode it, since I dont know basic javascript , I,m trying to learn it by coding daily instead of studying about it and then code. what do you think abut this..?"}, {"post_id": 9216, "ts": "2026-06-15T14:03:20Z", "hours": 0.3539, "text": "All the basic setups has been set, gotta code and add extra commands!!"}]...
|
Title: SlackBot (with 0%experience) by @Srirangan Title: SlackBot (with 0%experience) by @Srirangan | Stardance
Devlogs:
All the basic setups has been set, gotta code and add extra commands!!
I have cleared all code in my index.js file and trying to recode it, since I dont know basic javascript , I,m trying to learn it by coding daily instead of studying about it and then code. what do you think abut this..?...
|
1792803077.3310077
|
1793407877.3310077
|
|
13048
|
My first slack bot! by @Rishit | Stardance
|
Rishit
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Rishit | Stardance
|
1793361387.2438085
|
1793966187.2438085
|
|
13049
|
SortIT by @abdullahm | Stardance
|
abdullahm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SortIT by @abdullahm | Stardance
|
1793389936.4000697
|
1793994736.4000697
|
|
13050
|
K.A.I by @JoshuaK | Stardance
|
JoshuaK
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: K.A.I by @JoshuaK | Stardance
|
1793256798.5933657
|
1793861598.5933657
|