|
13891
|
MachineServer by @job | Stardance
|
job
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: MachineServer by @job | Stardance
|
1792774165.881996
|
1793378965.881996
|
|
28159
|
Drone by @Aarushp | Stardance
|
Aarushp
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Drone by @Aarushp | Stardance
|
1792774166.7061453
|
1793378966.7061453
|
|
27429
|
Untitled by @lochi | Stardance
|
lochi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @lochi | Stardance
|
1792774167.53987
|
1793378967.53987
|
|
26220
|
My awesome macropad! by @JP_Botha | Stardance
|
JP_Botha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @JP_Botha | Stardan Title: My awesome macropad! by @JP_Botha | Stardance...
|
1792774170.9562123
|
1793378970.9562123
|
|
26406
|
Pendryx Pico by @Partholimew | Stardance
|
Partholimew
|
0
|
18.58
|
0
|
[]
|
[{"post_id": 69612, "ts": "202 [{"post_id": 69612, "ts": "2026-09-17T12:44:46Z", "hours": 1.7833, "text": "Here’s an update since it’s been awhile. I have received all my parts. It took awhile since I accidentally ordered the wrong solder paste and had to wait to get the new one though. Anyway, I have assembled the board, accidentally put the LEDs on backwards, had to remove and reorient them, and now I’m debugging it to see what could be wrong with it. The power LED does turn on, but the board is not recognized, so I’m still looking into why. Here’s how it turned out though! (SMD soldering is fun!)"}, {"post_id": 46410, "ts": "2026-08-13T16:24:25Z", "hours": 0.39, "text": "I did some last-minute organization to correct a few messy traces on the PCB, but now that I have funding, I have ordered the components and will be building once they arrive."}, {"post_id": 36041, "ts": "2026-07-27T21:19:25Z", "hours": 1.8294, "text": "Shipped! (At least until I have approval for funding) The Pendryx Pico is a rpi Pico-sized devboard with 28 GPIO pins, including I2C (In order), and a mic. It has 520 KB of ram, 18 MB of flash memory, and connects via USB-C!"}, {"post_id": 35538, "ts": "2026-07-27T01:27:33Z", "hours": 0.9503, "text": "I have completed my PCB checks and finished labeling the board. All that is left before shipping is to complete the GitHub page and actually ship!"}, {"post_id": 35228, "ts": "2026-07-26T15:10:06Z", "hours": 3.2003, "text": "I DID IT! I managed to route the entire PCB, and fit all the components. The only thing I had to cut was the I2C header. However, It’s still accessible on the GPIO (In the correct order and including the needed resistors) So you could directly connect a display to it. All that’s left to do before I ship is to check all my work and do some more friendly labeling! (And of course the GitHub repo)"}, {"post_id": 34636, "ts": "2026-07-25T15:06:01Z", "hours": 0.9308, "text": "I managed to hook up the power and usb data to the actual rp2354a chip, including both the 3.3 and 1.1v connections. It’s a bit messy, but it worked. I’m currently trying to figure out how to attach my extra flash memory, since that chip isn’t exactly tiny, and it still needs to reach the correct pins on the core. I’ll also have to leave room for GPIO wiring. But I’m still hoping it will continue to go fairly well."}, {"post_id": 34585, "ts": "2026-07-25T13:09:27Z", "hours": 4.9378, "text": "This one isn’t going to look like much progress per amount of time compared to the others, but here we go. I assigned pcb footprints to all my components. Then, I started on the pcb, only to realize that some of those footprints are a bit large for a 20 x 50 mm board. So after a lot of attempting to make it work, I finally changed to smaller resistor and capacitor footprints. I will also likely change my button and crystal footprints later, since they are a bit too large as well, but I’ll do that when I get to that part of the board. Anyway, I’m finished with the usb power and data parts of the pcb (for now) and have to do the main core and I/O next, which will likely be a pain, (Hence why my starting sections are so cramped) but I figured I should stop here to make a log. Hoping all goes well in the next steps!"}, {"post_id": 33768, "ts": "2026-07-23T23:07:08Z", "hours": 0.5283, "text": "Ok, so I’ve added an analog mic, as well as an extra 16 mb flash memory. So in theory you can store a decent amount of audio or whatever else on this thing. The mic won’t exactly be great quality, but it will work for general uses like sound activation. I’m tempted to add wifi, so I’m either going to do that next or start the PCB."}, {"post_id": 33755, "ts": "2026-07-23T22:26:45Z", "hours": 0.9836, "text": "I finished the main schematic for the board by adding a status LED and setting up the IO pins. I think I might still add a few things before working on the PCB though. I’m considering extra flash memory and perhaps an inbuilt mic for some extra features. I may end up making some modules for this board later on. But here’s thee pictures!"}, {"post_id": 33547, "ts": "2026-07-23T16:12:28Z", "hours": 0.5836, "text": "I finished the USB data sheet. So now the board can actually send and receive data, which is rather important for a devboard. Lots of screenshots this time due to small changes to various parts of the schematic. Once I finish all the critical systems, I’ll add some of the things that will make it a bit different from a standard pico."}, {"post_id": 33211, "ts": "2026-07-22T22:17:50Z", "hours": 1.6503, "text": "I updated the power sheet a bit. Then I worked on one of the more complicated parts of this schematic design; the core sheet. It took a little while, but I think it works, so long as I do the other sheets right of course. I also began my main schematic diagram since I have more than one sheet, and you can see the single 3.3v line from the usb-c power sheet running to the core! I know, exciting stuff, right? Anyways, I have a ways to go before I can work on the actual pcb, and will likely be adding some features to make it different from a basic pico, otherwise there wouldn’t be much point!"}, {"post_id": 32526, "ts": "2026-07-21T19:18:23Z", "hours": 0.8167, "text": "So I’ve decided to try making an Rpi Pico-esque devboard. Since I don’t have that much experience with such things, it’s a lot of trial and error, as well as referencing far too many things at once. I decided to start by trying to make the power delivery circuit. I’m not certain it is correct, but an attempt was made."}]...
|
Title: Pendryx Pico by @Partholimew | Stardance
D Title: Pendryx Pico by @Partholimew | Stardance
Devlogs:
So I’ve decided to try making an Rpi Pico-esque devboard. Since I don’t have that much experience with such things, it’s a lot of trial and error, as well as referencing far too many things at once. I decided to start by trying to make the power delivery circuit. I’m not certain it is correct, but an attempt was made.
I updated the power sheet a bit. Then I worked on one of the more complicated parts of this schematic design; the core sheet. It took a little while, but I think it works, so long as I do the other sheets right of course. I also began my main schematic diagram since I have more than one sheet, and you can see the single 3.3v line from the usb-c power sheet running to the core! I know, exciting stuff, right? Anyways, I have a ways to go before I can work on the actual pcb, and will likely be adding some features to make it different from a basic pico, otherwise there wouldn’t be much point!
I finished the USB data sheet. So now the board can actually send and receive data, which is rather important for a devboard. Lots of screenshots this time due to small changes to various parts of the schematic. Once I finish all the critical systems, I’ll add some of the things that will make it a bit different from a standard pico.
I finished the main schematic for the board by adding a status LED and setting up the IO pins. I think I might still add a few things before working on the PCB though. I’m considering extra flash memory and perhaps an inbuilt mic for some extra features. I may end up making some modules for this board later on. But here’s thee pictures!
Ok, so I’ve added an analog mic, as well as an extra 16 mb flash memory. So in theory you can store a decent amount of audio or whatever else on this thing. The mic won’t exactly be great quality, but it will work for general uses like sound activation. I’m tempted to add wifi, so I’m either going to do that next or start the PCB.
This one isn’t going to look like much progress per amount of time compared to the others, but here we go. I assigned pcb footprints to all my components. Then, I started on the pcb, only to realize that some of those footprints are a bit large for a 20 x 50 mm board. So after a lot of attempting to make it work, I finally changed to smaller resistor and capacitor footprints. I will also likely change my button and crystal footprints later, since they are a bit too large as well, but I’ll do that when I get to that part of the board. Anyway, I’m finished with the usb power and data parts of the pcb (for now) and have to do the main core and I/O next, which will likely be a pain, (Hence why my starting sections are so cramped) but I figured I should stop here to make a log. Hoping all goes well in the next steps!
I managed to hook up the power and usb data to the actual rp2354a chip, including both the 3.3 and 1.1v connections. It’s a bit messy, but it worked. I’m currently trying to figure out how to attach my extra flash memory, since that chip isn’t exactly tiny, and it still needs to reach the correct pins on the core. I’ll also have to leave room for GPIO wiring. But I’m still hoping it will continue to go fairly well.
I DID IT! I managed to route the entire PCB, and fit all the components. The only thing I had to cut was the I2C header. However, It’s still accessible on the GPIO (In the correct order and including the needed resistors) So you could directly connect a display to it. All that’s left to do before I ship is to check all my work and do some more friendly labeling! (And of course the GitHub repo)
I have completed my PCB checks and finished labeling the board. All that is left before shipping is to complete the GitHub page and actually ship!
Shipped! (At least until I have approval for funding) The Pendryx Pico is a rpi Pico-sized devboard with 28 GPIO pins, including I2C (In order), and a mic. It has 520 KB of ram, 18 MB of flash memory, and connects via USB-C!
I did some last-minute organization to correct a few messy traces on the PCB, but now that I have funding, I have ordered the components and will be building once they arrive.
Here’s an update since it’s been awhile. I have received all my parts. It took awhile since I accidentally ordered the wrong solder paste and had to wait to get the new one though. Anyway, I have assembled the board, accidentally put the LEDs on backwards, had to remove and reorient them, and now I’m debugging it to see what could be wrong with it. The power LED does turn on, but the board is not recognized, so I’m still looking into why. Here’s how it turned out though! (SMD soldering is fun!)...
|
1792774171.8277335
|
1793378971.8277335
|
|
17055
|
Student OS by @gavinkluch | Stardance
|
gavinkluch
|
0
|
1.84
|
0
|
[]
|
[{"post_id": 9034, "ts": "2026 [{"post_id": 9034, "ts": "2026-06-15T02:20:02Z", "hours": 1.8369, "text": "Today I started building StudentOS, a web-based OS to help students be more productive. My goal was to make a simple splash screen as well as a desktop page, both to look clean. I spent about 3 hours on this between actual coding and googling how to code. What I built: Splash screen fades in “StudentOS” and a loading message, then transitions to the desktop after a few seconds. The desktop has a macOS style dock and menu bar that both do absolutely nothing when you click them (for now). On hover, the top menu bar words have a gray background, while the doc icons scale up and present a title when you hover over those. Problems: More than I expected for two simple pages. My live preview in VS code kept showing “File not found”, which makes sense because I lost the file for a bit, plus I had to mess around with a bunch of different servers to get it working. Additionally, the splash page did NOT fade correctly the first few tries and I had to get some keyframes with opacity working to figure that out. Another problem I ran into was the desktop not coming in after any amount of time, and it turned out that the CSS rule I wrote for the text was accidentally making it all invisible. Lastly, the clock wasn’t updating because I had the interval logic messed up as well as in the wrong place. Next Up: Clickable app icons and draggable windows."}]...
|
Title: Student OS by @gavinkluch | Stardance
Devl Title: Student OS by @gavinkluch | Stardance
Devlogs:
Today I started building StudentOS, a web-based OS to help students be more productive. My goal was to make a simple splash screen as well as a desktop page, both to look clean. I spent about 3 hours on this between actual coding and googling how to code. What I built: Splash screen fades in “StudentOS” and a loading message, then transitions to the desktop after a few seconds. The desktop has a macOS style dock and menu bar that both do absolutely nothing when you click them (for now). On hover, the top menu bar words have a gray background, while the doc icons scale up and present a title when you hover over those. Problems: More than I expected for two simple pages. My live preview in VS code kept showing “File not found”, which makes sense because I lost the file for a bit, plus I had to mess around with a bunch of different servers to get it working. Additionally, the splash page did NOT fade correctly the first few tries and I had to get some keyframes with opacity working to figure that out. Another problem I ran into was the desktop not coming in after any amount of time, and it turned out that the CSS rule I wrote for the text was accidentally making it all invisible. Lastly, the clock wasn’t updating because I had the interval logic messed up as well as in the wrong place. Next Up: Clickable app icons and draggable windows....
|
1792774173.0222516
|
1793378973.0222516
|
|
18487
|
Untitled project by @ayansonthalia20 | Stardance
|
ayansonthalia20
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @ayansonthalia20 | Star Title: Untitled project by @ayansonthalia20 | Stardance...
|
1792774173.885447
|
1793378973.885447
|
|
4133
|
My awesome macropad! by @devesh | Stardance
|
devesh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @devesh | Stardance
|
1792774174.751155
|
1793378974.751155
|
|
34325
|
WarioWare Game by @Swanky | Stardance
|
Swanky
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @Swanky | Stardance
|
1792774175.5821626
|
1793378975.5821626
|
|
28787
|
REMail by @afonya | Stardance
|
afonya
|
0
|
13.9
|
0
|
[]
|
[{"post_id": 29140, "ts": "202 [{"post_id": 29140, "ts": "2026-07-15T20:32:55Z", "hours": 5.1406, "text": "So I started designing the main UI for REMail; however, I discovered that Lanterna (the TUI library I used) wasn’t the best for this because it couldn’t handle too many things on the screen. So I decided to switch to Compose Multiplatform. However, figuring out how to use Compose was a complete pain. The documentation is nowhere near friendly, not to mention that you have to go to the Google documentation. I actually don’t know how someone can look at it and say, “Oh yeah, this is fine.” Anyway, after a few hours of pain, I figured out how to use navigation, inputs, buttons, and alerts. Even though there aren’t any new features, at least the UI looks very good and friendly now. Also, don’t ask why the default primary color looks like that, but I figured that just changing that would take another 5 hours of researching."}, {"post_id": 27918, "ts": "2026-07-13T20:54:19Z", "hours": 5.1672, "text": "Made register and login actually work and go through. It uses Libsodium for cryptography. The way it works is it derives a key from the password using Argon2id and then derives 2 subkeys using KDF. 1 of the keys is used to seed a signature key (ed25519). The public key is shared with the server when one registers. When one wants to log in, they do the same process: ask the server for a challenge, sign the challenge, and send it back to the server. The server uses this to verify one’s password without having to send the password to the server. The other KDF subkey is then used to decrypt the master key, and the master key is used to decrypt the encryption and signature keys that will be used for email sending. This solution is not the greatest, because if the database gets leaked, it is possible to do an offline attack by computing the KDF subkeys for random passwords and see if any of them give a public key that’s in the database."}, {"post_id": 19541, "ts": "2026-06-30T21:18:06Z", "hours": 3.5928, "text": "The idea of REMail was in my head for 2 months; however, I didn’t really start working on it apart from figuring the design out. So now I decided to continue it. I began by making the registration. I also made a TUI client for it, which you can see below. It doesn’t do much yet; however, it can generate the keys and encrypt them like a password manager."}]...
|
Title: REMail by @afonya | Stardance
Devlogs:
The Title: REMail by @afonya | Stardance
Devlogs:
The idea of REMail was in my head for 2 months; however, I didn’t really start working on it apart from figuring the design out. So now I decided to continue it. I began by making the registration. I also made a TUI client for it, which you can see below. It doesn’t do much yet; however, it can generate the keys and encrypt them like a password manager.
Made register and login actually work and go through. It uses Libsodium for cryptography. The way it works is it derives a key from the password using Argon2id and then derives 2 subkeys using KDF. 1 of the keys is used to seed a signature key (ed25519). The public key is shared with the server when one registers. When one wants to log in, they do the same process: ask the server for a challenge, sign the challenge, and send it back to the server. The server uses this to verify one’s password without having to send the password to the server. The other KDF subkey is then used to decrypt the master key, and the master key is used to decrypt the encryption and signature keys that will be used for email sending. This solution is not the greatest, because if the database gets leaked, it is possible to do an offline attack by computing the KDF subkeys for random passwords and see if any of them give a public key that’s in the database.
So I started designing the main UI for REMail; however, I discovered that Lanterna (the TUI library I used) wasn’t the best for this because it couldn’t handle too many things on the screen. So I decided to switch to Compose Multiplatform. However, figuring out how to use Compose was a complete pain. The documentation is nowhere near friendly, not to mention that you have to go to the Google documentation. I actually don’t know how someone can look at it and say, “Oh yeah, this is fine.” Anyway, after a few hours of pain, I figured out how to use navigation, inputs, buttons, and alerts. Even though there aren’t any new features, at least the UI looks very good and friendly now. Also, don’t ask why the default primary color looks like that, but I figured that just changing that would take another 5 hours of researching....
|
1792774176.4292161
|
1793378976.4292161
|
|
35326
|
Untitled by @Prat | Stardance
|
Prat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Prat | Stardance
|
1792774177.2716112
|
1793378977.2716112
|
|
25015
|
Untitled by @shayan1 | Stardance
|
shayan1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @shayan1 | Stardance
|
1792774178.138286
|
1793378978.138286
|
|
24230
|
My very own WebOS by @Brayden_Devs | Stardance
|
Brayden_Devs
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Brayden_Devs | Starda Title: My very own WebOS by @Brayden_Devs | Stardance...
|
1792774178.9916272
|
1793378978.9916272
|
|
7202
|
Titanic Survival Predictor by @sinagdev | Stardanc Titanic Survival Predictor by @sinagdev | Stardance...
|
sinagdev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Titanic Survival Predictor by @sinagdev | S Title: Titanic Survival Predictor by @sinagdev | Stardance...
|
1792774179.8314419
|
1793378979.8314419
|
|
31374
|
My awesome macropad! by @dhruvbpatel | Stardance
|
dhruvbpatel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @dhruvbpatel | Star Title: My awesome macropad! by @dhruvbpatel | Stardance...
|
1792774180.6545444
|
1793378980.6545444
|
|
36866
|
Hi-car by @Ryan_Ng | Stardance
|
Ryan_Ng
|
0
|
12.19
|
0
|
[]
|
[{"post_id": 39813, "ts": "202 [{"post_id": 39813, "ts": "2026-08-03T01:40:27Z", "hours": 3.3983, "text": "Start making the v2"}, {"post_id": 39565, "ts": "2026-08-02T16:48:18Z", "hours": 0.3667, "text": "Sketching out V2 of my car almost done,added some wiring and the new design of the car"}, {"post_id": 39031, "ts": "2026-08-01T18:16:00Z", "hours": 1.3361, "text": "first time making schematic"}, {"post_id": 38641, "ts": "2026-08-01T04:26:37Z", "hours": 1.4669, "text": "ADDED RGB LIGHT on my car"}, {"post_id": 38410, "ts": "2026-07-31T19:21:04Z", "hours": 0.5075, "text": "Added audio to my car"}, {"post_id": 38373, "ts": "2026-07-31T18:33:47Z", "hours": 0.35, "text": "First time Soildering"}, {"post_id": 38203, "ts": "2026-07-31T14:30:37Z", "hours": 0.55, "text": "editing github (HI-car)"}, {"post_id": 38122, "ts": "2026-07-31T10:29:51Z", "hours": 1.5219, "text": "ESP32 cam on my HI-car added camera feature on my funny moving aaah car and i finally can deply my car on toilet hahahaha and it can see the surrounding make it easier to control yaaay"}, {"post_id": 38052, "ts": "2026-07-31T07:26:02Z", "hours": 2.6897, "text": "HI-car first build up items: -esp 32 -4 tt motor and wheels -motor module -two 18650 battery with the case -a mini oled screen -wires just build up and write the code,it can now move and sucessfully moving.still trying to add some features"}]...
|
Title: Hi-car by @Ryan_Ng | Stardance
Devlogs:
HI Title: Hi-car by @Ryan_Ng | Stardance
Devlogs:
HI-car first build up items: -esp 32 -4 tt motor and wheels -motor module -two 18650 battery with the case -a mini oled screen -wires just build up and write the code,it can now move and sucessfully moving.still trying to add some features
ESP32 cam on my HI-car added camera feature on my funny moving aaah car and i finally can deply my car on toilet hahahaha and it can see the surrounding make it easier to control yaaay
editing github (HI-car)
First time Soildering
Added audio to my car
ADDED RGB LIGHT on my car
first time making schematic
Sketching out V2 of my car almost done,added some wiring and the new design of the car
Start making the v2...
|
1792774181.5020158
|
1793378981.5020158
|
|
28674
|
Solgaleo Fursuit Screen by @Bagel | Stardance
|
Bagel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Solgaleo Fursuit Screen by @Bagel | Stardan Title: Solgaleo Fursuit Screen by @Bagel | Stardance...
|
1792774182.6356735
|
1793378982.6356735
|
|
14182
|
My first slack bot! by @90D09 | Stardance
|
90D09
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @90D09 | Stardance
|
1792774183.4992795
|
1793378983.4992795
|
|
1768
|
My awesome macropad! by @Aarjith | Stardance
|
Aarjith
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Aarjith | Stardanc Title: My awesome macropad! by @Aarjith | Stardance...
|
1792774184.3249278
|
1793378984.3249278
|
|
24930
|
WarioWare Game by @synameta | Stardance
|
synameta
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @synameta | Stardance
|
1792774185.1915212
|
1793378985.1915212
|
|
33254
|
Unity Porting by @Pari | Stardance
|
Pari
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Unity Porting by @Pari | Stardance
|
1792774186.0463536
|
1793378986.0463536
|
|
16283
|
Untitled project by @srinp131 | Stardance
|
srinp131
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @srinp131 | Stardance
|
1792774186.8728302
|
1793378986.8728302
|
|
5963
|
Custom Mouse by @neoskimmer | Stardance
|
neoskimmer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Custom Mouse by @neoskimmer | Stardance
|
1792774187.7129729
|
1793378987.7129729
|
|
12148
|
My awesome macropad! by @sami_bibs | Stardance
|
sami_bibs
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sami_bibs | Starda Title: My awesome macropad! by @sami_bibs | Stardance...
|
1792774188.5658326
|
1793378988.5658326
|
|
23473
|
Untitled project by @Cassiusdev | Stardance
|
Cassiusdev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Cassiusdev | Stardance
|
1792774189.431631
|
1793378989.431631
|
|
430
|
StarLinks by @Suryansh-Mishra | Stardance
|
Suryansh-Mishra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: StarLinks by @Suryansh-Mishra | Stardance
|
1792774190.2906423
|
1793378990.2906423
|
|
30734
|
My very own WebOS by @Lol123rl | Stardance
|
Lol123rl
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Lol123rl | Stardance
|
1792774191.135163
|
1793378991.135163
|
|
23915
|
My very own WebOS by @karmanyasangwan | Stardance
|
karmanyasangwan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @karmanyasangwan | Sta Title: My very own WebOS by @karmanyasangwan | Stardance...
|
1792774191.9871542
|
1793378991.9871542
|
|
15121
|
My awesome macropad! by @SpacerCoder | Stardance
|
SpacerCoder
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @SpacerCoder | Star Title: My awesome macropad! by @SpacerCoder | Stardance...
|
1792774193.041587
|
1793378993.041587
|
|
14776
|
My very own WebOS by @criver473 | Stardance
|
criver473
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @criver473 | Stardance
|
1792774193.9003487
|
1793378993.9003487
|
|
16951
|
First WebOS by @rehanmughal2008 | Stardance
|
rehanmughal2008
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: First WebOS by @rehanmughal2008 | Stardance
|
1792774194.7343202
|
1793378994.7343202
|
|
38026
|
My own site! by @adakesikbas | Stardance
|
adakesikbas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @adakesikbas | Stardance
|
1792774195.620565
|
1793378995.620565
|
|
2370
|
First Drone by @Aliexpress_enjoyer | Stardance
|
Aliexpress_enjoyer
|
0
|
45.82
|
0
|
[]
|
[{"post_id": 69505, "ts": "202 [{"post_id": 69505, "ts": "2026-09-17T06:19:48Z", "hours": 0.4597, "text": "Got a battery monitor working (it disarms the drone when the 3s lipo reaches 10v or below)"}, {"post_id": 68431, "ts": "2026-09-15T03:27:06Z", "hours": 2.4386, "text": "I was mostly working on code (its going horribly), but I soldered the battery connector along with a voltage measurement wire."}, {"post_id": 37991, "ts": "2026-07-31T02:46:42Z", "hours": 0.9169, "text": "Cadded a battery compartment in Autodesk Fusion"}, {"post_id": 37373, "ts": "2026-07-30T01:18:04Z", "hours": 1.0425, "text": "Added a calibration mode for easy esc tweaking, and the motor now uses 250hz I needed an input of some sort for calibrating, so I used the battery voltage pin as a temporary solution."}, {"post_id": 37294, "ts": "2026-07-29T22:01:39Z", "hours": 0.6047, "text": "made a custom quadcopter model in blender and added it to the web viewer!!"}, {"post_id": 37158, "ts": "2026-07-29T17:34:20Z", "hours": 3.9661, "text": "Learned threejs so that I could render a cube in the browser that rotates based on the flight controller’s orientation. While doing that, I got distracted and started playing the threejs port of doom for a bit. Anyway, it works really well Also, I suck at math This is a problem because I’m trying to write drone firmware from scratch. Fortunately, there are some pretty good guides out there like the one from Carbon Aeronautics. This session was mostly me trying to learn the math used to measure angles from the accelerometer and gyro. I get some of it, such as the basic trig stuff and integrating the gyro’s readings. I don’t get the more complex stuff like the Kalman Filter because sadly, I only posses 2nd year high school math knowledge. But mark my words, I WILL learn linear algebra and will understand it one day, maybe also what does stardance mean by “please write this yourself, humans can read it!,” right after I pasted in an IMAGE??"}, {"post_id": 36176, "ts": "2026-07-28T02:57:34Z", "hours": 2.8189, "text": "I modded my radio transmitter so it works with the current flight controller I also did some radio testing. I also tried playing around with FreeRTOS but I’m too dumb so I gave up Edit: Forgot to mention I created a holder for the flight controller"}, {"post_id": 32474, "ts": "2026-07-21T17:53:30Z", "hours": 10.6878, "text": "i did a high risk high reward type thing I paid 6 billion dollars to JLC for the flight controller, not even being fully sure if the flight controller would work. It arrived a week ago but I was dying at outpost so I haven’t tested until yesterday. I confirmed that the radio, imu, and motor pins work which are basically the most important parts of the FC"}, {"post_id": 12323, "ts": "2026-06-20T03:22:19Z", "hours": 1.3092, "text": "I’m finalizing the flight controller This means that I had to do a lot of double checking and random tweaks. I didn’t record it since I wasn’t very productive and essentially wasted an entire day half doom scrolling I did other miscellaneous things. Added a silkscreen Assembled part of the frame that arrived Wrote a BOM and tweaked stuff to appease JLCPCB"}, {"post_id": 10430, "ts": "2026-06-17T04:29:05Z", "hours": 0.5406, "text": "I fixed some DRC violations. Most of them were caused by me needing to shrink the default trace sizes for that one sensor. Four errors remain, which I likely won’t bother fixing since they’re just courtyard violations of the esp32s3’s antenna, which is not that integral to my project."}, {"post_id": 10387, "ts": "2026-06-17T02:15:18Z", "hours": 4.2706, "text": "Routed (most of) the Flight Controller. It may not look like much, but it was a lot of suffering. To start off, the magnetometer I’m using has the most annoying package I’ve encountered yet. There are pins buried deep inside the center of it, and I had to adjust trace and via sizes to accommodate for them. I ended up using the absolute minimum sizes that JLCPCB has to offer. Secondly, the radio module I’m using, which could not be moved or oriented differently, has a seriously unlucky pinout, and I ended up needing vias for almost every pin for it. Consequently, most other pins of the other sensors needed vias too, since they had to pass through or be connected to it. I ended up with the worst PCB layout I’ve ever seen. (To be fair, I haven’t seen many PCB layouts, so it probably isn’t as bad as I make it sound) I think it works though, I just need to spend like a day checking over it, and also route the remaining things, which are just ground planes, and power traces. I also cost optimized my board a little by reducing the assortment of header pins, so most of them will use the same parts, reducing JLC’s unique extended component fee. Here are some takeaways Don’t wire GND and power wires first, they have nonzero chances of needing to be moved later on, meaning you’ll have wasted your time JLCPCB allows smaller minimum trace sizes the more layers your boards have Never ever ever use WLCSP if you’re dumb like me There were probably more takeaways but I forgot"}, {"post_id": 9331, "ts": "2026-06-15T17:31:19Z", "hours": 1.9758, "text": "I did more component placing. I think it’s almost ready to route, but I want to make sure I didn’t make any mistakes, namely using a forbidden pin. I also did some component testing with the parts I already have, such as seeing if multiple motors could run at once, while the radio was transmitting, etc."}, {"post_id": 7781, "ts": "2026-06-13T00:10:19Z", "hours": 3.53, "text": "Before continuing with the PCB, I wanted to do a quick and stress free session where I tested firmware that would make the motors run. Safe to say, it was not quick and stress free. I initially tested the servo code on a mini mg90 servo since it was safer than testing with the esc which is powered by a big scary LiPo battery. I wasted 45 minutes with the firmware only to learn that the battery pack I used was drained. (All 4 AA batteries fell to 0.9v…) Then I managed to get the espservo library to work, but for some reason it kept crashing the entire code whenever I tried using pinMode(). I still don’t know why that happened. I switched to controlling the servo using the ledc api instead, which worked much better, and was quite fun to figure out. After succeeding in moving the mini servo, the ESC + motor gave me some issues. For safety purposes, ESCs have to be armed before they spin. To learn exactly how to calibrate it, I dug up a datasheet of the ESC, and finally got the ESC to spin the motor. Overall I learned: ESCs aren’t as dumb as I thought they were ledc api exists I still hate programming"}, {"post_id": 7011, "ts": "2026-06-11T19:21:35Z", "hours": 1.9411, "text": "I started working on component placements of the PCB. It was harder than I thought it would be. Firstly, I had over-estimated the size of flight controllers in general, so I had less space to work with as anticipated. Secondly, I forgot to add some decoupling capacitors in the schematic, so after doing so, I had much more components to wire. Thirdly, the connectors were bigger than I thought, especially the ones for the radio module I plan to attach to it. I’m still deciding some things, such as how big I want the board to be, (I’m thinking somewhere around 50x50mm, excluding the protruding antenna and usb port) and whether the PCB will be a 2 or 4 layer pcb."}, {"post_id": 6573, "ts": "2026-06-11T01:17:08Z", "hours": 0.7056, "text": "I assigned some footprints Not many interesting things happened, just mostly browsing LCSC and JLCPCB’s parts. I also spent some effort figuring out how to import footprints from componentsearchengine"}, {"post_id": 6553, "ts": "2026-06-11T00:23:09Z", "hours": 0.8667, "text": "I finished the schematic. I still have some warnings to fix, but I’ve reviewed the connections, and they seem correct. The current schematic has: An ESP32-S3 An IMU, which is the BMI270 + BMM150 Connectors for the ESC signals Extra GPIOs that are broken out A USB-C port A BMP338 barometer Some connectors for attaching the RF24s I have A connector for measuring battery voltage An LED :)"}, {"post_id": 6354, "ts": "2026-06-10T18:08:08Z", "hours": 3.1303, "text": "I hate working on the flight controller so I decided to work on something else instead. This is supposed to be a webpage that tests drone sensors where you can see the drone’s orientation in real time. I’ve been dying to try out the web serial api for a while now, but I never got to it. Fortunately, I finally got to use it to receive data from the microcontroller. I managed to make the webpage receive serial data from the receiver that I built in the last devlog."}, {"post_id": 5409, "ts": "2026-06-09T05:02:07Z", "hours": 1.6242, "text": "I took on a little sidequest from working on the schematic of the flight controller. I plan to use a set of nrf24l01’s as the radio, since I already have them. Therefore, I wanted to test them before putting it on the schematic. I hooked one up to a brand new esp32-s3, and the other to an esp32-wroom1. The process of sending data between each one was relatively straightforward, thanks to a helpful instructable I found. However, I did get some issues with the default SPI pins with the s3, but that got sorted out after some pin switching. Eventually I got the two devices to remotely talk to each other and was overjoyed. Also somewhere in between all of that, I realized I ran out of male to female jumper wires so that sucks :("}, {"post_id": 5300, "ts": "2026-06-09T00:55:22Z", "hours": 1.1764, "text": "I made some more progress on the flight controller. I may have forgotten some of what I did since the lapse was recorded like a day ago, but I added some connectors to the four escs, and connected most things to the main microcontroller."}, {"post_id": 3301, "ts": "2026-06-06T05:00:54Z", "hours": 1.81, "text": "I started researching/designing a custom flight controller! I began by choosing an IMU for it. I was initially going to use an MPU-6500, but learned it was trash for drones. I eventually settled on the BMI270 since it was relatively cheap but still powerful. Another benefit of that chip was that it could be hooked up to a magnetometer, so I looked into the BMM150, which was recommended. I also wasted my time with another random magnetometer that I keep forgetting the name of. Anyway I added those to the schematic, which wasn’t too bad. I’m pretty new to KiCad so I needed to figure out how to import symbols into it. I discovered the lifesaver known as the componentsearchengine, which is an extensive database of symbols that KiCad or other cad programs may not have. I also chose a microcontroller for the FC. I wanted to use an ESP32 chip since I’m most familiar with them, and ended up choosing an ESP32-S3 Wroom 1 (mostly arbitrarily)"}]...
|
Title: First Drone by @Aliexpress_enjoyer | Starda Title: First Drone by @Aliexpress_enjoyer | Stardance
Devlogs:
I started researching/designing a custom flight controller! I began by choosing an IMU for it. I was initially going to use an MPU-6500, but learned it was trash for drones. I eventually settled on the BMI270 since it was relatively cheap but still powerful. Another benefit of that chip was that it could be hooked up to a magnetometer, so I looked into the BMM150, which was recommended. I also wasted my time with another random magnetometer that I keep forgetting the name of. Anyway I added those to the schematic, which wasn’t too bad. I’m pretty new to KiCad so I needed to figure out how to import symbols into it. I discovered the lifesaver known as the componentsearchengine, which is an extensive database of symbols that KiCad or other cad programs may not have. I also chose a microcontroller for the FC. I wanted to use an ESP32 chip since I’m most familiar with them, and ended up choosing an ESP32-S3 Wroom 1 (mostly arbitrarily)
I made some more progress on the flight controller. I may have forgotten some of what I did since the lapse was recorded like a day ago, but I added some connectors to the four escs, and connected most things to the main microcontroller.
I took on a little sidequest from working on the schematic of the flight controller. I plan to use a set of nrf24l01’s as the radio, since I already have them. Therefore, I wanted to test them before putting it on the schematic. I hooked one up to a brand new esp32-s3, and the other to an esp32-wroom1. The process of sending data between each one was relatively straightforward, thanks to a helpful instructable I found. However, I did get some issues with the default SPI pins with the s3, but that got sorted out after some pin switching. Eventually I got the two devices to remotely talk to each other and was overjoyed. Also somewhere in between all of that, I realized I ran out of male to female jumper wires so that sucks :(
I hate working on the flight controller so I decided to work on something else instead. This is supposed to be a webpage that tests drone sensors where you can see the drone’s orientation in real time. I’ve been dying to try out the web serial api for a while now, but I never got to it. Fortunately, I finally got to use it to receive data from the microcontroller. I managed to make the webpage receive serial data from the receiver that I built in the last devlog.
I finished the schematic. I still have some warnings to fix, but I’ve reviewed the connections, and they seem correct. The current schematic has: An ESP32-S3 An IMU, which is the BMI270 + BMM150 Connectors for the ESC signals Extra GPIOs that are broken out A USB-C port A BMP338 barometer Some connectors for attaching the RF24s I have A connector for measuring battery voltage An LED :)
I assigned some footprints Not many interesting things happened, just mostly browsing LCSC and JLCPCB’s parts. I also spent some effort figuring out how to import footprints from componentsearchengine
I started working on component placements of the PCB. It was harder than I thought it would be. Firstly, I had over-estimated the size of flight controllers in general, so I had less space to work with as anticipated. Secondly, I forgot to add some decoupling capacitors in the schematic, so after doing so, I had much more components to wire. Thirdly, the connectors were bigger than I thought, especially the ones for the radio module I plan to attach to it. I’m still deciding some things, such as how big I want the board to be, (I’m thinking somewhere around 50x50mm, excluding the protruding antenna and usb port) and whether the PCB will be a 2 or 4 layer pcb.
Before continuing with the PCB, I wanted to do a quick and stress free session where I tested firmware that would make the motors run. Safe to say, it was not quick and stress free. I initially tested the servo code on a mini mg90 servo since it was safer than testing with the esc which is powered by a big scary LiPo battery. I wasted 45 minutes with the firmware only to learn that the battery pack I used was drained. (All 4 AA batteries fell to 0.9v…) Then I managed to get the espservo library to work, but for some reason it kept crashing the entire code whenever I tried using pinMode(). I still don’t know why that happened. I switched to controlling the servo using the ledc api instead, which worked much better, and was quite fun to figure out. After succeeding in moving the mini servo, the ESC + motor gave me some issues. For safety purposes, ESCs have to be armed before they spin. To learn exactly how to calibrate it, I dug up a datasheet of the ESC, and finally got the ESC to spin the motor. Overall I learned: ESCs aren’t as dumb as I thought they were ledc api exists I still hate programming
I did more component placing. I think it’s almost ready to route, but I want to make sure I didn’t make any mistakes, namely using a forbidden pin. I also did some component testing with the parts I already have, such as seeing if multiple motors could run at once, while the radio was transmitting, etc.
Routed (most of) the Flight Controller. It may not look like much, but it was a lot of suffering. To start off, the magnetometer I’m using has the most annoying package I’ve encountered yet. There are pins buried deep inside the center of it, and I had to adjust trace and via sizes to accommodate for them. I ended up using the absolute minimum sizes that JLCPCB has to offer. Secondly, the radio module I’m using, which could not be moved or oriented differently, has a seriously unlucky pinout, and I ended up needing vias for almost every pin for it. Consequently, most other pins of the other sensors needed vias too, since they had to pass through or be connected to it. I ended up with the worst PCB layout I’ve ever seen. (To be fair, I haven’t seen many PCB layouts, so it probably isn’t as bad as I make it sound) I think it works though, I just need to spend like a day checking over it, and also route the remaining things, which are just ground planes, and power traces. I also cost optimized my board a little by reducing the assortment of header pins, so most of them will use the same parts, reducing JLC’s unique extended component fee. Here are some takeaways Don’t wire GND and power wires first, they have nonzero chances of needing to be moved later on, meaning you’ll have wasted your time JLCPCB allows smaller minimum trace sizes the more layers your boards have Never ever ever use WLCSP if you’re dumb like me There were probably more takeaways but I forgot
I fixed some DRC violations. Most of them were caused by me needing to shrink the default trace sizes for that one sensor. Four errors remain, which I likely won’t bother fixing since they’re just courtyard violations of the esp32s3’s antenna, which is not that integral to my project.
I’m finalizing the flight controller This means that I had to do a lot of double checking and random tweaks. I didn’t record it since I wasn’t very productive and essentially wasted an entire day half doom scrolling I did other miscellaneous things. Added a silkscreen Assembled part of the frame that arrived Wrote a BOM and tweaked stuff to appease JLCPCB
i did a high risk high reward type thing I paid 6 billion dollars to JLC for the flight controller, not even being fully sure if the flight controller would work. It arrived a week ago but I was dying at outpost so I haven’t tested until yesterday. I confirmed that the radio, imu, and motor pins work which are basically the most important parts of the FC
I modded my radio transmitter so it works with the current flight controller I also did some radio testing. I also tried playing around with FreeRTOS but I’m too dumb so I gave up Edit: Forgot to mention I created a holder for the flight controller
Learned threejs so that I could render a cube in the browser that rotates based on the flight controller’s orientation. While doing that, I got distracted and started playing the threejs port of doom for a bit. Anyway, it works really well Also, I suck at math This is a problem because I’m trying to write drone firmware from scratch. Fortunately, there are some pretty good guides out there like the one from Carbon Aeronautics. This session was mostly me trying to learn the math used to measure angles from the accelerometer and gyro. I get some of it, such as the basic trig stuff and integrating the gyro’s readings. I don’t get the more complex stuff like the Kalman Filter because sadly, I only posses 2nd year high school math knowledge. But mark my words, I WILL learn linear algebra and will understand it one day, maybe also what does stardance mean by “please write this yourself, humans can read it!,” right after I pasted in an IMAGE??
made a custom quadcopter model in blender and added it to the web viewer!!
Added a calibration mode for easy esc tweaking, and the motor now uses 250hz I needed an input of some sort for calibrating, so I used the battery voltage pin as a temporary solution.
Cadded a battery compartment in Autodesk Fusion
I was mostly working on code (its going horribly), but I soldered the battery connector along with a voltage measurement wire.
Got a battery monitor working (it disarms the drone when the 3s lipo reaches 10v or below)...
|
1792774196.4867506
|
1793378996.4867506
|
|
33358
|
GCSE study space by @BIG_JO | Stardance
|
BIG_JO
|
0
|
6.91
|
0
|
[]
|
[{"post_id": 62341, "ts": "202 [{"post_id": 62341, "ts": "2026-09-05T17:43:59Z", "hours": 0.9758, "text": "kkk so i was trying to make a back end for my api recall but like it didnt work cause i remembered am using netifly so like if it was with vercel it would be easy but with netlify am using my actual github to deplay and it also makes thing so much easier so atp am leaving it in the frontend and hope nothing bad happens.. pls"}, {"post_id": 46933, "ts": "2026-08-14T14:28:15Z", "hours": 0.9642, "text": "i was trying to fix this mistake for a time that make that when i press the generate with ai(this is the feature in flashcard.html) it doesnt work and i realised the api key i wrote was actually not correct….yeah idk why how cause am pretty much sure i copy pasted it anyways now its fixed i might say and yeah. also i am just using the picture of the whole page cause idk what picture to use for this."}, {"post_id": 41995, "ts": "2026-08-06T15:13:19Z", "hours": 2.0306, "text": "so i changed the flahscard structure to make it look like that an it still cant do anything whan u click but i will soon work on that for now just dong a devlog."}, {"post_id": 31687, "ts": "2026-07-20T09:30:48Z", "hours": 2.9394, "text": "i was doing the flashcard today and i was able to make a good loocking structure even tho i was not able to make the buttons do anything for now i think ill use ai to help me make the AI generated flashcards work and am not sure on wich API to use but anyways am done for today and tomorow i think ill make the buttons do something when u press"}]...
|
Title: GCSE study space by @BIG_JO | Stardance
De Title: GCSE study space by @BIG_JO | Stardance
Devlogs:
i was doing the flashcard today and i was able to make a good loocking structure even tho i was not able to make the buttons do anything for now i think ill use ai to help me make the AI generated flashcards work and am not sure on wich API to use but anyways am done for today and tomorow i think ill make the buttons do something when u press
so i changed the flahscard structure to make it look like that an it still cant do anything whan u click but i will soon work on that for now just dong a devlog.
i was trying to fix this mistake for a time that make that when i press the generate with ai(this is the feature in flashcard.html) it doesnt work and i realised the api key i wrote was actually not correct….yeah idk why how cause am pretty much sure i copy pasted it anyways now its fixed i might say and yeah. also i am just using the picture of the whole page cause idk what picture to use for this.
kkk so i was trying to make a back end for my api recall but like it didnt work cause i remembered am using netifly so like if it was with vercel it would be easy but with netlify am using my actual github to deplay and it also makes thing so much easier so atp am leaving it in the frontend and hope nothing bad happens.. pls...
|
1792774198.2743573
|
1793378998.2743573
|
|
17894
|
Air Plane photographer by @jack_lacombe212 | Stard Air Plane photographer by @jack_lacombe212 | Stardance...
|
jack_lacombe212
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Air Plane photographer by @jack_lacombe212 Title: Air Plane photographer by @jack_lacombe212 | Stardance...
|
1792774199.1220627
|
1793378999.1220627
|
|
40304
|
Untitled by @VictorParacki | Stardance
|
VictorParacki
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @VictorParacki | Stardance
|
1792774199.9812071
|
1793378999.9812071
|
|
24504
|
My very own WebOS by @Smasher | Stardance
|
Smasher
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Smasher | Stardance
|
1792774200.824336
|
1793379000.824336
|
|
23865
|
Survey Vessel by @alexew0923 | Stardance
|
alexew0923
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Survey Vessel by @alexew0923 | Stardance
|
1792774201.6992383
|
1793379001.6992383
|
|
15727
|
Moon Photography Album by @isaiah-Halder | Stardan Moon Photography Album by @isaiah-Halder | Stardance...
|
isaiah-Halder
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Moon Photography Album by @isaiah-Halder | Title: Moon Photography Album by @isaiah-Halder | Stardance...
|
1792774202.5653687
|
1793379002.5653687
|
|
21154
|
My very own WebOS by @Neil_Kakad | Stardance
|
Neil_Kakad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Neil_Kakad | Stardanc Title: My very own WebOS by @Neil_Kakad | Stardance...
|
1792774205.9370174
|
1793379005.9370174
|
|
38564
|
My very own WebOS by @anirudh1mathur | Stardance
|
anirudh1mathur
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @anirudh1mathur | Star Title: My very own WebOS by @anirudh1mathur | Stardance...
|
1792774206.791143
|
1793379006.791143
|
|
16185
|
My very own WebOS by @marcusbauer77 | Stardance
|
marcusbauer77
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @marcusbauer77 | Stard Title: My very own WebOS by @marcusbauer77 | Stardance...
|
1792774207.6774414
|
1793379007.6774414
|
|
3925
|
AI Powered Criminal Activity Detection Through Sen AI Powered Criminal Activity Detection Through Sensor-less Sensing by @vvishal0507 | Stardance...
|
vvishal0507
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI Powered Criminal Activity Detection Thro Title: AI Powered Criminal Activity Detection Through Sensor-less Sensing by @vvishal0507 | Stardance...
|
1792774208.5548244
|
1793379008.5548244
|
|
15581
|
My very own WebOS by @connorlraines | Stardance
|
connorlraines
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @connorlraines | Stard Title: My very own WebOS by @connorlraines | Stardance...
|
1792774209.4003272
|
1793379009.4003272
|
|
17114
|
Blind os by @Ashir | Stardance
|
Ashir
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Blind os by @Ashir | Stardance
|
1792774210.2690136
|
1793379010.2690136
|
|
2141
|
My awesome macropad! by @kotosmiornica | Stardance
|
kotosmiornica
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @kotosmiornica | St Title: My awesome macropad! by @kotosmiornica | Stardance...
|
1792774211.1278462
|
1793379011.1278462
|
|
1349
|
My awesome macropad! by @Fiilzy | Stardance
|
Fiilzy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Fiilzy | Stardance
|
1792774211.9910858
|
1793379011.9910858
|
|
17547
|
My awesome macropad! by @Tanush_Chittem | Stardanc My awesome macropad! by @Tanush_Chittem | Stardance...
|
Tanush_Chittem
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Tanush_Chittem | S Title: My awesome macropad! by @Tanush_Chittem | Stardance...
|
1792774212.8307726
|
1793379012.8307726
|
|
15151
|
My very own WebOS by @Jhonnyby | Stardance
|
Jhonnyby
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Jhonnyby | Stardance
|
1792774213.6750495
|
1793379013.6750495
|
|
38123
|
NOVA - an AI assistant/Camera by @Mazin_Kornijenko NOVA - an AI assistant/Camera by @Mazin_Kornijenko | Stardance...
|
Mazin_Kornijenko
|
0
|
1.25
|
0
|
[]
|
[{"post_id": 34327, "ts": "202 [{"post_id": 34327, "ts": "2026-07-24T22:48:52Z", "hours": 0.3333, "text": "Further expanded by design"}, {"post_id": 34305, "ts": "2026-07-24T21:53:16Z", "hours": 0.9206, "text": "New AI Camera Design This will help my AI with face recognition and other features!"}]...
|
Title: NOVA - an AI assistant/Camera by @Mazin_Kor Title: NOVA - an AI assistant/Camera by @Mazin_Kornijenko | Stardance
Devlogs:
New AI Camera Design This will help my AI with face recognition and other features!
Further expanded by design...
|
1792774214.5092032
|
1793379014.5092032
|