|
3096
|
My awesome macropad! by @stefche | Stardance
|
stefche
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stefche | Stardanc Title: My awesome macropad! by @stefche | Stardance...
|
1793339466.6777081
|
1793944266.6777081
|
|
37162
|
My own site! by @stefanstefanowicz25 | Stardance
|
stefanstefanowicz25
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @stefanstefanowicz25 | Star Title: My own site! by @stefanstefanowicz25 | Stardance...
|
1793811013.910873
|
1794415813.910873
|
|
37194
|
Untitled by @stefanstefanowicz25 | Stardance
|
stefanstefanowicz25
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @stefanstefanowicz25 | Stardanc Title: Untitled by @stefanstefanowicz25 | Stardance...
|
1793865074.0936253
|
1794469874.0936253
|
|
64106
|
My own site! by @stefanpopovski88 | Stardance
|
stefanpopovski88
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @stefanpopovski88 | Stardan Title: My own site! by @stefanpopovski88 | Stardance...
|
1793670440.7526393
|
1794275240.7526393
|
|
2336
|
My awesome macropad! by @stefanpantalir | Stardanc My awesome macropad! by @stefanpantalir | Stardance...
|
stefanpantalir
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stefanpantalir | S Title: My awesome macropad! by @stefanpantalir | Stardance...
|
1793353819.8301423
|
1793958619.8301423
|
|
60634
|
My own site! by @stefanellinicolas72 | Stardance
|
stefanellinicolas72
|
1
|
0.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-14T14:19:06Z", "hours": 0.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "i made a custom website about myself. it’s not very pretty but i’m not good at coding so it was kinda hard", "repo": "https://github.com/stefanellinicolas72-glitch/my-website-", "demo": "https://stefanellinicolas72-glitch.github.io/my-website-/"}]...
|
[{"post_id": 65561, "ts": "202 [{"post_id": 65561, "ts": "2026-09-10T19:39:03Z", "hours": 0.3806, "text": "a simple page that tells about me"}]...
|
Title: My own site! by @stefanellinicolas72 | Star Title: My own site! by @stefanellinicolas72 | Stardance
Devlogs:
a simple page that tells about me
Ships:
i made a custom website about myself. it’s not very pretty but i’m not good at coding so it was kinda hard...
|
1793825634.4163685
|
1793912034.4163685
|
|
64881
|
my new website by @stefanellinicolas72 | Stardance
|
stefanellinicolas72
|
1
|
0.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-22T19:11:49Z", "hours": 0.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "i made a website that tellls about me, it explains my hobbies and who i am. it wasn’t that challenging to make, since i watched many, and i mean MANY youtube videos to try and make something beautiful!", "repo": "https://github.com/stefanellinicolas72-glitch/my-website-2", "demo": "https://stefanellinicolas72-glitch.github.io/my-website-2/"}]...
|
[{"post_id": 72361, "ts": "202 [{"post_id": 72361, "ts": "2026-09-22T19:08:35Z", "hours": 0.4856, "text": "a website about me. my portfolio"}]...
|
Title: my new website by @stefanellinicolas72 | St Title: my new website by @stefanellinicolas72 | Stardance
Devlogs:
a website about me. my portfolio
Ships:
i made a website that tellls about me, it explains my hobbies and who i am. it wasn’t that challenging to make, since i watched many, and i mean MANY youtube videos to try and make something beautiful!...
|
1793836207.63738
|
1793922607.63738
|
|
66284
|
My awesome macropad! by @stefanakosxrhstos | Stard My awesome macropad! by @stefanakosxrhstos | Stardance...
|
stefanakosxrhstos
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stefanakosxrhstos Title: My awesome macropad! by @stefanakosxrhstos | Stardance...
|
1793717278.7971153
|
1794322078.7971153
|
|
67131
|
Walk by @stefan_iftode | Stardance
|
stefan_iftode
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Walk by @stefan_iftode | Stardance
|
1793728318.4467988
|
1794333118.4467988
|
|
67266
|
My first slack bot! by @stefa | Stardance
|
stefa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @stefa | Stardance
|
1793728590.0597208
|
1794333390.0597208
|
|
33672
|
My own site! by @stef | Stardance
|
stef
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @stef | Stardance
|
1793300120.4325507
|
1793904920.4325507
|
|
33677
|
My very own WebOS by @stef | Stardance
|
stef
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @stef | Stardance
|
1793797056.0458531
|
1794401856.0458531
|
|
53460
|
The magic wand by @stef | Stardance
|
stef
|
0
|
0.3
|
0
|
[]
|
[{"post_id": 53684, "ts": "202 [{"post_id": 53684, "ts": "2026-08-24T11:10:32Z", "hours": 0.3003, "text": "I made a drawing on how would i like it to look + list of parts"}]...
|
Title: The magic wand by @stef | Stardance
Devlog Title: The magic wand by @stef | Stardance
Devlogs:
I made a drawing on how would i like it to look + list of parts...
|
1793490486.8128135
|
1794095286.8128135
|
|
45056
|
Fries building machine by @steep-wagon-silo | Star Fries building machine by @steep-wagon-silo | Stardance...
|
steep-wagon-silo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fries building machine by @steep-wagon-silo Title: Fries building machine by @steep-wagon-silo | Stardance...
|
1793310995.4079378
|
1793915795.4079378
|
|
7323
|
My awesome macropad! by @steelvult19 | Stardance
|
steelvult19
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @steelvult19 | Star Title: My awesome macropad! by @steelvult19 | Stardance...
|
1793775048.9926977
|
1794379848.9926977
|
|
18940
|
educaxia by @steeeeven | Stardance
|
steeeeven
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: educaxia by @steeeeven | Stardance
|
1793303723.9362264
|
1793908523.9362264
|
|
33306
|
Stenography keyboard by @stayawaynoobs | Stardance
|
stayawaynoobs
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Stenography keyboard by @stayawaynoobs | St Title: Stenography keyboard by @stayawaynoobs | Stardance...
|
1793872108.040196
|
1794476908.040196
|
|
55487
|
Warrior IQ by @stavrou | Stardance
|
stavrou
|
1
|
1.47
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-29T12:19:01Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I built Warrior IQ, an AI-powered combat sports analysis website that analyzes fight footage and tracks actions such as punches, kicks, landed shots, misses, blocks, and evasions. It also creates fight statistics and performance feedback. The most challenging part was making the analysis work reliably with real fight footage and connecting the AI/video processing to the website without making everything too slow. I’m proud that I turned it into a real working web app that people can actually open online instead of only running it locally on my computer. To test it, open the demo, upload a fight video, choose the fighters/settings, and start an analysis. Some AI analysis features may take a while because the public demo is running on limited hosting resources.", "repo": "https://github.com/stavroutheo50/WarriorIQ", "demo": "https://warrioriq.eu"}]...
|
[{"post_id": 57309, "ts": "202 [{"post_id": 57309, "ts": "2026-08-29T12:56:45Z", "hours": 0.4703, "text": "Trying to fix a bug on the Fighter Selection tab with almighty Codex"}, {"post_id": 57215, "ts": "2026-08-29T10:02:04Z", "hours": 1.2064, "text": "Trying to upgarde the UI and maybe redesigning the whole website"}]...
|
Title: Warrior IQ by @stavrou | Stardance
Devlogs Title: Warrior IQ by @stavrou | Stardance
Devlogs:
Trying to upgarde the UI and maybe redesigning the whole website
Trying to fix a bug on the Fighter Selection tab with almighty Codex
Ships:
I built Warrior IQ, an AI-powered combat sports analysis website that analyzes fight footage and tracks actions such as punches, kicks, landed shots, misses, blocks, and evasions. It also creates fight statistics and performance feedback. The most challenging part was making the analysis work reliably with real fight footage and connecting the AI/video processing to the website without making everything too slow. I’m proud that I turned it into a real working web app that people can actually open online instead of only running it locally on my computer. To test it, open the demo, upload a fight video, choose the fighters/settings, and start an analysis. Some AI analysis features may take a while because the public demo is running on limited hosting resources....
|
1793955291.254995
|
1794041691.254995
|
|
36310
|
Puta by @staumi_waser | Stardance
|
staumi_waser
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Puta by @staumi_waser | Stardance
|
1793360884.0310295
|
1793965684.0310295
|
|
40426
|
trailhead by @staticiize | Stardance
|
staticiize
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: trailhead by @staticiize | Stardance
|
1793271216.9286807
|
1793876016.9286807
|
|
39847
|
My very own WebOS by @static_noise | Stardance
|
static_noise
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @static_noise | Starda Title: My very own WebOS by @static_noise | Stardance...
|
1793908396.1760025
|
1794772396.1760025
|
|
40228
|
lstc by @static_noise | Stardance
|
static_noise
|
0
|
63.7
|
0
|
[]
|
[{"post_id": 74474, "ts": "202 [{"post_id": 74474, "ts": "2026-09-27T13:40:25Z", "hours": 4.2642, "text": "finished lexer YAY!!! so, lexer is done, one out of several parts of the compiler… used example for parsing: fn XD() -> none { return; } lexer works as intended, which is good, now I will have to write a parser for the lexer output, btw, I will not use AST, in my plans is to use 4 stages of IR to provide faster compiler speed (also, way less memory hungry because AST nodes are big, linear IR is slim), and, I will not use LLVM cuz of lack of control and always changing API"}, {"post_id": 73645, "ts": "2026-09-25T15:56:53Z", "hours": 25.3197, "text": "BRUH, I’m stuck on lexer, fking lexer, I have to do it, but somewhy I can’t, I need to finish it, I NEED TO FINISH IT, FINISH IT, also switched to nvim XD"}, {"post_id": 54034, "ts": "2026-08-24T19:48:51Z", "hours": 9.7186, "text": "fuck fuck fuck, I tried writing a lexer, this… piece of - code - doesn’t wanna work, gotta rewrite it (yes, I barely ever publish devblogs, this is why its near 10 hours)"}, {"post_id": 49865, "ts": "2026-08-18T20:19:28Z", "hours": 12.115, "text": "working on primitives, changed plans (now I won’t try to make the compiler super good from the start, just a carry to bootstrap) and so on"}, {"post_id": 37789, "ts": "2026-07-30T18:34:52Z", "hours": 2.5086, "text": "still stuck on asm, but finished more shit (I achieved independence from libc, still better than C++) overall cool, but should finish and pack up with the library and start lexer"}, {"post_id": 36956, "ts": "2026-07-29T11:30:11Z", "hours": 5.6811, "text": "went a bit crazy with primitives and asm (still working on them, but they’re starting to get shape, most still just stubs)"}, {"post_id": 36282, "ts": "2026-07-28T09:00:19Z", "hours": 1.5514, "text": "Tried to fix a bug, couldn’t, fuck C++, gonna try and rewrite everything in C (P.S. C++ is a pile of shitty compromises)"}, {"post_id": 35830, "ts": "2026-07-27T14:54:50Z", "hours": 2.1919, "text": "Added path expansion"}, {"post_id": 35315, "ts": "2026-07-26T17:12:29Z", "hours": 0.3506, "text": "starting project architecture and execution"}]...
|
Title: lstc by @static_noise | Stardance
Devlogs: Title: lstc by @static_noise | Stardance
Devlogs:
starting project architecture and execution
Added path expansion
Tried to fix a bug, couldn’t, fuck C++, gonna try and rewrite everything in C (P.S. C++ is a pile of shitty compromises)
went a bit crazy with primitives and asm (still working on them, but they’re starting to get shape, most still just stubs)
still stuck on asm, but finished more shit (I achieved independence from libc, still better than C++) overall cool, but should finish and pack up with the library and start lexer
working on primitives, changed plans (now I won’t try to make the compiler super good from the start, just a carry to bootstrap) and so on
fuck fuck fuck, I tried writing a lexer, this… piece of - code - doesn’t wanna work, gotta rewrite it (yes, I barely ever publish devblogs, this is why its near 10 hours)
BRUH, I’m stuck on lexer, fking lexer, I have to do it, but somewhy I can’t, I need to finish it, I NEED TO FINISH IT, FINISH IT, also switched to nvim XD
finished lexer YAY!!! so, lexer is done, one out of several parts of the compiler… used example for parsing: fn XD() -> none { return; } lexer works as intended, which is good, now I will have to write a parser for the lexer output, btw, I will not use AST, in my plans is to use 4 stages of IR to provide faster compiler speed (also, way less memory hungry because AST nodes are big, linear IR is slim), and, I will not use LLVM cuz of lack of control and always changing API...
|
1793407702.1137624
|
1794012502.1137624
|
|
40710
|
StatSbot by @static_noise | Stardance
|
static_noise
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-27T19:34:00Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "some random bot, nothing to be proud of", "repo": "https://github.com/TheStaticNoise/StatSbot", "demo": "https://staticssht.slack.com/archives/C0BM2FVC4PN"}]...
|
[{"post_id": 35975, "ts": "202 [{"post_id": 35975, "ts": "2026-07-27T19:28:20Z", "hours": 0.9989, "text": "generally done XD (almost the entire token)"}]...
|
Title: StatSbot by @static_noise | Stardance
Devl Title: StatSbot by @static_noise | Stardance
Devlogs:
generally done XD (almost the entire token)
Ships:
some random bot, nothing to be proud of...
|
1793890266.861283
|
1793976666.861283
|
|
43183
|
tome by @static_noise | Stardance
|
static_noise
|
0
|
2.0
|
0
|
[]
|
[{"post_id": 42873, "ts": "202 [{"post_id": 42873, "ts": "2026-08-07T20:38:04Z", "hours": 1.4722, "text": "shaping the project, burned out"}, {"post_id": 39661, "ts": "2026-08-02T19:47:28Z", "hours": 0.5311, "text": "Started work on TOME, so, tome is designed to be easily embeddable (because I literally saw how shitty toml++ is to embed) and being easy to write and read"}]...
|
Title: tome by @static_noise | Stardance
Devlogs: Title: tome by @static_noise | Stardance
Devlogs:
Started work on TOME, so, tome is designed to be easily embeddable (because I literally saw how shitty toml++ is to embed) and being easy to write and read
shaping the project, burned out...
|
1793944138.9446461
|
1794548938.9446461
|
|
43795
|
WL Engine by @static_noise | Stardance
|
static_noise
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WL Engine by @static_noise | Stardance
|
1793238565.4845653
|
1793843365.4845653
|
|
51129
|
Silverflame - TVC propulsively landing rocket by @ Silverflame - TVC propulsively landing rocket by @staspomortsev | Stardance...
|
staspomortsev
|
0
|
65.47
|
0
|
[]
|
[{"post_id": 78259, "ts": "202 [{"post_id": 78259, "ts": "2026-10-10T05:56:56Z", "hours": 3.9631, "text": "I have finished on the rocket and I submitted for funding I don’t really know how to make logos so I just threw up something together, and I guess it’s fine. I also made the BOM (Bill Of materials) you can also check out my project on https://github.com/CloudStas/Propulsively-Landing-Model-Rocket"}, {"post_id": 76250, "ts": "2026-10-02T21:28:25Z", "hours": 2.7197, "text": "I finally finished my PCB costs about $30 on JLCPCB: this pcb has an ESP32 for control and powers from a 2s lipo battery 2200mah and powers 4x KST x08 v6 servos for XY control and throttle control and a usb port for debugging and 2x Igniters for 2x Estes F15 motors and 1x for releasing landing legs, almost done with the rocket."}, {"post_id": 74984, "ts": "2026-09-28T19:32:11Z", "hours": 6.7669, "text": "I am basically finished with the Landing legs for my TVC rocket and I just have to finish my PCB since the deadline got expanded to oct 31st so I have enough time. I might make a reaction wheel since I have enough time. I might also make a reaction wheel for stabilizing rocket’s roll. I am excited for launch."}, {"post_id": 70018, "ts": "2026-09-18T09:01:41Z", "hours": 4.7772, "text": "I thought of finishing the PCB but realized that it would take a few weeks for it to be made so instead i decided to daisy chain everything and I also designed an Avionics Bay that holds 2 computers(1x Raspberry Pi 3 Model A+ that is connected to a camera, and 1x ESP32-S3) and the ESP can send signals to ignite rocket engines or deploy landing legs. I also made a spreadsheet for all the parts and here is how the Avionics Bay and the BOM(Bill Of Materials) looks like: Also here is the BOM Link: https://docs.google.com/spreadsheets/d/1w17DnCs4J0WBasmAesTz5ANlNJR9XYsVwglhH3W97UI/edit?pli=1&gid=0#gid=0 Total Cost for the Electronics is The materials without 3d printing which is the final step is $482.35, I am going to later try to optimize the cost but for now I need to finish designing the rocket and then I will."}, {"post_id": 69129, "ts": "2026-09-16T13:13:59Z", "hours": 10.6092, "text": "I finally finished the TVC mount with throttle arms. And it supports 2 rocket motors and it can gimbal in all directions 5 degrees, I am basically done with the one of the hart parts. Up next I am going to redesign the flight computer PCB."}, {"post_id": 65323, "ts": "2026-09-10T12:17:26Z", "hours": 7.7383, "text": "I am redesigning the TVC mount with a better one so it can move better on it’s X/Y axis and also to be smaller. I still need to do the throttle arms and before that also need to figure out how to make it smaller to fit in something like a 74mm OD(Outer Diameter) tube or similar."}, {"post_id": 64071, "ts": "2026-09-08T06:45:20Z", "hours": 7.9139, "text": "I was designing my PCB but I decided to not make my own pcb and instead just use a Pi zero 2w and a teensy 4.1 with seperate igniters and servo/motor power connections. So now I am going to be designing an avionics bay in onshape to hold the computers and all the electronics. Edit: I am going to finish the pcb I am just going to finish the rocket design first."}, {"post_id": 58492, "ts": "2026-08-30T22:13:21Z", "hours": 11.015, "text": "Right now I am almost finished with the flight computer I spent most of the time fixing issues. And once I am finished I will post the BOM and add it to my github repo. Here are some features of the flight computer: The main CPU will be the ESP32-S3 and it will power 4x DC motors, 2x of them for YAW and PITCH and 2x more will be for the throttle arms, and lastly a dc motor for a reaction wheel to stabilize the rocket’s roll."}, {"post_id": 54628, "ts": "2026-08-25T17:31:07Z", "hours": 9.9667, "text": "There are a lot of parts for a Propulsively Landing Model Rocket, and I finished 1 one them which is Designing the TVC Mount. TVC or Thrust Vector Control is for gimbaling the rocket motor so the rocket can go upward straight. The Mount can also hold 2 motors one for ascent and another one for landing. Once the Landing motor burns out it literally just gets jettisoned and it falls out as the landing motor inside the tube ignites and the throttle arms are originally open but the throttle arms can be commanded by the flight computer to throttle down when needed. When the rocket gets closer to the ground it can throttle down more so it can become slower and slower until the legs touchdown on the ground. Right now I am currently designing the flight computer which is my first PCB and then I will make a mount for the rocket to hold the computer and the battery. After the Flight Computer is done I will work on the Reaction Wheel to Stabilize the rocket’s roll, and the airframe of the rocket which is simple, it’s just cardboard. And the final hardware design step is to design the landing legs which will be most likely to be made out of carbon fiber with a toy dampener. The way the legs work is kind of simple, they just have a nichrome wire on top of the legs, when the electrical current gets sent thru the wire it burns up and the legs can get out and click in so they are ready for impact. My Mount btw uses plastic + ceramic throttle arms and 4x Genuine MG90s servo’s. That said, Here is my TVC Mount: You can also check out the project on Github: https://github.com/CloudStas/Propulsively-Landing-Model-Rocket"}]...
|
Title: Silverflame - TVC propulsively landing rock Title: Silverflame - TVC propulsively landing rocket by @staspomortsev | Stardance
Devlogs:
There are a lot of parts for a Propulsively Landing Model Rocket, and I finished 1 one them which is Designing the TVC Mount. TVC or Thrust Vector Control is for gimbaling the rocket motor so the rocket can go upward straight. The Mount can also hold 2 motors one for ascent and another one for landing. Once the Landing motor burns out it literally just gets jettisoned and it falls out as the landing motor inside the tube ignites and the throttle arms are originally open but the throttle arms can be commanded by the flight computer to throttle down when needed. When the rocket gets closer to the ground it can throttle down more so it can become slower and slower until the legs touchdown on the ground. Right now I am currently designing the flight computer which is my first PCB and then I will make a mount for the rocket to hold the computer and the battery. After the Flight Computer is done I will work on the Reaction Wheel to Stabilize the rocket’s roll, and the airframe of the rocket which is simple, it’s just cardboard. And the final hardware design step is to design the landing legs which will be most likely to be made out of carbon fiber with a toy dampener. The way the legs work is kind of simple, they just have a nichrome wire on top of the legs, when the electrical current gets sent thru the wire it burns up and the legs can get out and click in so they are ready for impact. My Mount btw uses plastic + ceramic throttle arms and 4x Genuine MG90s servo’s. That said, Here is my TVC Mount: You can also check out the project on Github: https://github.com/CloudStas/Propulsively-Landing-Model-Rocket
Right now I am almost finished with the flight computer I spent most of the time fixing issues. And once I am finished I will post the BOM and add it to my github repo. Here are some features of the flight computer: The main CPU will be the ESP32-S3 and it will power 4x DC motors, 2x of them for YAW and PITCH and 2x more will be for the throttle arms, and lastly a dc motor for a reaction wheel to stabilize the rocket’s roll.
I was designing my PCB but I decided to not make my own pcb and instead just use a Pi zero 2w and a teensy 4.1 with seperate igniters and servo/motor power connections. So now I am going to be designing an avionics bay in onshape to hold the computers and all the electronics. Edit: I am going to finish the pcb I am just going to finish the rocket design first.
I am redesigning the TVC mount with a better one so it can move better on it’s X/Y axis and also to be smaller. I still need to do the throttle arms and before that also need to figure out how to make it smaller to fit in something like a 74mm OD(Outer Diameter) tube or similar.
I finally finished the TVC mount with throttle arms. And it supports 2 rocket motors and it can gimbal in all directions 5 degrees, I am basically done with the one of the hart parts. Up next I am going to redesign the flight computer PCB.
I thought of finishing the PCB but realized that it would take a few weeks for it to be made so instead i decided to daisy chain everything and I also designed an Avionics Bay that holds 2 computers(1x Raspberry Pi 3 Model A+ that is connected to a camera, and 1x ESP32-S3) and the ESP can send signals to ignite rocket engines or deploy landing legs. I also made a spreadsheet for all the parts and here is how the Avionics Bay and the BOM(Bill Of Materials) looks like: Also here is the BOM Link: https://docs.google.com/spreadsheets/d/1w17DnCs4J0WBasmAesTz5ANlNJR9XYsVwglhH3W97UI/edit?pli=1&gid=0#gid=0 Total Cost for the Electronics is The materials without 3d printing which is the final step is $482.35, I am going to later try to optimize the cost but for now I need to finish designing the rocket and then I will.
I am basically finished with the Landing legs for my TVC rocket and I just have to finish my PCB since the deadline got expanded to oct 31st so I have enough time. I might make a reaction wheel since I have enough time. I might also make a reaction wheel for stabilizing rocket’s roll. I am excited for launch.
I finally finished my PCB costs about $30 on JLCPCB: this pcb has an ESP32 for control and powers from a 2s lipo battery 2200mah and powers 4x KST x08 v6 servos for XY control and throttle control and a usb port for debugging and 2x Igniters for 2x Estes F15 motors and 1x for releasing landing legs, almost done with the rocket.
I have finished on the rocket and I submitted for funding I don’t really know how to make logos so I just threw up something together, and I guess it’s fine. I also made the BOM (Bill Of materials) you can also check out my project on https://github.com/CloudStas/Propulsively-Landing-Model-Rocket...
|
1793378943.7756124
|
1793983743.7756124
|
|
69576
|
Supersonic_rocket by @staspomortsev | Stardance
|
staspomortsev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Supersonic_rocket by @staspomortsev | Stard Title: Supersonic_rocket by @staspomortsev | Stardance...
|
1793735748.4589927
|
1794599748.4589927
|
|
71547
|
Supersonic-rocket by @staspomortsev | Stardance
|
staspomortsev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Supersonic-rocket by @staspomortsev | Stard Title: Supersonic-rocket by @staspomortsev | Stardance...
|
1793681243.760377
|
1794545243.760377
|
|
17000
|
Opening Knowledge by @stashm10 | Stardance
|
stashm10
|
1
|
6.24
|
38
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-17T04:53:37Z", "hours": 2.0, "multiplier": 17.21, "payout": 38, "blessing": "neutral", "text": "I made a fun chess game, specifically, a chess opening game, Chession. How it works is simple. A position from a famous chess opening is shown on the board, and you have to guess which opening it is. The opening is selected from a list of 25, and the board renders the position after move 10 (20 plies). You type a guess or pick from a list that filters as you type. If your guess is wrong, the board steps back two plies (one full move) and shows an earlier position as a hint. You get 5 guesses total. Each wrong guess reveals more of the position’s history, making the next guess easier. The cool part is that there are so many openings (well, 25 for now), so you can have multiple attempts. Unlike Wordle or other guessing games, you dont have to wait 24 hours to play. It was difficult setting up the chess board, the pieces, and piece animation, however I made it work. The trickiest part was animating between positions when going back, since each wrong guess jumps the board back two plies rather than one. I solved this by stepping through each half-move individually and animating the piece slide for every step, rather than animating directly from the start position to the end position. This keeps the motion readable even when skipping multiple moves. I hope in the future I can add more openings, and vartions of popular openings, that way I can make it more difficult :) The idea is just a simple game for all types of chess players, a chess version of Wordle… if that makes sense. Enjoy!", "repo": "https://github.com/stashm10/Chession", "demo": "https://stashm10.github.io/Chession/"}]...
|
[{"post_id": 12946, "ts": "202 [{"post_id": 12946, "ts": "2026-06-21T05:51:25Z", "hours": 4.2428, "text": "Devlog#2 I decided to add some more features to make this game more accessible. The main feature that I added was a difficulty section. How it works: After selecting “let’s play” you get the option to pick the “normal” or “grandmaster” difficulty. You can easily tell that the grandmaster difficulty is the harder one by the intimidating cartoon picture next to it (I did use AI to make that since I am not good at drawing). As the game grew, I noticed that chess puzzles and openings can be incredibly brutal if you do not know the exact lines, which often leads to quick frustration. On the flip side, making the game universally easier takes away the competitive edge that chess veterans look for. I wanted to bridge this gap so casual players can learn without getting punished immediately while hardcore players can still experience a strict challenge. Grandmaster mode offers the classic, strict experience with standard guess limits and only allows you to step two moves back on your final guess to try and correct your line. To make things more forgiving, Normal mode adds an extra lifeline giving you one more guess than usual, and it allows a deeper lookback of four moves instead of two on your final guess. This extra context helps players re-visualize where their theory went wrong and successfully find the right continuation. Looking ahead, now that the core difficulty framework is in place, I am focusing on content depth and progression. First, I plan to significantly expand the library of chess openings and variations. To balance out the difficulty, I might limit the pool of openings in Normal mode to more common, foundational lines while increasing them in the Grandmaster section to unleash rare, highly theoretical variations that require deep knowledge. I am also looking into implementing a login system to keep track of progress, save personal stats, and track which openings players have mastered. Along with user accounts, I want to introduce a potential leaderboard so players can see how their scores stack up against the rest of the community. The update is live right now, so please try it out for yourself and and let me know if you have any questions or feedback."}, {"post_id": 10425, "ts": "2026-06-17T04:09:17Z", "hours": 2.2156, "text": "Chession Devlog #1 I built a chess opening guessing game. The idea: a position from a famous chess opening is shown on the board, and you have to guess which opening it is. How it works A random opening is selected from a list of 25, and the board renders the position after move 10 (20 plies). You type a guess or pick from a list that filters as you type. If your guess is wrong, the board steps back one move (one move for black and one move for white) and shows an earlier position as a hint. You get 5 guesses total. Each wrong guess reveals more of the position’s history, making the next guess easier. What I’ve built so far Static board rendering using FEN-style positions generated from chess.js Move validation and position-building logic using chess.js -An animated piece-slide transition when navigating between hint positions, instead of just snapping Autocomplete with keyboard navigation (arrow keys, enter to select) -A guess history display showing correct/wrong attempts -Navigation buttons (and arrow keys) to move between all hint positions you’ve unlocked, not just the latest one -A welcome modal explaining the rules A reload-confirmation dialog so accidental refreshes don’t wipe progress mid-game Animating the hints The trickiest part was animating between positions when going back, since each wrong guess jumps the board back two plies rather than one. I solved this by stepping through each half-move individually and animating the piece slide for every step, rather than animating directly from the start position to the end position. This keeps the motion readable even when skipping multiple moves. What’s next I want to expand from 25 openings to 100+, including variations of openings that are already in the game (e.g. multiple lines within the Sicilian Defense, not just one). I also think the hinting system could be reworked. Stepping back through earlier moves might be too easy a hint, since recognizable patterns persist even a few moves back. I’m considering alternatives, like instead revealing partial information (e.g. only the pawn structure, or only the piece types without full positions) rather than rewinding the whole position. In short, this is a very rough draft, and simply a fun project for me. If anyone here knows chess and has any ideas or comments, please let me know. Thanks!! live at: https://stashm10.github.io/Chession/"}]...
|
Title: Opening Knowledge by @stashm10 | Stardance
Title: Opening Knowledge by @stashm10 | Stardance
Devlogs:
Chession Devlog #1 I built a chess opening guessing game. The idea: a position from a famous chess opening is shown on the board, and you have to guess which opening it is. How it works A random opening is selected from a list of 25, and the board renders the position after move 10 (20 plies). You type a guess or pick from a list that filters as you type. If your guess is wrong, the board steps back one move (one move for black and one move for white) and shows an earlier position as a hint. You get 5 guesses total. Each wrong guess reveals more of the position’s history, making the next guess easier. What I’ve built so far Static board rendering using FEN-style positions generated from chess.js Move validation and position-building logic using chess.js -An animated piece-slide transition when navigating between hint positions, instead of just snapping Autocomplete with keyboard navigation (arrow keys, enter to select) -A guess history display showing correct/wrong attempts -Navigation buttons (and arrow keys) to move between all hint positions you’ve unlocked, not just the latest one -A welcome modal explaining the rules A reload-confirmation dialog so accidental refreshes don’t wipe progress mid-game Animating the hints The trickiest part was animating between positions when going back, since each wrong guess jumps the board back two plies rather than one. I solved this by stepping through each half-move individually and animating the piece slide for every step, rather than animating directly from the start position to the end position. This keeps the motion readable even when skipping multiple moves. What’s next I want to expand from 25 openings to 100+, including variations of openings that are already in the game (e.g. multiple lines within the Sicilian Defense, not just one). I also think the hinting system could be reworked. Stepping back through earlier moves might be too easy a hint, since recognizable patterns persist even a few moves back. I’m considering alternatives, like instead revealing partial information (e.g. only the pawn structure, or only the piece types without full positions) rather than rewinding the whole position. In short, this is a very rough draft, and simply a fun project for me. If anyone here knows chess and has any ideas or comments, please let me know. Thanks!! live at: https://stashm10.github.io/Chession/
Devlog#2 I decided to add some more features to make this game more accessible. The main feature that I added was a difficulty section. How it works: After selecting “let’s play” you get the option to pick the “normal” or “grandmaster” difficulty. You can easily tell that the grandmaster difficulty is the harder one by the intimidating cartoon picture next to it (I did use AI to make that since I am not good at drawing). As the game grew, I noticed that chess puzzles and openings can be incredibly brutal if you do not know the exact lines, which often leads to quick frustration. On the flip side, making the game universally easier takes away the competitive edge that chess veterans look for. I wanted to bridge this gap so casual players can learn without getting punished immediately while hardcore players can still experience a strict challenge. Grandmaster mode offers the classic, strict experience with standard guess limits and only allows you to step two moves back on your final guess to try and correct your line. To make things more forgiving, Normal mode adds an extra lifeline giving you one more guess than usual, and it allows a deeper lookback of four moves instead of two on your final guess. This extra context helps players re-visualize where their theory went wrong and successfully find the right continuation. Looking ahead, now that the core difficulty framework is in place, I am focusing on content depth and progression. First, I plan to significantly expand the library of chess openings and variations. To balance out the difficulty, I might limit the pool of openings in Normal mode to more common, foundational lines while increasing them in the Grandmaster section to unleash rare, highly theoretical variations that require deep knowledge. I am also looking into implementing a login system to keep track of progress, save personal stats, and track which openings players have mastered. Along with user accounts, I want to introduce a potential leaderboard so players can see how their scores stack up against the rest of the community. The update is live right now, so please try it out for yourself and and let me know if you have any questions or feedback.
Ships:
I made a fun chess game, specifically, a chess opening game, Chession. How it works is simple. A position from a famous chess opening is shown on the board, and you have to guess which opening it is. The opening is selected from a list of 25, and the board renders the position after move 10 (20 plies). You type a guess or pick from a list that filters as you type. If your guess is wrong, the board steps back two plies (one full move) and shows an earlier position as a hint. You get 5 guesses total. Each wrong guess reveals more of the position’s history, making the next guess easier. The cool part is that there are so many openings (well, 25 for now), so you can have multiple attempts. Unlike Wordle or other guessing games, you dont have to wait 24 hours to play. It was difficult setting up the chess board, the pieces, and piece animation, however I made it work. The trickiest part was animating between positions when going back, since each wrong guess jumps the board back two plies rather than one. I solved this by stepping through each half-move individually and animating the piece slide for every step, rather than animating directly from the start position to the end position. This keeps the motion readable even when skipping multiple moves. I hope in the future I can add more openings, and vartions of popular openings, that way I can make it more difficult :) The idea is just a simple game for all types of chess players, a chess version of Wordle… if that makes sense. Enjoy!...
|
1793890182.105311
|
1793976582.105311
|
|
29192
|
my APOD site by @stashm10 | Stardance
|
stashm10
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-01T06:13:36Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Built NASA-Pulse, a site that fetches NASA’s Astronomy Picture of the Day and displays the title, image/video, and explanation, updated daily. Used Vite + vanilla JS, deployed via GitHub Actions to GitHub Pages. The trickiest part was debugging a “stuck loading” bug that turned out not to be my code at all. NASA’s own API servers were timing out. Confirmed it by hitting the raw API URL directly and seeing the same timeout. Fixed it by adding a 15s timeout with one automatic retry so the site fails faster and recovers on its own more often instead of hanging. Proudest of getting the full pipeline working end to end local dev, GitHub Secrets for the API key, and auto-deploy on every push since this was my first time setting up real CI/CD instead of just running things locally. To test it: just visit the live link, it fetches today’s picture automatically. Occasionally NASA’s API itself is slow (their servers, not the site), so a refresh usually fixes it if it takes a moment.", "repo": "https://github.com/Stashm10/NASA-Pulse", "demo": "https://stashm10.github.io/NASA-Pulse/"}]...
|
[{"post_id": 19807, "ts": "202 [{"post_id": 19807, "ts": "2026-07-01T06:11:02Z", "hours": 1.2664, "text": "Devlog #1: Building NASA-Pulse What I built A little site that pulls NASA’s Astronomy Picture of the Day and shows it with the title, image (or video), and explanation. Nothing crazy complicated on paper, but it ended up teaching me a lot more than I expected going in. Live here: https://stashm10.github.io/NASA-Pulse/ This was my first time actually setting up a full pipeline from scratch –> Vite for the build, GitHub for version control, GitHub Actions for CI/CD, and GitHub Pages for hosting. I’d used git before but never wired together a real automated deploy flow, so that part alone was a good learning curve. Currently, this website is a little slow in terms of loading speed. After deploying, the site would sometimes work fine and sometimes just hang on “Loading…” for a minute before failing. Turns out NASA’s own API servers were timing out, not a bug in my code. Confirmed it by hitting the raw API URL directly and getting a server timeout error. Ended up adding a timeout + automatic retry so the site fails faster and recovers on its own more often instead of just hanging. What I’d do differently Honestly, not much. Going step by step through GitHub setup -> local scaffolding -> coding -> deployment in that order made debugging way easier than if I’d tried to do everything at once. Testing locally before pushing saved me from pushing broken code multiple times. What’s next A few ideas I want to come back to: Add a date picker so I can browse past APOD entries, not just today’s Handle the “already have a token but rate-limited” case more gracefully, maybe cache the day’s response so repeated visits don’t hit the API again Clean up mobile styling a bit more — the zigzag decorative strips are hidden below 600px right now, but I want to double check the rest of the layout holds up on smaller screens Maybe swap in a search-by-date feature or a “random APOD” button for fun Takeaways This was a good first real end-to-end project AND not just “write some code” but actually shipping something live, dealing with a flaky third-party API, and setting up a deploy pipeline that runs itself going forward. Small project, but it covered a surprising amount of ground."}]...
|
Title: my APOD site by @stashm10 | Stardance
Devl Title: my APOD site by @stashm10 | Stardance
Devlogs:
Devlog #1: Building NASA-Pulse What I built A little site that pulls NASA’s Astronomy Picture of the Day and shows it with the title, image (or video), and explanation. Nothing crazy complicated on paper, but it ended up teaching me a lot more than I expected going in. Live here: https://stashm10.github.io/NASA-Pulse/ This was my first time actually setting up a full pipeline from scratch –> Vite for the build, GitHub for version control, GitHub Actions for CI/CD, and GitHub Pages for hosting. I’d used git before but never wired together a real automated deploy flow, so that part alone was a good learning curve. Currently, this website is a little slow in terms of loading speed. After deploying, the site would sometimes work fine and sometimes just hang on “Loading…” for a minute before failing. Turns out NASA’s own API servers were timing out, not a bug in my code. Confirmed it by hitting the raw API URL directly and getting a server timeout error. Ended up adding a timeout + automatic retry so the site fails faster and recovers on its own more often instead of just hanging. What I’d do differently Honestly, not much. Going step by step through GitHub setup -> local scaffolding -> coding -> deployment in that order made debugging way easier than if I’d tried to do everything at once. Testing locally before pushing saved me from pushing broken code multiple times. What’s next A few ideas I want to come back to: Add a date picker so I can browse past APOD entries, not just today’s Handle the “already have a token but rate-limited” case more gracefully, maybe cache the day’s response so repeated visits don’t hit the API again Clean up mobile styling a bit more — the zigzag decorative strips are hidden below 600px right now, but I want to double check the rest of the layout holds up on smaller screens Maybe swap in a search-by-date feature or a “random APOD” button for fun Takeaways This was a good first real end-to-end project AND not just “write some code” but actually shipping something live, dealing with a flaky third-party API, and setting up a deploy pipeline that runs itself going forward. Small project, but it covered a surprising amount of ground.
Ships:
Built NASA-Pulse, a site that fetches NASA’s Astronomy Picture of the Day and displays the title, image/video, and explanation, updated daily. Used Vite + vanilla JS, deployed via GitHub Actions to GitHub Pages. The trickiest part was debugging a “stuck loading” bug that turned out not to be my code at all. NASA’s own API servers were timing out. Confirmed it by hitting the raw API URL directly and seeing the same timeout. Fixed it by adding a 15s timeout with one automatic retry so the site fails faster and recovers on its own more often instead of hanging. Proudest of getting the full pipeline working end to end local dev, GitHub Secrets for the API key, and auto-deploy on every push since this was my first time setting up real CI/CD instead of just running things locally. To test it: just visit the live link, it fetches today’s picture automatically. Occasionally NASA’s API itself is slow (their servers, not the site), so a refresh usually fixes it if it takes a moment....
|
1793847254.7029715
|
1793933654.7029715
|
|
22041
|
My awesome macropad! by @starz | Stardance
|
starz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @starz | Stardance
|
1793260504.0717678
|
1793865304.0717678
|
|
36863
|
Untitled project by @starwhisper | Stardance
|
starwhisper
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @starwhisper | Stardanc Title: Untitled project by @starwhisper | Stardance...
|
1793523188.0416992
|
1794127988.0416992
|
|
60657
|
onFocus by @starvulkan | Stardance
|
starvulkan
|
2
|
18.0
|
88
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-31T15:05:46Z", "hours": 7.0, "multiplier": 13.27, "payout": 88, "blessing": "neutral", "text": "the mysterious onFocus sequel! So it turns out I had about 6.6 unshipped hours for this project and I just realized lol (thx amberrr), so I figured what is the loss of reshipping it, the more stardust the merrier! So these hours mostly come from the changes I made while ship #1 was being reviewed, which I thought were included in that ship, but it turns out I was wrong lol! So this ship includes the weather functionality, deleting focus sessions from your history, and the very good UI refresh I gave it! as my first project for any ysws, I am still very fond of it although now I see sooo many stuff I could’ve done better. i still use onFocus as my primary new tab on my browser, and I can give testimony that it was helped me quite a bit on enhancing my productivity, as before I would get easily distracted by the shortcut links on my new tab, but now i never do! its also very cozy and I quite like the UI I made for it. for voters, um yea I understand if you give it a low rating lol, its kinda mid in the grand scheme of things, and i’ve realized this with time (i now see soooo many stuff I could’ve added or enhanced lol). i kinda just see this project as the thing that made me begin my hack club adventure, as a relic of the near past, yk?", "repo": "https://github.com/starvulkan/onFocus", "demo": "https://starvulkan.github.io/onFocus/"}, {"ship_num": 2, "ts": "2026-09-15T20:27:20Z", "hours": 11.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "onFocus !", "repo": "https://github.com/starvulkan/onFocus", "demo": "https://starvulkan.github.io/onFocus/"}]...
|
[{"post_id": 71366, "ts": "202 [{"post_id": 71366, "ts": "2026-09-20T18:17:05Z", "hours": 3.1311, "text": "Devlog 7: are you blind? they are clearly different! its a UI refresh! like chrome in 2023, the onFocus UI has been updated! i rewrote the whole css stylesheet and brought some changes along the way! buttons are now minty! the weather icon is now also filled with minty color, not just an outline as before. rounded corners in bars have also been amplified. the onFocus logo has been moved to the top of all the center elements. most importantly, i realized that previously, onFocus used to be quite resource wasteful with some visuals (like the moving aurora blobs). all these unnecessary stuff have been removed, and now onFocus doesnt consume as much system resources as before."}, {"post_id": 70890, "ts": "2026-09-19T23:22:47Z", "hours": 0.3197, "text": "quick devlog 6.5! the features and changes mentioned in devlog 6 are now available! since the ship review came back needing a few changes, i figured i should just bundle them in the re-ship."}, {"post_id": 69457, "ts": "2026-09-17T02:54:25Z", "hours": 3.1639, "text": "The onFocusing Sessions, Devlog 6: Updates While-U-Wait although my first ship is still under review, this doesn’t stop me to continue working on features for the next ship! these aren’t available in the repo just yet, but they will be as soon as the ship gets reviewed! i’ve added two new features and fixed a bug. before, if you refreshed the page, whatever you wrote into the focus intent didnt get saved and cached if you didnt start the focus session. now, it gets saved, no matter if the focus session has been started or nah. as for features, you can now delete focus sessions from history, in case they got accidentally started or the intent wasn’t written correctly. if you accidentally delete one, you can undo your delete as long as you dont leave the history menu. if you delete and leave the menu, its gone forever. also, weather has been added (uses Open-Meteo)! you may now search for your location or use the “use my location” button to find it automatically, and get weather info (will appear in the top left corner once set)! soo cool! this will be the last update until the first ship gets reviewed. once it comes back from that, this update will be available in the repo, and i’ll start working on a few more for the second ship!"}, {"post_id": 68814, "ts": "2026-09-15T19:59:40Z", "hours": 3.0603, "text": "The onFocusing Sessions, Devlog 5: Houston, we have focused! You can now set NASA’s Astronomy Picture of the Day as your new tab wallpaper! With this update, a new settings menu has also been added, where you can change between the NASA APOD or onFocus’s default wallpaper; Aurora Blobs. due to the randomized nature of the NASA APOD, this can create problems with the visibility of on-screen texts and images, cuz some pictures may be brighter or darker than others. thats why, when in NASA APOD wallpaper mode, a dimming config will appear in settings, allowing you to get the image to look just right in relation to the other on-screen elements. I have also added into the settings menu the config to set a different search engine other than duckyduckygooo. you can choose between a set of engines in a dropdown, or add a link to a custom search engine. you may call this the first actual release of onFocus! this version is going to get shipped. but, a second ship will start development immediately afterwards, with new features to enhance your experience!"}, {"post_id": 68470, "ts": "2026-09-15T05:10:29Z", "hours": 2.9053, "text": "The onFocusing Sessions, Devlog 4: ITS ALIVEEE sooo slight detour… I delayed the NASA APOD thingy to prioritize getting onFocus’s main features up and running. because why if no focus features, why focus shaped? so yea! now it’s an actually useable new tab replacement for your current one! the focus features have been added. this includes your task/focus creator, pomodoro timer, and focus history. your very important and essential search bar has also been added, with duckygo as the default search engine. expect a custom search engine selector in a future update! isnt it so fun when you are falling asleep while programming and you make a typo and dont realize you did until oh wow why is my code not working?? yea i find that EXTREMELY funn… next up for tomorrow’s me to deal with: i’m finally getting the NASA APOD wallpaper setting up and running. once that’s done, imma ship this thing’s first release. but that wont be the end, imma ship again afterwards with more features!!"}, {"post_id": 68297, "ts": "2026-09-14T21:36:18Z", "hours": 2.9986, "text": "The onFocusing Sessions, Devlog 3: onFocus invades your browser, muehehe guysss, finally, tangible progress has been made! with the addition of the Manifest V3, alongside other configs, onFocus can now be installed as an extension on Chromium-based browsers in extension developer mode and take over your (allegedly) very bloated and time-consuming new tab! For our fellow non-Chromium browser users, you may set the live demo link as your homepage, cuz custom extension installs are just temporary (one browser restart and they be gone) and for the possibility of permanent installs i would have to get it signed, and that would take too long… the codebase is still one for both the extension and website, with a small storage layer that quietly uses chrome.storage inside the extension and localStorage on the web. with this update, a semi-functional UI has also been added to onFocus. It features a time-triggered greeter and a clock, as well as a background with three CSS-animated blobs. soo cool!! for them to move and breathe around, you need to enable animation effects in your OS, otherwise they gonna stay still the whole time. next, I will start working on getting NASA’s APOD as a background option, so you can choose between that and the onFocus blobs!"}, {"post_id": 67847, "ts": "2026-09-14T03:40:23Z", "hours": 0.3303, "text": "The onFocusing Sessions, Devlog 2: Graphicssss most of the work on onFocus today went to creating its graphical identity: logos, wordmarks, etcc! Took time to settle on colors and designs, but ended with something I feel very happy with! Its logo icon features a crescent moon with a star, to represent focus and late-night work sessions. The color palette chosen gives it a “minty clean” feeling, just like our (planned) UI! main issue today involved the fact that I used live text on the wordmark when designing it in Affinity, so when exported to SVG, if the host device didn’t have the custom font, it would look horrible in a fallback sans-serif, and thats putting it lightly. So I just ended up using PNGs for all designs to avoid a big headache… also dealt with few canvas dimension issues and embedded bitmaps with no actual paths in supposed “vector” icons, but nothing beyond that. Once all the graphics were ready, they were added to the GitHub README, the placeholder in the live demo, and wherever necessary! now, it doesn’t look stale and boring! and thats funn! next up, we return to work on the actual new tab itself! we’ll prepare the Manifest V3 extension wrapper, so onFocus can actually take over a new tab page and finally give you that much needed focus!"}, {"post_id": 67087, "ts": "2026-09-13T04:25:02Z", "hours": 1.6325, "text": "The onFocusing Sessions, Devlog 1: Humble Beginnings welcome to the development of onFocus, a new tab page that helps you keep your mind where your work is, instead of on the distractions killing our chances of becoming responsible human beings. you’ll be able to set a focus session, run a timer against it, and get weekly reports on where your time actually went. Time runs and waits for nobody, yk! as with any project, work today involved getting the whole structure and basics up and running, so a lot of scaffolding, cleaning, configuring, ETCCC. as we all know, that’s E V E R Y B O D Y ’ S favorite part, so funnnnn… few issues here and there, biggest one being when I had to install node through VS Code terminal and then it refused to accept it existed, so every new terminal window was getting a “snapshot” from before the install, until VS Code got its little restart. as for important decisions, today was decided that onFocus should exist and run as both a website and as a browser extension for mass access, and those live at completely different URLs, so every asset path in the build has to be relative rather than absolute. what this mostly involved was one new line in the vite config, to get both targets with one build. kill two birds with one stone right there! live demo up and running, but it’s just fun placeholder stuff. real progress on design and structure next!"}]...
|
Title: onFocus by @starvulkan | Stardance
Devlogs Title: onFocus by @starvulkan | Stardance
Devlogs:
The onFocusing Sessions, Devlog 1: Humble Beginnings welcome to the development of onFocus, a new tab page that helps you keep your mind where your work is, instead of on the distractions killing our chances of becoming responsible human beings. you’ll be able to set a focus session, run a timer against it, and get weekly reports on where your time actually went. Time runs and waits for nobody, yk! as with any project, work today involved getting the whole structure and basics up and running, so a lot of scaffolding, cleaning, configuring, ETCCC. as we all know, that’s E V E R Y B O D Y ’ S favorite part, so funnnnn… few issues here and there, biggest one being when I had to install node through VS Code terminal and then it refused to accept it existed, so every new terminal window was getting a “snapshot” from before the install, until VS Code got its little restart. as for important decisions, today was decided that onFocus should exist and run as both a website and as a browser extension for mass access, and those live at completely different URLs, so every asset path in the build has to be relative rather than absolute. what this mostly involved was one new line in the vite config, to get both targets with one build. kill two birds with one stone right there! live demo up and running, but it’s just fun placeholder stuff. real progress on design and structure next!
The onFocusing Sessions, Devlog 2: Graphicssss most of the work on onFocus today went to creating its graphical identity: logos, wordmarks, etcc! Took time to settle on colors and designs, but ended with something I feel very happy with! Its logo icon features a crescent moon with a star, to represent focus and late-night work sessions. The color palette chosen gives it a “minty clean” feeling, just like our (planned) UI! main issue today involved the fact that I used live text on the wordmark when designing it in Affinity, so when exported to SVG, if the host device didn’t have the custom font, it would look horrible in a fallback sans-serif, and thats putting it lightly. So I just ended up using PNGs for all designs to avoid a big headache… also dealt with few canvas dimension issues and embedded bitmaps with no actual paths in supposed “vector” icons, but nothing beyond that. Once all the graphics were ready, they were added to the GitHub README, the placeholder in the live demo, and wherever necessary! now, it doesn’t look stale and boring! and thats funn! next up, we return to work on the actual new tab itself! we’ll prepare the Manifest V3 extension wrapper, so onFocus can actually take over a new tab page and finally give you that much needed focus!
The onFocusing Sessions, Devlog 3: onFocus invades your browser, muehehe guysss, finally, tangible progress has been made! with the addition of the Manifest V3, alongside other configs, onFocus can now be installed as an extension on Chromium-based browsers in extension developer mode and take over your (allegedly) very bloated and time-consuming new tab! For our fellow non-Chromium browser users, you may set the live demo link as your homepage, cuz custom extension installs are just temporary (one browser restart and they be gone) and for the possibility of permanent installs i would have to get it signed, and that would take too long… the codebase is still one for both the extension and website, with a small storage layer that quietly uses chrome.storage inside the extension and localStorage on the web. with this update, a semi-functional UI has also been added to onFocus. It features a time-triggered greeter and a clock, as well as a background with three CSS-animated blobs. soo cool!! for them to move and breathe around, you need to enable animation effects in your OS, otherwise they gonna stay still the whole time. next, I will start working on getting NASA’s APOD as a background option, so you can choose between that and the onFocus blobs!
The onFocusing Sessions, Devlog 4: ITS ALIVEEE sooo slight detour… I delayed the NASA APOD thingy to prioritize getting onFocus’s main features up and running. because why if no focus features, why focus shaped? so yea! now it’s an actually useable new tab replacement for your current one! the focus features have been added. this includes your task/focus creator, pomodoro timer, and focus history. your very important and essential search bar has also been added, with duckygo as the default search engine. expect a custom search engine selector in a future update! isnt it so fun when you are falling asleep while programming and you make a typo and dont realize you did until oh wow why is my code not working?? yea i find that EXTREMELY funn… next up for tomorrow’s me to deal with: i’m finally getting the NASA APOD wallpaper setting up and running. once that’s done, imma ship this thing’s first release. but that wont be the end, imma ship again afterwards with more features!!
The onFocusing Sessions, Devlog 5: Houston, we have focused! You can now set NASA’s Astronomy Picture of the Day as your new tab wallpaper! With this update, a new settings menu has also been added, where you can change between the NASA APOD or onFocus’s default wallpaper; Aurora Blobs. due to the randomized nature of the NASA APOD, this can create problems with the visibility of on-screen texts and images, cuz some pictures may be brighter or darker than others. thats why, when in NASA APOD wallpaper mode, a dimming config will appear in settings, allowing you to get the image to look just right in relation to the other on-screen elements. I have also added into the settings menu the config to set a different search engine other than duckyduckygooo. you can choose between a set of engines in a dropdown, or add a link to a custom search engine. you may call this the first actual release of onFocus! this version is going to get shipped. but, a second ship will start development immediately afterwards, with new features to enhance your experience!
The onFocusing Sessions, Devlog 6: Updates While-U-Wait although my first ship is still under review, this doesn’t stop me to continue working on features for the next ship! these aren’t available in the repo just yet, but they will be as soon as the ship gets reviewed! i’ve added two new features and fixed a bug. before, if you refreshed the page, whatever you wrote into the focus intent didnt get saved and cached if you didnt start the focus session. now, it gets saved, no matter if the focus session has been started or nah. as for features, you can now delete focus sessions from history, in case they got accidentally started or the intent wasn’t written correctly. if you accidentally delete one, you can undo your delete as long as you dont leave the history menu. if you delete and leave the menu, its gone forever. also, weather has been added (uses Open-Meteo)! you may now search for your location or use the “use my location” button to find it automatically, and get weather info (will appear in the top left corner once set)! soo cool! this will be the last update until the first ship gets reviewed. once it comes back from that, this update will be available in the repo, and i’ll start working on a few more for the second ship!
quick devlog 6.5! the features and changes mentioned in devlog 6 are now available! since the ship review came back needing a few changes, i figured i should just bundle them in the re-ship.
Devlog 7: are you blind? they are clearly different! its a UI refresh! like chrome in 2023, the onFocus UI has been updated! i rewrote the whole css stylesheet and brought some changes along the way! buttons are now minty! the weather icon is now also filled with minty color, not just an outline as before. rounded corners in bars have also been amplified. the onFocus logo has been moved to the top of all the center elements. most importantly, i realized that previously, onFocus used to be quite resource wasteful with some visuals (like the moving aurora blobs). all these unnecessary stuff have been removed, and now onFocus doesnt consume as much system resources as before.
Ships:
onFocus !
the mysterious onFocus sequel! So it turns out I had about 6.6 unshipped hours for this project and I just realized lol (thx amberrr), so I figured what is the loss of reshipping it, the more stardust the merrier! So these hours mostly come from the changes I made while ship #1 was being reviewed, which I thought were included in that ship, but it turns out I was wrong lol! So this ship includes the weather functionality, deleting focus sessions from your history, and the very good UI refresh I gave it! as my first project for any ysws, I am still very fond of it although now I see sooo many stuff I could’ve done better. i still use onFocus as my primary new tab on my browser, and I can give testimony that it was helped me quite a bit on enhancing my productivity, as before I would get easily distracted by the shortcut links on my new tab, but now i never do! its also very cozy and I quite like the UI I made for it. for voters, um yea I understand if you give it a low rating lol, its kinda mid in the grand scheme of things, and i’ve realized this with time (i now see soooo many stuff I could’ve added or enhanced lol). i kinda just see this project as the thing that made me begin my hack club adventure, as a relic of the near past, yk?...
|
1793825635.5906708
|
1793912035.5906708
|
|
63142
|
P1ˣᵖ by @starvulkan | Stardance
|
starvulkan
|
1
|
42.0
|
767
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-12T02:08:50Z", "hours": 42.0, "multiplier": 15.34, "payout": 767, "blessing": "neutral", "text": "P1xp!", "repo": "https://github.com/starvulkan/P1xp", "demo": "https://github.com/starvulkan/P1xp/releases/latest"}]...
|
[{"post_id": 78921, "ts": "202 [{"post_id": 78921, "ts": "2026-10-12T01:53:55Z", "hours": 3.1594, "text": "vroom vroom, Devlog 15: STARVULKAN WINS THE MENTAL SANITY GRAND PRIX ! guysss FINALLYY, after weeks and weeks of slowly decaying into insanity, i’ve FINALLYY finished this very cool and amazing project!! im so happy with how things came along at the end, and I hope y’all can enjoy this silly little F1 project! testing during the race went as smooth the smooth operator 55 himself before 2026, with basically one lone issue, that being the app struggling to refresh the race weekend post race (throughout the whole developing process my biggest enemy was that ending transition huh). that’s now fixed, it now uses storage to know if to refresh. wrote the whole readme today as well, by far the most effort i’ve ever made for a readme, but i had to cuz this project means quite a lot to me. and as a final feature, cuz if i didnt i would get exterminated from this planet by the copyright agents, i added the possibility for you to choose your track images for the hero! since i had to delete the hero images that came bundled before cuz copyright and redistribution and stuff, the app, by default, now comes with no hero image, just a silly gradient. you, the user, now have the power of choosing the circuit hero image, bring your own from whatever source! details on how to do this in the readme! and yea! like that, i’m finally shipping this project of mine! thanks to y’all that have followed the whole development process and my (alleged) suffering and gave your amazing support! it truly means a lot to me 💖."}, {"post_id": 78530, "ts": "2026-10-11T03:31:16Z", "hours": 2.2725, "text": "vroom vroom, Devlog 14: WE’RE NEARLY THEREEE!! im sooo closee to finishing this projectt! im actually soo happy with how things are coming along! although working on this messed up my sleep schedule very badly its really all been worth it. singapore quali testing went better than i expected, with the issues really just being the join live button hiding behind the hero cuz i forgot how to do basic css and the session end and live mode exit feeling very jarring as it ended immediately when the session ended, which combined with the F1 TV broadcast being off by aprox. 30 seconds, made the transition feel off. both of these have been fixed (more info below)! once again, im too tired to write another explanation for all the changes and updates i did, so its time to let github release notes me speak lol updates and changes in this build (tag 1.0.0-beta) 1. After a session ends, the app no longer leaves live mode immediately, rather it freezes final data (after 5 mins of wait to ensure all data is final) and waits until the user manually clicks exit live. this is to avoid the transition from live mode back to countdown from being very jarring, especially considering that F1 TV stream is delayed by a varying number of seconds. 2. added car status badges in the tower (these indicate if a car/driver is out, retired, in pit, or eliminated, and greys them out accordingly)! 3. animations in the tower! these indicate when a driver changes positions (either by overtaking/getting overtaken in race/sprint, or setting faster laps in practice/qualis). by obvious reasons, these project better in live mode than in demo mode (the whole thing is sped up x3, its an animation party lol). also didnt mention this in github but i added an about button in the app so its easier to find the build version yes you heard that right, this aint a DEV build, im confident enough in this build to finally upgrade the app to beta! if everything goes well tomorrow during the race, im finally releasing v1 and shipping this project! and if you ask why i just tested with quali and not with the sprint as i promised, eeeeh i may or may not have completely missed my alarm and slept through the sprint… DONT BLAME ME IM TIRED AF"}, {"post_id": 78212, "ts": "2026-10-09T23:53:23Z", "hours": 3.3825, "text": "vroom vroom, Devlog 13: post-singapore sprint quali testing! basically every feature worked during this test, but at the end of SQ2 the app decided to kill my hopes and dreams by exiting live mode mid-session, but i think ive found the fix (hopefully). once again, since ive not slept for over 30 hours atp, i am too tired to rewrite a new explanation for all the changes i did during this time period, so imma think smarter, not harder by recycling my very good and thorough explanation i used for the github release notes lol these are the changes and updates in this new build (DEV_0.3.0): 1. Instead of using an automatic switcher (which proved to give lots of errors) to switch between live mode and countdown, now you can enter/exit live mode through a button (when there’s an ongoing live session). 2. lap counter for races & sprints (only available in live mode). 3. Track map and live mode changes & updates (using MultiView’s API): better circuit outlines and color change for better visibility, track map broadcast orientation, numbered corners, sector flag zones, and pit loss with safety car and VSC figures. and yea, that’s that! now imma go get some real good sleep before waking up at 3 am AGAIN to test with the sprint race why do i do this to myself"}, {"post_id": 78051, "ts": "2026-10-09T11:51:21Z", "hours": 1.5442, "text": "vroom vroom, Devlog 12: post-singapore fp1 testing! WOW THE THING THAT DOES THE LIVE THING WORKS (kinda ig but YAYY nonetheless i wont have to experience more unnecessary mental decay !! ) had to fix a few things, some are bigger issues than others but i think i have permanent solutions for those (hopefully)! as described in the new github repo pre-release (tag DEV_0.2.0), main changes include: updates to the track map (had rendering issues and is incapable of projecting driver position dots without a F1 TV subscription token, so it’s stuck as a simple track map for now, I might add the option to connect to your F1 TV subscription in a future update). driver acronym fix (due to update overwrite blanking the driver acronyms were turning into their number fallbacks mid-session). proper session ending (now you should NOT have to wait an eternity for the app to leave live mode after a session ends, i hope!). i really didnt feel like writing another explanation for that lol ive barely slept tonight and sprint quali is in about 40 mins, so yea no more sleeping for me yayyy endme . so yea, its time for testing round 2! lets see how that goes."}, {"post_id": 78005, "ts": "2026-10-09T04:49:58Z", "hours": 1.4967, "text": "vroom vroom, Devlog 11.5: get lance strolled so major oversight, two issues that i completely forgot to fix before packaging came to my mind again. specifically: 1. the app was incapable of entering live mode on a fresh install during race weekend, cuz the cache was never created. 2. in case of a delay, cuz the live mode timer follows the predicted end time, the app would exit live mode before the session itself actually finished. these two are now fixed. now, the schedule comes bundled with the build, and proper processing in case of delay was added, only downside is that the app will take long to exit live mode, as it will stay waiting for signals after a session finishes, as this is the sacrifice to avoid, yk, leaving the whole session while its going on! installers for this build (DEV_0.1.1) are also now available in the repo. we will be back in 3 hours…"}, {"post_id": 77601, "ts": "2026-10-07T16:22:54Z", "hours": 0.8322, "text": "vroom vroom, Devlog 11: short n’ sweet short work session today i added an offline fallback to the drivers list in setup, as that was the only openf1-dependent item that still didnt have a fallback. it is also capable of self-updating. most importantly tho, i packaged the app itself! runners and installers are now available in the github repo (pre-release tag DEV_0.1.0), so feel free to try them out and to help out identifying bugs during the live testing this week in singapore! available for windows, macOS, and linux!"}, {"post_id": 77377, "ts": "2026-10-06T18:19:27Z", "hours": 1.1767, "text": "vroom vroom, Devlog 10.5: debugging dewormers this is a short one, just added a few visual debuggers in live stream mode in case of unexpected inchidents during live testing. i really dont have a good image for this devlog, so take the countdown to the day in which the f1 gods will decide to either keep me alive or to kill me."}, {"post_id": 77214, "ts": "2026-10-06T03:39:52Z", "hours": 5.4253, "text": "vroom vroom, Devlog 10: ITS LIGHTS OUT AND AWAY WE GO (untested) pt.2 yes im very creative with my devlog names and like in pt.1, ive just finished my longest work session EVER. but the process sure makes it worth it. first and foremost, the electron stuff is ready, so P1xp is now capable of invading your desktop! isnt that so cool? the new live session data fetcher is now ready to be tested! its, in short, a signalR core client in the electron main process that connects straight to f1’s own live timing feed, which is hosted in their servers. unlike openf1, this one is free and requires no account to access live data. due to f1’s feed being completely different from openf1’s as it sends partial deltas (so one driver and one field at a time), a naive merge wipes data it didnt mention. so, ive created a new converter that keeps a cache per driver and always emits complete rows, so the timing tower, track map, radio, and race control panes all project live data without a single change to any of them directly. in demo mode, the circuit outline for the track map comes from replaying a lap of position data. when live, theres no history. instead, the app accumulates each car’s trail as it goes and draws the whole circuit in roughly the first minute of running. IN THEORY (again), this should be a definite, fully functional build of P1xp. like before, i still need to test it live, so this week’s singapore gp will be my new test dummy. i created a recorder in the client thats capable of dumping every raw frame f1 sends to a file, plus a tool that reads a recording back and summarises what arrived. this allows me to have a recorded copy of singapore fp1 i can use as a permanent test fixture in case something doesnt work as intended during live testing. i really hope this works, im slowly going insane…"}, {"post_id": 76878, "ts": "2026-10-04T22:16:21Z", "hours": 4.5525, "text": "vroom vroom, Devlog 9: WE’RE BACK TO RACING!! so since i’ve only been able to work in short bursts of time over the past few days, progress had been very slow and not very devlog worthy, until today! i’ve been working on getting the most important OpenF1-dependent items to work offline, so in case of request blocks, they can still work just fine. this includes mainly the season calendar and the demo. the calendar now gets cached in storage for offline access. it is also able to update its contents by fetching from OpenF1 when possible, which helps make it proof to unexpected race calendar changes. for the demo, i created a .MJS file to create a .JSON file that saves the data from silverstone 2025 used in the demo. this allows the demo to always run offline and separate from openf1, instead of fetching data every time its used. this also allows the demo to run waaay faster than before, and makes it always available, even when openf1 blocks access to historical data when a live session is active. as a bonus, i also fixed the timing tower to actually differentiate between a race and practices/qualis, so for the latter it orders positions by best lap and show gaps to pole instead of race intervals, which are used for just the race itself. next up, i need to prepare the electron scaffolding for the app, as in order to fetch live data from F1 directly i need it to run as a desktop app. F1’s server doesnt send CORS headers, so browsers refuse to read it, but CORS is a browser rule, and electron’s main process is just node, so this allows a desktop app to connect where a webpage cant. and i need this to actually get the live session feed working, cuz as i said before… you mean i cant see LIVE data in the f1 LIVE experience app?! what kind of scam is this?!?!"}, {"post_id": 74717, "ts": "2026-09-28T02:04:18Z", "hours": 2.0064, "text": "vroom vroom, Devlog 8: HOW CAN YOU BE SO USELESS MAN?!?! pt.2 im backk! well technically ive been working a bit this whole time ive just not devlogged yet, so its time to report what has happened in the past few days! so as i mentioned last time, i tried to test with baku fp3, quali, and race, but my plan got cut short right in fp3. sooo due to my bad habit of not investigating deeply and not reading details, i didnt realize that OpenF1 doesnt give out LIVE session data to non-authorized users just historical data, which means there’s a paywall, stardance’s biggest enemy … soo effectively the project became useless in its current state. to add insult to injury, OpenF1 blocks all non-authorized requests to their servers when there’s a live session going on, so the whole app stops working when a live session begins lol you mean i cant see LIVE data in the f1 LIVE experience app?! what kind of scam is this?!?! if i had just investigated a bit further i would have found out that F1 themselves give out live session data for free. thing is, i can’t fetch this through web, so i will have to lock the app to desktop upon release. as for what ive actually done until now, i created a .json that saves the 2026 & 2027 calendars locally so it can fallback to that version when OpenF1 locks their servers and the home menu stops fetching data from them directly. this .json will also be capable of updating its contents when its fetching live from OpenF1, so in case of small inchidents (ahem war) that cause a race to be cancelled or changed of location (i sure love the bahrain gp in malaysia), the local calendar.json can update."}, {"post_id": 73429, "ts": "2026-09-25T02:20:58Z", "hours": 4.8192, "text": "vroom vroom, Devlog 7: ITS LIGHTS OUT AND AWAY WE GO (untested) FINALLYYY, after my longest work session ever, I got the live f1 session stream working*, with all the features i previously mentioned (time and position tower with wheel stats, race control, track map, team radios, and allocated space for F1 TV live stream if you are a subscriber)! *: the live stream was tested using past race data from silverstone 2025 (you can demo test the stream with the same data using the Demo option). It fetches the most eventful 10 minutes from this race, and plays them at 3x speed, so you can test most of the live stream features in less than 6 minutes! I still have to test the live stream with actual live session data from OpenF1, so i’ll use baku FP3, quali, and race to do this. You can join the testing and try P1xp out for the first time too, as all these changes are now public in the github pages deployment! If everything goes well during live testing, this version will be shipped! We’re so closeee!"}, {"post_id": 72533, "ts": "2026-09-23T04:47:23Z", "hours": 3.7092, "text": "vroom vroom, Devlog 6: less is more not a lot of visible progress today, but certainly a bunch of invisible developments! so most of the backend javascript scripts for the livestream session components (time and position tower, session data logger, track map) were programmed today. The possibility for a livestream demo was also added, to make it possible to test the livestream display screen even when a live f1 session isn’t going on at that time. This demo uses Silverstone 2025 for its race data, as it was quite a interesting and complete race with most of the data points that can be demoed and displayed by P1xp. tomorrow, i’ll edit and prepare the main 3 files (index.html, style.css, main.js) to use these scripts so these features can be deployed. i mean, its like the main selling point it would be outrageous if they weren’t available by the time baku fp1 starts, right? …right?"}, {"post_id": 72093, "ts": "2026-09-22T04:47:14Z", "hours": 1.0178, "text": "vroom vroom, Devlog 5: IMAGESSS!! so although once again my schedule really limited what i was able to do today, i was able to keep my promise and now there’s track display images in the countdown! woww so cool! added images for the tracks in the 2026 & 2027 calendars."}, {"post_id": 71589, "ts": "2026-09-21T03:28:01Z", "hours": 1.7422, "text": "vroom vroom: Devlog 4: hi starvulkan, my name is progress! i finally locked in and finished the stylesheet from its incomplete state, which means we have the first functioning deploy up now! tomorrow’s mission is to get good-looking track images for the big blank space on top of the countdown. i mean, its screaming to put an image on it!"}, {"post_id": 70956, "ts": "2026-09-20T03:08:22Z", "hours": 1.9233, "text": "vroom vroom, Devlog 3: wow… its… incomplete?!? yeaaa so due to my very fun schedule i didnt finish what i had intended to do today… i did finish index.html and the main JS script, so 2/3 ig! i really could only start the css stylesheet due to time, so im hopefully finishing that tomorrow, as well as actually testing if what i already did um… works. if everything goes well, the first actual deployed build should be up by tomorrow, so lets hope for the best! no updates to the github repo today, i want to finish these 3 fully first before committing and pushing."}, {"post_id": 70417, "ts": "2026-09-19T04:39:41Z", "hours": 1.2761, "text": "vroom vroom, Devlog 2: how can you be so useless man?! yeaa so my school made my free time vanish by adding so much stuff to do out of the blue, so yeaa kinda didnt do much today lol most importantly, the JavaScript base for the first time setup got done today, so thats something i guess… if my schedule allows it tomorrow i should start working on, yk, the actual main stuff (index.html, main.js, and style.css stuff). also i need to fix the currently broken deploy, as i have not updated the main files from their original vite templates state."}, {"post_id": 69961, "ts": "2026-09-18T04:04:00Z", "hours": 1.3525, "text": "vroom vroom, Devlog 1: the fun stuff so the idea for P1xp is to provide an unique way to experience F1, right from your pc. using data from openF1, it can show data like track info, current session positions, conditions, etc. If you are an F1 TV user (you’ll be able to determine all this through first time settings), you’ll get an allocated space in the app to place your F1 TV window to watch both the live stream and the session data simultaneously. if you are a F1 TV Premium user, you’ll also get a double allocated space to place the onboard cam for your favorite driver (also chosen through first time settings, this will matter for theming!). and speaking of theming, the app will offer multiple app themes and skins based on your favorite team chosen! today i did the vite scaffolding and the other fun environment setups and configs, and i programmed the JS controllers and bones for the team themes and the session schedules. it got too late to keep working on the rest, and i have homeworks to do soooo… i’ll work on the main functionality stuff tomorrow once im recharged lol. i need to get this app working before next thursday cuz the last F1 race weekend before Stardance ends is next week (welcome to skibidi toilet baku my dudesss 🔥🔥🔥) and after that its gonna be basically impossible to test the app. so yea i have a week to finish this! time to speedrunnnn"}]...
|
Title: P1ˣᵖ by @starvulkan | Stardance
Devlogs:
v Title: P1ˣᵖ by @starvulkan | Stardance
Devlogs:
vroom vroom, Devlog 1: the fun stuff so the idea for P1xp is to provide an unique way to experience F1, right from your pc. using data from openF1, it can show data like track info, current session positions, conditions, etc. If you are an F1 TV user (you’ll be able to determine all this through first time settings), you’ll get an allocated space in the app to place your F1 TV window to watch both the live stream and the session data simultaneously. if you are a F1 TV Premium user, you’ll also get a double allocated space to place the onboard cam for your favorite driver (also chosen through first time settings, this will matter for theming!). and speaking of theming, the app will offer multiple app themes and skins based on your favorite team chosen! today i did the vite scaffolding and the other fun environment setups and configs, and i programmed the JS controllers and bones for the team themes and the session schedules. it got too late to keep working on the rest, and i have homeworks to do soooo… i’ll work on the main functionality stuff tomorrow once im recharged lol. i need to get this app working before next thursday cuz the last F1 race weekend before Stardance ends is next week (welcome to skibidi toilet baku my dudesss 🔥🔥🔥) and after that its gonna be basically impossible to test the app. so yea i have a week to finish this! time to speedrunnnn
vroom vroom, Devlog 2: how can you be so useless man?! yeaa so my school made my free time vanish by adding so much stuff to do out of the blue, so yeaa kinda didnt do much today lol most importantly, the JavaScript base for the first time setup got done today, so thats something i guess… if my schedule allows it tomorrow i should start working on, yk, the actual main stuff (index.html, main.js, and style.css stuff). also i need to fix the currently broken deploy, as i have not updated the main files from their original vite templates state.
vroom vroom, Devlog 3: wow… its… incomplete?!? yeaaa so due to my very fun schedule i didnt finish what i had intended to do today… i did finish index.html and the main JS script, so 2/3 ig! i really could only start the css stylesheet due to time, so im hopefully finishing that tomorrow, as well as actually testing if what i already did um… works. if everything goes well, the first actual deployed build should be up by tomorrow, so lets hope for the best! no updates to the github repo today, i want to finish these 3 fully first before committing and pushing.
vroom vroom: Devlog 4: hi starvulkan, my name is progress! i finally locked in and finished the stylesheet from its incomplete state, which means we have the first functioning deploy up now! tomorrow’s mission is to get good-looking track images for the big blank space on top of the countdown. i mean, its screaming to put an image on it!
vroom vroom, Devlog 5: IMAGESSS!! so although once again my schedule really limited what i was able to do today, i was able to keep my promise and now there’s track display images in the countdown! woww so cool! added images for the tracks in the 2026 & 2027 calendars.
vroom vroom, Devlog 6: less is more not a lot of visible progress today, but certainly a bunch of invisible developments! so most of the backend javascript scripts for the livestream session components (time and position tower, session data logger, track map) were programmed today. The possibility for a livestream demo was also added, to make it possible to test the livestream display screen even when a live f1 session isn’t going on at that time. This demo uses Silverstone 2025 for its race data, as it was quite a interesting and complete race with most of the data points that can be demoed and displayed by P1xp. tomorrow, i’ll edit and prepare the main 3 files (index.html, style.css, main.js) to use these scripts so these features can be deployed. i mean, its like the main selling point it would be outrageous if they weren’t available by the time baku fp1 starts, right? …right?
vroom vroom, Devlog 7: ITS LIGHTS OUT AND AWAY WE GO (untested) FINALLYYY, after my longest work session ever, I got the live f1 session stream working*, with all the features i previously mentioned (time and position tower with wheel stats, race control, track map, team radios, and allocated space for F1 TV live stream if you are a subscriber)! *: the live stream was tested using past race data from silverstone 2025 (you can demo test the stream with the same data using the Demo option). It fetches the most eventful 10 minutes from this race, and plays them at 3x speed, so you can test most of the live stream features in less than 6 minutes! I still have to test the live stream with actual live session data from OpenF1, so i’ll use baku FP3, quali, and race to do this. You can join the testing and try P1xp out for the first time too, as all these changes are now public in the github pages deployment! If everything goes well during live testing, this version will be shipped! We’re so closeee!
vroom vroom, Devlog 8: HOW CAN YOU BE SO USELESS MAN?!?! pt.2 im backk! well technically ive been working a bit this whole time ive just not devlogged yet, so its time to report what has happened in the past few days! so as i mentioned last time, i tried to test with baku fp3, quali, and race, but my plan got cut short right in fp3. sooo due to my bad habit of not investigating deeply and not reading details, i didnt realize that OpenF1 doesnt give out LIVE session data to non-authorized users just historical data, which means there’s a paywall, stardance’s biggest enemy … soo effectively the project became useless in its current state. to add insult to injury, OpenF1 blocks all non-authorized requests to their servers when there’s a live session going on, so the whole app stops working when a live session begins lol you mean i cant see LIVE data in the f1 LIVE experience app?! what kind of scam is this?!?! if i had just investigated a bit further i would have found out that F1 themselves give out live session data for free. thing is, i can’t fetch this through web, so i will have to lock the app to desktop upon release. as for what ive actually done until now, i created a .json that saves the 2026 & 2027 calendars locally so it can fallback to that version when OpenF1 locks their servers and the home menu stops fetching data from them directly. this .json will also be capable of updating its contents when its fetching live from OpenF1, so in case of small inchidents (ahem war) that cause a race to be cancelled or changed of location (i sure love the bahrain gp in malaysia), the local calendar.json can update.
vroom vroom, Devlog 9: WE’RE BACK TO RACING!! so since i’ve only been able to work in short bursts of time over the past few days, progress had been very slow and not very devlog worthy, until today! i’ve been working on getting the most important OpenF1-dependent items to work offline, so in case of request blocks, they can still work just fine. this includes mainly the season calendar and the demo. the calendar now gets cached in storage for offline access. it is also able to update its contents by fetching from OpenF1 when possible, which helps make it proof to unexpected race calendar changes. for the demo, i created a .MJS file to create a .JSON file that saves the data from silverstone 2025 used in the demo. this allows the demo to always run offline and separate from openf1, instead of fetching data every time its used. this also allows the demo to run waaay faster than before, and makes it always available, even when openf1 blocks access to historical data when a live session is active. as a bonus, i also fixed the timing tower to actually differentiate between a race and practices/qualis, so for the latter it orders positions by best lap and show gaps to pole instead of race intervals, which are used for just the race itself. next up, i need to prepare the electron scaffolding for the app, as in order to fetch live data from F1 directly i need it to run as a desktop app. F1’s server doesnt send CORS headers, so browsers refuse to read it, but CORS is a browser rule, and electron’s main process is just node, so this allows a desktop app to connect where a webpage cant. and i need this to actually get the live session feed working, cuz as i said before… you mean i cant see LIVE data in the f1 LIVE experience app?! what kind of scam is this?!?!
vroom vroom, Devlog 10: ITS LIGHTS OUT AND AWAY WE GO (untested) pt.2 yes im very creative with my devlog names and like in pt.1, ive just finished my longest work session EVER. but the process sure makes it worth it. first and foremost, the electron stuff is ready, so P1xp is now capable of invading your desktop! isnt that so cool? the new live session data fetcher is now ready to be tested! its, in short, a signalR core client in the electron main process that connects straight to f1’s own live timing feed, which is hosted in their servers. unlike openf1, this one is free and requires no account to access live data. due to f1’s feed being completely different from openf1’s as it sends partial deltas (so one driver and one field at a time), a naive merge wipes data it didnt mention. so, ive created a new converter that keeps a cache per driver and always emits complete rows, so the timing tower, track map, radio, and race control panes all project live data without a single change to any of them directly. in demo mode, the circuit outline for the track map comes from replaying a lap of position data. when live, theres no history. instead, the app accumulates each car’s trail as it goes and draws the whole circuit in roughly the first minute of running. IN THEORY (again), this should be a definite, fully functional build of P1xp. like before, i still need to test it live, so this week’s singapore gp will be my new test dummy. i created a recorder in the client thats capable of dumping every raw frame f1 sends to a file, plus a tool that reads a recording back and summarises what arrived. this allows me to have a recorded copy of singapore fp1 i can use as a permanent test fixture in case something doesnt work as intended during live testing. i really hope this works, im slowly going insane…
vroom vroom, Devlog 10.5: debugging dewormers this is a short one, just added a few visual debuggers in live stream mode in case of unexpected inchidents during live testing. i really dont have a good image for this devlog, so take the countdown to the day in which the f1 gods will decide to either keep me alive or to kill me.
vroom vroom, Devlog 11: short n’ sweet short work session today i added an offline fallback to the drivers list in setup, as that was the only openf1-dependent item that still didnt have a fallback. it is also capable of self-updating. most importantly tho, i packaged the app itself! runners and installers are now available in the github repo (pre-release tag DEV_0.1.0), so feel free to try them out and to help out identifying bugs during the live testing this week in singapore! available for windows, macOS, and linux!
vroom vroom, Devlog 11.5: get lance strolled so major oversight, two issues that i completely forgot to fix before packaging came to my mind again. specifically: 1. the app was incapable of entering live mode on a fresh install during race weekend, cuz the cache was never created. 2. in case of a delay, cuz the live mode timer follows the predicted end time, the app would exit live mode before the session itself actually finished. these two are now fixed. now, the schedule comes bundled with the build, and proper processing in case of delay was added, only downside is that the app will take long to exit live mode, as it will stay waiting for signals after a session finishes, as this is the sacrifice to avoid, yk, leaving the whole session while its going on! installers for this build (DEV_0.1.1) are also now available in the repo. we will be back in 3 hours…
vroom vroom, Devlog 12: post-singapore fp1 testing! WOW THE THING THAT DOES THE LIVE THING WORKS (kinda ig but YAYY nonetheless i wont have to experience more unnecessary mental decay !! ) had to fix a few things, some are bigger issues than others but i think i have permanent solutions for those (hopefully)! as described in the new github repo pre-release (tag DEV_0.2.0), main changes include: updates to the track map (had rendering issues and is incapable of projecting driver position dots without a F1 TV subscription token, so it’s stuck as a simple track map for now, I might add the option to connect to your F1 TV subscription in a future update). driver acronym fix (due to update overwrite blanking the driver acronyms were turning into their number fallbacks mid-session). proper session ending (now you should NOT have to wait an eternity for the app to leave live mode after a session ends, i hope!). i really didnt feel like writing another explanation for that lol ive barely slept tonight and sprint quali is in about 40 mins, so yea no more sleeping for me yayyy endme . so yea, its time for testing round 2! lets see how that goes.
vroom vroom, Devlog 13: post-singapore sprint quali testing! basically every feature worked during this test, but at the end of SQ2 the app decided to kill my hopes and dreams by exiting live mode mid-session, but i think ive found the fix (hopefully). once again, since ive not slept for over 30 hours atp, i am too tired to rewrite a new explanation for all the changes i did during this time period, so imma think smarter, not harder by recycling my very good and thorough explanation i used for the github release notes lol these are the changes and updates in this new build (DEV_0.3.0): 1. Instead of using an automatic switcher (which proved to give lots of errors) to switch between live mode and countdown, now you can enter/exit live mode through a button (when there’s an ongoing live session). 2. lap counter for races & sprints (only available in live mode). 3. Track map and live mode changes & updates (using MultiView’s API): better circuit outlines and color change for better visibility, track map broadcast orientation, numbered corners, sector flag zones, and pit loss with safety car and VSC figures. and yea, that’s that! now imma go get some real good sleep before waking up at 3 am AGAIN to test with the sprint race why do i do this to myself
vroom vroom, Devlog 14: WE’RE NEARLY THEREEE!! im sooo closee to finishing this projectt! im actually soo happy with how things are coming along! although working on this messed up my sleep schedule very badly its really all been worth it. singapore quali testing went better than i expected, with the issues really just being the join live button hiding behind the hero cuz i forgot how to do basic css and the session end and live mode exit feeling very jarring as it ended immediately when the session ended, which combined with the F1 TV broadcast being off by aprox. 30 seconds, made the transition feel off. both of these have been fixed (more info below)! once again, im too tired to write another explanation for all the changes and updates i did, so its time to let github release notes me speak lol updates and changes in this build (tag 1.0.0-beta) 1. After a session ends, the app no longer leaves live mode immediately, rather it freezes final data (after 5 mins of wait to ensure all data is final) and waits until the user manually clicks exit live. this is to avoid the transition from live mode back to countdown from being very jarring, especially considering that F1 TV stream is delayed by a varying number of seconds. 2. added car status badges in the tower (these indicate if a car/driver is out, retired, in pit, or eliminated, and greys them out accordingly)! 3. animations in the tower! these indicate when a driver changes positions (either by overtaking/getting overtaken in race/sprint, or setting faster laps in practice/qualis). by obvious reasons, these project better in live mode than in demo mode (the whole thing is sped up x3, its an animation party lol). also didnt mention this in github but i added an about button in the app so its easier to find the build version yes you heard that right, this aint a DEV build, im confident enough in this build to finally upgrade the app to beta! if everything goes well tomorrow during the race, im finally releasing v1 and shipping this project! and if you ask why i just tested with quali and not with the sprint as i promised, eeeeh i may or may not have completely missed my alarm and slept through the sprint… DONT BLAME ME IM TIRED AF
vroom vroom, Devlog 15: STARVULKAN WINS THE MENTAL SANITY GRAND PRIX ! guysss FINALLYY, after weeks and weeks of slowly decaying into insanity, i’ve FINALLYY finished this very cool and amazing project!! im so happy with how things came along at the end, and I hope y’all can enjoy this silly little F1 project! testing during the race went as smooth the smooth operator 55 himself before 2026, with basically one lone issue, that being the app struggling to refresh the race weekend post race (throughout the whole developing process my biggest enemy was that ending transition huh). that’s now fixed, it now uses storage to know if to refresh. wrote the whole readme today as well, by far the most effort i’ve ever made for a readme, but i had to cuz this project means quite a lot to me. and as a final feature, cuz if i didnt i would get exterminated from this planet by the copyright agents, i added the possibility for you to choose your track images for the hero! since i had to delete the hero images that came bundled before cuz copyright and redistribution and stuff, the app, by default, now comes with no hero image, just a silly gradient. you, the user, now have the power of choosing the circuit hero image, bring your own from whatever source! details on how to do this in the readme! and yea! like that, i’m finally shipping this project of mine! thanks to y’all that have followed the whole development process and my (alleged) suffering and gave your amazing support! it truly means a lot to me 💖.
Ships:
P1xp!...
|
1793832611.7802427
|
1793919011.7802427
|
|
15464
|
My very own WebOS by @starstellarr093 | Stardance
|
starstellarr093
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @starstellarr093 | Sta Title: My very own WebOS by @starstellarr093 | Stardance...
|
1793281886.7014215
|
1793886686.7014215
|
|
7248
|
P.R.I.M by @stars | Stardance
|
stars
|
0
|
5.77
|
0
|
[]
|
[{"post_id": 19487, "ts": "202 [{"post_id": 19487, "ts": "2026-06-30T20:18:29Z", "hours": 0.8833, "text": "After much pain of routing, I discovered the amount of GND pins not connected! so I’m currently fighting gnd. I also decieded to ruin DRC and boy am I depressed. I’m probably gonna restart with a better layout in mind because there are alot of impossible gnd islands."}, {"post_id": 19441, "ts": "2026-06-30T19:19:55Z", "hours": 4.0919, "text": "Finally Finished the Schematic! I got the final touches done, and got some friends to sanity check. Got started on the first layout and started routing. Im probably gonna redo It once I figure out the optimal layout."}, {"post_id": 18529, "ts": "2026-06-29T18:27:46Z", "hours": 0.7917, "text": "I selected the parts I want to use, as well as created requirements in a markdown file."}]...
|
Title: P.R.I.M by @stars | Stardance
Devlogs:
I s Title: P.R.I.M by @stars | Stardance
Devlogs:
I selected the parts I want to use, as well as created requirements in a markdown file.
Finally Finished the Schematic! I got the final touches done, and got some friends to sanity check. Got started on the first layout and started routing. Im probably gonna redo It once I figure out the optimal layout.
After much pain of routing, I discovered the amount of GND pins not connected! so I’m currently fighting gnd. I also decieded to ruin DRC and boy am I depressed. I’m probably gonna restart with a better layout in mind because there are alot of impossible gnd islands....
|
1793325188.1308322
|
1793929988.1308322
|
|
69870
|
My own site! by @starrohan | Stardance
|
starrohan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @starrohan | Stardance
|
1793595181.6188638
|
1794199981.6188638
|
|
176
|
My first slack bot! by @starr | Stardance
|
starr
|
0
|
0.69
|
0
|
[]
|
[{"post_id": 4738, "ts": "2026 [{"post_id": 4738, "ts": "2026-06-08T05:41:31Z", "hours": 0.6867, "text": "Setting up commands"}]...
|
Title: My first slack bot! by @starr | Stardance
Title: My first slack bot! by @starr | Stardance
Devlogs:
Setting up commands...
|
1793498090.3965163
|
1794102890.3965163
|
|
13666
|
My very own WebOS by @starr | Stardance
|
starr
|
1
|
7.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-24T08:09:55Z", "hours": 7.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I have finally made my first webOS with a welcome window, notes app and stopwatch app. The most challenging part of this project was learning to use JavaScript and trying to code some of the logic myself (and debugging it too!!).", "repo": "https://github.com/userr73/First-WebOS", "demo": "https://userr73.github.io/First-WebOS/"}]...
|
[{"post_id": 73042, "ts": "202 [{"post_id": 73042, "ts": "2026-09-24T08:07:12Z", "hours": 0.4772, "text": "Made some quick updates to the desktop apps so that is is structured into a grid and also changed some content in the welcome and notes window"}, {"post_id": 71708, "ts": "2026-09-21T10:59:57Z", "hours": 0.9417, "text": "Stopwatch App I found a video tutorial for making a stopwatch in JS. The original vid had three separate buttons for START, STOP and RESET, but I changed this so that the START and STOP button are combined together."}, {"post_id": 68034, "ts": "2026-09-14T12:33:41Z", "hours": 1.1922, "text": "idk - Notes app content update + element exceeding window bug?? I updated the HTML so that I can add content through JavaScript so it does not need to be hard coded into the HTML file. I spent of bit of time debugging this as I couldn’t figure out why some of the content I added to the Notes app was disappearing when I clicked it. Turns out there were a few issues like calling the same function twice, but I also realised I added an event listener that ran the wrong function which was why some of the content was disappearing. Also, I did the ‘additional challenges’ in the guide, mainly the 4th point about the bug where windows can exceed the screen width and height. I used a bit of Gemini here to figure out how to get max and min values from a set of numbers (Maths.min and Maths.max) and also used W3Schools to get the window height and width as well as the div element’s own height and width. Using this, I implemented my own logic (with an if statement) to contain the element within the viewport height and width. This took a tiny bit of trial and error coz I kept getting confused on when to use min and when to use max but I got there eventually"}, {"post_id": 65925, "ts": "2026-09-11T11:55:43Z", "hours": 0.9047, "text": "Update JS code file structure + Creating the Notes app functionality I spent some time updating the structure of my js file by reordering some code and also creating functions for any repeated tasks such as initialising windows. I also worked on my Notes app and played around with some border and outline properties to see what combination of styles would make it easier for users to edit in the app. I ended up with going for a left border indicator type of thing (the colours in the screenshot below aren’t final since I haven’t worked on the overall style of my OS yet so I just went with grey and black)"}, {"post_id": 64728, "ts": "2026-09-09T11:13:39Z", "hours": 0.6311, "text": "Working with z-index Continuing with the guide, I’ve added code that ensures that whenever a window clicks, it rises to the top using the z-index property. I did the same for the top bar. Bugs An issue I faced was when I tried to use the function addWindowTapHandling() for my notes screen but I forgot that I defined the notesScreen variable later on in js file so the notes app disappeared from my OS screen for a bit. I also got really stuck on why my top bar wasn’t rising above the windows so I put my js file into Gemini and I realised it was because I had two openWindow() functions and the second one was the old version that did not have the added lines of code."}, {"post_id": 63485, "ts": "2026-09-07T11:20:20Z", "hours": 1.1106, "text": "Adding my second window I have begun working on my second window which will be a notes app. I continued to follow the guide and created an icon for the app and also a new window for it. It’s mostly taken a while to sort out the js file since I got confused with why the window wasn’t popping up at first (I didn’t name the classes and ids for the divs correctly). Here’s the update:"}, {"post_id": 61460, "ts": "2026-09-04T12:05:06Z", "hours": 2.1317, "text": "Setting up the background, top bar, window So far, I have followed the guide and created the background page with a top bar and created my first welcome page window (the content is random right now - I’ll update this later). The window is also draggable at the handle. I’m still working on what kind of style I want to aim for in my OS… Also, this is kinda my first devlog because I thought my devlogs were broken (turns out I just couldn’t figure out how to use this 💀)"}]...
|
Title: My very own WebOS by @starr | Stardance
De Title: My very own WebOS by @starr | Stardance
Devlogs:
Setting up the background, top bar, window So far, I have followed the guide and created the background page with a top bar and created my first welcome page window (the content is random right now - I’ll update this later). The window is also draggable at the handle. I’m still working on what kind of style I want to aim for in my OS… Also, this is kinda my first devlog because I thought my devlogs were broken (turns out I just couldn’t figure out how to use this 💀)
Adding my second window I have begun working on my second window which will be a notes app. I continued to follow the guide and created an icon for the app and also a new window for it. It’s mostly taken a while to sort out the js file since I got confused with why the window wasn’t popping up at first (I didn’t name the classes and ids for the divs correctly). Here’s the update:
Working with z-index Continuing with the guide, I’ve added code that ensures that whenever a window clicks, it rises to the top using the z-index property. I did the same for the top bar. Bugs An issue I faced was when I tried to use the function addWindowTapHandling() for my notes screen but I forgot that I defined the notesScreen variable later on in js file so the notes app disappeared from my OS screen for a bit. I also got really stuck on why my top bar wasn’t rising above the windows so I put my js file into Gemini and I realised it was because I had two openWindow() functions and the second one was the old version that did not have the added lines of code.
Update JS code file structure + Creating the Notes app functionality I spent some time updating the structure of my js file by reordering some code and also creating functions for any repeated tasks such as initialising windows. I also worked on my Notes app and played around with some border and outline properties to see what combination of styles would make it easier for users to edit in the app. I ended up with going for a left border indicator type of thing (the colours in the screenshot below aren’t final since I haven’t worked on the overall style of my OS yet so I just went with grey and black)
idk - Notes app content update + element exceeding window bug?? I updated the HTML so that I can add content through JavaScript so it does not need to be hard coded into the HTML file. I spent of bit of time debugging this as I couldn’t figure out why some of the content I added to the Notes app was disappearing when I clicked it. Turns out there were a few issues like calling the same function twice, but I also realised I added an event listener that ran the wrong function which was why some of the content was disappearing. Also, I did the ‘additional challenges’ in the guide, mainly the 4th point about the bug where windows can exceed the screen width and height. I used a bit of Gemini here to figure out how to get max and min values from a set of numbers (Maths.min and Maths.max) and also used W3Schools to get the window height and width as well as the div element’s own height and width. Using this, I implemented my own logic (with an if statement) to contain the element within the viewport height and width. This took a tiny bit of trial and error coz I kept getting confused on when to use min and when to use max but I got there eventually
Stopwatch App I found a video tutorial for making a stopwatch in JS. The original vid had three separate buttons for START, STOP and RESET, but I changed this so that the START and STOP button are combined together.
Made some quick updates to the desktop apps so that is is structured into a grid and also changed some content in the welcome and notes window
Ships:
I have finally made my first webOS with a welcome window, notes app and stopwatch app. The most challenging part of this project was learning to use JavaScript and trying to code some of the logic myself (and debugging it too!!)....
|
1793797173.134773
|
1793883573.134773
|
|
19313
|
My first slack bot! by @starmender | Stardance
|
starmender
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @starmender | Starda Title: My first slack bot! by @starmender | Stardance...
|
1793469242.5374887
|
1794074042.5374887
|
|
63996
|
My awesome macropad! by @starmaster | Stardance
|
starmaster
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @starmaster | Stard Title: My awesome macropad! by @starmaster | Stardance...
|
1793667351.2310889
|
1794272151.2310889
|
|
3146
|
solarpunk devboard by @starlitfire | Stardance
|
starlitfire
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: solarpunk devboard by @starlitfire | Starda Title: solarpunk devboard by @starlitfire | Stardance...
|
1793263908.136018
|
1793868708.136018
|
|
4205
|
Untitled by @starlitfire | Stardance
|
starlitfire
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @starlitfire | Stardance
|
1793551912.9438536
|
1794156712.9438536
|
|
37383
|
My own site! by @starkmnd | Stardance
|
starkmnd
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @starkmnd | Stardance
|
1793523296.9795632
|
1794128096.9795632
|
|
27113
|
My awesome macropad! by @starkiller261 | Stardance
|
starkiller261
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @starkiller261 | St Title: My awesome macropad! by @starkiller261 | Stardance...
|
1793455036.357222
|
1794059836.357222
|
|
27117
|
Library Manager by @starkiller261 | Stardance
|
starkiller261
|
2
|
10.0
|
89
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-30T18:17:35Z", "hours": 0.0, "multiplier": 2.76, "payout": 1, "blessing": "neutral", "text": "I have completed the authentication system so now the sign in with google function should work smoothly.", "repo": "https://github.com/petevass/VirtualLibrary", "demo": "https://virtual-library.tail5b0cb9.ts.net/"}, {"ship_num": 2, "ts": "2026-07-01T01:58:02Z", "hours": 10.0, "multiplier": 9.31, "payout": 88, "blessing": "neutral", "text": "I use Spring MVC to make a virtual library complete with a full book catalogue, scheduled events, and more. You can sign in to act as the owner, librarian, admin, or just a user! look at the README to find the email and passwords to sign in to the roles. Enjoy!", "repo": "https://github.com/petevass/VirtualLibrary", "demo": "https://virtual-library.tail5b0cb9.ts.net/"}]...
|
[{"post_id": 20096, "ts": "202 [{"post_id": 20096, "ts": "2026-07-01T16:45:40Z", "hours": 0.2706, "text": "Ready For ship"}, {"post_id": 19676, "ts": "2026-07-01T01:56:02Z", "hours": 3.9964, "text": "Library Complete"}, {"post_id": 18869, "ts": "2026-06-30T02:07:05Z", "hours": 1.4311, "text": "Librarian Controls Finshed"}, {"post_id": 18790, "ts": "2026-06-30T00:12:58Z", "hours": 1.1219, "text": "Home Page is Complete"}, {"post_id": 17760, "ts": "2026-06-28T18:02:48Z", "hours": 2.9997, "text": "User Actions are almost done"}]...
|
Title: Library Manager by @starkiller261 | Stardan Title: Library Manager by @starkiller261 | Stardance
Devlogs:
User Actions are almost done
Home Page is Complete
Librarian Controls Finshed
Library Complete
Ready For ship
Ships:
I use Spring MVC to make a virtual library complete with a full book catalogue, scheduled events, and more. You can sign in to act as the owner, librarian, admin, or just a user! look at the README to find the email and passwords to sign in to the roles. Enjoy!
I have completed the authentication system so now the sign in with google function should work smoothly....
|
1793858077.0004609
|
1793944477.0004609
|
|
29649
|
Document SaaS by @starkiller261 | Stardance
|
starkiller261
|
1
|
11.0
|
27
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-16T01:46:01Z", "hours": 11.0, "multiplier": 2.32, "payout": 27, "blessing": "neutral", "text": "This is a Monolithic Spring MVC application which serves as a SaaS that allows users to store, edit, and read documents (Similar to Google Docs). It uses Postgresql to store user and document data and session id authentication", "repo": "https://github.com/petevass/Document_SaaS", "demo": "https://jarvis-ubuntu.tail5b0cb9.ts.net/"}]...
|
[{"post_id": 68888, "ts": "202 [{"post_id": 68888, "ts": "2026-09-15T23:25:30Z", "hours": 5.2253, "text": "finished editing process"}, {"post_id": 63932, "ts": "2026-09-08T00:14:45Z", "hours": 6.2228, "text": "Working on thymeleaf UI"}]...
|
Title: Document SaaS by @starkiller261 | Stardance Title: Document SaaS by @starkiller261 | Stardance
Devlogs:
Working on thymeleaf UI
finished editing process
Ships:
This is a Monolithic Spring MVC application which serves as a SaaS that allows users to store, edit, and read documents (Similar to Google Docs). It uses Postgresql to store user and document data and session id authentication...
|
1793796961.661406
|
1793883361.661406
|
|
29967
|
Trivia Game by @starkiller261 | Stardance
|
starkiller261
|
2
|
34.0
|
82
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-16T16:52:41Z", "hours": 22.0, "multiplier": 1.59, "payout": 35, "blessing": "neutral", "text": "NO AI– completely coded by hand. Spent 20 more hours on this new redesign following the recommendations from my last ship about changing the ui. This is a self hosted kubernetes cluster and full stack website with a flutter ui, Spring Boot backend, connected using a RESTful architectured api. I also used postgresql to store user information and that was seperately hosted using supabase. I then used tailscale to tunnel traffic to my home lab setup. It all works be allowing a user to sign in with jwt authentication through the spring boot backend and generating trivia questions through the open trivia database api.", "repo": "https://github.com/petevass/Trivia-Generator", "demo": "https://stardance-frontend.tail5b0cb9.ts.net/"}, {"ship_num": 2, "ts": "2026-07-22T02:52:42Z", "hours": 12.0, "multiplier": 4.01, "payout": 47, "blessing": "neutral", "text": "This a fullstack app using the spring mvc framework which allows users to test their knowledge to the limits through the variety of trivia topics and questions in the app. The webstack is a Spring MVC, Thymeleaf, and Postgres app with supabase used to host the database and ngrok used to tunnel from a self-hosting rig", "repo": "https://github.com/petevass/Trivia-Generator", "demo": "https://stardance-frontend.tail5b0cb9.ts.net/"}]...
|
[{"post_id": 46589, "ts": "202 [{"post_id": 46589, "ts": "2026-08-13T22:36:31Z", "hours": 6.3025, "text": "Finished Game Play UI"}, {"post_id": 37423, "ts": "2026-07-30T04:01:22Z", "hours": 8.8994, "text": "Working on the Leaderboard"}, {"post_id": 35331, "ts": "2026-07-26T17:26:18Z", "hours": 6.865, "text": "New Flutter Frontend in the works"}, {"post_id": 32041, "ts": "2026-07-20T22:33:58Z", "hours": 3.5997, "text": "UIs Finnaly Done"}, {"post_id": 31269, "ts": "2026-07-19T15:23:08Z", "hours": 4.86, "text": "Trivia API is finished, now I just have to make the frontend"}, {"post_id": 29885, "ts": "2026-07-17T01:32:18Z", "hours": 3.2933, "text": "Just finished configuring my data base and jwt authentication system"}]...
|
Title: Trivia Game by @starkiller261 | Stardance
Title: Trivia Game by @starkiller261 | Stardance
Devlogs:
Just finished configuring my data base and jwt authentication system
Trivia API is finished, now I just have to make the frontend
UIs Finnaly Done
New Flutter Frontend in the works
Working on the Leaderboard
Finished Game Play UI
Ships:
This a fullstack app using the spring mvc framework which allows users to test their knowledge to the limits through the variety of trivia topics and questions in the app. The webstack is a Spring MVC, Thymeleaf, and Postgres app with supabase used to host the database and ngrok used to tunnel from a self-hosting rig
NO AI– completely coded by hand. Spent 20 more hours on this new redesign following the recommendations from my last ship about changing the ui. This is a self hosted kubernetes cluster and full stack website with a flutter ui, Spring Boot backend, connected using a RESTful architectured api. I also used postgresql to store user information and that was seperately hosted using supabase. I then used tailscale to tunnel traffic to my home lab setup. It all works be allowing a user to sign in with jwt authentication through the spring boot backend and generating trivia questions through the open trivia database api....
|
1793912044.6467712
|
1793998444.6467712
|
|
6022
|
My awesome macropad! by @stargazer | Stardance
|
stargazer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stargazer | Starda Title: My awesome macropad! by @stargazer | Stardance...
|
1793386227.6536973
|
1793991027.6536973
|
|
17973
|
Tamawotchu by @stargaze | Stardance
|
stargaze
|
0
|
0.35
|
0
|
[]
|
[{"post_id": 8091, "ts": "2026 [{"post_id": 8091, "ts": "2026-06-13T14:42:59Z", "hours": 0.3531, "text": "only working on it when on edge, half completed thoughts only"}]...
|
Title: Tamawotchu by @stargaze | Stardance
Devlog Title: Tamawotchu by @stargaze | Stardance
Devlogs:
only working on it when on edge, half completed thoughts only...
|
1793454976.869479
|
1794059776.869479
|