|
47777
|
goofy ahh website by @starbound | Stardance
|
starbound
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: goofy ahh website by @starbound | Stardance
|
1793195452.4316356
|
1793800252.4316356
|
|
42932
|
Spider Os by @gamebites802 | Stardance
|
gamebites802
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Spider Os by @gamebites802 | Stardance
|
1793195451.5131762
|
1793800251.5131762
|
|
47776
|
Mariobot by @kanishkpanchamia | Stardance
|
kanishkpanchamia
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mariobot by @kanishkpanchamia | Stardance
|
1793195450.598547
|
1793800250.598547
|
|
47775
|
Mars Greenhouse Project by @Manvireddy | Stardance
|
Manvireddy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mars Greenhouse Project by @Manvireddy | St Title: Mars Greenhouse Project by @Manvireddy | Stardance...
|
1793195449.6920094
|
1793800249.6920094
|
|
47774
|
a cool project by @vishalyep | Stardance
|
vishalyep
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: a cool project by @vishalyep | Stardance
|
1793195448.808577
|
1793800248.808577
|
|
47773
|
my APOD site by @teqcoder001 | Stardance
|
teqcoder001
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: my APOD site by @teqcoder001 | Stardance
|
1793195447.8757026
|
1793800247.8757026
|
|
47772
|
RFID based attendence system by @MadameLouise | St RFID based attendence system by @MadameLouise | Stardance...
|
MadameLouise
|
0
|
0.55
|
0
|
[]
|
[{"post_id": 46884, "ts": "202 [{"post_id": 46884, "ts": "2026-08-14T13:03:18Z", "hours": 0.5464, "text": "RFID Based entry monitoring sytem or house or school"}]...
|
Title: RFID based attendence system by @MadameLoui Title: RFID based attendence system by @MadameLouise | Stardance
Devlogs:
RFID Based entry monitoring sytem or house or school...
|
1793195446.9474182
|
1793800246.9474182
|
|
42929
|
Eggball by @vaughn | Stardance
|
vaughn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Eggball by @vaughn | Stardance
|
1793195445.9931412
|
1793800245.9931412
|
|
47770
|
My own site! by @starbound | Stardance
|
starbound
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @starbound | Stardance
|
1793195445.0628796
|
1793800245.0628796
|
|
42927
|
Libra by @JM | Stardance
|
JM
|
0
|
2.31
|
0
|
[]
|
[{"post_id": 39271, "ts": "202 [{"post_id": 39271, "ts": "2026-08-02T04:18:56Z", "hours": 2.3067, "text": "Are you struggling with APs? Does any AP website you stumble upon like Fiveable just punch you in the face with a $35 paywall just to access the site? Well if you don’t then I mean let me still tell you about this cool app/website called Libra. This will help everyone with their AP classes which I know is really hard so I am here to fix it. You can choose between 1-2 of the 35 tests and get free study tools. AND not just that. You can have your own libra to chat with which will help you plan, and study for EVERY AP not just the 1-2 for only $15 (yes I still need to get paid I need money too) Enough with the plug here’s what I have so far I have a basic dashboard with tasks, and a backend of account creation and memory database. Since I am a frontend engineer this is my first time using a backend and I learned a lot from it. I also added a sidebar which needs some work on icons and that empty box (a pomodoro timer). So let me know if you have any ideas I really need some feedback. (And most of my recorded hours on this project were wasted on a different IDE which is very sads)"}]...
|
Title: Libra by @JM | Stardance
Devlogs:
Are you Title: Libra by @JM | Stardance
Devlogs:
Are you struggling with APs? Does any AP website you stumble upon like Fiveable just punch you in the face with a $35 paywall just to access the site? Well if you don’t then I mean let me still tell you about this cool app/website called Libra. This will help everyone with their AP classes which I know is really hard so I am here to fix it. You can choose between 1-2 of the 35 tests and get free study tools. AND not just that. You can have your own libra to chat with which will help you plan, and study for EVERY AP not just the 1-2 for only $15 (yes I still need to get paid I need money too) Enough with the plug here’s what I have so far I have a basic dashboard with tasks, and a backend of account creation and memory database. Since I am a frontend engineer this is my first time using a backend and I learned a lot from it. I also added a sidebar which needs some work on icons and that empty box (a pomodoro timer). So let me know if you have any ideas I really need some feedback. (And most of my recorded hours on this project were wasted on a different IDE which is very sads)...
|
1793195444.1498685
|
1793800244.1498685
|
|
47769
|
StardanceOS by @Aizen_Sosuke | Stardance
|
Aizen_Sosuke
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: StardanceOS by @Aizen_Sosuke | Stardance
|
1793195443.2314079
|
1793800243.2314079
|
|
42924
|
Traffic Control by @dancejjjjjjjjjjjjjjj | Stardan Traffic Control by @dancejjjjjjjjjjjjjjj | Stardance...
|
dancejjjjjjjjjjjjjjj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Traffic Control by @dancejjjjjjjjjjjjjjj | Title: Traffic Control by @dancejjjjjjjjjjjjjjj | Stardance...
|
1793195442.363038
|
1793800242.363038
|
|
47768
|
CS os by @vito0812 | Stardance
|
vito0812
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CS os by @vito0812 | Stardance
|
1793195441.451603
|
1793800241.451603
|
|
47766
|
My awesome macropad! by @Aizen_Sosuke | Stardance
|
Aizen_Sosuke
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Aizen_Sosuke | Sta Title: My awesome macropad! by @Aizen_Sosuke | Stardance...
|
1793195440.548648
|
1793800240.548648
|
|
47765
|
Micro Mouse by @Sneh_Kahodariya | Stardance
|
Sneh_Kahodariya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Micro Mouse by @Sneh_Kahodariya | Stardance
|
1793195439.5897117
|
1793800239.5897117
|
|
47763
|
My own site! by @rodyert44 | Stardance
|
rodyert44
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @rodyert44 | Stardance
|
1793195438.7063162
|
1793800238.7063162
|
|
42918
|
RAM- Random Access Macropad by @vedude42 | Stardan RAM- Random Access Macropad by @vedude42 | Stardance...
|
vedude42
|
0
|
3.99
|
0
|
[]
|
[{"post_id": 46160, "ts": "202 [{"post_id": 46160, "ts": "2026-08-13T05:46:08Z", "hours": 1.3853, "text": "I worked on firmware and made my github repo"}, {"post_id": 45585, "ts": "2026-08-12T05:27:47Z", "hours": 2.6006, "text": "I just followed the tutorial a little bit and started routing my pcb in the timelapse. I forgot to log a few hours after this, and I ended up finishing the macropad, I might end up pocketing it differently in the end though, now all that’s left is to finish the firmware"}]...
|
Title: RAM- Random Access Macropad by @vedude42 | Title: RAM- Random Access Macropad by @vedude42 | Stardance
Devlogs:
I just followed the tutorial a little bit and started routing my pcb in the timelapse. I forgot to log a few hours after this, and I ended up finishing the macropad, I might end up pocketing it differently in the end though, now all that’s left is to finish the firmware
I worked on firmware and made my github repo...
|
1793195437.731258
|
1793800237.731258
|
|
42917
|
My very own WebOS by @Itz_Capy | Stardance
|
Itz_Capy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Itz_Capy | Stardance
|
1793195436.8247447
|
1793800236.8247447
|
|
47761
|
0x6502 by @ThePangel | Stardance
|
ThePangel
|
0
|
29.88
|
0
|
[]
|
[{"post_id": 75025, "ts": "202 [{"post_id": 75025, "ts": "2026-09-28T21:57:03Z", "hours": 4.5253, "text": "Big progress. GOT THE APPLE I RUNNING Hooray wozmon is up and running, marking the most successful milestone yet, a running system, i had to fix some opcode behaviors but it runs great!! Still very early, 1st, not all input keys are mapped, cycle stepping, the ui etc etc, but for now its progress."}, {"post_id": 73677, "ts": "2026-09-25T17:32:55Z", "hours": 3.1269, "text": "So I had to tackle some special cases to adapt everything to the new cycle accurate architecture These are mainly the operations that work with the stack In my architecture addressing handles fetching, while the run_operation() just does the math (and final data write if needed), so it only consumes one cycle, these special cases handles various cycles in their operation (independently of addressing mode) so I had to add that, and some other minor fixes to branch operations and other stuff"}, {"post_id": 73258, "ts": "2026-09-24T18:04:40Z", "hours": 2.7364, "text": "Finished refactoring all the addressing code for it to be cycle accurate. Next I’ll check and fix operations and then the TUI situation and try to get the Apple I running, good progress"}, {"post_id": 72840, "ts": "2026-09-23T20:58:26Z", "hours": 4.7969, "text": "Ok so I’m back Sorta refactoring the code base to be a cycle accurate state machine to make the emulation as truthful as I can, this involves coding each cycle independently (sorta) to maintain accuracy, I have started this refactoring with a lot to go, but at the end it will be much better than before see the code here as an example"}, {"post_id": 48539, "ts": "2026-08-16T23:29:01Z", "hours": 1.5603, "text": "Made some more progress on Implementing the Apple I machine and some TUI handling code + misc fixes"}, {"post_id": 48404, "ts": "2026-08-16T18:54:19Z", "hours": 2.1569, "text": "I worked on adding all the Apple I roms to the program, loading them at each required memory location and started working on some more of the UI"}, {"post_id": 48142, "ts": "2026-08-16T13:09:54Z", "hours": 0.9506, "text": "Started working on the Apple I implementation. Setting memory ranges and more. Also added a console write and read to the bus so machines can display what the want, since each machine does whatever this is a way to normalize it"}, {"post_id": 48083, "ts": "2026-08-16T11:31:43Z", "hours": 0.3844, "text": "Finally finished all instructions. Now I will move to making the first machine (maybe apple I or II) and connecting all cpu mechanics and get the emu working."}, {"post_id": 47782, "ts": "2026-08-15T23:15:38Z", "hours": 2.1928, "text": "Added a bunch more operations, had to learn a bit of low level byte and bit operations. Also started working on operations that work with the stack which is always fun"}, {"post_id": 47656, "ts": "2026-08-15T18:11:48Z", "hours": 3.2358, "text": "Started working on the first cpu operations, also added cycle emulation. Some operations where a struggle, It took a while till I got BCD operations, also the break flag is special in it of itself, but good progress. Next up, more operations"}, {"post_id": 47081, "ts": "2026-08-14T18:31:02Z", "hours": 0.4989, "text": "Added helper functions for flag handling. Setting and reading the status register flags."}, {"post_id": 46859, "ts": "2026-08-14T12:14:13Z", "hours": 3.7103, "text": "I started working on 0x6502, a retro computer lab where you can emulate 6502 based retro computers, like the Apple II or C64 directly in terminal, while being able to live view the stack, memory and registers, all in a tui built woth ratatui. For now I have just worked on the 6502 cpu logic and blocked out the main UI, I have done Instruction and addressing handling, next its operations."}]...
|
Title: 0x6502 by @ThePangel | Stardance
Devlogs:
Title: 0x6502 by @ThePangel | Stardance
Devlogs:
I started working on 0x6502, a retro computer lab where you can emulate 6502 based retro computers, like the Apple II or C64 directly in terminal, while being able to live view the stack, memory and registers, all in a tui built woth ratatui. For now I have just worked on the 6502 cpu logic and blocked out the main UI, I have done Instruction and addressing handling, next its operations.
Added helper functions for flag handling. Setting and reading the status register flags.
Started working on the first cpu operations, also added cycle emulation. Some operations where a struggle, It took a while till I got BCD operations, also the break flag is special in it of itself, but good progress. Next up, more operations
Added a bunch more operations, had to learn a bit of low level byte and bit operations. Also started working on operations that work with the stack which is always fun
Finally finished all instructions. Now I will move to making the first machine (maybe apple I or II) and connecting all cpu mechanics and get the emu working.
Started working on the Apple I implementation. Setting memory ranges and more. Also added a console write and read to the bus so machines can display what the want, since each machine does whatever this is a way to normalize it
I worked on adding all the Apple I roms to the program, loading them at each required memory location and started working on some more of the UI
Made some more progress on Implementing the Apple I machine and some TUI handling code + misc fixes
Ok so I’m back Sorta refactoring the code base to be a cycle accurate state machine to make the emulation as truthful as I can, this involves coding each cycle independently (sorta) to maintain accuracy, I have started this refactoring with a lot to go, but at the end it will be much better than before see the code here as an example
Finished refactoring all the addressing code for it to be cycle accurate. Next I’ll check and fix operations and then the TUI situation and try to get the Apple I running, good progress
So I had to tackle some special cases to adapt everything to the new cycle accurate architecture These are mainly the operations that work with the stack In my architecture addressing handles fetching, while the run_operation() just does the math (and final data write if needed), so it only consumes one cycle, these special cases handles various cycles in their operation (independently of addressing mode) so I had to add that, and some other minor fixes to branch operations and other stuff
Big progress. GOT THE APPLE I RUNNING Hooray wozmon is up and running, marking the most successful milestone yet, a running system, i had to fix some opcode behaviors but it runs great!! Still very early, 1st, not all input keys are mapped, cycle stepping, the ui etc etc, but for now its progress....
|
1793195435.4388902
|
1793800235.4388902
|
|
47759
|
My own site! by @tnx | Stardance
|
tnx
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @tnx | Stardance
|
1793195434.5608208
|
1793800234.5608208
|
|
47758
|
My awesome macropad! by @carolinjilson8 | Stardanc My awesome macropad! by @carolinjilson8 | Stardance...
|
carolinjilson8
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @carolinjilson8 | S Title: My awesome macropad! by @carolinjilson8 | Stardance...
|
1793195433.6598568
|
1793800233.6598568
|
|
47757
|
My own site! by @Charstelle | Stardance
|
Charstelle
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @Charstelle | Stardance
|
1793195432.762725
|
1793800232.762725
|
|
47756
|
My awesome macropad! by @Felix215 | Stardance
|
Felix215
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Felix215 | Stardan Title: My awesome macropad! by @Felix215 | Stardance...
|
1793195431.8564093
|
1793800231.8564093
|
|
47755
|
Functional macropad by @YK-0n | Stardance
|
YK-0n
|
0
|
7.6
|
0
|
[]
|
[{"post_id": 51860, "ts": "202 [{"post_id": 51860, "ts": "2026-08-21T18:49:47Z", "hours": 1.1836, "text": "Applying some changes…"}, {"post_id": 51040, "ts": "2026-08-20T15:03:51Z", "hours": 1.6153, "text": "Update of the case"}, {"post_id": 50606, "ts": "2026-08-19T20:21:17Z", "hours": 0.3, "text": "I started the case"}, {"post_id": 49839, "ts": "2026-08-18T19:47:25Z", "hours": 2.4283, "text": "Finished the PCB!!! Let’s begin the Case!"}, {"post_id": 49095, "ts": "2026-08-17T18:35:04Z", "hours": 1.1836, "text": "Final PCB Design!!! (I simplified it a bit loll)"}, {"post_id": 48234, "ts": "2026-08-16T15:16:10Z", "hours": 0.8853, "text": "First step of designing a PCB: designing the scheme"}]...
|
Title: Functional macropad by @YK-0n | Stardance
Title: Functional macropad by @YK-0n | Stardance
Devlogs:
First step of designing a PCB: designing the scheme
Final PCB Design!!! (I simplified it a bit loll)
Finished the PCB!!! Let’s begin the Case!
I started the case
Update of the case
Applying some changes…...
|
1793195430.8590214
|
1793800230.8590214
|
|
47754
|
yildizzzzz by @phambinh10062011 | Stardance
|
phambinh10062011
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: yildizzzzz by @phambinh10062011 | Stardance
|
1793195429.933804
|
1793800229.933804
|
|
47753
|
yildizzzzz by @phambinh10062011 | Stardance
|
phambinh10062011
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: yildizzzzz by @phambinh10062011 | Stardance
|
1793195429.0233016
|
1793800229.0233016
|
|
47752
|
SDF Ray Tracing by @Stalhein | Stardance
|
Stalhein
|
0
|
6.7
|
0
|
[]
|
[{"post_id": 48025, "ts": "202 [{"post_id": 48025, "ts": "2026-08-16T09:48:47Z", "hours": 1.1453, "text": "Added shadows, another ray is just traced from the original hit towards the “sun”, and if it passes close to objects or hits objects, the colour is multiplied by some kind of factor. It was a great pain stopping the shadow ray intersecting the shape that was hit instantly, making everything look dark, as the start position must be moved out of the shape, but that can cause artifacts. This was fixed with a “bias” variable, which determines how steep the intersection was, and moves the position out of the shape accordingly."}, {"post_id": 47590, "ts": "2026-08-15T15:55:34Z", "hours": 1.0489, "text": "Not much progress this time, just normals for lighting, but I discovered the SDF of a ‘Mandelbulb’; a 3D version of a Mandelbrot fractal. I don’t really understand the function, but it produces the image underneath."}, {"post_id": 47111, "ts": "2026-08-14T19:17:54Z", "hours": 4.5039, "text": "I have set up WGPU with Rust to run a compute shader to render to a texture, which is then rendered to the screen. The compute shader ray traces using signed distance functions, stepping as far as the closest object at a time. There is also a simple, FPS-style camera implementation, so the scene can be looked around. Next, I plan to improve the graphics, with basic lighting and shadows, and perhaps materials instead of colours. I’m not sure where this project will go, but hopefully something interesting will come of it. The picture shows a sphere and long cuboid, a smin function used on them, with different parameters, causes them to blend. This is only one of the many interesting properties of SDFs."}]...
|
Title: SDF Ray Tracing by @Stalhein | Stardance
D Title: SDF Ray Tracing by @Stalhein | Stardance
Devlogs:
I have set up WGPU with Rust to run a compute shader to render to a texture, which is then rendered to the screen. The compute shader ray traces using signed distance functions, stepping as far as the closest object at a time. There is also a simple, FPS-style camera implementation, so the scene can be looked around. Next, I plan to improve the graphics, with basic lighting and shadows, and perhaps materials instead of colours. I’m not sure where this project will go, but hopefully something interesting will come of it. The picture shows a sphere and long cuboid, a smin function used on them, with different parameters, causes them to blend. This is only one of the many interesting properties of SDFs.
Not much progress this time, just normals for lighting, but I discovered the SDF of a ‘Mandelbulb’; a 3D version of a Mandelbrot fractal. I don’t really understand the function, but it produces the image underneath.
Added shadows, another ray is just traced from the original hit towards the “sun”, and if it passes close to objects or hits objects, the colour is multiplied by some kind of factor. It was a great pain stopping the shadow ray intersecting the shape that was hit instantly, making everything look dark, as the start position must be moved out of the shape, but that can cause artifacts. This was fixed with a “bias” variable, which determines how steep the intersection was, and moves the position out of the shape accordingly....
|
1793195428.0408018
|
1793800228.0408018
|
|
47751
|
Blueprint Create Site Contributions by @GoldMonke Blueprint Create Site Contributions by @GoldMonke | Stardance...
|
GoldMonke
|
0
|
2.13
|
0
|
[]
|
[{"post_id": 48426, "ts": "202 [{"post_id": 48426, "ts": "2026-08-16T19:28:57Z", "hours": 2.1325, "text": "IDK how ts took 2 hrs I was looking on egorro’s site blueprint that collects create addons and puts them nicely together, when I noticed that on my monitor (1440p) the text was overflowing in the info cards. So as any normal person would do I tried to fix it. I tried and I tried until I eventually fixed it by modifying the padding for large screens (2xl so 1536px wide and more) from 4 to 1. No idea how it took me TWO HOURS before I found that I tried so many different ways. PR"}]...
|
Title: Blueprint Create Site Contributions by @Gol Title: Blueprint Create Site Contributions by @GoldMonke | Stardance
Devlogs:
IDK how ts took 2 hrs I was looking on egorro’s site blueprint that collects create addons and puts them nicely together, when I noticed that on my monitor (1440p) the text was overflowing in the info cards. So as any normal person would do I tried to fix it. I tried and I tried until I eventually fixed it by modifying the padding for large screens (2xl so 1536px wide and more) from 4 to 1. No idea how it took me TWO HOURS before I found that I tried so many different ways. PR...
|
1793195426.8115115
|
1793800226.8115115
|
|
42915
|
The AR Study Zone by @ainesh_kumar7 | Stardance
|
ainesh_kumar7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The AR Study Zone by @ainesh_kumar7 | Stard Title: The AR Study Zone by @ainesh_kumar7 | Stardance...
|
1793195424.9357507
|
1793800224.9357507
|
|
47750
|
My awesome macropad! by @naaveemohamed289 | Starda My awesome macropad! by @naaveemohamed289 | Stardance...
|
naaveemohamed289
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @naaveemohamed289 | Title: My awesome macropad! by @naaveemohamed289 | Stardance...
|
1793195421.5782676
|
1793800221.5782676
|
|
42914
|
Fero by @mohammedkechida | Stardance
|
mohammedkechida
|
0
|
14.61
|
0
|
[]
|
[{"post_id": 47088, "ts": "202 [{"post_id": 47088, "ts": "2026-08-14T18:39:46Z", "hours": 4.5222, "text": "Devlog #3 | Big milestone What’s up buttercup Okay, so 1. I found out that devlogs should be shorter than what I am doing, but I realised that other people are doing the same so I don’t know if I should make it shorter or no, but I’ll try to reduce it. 2. I just realised I probably shouldn’t have explained that part because now it’s longer. 3. I just did it again I am super sorry. Okay fr now what’s up I’ve finally implemented FILE TRANSFERS yay!! But why not earlier? I need to first implement basic security measures, authentication and where each file belongs to. If I hadn’t made that part yet, then I’d be stuck having a bigger headache than I already have. I’ve also added device information in order to display what devices share the same room. I’ve ALSO also added some new templates for flask to render_template() with and display new information. Stubbornness My biggest issue that I’ve encountered by far was downloading multiple files at a time. And I find it kind of stupid because why can I upload multiple files but not download them??? I’ve scoured the internet and found the same suggestion: “just make it so you download a zip brah”. But I did not like that idea, it was so stupid and just ruined usability. So after a while of thinking, I realised I would probably make multiple download links and return them to the user for them to install the files, but what python command/feature could do a sorta thing.. hmmm. what python command could bundle up strings into one big string that can be analysed piece by piece, like some sort of… list… (say that again..). Anywho, yeah so I made a function where it puts all the links it generated into one list and that way another function (at the moment it’s a render_template) can take all of the links and download each file individually in the same page without redirecting the user constantly and without the user knowing. Although at the moment it’s just one page that displays all of the links and you have to download them manually by clicking the links but that will change later. The app now also contains a license (GPL-3.0) that will get distributed with it once it releases. What’s next? Right now, all of my functions have to be accessed manually (so I have to go to one link to create a room, another to upload, etc, etc), I’ll change it to be one continuous smooth process. At the same time, I’ll implement approving connections and various other minor stuff. What’s attached? This is some brand-new stuff: I’m attaching a video that both shows the file transfer working AND promotes my app. (I was going to use Bobby brown’s song “that’s the way love is” because he’s the goat but because of copyright I can’t, so take this audioless video instead.)"}, {"post_id": 45924, "ts": "2026-08-12T18:19:51Z", "hours": 5.1136, "text": "Devlog #2 | Yummy cookies Recap!! Fero is an application that runs locally on your computer allowing you to transfer files to and from your devices. Last devlog I explained that I managed to setup a sort of session system to assign devices a “room”, that will be useful for the transfer of files later on, but then I realised that flask can not really manage sessions server side… What’s new? I managed to find out how to make titles and stuff for my devlogs :). But yeah, you’re probably wondering what’s new for Fero and not my devlog :(. After some time of research, I realised I would not use flask-session, it wasn’t documented very well in my opinion, so it was difficult trying to implement it. I knew I needed some sort of database like SQL, and I knew how to use SQL a bit because of this super awesome steam game that teaches you about SQL (shout out Database Detective!!!). After a quick search I found flask_sqlalchemy, it gives you the ability to host your database in a file ending with .db and doesn’t require you to setup a service running in a different port and in docker (yeah flask-session I’m looking at you. Who even uses redis???). After some trial and error, I got the hang of the package, and I managed to implement a Rooms database that grabs the room’s ID, device IP (which is set as unique and the primary key), invite code, and the device type (whether the device is recieving or sending): class Rooms(db.Model): roomident: Mapped[str] deviceip: Mapped[str] = mapped_column(unique=True, primary_key=True) invcode: Mapped[str] devicetype: Mapped[str] I’ve added the ability to delete rooms, get room info of the receiver or the sender, delete client sessions, and made the room info show a QR code that allows you to join the room from a different device! @app.route('/reciever/join/<joincode>') def bindingjoin(joincode): findRoom = db.session.execute(db.select(Rooms.roomident).where(Rooms.invcode == joincode)).scalar_one() # took me a RIDICULOUS amount of time to figure out how to filter it, turns out I was doing Rooms.roomident == joincode instead of Rooms.invcode == joincode. smh. session['ident'] = findRoom session['joincode'] = joincode session['IP'] = request.remote_addr session['type'] = \"recieve\" createdroom = Rooms(roomident=findRoom, invcode=joincode, deviceip=request.remote_addr, devicetype=\"recieve\") db.session.add(createdroom) db.session.commit() return redirect('http://' + IPAddr + ':5000/reciever/roominfo') I’ve also added temporary developer tools in order to debug my program, this WILL be removed in the future as they provide access to modifications and the invite code (big no no to leave it public) to EVERY client. Unless I can find a way to leave it in WITHOUT giving access to it to every client. This took me a lot of time to make, mostly because I was experimenting with a new package that I have no clue how to use. I don’t remember really what were the parts that were super hard to implement because this devlog was supposed to be upload like 2 days ago, but I took a little well-deserved break. What’s next? Now we have a way to track devices (local router assigned IP and room Ident) and what they are supposed to be doing (recieving or sending), I will implement a new system that allows me to get ADDITIONAL device information (like device name), that way in the future, we can approve or deny access to clients to the room. I will also now work on the MAIN part of the project now, which is file sending and recieving. Which will be an IMPORTANT milestone and I cannot wait! What’s attached? Just some photos of some of the dev tools and the new room info page."}, {"post_id": 43507, "ts": "2026-08-08T20:31:24Z", "hours": 2.325, "text": "ACTUAL Devlog #1 | I managed to start it. (Before going into this, I’d like to apologize for the last devlog and this one, I am still getting the hang of the best practices for stardance.) So, I’ve managed to start my project. How? Well, I realized I need to slow down and focus, I grabbed a piece of paper from my printer and started writing down how Fero would work on a arrow diagram (I think that’s what it’s called.) And when I was staring at this piece of paper, It hit me, I should work on the project step by step (duhh.) I’ve never really completed much of my projects, I’ve always rushed them so I don’t know how to make projects, but I really wanted to finish this one to prove to myself, I wasn’t lazy and I could do whatever I set my mind to. Back to what I was saying, the first step of the project was device discovery and room creation. I worked on making an API service that could make random “room and share codes”. Room codes follow a 2 letter then 3 number system (example: AB-123) and the share codes are extremely long and are made using the secrets package on python. They sort of work as like a username and password. The room code is the username, can be public and can be used to verify if you are in the right room. The share code is like the password, it’s not public (should be private) and the server (local machine) checks if both matches on both devices (both session cookies), if it does then it would allow the receiver device to, well, receive. Although I haven’t worked on the discovery nor have I worked on the sharing part of the app, it’s still a major step in this project that I am proud of. However, I realized I have made a big mistake, you see, session cookies are handled by flask, but it shouldn’t be that way because natively flask can’t do much management or filtering for sessions, it only does basic stuff. For that I need flask-session, so NOW i have to learn flask-session, what it can do and how to use it. And rewrite a big part of my code (though it’s only 75 lines at the moment so no big deal, I guess.) Time to get back to work."}, {"post_id": 42651, "ts": "2026-08-07T14:23:18Z", "hours": 2.6444, "text": "The longest road I’ve ever been in… So, right now I’m working on Fero, my peer-to-peer application that solves one of my biggest issues, dropping files from one device to another because most of ’em either are too weird and bad and some have been just shutdown (rip intel unison). I made this project to challenge myself, and now it seems like my biggest step of this project is the START of the project, I have no clue where to start, it’s very difficult. Not only that but I’m thinking of utilising P2P packages like libp2p, but even then it’s very complicated. I’ve been going at this for 2h and 36 minutes and regardless how much I try to make sense of this project, I don’t how to start it. Regardless, I will push through, and I will make it a reality. I have perseverance."}]...
|
Title: Fero by @mohammedkechida | Stardance
Devlo Title: Fero by @mohammedkechida | Stardance
Devlogs:
The longest road I’ve ever been in… So, right now I’m working on Fero, my peer-to-peer application that solves one of my biggest issues, dropping files from one device to another because most of ’em either are too weird and bad and some have been just shutdown (rip intel unison). I made this project to challenge myself, and now it seems like my biggest step of this project is the START of the project, I have no clue where to start, it’s very difficult. Not only that but I’m thinking of utilising P2P packages like libp2p, but even then it’s very complicated. I’ve been going at this for 2h and 36 minutes and regardless how much I try to make sense of this project, I don’t how to start it. Regardless, I will push through, and I will make it a reality. I have perseverance.
ACTUAL Devlog #1 | I managed to start it. (Before going into this, I’d like to apologize for the last devlog and this one, I am still getting the hang of the best practices for stardance.) So, I’ve managed to start my project. How? Well, I realized I need to slow down and focus, I grabbed a piece of paper from my printer and started writing down how Fero would work on a arrow diagram (I think that’s what it’s called.) And when I was staring at this piece of paper, It hit me, I should work on the project step by step (duhh.) I’ve never really completed much of my projects, I’ve always rushed them so I don’t know how to make projects, but I really wanted to finish this one to prove to myself, I wasn’t lazy and I could do whatever I set my mind to. Back to what I was saying, the first step of the project was device discovery and room creation. I worked on making an API service that could make random “room and share codes”. Room codes follow a 2 letter then 3 number system (example: AB-123) and the share codes are extremely long and are made using the secrets package on python. They sort of work as like a username and password. The room code is the username, can be public and can be used to verify if you are in the right room. The share code is like the password, it’s not public (should be private) and the server (local machine) checks if both matches on both devices (both session cookies), if it does then it would allow the receiver device to, well, receive. Although I haven’t worked on the discovery nor have I worked on the sharing part of the app, it’s still a major step in this project that I am proud of. However, I realized I have made a big mistake, you see, session cookies are handled by flask, but it shouldn’t be that way because natively flask can’t do much management or filtering for sessions, it only does basic stuff. For that I need flask-session, so NOW i have to learn flask-session, what it can do and how to use it. And rewrite a big part of my code (though it’s only 75 lines at the moment so no big deal, I guess.) Time to get back to work.
Devlog #2 | Yummy cookies Recap!! Fero is an application that runs locally on your computer allowing you to transfer files to and from your devices. Last devlog I explained that I managed to setup a sort of session system to assign devices a “room”, that will be useful for the transfer of files later on, but then I realised that flask can not really manage sessions server side… What’s new? I managed to find out how to make titles and stuff for my devlogs :). But yeah, you’re probably wondering what’s new for Fero and not my devlog :(. After some time of research, I realised I would not use flask-session, it wasn’t documented very well in my opinion, so it was difficult trying to implement it. I knew I needed some sort of database like SQL, and I knew how to use SQL a bit because of this super awesome steam game that teaches you about SQL (shout out Database Detective!!!). After a quick search I found flask_sqlalchemy, it gives you the ability to host your database in a file ending with .db and doesn’t require you to setup a service running in a different port and in docker (yeah flask-session I’m looking at you. Who even uses redis???). After some trial and error, I got the hang of the package, and I managed to implement a Rooms database that grabs the room’s ID, device IP (which is set as unique and the primary key), invite code, and the device type (whether the device is recieving or sending): class Rooms(db.Model): roomident: Mapped[str] deviceip: Mapped[str] = mapped_column(unique=True, primary_key=True) invcode: Mapped[str] devicetype: Mapped[str] I’ve added the ability to delete rooms, get room info of the receiver or the sender, delete client sessions, and made the room info show a QR code that allows you to join the room from a different device! @app.route('/reciever/join/<joincode>') def bindingjoin(joincode): findRoom = db.session.execute(db.select(Rooms.roomident).where(Rooms.invcode == joincode)).scalar_one() # took me a RIDICULOUS amount of time to figure out how to filter it, turns out I was doing Rooms.roomident == joincode instead of Rooms.invcode == joincode. smh. session['ident'] = findRoom session['joincode'] = joincode session['IP'] = request.remote_addr session['type'] = "recieve" createdroom = Rooms(roomident=findRoom, invcode=joincode, deviceip=request.remote_addr, devicetype="recieve") db.session.add(createdroom) db.session.commit() return redirect('http://' + IPAddr + ':5000/reciever/roominfo') I’ve also added temporary developer tools in order to debug my program, this WILL be removed in the future as they provide access to modifications and the invite code (big no no to leave it public) to EVERY client. Unless I can find a way to leave it in WITHOUT giving access to it to every client. This took me a lot of time to make, mostly because I was experimenting with a new package that I have no clue how to use. I don’t remember really what were the parts that were super hard to implement because this devlog was supposed to be upload like 2 days ago, but I took a little well-deserved break. What’s next? Now we have a way to track devices (local router assigned IP and room Ident) and what they are supposed to be doing (recieving or sending), I will implement a new system that allows me to get ADDITIONAL device information (like device name), that way in the future, we can approve or deny access to clients to the room. I will also now work on the MAIN part of the project now, which is file sending and recieving. Which will be an IMPORTANT milestone and I cannot wait! What’s attached? Just some photos of some of the dev tools and the new room info page.
Devlog #3 | Big milestone What’s up buttercup Okay, so 1. I found out that devlogs should be shorter than what I am doing, but I realised that other people are doing the same so I don’t know if I should make it shorter or no, but I’ll try to reduce it. 2. I just realised I probably shouldn’t have explained that part because now it’s longer. 3. I just did it again I am super sorry. Okay fr now what’s up I’ve finally implemented FILE TRANSFERS yay!! But why not earlier? I need to first implement basic security measures, authentication and where each file belongs to. If I hadn’t made that part yet, then I’d be stuck having a bigger headache than I already have. I’ve also added device information in order to display what devices share the same room. I’ve ALSO also added some new templates for flask to render_template() with and display new information. Stubbornness My biggest issue that I’ve encountered by far was downloading multiple files at a time. And I find it kind of stupid because why can I upload multiple files but not download them??? I’ve scoured the internet and found the same suggestion: “just make it so you download a zip brah”. But I did not like that idea, it was so stupid and just ruined usability. So after a while of thinking, I realised I would probably make multiple download links and return them to the user for them to install the files, but what python command/feature could do a sorta thing.. hmmm. what python command could bundle up strings into one big string that can be analysed piece by piece, like some sort of… list… (say that again..). Anywho, yeah so I made a function where it puts all the links it generated into one list and that way another function (at the moment it’s a render_template) can take all of the links and download each file individually in the same page without redirecting the user constantly and without the user knowing. Although at the moment it’s just one page that displays all of the links and you have to download them manually by clicking the links but that will change later. The app now also contains a license (GPL-3.0) that will get distributed with it once it releases. What’s next? Right now, all of my functions have to be accessed manually (so I have to go to one link to create a room, another to upload, etc, etc), I’ll change it to be one continuous smooth process. At the same time, I’ll implement approving connections and various other minor stuff. What’s attached? This is some brand-new stuff: I’m attaching a video that both shows the file transfer working AND promotes my app. (I was going to use Bobby brown’s song “that’s the way love is” because he’s the goat but because of copyright I can’t, so take this audioless video instead.)...
|
1793195420.3507392
|
1793800220.3507392
|
|
42913
|
Adventurer by @Clouden | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Adventurer by @Clouden | Stardance
|
1793195419.4159153
|
1793800219.4159153
|
|
42912
|
My very own WebOS by @BlueDude11 | Stardance
|
BlueDude11
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @BlueDude11 | Stardanc Title: My very own WebOS by @BlueDude11 | Stardance...
|
1793195418.5124748
|
1793800218.5124748
|
|
42905
|
Right hand man by @Evangel | Stardance
|
Evangel
|
0
|
6.52
|
0
|
[]
|
[{"post_id": 68854, "ts": "202 [{"post_id": 68854, "ts": "2026-09-15T21:33:36Z", "hours": 0.6167, "text": "I have been working on the HackPad for a while (way more than I’ve tracked because it kept crashing; now it doesn’t work at all). I did run into a few problems with the RGB LEDs. The DRC keeps on giving me unsolvable errors. I have consulted with multiple Hackclubbers who I based my project on, but it just doesn’t work for some reason. I might remove them, but since it’s such a cool feature, it seems like a waste. Plus, routing around them took ages, so I do not want to reroute the PCB for the billionth time."}, {"post_id": 65641, "ts": "2026-09-10T22:15:43Z", "hours": 1.9667, "text": "I completely redesigned my schematic 2 days ago (forgot to devlog). I watched many tutorials and got inspiration from many people’s own projects, which surprisingly worked effectively. I think this is the 4th time I’m doing the schematic again. In my previous schematic, I ran into a few problems when routing, and I feel like I did not really understand what I was doing. These past few days I’ve just been fixing my problems, and surprisingly I’ve actually learnt a lot. Before, I was just following tutorials without really thinking much abt what I was doing. As of recent thouh one of the problems I have is regarding the PCB, which has a problem that basically has no solution. I’ll try to talk abt it in my next devlog."}, {"post_id": 62137, "ts": "2026-09-05T12:04:56Z", "hours": 2.6833, "text": "Trying to route the PCB for my macropad. This is my first and half a time freestyling a PCB, and I am so confused. Im just doing anything, like literally. had to change up the schematic and fix the frame. It probably has a lot of defects, but what can I say. It’s a learning process."}, {"post_id": 59903, "ts": "2026-09-01T22:31:19Z", "hours": 1.2544, "text": "My soon-to-be right-hand man is officially in progress. Just finished the basics of my hackpad, which is basically working on the PCB and the case. Tomorrow I’ll customize it. I also need to create a GitHub repository and the firmware."}]...
|
Title: Right hand man by @Evangel | Stardance
Dev Title: Right hand man by @Evangel | Stardance
Devlogs:
My soon-to-be right-hand man is officially in progress. Just finished the basics of my hackpad, which is basically working on the PCB and the case. Tomorrow I’ll customize it. I also need to create a GitHub repository and the firmware.
Trying to route the PCB for my macropad. This is my first and half a time freestyling a PCB, and I am so confused. Im just doing anything, like literally. had to change up the schematic and fix the frame. It probably has a lot of defects, but what can I say. It’s a learning process.
I completely redesigned my schematic 2 days ago (forgot to devlog). I watched many tutorials and got inspiration from many people’s own projects, which surprisingly worked effectively. I think this is the 4th time I’m doing the schematic again. In my previous schematic, I ran into a few problems when routing, and I feel like I did not really understand what I was doing. These past few days I’ve just been fixing my problems, and surprisingly I’ve actually learnt a lot. Before, I was just following tutorials without really thinking much abt what I was doing. As of recent thouh one of the problems I have is regarding the PCB, which has a problem that basically has no solution. I’ll try to talk abt it in my next devlog.
I have been working on the HackPad for a while (way more than I’ve tracked because it kept crashing; now it doesn’t work at all). I did run into a few problems with the RGB LEDs. The DRC keeps on giving me unsolvable errors. I have consulted with multiple Hackclubbers who I based my project on, but it just doesn’t work for some reason. I might remove them, but since it’s such a cool feature, it seems like a waste. Plus, routing around them took ages, so I do not want to reroute the PCB for the billionth time....
|
1793195417.4531007
|
1793800217.4531007
|
|
42902
|
SmartCalc by @imranbelhaj89 | Stardance
|
imranbelhaj89
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SmartCalc by @imranbelhaj89 | Stardance
|
1793195416.5047972
|
1793800216.5047972
|
|
42901
|
My awesome macropad! by @adamghauri | Stardance
|
adamghauri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @adamghauri | Stard Title: My awesome macropad! by @adamghauri | Stardance...
|
1793195415.5713422
|
1793800215.5713422
|
|
42900
|
Once Upon an October by @uponadecember | Stardance
|
uponadecember
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Once Upon an October by @uponadecember | St Title: Once Upon an October by @uponadecember | Stardance...
|
1793195414.6684844
|
1793800214.6684844
|
|
17516
|
My very own WebOS by @Sahithi | Stardance
|
Sahithi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Sahithi | Stardance
|
1793195413.7680817
|
1793800213.7680817
|
|
21497
|
An ai chat bot by @Raj7 | Stardance
|
Raj7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: An ai chat bot by @Raj7 | Stardance
|
1793195412.8898118
|
1793800212.8898118
|
|
578
|
Cara Website by @SB | Stardance
|
SB
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cara Website by @SB | Stardance
|
1793195411.9876823
|
1793800211.9876823
|
|
1990
|
Untitled project by @bushbaby9001 | Stardance
|
bushbaby9001
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @bushbaby9001 | Stardan Title: Untitled project by @bushbaby9001 | Stardance...
|
1793195411.008537
|
1793800211.008537
|
|
4101
|
My first slack bot! by @kushalava917 | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @kushalava917 | Star Title: My first slack bot! by @kushalava917 | Stardance...
|
1793195410.0695655
|
1793800210.0695655
|
|
16557
|
My first slack bot! by @Di | Stardance
|
Di
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Di | Stardance
|
1793195409.165939
|
1793800209.165939
|
|
27174
|
Fracture Pad (Macro Pad Project) by @Imversia | St Fracture Pad (Macro Pad Project) by @Imversia | Stardance...
|
Imversia
|
0
|
43.85
|
0
|
[]
|
[{"post_id": 35958, "ts": "202 [{"post_id": 35958, "ts": "2026-07-27T19:00:12Z", "hours": 3.3547, "text": "Dev Log 16 (27/07/26) What have I done? Worked on Git hub stuff like read me and uploaded some files. Mainly learnt how Git works like cloning repos and stuff (man that was so annoying learning how use Github is was so confusing *for me). Link to my Github for the macro pad. What is there left to do? Get firmware done. Get PCB sent to manufacture for assembly"}, {"post_id": 32636, "ts": "2026-07-21T22:27:24Z", "hours": 3.4931, "text": "Dev Log 15 (21/07/26) What have I done: Finished Aesthetics, added a Voronoi patterned geometry on the OLED cover, i experimented with adding a full Voronoi pattern across the top faces but that just looked messy and based on the feedback i gotten from friend and other people i have decided that its better to only have the OLED cover with the pattern. Added TPU feet to the casing as based on my experience with 3d printing, 3d printed objects tend to slide really easily on smooth surfaces like tables so yeah… will be printed separately from the case and glued on. What will I do next? Well I guess its time to start to refine the BOM and Github stuff and get the PCB to be manufactured…. thats going to be a pain…. Start work on firmware, need to research what to do and how to do it. Thats my devblog today, thanks for reading."}, {"post_id": 31995, "ts": "2026-07-20T20:45:19Z", "hours": 3.3333, "text": "Dev Log 14 (20/07/26) Will post full dev log later, but short summary: Completed snap lock system just need to work on aesthetics and then im done."}, {"post_id": 31536, "ts": "2026-07-20T00:50:43Z", "hours": 1.5003, "text": "Dev Log 13 (20/07/26) Sooooo its finally starting to come into shape, think im done with the case? nahhh its a still a freaking ugly box, just wait to see what im going to do… (check my pfp for hints). What have I done? Completed the cover for the OLED driver. Designed a slot system to secure the OLED to the case. (Totally did not overthink this…) Designed Rotary encoder knobs that i will 3D print, added the texturing to it for more grip. What I still need to do to complete the case? Need to add in the snap lock system (ughh i can feel that this part is going to be annoying, probably need to 3D print a prototype to test before I can get it right) Anyways thats my dev blog for today, thanks for reading."}, {"post_id": 31001, "ts": "2026-07-19T01:19:56Z", "hours": 1.6553, "text": "Dev Log 12 (19/07/26) What are the main things I done: Worked on OLED placement (so annoying due to the sizing requirements cause i really wanted this transparent OLED that looks really cool but it came with a driver board so i had create mounting space for it, ik i could have integrated it into the board itself but that will cause more failure points and for a macropad its not worth it so yeah) Edited PCB OLED driver board mounting holes to accommodate the OLED placement (another really frustrating part cause i had to revert and redo stuff…) What Is there still to do for the case? Complete OLED mounting on the case. Add the snap lock system"}, {"post_id": 30461, "ts": "2026-07-18T01:21:47Z", "hours": 2.5, "text": "Dev Log 11 (18/07/26) Alr yeah took a 10 day break but back at it again, had to make changes to my PCB cause i didnt know about settings design constrains so some of my clearances were wrong…. butttt I work on the casing today and got the hardest part of the casing done, man i was stuck on this part forever…. i swear the longest part of designing smth is thinking of ideas over and over again… *screaming internally, like i spent so so so so long trying to figure out how to add in a plate to support the MX switches while using no screws and allowing room for the OLED and its driver board… Turns out i was OVERTHINKING…. and the solution was so simple, just create a hole for it and design a cool looking lid to cover it. –––––––––– What did I learn? —————–– Dont overthink stuff. ———————What will i do next time?––––––– Work on the case, should be done within a couple of hours, and its not going to a plain box…"}, {"post_id": 26371, "ts": "2026-07-11T03:47:36Z", "hours": 0.8061, "text": "Will post full dev log later on today, just need to log time"}, {"post_id": 25627, "ts": "2026-07-10T00:55:38Z", "hours": 1.4167, "text": "Dev log 10 (10/07/26) I lost 3hrs of time….. :((((( but oh well, at least im progressing, so heres what i did. ———————— What have I done ———————— I have started work and completed the main parts of the lower half of the case, i decided to add a 5 degree slant to the case for ergonomics and made a slot for the USB slot, my goal for the case is to not use screws so i designed a type of insert for the PCB mounting holes as shown in the picture. ————————What have I learnt—————— I noticed some boards have a plate for their MX switches to support them and I have done research of snap lock profiles and how they work so i can implement that into my case."}, {"post_id": 24482, "ts": "2026-07-08T01:48:36Z", "hours": 2.3167, "text": "Dev Log 9 (08/07/26) ———————Quick summary––––––––––– Finished 3D model of the PCB, didnt really learn much today apart from the orientation of a RGB led (SK smth mini-e) is defined by a chamfered notch. Will move onto designing the case now."}, {"post_id": 23913, "ts": "2026-07-07T03:40:11Z", "hours": 4.7336, "text": "Dev log 8 (07/07/26) ––––––––––PCB Tracing Complete––––––––––– PCB tracing complete, in my opinion its the best part of PCB design but yeah. I know I could have routed the 5V line to the right of the board but by the time I realized that I would have needed to redo large sections of the board, so I will keep that in mind if I ever want to make a version 2. ———————– What I learnt —————— You can create a trace at any angle from a vias on a pcb, keep sensitive signal lines away from 5V and 3.3V lines, Minimize the interruptions of the ground plane to allow an uninterrupted ground path etc… 5V trace thickness : 0.5mm 3.3V trace thickness 0.3mm signal trace thickness : 0.25mm, when routing power to components it is ideal to split the power in parallel than in series as it allows the voltage across branches to be the same (basic physics). ———————–What will I do next? —————— I will move on to casing design once I ensured my PCB can function, I can ensure that by asking around communities like discord or slack."}, {"post_id": 23714, "ts": "2026-07-06T20:24:47Z", "hours": 4.7336, "text": "Ill post full dev log later on today"}, {"post_id": 23188, "ts": "2026-07-06T00:36:44Z", "hours": 1.65, "text": "Dev log 7 ( 06/07/26 ) —————Just a quick summary this time––––––– Worked on PCB layout, decided to place the diodes and local decoupling capacitors for the RGB leds and Switches on the underside of the board to save space. Always learning as per usual, key highlight that I learned today that you cant manufacture asymmetrical layered boards due to PCB manufacturing methods *not going to go into detail, basically in a nutshell you cant make boards with an odd number of layers. —————––What will I do next———————– I should finally actually start work on tracing, idk why its taking so long…."}, {"post_id": 22499, "ts": "2026-07-05T00:15:25Z", "hours": 3.7678, "text": "PCB traces dev log 6 ( 05/07/26 ) Unfortunately i lost 5 hours of time cause the tab linking the lookout time lapse accidentally got closed on my last session. —————–– What have I done –––––––––– Completed pcb component placement. Started work on tracing. Replaced the original RGBs with SK6812MINI‑E cause these LEDs have a cutout in the PCB allowing them to sit flush and not take up any space on the surface layer allowing room for the cherry mx switches (need to find the footprint online, i used something called component search engine to find the footprint) . Added mounting holes for the OLED driver board and PCB placement. Added a ground plane. Studied PCB tracing and component placement order. Helped more ppl with their hackpad schematic/pcb on slack. ––––––––––– What have I learnt —————— Component placement order, placing the components that define the PCB onto the board, (not going to go into details, cant be bothered, its 1am lol) What routes i should trace first. How to make edges curved in Ki Cad PCB design (pcb looks nicer). Learnt that every RGB LED needs a individual decoupling capacitor, learnt that the GPIO expander should have 2 capacitors. ––––––––––––––What i will do next –––––––––– Complete traces on PCB. Start work on the casing, i wana make it look cool, should be smth like my Raspberry pi cases (check my pfp) Share the knowledge I learnt if someone needs or wants it."}, {"post_id": 21220, "ts": "2026-07-03T01:31:02Z", "hours": 1.35, "text": "Dev log 4 (03/07/2026) —————–What i learnt today—————– Pins on the Xiao Microcontroller like Tx for serial communications what do A and D stand for (digital, analogue) and how I2C works like addresses and how multiple components share the same line. How to assign footprints in KiCad. MLCC capacitors (learnt the name and their existence lol) –––––––– What i have done —————–– Completed the schematic, fully refined it, added a GPIO extender. Refined component BOM Helped some people with their schematic today> ––––––––What will i do next?—————– Will refine the BOM more, amazon is kinda expensive, maybe aliexpress?? *any suggestions? Start research and work on PCB, by research i mean using AI and websites to understand what im doing, NOTE: I only use AI to understand and learn things so i dont have to use it again/dependent on it to do stuff. I will also take a look at how people layout their BOM so i can learn how to write a good BOM cause the current one i have is kinda sketch *i think"}, {"post_id": 20946, "ts": "2026-07-02T17:55:53Z", "hours": 1.9833, "text": "Completing component BOM + refining schematic Fixed some problems with my schematic. Added a GPIO expander for rotary encoders, did some research about the components im using such as how to wire the Expander or which type of capacitor im using e.g electrolytic or ceramic."}, {"post_id": 20267, "ts": "2026-07-01T20:22:33Z", "hours": 3.5833, "text": "Dev Log 02 01/07/26 Schematic complete: ———––What I have done?––––––– Completed the schematic. Reduced the number or rotary encoders from 3 to 1 because I ran out of GPIO pins. Sorta learnt how components such as rotary encoders work, like how the MCU pin detects the digital input (low) from the rotary encoder as it turns and how the WS2812B -2020 are meant to be wired, (led for back lit keys). Learnt about decoupling capacitors and how they work by providing current when power supply cant handle it. —– What will I do next? —– I will move onto tracing the schematic to turn it into a PCB, but first I will ask for feedback from places like discord to ensure my schematic is ok. Or if anyone sees this, please provide feedback, it would be greatly appreciated."}, {"post_id": 20034, "ts": "2026-07-01T15:15:04Z", "hours": 1.6689, "text": "01/07/26 First ever project involving a PCB. Worked on selecting the parts I would use for the macro pad to set constraints for dimensions and made a simple sketch in CAD to visualize the layout. I wanted a macro pad with 9 keys, 3 rotary encoders, and a OLED to display stats like cpu temps / usage, RAM usage etc…. I had trouble finding a OLED with the correct dimensions that suited my project as aliexpress or amazon dont really specify dimensions but i found a supplier called waveshare that provided the information i needed and a suitable OLED. Based on my research I will be using a keyboard matrix with diodes to prevent ghost keys, i will be also adding RGB lights to enhance aesthetic appeal."}]...
|
Title: Fracture Pad (Macro Pad Project) by @Imvers Title: Fracture Pad (Macro Pad Project) by @Imversia | Stardance
Devlogs:
01/07/26 First ever project involving a PCB. Worked on selecting the parts I would use for the macro pad to set constraints for dimensions and made a simple sketch in CAD to visualize the layout. I wanted a macro pad with 9 keys, 3 rotary encoders, and a OLED to display stats like cpu temps / usage, RAM usage etc…. I had trouble finding a OLED with the correct dimensions that suited my project as aliexpress or amazon dont really specify dimensions but i found a supplier called waveshare that provided the information i needed and a suitable OLED. Based on my research I will be using a keyboard matrix with diodes to prevent ghost keys, i will be also adding RGB lights to enhance aesthetic appeal.
Dev Log 02 01/07/26 Schematic complete: ———––What I have done?––––––– Completed the schematic. Reduced the number or rotary encoders from 3 to 1 because I ran out of GPIO pins. Sorta learnt how components such as rotary encoders work, like how the MCU pin detects the digital input (low) from the rotary encoder as it turns and how the WS2812B -2020 are meant to be wired, (led for back lit keys). Learnt about decoupling capacitors and how they work by providing current when power supply cant handle it. —– What will I do next? —– I will move onto tracing the schematic to turn it into a PCB, but first I will ask for feedback from places like discord to ensure my schematic is ok. Or if anyone sees this, please provide feedback, it would be greatly appreciated.
Completing component BOM + refining schematic Fixed some problems with my schematic. Added a GPIO expander for rotary encoders, did some research about the components im using such as how to wire the Expander or which type of capacitor im using e.g electrolytic or ceramic.
Dev log 4 (03/07/2026) —————–What i learnt today—————– Pins on the Xiao Microcontroller like Tx for serial communications what do A and D stand for (digital, analogue) and how I2C works like addresses and how multiple components share the same line. How to assign footprints in KiCad. MLCC capacitors (learnt the name and their existence lol) –––––––– What i have done —————–– Completed the schematic, fully refined it, added a GPIO extender. Refined component BOM Helped some people with their schematic today> ––––––––What will i do next?—————– Will refine the BOM more, amazon is kinda expensive, maybe aliexpress?? *any suggestions? Start research and work on PCB, by research i mean using AI and websites to understand what im doing, NOTE: I only use AI to understand and learn things so i dont have to use it again/dependent on it to do stuff. I will also take a look at how people layout their BOM so i can learn how to write a good BOM cause the current one i have is kinda sketch *i think
PCB traces dev log 6 ( 05/07/26 ) Unfortunately i lost 5 hours of time cause the tab linking the lookout time lapse accidentally got closed on my last session. —————–– What have I done –––––––––– Completed pcb component placement. Started work on tracing. Replaced the original RGBs with SK6812MINI‑E cause these LEDs have a cutout in the PCB allowing them to sit flush and not take up any space on the surface layer allowing room for the cherry mx switches (need to find the footprint online, i used something called component search engine to find the footprint) . Added mounting holes for the OLED driver board and PCB placement. Added a ground plane. Studied PCB tracing and component placement order. Helped more ppl with their hackpad schematic/pcb on slack. ––––––––––– What have I learnt —————— Component placement order, placing the components that define the PCB onto the board, (not going to go into details, cant be bothered, its 1am lol) What routes i should trace first. How to make edges curved in Ki Cad PCB design (pcb looks nicer). Learnt that every RGB LED needs a individual decoupling capacitor, learnt that the GPIO expander should have 2 capacitors. ––––––––––––––What i will do next –––––––––– Complete traces on PCB. Start work on the casing, i wana make it look cool, should be smth like my Raspberry pi cases (check my pfp) Share the knowledge I learnt if someone needs or wants it.
Dev log 7 ( 06/07/26 ) —————Just a quick summary this time––––––– Worked on PCB layout, decided to place the diodes and local decoupling capacitors for the RGB leds and Switches on the underside of the board to save space. Always learning as per usual, key highlight that I learned today that you cant manufacture asymmetrical layered boards due to PCB manufacturing methods *not going to go into detail, basically in a nutshell you cant make boards with an odd number of layers. —————––What will I do next———————– I should finally actually start work on tracing, idk why its taking so long….
Ill post full dev log later on today
Dev log 8 (07/07/26) ––––––––––PCB Tracing Complete––––––––––– PCB tracing complete, in my opinion its the best part of PCB design but yeah. I know I could have routed the 5V line to the right of the board but by the time I realized that I would have needed to redo large sections of the board, so I will keep that in mind if I ever want to make a version 2. ———————– What I learnt —————— You can create a trace at any angle from a vias on a pcb, keep sensitive signal lines away from 5V and 3.3V lines, Minimize the interruptions of the ground plane to allow an uninterrupted ground path etc… 5V trace thickness : 0.5mm 3.3V trace thickness 0.3mm signal trace thickness : 0.25mm, when routing power to components it is ideal to split the power in parallel than in series as it allows the voltage across branches to be the same (basic physics). ———————–What will I do next? —————— I will move on to casing design once I ensured my PCB can function, I can ensure that by asking around communities like discord or slack.
Dev Log 9 (08/07/26) ———————Quick summary––––––––––– Finished 3D model of the PCB, didnt really learn much today apart from the orientation of a RGB led (SK smth mini-e) is defined by a chamfered notch. Will move onto designing the case now.
Dev log 10 (10/07/26) I lost 3hrs of time….. :((((( but oh well, at least im progressing, so heres what i did. ———————— What have I done ———————— I have started work and completed the main parts of the lower half of the case, i decided to add a 5 degree slant to the case for ergonomics and made a slot for the USB slot, my goal for the case is to not use screws so i designed a type of insert for the PCB mounting holes as shown in the picture. ————————What have I learnt—————— I noticed some boards have a plate for their MX switches to support them and I have done research of snap lock profiles and how they work so i can implement that into my case.
Will post full dev log later on today, just need to log time
Dev Log 11 (18/07/26) Alr yeah took a 10 day break but back at it again, had to make changes to my PCB cause i didnt know about settings design constrains so some of my clearances were wrong…. butttt I work on the casing today and got the hardest part of the casing done, man i was stuck on this part forever…. i swear the longest part of designing smth is thinking of ideas over and over again… *screaming internally, like i spent so so so so long trying to figure out how to add in a plate to support the MX switches while using no screws and allowing room for the OLED and its driver board… Turns out i was OVERTHINKING…. and the solution was so simple, just create a hole for it and design a cool looking lid to cover it. –––––––––– What did I learn? —————–– Dont overthink stuff. ———————What will i do next time?––––––– Work on the case, should be done within a couple of hours, and its not going to a plain box…
Dev Log 12 (19/07/26) What are the main things I done: Worked on OLED placement (so annoying due to the sizing requirements cause i really wanted this transparent OLED that looks really cool but it came with a driver board so i had create mounting space for it, ik i could have integrated it into the board itself but that will cause more failure points and for a macropad its not worth it so yeah) Edited PCB OLED driver board mounting holes to accommodate the OLED placement (another really frustrating part cause i had to revert and redo stuff…) What Is there still to do for the case? Complete OLED mounting on the case. Add the snap lock system
Dev Log 13 (20/07/26) Sooooo its finally starting to come into shape, think im done with the case? nahhh its a still a freaking ugly box, just wait to see what im going to do… (check my pfp for hints). What have I done? Completed the cover for the OLED driver. Designed a slot system to secure the OLED to the case. (Totally did not overthink this…) Designed Rotary encoder knobs that i will 3D print, added the texturing to it for more grip. What I still need to do to complete the case? Need to add in the snap lock system (ughh i can feel that this part is going to be annoying, probably need to 3D print a prototype to test before I can get it right) Anyways thats my dev blog for today, thanks for reading.
Dev Log 14 (20/07/26) Will post full dev log later, but short summary: Completed snap lock system just need to work on aesthetics and then im done.
Dev Log 15 (21/07/26) What have I done: Finished Aesthetics, added a Voronoi patterned geometry on the OLED cover, i experimented with adding a full Voronoi pattern across the top faces but that just looked messy and based on the feedback i gotten from friend and other people i have decided that its better to only have the OLED cover with the pattern. Added TPU feet to the casing as based on my experience with 3d printing, 3d printed objects tend to slide really easily on smooth surfaces like tables so yeah… will be printed separately from the case and glued on. What will I do next? Well I guess its time to start to refine the BOM and Github stuff and get the PCB to be manufactured…. thats going to be a pain…. Start work on firmware, need to research what to do and how to do it. Thats my devblog today, thanks for reading.
Dev Log 16 (27/07/26) What have I done? Worked on Git hub stuff like read me and uploaded some files. Mainly learnt how Git works like cloning repos and stuff (man that was so annoying learning how use Github is was so confusing *for me). Link to my Github for the macro pad. What is there left to do? Get firmware done. Get PCB sent to manufacture for assembly...
|
1793195407.7866378
|
1793800207.7866378
|
|
8526
|
Untitled project by @baruchgeuze | Stardance
|
baruchgeuze
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @baruchgeuze | Stardanc Title: Untitled project by @baruchgeuze | Stardance...
|
1793195406.8698118
|
1793800206.8698118
|
|
25161
|
My very own WebOS by @danique | Stardance
|
danique
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @danique | Stardance
|
1793195405.9736376
|
1793800205.9736376
|
|
14435
|
Pulse by @Mark_Mitrofanov | Stardance
|
Mark_Mitrofanov
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Pulse by @Mark_Mitrofanov | Stardance
|
1793195405.0786119
|
1793800205.0786119
|
|
8925
|
My awesome macropad! by @antek042 | Stardance
|
antek042
|
0
|
2.68
|
0
|
[]
|
[{"post_id": 5118, "ts": "2026 [{"post_id": 5118, "ts": "2026-06-08T20:06:50Z", "hours": 0.6781, "text": "I added basic firmware for my controller"}, {"post_id": 4085, "ts": "2026-06-07T08:44:17Z", "hours": 1.2325, "text": "I added diodes to make keyboard matrix"}, {"post_id": 3582, "ts": "2026-06-06T16:13:24Z", "hours": 0.4492, "text": "I’ve done complete PCB for the controller"}, {"post_id": 3385, "ts": "2026-06-06T08:57:06Z", "hours": 0.3197, "text": "I’ve designed my first PCB in my life and I feel amazing. My PCB has slots for keycaps and a microcontroller which I plan to program in raw C. Now I’m going to create a case for it to make this project even cooler!"}]...
|
Title: My awesome macropad! by @antek042 | Stardan Title: My awesome macropad! by @antek042 | Stardance
Devlogs:
I’ve designed my first PCB in my life and I feel amazing. My PCB has slots for keycaps and a microcontroller which I plan to program in raw C. Now I’m going to create a case for it to make this project even cooler!
I’ve done complete PCB for the controller
I added diodes to make keyboard matrix
I added basic firmware for my controller...
|
1793195404.1096606
|
1793800204.1096606
|
|
3915
|
My awesome macropad! by @rykerj | Stardance
|
rykerj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @rykerj | Stardance
|
1793195403.190828
|
1793800203.190828
|
|
3885
|
the escape by @Monstermoy | Stardance
|
Monstermoy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: the escape by @Monstermoy | Stardance
|
1793195402.2973864
|
1793800202.2973864
|