|
2385
|
Bio controlled arm by @Scott | Stardance
|
Scott
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Bio controlled arm by @Scott | Stardance
|
1793354221.93971
|
1793959021.93971
|
|
2386
|
My first slack bot! by @Jenna | Stardance
|
Jenna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Jenna | Stardance
|
1793274661.797601
|
1793879461.797601
|
|
2387
|
Project Macropad by @theycantseemeyall | Stardance
|
theycantseemeyall
|
0
|
1.48
|
0
|
[]
|
[{"post_id": 32014, "ts": "202 [{"post_id": 32014, "ts": "2026-07-20T21:35:07Z", "hours": 1.4844, "text": "Today i finally finsihed with the schematic of project macro and assigning the appropriate footnotes to each component. It was pretty easy going but took sm onger than I had actually expected. I think debugging the errors and warnings took the longets part as I had to learn how to manually assign footnotes, how to do global nets to avoid a cluster of wires, close parts I wasn’t using and adding power flags to parts. The bad thing was that as I was trying to figure out how to assign the footnotes I decided to just place the footnotes in a different folder and then use that so it readjusts but I also changed the symbols library by accident now I can’t even ctrl Z and I doin’t remember what was there originally. But thats a problem for tmr me."}]...
|
Title: Project Macropad by @theycantseemeyall | St Title: Project Macropad by @theycantseemeyall | Stardance
Devlogs:
Today i finally finsihed with the schematic of project macro and assigning the appropriate footnotes to each component. It was pretty easy going but took sm onger than I had actually expected. I think debugging the errors and warnings took the longets part as I had to learn how to manually assign footnotes, how to do global nets to avoid a cluster of wires, close parts I wasn’t using and adding power flags to parts. The bad thing was that as I was trying to figure out how to assign the footnotes I decided to just place the footnotes in a different folder and then use that so it readjusts but I also changed the symbols library by accident now I can’t even ctrl Z and I doin’t remember what was there originally. But thats a problem for tmr me....
|
1793354198.4259894
|
1793958998.4259894
|
|
2388
|
My awesome macropad! by @ianparedes | Stardance
|
ianparedes
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ianparedes | Stard Title: My awesome macropad! by @ianparedes | Stardance...
|
1793145154.637145
|
1793749954.637145
|
|
2389
|
My awesome macropad! by @eunchanh325 | Stardance
|
eunchanh325
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @eunchanh325 | Star Title: My awesome macropad! by @eunchanh325 | Stardance...
|
1793310938.9099793
|
1793915738.9099793
|
|
2390
|
Custom Slack Command that teaches Spanish by @lee2 Custom Slack Command that teaches Spanish by @lee264 | Stardance...
|
lee264
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Custom Slack Command that teaches Spanish b Title: Custom Slack Command that teaches Spanish by @lee264 | Stardance...
|
1792767011.786843
|
1793631011.786843
|
|
2391
|
My awesome macropad! by @Mirac | Stardance
|
Mirac
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Mirac | Stardance
|
1792767287.9682374
|
1793372087.9682374
|
|
2392
|
Untitled by @CY3er | Stardance
|
CY3er
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @CY3er | Stardance
|
1793317996.836597
|
1793922796.836597
|
|
2393
|
Untitled by @itzstt | Stardance
|
itzstt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @itzstt | Stardance
|
1793404176.9948785
|
1794008976.9948785
|
|
2394
|
My first slack bot! by @antoninvallonazoulay | Sta My first slack bot! by @antoninvallonazoulay | Stardance...
|
antoninvallonazoulay
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @antoninvallonazoula Title: My first slack bot! by @antoninvallonazoulay | Stardance...
|
1793245802.0230231
|
1793850602.0230231
|
|
2395
|
My awesome macropad! by @Sgattix | Stardance
|
Sgattix
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Sgattix | Stardanc Title: My awesome macropad! by @Sgattix | Stardance...
|
1793271222.32627
|
1793876022.32627
|
|
2396
|
My first slack bot! by @bali0531 | Stardance
|
bali0531
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @bali0531 | Stardanc Title: My first slack bot! by @bali0531 | Stardance...
|
1792929096.3428986
|
1793793096.3428986
|
|
2397
|
Drone by @Kynetic | Stardance
|
Kynetic
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Drone by @Kynetic | Stardance
|
1792936307.7351282
|
1793800307.7351282
|
|
2399
|
AI Robot by @Ibrahim-Khurram | Stardance
|
Ibrahim-Khurram
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI Robot by @Ibrahim-Khurram | Stardance
|
1793198859.8389342
|
1793803659.8389342
|
|
2400
|
My first slack bot! by @itzstt | Stardance
|
itzstt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @itzstt | Stardance
|
1793288960.9499257
|
1793893760.9499257
|
|
2401
|
FRC Style Robotic Arm by @Mattsalt | Stardance
|
Mattsalt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FRC Style Robotic Arm by @Mattsalt | Starda Title: FRC Style Robotic Arm by @Mattsalt | Stardance...
|
1793278392.7898126
|
1793883192.7898126
|
|
2402
|
My awesome macropad! by @corey | Stardance
|
corey
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @corey | Stardance
|
1793292886.5940475
|
1793897686.5940475
|
|
2403
|
uforce website by @Pho3n1x | Stardance
|
Pho3n1x
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: uforce website by @Pho3n1x | Stardance
|
1793184436.925775
|
1793789236.925775
|
|
2404
|
Should I Invest App by @jordann0518 | Stardance
|
jordann0518
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Should I Invest App by @jordann0518 | Stard Title: Should I Invest App by @jordann0518 | Stardance...
|
1793292458.560736
|
1793897258.560736
|
|
2405
|
My awesome macropad! by @MaybeMae | Stardance
|
MaybeMae
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @MaybeMae | Stardan Title: My awesome macropad! by @MaybeMae | Stardance...
|
1793192001.6109593
|
1793796801.6109593
|
|
2406
|
Language Evolution by @orman | Stardance
|
orman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Language Evolution by @orman | Stardance
|
1792742069.5660694
|
1793346869.5660694
|
|
2407
|
Steller-x1 by @matthewhanna09 | Stardance
|
matthewhanna09
|
0
|
0.58
|
0
|
[]
|
[{"post_id": 56364, "ts": "202 [{"post_id": 56364, "ts": "2026-08-28T03:34:11Z", "hours": 0.5825, "text": "making all the test models"}]...
|
Title: Steller-x1 by @matthewhanna09 | Stardance
Title: Steller-x1 by @matthewhanna09 | Stardance
Devlogs:
making all the test models...
|
1793184836.2294288
|
1793789636.2294288
|
|
2409
|
MemoryMap by @LEOM | Stardance
|
LEOM
|
1
|
9.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-23T23:24:36Z", "hours": 9.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Hello! This is MemoryMap - this project aims to help you find your lost items by scanning you room with a couple of pictures and asking later the object detector if you forget where you placed them! With just some simple clicks and pictures, this assistant will help you find all of your lost all objects all around the house in SECONDS! Thank you for stopping by!", "repo": "https://github.com/Planetech0071/MemoryMap", "demo": "https://memorymap-demo-brief.vercel.app/"}]...
|
[{"post_id": 14737, "ts": "202 [{"post_id": 14737, "ts": "2026-06-23T23:02:47Z", "hours": 1.0569, "text": "It is OVER! Shipping! What a project man- I am sure I’ll actually use this. Maybe my second ship could be an integration with ALEXA/Google Home to have a physical assistant? I’d keep an eye out for that, but for now, this is my first ship!"}, {"post_id": 14438, "ts": "2026-06-23T15:52:34Z", "hours": 1.7575, "text": "Hey again :D Quick update: MemoryMap is now basically done. All core systems are in place and working together as expected. The full pipeline from camera input → detection → merging → storage → query is stable. I also went through the remaining edge cases that were causing inconsistent object histories, especially around duplicate merges and stale updates. Most of the time this session was spent on tightening things up instead of adding new features. That included cleaning logs, fixing a few timing issues in the frame handler, and making sure the memory store stays consistent under continuous input. The system now holds up under longer runs without breaking state or losing tracked objects. The query layer is also in a usable state. You can ask questions like where an object was last seen and get a reliable answer based on stored history, not just the latest frame. That part took a bit of tuning to make responses consistent. Right now I’m not planning any more big changes. The project is in final testing mode. I’m running longer sessions across different rooms to check stability, accuracy, and performance under real use. Next step is just validation and small fixes if anything shows up during testing. Feels good to see it reach this stage."}, {"post_id": 4993, "ts": "2026-06-08T17:15:07Z", "hours": 1.4667, "text": "Hey again :D This one was less about fixing bugs and more about actually building out the pipeline. MemoryMap is now split into separate modules instead of everything being stuffed together. The project currently consists of: frame_reader.py: receives and processes incoming video frames detector.py: handles object detection handler.py: coordinates detections and memory updates store.py: persistent memory storage object_record.py: object history tracking merge.py: combines duplicate observations main.py: starts and manages everything The biggest addition this session was the detection pipeline itself. Previously, I had the memory system working, but there wasn’t really a complete path from camera feed → object detection → stored memory. That’s now connected together. Frames arrive, detections are produced, records are updated, and the information is written into MemoryStore automatically. I also started work on observation merging. One issue with object tracking is that the same object can appear multiple times across different frames, creating fragmented records. The merge layer now attempts to consolidate those observations into a single memory entry, making the stored data much cleaner and more useful when querying later. Another thing I spent time on was restructuring the codebase. It doesn’t sound exciting, but getting clear separation between frame capture, detection, storage, and record management will make future work much easier. Debugging individual components is already significantly simpler. The project is starting to look less like a prototype and more like an actual system! Next steps are improving location accuracy, expanding object history tracking, and building the query layer so MemoryMap can start answering natural questions such as: “Where did I leave my headphones?” or “When was the last time the wallet was seen?” Still a lot to build, but the foundations are finally coming together. More soon. 🚀"}, {"post_id": 3550, "ts": "2026-06-06T15:20:35Z", "hours": 1.5297, "text": "Hello :D Firstly, I did say I wanted to update both object_record.py and get everything running. Done and done. In object_record.py, the function “update()” would overwrite the history before saving it, thus creating just one history per object, which isn’t much when we need to know when and how objects have been moved. This is now fixed, while main.py was facing a circular importing error, which has now been sorted out too. And here comes the fun part: Phone camera integration! Originally, we were going to use a webcam for recording purposes. It will work fine on a desk but what about the other areas of the house? Well, there is always the phone! Simply go from room to room pointing it at the surroundings for 10 seconds. Now the server has an additional WebSocket receiver listening at port 8001. Start by entering on phone, use the URL displayed to connect to the web server with your phone, and just the web browser, no special app required; use Safari or Chrome. It starts sending video feeds through Wi-Fi straight from your phone’s rear camera. Added a location label field so that each location gets labeled as you scan it. No longer will the results say “somewhere left of centre frame,” instead they’ll now read “kitchen”. Switched from using YOLOv8 to YOLOv10. Main improvement with v10? None other than the complete removal of non-maximum suppression post-processing. No duplicates, even better for a system like ours which relies heavily on memory. Good trade-off. Completed 28 tests, all successful. Memory layer is ready to go. The thing powers up, retains data, you walk around your house, and you get answers. Basic functionality is there. Now, everything else is about polish. More details soon."}, {"post_id": 477, "ts": "2026-06-01T22:46:20Z", "hours": 2.8167, "text": "Hey, welcome to the first devlog for MemoryMap! I’ve been wanting to build this for a while and I finally started with this perfect opportunity! Fair warning: this is very much a “day one” post, things are rough, bugs, and not everything compiles :/ So what is MemoryMap? You know that feeling when you’re late and you can’t find your keys or your wallet and you wish your house could just tell you where they are? That’s the whole idea. Point a camera at your space (either through “memory” or persistent view), let the system watch continuously and build a memory of where objects are, then ask it questions, like “where are my headphones?” and get an instant answer based on the last time they were actually seen. No more searching the same three spots over and over. The core of the project: store.py, the MemoryStore class. This is the memory layer everything else will depend on. It handles three things. Ingestion: every camera frame hands in a list of detections, and the store either updates an existing record or creates a new one, all thread-safe. Staleness: objects don’t vanish when they leave frame, they get marked stale after a configurable number of hours, so last-known location is always preserved. Persistence: a background thread periodically flushes everything to disk as JSON, atomically obviously, so memory survives restarts. The other two files (object_record.py and main.py) are started but still buggy. They’ll get their moment in a future devlog. Next up: fix object_record.py and get the whole thing to actually boot :D"}]...
|
Title: MemoryMap by @LEOM | Stardance
Devlogs:
He Title: MemoryMap by @LEOM | Stardance
Devlogs:
Hey, welcome to the first devlog for MemoryMap! I’ve been wanting to build this for a while and I finally started with this perfect opportunity! Fair warning: this is very much a “day one” post, things are rough, bugs, and not everything compiles :/ So what is MemoryMap? You know that feeling when you’re late and you can’t find your keys or your wallet and you wish your house could just tell you where they are? That’s the whole idea. Point a camera at your space (either through “memory” or persistent view), let the system watch continuously and build a memory of where objects are, then ask it questions, like “where are my headphones?” and get an instant answer based on the last time they were actually seen. No more searching the same three spots over and over. The core of the project: store.py, the MemoryStore class. This is the memory layer everything else will depend on. It handles three things. Ingestion: every camera frame hands in a list of detections, and the store either updates an existing record or creates a new one, all thread-safe. Staleness: objects don’t vanish when they leave frame, they get marked stale after a configurable number of hours, so last-known location is always preserved. Persistence: a background thread periodically flushes everything to disk as JSON, atomically obviously, so memory survives restarts. The other two files (object_record.py and main.py) are started but still buggy. They’ll get their moment in a future devlog. Next up: fix object_record.py and get the whole thing to actually boot :D
Hello :D Firstly, I did say I wanted to update both object_record.py and get everything running. Done and done. In object_record.py, the function “update()” would overwrite the history before saving it, thus creating just one history per object, which isn’t much when we need to know when and how objects have been moved. This is now fixed, while main.py was facing a circular importing error, which has now been sorted out too. And here comes the fun part: Phone camera integration! Originally, we were going to use a webcam for recording purposes. It will work fine on a desk but what about the other areas of the house? Well, there is always the phone! Simply go from room to room pointing it at the surroundings for 10 seconds. Now the server has an additional WebSocket receiver listening at port 8001. Start by entering on phone, use the URL displayed to connect to the web server with your phone, and just the web browser, no special app required; use Safari or Chrome. It starts sending video feeds through Wi-Fi straight from your phone’s rear camera. Added a location label field so that each location gets labeled as you scan it. No longer will the results say “somewhere left of centre frame,” instead they’ll now read “kitchen”. Switched from using YOLOv8 to YOLOv10. Main improvement with v10? None other than the complete removal of non-maximum suppression post-processing. No duplicates, even better for a system like ours which relies heavily on memory. Good trade-off. Completed 28 tests, all successful. Memory layer is ready to go. The thing powers up, retains data, you walk around your house, and you get answers. Basic functionality is there. Now, everything else is about polish. More details soon.
Hey again :D This one was less about fixing bugs and more about actually building out the pipeline. MemoryMap is now split into separate modules instead of everything being stuffed together. The project currently consists of: frame_reader.py: receives and processes incoming video frames detector.py: handles object detection handler.py: coordinates detections and memory updates store.py: persistent memory storage object_record.py: object history tracking merge.py: combines duplicate observations main.py: starts and manages everything The biggest addition this session was the detection pipeline itself. Previously, I had the memory system working, but there wasn’t really a complete path from camera feed → object detection → stored memory. That’s now connected together. Frames arrive, detections are produced, records are updated, and the information is written into MemoryStore automatically. I also started work on observation merging. One issue with object tracking is that the same object can appear multiple times across different frames, creating fragmented records. The merge layer now attempts to consolidate those observations into a single memory entry, making the stored data much cleaner and more useful when querying later. Another thing I spent time on was restructuring the codebase. It doesn’t sound exciting, but getting clear separation between frame capture, detection, storage, and record management will make future work much easier. Debugging individual components is already significantly simpler. The project is starting to look less like a prototype and more like an actual system! Next steps are improving location accuracy, expanding object history tracking, and building the query layer so MemoryMap can start answering natural questions such as: “Where did I leave my headphones?” or “When was the last time the wallet was seen?” Still a lot to build, but the foundations are finally coming together. More soon. 🚀
Hey again :D Quick update: MemoryMap is now basically done. All core systems are in place and working together as expected. The full pipeline from camera input → detection → merging → storage → query is stable. I also went through the remaining edge cases that were causing inconsistent object histories, especially around duplicate merges and stale updates. Most of the time this session was spent on tightening things up instead of adding new features. That included cleaning logs, fixing a few timing issues in the frame handler, and making sure the memory store stays consistent under continuous input. The system now holds up under longer runs without breaking state or losing tracked objects. The query layer is also in a usable state. You can ask questions like where an object was last seen and get a reliable answer based on stored history, not just the latest frame. That part took a bit of tuning to make responses consistent. Right now I’m not planning any more big changes. The project is in final testing mode. I’m running longer sessions across different rooms to check stability, accuracy, and performance under real use. Next step is just validation and small fixes if anything shows up during testing. Feels good to see it reach this stage.
It is OVER! Shipping! What a project man- I am sure I’ll actually use this. Maybe my second ship could be an integration with ALEXA/Google Home to have a physical assistant? I’d keep an eye out for that, but for now, this is my first ship!
Ships:
Hello! This is MemoryMap - this project aims to help you find your lost items by scanning you room with a couple of pictures and asking later the object detector if you forget where you placed them! With just some simple clicks and pictures, this assistant will help you find all of your lost all objects all around the house in SECONDS! Thank you for stopping by!...
|
1793245683.4200382
|
1793332083.4200382
|
|
2410
|
Untitled by @Jenna | Stardance
|
Jenna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Jenna | Stardance
|
1793411371.353677
|
1794016171.353677
|
|
2411
|
My first slack bot! by @evanwhitt | Stardance
|
evanwhitt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @evanwhitt | Stardan Title: My first slack bot! by @evanwhitt | Stardance...
|
1793177497.246552
|
1793782297.246552
|
|
2412
|
My first slack bot! by @nishythefishy43 | Stardanc My first slack bot! by @nishythefishy43 | Stardance...
|
nishythefishy43
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @nishythefishy43 | S Title: My first slack bot! by @nishythefishy43 | Stardance...
|
1793184692.4023328
|
1793789492.4023328
|
|
2413
|
Untitled project by @Cheerawab | Stardance
|
Cheerawab
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Cheerawab | Stardance
|
1793411456.4560962
|
1794016256.4560962
|
|
2415
|
My first slack bot! by @jupeme6 | Stardance
|
jupeme6
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @jupeme6 | Stardance
|
1792907568.266105
|
1793771568.266105
|
|
2416
|
Humanoid Robot by @Lotzzy1 | Stardance
|
Lotzzy1
|
0
|
3.76
|
0
|
[]
|
[{"post_id": 26547, "ts": "202 [{"post_id": 26547, "ts": "2026-07-11T13:03:33Z", "hours": 3.3447, "text": "I’m working on my humanoid robot project to make it seem more friendly and humanlike. I have added a few new animations. For example in the picture that would be the thinking animation. The AI has complete control over what animations it wants to use. The robot can talk to you back and forth as well as recognize people that have registered with the robot their name. The robot has memory as well so it can recall past conversations. The robot can face track people around it. The robot can analyze what it can see and tell you want it can see if prompted."}, {"post_id": 11011, "ts": "2026-06-18T01:11:24Z", "hours": 0.4192, "text": "I’m working on making my humanoid Robot actually move. I’ve been working on giving it A.I. that you can talk to and let it move freely. I also would like to add face tracking sooner or later so it can really feel like a person in the room and not just a toy."}]...
|
Title: Humanoid Robot by @Lotzzy1 | Stardance
Dev Title: Humanoid Robot by @Lotzzy1 | Stardance
Devlogs:
I’m working on making my humanoid Robot actually move. I’ve been working on giving it A.I. that you can talk to and let it move freely. I also would like to add face tracking sooner or later so it can really feel like a person in the room and not just a toy.
I’m working on my humanoid robot project to make it seem more friendly and humanlike. I have added a few new animations. For example in the picture that would be the thinking animation. The AI has complete control over what animations it wants to use. The robot can talk to you back and forth as well as recognize people that have registered with the robot their name. The robot has memory as well so it can recall past conversations. The robot can face track people around it. The robot can analyze what it can see and tell you want it can see if prompted....
|
1793328992.1312144
|
1793933792.1312144
|
|
2417
|
JJ by @chuku-N0 | Stardance
|
chuku-N0
|
0
|
0.39
|
0
|
[]
|
[{"post_id": 1409, "ts": "2026 [{"post_id": 1409, "ts": "2026-06-03T13:01:46Z", "hours": 0.3917, "text": "Spent some quality time building out a completely local, voice-activated desktop assistant. I was not able to log all of my time which is around 2 weeks of work because stardust didn’t start. The goal was speed, screen awareness, and an interface that doesn’t just sit there but actually feels alive. What’s working: Dual-Model Brains: Hooked up Ollama to dynamically switch models depending on the task. It defaults to a fast text model (mistral) for snappy voice conversations but instantly pivots to a vision model (llama3.2-vision) when triggered to inspect the screen. Eyes on the Desktop: Integrated real-time screenshot capturing using PyAutoGUI. If I ask “Jarvis, look at this,” it grabs the frame, pipes it to the vision model, and tells me what I’m looking at completely offline. Reactive Audio GUI: Built a CustomTkinter dark-themed interface featuring a central arc engine. It doesn’t just loop an animation; it parses live microphone input streams via sounddevice to pulse and flash dynamically based on my voice volume. Contextual YouTube & Notes Engine: Taught it to search YouTube, read the top three results via voice synthesis, and wait for contextual follow-ups (“open the second one”). It can also handle local Python file analysis and dynamic note-taking routines through a custom chunk-reading mechanism. Barge-In Interrupts: Implemented background thread monitoring so I can cut the AI off mid-speech or mid-thought with a quick phrase if it gets too chatty. N.B: if you have any improvements in mind I could add plz feel free"}]...
|
Title: JJ by @chuku-N0 | Stardance
Devlogs:
Spent Title: JJ by @chuku-N0 | Stardance
Devlogs:
Spent some quality time building out a completely local, voice-activated desktop assistant. I was not able to log all of my time which is around 2 weeks of work because stardust didn’t start. The goal was speed, screen awareness, and an interface that doesn’t just sit there but actually feels alive. What’s working: Dual-Model Brains: Hooked up Ollama to dynamically switch models depending on the task. It defaults to a fast text model (mistral) for snappy voice conversations but instantly pivots to a vision model (llama3.2-vision) when triggered to inspect the screen. Eyes on the Desktop: Integrated real-time screenshot capturing using PyAutoGUI. If I ask “Jarvis, look at this,” it grabs the frame, pipes it to the vision model, and tells me what I’m looking at completely offline. Reactive Audio GUI: Built a CustomTkinter dark-themed interface featuring a central arc engine. It doesn’t just loop an animation; it parses live microphone input streams via sounddevice to pulse and flash dynamically based on my voice volume. Contextual YouTube & Notes Engine: Taught it to search YouTube, read the top three results via voice synthesis, and wait for contextual follow-ups (“open the second one”). It can also handle local Python file analysis and dynamic note-taking routines through a custom chunk-reading mechanism. Barge-In Interrupts: Implemented background thread monitoring so I can cut the AI off mid-speech or mid-thought with a quick phrase if it gets too chatty. N.B: if you have any improvements in mind I could add plz feel free...
|
1793198882.595975
|
1793803682.595975
|
|
2418
|
Objection your Honour Remake by @Hridyansh | Stard Objection your Honour Remake by @Hridyansh | Stardance...
|
Hridyansh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Objection your Honour Remake by @Hridyansh Title: Objection your Honour Remake by @Hridyansh | Stardance...
|
1793415066.3792913
|
1794019866.3792913
|
|
2419
|
AI Agent by @mohnish | Stardance
|
mohnish
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI Agent by @mohnish | Stardance
|
1793274868.4172163
|
1793879668.4172163
|
|
2420
|
My awesome macropad! by @fatimah | Stardance
|
fatimah
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @fatimah | Stardanc Title: My awesome macropad! by @fatimah | Stardance...
|
1793206525.0458918
|
1793811325.0458918
|
|
2421
|
My awesome macropad! by @Antonovna | Stardance
|
Antonovna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Antonovna | Starda Title: My awesome macropad! by @Antonovna | Stardance...
|
1793238952.3897648
|
1793843752.3897648
|
|
2422
|
My first slack bot! by @fatimah | Stardance
|
fatimah
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @fatimah | Stardance
|
1793292799.6904848
|
1793897599.6904848
|
|
2423
|
Clanker Conundrum by @Jinsu | Stardance
|
Jinsu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Clanker Conundrum by @Jinsu | Stardance
|
1793386254.0975618
|
1793991054.0975618
|
|
2424
|
My first slack bot! (yeah tring :/) by @Lunex | St My first slack bot! (yeah tring :/) by @Lunex | Stardance...
|
Lunex
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! (yeah tring :/) by @Lun Title: My first slack bot! (yeah tring :/) by @Lunex | Stardance...
|
1793289225.3928108
|
1793894025.3928108
|
|
2425
|
My awesome macropad! by @tylerf | Stardance
|
tylerf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tylerf | Stardance
|
1793137881.7200446
|
1793742681.7200446
|
|
2426
|
My awesome macropad! by @sohamdev77 | Stardance
|
sohamdev77
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sohamdev77 | Stard Title: My awesome macropad! by @sohamdev77 | Stardance...
|
1793321302.044773
|
1793926102.044773
|
|
2427
|
DISTORTION PEDAL by @Abii | Stardance
|
Abii
|
0
|
6.55
|
0
|
[]
|
[{"post_id": 29028, "ts": "202 [{"post_id": 29028, "ts": "2026-07-15T17:56:35Z", "hours": 2.4981, "text": "KICAD PCB design This was way harder than ltspice for me because i was still trying to navigate the software. A lot of time was spent on looking for the appropriate foot prints. I honestly don’t have much to say apart from needing to cleaning up the layouts. Next Action: I may take a break from Kicad and move on to fusion 360 . That would be better for figuring out what I want in my PCB design"}, {"post_id": 23570, "ts": "2026-07-06T16:35:49Z", "hours": 2.6506, "text": "2ND DISTORTION PEDAL DRAFT #devlog 2 My initial distortion circuit had lots of problems regarding simulating the waves as the out put of each stage did not give the desired shape. I had to go back to some youtube videos and some examples online to see what I could improve to my circuit, comparing the picture below to my previous devlog, you can see I made some major changes regarding the amplifier, clipping and tone control stages. NEXT STEP: I’m pretty confident in this schematic so next step would be designing the enclosure then the PCB"}, {"post_id": 18534, "ts": "2026-06-29T18:31:46Z", "hours": 1.4, "text": "DEVLOG #1 - initial draft of the schematic Hi 👋🏾, this is my first project and post and i wanted to share what i’ve done. A while ago, I expressed my interest in electronics and a friend had given me some good advice on separating my projects into stages to try and understand things better and it was definitely helpful. A distortion pedal usually amplifies your clean guitar signal and clips it which alters the sound. From what I’ve seen online, the main features of the distortion pedal includes: Gain control: controls how much the signal is altered Volume Control: Controls the output volume Tone Control: Controls specific pitches to make them softer or harder. These can all be altered using a standard potentiometer. For my schematic, I decided to break it into parts. POWER SUPPLY: I intend to use a standard 9V battery, however, this only pushes electricity to one direction in contrast to plugging it into an ac supply. Guitar signals are typically sine waves so they go above and below the 0V line. To prevent harsh clipping of the signal, the stage creates a virtual ground at 4.5V OFFSET CIRCUIT: This offsets the guitar signal so that 4.5V is the middle ground. This circuit prepares the tiny guitar signal for the amplification stage. 3.AMPLIFIER CIRCUIT: This is where the volume control happens, this stage amplifies the guitars signal so that it becomes easier to distort. This stage is defined by the inverting amplifier so changing the resistance of the potentiometer affects the gain. CLIPPING CIRCUIT: Two diodes pointing in opposite directions toward the ground act like the ceiling and floor. When an amplified guitar signal hits that stage, they get clipped at the top and bottom of the wave. This is supposed to turn the signal into a square like wave but i’m having trouble getting that ideal shape in the simulation. TONE CONTROL: The clipping stage produces a harsh and buzzy sound so the tone control circuit filters out the high frequencies so that the distorted signal sounds smooth. ROUGH COMPONENTS LIST Shottcky Diodes(may switch this out for a regular silicon diode) Resistors Capacitors OP07 operational amplifier 9V battery Potentiometer PROBLEMS AND THINGS TO WORK ON This is only a rough draft but my simulations don’t give me the ideal waveforms that I want so i need to play around with the values and arrangements of the circuit. My main problems are in the clipping and tone control stage as the output wave forms aren’t ideal. next actions: Work more on the schematic, start designing the enclosure, work on the actual pcb 👍🏾"}]...
|
Title: DISTORTION PEDAL by @Abii | Stardance
Devl Title: DISTORTION PEDAL by @Abii | Stardance
Devlogs:
DEVLOG #1 - initial draft of the schematic Hi 👋🏾, this is my first project and post and i wanted to share what i’ve done. A while ago, I expressed my interest in electronics and a friend had given me some good advice on separating my projects into stages to try and understand things better and it was definitely helpful. A distortion pedal usually amplifies your clean guitar signal and clips it which alters the sound. From what I’ve seen online, the main features of the distortion pedal includes: Gain control: controls how much the signal is altered Volume Control: Controls the output volume Tone Control: Controls specific pitches to make them softer or harder. These can all be altered using a standard potentiometer. For my schematic, I decided to break it into parts. POWER SUPPLY: I intend to use a standard 9V battery, however, this only pushes electricity to one direction in contrast to plugging it into an ac supply. Guitar signals are typically sine waves so they go above and below the 0V line. To prevent harsh clipping of the signal, the stage creates a virtual ground at 4.5V OFFSET CIRCUIT: This offsets the guitar signal so that 4.5V is the middle ground. This circuit prepares the tiny guitar signal for the amplification stage. 3.AMPLIFIER CIRCUIT: This is where the volume control happens, this stage amplifies the guitars signal so that it becomes easier to distort. This stage is defined by the inverting amplifier so changing the resistance of the potentiometer affects the gain. CLIPPING CIRCUIT: Two diodes pointing in opposite directions toward the ground act like the ceiling and floor. When an amplified guitar signal hits that stage, they get clipped at the top and bottom of the wave. This is supposed to turn the signal into a square like wave but i’m having trouble getting that ideal shape in the simulation. TONE CONTROL: The clipping stage produces a harsh and buzzy sound so the tone control circuit filters out the high frequencies so that the distorted signal sounds smooth. ROUGH COMPONENTS LIST Shottcky Diodes(may switch this out for a regular silicon diode) Resistors Capacitors OP07 operational amplifier 9V battery Potentiometer PROBLEMS AND THINGS TO WORK ON This is only a rough draft but my simulations don’t give me the ideal waveforms that I want so i need to play around with the values and arrangements of the circuit. My main problems are in the clipping and tone control stage as the output wave forms aren’t ideal. next actions: Work more on the schematic, start designing the enclosure, work on the actual pcb 👍🏾
2ND DISTORTION PEDAL DRAFT #devlog 2 My initial distortion circuit had lots of problems regarding simulating the waves as the out put of each stage did not give the desired shape. I had to go back to some youtube videos and some examples online to see what I could improve to my circuit, comparing the picture below to my previous devlog, you can see I made some major changes regarding the amplifier, clipping and tone control stages. NEXT STEP: I’m pretty confident in this schematic so next step would be designing the enclosure then the PCB
KICAD PCB design This was way harder than ltspice for me because i was still trying to navigate the software. A lot of time was spent on looking for the appropriate foot prints. I honestly don’t have much to say apart from needing to cleaning up the layouts. Next Action: I may take a break from Kicad and move on to fusion 360 . That would be better for figuring out what I want in my PCB design...
|
1793440543.0265615
|
1794045343.0265615
|
|
2428
|
My first slack bot! by @DonaA | Stardance
|
DonaA
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @DonaA | Stardance
|
1793242461.1132865
|
1793847261.1132865
|
|
2429
|
OddQuest Air by @airpod | Stardance
|
airpod
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: OddQuest Air by @airpod | Stardance
|
1792723776.0233395
|
1793328576.0233395
|
|
2431
|
Love no matter what by @yose | Stardance
|
yose
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Love no matter what by @yose | Stardance
|
1793206155.1859405
|
1793810955.1859405
|
|
2432
|
Eink Desk Hub by @Timhongphuc | Stardance
|
Timhongphuc
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Eink Desk Hub by @Timhongphuc | Stardance
|
1793451227.775815
|
1794056027.775815
|
|
2433
|
My first slack bot! by @Dom | Stardance
|
Dom
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Dom | Stardance
|
1792788656.3473773
|
1793393456.3473773
|
|
2434
|
Glide by @pranay | Stardance
|
pranay
|
0
|
5.31
|
0
|
[]
|
[{"post_id": 63657, "ts": "202 [{"post_id": 63657, "ts": "2026-09-07T16:13:19Z", "hours": 0.8533, "text": "Devlog 03 Ok, it’s been so long (school takes up too much time). Despite that time, this is a really short devlog. Updates We have a mockup for the UI that we want the app to have. Now, the mockup (since AI made it) focuses a bit too much on just tasks, but the app will be a notes app; just wanted to make sure that was clear. These colors aren’t finalized and neither is the UI, but the design is what we think would work best for our app. The mockup is attached as a picture. Feedback If you guys have any feedback on the UI or just features you want to see in the app (description of app is in the first devlog), you guys can post comments here or add a suggestion on Github: https://github.com/get-glide/Glide-Mac/discussions/9 . Thanks for reading and have a great day!"}, {"post_id": 40495, "ts": "2026-08-04T01:59:56Z", "hours": 2.9492, "text": "Devlog 02 Still the same basic editor as last time, but we are working on UI design right now. We should have a somewhat decided design in a couple of days. More parsing stuff Anyway, I got markdown header formatting working in the app (you can’t notice a difference visually, but the app knows whether you want a # or ## header now). Now, the plan is to work on getting inline formatting to work ( bold , italics , etc). Dates and moving tasks to different days For being able to have a task repeat weekly, the app needs to be aware of the original day that the task was created on. To do this (as you can see in the image), every task gets a @created (yyyy-mm-dd) tag. The other tag you see in the image ( @carried ) means that task was procrastinated on and got moved to the next day or postponed to some other time. Side note Maybe it’s just me, but the git integration in Xcode is confusing. I may or may not have had to redo some code and that is why this devlog has so much time on it. I’ll make sure that my future devlogs aren’t this unproductive when it comes to actually making features. Thanks for reading my devlog and have an amazing day!!"}, {"post_id": 30796, "ts": "2026-07-18T18:02:59Z", "hours": 1.5114, "text": "Devlog 01 What is Glide? Glide is a Mac note-taking/task planner app built for students. You take notes and create tasks by typing things like “9:00 [] Integral rules homework @daily .” The tasks are then parsed live into a clean, structured timeline. In the future, we want to make an iOS app, add sync, and more features that will help students. Also, I’m making this app with @aarnav_sharma and @harieshkarth . Why Glide? Every other note-taking app that we’ve tried is either overwhelming or missing features students (like us) would want. Glide is our attempt to fix that. What I did in these 90 minutes Now that you guys have some content on the app. So far, I’ve made a basic window so that I can on the line parsing stuff. The images attached show you what the line parsing (as of right now) is doing."}]...
|
Title: Glide by @pranay | Stardance
Devlogs:
Devl Title: Glide by @pranay | Stardance
Devlogs:
Devlog 01 What is Glide? Glide is a Mac note-taking/task planner app built for students. You take notes and create tasks by typing things like “9:00 [] Integral rules homework @daily .” The tasks are then parsed live into a clean, structured timeline. In the future, we want to make an iOS app, add sync, and more features that will help students. Also, I’m making this app with @aarnav_sharma and @harieshkarth . Why Glide? Every other note-taking app that we’ve tried is either overwhelming or missing features students (like us) would want. Glide is our attempt to fix that. What I did in these 90 minutes Now that you guys have some content on the app. So far, I’ve made a basic window so that I can on the line parsing stuff. The images attached show you what the line parsing (as of right now) is doing.
Devlog 02 Still the same basic editor as last time, but we are working on UI design right now. We should have a somewhat decided design in a couple of days. More parsing stuff Anyway, I got markdown header formatting working in the app (you can’t notice a difference visually, but the app knows whether you want a # or ## header now). Now, the plan is to work on getting inline formatting to work ( bold , italics , etc). Dates and moving tasks to different days For being able to have a task repeat weekly, the app needs to be aware of the original day that the task was created on. To do this (as you can see in the image), every task gets a @created (yyyy-mm-dd) tag. The other tag you see in the image ( @carried ) means that task was procrastinated on and got moved to the next day or postponed to some other time. Side note Maybe it’s just me, but the git integration in Xcode is confusing. I may or may not have had to redo some code and that is why this devlog has so much time on it. I’ll make sure that my future devlogs aren’t this unproductive when it comes to actually making features. Thanks for reading my devlog and have an amazing day!!
Devlog 03 Ok, it’s been so long (school takes up too much time). Despite that time, this is a really short devlog. Updates We have a mockup for the UI that we want the app to have. Now, the mockup (since AI made it) focuses a bit too much on just tasks, but the app will be a notes app; just wanted to make sure that was clear. These colors aren’t finalized and neither is the UI, but the design is what we think would work best for our app. The mockup is attached as a picture. Feedback If you guys have any feedback on the UI or just features you want to see in the app (description of app is in the first devlog), you guys can post comments here or add a suggestion on Github: https://github.com/get-glide/Glide-Mac/discussions/9 . Thanks for reading and have a great day!...
|
1793156152.2785394
|
1793760952.2785394
|
|
2435
|
Magic Docs by @covell_bernstein | Stardance
|
covell_bernstein
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Magic Docs by @covell_bernstein | Stardance
|
1793447307.6780908
|
1794052107.6780908
|
|
2436
|
My first slack bot! by @satxtornado | Stardance
|
satxtornado
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @satxtornado | Stard Title: My first slack bot! by @satxtornado | Stardance...
|
1793245900.7161498
|
1793850700.7161498
|
|
2437
|
a paradoxical portfolio by @deltarunesangel | Star a paradoxical portfolio by @deltarunesangel | Stardance...
|
deltarunesangel
|
1
|
6.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-25T17:23:52Z", "hours": 6.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "here’s what’s been made thus far… it’s unfinished, but all the major aspects of it (bg, bg music, links, etc.) work just fine. i had some trouble at first with the supabase linking aspect of my project but i managed to figure that out. now i have a cool lil guestbook :) anywho, this is my blood sweat and thankfully not tears. so happy to have a version out at long last", "repo": "https://github.com/deltarunesangel/actual-stuff", "demo": "https://deltarunesangel.github.io/actual-stuff/"}]...
|
[{"post_id": 4616, "ts": "2026 [{"post_id": 4616, "ts": "2026-06-08T00:06:53Z", "hours": 2.9322, "text": "FINALLY finished the guestbook (used supabase) and added background music for every tab!! 🎉 🥳 ✨"}, {"post_id": 2866, "ts": "2026-06-05T18:50:02Z", "hours": 2.4119, "text": "💫 Finished the Splash Screen and Set Up the Fading Transition! 💫"}, {"post_id": 1533, "ts": "2026-06-03T16:47:24Z", "hours": 0.8456, "text": "✨The Boring Basics Completed! (background, basic js, html framework, etc.) ✨"}]...
|
Title: a paradoxical portfolio by @deltarunesangel Title: a paradoxical portfolio by @deltarunesangel | Stardance
Devlogs:
✨The Boring Basics Completed! (background, basic js, html framework, etc.) ✨
💫 Finished the Splash Screen and Set Up the Fading Transition! 💫
FINALLY finished the guestbook (used supabase) and added background music for every tab!! 🎉 🥳 ✨
Ships:
here’s what’s been made thus far… it’s unfinished, but all the major aspects of it (bg, bg music, links, etc.) work just fine. i had some trouble at first with the supabase linking aspect of my project but i managed to figure that out. now i have a cool lil guestbook :) anywho, this is my blood sweat and thankfully not tears. so happy to have a version out at long last...
|
1793278562.0488703
|
1793364962.0488703
|
|
2438
|
My first slack bot! by @ianparedes | Stardance
|
ianparedes
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @ianparedes | Starda Title: My first slack bot! by @ianparedes | Stardance...
|
1793227948.110391
|
1793832748.110391
|