|
6101
|
VisionArch by @raslanyossif | Stardance
|
raslanyossif
|
1
|
117.23
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-03T06:45:42Z", "hours": 101.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "VisionArch is an AI-based architectural design software that allows users to upload 2D floor plans on the platform or draw them manually before receiving an instantaneous top-down 3D photo rendering of the plan. The new changes fixed the bug of the bar displaying incorrect progress, added an authentication blocker that prevents unauthorized users from causing backend errors, created a worker keep alive ping so there are no cold start CORS failures, and repaired missing environment variables, making API calls possible. To try it out, go to vision-arch-two.vercel.app, register using Puter, upload the floor plan, or use the Draw mode to draw the floor plan. After that, just hit Generate 3D Render. You can also share your renderings with other users and rate their projects in return.", "repo": "https://github.com/Yossifraslan/VisionArch", "demo": "https://vision-arch-two.vercel.app/"}]...
|
[{"post_id": 77190, "ts": "202 [{"post_id": 77190, "ts": "2026-10-06T00:37:05Z", "hours": 6.6897, "text": "I decided to change the complete look of this website to something that feels a bit more housy vibe. and made the dark mode into green colored. fixed a bug for generating because each user has a limit, so this time once you reach your limit you will get a message."}, {"post_id": 55500, "ts": "2026-08-27T12:01:14Z", "hours": 7.67, "text": "Spent this session tracking down a login bug that had been bugging me - turns out a security header on my site was quietly blocking the auth popup from talking back to the app, so users had to refresh after signing in for it to actually register. Fixed that, then made the upload box actually prompt you to sign in instead of just… doing nothing when you’re logged out. After that I gave the whole site a real visual identity instead of the generic AI-startup look it had - leaned into a blueprint/drafting theme since it fits an architecture tool, ditched the soft gradient blobs for a grid background, and rebuilt all the buttons with a chunky neo brutalist shadow style. Also added dark mode from scratch - toggle in the navbar, remembers your preference, styled across every page - and caught a dumb bug along the way where one page’s card was using the wrong color variable and turned into an unreadable white blob in dark mode. Fun catch."}, {"post_id": 51522, "ts": "2026-08-21T09:04:00Z", "hours": 1.8747, "text": "What was broken: Login/upload silently failed for signed-out users, and after signing in, the UI wouldn’t reflect it until a manual refresh. What you found: Console showed Cross-Origin-Opener-Policy policy would block the window.closed call - the site’s COOP header was preventing Puter’s auth popup from reporting back to the app. The fix: Added vercel.json with Cross-Origin-Opener-Policy: unsafe-none, plus made the upload dropzone and “Get Started” button properly prompt/guard sign-in instead of failing silently. Verified: Signed in -> UI updated instantly, no refresh -> uploaded a floor plan -> rendered correctly end-to-end."}, {"post_id": 39911, "ts": "2026-08-03T06:41:10Z", "hours": 8.8069, "text": "TIME FOR DEVLOG :> For VisionArch you can test it/ generate 4-5 times then you hit limit and need to wait for your limit to reset. Resolved issues regarding the progress bar which was working incorrectly. Introduced a new authorization guard to prevent unauthorized people from causing authentication issues upon webpage loading. Added a silent worker ping to ensure that the Puter worker is awake prior to requests and thereby eliminate cold starts with multiple CORS errors and 404s during access of community pages. Corrected the missing environment variables in local configuration and Vercel dashboard."}, {"post_id": 18248, "ts": "2026-06-29T10:08:25Z", "hours": 9.4314, "text": "TIME FOR DEVLOG> was busy so I slowed down. Fixed: The Puter consent popup was getting shown to all visitors, instantly Discovered that the getCurrentUser() function is executing puter.auth.getUser() every time the page loads, for every single visitor, including those who haven’t signed in at all. This was triggering the Puter consent modal asking whether the user consents to seeing “this site uses Puter”. Fixed by adding an additional call to puter.auth.isSignedIn(), a synchronous function that doesn’t require network access, which checks if a session already exists. Users who aren’t logged in get directed straight to the homepage now. Fixed: Regeneration with a different style required a refresh. This was due to double invocation of the setCurrentImage() method, which overrode the just-completed AI-rendered image with the stored hosted URL. Removed the redundant call, so that the UI respects the freshly generated image. Improved the “no text in renders” requirement. Some renders featured room labels like “Bathroom” or “Bedroom”. Re-wrote the prompt to the AI, putting text-removal above all other rules, emphasizing that the room label informs furniture choices but should not be present itself, and instructing the AI to include the self-check step in the result. Added README Credits, features, tech stack, architecture notes, local development instructions, Vercel deployment instructions. Next: going through the whole app end-to-end once more - code and UI - before calling this fully submitted"}, {"post_id": 14959, "ts": "2026-06-24T09:16:23Z", "hours": 9.4006, "text": "WHAT’S NEW Projects no longer have to stay stuck as “Residence 1239812737128.” Now you can simply click the title in the visualizer, and it becomes editable, just edit and hit enter to save. I also added a Floor plan template on draw page because not everyone wants to start from a blank canvas, so I added 5 starter templates (Studio, 1-Bedroom, 2-Bedroom, Open Loft, Family Home) built with tldraw’s shape API. One click loads a labeled room layout onto the canvas, which you can edit and all before generating the 3D render. Additionally, I added a hint for new users, so they immediately understand that they need to draw and generate instead of just thinking it’s blank canvas not knowing what to do. Fixed: logged-out visitors couldn’t see Community at all This is an issue that had a greater depth than it appeared to be. All calls made through the workers.exec() of Puter’s automatically attach the user’s session to the call. Although, this thoroughly works for authenticated actions, any calls made by un-logged-in users will not execute properly, even on routes that are not required to be authenticated on the server side. The read-only endpoints (public project list, and comments) were switched to plain fetch() calls, as they do not require a user session to execute in any way. Therefore, un-logged-in users can now browse the Community and view designs. Fixed: voting did nothing when logged out Similar to the above issue, there were simply no active buttons for guests to ‘vote’ at all. Now, when an un-logged-in visitor clicks on the Upvote / Downvote button (or tries to comment), it now brings up the Puter sign-in pop-up automatically. So, it allows for a real call to action rather than a ‘dead click’."}, {"post_id": 12934, "ts": "2026-06-21T05:24:55Z", "hours": 9.4869, "text": "WHAT’S NEW: Not everyone has a floor plan image lying around, so I added a full drawing canvas using tldraw. You can now sketch a layout freehand, with shapes and text, then hit “Generate 3D Render” and it feeds straight into the same AI pipeline as an uploaded image. I recently discovered that my style picker feature (Modern/Minimalist/Industrial/Luxury) created random styled images as opposed to rendering the correct object from the actual floor plan and thus would just replace my existing prompt with a new one capable of producing an appropriate render. To remedy this issue, I created short style modifiers that will all be appending themselves to a single base prompt. As a result, there are now clear differences between Modern/Industrial/Luxury styles, and the base wall geometric shapes are maintained no matter which style is used. Still need to improve upon the Minimalist-style image as it still looks so close to the other styles due to its similarity with the original base aesthetic."}, {"post_id": 11827, "ts": "2026-06-19T08:24:22Z", "hours": 9.5761, "text": "It’s been a TOUGH coding day :> WHAT’ NEW: Share/unshare system allows users to share files from their local ‘Storage’ with other users and vice versa. I learned that Puter’s data model has separate user (for their own files) and me (for shared/app files), which has taken me a number of attempts to understand. Added a confirmation dialog with custom styling to the delete function instead of a boring confirmation dialog. In the works are an upvote/downvote and threaded comment feature to allow users to vote on designs in the community similar to Reddit’s. Biggest debugging lesson of the day: CORS preflight requests need to define OPTIONS handlers on all routes, not just those that need CORS. One example was an attempt to resolve a CORS Access-Control-Allow-Methods header, which took so long to debug."}, {"post_id": 10453, "ts": "2026-06-17T05:45:25Z", "hours": 9.7019, "text": "The pull request adds image export functionality and a before/after comparison slider to the visualizer route, expands WebP upload support, and introduces the react-compare-slider dependency. Configuration files and memory tracking are updated accordingly. Changes: Image Export & Comparison UI - Added HandleExport function to trigger PNG downloads of currentImage; introduced ReactCompareSlider UI panel to display before (sourceimage) and after (currentimage) comparison with conditional rendering; added react-compare-slider dependency. Upload Enchantment - Expanded accepted file types to include .webp format alongside existing .jpg, jpeg, and .png support. Workspace & Development Tracking - Rebalanced IDE ChangeListManager entries; added two new trajectory analysis entries documenting plans for handling sensitive env file history and cross-origin image downloads."}, {"post_id": 9100, "ts": "2026-06-15T06:38:33Z", "hours": 9.4303, "text": "This pull request introduces a backend project management system via a new Puter worker module that provides REST APIs for persisting, listing, and retrieving design projects. The frontend is updated to load projects on startup, handle project creation with persistence, and enable navigation between project visualization with stateful project data. Next, I’m planning on doing a comparison between before and after."}, {"post_id": 7962, "ts": "2026-06-13T09:02:05Z", "hours": 9.8583, "text": "A new AI-powered 3D visualization feature is introduced with fetchAsDataUrl and generate3DView functions in lib/ai/action.ts that integrate with puter.ai for image generation. The Visualizer route is enhanced with state management, automatic generation flow, and a complete UI redesign including navigation, project metadata render area and loading states."}, {"post_id": 6209, "ts": "2026-06-10T12:53:25Z", "hours": 9.5592, "text": "I Implemented project persistence and retrieval functionality by introducing hosting utilities for image uploads, a project creation action that prepares and saves project data with hosted assets, enables dynamic project listing on the home page, and updates the visualizer to consume project state from router navigation. I faced multiple Errors where when I drag n drop a PNG file the loading freezes which took time to fix but made it work. The goal is to create a whole 3D architectural render of this boring 2D design. and also design this page itself and make it nicer."}, {"post_id": 4133, "ts": "2026-06-07T10:27:01Z", "hours": 8.3689, "text": "Added a Projects list section, so everything is saved under that. I’ve been dealing with a bunch of errors that I’m fixing, took me time to find that specific error. Working on Hosting-Images in a branch and thinking of other ideas to come up with. This is my first big project that I did, so that may be the reason I’m facing many problems. However, everything is going good so far. Hope it becomes good when I have the end webpage."}, {"post_id": 2628, "ts": "2026-06-05T08:17:18Z", "hours": 5.5428, "text": "In the video, I’ve made it to be able to upload your floor plan by drag and drop or simply clicking like what was shown in the video. I’ve faced some errors with branches mixing up. Also, next step will be hosting images."}, {"post_id": 2013, "ts": "2026-06-04T09:16:29Z", "hours": 2.0736, "text": "I’m working on an architectural 3D design where you can upload your floor plan and edit it. Currently I did the Homepage and I’m working on being able to upload your floor plan."}]...
|
Title: VisionArch by @raslanyossif | Stardance
De Title: VisionArch by @raslanyossif | Stardance
Devlogs:
I’m working on an architectural 3D design where you can upload your floor plan and edit it. Currently I did the Homepage and I’m working on being able to upload your floor plan.
In the video, I’ve made it to be able to upload your floor plan by drag and drop or simply clicking like what was shown in the video. I’ve faced some errors with branches mixing up. Also, next step will be hosting images.
Added a Projects list section, so everything is saved under that. I’ve been dealing with a bunch of errors that I’m fixing, took me time to find that specific error. Working on Hosting-Images in a branch and thinking of other ideas to come up with. This is my first big project that I did, so that may be the reason I’m facing many problems. However, everything is going good so far. Hope it becomes good when I have the end webpage.
I Implemented project persistence and retrieval functionality by introducing hosting utilities for image uploads, a project creation action that prepares and saves project data with hosted assets, enables dynamic project listing on the home page, and updates the visualizer to consume project state from router navigation. I faced multiple Errors where when I drag n drop a PNG file the loading freezes which took time to fix but made it work. The goal is to create a whole 3D architectural render of this boring 2D design. and also design this page itself and make it nicer.
A new AI-powered 3D visualization feature is introduced with fetchAsDataUrl and generate3DView functions in lib/ai/action.ts that integrate with puter.ai for image generation. The Visualizer route is enhanced with state management, automatic generation flow, and a complete UI redesign including navigation, project metadata render area and loading states.
This pull request introduces a backend project management system via a new Puter worker module that provides REST APIs for persisting, listing, and retrieving design projects. The frontend is updated to load projects on startup, handle project creation with persistence, and enable navigation between project visualization with stateful project data. Next, I’m planning on doing a comparison between before and after.
The pull request adds image export functionality and a before/after comparison slider to the visualizer route, expands WebP upload support, and introduces the react-compare-slider dependency. Configuration files and memory tracking are updated accordingly. Changes: Image Export & Comparison UI - Added HandleExport function to trigger PNG downloads of currentImage; introduced ReactCompareSlider UI panel to display before (sourceimage) and after (currentimage) comparison with conditional rendering; added react-compare-slider dependency. Upload Enchantment - Expanded accepted file types to include .webp format alongside existing .jpg, jpeg, and .png support. Workspace & Development Tracking - Rebalanced IDE ChangeListManager entries; added two new trajectory analysis entries documenting plans for handling sensitive env file history and cross-origin image downloads.
It’s been a TOUGH coding day :> WHAT’ NEW: Share/unshare system allows users to share files from their local ‘Storage’ with other users and vice versa. I learned that Puter’s data model has separate user (for their own files) and me (for shared/app files), which has taken me a number of attempts to understand. Added a confirmation dialog with custom styling to the delete function instead of a boring confirmation dialog. In the works are an upvote/downvote and threaded comment feature to allow users to vote on designs in the community similar to Reddit’s. Biggest debugging lesson of the day: CORS preflight requests need to define OPTIONS handlers on all routes, not just those that need CORS. One example was an attempt to resolve a CORS Access-Control-Allow-Methods header, which took so long to debug.
WHAT’S NEW: Not everyone has a floor plan image lying around, so I added a full drawing canvas using tldraw. You can now sketch a layout freehand, with shapes and text, then hit “Generate 3D Render” and it feeds straight into the same AI pipeline as an uploaded image. I recently discovered that my style picker feature (Modern/Minimalist/Industrial/Luxury) created random styled images as opposed to rendering the correct object from the actual floor plan and thus would just replace my existing prompt with a new one capable of producing an appropriate render. To remedy this issue, I created short style modifiers that will all be appending themselves to a single base prompt. As a result, there are now clear differences between Modern/Industrial/Luxury styles, and the base wall geometric shapes are maintained no matter which style is used. Still need to improve upon the Minimalist-style image as it still looks so close to the other styles due to its similarity with the original base aesthetic.
WHAT’S NEW Projects no longer have to stay stuck as “Residence 1239812737128.” Now you can simply click the title in the visualizer, and it becomes editable, just edit and hit enter to save. I also added a Floor plan template on draw page because not everyone wants to start from a blank canvas, so I added 5 starter templates (Studio, 1-Bedroom, 2-Bedroom, Open Loft, Family Home) built with tldraw’s shape API. One click loads a labeled room layout onto the canvas, which you can edit and all before generating the 3D render. Additionally, I added a hint for new users, so they immediately understand that they need to draw and generate instead of just thinking it’s blank canvas not knowing what to do. Fixed: logged-out visitors couldn’t see Community at all This is an issue that had a greater depth than it appeared to be. All calls made through the workers.exec() of Puter’s automatically attach the user’s session to the call. Although, this thoroughly works for authenticated actions, any calls made by un-logged-in users will not execute properly, even on routes that are not required to be authenticated on the server side. The read-only endpoints (public project list, and comments) were switched to plain fetch() calls, as they do not require a user session to execute in any way. Therefore, un-logged-in users can now browse the Community and view designs. Fixed: voting did nothing when logged out Similar to the above issue, there were simply no active buttons for guests to ‘vote’ at all. Now, when an un-logged-in visitor clicks on the Upvote / Downvote button (or tries to comment), it now brings up the Puter sign-in pop-up automatically. So, it allows for a real call to action rather than a ‘dead click’.
TIME FOR DEVLOG> was busy so I slowed down. Fixed: The Puter consent popup was getting shown to all visitors, instantly Discovered that the getCurrentUser() function is executing puter.auth.getUser() every time the page loads, for every single visitor, including those who haven’t signed in at all. This was triggering the Puter consent modal asking whether the user consents to seeing “this site uses Puter”. Fixed by adding an additional call to puter.auth.isSignedIn(), a synchronous function that doesn’t require network access, which checks if a session already exists. Users who aren’t logged in get directed straight to the homepage now. Fixed: Regeneration with a different style required a refresh. This was due to double invocation of the setCurrentImage() method, which overrode the just-completed AI-rendered image with the stored hosted URL. Removed the redundant call, so that the UI respects the freshly generated image. Improved the “no text in renders” requirement. Some renders featured room labels like “Bathroom” or “Bedroom”. Re-wrote the prompt to the AI, putting text-removal above all other rules, emphasizing that the room label informs furniture choices but should not be present itself, and instructing the AI to include the self-check step in the result. Added README Credits, features, tech stack, architecture notes, local development instructions, Vercel deployment instructions. Next: going through the whole app end-to-end once more - code and UI - before calling this fully submitted
TIME FOR DEVLOG :> For VisionArch you can test it/ generate 4-5 times then you hit limit and need to wait for your limit to reset. Resolved issues regarding the progress bar which was working incorrectly. Introduced a new authorization guard to prevent unauthorized people from causing authentication issues upon webpage loading. Added a silent worker ping to ensure that the Puter worker is awake prior to requests and thereby eliminate cold starts with multiple CORS errors and 404s during access of community pages. Corrected the missing environment variables in local configuration and Vercel dashboard.
What was broken: Login/upload silently failed for signed-out users, and after signing in, the UI wouldn’t reflect it until a manual refresh. What you found: Console showed Cross-Origin-Opener-Policy policy would block the window.closed call - the site’s COOP header was preventing Puter’s auth popup from reporting back to the app. The fix: Added vercel.json with Cross-Origin-Opener-Policy: unsafe-none, plus made the upload dropzone and “Get Started” button properly prompt/guard sign-in instead of failing silently. Verified: Signed in -> UI updated instantly, no refresh -> uploaded a floor plan -> rendered correctly end-to-end.
Spent this session tracking down a login bug that had been bugging me - turns out a security header on my site was quietly blocking the auth popup from talking back to the app, so users had to refresh after signing in for it to actually register. Fixed that, then made the upload box actually prompt you to sign in instead of just… doing nothing when you’re logged out. After that I gave the whole site a real visual identity instead of the generic AI-startup look it had - leaned into a blueprint/drafting theme since it fits an architecture tool, ditched the soft gradient blobs for a grid background, and rebuilt all the buttons with a chunky neo brutalist shadow style. Also added dark mode from scratch - toggle in the navbar, remembers your preference, styled across every page - and caught a dumb bug along the way where one page’s card was using the wrong color variable and turned into an unreadable white blob in dark mode. Fun catch.
I decided to change the complete look of this website to something that feels a bit more housy vibe. and made the dark mode into green colored. fixed a bug for generating because each user has a limit, so this time once you reach your limit you will get a message.
Ships:
VisionArch is an AI-based architectural design software that allows users to upload 2D floor plans on the platform or draw them manually before receiving an instantaneous top-down 3D photo rendering of the plan. The new changes fixed the bug of the bar displaying incorrect progress, added an authentication blocker that prevents unauthorized users from causing backend errors, created a worker keep alive ping so there are no cold start CORS failures, and repaired missing environment variables, making API calls possible. To try it out, go to vision-arch-two.vercel.app, register using Puter, upload the floor plan, or use the Draw mode to draw the floor plan. After that, just hit Generate 3D Render. You can also share your renderings with other users and rate their projects in return....
|
1793271085.1658545
|
1793357485.1658545
|
|
6102
|
My awesome macropad! by @thebiraj_hkr | Stardance
|
thebiraj_hkr
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @thebiraj_hkr | Sta Title: My awesome macropad! by @thebiraj_hkr | Stardance...
|
1792799454.6793246
|
1793404254.6793246
|
|
6103
|
Celestial Candbox by @Goboshow | Stardance
|
Goboshow
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Celestial Candbox by @Goboshow | Stardance
|
1793231461.2077155
|
1793836261.2077155
|
|
6104
|
Skillbridge-project by @iranpaccy | Stardance
|
iranpaccy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Skillbridge-project by @iranpaccy | Stardan Title: Skillbridge-project by @iranpaccy | Stardance...
|
1792637515.817817
|
1793242315.817817
|
|
6105
|
My awesome macropad! by @Daellix | Stardance
|
Daellix
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Daellix | Stardanc Title: My awesome macropad! by @Daellix | Stardance...
|
1792777821.4172714
|
1793382621.4172714
|
|
6106
|
Oracle Copilot by @hiepdevo2 | Stardance
|
hiepdevo2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Oracle Copilot by @hiepdevo2 | Stardance
|
1792792264.8337874
|
1793397064.8337874
|
|
6107
|
My awesome macropad! by @S4x0o | Stardance
|
S4x0o
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @S4x0o | Stardance
|
1792644766.586013
|
1793249566.586013
|
|
6108
|
My awesome macropad! by @argparse | Stardance
|
argparse
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @argparse | Stardan Title: My awesome macropad! by @argparse | Stardance...
|
1793271148.160748
|
1793875948.160748
|
|
6109
|
TheAshmiEditor by @Jeehank | Stardance
|
Jeehank
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: TheAshmiEditor by @Jeehank | Stardance
|
1793188526.7116783
|
1793793326.7116783
|
|
6110
|
My first slack bot! by @Sanvi | Stardance
|
Sanvi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Sanvi | Stardance
|
1793192023.945369
|
1793796823.945369
|
|
6111
|
My first slack bot! by @Shrijanagain | Stardance
|
Shrijanagain
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Shrijanagain | Star Title: My first slack bot! by @Shrijanagain | Stardance...
|
1793181335.0744524
|
1793786135.0744524
|
|
6112
|
???? by @Kuzu | Stardance
|
Kuzu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ???? by @Kuzu | Stardance
|
1792767290.5051367
|
1793372090.5051367
|
|
6113
|
Untitled by @Namaami | Stardance
|
Namaami
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Namaami | Stardance
|
1792630349.4461842
|
1793235149.4461842
|
|
6114
|
Website by @Boogie_Woogie | Stardance
|
Boogie_Woogie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Website by @Boogie_Woogie | Stardance
|
1792644568.9955168
|
1793249368.9955168
|
|
6115
|
Air Quality sensor by @oliiverdwyer | Stardance
|
oliiverdwyer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Air Quality sensor by @oliiverdwyer | Stard Title: Air Quality sensor by @oliiverdwyer | Stardance...
|
1792734441.3798382
|
1793339241.3798382
|
|
6116
|
Untitled by @Lord_Julia | Stardance
|
Lord_Julia
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Lord_Julia | Stardance
|
1792691327.8804898
|
1793296127.8804898
|
|
6117
|
My first slack bot! by @muskan354b0 | Stardance
|
muskan354b0
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @muskan354b0 | Stard Title: My first slack bot! by @muskan354b0 | Stardance...
|
1792795692.5285
|
1793400492.5285
|
|
6118
|
My first slack bot! by @HappySoul | Stardance
|
HappySoul
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @HappySoul | Stardan Title: My first slack bot! by @HappySoul | Stardance...
|
1792749056.5982146
|
1793353856.5982146
|
|
6119
|
6502 Emulator by @NiDo | Stardance
|
NiDo
|
0
|
9.39
|
0
|
[]
|
[{"post_id": 2249, "ts": "2026 [{"post_id": 2249, "ts": "2026-06-04T17:14:43Z", "hours": 1.6544, "text": "I finished implementing everything!! I’ve tested it with Klaus’s test suite and it passed the entire test (the loop at 3469 means the test passed) So ya, that’s the end of the project I guess. I’ll just add some stuff and ship it."}, {"post_id": 1990, "ts": "2026-06-04T07:59:44Z", "hours": 4.4517, "text": "So I’ve locked in yesterday and this morning and implemented about 118 of the total 151 instructions (78%). I’ve lost track of what all instructions I implemented as instead of implementing instruction wise, I’ve began implementing them in the order Klaus’s test suite tests them. Currently, it’s able to run 44119 cycles. I’m hoping that after a few more instructions it can go up to about 60k but let’s see. I’m planning to implement it till it gets to 60k today."}, {"post_id": 1317, "ts": "2026-06-03T07:31:14Z", "hours": 3.2856, "text": "So currently, I’ve implemented about 55 of the total 151 instructions. I think I’ll finish implementing the rest by the end of this week."}]...
|
Title: 6502 Emulator by @NiDo | Stardance
Devlogs Title: 6502 Emulator by @NiDo | Stardance
Devlogs:
So currently, I’ve implemented about 55 of the total 151 instructions. I think I’ll finish implementing the rest by the end of this week.
So I’ve locked in yesterday and this morning and implemented about 118 of the total 151 instructions (78%). I’ve lost track of what all instructions I implemented as instead of implementing instruction wise, I’ve began implementing them in the order Klaus’s test suite tests them. Currently, it’s able to run 44119 cycles. I’m hoping that after a few more instructions it can go up to about 60k but let’s see. I’m planning to implement it till it gets to 60k today.
I finished implementing everything!! I’ve tested it with Klaus’s test suite and it passed the entire test (the loop at 3469 means the test passed) So ya, that’s the end of the project I guess. I’ll just add some stuff and ship it....
|
1792799442.8723328
|
1793404242.8723328
|
|
6120
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792936259.905422
|
1793800259.905422
|
|
6121
|
Untitled project by @kristoferp | Stardance
|
kristoferp
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @kristoferp | Stardance
|
1792684111.3058977
|
1793288911.3058977
|
|
6122
|
Personal portfolio by @jonas_gaden | Stardance
|
jonas_gaden
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Personal portfolio by @jonas_gaden | Starda Title: Personal portfolio by @jonas_gaden | Stardance...
|
1792904061.9672074
|
1793768061.9672074
|
|
6123
|
DND TUI by @Chris-B | Stardance
|
Chris-B
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DND TUI by @Chris-B | Stardance
|
1793184694.147813
|
1793789494.147813
|
|
6124
|
My first slack bot! by @anyaa | Stardance
|
anyaa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @anyaa | Stardance
|
1792716844.2204285
|
1793321644.2204285
|
|
6125
|
GhOsT by @GhOsT_ | Stardance
|
GhOsT_
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-10T16:21:54Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a slack bot which impersonate me. Like same name and profile. Then there are many commands some of them i am still working upon. The biggest challange was making the bot work. The guide helps a lot i followed it line by line more over i used AI a bit to help me with ideas for command and formatting the texts to look more professional. People can type /ghost-help to know the features etc.", "repo": "https://github.com/surajjha0622/GhOsT", "demo": "https://hackclub.enterprise.slack.com/archives/C0BGGH6TQ2Z"}]...
|
[{"post_id": 25562, "ts": "202 [{"post_id": 25562, "ts": "2026-07-09T21:46:08Z", "hours": 1.0317, "text": "DEvlog 1 FInished the slackbot After so many days….well it took much more time cause i slacked off in between but nvm finally the bot is here 24/7 live. Features 👻 /ghost-help — Displays all available commands🪙 /ghost-coinflip — Flip a virtual coin 🎲 /ghost-roll — Roll a dice with a custom number of sides 🎯 /ghost-pick — Randomly choose from multiple options 🎱 /ghost-8ball — Magic 8 Ball answers for yes/no questions 😂 /ghost-roast — Generates a random roast 🔮 /ghost-fortune — Receive a random fortune 🎨 /ghost-color — Generate a random HEX color 🔑 /ghost-password — Create a secure random password 📸 /ghost-quote — Placeholder for quote image generation (coming next!) What I learned Building Slack apps using Slack Bolt -Creating and handling slash commands -Using environment variables securely -Deploying Node.js apps on Hack Club Nest -Keeping applications running 24/7 using PM2 -Basic Linux server management and SSH"}]...
|
Title: GhOsT by @GhOsT_ | Stardance
Devlogs:
DEvl Title: GhOsT by @GhOsT_ | Stardance
Devlogs:
DEvlog 1 FInished the slackbot After so many days….well it took much more time cause i slacked off in between but nvm finally the bot is here 24/7 live. Features 👻 /ghost-help — Displays all available commands🪙 /ghost-coinflip — Flip a virtual coin 🎲 /ghost-roll — Roll a dice with a custom number of sides 🎯 /ghost-pick — Randomly choose from multiple options 🎱 /ghost-8ball — Magic 8 Ball answers for yes/no questions 😂 /ghost-roast — Generates a random roast 🔮 /ghost-fortune — Receive a random fortune 🎨 /ghost-color — Generate a random HEX color 🔑 /ghost-password — Create a secure random password 📸 /ghost-quote — Placeholder for quote image generation (coming next!) What I learned Building Slack apps using Slack Bolt -Creating and handling slash commands -Using environment variables securely -Deploying Node.js apps on Hack Club Nest -Keeping applications running 24/7 using PM2 -Basic Linux server management and SSH
Ships:
I made a slack bot which impersonate me. Like same name and profile. Then there are many commands some of them i am still working upon. The biggest challange was making the bot work. The guide helps a lot i followed it line by line more over i used AI a bit to help me with ideas for command and formatting the texts to look more professional. People can type /ghost-help to know the features etc....
|
1793314538.8697085
|
1793400938.8697085
|
|
6126
|
My awesome macropad! by @sarahh | Stardance
|
sarahh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sarahh | Stardance
|
1793029652.8135722
|
1793634452.8135722
|
|
6127
|
Untitled by @Joey | Stardance
|
Joey
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Joey | Stardance
|
1792792370.9777899
|
1793397170.9777899
|
|
6128
|
Learning Unity by @Joey | Stardance
|
Joey
|
0
|
4.03
|
0
|
[]
|
[{"post_id": 2465, "ts": "2026 [{"post_id": 2465, "ts": "2026-06-04T23:41:17Z", "hours": 0.5836, "text": "Van now moves with w,a.s.d"}, {"post_id": 2437, "ts": "2026-06-04T22:42:09Z", "hours": 1.2153, "text": "Learning about moveInput"}, {"post_id": 2078, "ts": "2026-06-04T12:08:51Z", "hours": 0.895, "text": "Yay it can knock over a traffic cone :D"}, {"post_id": 1861, "ts": "2026-06-04T02:16:22Z", "hours": 0.3333, "text": "Halfway through project 1!"}, {"post_id": 1388, "ts": "2026-06-03T12:00:03Z", "hours": 1.0, "text": "Still working on first tutorial project"}]...
|
Title: Learning Unity by @Joey | Stardance
Devlog Title: Learning Unity by @Joey | Stardance
Devlogs:
Still working on first tutorial project
Halfway through project 1!
Yay it can knock over a traffic cone :D
Learning about moveInput
Van now moves with w,a.s.d...
|
1792788873.3922908
|
1793393673.3922908
|
|
6129
|
ContribBot_REPO by @phantomlegends381 | Stardance
|
phantomlegends381
|
1
|
2.3
|
9
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-15T23:19:32Z", "hours": 2.0, "multiplier": 5.99, "payout": 9, "blessing": "neutral", "text": "I made a slack bot which has 4-5 different commands it can track and gives a leaderboard of people with most commits in temrs of 1st, 2nd, 3rd. Also has a command which gives extra coordinates of place in terms of latitude and longtiude. The main is space once which has a from sample list of planets in readme it can give you a random pic and random fact of the planet. The things I found challenging were to host 24/7 on nest which i did by giving nest permissions to don’t terminate my background process when i close powershell. Also putting bootprint space package into my api was also challenging. I am proud of my coordinate map command and github commit history leaderboard command and the fact that my app is 24/7", "repo": "https://github.com/phantomlegends381-max/Contribot-Repo", "demo": "https://hackclub.enterprise.slack.com/archives/C0B96454ZHR"}]...
|
[{"post_id": 12922, "ts": "202 [{"post_id": 12922, "ts": "2026-06-21T04:54:18Z", "hours": 0.3028, "text": "Fixed my shipping errors . Gave the right demo link for the slack bot. Gave updated auth permissions"}, {"post_id": 7181, "ts": "2026-06-12T00:01:14Z", "hours": 0.9297, "text": "Used API keys from OpenStreetMap and implemented a city, Country based system. Important functions used for /beatifymaps. parseMapsCommand(text) Reads what the user typed after /beatifymaps. It decides if the user wants help, place search, or distance mode. geocodePlace(query) Searches OpenStreetMap for a place like Tokyo, Japan or Los Angeles. getNominatimHeaders() Adds the required User-Agent header for OpenStreetMap Nominatim. getDistanceMiles(fromPlace, toPlace) Calculates distance between two places using their latitude and longitude. buildPlaceResponse(query, place) Creates the nice Slack Block Kit card for one searched place. buildDistanceResponse(fromPlace, toPlace, distanceMiles) Creates the nice Slack Block Kit card for distance between two places. buildFlagImageUrl(countryCode) Creates a flag image URL for the country. getOpenStreetMapUrl(place) Creates the “View Map” button link."}, {"post_id": 6353, "ts": "2026-06-10T18:07:56Z", "hours": 0.5933, "text": "👍Still debugging and polishing the github token credit. Right now jsut plain text with github profile name with number of commits . Still need to add more features"}]...
|
Title: ContribBot_REPO by @phantomlegends381 | Sta Title: ContribBot_REPO by @phantomlegends381 | Stardance
Devlogs:
👍Still debugging and polishing the github token credit. Right now jsut plain text with github profile name with number of commits . Still need to add more features
Used API keys from OpenStreetMap and implemented a city, Country based system. Important functions used for /beatifymaps. parseMapsCommand(text) Reads what the user typed after /beatifymaps. It decides if the user wants help, place search, or distance mode. geocodePlace(query) Searches OpenStreetMap for a place like Tokyo, Japan or Los Angeles. getNominatimHeaders() Adds the required User-Agent header for OpenStreetMap Nominatim. getDistanceMiles(fromPlace, toPlace) Calculates distance between two places using their latitude and longitude. buildPlaceResponse(query, place) Creates the nice Slack Block Kit card for one searched place. buildDistanceResponse(fromPlace, toPlace, distanceMiles) Creates the nice Slack Block Kit card for distance between two places. buildFlagImageUrl(countryCode) Creates a flag image URL for the country. getOpenStreetMapUrl(place) Creates the “View Map” button link.
Fixed my shipping errors . Gave the right demo link for the slack bot. Gave updated auth permissions
Ships:
I made a slack bot which has 4-5 different commands it can track and gives a leaderboard of people with most commits in temrs of 1st, 2nd, 3rd. Also has a command which gives extra coordinates of place in terms of latitude and longtiude. The main is space once which has a from sample list of planets in readme it can give you a random pic and random fact of the planet. The things I found challenging were to host 24/7 on nest which i did by giving nest permissions to don’t terminate my background process when i close powershell. Also putting bootprint space package into my api was also challenging. I am proud of my coordinate map command and github commit history leaderboard command and the fact that my app is 24/7...
|
1793281733.9719815
|
1793368133.9719815
|
|
6130
|
3V Plugin Power Supplier by @hacha-mouse | Stardan 3V Plugin Power Supplier by @hacha-mouse | Stardance...
|
hacha-mouse
|
1
|
1.0
|
4
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-06T15:00:38Z", "hours": 1.0, "multiplier": 3.17, "payout": 4, "blessing": "neutral", "text": "I made a device to provide 3V plugin power to microphones using CR2032 coin battery. Why I built this? I built this because I wanted to make use of my microphone which required 2-5V plugin power. I had nothing that can provide some power to the microphone, and there weren’t any products at affordable prices. How can I try it? This is a hardware project, so if you really wish to try it yourself, please make one yourself!", "repo": "https://github.com/hatya-mouse/plugin-power-supplier", "demo": ""}]...
|
[{"post_id": 3524, "ts": "2026 [{"post_id": 3524, "ts": "2026-06-06T14:37:45Z", "hours": 0.3514, "text": "I’ve finished editing a demo video! https://www.youtube.com/watch?v=aCJ3Ztfm0Tg"}, {"post_id": 3415, "ts": "2026-06-06T10:31:31Z", "hours": 0.5236, "text": "I’ve improved the README for this"}, {"post_id": 3401, "ts": "2026-06-06T09:47:45Z", "hours": 0.5008, "text": "Finished soldering the plugin power supplier! It works perfectly when connected to microphone"}]...
|
Title: 3V Plugin Power Supplier by @hacha-mouse | Title: 3V Plugin Power Supplier by @hacha-mouse | Stardance
Devlogs:
Finished soldering the plugin power supplier! It works perfectly when connected to microphone
I’ve improved the README for this
I’ve finished editing a demo video! https://www.youtube.com/watch?v=aCJ3Ztfm0Tg
Ships:
I made a device to provide 3V plugin power to microphones using CR2032 coin battery. Why I built this? I built this because I wanted to make use of my microphone which required 2-5V plugin power. I had nothing that can provide some power to the microphone, and there weren’t any products at affordable prices. How can I try it? This is a hardware project, so if you really wish to try it yourself, please make one yourself!...
|
1793307361.4915154
|
1793393761.4915154
|
|
6131
|
MicroDev128 Project by @I-like-BWRs | Stardance
|
I-like-BWRs
|
1
|
29.12
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-05T21:06:22Z", "hours": 0.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "AVR128DB28 Concept Board. Being made right now", "repo": "https://github.com/ILikeBWRs/MicroDev128", "demo": ""}]...
|
[{"post_id": 70291, "ts": "202 [{"post_id": 70291, "ts": "2026-09-18T21:43:11Z", "hours": 0.3333, "text": "Finished my BOM and sent and email THANK YOU PCBWay for sponsoring this project! I needed to lock in. I (mostly off-camera) worked on selecting parts for the BOM. This included the parts for the MicroDevUPDI Programmer, and the MicroDev128-32P. I wrote a email to PCBWay (off-camera) asking if they will continue to sponsor me. (fingers crossed as the Hack Club grant just covered the first lot of parts). Because Stardance ends in 2 weeks - and shipping and assembly takes more than 2 weeks this will be the last devlog on stardance :( Thank you to all who have helped with this project - including you * reading this now. I really appreciate your support!"}, {"post_id": 66999, "ts": "2026-09-13T00:53:38Z", "hours": 1.9167, "text": "Finished the Rev1B and started work on the UPDI programmer I finished work on the MicroDev128-32P Rev1B. It some new things that you can see in the past devlogs. For MicroDevUPDI I made a simple USB to UPDI programmer. It uses the CH340E - which has an internal crystal. small footprint and needs few external parts. I added reverse polarity protection. It uses USB-C for its connector and is 2 small two layer board. I changed the main MicroDev128 repo to be a main landing page - with each board having its own repo."}, {"post_id": 66311, "ts": "2026-09-12T02:21:53Z", "hours": 3.3525, "text": "FINISHED Rev 1B I finished this revision by adding a few things: A full changelog bellow Rounded corners (idk just looks better in my opionion) Changed the TVS blows a fuse thing for a diode for proper reverse polarity protection Rearranged all the components Fixed some decoupling caps that were linked to GND and 5V but not even close to the acuall pin. Changed the UPDI header to be a 3x1 to save board space. As per request of a guy in my schools robotics club the board now fetures 3 neopixels (couldnt do his other request of a diode on every pin) Re-jigged the silkscreen labels so they should be acually readable Fixed the LT8653S being wired for burst mode ( which is great for battery life, but has higher ripple (I measured 30mV peak to peak with my scope) Now it is wired for FCM (Forced Countiuous Mode) for that super low ripple that the LT8653S is capable of. I learnt a thing or two about routing and made the pins for everything as close as possible to each other. Most likely I forgot to mention some stuff that I changed …. Anyway … turning out to be a genuinely useful board. Had the MVIO comunicating with a 3.3V SD card module yesterday no problems. Until next time … ILikeBWRs - Keegan Muller"}, {"post_id": 66143, "ts": "2026-09-11T19:28:32Z", "hours": 1.0169, "text": "Rearranging the power section I started to rearange the power section of the board, making the layout of componenets better and in general improving the overall board layout. I added a big diode for reverse polarity protection. I also added neo pixels and are spliting the board more. I resized the UPDI header to bbe a 1x3 header with power on the outside - Ill put a full bridge recitifier on the programer so you can plug it in both ways."}, {"post_id": 65815, "ts": "2026-09-11T06:35:02Z", "hours": 4.0006, "text": "Some Polishing MicroDev128-32P I noticed that my Rev 1B, is nearly completely different than my original design - so it merits a different board name. I am going to polish the MicroDev128-32P, make a programer for it then move on. I am adding USB to new board as well as some more fetures. The MicroDev128-32P will be polished so that it functions perfectly. Also started more work on the docs!"}, {"post_id": 62073, "ts": "2026-09-05T09:47:43Z", "hours": 1.4667, "text": "Started work on MicroDev128-32P Rev 1B I need to fix some flaws with the original design. I’ll address them as a list: It doesn’t have onboard USB It has small hard to read silkscreen and clearance issues. It has an oversized programming header which can be ommited if I add onboard USB. The 3PDT switch is big, easy to knock and takes up valuable board space. The 603 Ceramic caps are large and are not in the best places for power filtering. I plan to fix these all. Stay tuned to see what changes!"}, {"post_id": 60666, "ts": "2026-09-03T05:18:50Z", "hours": 1.6572, "text": "Ordered Parts, Assembled, and Tested MicroDev128 Project Quick recap: I like the Arduino Nano but wow is it old. And outdated. And slow. And underpowered. So I put all my frustrations into making a board the same size (’cause trying to use a ESP32 on breadboard sucks when they are so thick) and waayyyyyyy more powerful. So then this thing was born. With a power regulator that can supply two times more current that my oscilloscope draws , mixed with the latest and greatest 8-bit AVR microcontrollers (not that 8-bit AVR microcontrollers are very new ). Sorry I haven’t devloged in a while so this is a lot of stuff in this devlog. This will say 1h 4min logged [because im really bad at remebering to devlog and I use my phone often that I can put Lookout on so I someone gets in the recordering I have to trash it :( ] Day 1 I started by ordering parts from Digikey. I spend roughly 3 hours looking at part selections for the passives and LEDs. Day 2 After the parts arrived I looked through the parts and then assebled one board. The caps placement was tricky because they all look the same size, so I’ll add a diagram to the Github repo in the future to make this easier. Day 3 I tested the board and, well you can watch the video to see how it turned out. So thats this updates devlog. See the Github repository for more info: github.com/ILikeBWRs/MicroDev128 WATCH THE VIDEO"}, {"post_id": 34416, "ts": "2026-07-25T03:23:11Z", "hours": 5.0506, "text": "Cleaning Up the PCB and getting it ready for production Woooooo!!!!!!!!!!!!!!!!!! Its done Check the other MicroDev128-32P devlogs for more info. I changed the short circuit/reverse polarity protection to using a TVS and fuse. I fixed some errors, worked on docs, and finished doing the silkscreen labels. Now I have to request funding and test (aka abuse it until it blows up >:] ) Sorry for gaps in the time-lapse, I got distracted reading my voltage regulator datasheet and forgot to pause the recording. Maaa Bad."}, {"post_id": 31094, "ts": "2026-07-19T06:55:58Z", "hours": 2.2339, "text": "PCB Routing Pt3 Finally Finished Routing the project!!!!!! Took a while but I ended up using layer 3 as a mixed power and signal plane insteed of a solid power plane. I am happy with how it turned out. I still might add TX and RX lines to the UPDI header, so you can do serial print . Overall very happy. Now I have to finish the silkscreen labels, do the documentation :/ , and test it (yay)."}, {"post_id": 29423, "ts": "2026-07-16T11:18:22Z", "hours": 0.8167, "text": "PCB Routing MicroDev128-32 Started routing everything for the whole board. I am sick of routing a good seeming line and then ripping it up 20 times. Started on the power lines Made planes for the GND and 5v lines Learnt that I really suck at PCB design in general ________________________________________________________________Project Overview Based on the AVR128DB32, with the LT8653S switching power regulator. It has: Up to 2 amps on both the 3.3v and 5v lines. 128kB Flash and 16kB SRAM MVIO on 4-pins with 3.3v, 5v and EXTERNAL source presets UPDI Programing Arduino Nano sized footprint Aims to have a better price to performance ratio than Arduino (not hard considering a Genuine Uno is $40 NZD (About 20 USD) More to come as I hopfully soon finish this project!"}, {"post_id": 12849, "ts": "2026-06-21T01:25:48Z", "hours": 1.7864, "text": "PCB PT2 This time: I have changed the voltage regulator to be the LT8653S (smaller footprint) I have relaid the board (again) I have started routing some basic data lines and the crystal. I have updated all footprints More to go! Getting there"}, {"post_id": 8519, "ts": "2026-06-14T05:13:06Z", "hours": 1.8056, "text": "Schematic Finishing and PCB (PT1)"}, {"post_id": 8482, "ts": "2026-06-14T03:17:10Z", "hours": 1.1797, "text": "Schematic PT2"}, {"post_id": 8446, "ts": "2026-06-14T01:23:50Z", "hours": 1.0075, "text": "Schematic AND ideas"}, {"post_id": 8402, "ts": "2026-06-13T23:33:35Z", "hours": 0.77, "text": "Schematic Work and Pondering"}, {"post_id": 7143, "ts": "2026-06-11T22:40:31Z", "hours": 0.3167, "text": "Hardware figuring out"}, {"post_id": 2956, "ts": "2026-06-05T21:17:39Z", "hours": 0.4111, "text": "Block Diagram"}, {"post_id": 1973, "ts": "2026-06-04T07:17:02Z", "hours": 0.2722, "text": "A basic program “BLINK” for the bare chip I have."}]...
|
Title: MicroDev128 Project by @I-like-BWRs | Stard Title: MicroDev128 Project by @I-like-BWRs | Stardance
Devlogs:
A basic program “BLINK” for the bare chip I have.
Block Diagram
Hardware figuring out
Schematic Work and Pondering
Schematic AND ideas
Schematic PT2
Schematic Finishing and PCB (PT1)
PCB PT2 This time: I have changed the voltage regulator to be the LT8653S (smaller footprint) I have relaid the board (again) I have started routing some basic data lines and the crystal. I have updated all footprints More to go! Getting there
PCB Routing MicroDev128-32 Started routing everything for the whole board. I am sick of routing a good seeming line and then ripping it up 20 times. Started on the power lines Made planes for the GND and 5v lines Learnt that I really suck at PCB design in general ________________________________________________________________Project Overview Based on the AVR128DB32, with the LT8653S switching power regulator. It has: Up to 2 amps on both the 3.3v and 5v lines. 128kB Flash and 16kB SRAM MVIO on 4-pins with 3.3v, 5v and EXTERNAL source presets UPDI Programing Arduino Nano sized footprint Aims to have a better price to performance ratio than Arduino (not hard considering a Genuine Uno is $40 NZD (About 20 USD) More to come as I hopfully soon finish this project!
PCB Routing Pt3 Finally Finished Routing the project!!!!!! Took a while but I ended up using layer 3 as a mixed power and signal plane insteed of a solid power plane. I am happy with how it turned out. I still might add TX and RX lines to the UPDI header, so you can do serial print . Overall very happy. Now I have to finish the silkscreen labels, do the documentation :/ , and test it (yay).
Cleaning Up the PCB and getting it ready for production Woooooo!!!!!!!!!!!!!!!!!! Its done Check the other MicroDev128-32P devlogs for more info. I changed the short circuit/reverse polarity protection to using a TVS and fuse. I fixed some errors, worked on docs, and finished doing the silkscreen labels. Now I have to request funding and test (aka abuse it until it blows up >:] ) Sorry for gaps in the time-lapse, I got distracted reading my voltage regulator datasheet and forgot to pause the recording. Maaa Bad.
Ordered Parts, Assembled, and Tested MicroDev128 Project Quick recap: I like the Arduino Nano but wow is it old. And outdated. And slow. And underpowered. So I put all my frustrations into making a board the same size (’cause trying to use a ESP32 on breadboard sucks when they are so thick) and waayyyyyyy more powerful. So then this thing was born. With a power regulator that can supply two times more current that my oscilloscope draws , mixed with the latest and greatest 8-bit AVR microcontrollers (not that 8-bit AVR microcontrollers are very new ). Sorry I haven’t devloged in a while so this is a lot of stuff in this devlog. This will say 1h 4min logged [because im really bad at remebering to devlog and I use my phone often that I can put Lookout on so I someone gets in the recordering I have to trash it :( ] Day 1 I started by ordering parts from Digikey. I spend roughly 3 hours looking at part selections for the passives and LEDs. Day 2 After the parts arrived I looked through the parts and then assebled one board. The caps placement was tricky because they all look the same size, so I’ll add a diagram to the Github repo in the future to make this easier. Day 3 I tested the board and, well you can watch the video to see how it turned out. So thats this updates devlog. See the Github repository for more info: github.com/ILikeBWRs/MicroDev128 WATCH THE VIDEO
Started work on MicroDev128-32P Rev 1B I need to fix some flaws with the original design. I’ll address them as a list: It doesn’t have onboard USB It has small hard to read silkscreen and clearance issues. It has an oversized programming header which can be ommited if I add onboard USB. The 3PDT switch is big, easy to knock and takes up valuable board space. The 603 Ceramic caps are large and are not in the best places for power filtering. I plan to fix these all. Stay tuned to see what changes!
Some Polishing MicroDev128-32P I noticed that my Rev 1B, is nearly completely different than my original design - so it merits a different board name. I am going to polish the MicroDev128-32P, make a programer for it then move on. I am adding USB to new board as well as some more fetures. The MicroDev128-32P will be polished so that it functions perfectly. Also started more work on the docs!
Rearranging the power section I started to rearange the power section of the board, making the layout of componenets better and in general improving the overall board layout. I added a big diode for reverse polarity protection. I also added neo pixels and are spliting the board more. I resized the UPDI header to bbe a 1x3 header with power on the outside - Ill put a full bridge recitifier on the programer so you can plug it in both ways.
FINISHED Rev 1B I finished this revision by adding a few things: A full changelog bellow Rounded corners (idk just looks better in my opionion) Changed the TVS blows a fuse thing for a diode for proper reverse polarity protection Rearranged all the components Fixed some decoupling caps that were linked to GND and 5V but not even close to the acuall pin. Changed the UPDI header to be a 3x1 to save board space. As per request of a guy in my schools robotics club the board now fetures 3 neopixels (couldnt do his other request of a diode on every pin) Re-jigged the silkscreen labels so they should be acually readable Fixed the LT8653S being wired for burst mode ( which is great for battery life, but has higher ripple (I measured 30mV peak to peak with my scope) Now it is wired for FCM (Forced Countiuous Mode) for that super low ripple that the LT8653S is capable of. I learnt a thing or two about routing and made the pins for everything as close as possible to each other. Most likely I forgot to mention some stuff that I changed …. Anyway … turning out to be a genuinely useful board. Had the MVIO comunicating with a 3.3V SD card module yesterday no problems. Until next time … ILikeBWRs - Keegan Muller
Finished the Rev1B and started work on the UPDI programmer I finished work on the MicroDev128-32P Rev1B. It some new things that you can see in the past devlogs. For MicroDevUPDI I made a simple USB to UPDI programmer. It uses the CH340E - which has an internal crystal. small footprint and needs few external parts. I added reverse polarity protection. It uses USB-C for its connector and is 2 small two layer board. I changed the main MicroDev128 repo to be a main landing page - with each board having its own repo.
Finished my BOM and sent and email THANK YOU PCBWay for sponsoring this project! I needed to lock in. I (mostly off-camera) worked on selecting parts for the BOM. This included the parts for the MicroDevUPDI Programmer, and the MicroDev128-32P. I wrote a email to PCBWay (off-camera) asking if they will continue to sponsor me. (fingers crossed as the Hack Club grant just covered the first lot of parts). Because Stardance ends in 2 weeks - and shipping and assembly takes more than 2 weeks this will be the last devlog on stardance :( Thank you to all who have helped with this project - including you * reading this now. I really appreciate your support!
Ships:
AVR128DB28 Concept Board. Being made right now...
|
1793289381.856529
|
1793375781.856529
|
|
6132
|
My first slack bot! by @neevmodi_5 | Stardance
|
neevmodi_5
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @neevmodi_5 | Starda Title: My first slack bot! by @neevmodi_5 | Stardance...
|
1793324864.8495631
|
1793929664.8495631
|
|
6133
|
HydroPad by @hatya-mouse | Stardance
|
hatya-mouse
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-16T12:50:13Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "HydroPad HydroPad is a macropad with some holes for the water to go through, designed for people with palmar hyperhidrosis. Why I created this I have palmar hyperhidrosis and that makes it hard to clean up keyboards, because sweat goes into the keyboard’s frame. So I designed a hackpad that has a hole that allows me to get the water out of it.", "repo": "https://github.com/hatya-mouse/hydropad", "demo": ""}]...
|
[{"post_id": 2205, "ts": "2026 [{"post_id": 2205, "ts": "2026-06-04T16:05:31Z", "hours": 0.4156, "text": "FInally finished preparing the required resources! https://github.com/hatya-mouse/hydropad"}, {"post_id": 2129, "ts": "2026-06-04T13:41:29Z", "hours": 0.2819, "text": "Implemented simple encoder and oled process to firmware"}, {"post_id": 2116, "ts": "2026-06-04T13:21:01Z", "hours": 0.3925, "text": "Finished designing the PCB and the case and finally started implementing the firmware!"}]...
|
Title: HydroPad by @hatya-mouse | Stardance
Devlo Title: HydroPad by @hatya-mouse | Stardance
Devlogs:
Finished designing the PCB and the case and finally started implementing the firmware!
Implemented simple encoder and oled process to firmware
FInally finished preparing the required resources! https://github.com/hatya-mouse/hydropad
Ships:
HydroPad HydroPad is a macropad with some holes for the water to go through, designed for people with palmar hyperhidrosis. Why I created this I have palmar hyperhidrosis and that makes it hard to clean up keyboards, because sweat goes into the keyboard’s frame. So I designed a hackpad that has a hole that allows me to get the water out of it....
|
1793299959.597722
|
1793386359.597722
|
|
6134
|
My awesome macropad! by @nodogklaa | Stardance
|
nodogklaa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @nodogklaa | Starda Title: My awesome macropad! by @nodogklaa | Stardance...
|
1793285372.176386
|
1793890172.176386
|
|
6135
|
My first slack bot! by @Snow | Stardance
|
Snow
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Snow | Stardance
|
1793307437.0995493
|
1793912237.0995493
|
|
6136
|
My first slack bot! by @nodogklaa | Stardance
|
nodogklaa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @nodogklaa | Stardan Title: My first slack bot! by @nodogklaa | Stardance...
|
1793321230.755165
|
1793926030.755165
|
|
6137
|
Untitled project by @Saathvik | Stardance
|
Saathvik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Saathvik | Stardance
|
1793231682.0778837
|
1793836482.0778837
|
|
6138
|
My first slack bot! by @Dammy | Stardance
|
Dammy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Dammy | Stardance
|
1792716763.6584158
|
1793321563.6584158
|
|
6139
|
ATN by @Dharshan | Stardance
|
Dharshan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ATN by @Dharshan | Stardance
|
1792680831.8582163
|
1793285631.8582163
|
|
6140
|
My first slack bot! by @Elie | Stardance
|
Elie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Elie | Stardance
|
1792677253.3897467
|
1793282053.3897467
|
|
6141
|
Environment simulation by @Neph | Stardance
|
Neph
|
0
|
0.87
|
0
|
[]
|
[{"post_id": 10634, "ts": "202 [{"post_id": 10634, "ts": "2026-06-17T14:20:16Z", "hours": 0.8667, "text": "I created a small simulation in Unity where a creature (red block) tries to find food (yellow sphere). I want to add some more environmental factors next, and maybe predators or a way for the creature and the food to reproduce."}]...
|
Title: Environment simulation by @Neph | Stardance Title: Environment simulation by @Neph | Stardance
Devlogs:
I created a small simulation in Unity where a creature (red block) tries to find food (yellow sphere). I want to add some more environmental factors next, and maybe predators or a way for the creature and the food to reproduce....
|
1793029772.0683122
|
1793634572.0683122
|
|
6142
|
My first slack bot! by @apishRana | Stardance
|
apishRana
|
0
|
0.39
|
0
|
[]
|
[{"post_id": 1339, "ts": "2026 [{"post_id": 1339, "ts": "2026-06-03T08:56:26Z", "hours": 0.3931, "text": "worked on my frist slack bot for now its just calculater, will update latter"}]...
|
Title: My first slack bot! by @apishRana | Stardan Title: My first slack bot! by @apishRana | Stardance
Devlogs:
worked on my frist slack bot for now its just calculater, will update latter...
|
1792644911.919014
|
1793249711.919014
|
|
6143
|
CTFDocsWeb by @ethan_soh | Stardance
|
ethan_soh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CTFDocsWeb by @ethan_soh | Stardance
|
1792777896.16809
|
1793382696.16809
|
|
6144
|
Prototype 95 by @Parv95Aerointellect | Stardance
|
Parv95Aerointellect
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Prototype 95 by @Parv95Aerointellect | Star Title: Prototype 95 by @Parv95Aerointellect | Stardance...
|
1792694883.3367925
|
1793299683.3367925
|
|
6145
|
UniverseBox by @SysError06 | Stardance
|
SysError06
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: UniverseBox by @SysError06 | Stardance
|
1792806686.995976
|
1793411486.995976
|
|
6146
|
Diana by @RedBlue | Stardance
|
RedBlue
|
1
|
43.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-21T07:23:42Z", "hours": 43.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Built Diana — a memory-aware AI assistant that actually remembers you across conversations. Diana extracts structured facts from every chat (your projects, skills, goals, preferences) and injects them into every future response. No more explaining yourself from scratch every session. Stack: React + TypeScript frontend, Express backend, FastAPI AI service, PostgreSQL on Neon, deployed on Google Cloud Run + Vercel. To test: go to https://diana-six-theta.vercel.app , create an account, tell Diana something about yourself or what you’re building, then start a new chat and ask “what do you know about me?” — she’ll already know. What was challenging: deploying three separate services to production for the first time, both Groq models getting decommissioned mid-deployment, and debugging a CORS issue caused by an Express 5 breaking change. What I’m proud of: the memory pipeline works end to end — extract, store, retrieve, inject — and it genuinely makes the AI feel different.", "repo": "https://github.com/HJeandedieu/Diana", "demo": "https://diana-six-theta.vercel.app/"}]...
|
[{"post_id": 51489, "ts": "202 [{"post_id": 51489, "ts": "2026-08-21T07:18:57Z", "hours": 6.4872, "text": "Diana — Final Update: Shipped. The last piece was getting Diana off localhost and into the world. The backend and AI service landed on Google Cloud Run, the database on Neon, the frontend on Vercel — three services, one product, all talking to each other in production. It wasn’t without a fight. Both Groq models we’d been using were decommissioned the same week we deployed. Docker refused to generate the Prisma client without a database URL at build time. Cloud Run silently dropped env vars. The auth token expired mid-deploy. Each one got fixed, and by the end Diana was running live — memory extraction, context injection, session persistence, the full pipeline — on real infrastructure. Diana is live at https://diana-six-theta.vercel.app Progress: Backend → AI Service → Memory System → Context Injection → Authentication → Component Library → Application Screens → UI Integration → Live Data → Shipped."}, {"post_id": 46629, "ts": "2026-08-14T00:57:19Z", "hours": 4.08, "text": "The frontend foundation met the backend this week and everything clicked into place. Real data replaced the mocks — sessions create automatically on load, conversations persist across visits, and the chat pipeline is fully live end to end. The Memories screen went from a shell to a working dashboard, with filters, inline editing, and deletion all connected to the database. On the first real test, Diana loaded two memories — “User built Diana” and “User knows Express” — exactly what she was supposed to remember. It wasn’t without a fight. CORS blocked the first login attempt because Express 5 was intercepting preflight requests before the middleware could run — downgraded to Express 4 and it resolved immediately. Sessions weren’t being created on the frontend so every chat request returned a 404. Messages rendered as empty bubbles until the controller response shape was corrected to return a full message object. Each one got fixed, and by the end of the week Diana was having real, memory-aware conversations through a UI that feels like something worth using. Progress: Backend → AI Service → Memory System → Context Injection → Authentication → Component Library → Application Screens → UI Integration → Live Data"}, {"post_id": 44691, "ts": "2026-08-10T16:59:45Z", "hours": 6.5836, "text": "Diana — Screens Implementation: Frontend Structure Complete All major screens are now created and connected with the component library. The UI layer is complete — Login, Register, Chat Interface, Memory Dashboard, Profile, Settings, and supporting layouts are built using the reusable TypeScript components. The Sidebar, Chat Experience, Authentication Flow, and Dashboard structure are now in place, giving Diana a complete application shell instead of isolated components. Frontend progress: Backend → AI Service → Memory System → Context Injection → Authentication → Component Library → Application Screens → UI Integration The frontend foundation is complete. Next steps are connecting real data, API integration, state management, and refining the user experience."}, {"post_id": 42021, "ts": "2026-08-06T15:49:12Z", "hours": 2.1331, "text": "Diana — UI Update: Components Complete All 12 components are done — UI and layout. Button, Input, PasswordInput, Label, Spinner, Toast, Badge, MarkdownRenderer, CodeBlock, Sidebar, ChatInput, and ChatMessage. The full component library is built, typed in TypeScript, and ready to compose into screens. Login is already live. Chat, Register, and Memory Dashboard are next. The frontend is taking shape. Progress: Backend → AI Service → Memory System → Context Injection → Login Page → Component Library → Screens"}, {"post_id": 41623, "ts": "2026-08-05T22:50:01Z", "hours": 5.0111, "text": "Diana — UI Update: Component Library All core UI components are built and ready — Button, Input, PasswordInput, Label, Spinner, Toast, Badge, MarkdownRenderer, and CodeBlock. The component library is the foundation every screen builds on. Nothing gets repeated, nothing gets inconsistent. Next up: layout components and the first full screens. Progress: Backend → AI Service → Memory System → Context Injection → Login Page → Component Library → Layout & Screens"}, {"post_id": 21840, "ts": "2026-07-03T23:42:22Z", "hours": 5.3878, "text": "First Week working on Diana Frontend. So far I’ve managed to create the login page other pages are coming soon. #frontend"}, {"post_id": 15617, "ts": "2026-06-25T12:21:44Z", "hours": 0.3967, "text": "Diana — Week 6 Update This week Diana became self-aware. Context injection is now fully operational. Before every response, Diana fetches the user’s most important memories from the database and injects them into her system prompt. She now knows who she is, what the user is building, and what they care about — before a single word is typed. The proof: ask her “What am I currently building?” with no context in the message. She responds: “You’re currently building me, Diana, a memory-aware AI assistant designed specifically for software developers.” The core pipeline is complete. Progress: Backend ✅ → Sessions & Messages ✅ → FastAPI Service ✅ → LLM Integration ✅ → Memory Extraction ✅ → Context Injection ✅ → React Frontend (next)"}, {"post_id": 15212, "ts": "2026-06-24T18:36:26Z", "hours": 1.8997, "text": "Diana — Week 5 Update This week Diana got her memory. Built out the full memory extraction pipeline — after every conversation, Diana automatically analyzes what was said and extracts structured long-term facts about the user, storing them as typed memory objects with importance scores in the database. Four memory types are now being captured in production: projects, skills, goals, and facts — exactly as designed. Progress: Backend ✅ → Sessions & Messages ✅ → FastAPI Service ✅ → LLM Integration ✅ → Memory Extraction ✅ → Context Injection (next)"}, {"post_id": 14650, "ts": "2026-06-23T20:41:48Z", "hours": 0.9828, "text": "Diana — Week 4 Update This week Diana got her voice. Replaced the hardcoded FastAPI stub with a real Groq LLM call using LLaMA 3.3-70b. Added a system prompt defining Diana’s identity and wired in conversation history so the model has context within a session. The full pipe is now live — a message sent from Express travels to FastAPI, hits Groq, and returns a real AI response. Progress: Backend ✅ → Sessions & Messages ✅ → FastAPI Service ✅ → OpenAI Integration ✅ → Memory Extraction (next)"}, {"post_id": 13851, "ts": "2026-06-22T18:11:39Z", "hours": 3.0103, "text": "Week 3 Progress – Diana Set up the initial FastAPI backend for the Diana project. Organized the project into a clean and scalable folder structure.Defined the core application entry point and server configuration. Established a foundation for future API route expansion. Created the /generate-response endpoint as a functional stub. Added request and response placeholders for response generation. Created the /extract-memory endpoint as a functional stub. Added placeholder logic for future memory extraction workflows. Verified route registration and successful application startup. Prepared the backend architecture for Week 4 feature implementation."}, {"post_id": 12137, "ts": "2026-06-19T20:40:56Z", "hours": 3.5233, "text": "Diana: Week 2 Update This week focused on the session and messaging layer of Diana’s backend. Built out full session management — creating chat sessions, listing them, and retrieving conversation history — along with the core chat endpoint that stores both user and assistant messages. Every endpoint is now scoped to the authenticated user, ensuring one user’s data can never be accessed by another. With this in place, the foundation is ready for Week 3: standing up the FastAPI AI service and connecting it to the backend. Progress: Backend Foundation ✅ → Session & Message System ✅ → AI Service Setup (next)"}, {"post_id": 6963, "ts": "2026-06-11T17:55:40Z", "hours": 2.3017, "text": "Project Diana — Weekly Dev Log This week focused on building the backend foundation: POST /api/auth/register implemented POST /api/auth/login returns JWT tokens JWT middleware added to protect private routes Prisma schema migrated successfully to the database All API routes created and returning 200 OK stubs Next: Replace stubs with real business logic and begin integrating Diana’s AI-agent workflows."}, {"post_id": 3864, "ts": "2026-06-06T22:50:32Z", "hours": 1.0072, "text": "Initiated Project Diana which is a memory-aware AI assistant for developers that stores important information from previous conversations and uses it to provide contextual responses across sessions. I currently have been setting up my code-space like configuring Prisma so far."}]...
|
Title: Diana by @RedBlue | Stardance
Devlogs:
Ini Title: Diana by @RedBlue | Stardance
Devlogs:
Initiated Project Diana which is a memory-aware AI assistant for developers that stores important information from previous conversations and uses it to provide contextual responses across sessions. I currently have been setting up my code-space like configuring Prisma so far.
Project Diana — Weekly Dev Log This week focused on building the backend foundation: POST /api/auth/register implemented POST /api/auth/login returns JWT tokens JWT middleware added to protect private routes Prisma schema migrated successfully to the database All API routes created and returning 200 OK stubs Next: Replace stubs with real business logic and begin integrating Diana’s AI-agent workflows.
Diana: Week 2 Update This week focused on the session and messaging layer of Diana’s backend. Built out full session management — creating chat sessions, listing them, and retrieving conversation history — along with the core chat endpoint that stores both user and assistant messages. Every endpoint is now scoped to the authenticated user, ensuring one user’s data can never be accessed by another. With this in place, the foundation is ready for Week 3: standing up the FastAPI AI service and connecting it to the backend. Progress: Backend Foundation ✅ → Session & Message System ✅ → AI Service Setup (next)
Week 3 Progress – Diana Set up the initial FastAPI backend for the Diana project. Organized the project into a clean and scalable folder structure.Defined the core application entry point and server configuration. Established a foundation for future API route expansion. Created the /generate-response endpoint as a functional stub. Added request and response placeholders for response generation. Created the /extract-memory endpoint as a functional stub. Added placeholder logic for future memory extraction workflows. Verified route registration and successful application startup. Prepared the backend architecture for Week 4 feature implementation.
Diana — Week 4 Update This week Diana got her voice. Replaced the hardcoded FastAPI stub with a real Groq LLM call using LLaMA 3.3-70b. Added a system prompt defining Diana’s identity and wired in conversation history so the model has context within a session. The full pipe is now live — a message sent from Express travels to FastAPI, hits Groq, and returns a real AI response. Progress: Backend ✅ → Sessions & Messages ✅ → FastAPI Service ✅ → OpenAI Integration ✅ → Memory Extraction (next)
Diana — Week 5 Update This week Diana got her memory. Built out the full memory extraction pipeline — after every conversation, Diana automatically analyzes what was said and extracts structured long-term facts about the user, storing them as typed memory objects with importance scores in the database. Four memory types are now being captured in production: projects, skills, goals, and facts — exactly as designed. Progress: Backend ✅ → Sessions & Messages ✅ → FastAPI Service ✅ → LLM Integration ✅ → Memory Extraction ✅ → Context Injection (next)
Diana — Week 6 Update This week Diana became self-aware. Context injection is now fully operational. Before every response, Diana fetches the user’s most important memories from the database and injects them into her system prompt. She now knows who she is, what the user is building, and what they care about — before a single word is typed. The proof: ask her “What am I currently building?” with no context in the message. She responds: “You’re currently building me, Diana, a memory-aware AI assistant designed specifically for software developers.” The core pipeline is complete. Progress: Backend ✅ → Sessions & Messages ✅ → FastAPI Service ✅ → LLM Integration ✅ → Memory Extraction ✅ → Context Injection ✅ → React Frontend (next)
First Week working on Diana Frontend. So far I’ve managed to create the login page other pages are coming soon. #frontend
Diana — UI Update: Component Library All core UI components are built and ready — Button, Input, PasswordInput, Label, Spinner, Toast, Badge, MarkdownRenderer, and CodeBlock. The component library is the foundation every screen builds on. Nothing gets repeated, nothing gets inconsistent. Next up: layout components and the first full screens. Progress: Backend → AI Service → Memory System → Context Injection → Login Page → Component Library → Layout & Screens
Diana — UI Update: Components Complete All 12 components are done — UI and layout. Button, Input, PasswordInput, Label, Spinner, Toast, Badge, MarkdownRenderer, CodeBlock, Sidebar, ChatInput, and ChatMessage. The full component library is built, typed in TypeScript, and ready to compose into screens. Login is already live. Chat, Register, and Memory Dashboard are next. The frontend is taking shape. Progress: Backend → AI Service → Memory System → Context Injection → Login Page → Component Library → Screens
Diana — Screens Implementation: Frontend Structure Complete All major screens are now created and connected with the component library. The UI layer is complete — Login, Register, Chat Interface, Memory Dashboard, Profile, Settings, and supporting layouts are built using the reusable TypeScript components. The Sidebar, Chat Experience, Authentication Flow, and Dashboard structure are now in place, giving Diana a complete application shell instead of isolated components. Frontend progress: Backend → AI Service → Memory System → Context Injection → Authentication → Component Library → Application Screens → UI Integration The frontend foundation is complete. Next steps are connecting real data, API integration, state management, and refining the user experience.
The frontend foundation met the backend this week and everything clicked into place. Real data replaced the mocks — sessions create automatically on load, conversations persist across visits, and the chat pipeline is fully live end to end. The Memories screen went from a shell to a working dashboard, with filters, inline editing, and deletion all connected to the database. On the first real test, Diana loaded two memories — “User built Diana” and “User knows Express” — exactly what she was supposed to remember. It wasn’t without a fight. CORS blocked the first login attempt because Express 5 was intercepting preflight requests before the middleware could run — downgraded to Express 4 and it resolved immediately. Sessions weren’t being created on the frontend so every chat request returned a 404. Messages rendered as empty bubbles until the controller response shape was corrected to return a full message object. Each one got fixed, and by the end of the week Diana was having real, memory-aware conversations through a UI that feels like something worth using. Progress: Backend → AI Service → Memory System → Context Injection → Authentication → Component Library → Application Screens → UI Integration → Live Data
Diana — Final Update: Shipped. The last piece was getting Diana off localhost and into the world. The backend and AI service landed on Google Cloud Run, the database on Neon, the frontend on Vercel — three services, one product, all talking to each other in production. It wasn’t without a fight. Both Groq models we’d been using were decommissioned the same week we deployed. Docker refused to generate the Prisma client without a database URL at build time. Cloud Run silently dropped env vars. The auth token expired mid-deploy. Each one got fixed, and by the end Diana was running live — memory extraction, context injection, session persistence, the full pipeline — on real infrastructure. Diana is live at https://diana-six-theta.vercel.app Progress: Backend → AI Service → Memory System → Context Injection → Authentication → Component Library → Application Screens → UI Integration → Live Data → Shipped.
Ships:
Built Diana — a memory-aware AI assistant that actually remembers you across conversations. Diana extracts structured facts from every chat (your projects, skills, goals, preferences) and injects them into every future response. No more explaining yourself from scratch every session. Stack: React + TypeScript frontend, Express backend, FastAPI AI service, PostgreSQL on Neon, deployed on Google Cloud Run + Vercel. To test: go to https://diana-six-theta.vercel.app , create an account, tell Diana something about yourself or what you’re building, then start a new chat and ask “what do you know about me?” — she’ll already know. What was challenging: deploying three separate services to production for the first time, both Groq models getting decommissioned mid-deployment, and debugging a CORS issue caused by an Express 5 breaking change. What I’m proud of: the memory pipeline works end to end — extract, store, retrieve, inject — and it genuinely makes the AI feel different....
|
1793300132.579741
|
1793386532.579741
|
|
6147
|
Rescue Drone by @PeterD | Stardance
|
PeterD
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Rescue Drone by @PeterD | Stardance
|
1793299997.2562702
|
1793904797.2562702
|
|
6148
|
nothelp by @Ruben | Stardance
|
Ruben
|
1
|
1.0
|
1
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-10T09:40:50Z", "hours": 1.0, "multiplier": 1.64, "payout": 1, "blessing": "neutral", "text": "I made a cool bot for people who aren’t on the help team to add a disclaimer to a message.", "repo": "https://github.com/code2344/helpbot", "demo": "https://app.slack.com/client/E09V59WQY1E/C0B5WQKC0F8"}]...
|
[{"post_id": 6129, "ts": "2026 [{"post_id": 6129, "ts": "2026-06-10T09:38:09Z", "hours": 0.3356, "text": "fixed bot so it sends for the right button but then realised i broke rules in like 4 channels (dw theyre getting removed) also got a icon :)"}, {"post_id": 6106, "ts": "2026-06-10T08:35:10Z", "hours": 0.4453, "text": "Added more features and working on making it change the button name in different channels!"}]...
|
Title: nothelp by @Ruben | Stardance
Devlogs:
Add Title: nothelp by @Ruben | Stardance
Devlogs:
Added more features and working on making it change the button name in different channels!
fixed bot so it sends for the right button but then realised i broke rules in like 4 channels (dw theyre getting removed) also got a icon :)
Ships:
I made a cool bot for people who aren’t on the help team to add a disclaimer to a message....
|
1793220647.0047197
|
1793307047.0047197
|
|
6149
|
Snake Game by @StarDhruv | Stardance
|
StarDhruv
|
0
|
0.35
|
0
|
[]
|
[{"post_id": 3324, "ts": "2026 [{"post_id": 3324, "ts": "2026-06-06T06:01:03Z", "hours": 0.3547, "text": "Making the Snake Game with Higher Graphics"}]...
|
Title: Snake Game by @StarDhruv | Stardance
Devlo Title: Snake Game by @StarDhruv | Stardance
Devlogs:
Making the Snake Game with Higher Graphics...
|
1792702509.8732212
|
1793307309.8732212
|
|
6150
|
website by @Dream_ | Stardance
|
Dream_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: website by @Dream_ | Stardance
|
1793181120.6564188
|
1793785920.6564188
|