|
45085
|
Blurred by @zips-elude-unkind | Stardance
|
zips-elude-unkind
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Blurred by @zips-elude-unkind | Stardance
|
1792612087.5587919
|
1793216887.5587919
|
|
22705
|
My very own WebOS by @zippy_cheetah228 | Stardance
|
zippy_cheetah228
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zippy_cheetah228 | St Title: My very own WebOS by @zippy_cheetah228 | Stardance...
|
1792580013.1279235
|
1793184813.1279235
|
|
36608
|
Frictionless by @zippy_cheetah228 | Stardance
|
zippy_cheetah228
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @zippy_cheetah228 | Stardan Title: Frictionless by @zippy_cheetah228 | Stardance...
|
1792587195.567776
|
1793191995.567776
|
|
14188
|
Tuff idea by @zionphita2022 | Stardance
|
zionphita2022
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Tuff idea by @zionphita2022 | Stardance
|
1792716872.643838
|
1793321672.643838
|
|
63955
|
Funtime game by @zionlwade45 | Stardance
|
zionlwade45
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Funtime game by @zionlwade45 | Stardance
|
1792443280.5094612
|
1793048080.5094612
|
|
55393
|
A two language quiz by @zinebrais | Stardance
|
zinebrais
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A two language quiz by @zinebrais | Stardan Title: A two language quiz by @zinebrais | Stardance...
|
1792493514.6402054
|
1793098314.6402054
|
|
24305
|
Creative Cats Website by @ziminganimates | Stardan Creative Cats Website by @ziminganimates | Stardance...
|
ziminganimates
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-23T16:08:35Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a website for the Creative Cats Robotics FTC team. This was a unpaid project with the goal of helping me review and polish my HTML/CSS/JS Skills", "repo": "https://github.com/zimingcsascsa/CreativeCats27606", "demo": "https://zimingcsascsa.github.io/CreativeCats27606/index.html"}]...
|
[{"post_id": 14450, "ts": "202 [{"post_id": 14450, "ts": "2026-06-23T16:07:17Z", "hours": 0.3825, "text": "tuff new font"}, {"post_id": 13992, "ts": "2026-06-22T23:21:27Z", "hours": 1.2581, "text": "Finished updating website for 2026-2027 season"}]...
|
Title: Creative Cats Website by @ziminganimates | Title: Creative Cats Website by @ziminganimates | Stardance
Devlogs:
Finished updating website for 2026-2027 season
tuff new font
Ships:
I made a website for the Creative Cats Robotics FTC team. This was a unpaid project with the goal of helping me review and polish my HTML/CSS/JS Skills...
|
1792821325.8989108
|
1792907725.8989108
|
|
16671
|
My very own WebOS by @zimamakmal17 | Stardance
|
zimamakmal17
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zimamakmal17 | Starda Title: My very own WebOS by @zimamakmal17 | Stardance...
|
1792547678.4791472
|
1793152478.4791472
|
|
22821
|
CatFinder by @zim | Stardance
|
zim
|
0
|
0.28
|
0
|
[]
|
[{"post_id": 12868, "ts": "202 [{"post_id": 12868, "ts": "2026-06-21T02:22:16Z", "hours": 0.2756, "text": "Devlog #1: Cat placement."}]...
|
Title: CatFinder by @zim | Stardance
Devlogs:
Dev Title: CatFinder by @zim | Stardance
Devlogs:
Devlog #1: Cat placement....
|
1792760111.5637305
|
1793364911.5637305
|
|
38852
|
My own site! by @zim | Stardance
|
zim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zim | Stardance
|
1792497164.7493591
|
1793101964.7493591
|
|
67634
|
My awesome macropad! by @zikoualexandra21 | Starda My awesome macropad! by @zikoualexandra21 | Stardance...
|
zikoualexandra21
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zikoualexandra21 | Title: My awesome macropad! by @zikoualexandra21 | Stardance...
|
1792468159.1858406
|
1793072959.1858406
|
|
21810
|
My awesome macropad! by @zihan | Stardance
|
zihan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zihan | Stardance
|
1792623127.1533554
|
1793227927.1533554
|
|
1310
|
Untitled project by @ziggy | Stardance
|
ziggy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @ziggy | Stardance
|
1792608882.1747222
|
1793213682.1747222
|
|
7761
|
Zico Chess Engine by @zico | Stardance
|
zico
|
1
|
11.0
|
97
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-09T23:06:12Z", "hours": 11.0, "multiplier": 9.01, "payout": 97, "blessing": "neutral", "text": "I created a chess-engine with a chess bot that plays smarter move by looking into the game by 3 steps or even more. Managing states was challenging to me at first cause the state was mutated which caused lot of error and missing piece so i cloned the board which makes it immutable. I’m proud because this project taught me a lot of things from state management to writing my first algorithm. You can check out my project at https://zico-chess-engine.vercel.app . My repo at https://github.com/young1dev/chess-engine", "repo": "https://github.com/young1dev/chess-engine", "demo": "https://zico-chess-engine.vercel.app"}]...
|
[{"post_id": 5944, "ts": "2026 [{"post_id": 5944, "ts": "2026-06-09T22:58:32Z", "hours": 7.8381, "text": "Added the min-max and alpha-beta pruning algorithm to enable the bot make smarter moves"}, {"post_id": 2605, "ts": "2026-06-05T06:52:56Z", "hours": 2.8917, "text": "I’m working on the v2 of my chessbot using the minmax algorithm and alpha beta pruning"}]...
|
Title: Zico Chess Engine by @zico | Stardance
Dev Title: Zico Chess Engine by @zico | Stardance
Devlogs:
I’m working on the v2 of my chessbot using the minmax algorithm and alpha beta pruning
Added the min-max and alpha-beta pruning algorithm to enable the bot make smarter moves
Ships:
I created a chess-engine with a chess bot that plays smarter move by looking into the game by 3 steps or even more. Managing states was challenging to me at first cause the state was mutated which caused lot of error and missing piece so i cloned the board which makes it immutable. I’m proud because this project taught me a lot of things from state management to writing my first algorithm. You can check out my project at https://zico-chess-engine.vercel.app . My repo at https://github.com/young1dev/chess-engine...
|
1792842903.4043968
|
1792929303.4043968
|
|
14542
|
My awesome macropad! by @zico | Stardance
|
zico
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zico | Stardance
|
1792752571.6179857
|
1793357371.6179857
|
|
45157
|
My Portfolio by @zico | Stardance
|
zico
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My Portfolio by @zico | Stardance
|
1792615714.114979
|
1793479714.114979
|
|
48643
|
Habit completion predictor by @zico | Stardance
|
zico
|
1
|
40.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-16T20:26:42Z", "hours": 40.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I just wrapped up the development of the prediction model although i’m yet to implement an auto retraining of model based on users data because i have little data to actually analyse which model would be the best which still leaves the model at the default one trained with synthetic data. Your data are been kept tho and would be trained on when the feature is active and your logs is up to the min requirement", "repo": "https://github.com/young1dev/habit-coach", "demo": "https://habit-coach-beige.vercel.app"}]...
|
[{"post_id": 77294, "ts": "202 [{"post_id": 77294, "ts": "2026-10-06T13:50:41Z", "hours": 3.8983, "text": "I just fixed a server failure for the backend due to duplicate db table. It’s up and running to use now. I’ll be improving feature engineering for the underlyin ML Model after i’ve gathered enough real data. Feel free to check out the project and suggest any changes 😊"}, {"post_id": 48504, "ts": "2026-08-16T21:35:26Z", "hours": 36.3628, "text": "Successfully trained the model with an accuracy of 99% (PSS: That’s because i used synthetic dataset and it wasn’t realistic enough). What i’ve done so far: Feature Engineering: Mapped out features that could be useful in predicting an habit completion and filtered out noise features Created a synthetic dataset for the ML training using Logistic Regression and Decision Tree (Both seemed to work well tho). I tested the ML model with the training dataset and did a mini visual evaluation on the model accuracy and features dependency."}]...
|
Title: Habit completion predictor by @zico | Stard Title: Habit completion predictor by @zico | Stardance
Devlogs:
Successfully trained the model with an accuracy of 99% (PSS: That’s because i used synthetic dataset and it wasn’t realistic enough). What i’ve done so far: Feature Engineering: Mapped out features that could be useful in predicting an habit completion and filtered out noise features Created a synthetic dataset for the ML training using Logistic Regression and Decision Tree (Both seemed to work well tho). I tested the ML model with the training dataset and did a mini visual evaluation on the model accuracy and features dependency.
I just fixed a server failure for the backend due to duplicate db table. It’s up and running to use now. I’ll be improving feature engineering for the underlyin ML Model after i’ve gathered enough real data. Feel free to check out the project and suggest any changes 😊
Ships:
I just wrapped up the development of the prediction model although i’m yet to implement an auto retraining of model based on users data because i have little data to actually analyse which model would be the best which still leaves the model at the default one trained with synthetic data. Your data are been kept tho and would be trained on when the feature is active and your logs is up to the min requirement...
|
1792857381.6839757
|
1792943781.6839757
|
|
34939
|
cubepilot by @ziadzohdy | Stardance
|
ziadzohdy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: cubepilot by @ziadzohdy | Stardance
|
1792486372.6472857
|
1793091172.6472857
|
|
34452
|
Spotify Player ESP32 by @ziadmansi | Stardance
|
ziadmansi
|
0
|
1.49
|
0
|
[]
|
[{"post_id": 30161, "ts": "202 [{"post_id": 30161, "ts": "2026-07-17T14:50:39Z", "hours": 1.4922, "text": "Im currently working on the code that’ll fetch the data from spotify from what’s being played, the artist, and etc."}]...
|
Title: Spotify Player ESP32 by @ziadmansi | Starda Title: Spotify Player ESP32 by @ziadmansi | Stardance
Devlogs:
Im currently working on the code that’ll fetch the data from spotify from what’s being played, the artist, and etc....
|
1792680896.714893
|
1793285696.714893
|
|
31968
|
My own site! by @ziadezziyara | Stardance
|
ziadezziyara
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @ziadezziyara | Stardance
|
1792630489.4427986
|
1793235289.4427986
|
|
63593
|
Image matcher by @zhul | Stardance
|
zhul
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Image matcher by @zhul | Stardance
|
1792443026.3167412
|
1793047826.3167412
|
|
15159
|
My awesome macropad! by @zhuang_j | Stardance
|
zhuang_j
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zhuang_j | Stardan Title: My awesome macropad! by @zhuang_j | Stardance...
|
1792749257.602543
|
1793354057.602543
|
|
53789
|
My awesome macropad! by @zhuJohnny | Stardance
|
zhuJohnny
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zhuJohnny | Starda Title: My awesome macropad! by @zhuJohnny | Stardance...
|
1792759935.0665874
|
1793364735.0665874
|
|
51087
|
DOTApad by @zhrado | Stardance
|
zhrado
|
0
|
4.47
|
0
|
[]
|
[{"post_id": 53628, "ts": "202 [{"post_id": 53628, "ts": "2026-08-24T08:39:54Z", "hours": 1.8667, "text": "Designing board layout/adding 3d view of pcb"}, {"post_id": 53469, "ts": "2026-08-24T01:15:01Z", "hours": 1.1172, "text": "Schematic changes. Added rotary encoder and neopixels."}, {"post_id": 50166, "ts": "2026-08-19T08:38:08Z", "hours": 1.4833, "text": "DOTApad schematic. Made key matrix, oled and wired it up."}]...
|
Title: DOTApad by @zhrado | Stardance
Devlogs:
DO Title: DOTApad by @zhrado | Stardance
Devlogs:
DOTApad schematic. Made key matrix, oled and wired it up.
Schematic changes. Added rotary encoder and neopixels.
Designing board layout/adding 3d view of pcb...
|
1792655575.1047137
|
1793260375.1047137
|
|
42892
|
My own site! by @zhowie_ | Stardance
|
zhowie_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zhowie_ | Stardance
|
1792525979.4158347
|
1793130779.4158347
|
|
45697
|
mini keyboard+ ellectric guitar pedals by @zhowie_ mini keyboard+ ellectric guitar pedals by @zhowie_ | Stardance...
|
zhowie_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: mini keyboard+ ellectric guitar pedals by @ Title: mini keyboard+ ellectric guitar pedals by @zhowie_ | Stardance...
|
1792633743.1609635
|
1793238543.1609635
|
|
45698
|
keybored+electric guitar by @zhowie_ | Stardance
|
zhowie_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: keybored+electric guitar by @zhowie_ | Star Title: keybored+electric guitar by @zhowie_ | Stardance...
|
1792633743.9968011
|
1793238543.9968011
|
|
2291
|
Typing Wizard by @zhoops | Stardance
|
zhoops
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Typing Wizard by @zhoops | Stardance
|
1792767209.3710938
|
1793372009.3710938
|
|
3549
|
My awesome macropad! by @zhongwendy4 | Stardance
|
zhongwendy4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zhongwendy4 | Star Title: My awesome macropad! by @zhongwendy4 | Stardance...
|
1792792365.1204486
|
1793397165.1204486
|
|
3555
|
My first slack bot! by @zhongwendy4 | Stardance
|
zhongwendy4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zhongwendy4 | Stard Title: My first slack bot! by @zhongwendy4 | Stardance...
|
1792730997.2793403
|
1793335797.2793403
|
|
3556
|
My first slack bot! by @zhongwendy4 | Stardance
|
zhongwendy4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zhongwendy4 | Stard Title: My first slack bot! by @zhongwendy4 | Stardance...
|
1792698433.1930928
|
1793303233.1930928
|
|
18357
|
Frictionless by @zhongwendy4 | Stardance
|
zhongwendy4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @zhongwendy4 | Stardance
|
1792493728.380035
|
1793098528.380035
|
|
11520
|
the rocket shooter by @zhirkopro115 | Stardance
|
zhirkopro115
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: the rocket shooter by @zhirkopro115 | Stard Title: the rocket shooter by @zhirkopro115 | Stardance...
|
1792594403.9119406
|
1793199203.9119406
|
|
27611
|
skywalk by @zhirkopro115 | Stardance
|
zhirkopro115
|
1
|
85.39
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-26T19:23:24Z", "hours": 82.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Hello dear tester i made this game cs i one time i stumbled across game like that that i liked but i wanted to add a phew things to it cs i liked it but it wasnt my game so i created my own with my own features. I am very proud that i made autopilot and guide i think that was the hardest things to do ( and physics od course like gravity and whatewer ). What do you need to know to play? i think you only need to know that arrow up it the throttle up and arrow down is throttle down and also you need to know that wars is the q and e buttoms map is m and you dont need to worry about autopilot doing strange things it will do it just don touch it cs it will turn off and remember that the starter rocket can fly to the moon but not back ( cs there is not enough fuel) so if you wanted to go back to earth you would need to build a larger rocket and i think thats all . good luck testing it and have a good morning/afternoon/evening/night bye :)", "repo": "https://github.com/zhirkoalexander-maker/ellipse", "demo": "https://zhirkoalexander-maker.github.io/ellipse/"}]...
|
[{"post_id": 75570, "ts": "202 [{"post_id": 75570, "ts": "2026-09-30T13:54:19Z", "hours": 3.3944, "text": "hello dear testers i wrote yes i wrote this game with help of ai but now i got 35 procent ai ( like the autopilot is ai and map is ai ( on map just planets)) everithing else i wrote myself with the help of my dad . Please may you stop rejecting my project again and again ( i am so sorry i cant do more of this cs i am in 8 grade ant only on this week i had 9 tests ( this includes piano that i play)) i just did everithing i could to this project sorry and bye"}, {"post_id": 74141, "ts": "2026-09-26T19:15:30Z", "hours": 5.6719, "text": "helloooo everyone and today i officially ended my project. jst added a new model of the rocket ( cs it looked bad in my opinion ) and in the start if you joined for the first time there will be a guide waiting for you ( kinda struggled on that one ) and added this legs that hold the rocket when it is about to launch. I very wanted to add more things about the game to this devlog but if i will be adding here every feature it would cost me like 8 h so sorry but you can always check it out yourself here https://zhirkoalexander-maker.github.io/ellipse/ oh and i changed the game name from ellipse to challanger ( yeah that spaceship that exploded back in 1990 (sorry dont know the real date)) cs the game with name ellipse alredy exsit bla bla bla. oookey this is the end so thanks every one for beeng here and buy ( for some one who is rating my game pls dont rate me hard i am a starter and my dad helped me a lot and i am jst so bad in english ) btw if anybody wanted to know i am saving up on a bambulab mini ok soo now its the real end so bye and see you later :)"}, {"post_id": 72370, "ts": "2026-09-22T19:29:54Z", "hours": 8.8811, "text": "hi everyone today i made this cool crash animation that shows up when you try to land on a planet faster than 30 m/s (i think i might change it to higher soon like to 70 m/s so it will be easier to land) and i am working on a landing porcess but it is so hard and idk what to do but i want to do it myself without ai so sorry if it will be trash and sorry for the rocket details i am just so bad at drawing especially 3d models (i trided hard)and thats all. Oh and i changed the warp a lil bit so it dosent take you 5 mins to fly to the jupiter (warp is q and e buttons) oh and i added sas (autopilot) so if you dont want to fly to the moon yourself ( its preery hard) you can just press sas and sellect the planet but still it is preety much a concepcion but il try my best to do it thnks for reading bye :)"}, {"post_id": 36662, "ts": "2026-07-28T21:18:14Z", "hours": 10.3414, "text": "hello. ehhhhh….. i dont think you know how much love and my life i gave to this game and this is the best i can do. when i add new things there are 2 new bugs and that was happening for more than a 100 times. i dont think i will end this game cs i and tired. sorry fellas.(dont judge my devlogs please cs i spend most time coding) sorry and see you in another 10 h"}, {"post_id": 29128, "ts": "2026-07-15T19:57:31Z", "hours": 8.8847, "text": "today added the sun and added the debug screen to see what wrong (debug was very hard even harder than the game(wasted 5 h on it)) and i think i am going to add the guide in the menu(there is help button but it dosnt work yet) soo i think i is all for today and have a good thms :)"}, {"post_id": 27670, "ts": "2026-07-13T13:21:13Z", "hours": 10.0064, "text": "today nothing special in this devlog i fixed some bugs that were glitching the game. and added so you can actualy see the rocket in the vehicle assembly and i am going to make this better. and if you want to know the bugs i fixed and what i added (bet you dont) but i am still going to write that cs it need to be in the devlog. soo i fixed thet the roket couldnt land properly on the planets and wasnt crashing if the speed was to fast (more than 30 m/s) also fixed that the earth gravity was to strong and you couldnt tke off cs your fuel was running yout to fast. also added that the rocket have weight so if your rocket is to heavy you cant lift od aaand i added the sun day and night. if you made it here i am impressed (pls follow?) ok ok i am joking by have a good day (or night or evening or lunch or morning or 1 oclock or 2 or clock or….) ok see ya :) (follow @paper_01 )"}, {"post_id": 26589, "ts": "2026-07-11T14:37:27Z", "hours": 8.4506, "text": "this is video of my gameplay of the game and i like it like this is what i wanted to create but there is more to presice like landing on other planets crashes and more. you can play it right now there https://zhirkoalexander-maker.github.io/ellipse/ the game isnt finshed yet but if you want to play here. :)"}, {"post_id": 24968, "ts": "2026-07-08T21:09:46Z", "hours": 8.3767, "text": "today nothing crazy i added a bunch of models and fixed a few bugs (like gravity was to strong) also i added crash to the game so if you go into the planet to fast you crash into it and i added a normal working menu yeah and also 3d recurces i took from here if you want https://science.nasa.gov/3d-resources/ (nasa 3d models)"}, {"post_id": 22045, "ts": "2026-07-04T09:22:41Z", "hours": 3.5458, "text": "today i added a better texture of the rocket and a degree meter so you know in what posytion are you right now also added a phew buttons (they were there but they werent working properly) and i think in the next update i will add a smoother landing see ya ;)"}, {"post_id": 20091, "ts": "2026-07-01T16:40:56Z", "hours": 2.6222, "text": "StarWeld v0.4: real textures + 3D terrain on all planets, KSC launch pad at real coords, terrain collision matches visual mountains, controls locked on pad until liftoff, compressed orbits (Moon 4Mm), fuel ×1.5, reentry heat, HUD. Fixed: Moon clipping, ocean spawn, mountain clipping, TS clean. sorry i was writing it like robot cs i dont have much time. ps it still sucks i will fix it toomorow"}, {"post_id": 19436, "ts": "2026-06-30T19:15:07Z", "hours": 9.2897, "text": "today didnt do much but added some buttons to menu fixed some bugs and added better texure of earth and now its time for physyk of the game and honestly …. ahhh i think i will need help of ai or if someone can help with it pls comment"}, {"post_id": 17607, "ts": "2026-06-28T14:06:37Z", "hours": 6.4111, "text": "i wanted to create game where you build and launch you rocket ship to planets in solar system here is my first work"}]...
|
Title: skywalk by @zhirkopro115 | Stardance
Devlo Title: skywalk by @zhirkopro115 | Stardance
Devlogs:
i wanted to create game where you build and launch you rocket ship to planets in solar system here is my first work
today didnt do much but added some buttons to menu fixed some bugs and added better texure of earth and now its time for physyk of the game and honestly …. ahhh i think i will need help of ai or if someone can help with it pls comment
StarWeld v0.4: real textures + 3D terrain on all planets, KSC launch pad at real coords, terrain collision matches visual mountains, controls locked on pad until liftoff, compressed orbits (Moon 4Mm), fuel ×1.5, reentry heat, HUD. Fixed: Moon clipping, ocean spawn, mountain clipping, TS clean. sorry i was writing it like robot cs i dont have much time. ps it still sucks i will fix it toomorow
today i added a better texture of the rocket and a degree meter so you know in what posytion are you right now also added a phew buttons (they were there but they werent working properly) and i think in the next update i will add a smoother landing see ya ;)
today nothing crazy i added a bunch of models and fixed a few bugs (like gravity was to strong) also i added crash to the game so if you go into the planet to fast you crash into it and i added a normal working menu yeah and also 3d recurces i took from here if you want https://science.nasa.gov/3d-resources/ (nasa 3d models)
this is video of my gameplay of the game and i like it like this is what i wanted to create but there is more to presice like landing on other planets crashes and more. you can play it right now there https://zhirkoalexander-maker.github.io/ellipse/ the game isnt finshed yet but if you want to play here. :)
today nothing special in this devlog i fixed some bugs that were glitching the game. and added so you can actualy see the rocket in the vehicle assembly and i am going to make this better. and if you want to know the bugs i fixed and what i added (bet you dont) but i am still going to write that cs it need to be in the devlog. soo i fixed thet the roket couldnt land properly on the planets and wasnt crashing if the speed was to fast (more than 30 m/s) also fixed that the earth gravity was to strong and you couldnt tke off cs your fuel was running yout to fast. also added that the rocket have weight so if your rocket is to heavy you cant lift od aaand i added the sun day and night. if you made it here i am impressed (pls follow?) ok ok i am joking by have a good day (or night or evening or lunch or morning or 1 oclock or 2 or clock or….) ok see ya :) (follow @paper_01 )
today added the sun and added the debug screen to see what wrong (debug was very hard even harder than the game(wasted 5 h on it)) and i think i am going to add the guide in the menu(there is help button but it dosnt work yet) soo i think i is all for today and have a good thms :)
hello. ehhhhh….. i dont think you know how much love and my life i gave to this game and this is the best i can do. when i add new things there are 2 new bugs and that was happening for more than a 100 times. i dont think i will end this game cs i and tired. sorry fellas.(dont judge my devlogs please cs i spend most time coding) sorry and see you in another 10 h
hi everyone today i made this cool crash animation that shows up when you try to land on a planet faster than 30 m/s (i think i might change it to higher soon like to 70 m/s so it will be easier to land) and i am working on a landing porcess but it is so hard and idk what to do but i want to do it myself without ai so sorry if it will be trash and sorry for the rocket details i am just so bad at drawing especially 3d models (i trided hard)and thats all. Oh and i changed the warp a lil bit so it dosent take you 5 mins to fly to the jupiter (warp is q and e buttons) oh and i added sas (autopilot) so if you dont want to fly to the moon yourself ( its preery hard) you can just press sas and sellect the planet but still it is preety much a concepcion but il try my best to do it thnks for reading bye :)
helloooo everyone and today i officially ended my project. jst added a new model of the rocket ( cs it looked bad in my opinion ) and in the start if you joined for the first time there will be a guide waiting for you ( kinda struggled on that one ) and added this legs that hold the rocket when it is about to launch. I very wanted to add more things about the game to this devlog but if i will be adding here every feature it would cost me like 8 h so sorry but you can always check it out yourself here https://zhirkoalexander-maker.github.io/ellipse/ oh and i changed the game name from ellipse to challanger ( yeah that spaceship that exploded back in 1990 (sorry dont know the real date)) cs the game with name ellipse alredy exsit bla bla bla. oookey this is the end so thanks every one for beeng here and buy ( for some one who is rating my game pls dont rate me hard i am a starter and my dad helped me a lot and i am jst so bad in english ) btw if anybody wanted to know i am saving up on a bambulab mini ok soo now its the real end so bye and see you later :)
hello dear testers i wrote yes i wrote this game with help of ai but now i got 35 procent ai ( like the autopilot is ai and map is ai ( on map just planets)) everithing else i wrote myself with the help of my dad . Please may you stop rejecting my project again and again ( i am so sorry i cant do more of this cs i am in 8 grade ant only on this week i had 9 tests ( this includes piano that i play)) i just did everithing i could to this project sorry and bye
Ships:
Hello dear tester i made this game cs i one time i stumbled across game like that that i liked but i wanted to add a phew things to it cs i liked it but it wasnt my game so i created my own with my own features. I am very proud that i made autopilot and guide i think that was the hardest things to do ( and physics od course like gravity and whatewer ). What do you need to know to play? i think you only need to know that arrow up it the throttle up and arrow down is throttle down and also you need to know that wars is the q and e buttoms map is m and you dont need to worry about autopilot doing strange things it will do it just don touch it cs it will turn off and remember that the starter rocket can fly to the moon but not back ( cs there is not enough fuel) so if you wanted to go back to earth you would need to build a larger rocket and i think thats all . good luck testing it and have a good morning/afternoon/evening/night bye :)...
|
1792856904.458555
|
1792943304.458555
|
|
29755
|
My own site! by @zhirkopro115 | Stardance
|
zhirkopro115
|
0
|
0.31
|
0
|
[]
|
[{"post_id": 20662, "ts": "202 [{"post_id": 20662, "ts": "2026-07-02T10:01:23Z", "hours": 0.3075, "text": "i created this web and honestly for me by 18 mins this is cool. i added the homepage button that leads you to the text (this page is cool) and i am planing to add a minigame and quiz about me"}]...
|
Title: My own site! by @zhirkopro115 | Stardance
Title: My own site! by @zhirkopro115 | Stardance
Devlogs:
i created this web and honestly for me by 18 mins this is cool. i added the homepage button that leads you to the text (this page is cool) and i am planing to add a minigame and quiz about me...
|
1792655642.7025113
|
1793260442.7025113
|
|
35783
|
my APOD site by @zhirkopro115 | Stardance
|
zhirkopro115
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: my APOD site by @zhirkopro115 | Stardance
|
1792518721.1722548
|
1793123521.1722548
|
|
68676
|
plane game by @zhirkopro115 | Stardance
|
zhirkopro115
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: plane game by @zhirkopro115 | Stardance
|
1792472071.6580617
|
1793076871.6580617
|
|
19988
|
My awesome macropad! by @zhichenlim | Stardance
|
zhichenlim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zhichenlim | Stard Title: My awesome macropad! by @zhichenlim | Stardance...
|
1792623077.5030622
|
1793227877.5030622
|
|
33226
|
Cosmic Non-Sticky Logs by @zhengkaitaken | Stardan Cosmic Non-Sticky Logs by @zhengkaitaken | Stardance...
|
zhengkaitaken
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cosmic Non-Sticky Logs by @zhengkaitaken | Title: Cosmic Non-Sticky Logs by @zhengkaitaken | Stardance...
|
1792558153.7434118
|
1793162953.7434118
|
|
46287
|
Frictionless by @zhelly | Stardance
|
zhelly
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @zhelly | Stardance
|
1792658970.0592825
|
1793263770.0592825
|
|
20162
|
My first slack bot! by @zharassova_adilya | Starda My first slack bot! by @zharassova_adilya | Stardance...
|
zharassova_adilya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zharassova_adilya | Title: My first slack bot! by @zharassova_adilya | Stardance...
|
1792522418.900885
|
1793127218.900885
|
|
26437
|
Wireless Piano by @zhal | Stardance
|
zhal
|
1
|
11.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-02T13:24:53Z", "hours": 11.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What did you make? I built a 12-key ESP32-powered Piano that has a WIFI Mode that hosts its own webpage. Users can connect to the ESP32 from any device on the same network and play piano notes through their web browser. Also it has a Standalone Mode were you can directly connect it to a speaker. The project combines 3D printing, electronics, programming, and web development into a portable instrument. What was challenging? The biggest challenge was getting the ESP32 and the web interface to communicate reliably while keeping the piano responsive. Designing and fitting the 3D-printed enclosure around all the electronics and wiring also required several iterations. What are you proud of? I’m most proud of creating a system that feels simple to use despite combining several technologies. Instead of needing a dedicated app or speaker, anyone on the same Wi-Fi network can open a browser and immediately start playing. I’m also proud that the project combines hardware, software, and 3D design into one product. What should people know so they can test your project? To test the project: Power on the ESP32. Ensure your device is connected to the same Wi-Fi network as the ESP32. Open the IP address shown in the Serial Monitor. (if not shown press the enable button on the ESP32) Press the physical keys or use the on-screen piano keyboard. Your device’s volume should be turned on since the audio is generated by the web browser rather than the ESP32 itself if in WIFI Mode.", "repo": "https://github.com/zhal8403/Piano", "demo": ""}]...
|
[{"post_id": 20486, "ts": "202 [{"post_id": 20486, "ts": "2026-07-02T02:52:09Z", "hours": 3.955, "text": "I have assembled the 12 key piano and I have adjusted code in the site to fit it I also have fixed many bugs and I’ve also made it have 2 modes. It has a Wi-Fi mode where you can connect to the site, but you can also use the site with your mouse and play or you can open it on your phone and use touchscreen. The second mode is the standalone mode which you can connect to a speaker to play with the board without using a device and I have fully enclosed the piano so you can transport it"}, {"post_id": 18775, "ts": "2026-06-29T23:50:44Z", "hours": 1.9331, "text": "added audio thats plays when keys are pressed connected to the keys and that"}, {"post_id": 18349, "ts": "2026-06-29T13:52:34Z", "hours": 0.7556, "text": "finished printing and assembling the mini version of the piano"}, {"post_id": 18043, "ts": "2026-06-29T00:35:35Z", "hours": 2.5472, "text": "Designed 12 key and 5 key pianos planning on adding more for electronic storage next"}, {"post_id": 17542, "ts": "2026-06-28T11:31:19Z", "hours": 1.2561, "text": "created simple webpage to receive esp32 signals from switches and a starter keyboard display taht shows what keys been pressed"}, {"post_id": 17344, "ts": "2026-06-28T02:57:20Z", "hours": 0.8108, "text": "ESP32 code that hosts a web server and sends piano key states to a browser."}]...
|
Title: Wireless Piano by @zhal | Stardance
Devlog Title: Wireless Piano by @zhal | Stardance
Devlogs:
ESP32 code that hosts a web server and sends piano key states to a browser.
created simple webpage to receive esp32 signals from switches and a starter keyboard display taht shows what keys been pressed
Designed 12 key and 5 key pianos planning on adding more for electronic storage next
finished printing and assembling the mini version of the piano
added audio thats plays when keys are pressed connected to the keys and that
I have assembled the 12 key piano and I have adjusted code in the site to fit it I also have fixed many bugs and I’ve also made it have 2 modes. It has a Wi-Fi mode where you can connect to the site, but you can also use the site with your mouse and play or you can open it on your phone and use touchscreen. The second mode is the standalone mode which you can connect to a speaker to play with the board without using a device and I have fully enclosed the piano so you can transport it
Ships:
What did you make? I built a 12-key ESP32-powered Piano that has a WIFI Mode that hosts its own webpage. Users can connect to the ESP32 from any device on the same network and play piano notes through their web browser. Also it has a Standalone Mode were you can directly connect it to a speaker. The project combines 3D printing, electronics, programming, and web development into a portable instrument. What was challenging? The biggest challenge was getting the ESP32 and the web interface to communicate reliably while keeping the piano responsive. Designing and fitting the 3D-printed enclosure around all the electronics and wiring also required several iterations. What are you proud of? I’m most proud of creating a system that feels simple to use despite combining several technologies. Instead of needing a dedicated app or speaker, anyone on the same Wi-Fi network can open a browser and immediately start playing. I’m also proud that the project combines hardware, software, and 3D design into one product. What should people know so they can test your project? To test the project: Power on the ESP32. Ensure your device is connected to the same Wi-Fi network as the ESP32. Open the IP address shown in the Serial Monitor. (if not shown press the enable button on the ESP32) Press the physical keys or use the on-screen piano keyboard. Your device’s volume should be turned on since the audio is generated by the web browser rather than the ESP32 itself if in WIFI Mode....
|
1792817610.044074
|
1792904010.044074
|
|
30393
|
StudyOS by @zhal | Stardance
|
zhal
|
1
|
24.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-14T17:29:04Z", "hours": 24.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What did you make? I built StudyOS, an AI-powered student dashboard that connects with Google Calendar to display upcoming events and generate personalized daily briefings. Instead of checking multiple apps, students get a single dashboard with their schedule, upcoming deadlines, and AI-generated advice for the day. (AI is still in beta) What was challenging? The biggest challenge was integrating multiple technologies together. Setting up Google OAuth, retrieving events from every calendar, deploying the website, and running a local AI model with Ollama all required debugging and learning new tools. I also had to figure out how to make the AI generate useful daily briefings instead of generic responses. What are you proud of? I’m most proud that the project actually works end-to-end. Users can sign in with Google, view all of their upcoming calendar events, and receive an AI-generated morning briefing based on their real schedule. What should people know so they can test it? The live demo is available here: https://study-website-88jo-4xbo1kols-zhal8403s-projects.vercel.app/ To fully test the project: Sign in with a Google account. Allow Calendar permissions. Make sure your Google Calendar has a few upcoming events. The dashboard will display your upcoming events and generate a personalized daily briefing based on your schedule. Note: The AI runs locally using Ollama, so the hosted demo currently uses a placeholder briefing. Running the project locally with Ollama enabled provides the full AI experience.", "repo": "https://github.com/zhal8403/Study-Website", "demo": "https://study-website-941c.vercel.app/"}]...
|
[{"post_id": 28392, "ts": "202 [{"post_id": 28392, "ts": "2026-07-14T16:58:52Z", "hours": 1.3714, "text": "Dev Log #6 – Local AI Integration with Ollama Overview Today I addeed a completely local AI model using Ollama . I researched local large language models and decided to integrate the Llama 3.2 3B model through Ollama. What I Worked On Installed Ollama and downloaded the llama3.2:3b model. Fixed the issue where PowerShell could not recognize the ollama command by updating my system PATH . Learned that Ollama automatically starts its own server, so running ollama serve again caused a port conflict. Created a Node.js backend using Express and CORS . Connected the backend to Ollama’s local API. Updated the React frontend to send AI requests to my local backend instead of OpenRouter. Removed the dependency on paid AI APIs. Challenges One of the biggest challenges was getting the backend running correctly. I accidentally tried to run server.js before creating the file, which caused a MODULE_NOT_FOUND error. After creating the server and installing the required packages, I was able to start it successfully. Another challenge was that the AI initially hallucinated events like holidays and birthdays that weren’t actually on my calendar. To fix this, I rewrote the prompt to clearly instruct the model to only use the calendar events provided and never invent additional information. Improvements I redesigned the AI briefing prompt so it now: Uses only events from the next 7 days . Creates a structured daily briefing. Highlights upcoming due dates, tests, meetings, and deadlines. Suggests what to focus on for the day. Ends with a short motivational message. Avoids generating fake events. Result The AI summary feature now runs entirely on my own computer with: No API keys No usage limits Faster response times Better privacy because calendar data never leaves my computer. The morning briefing is much more useful and feels like a real student assistant instead of a generic chatbot."}, {"post_id": 25646, "ts": "2026-07-10T01:49:24Z", "hours": 3.4958, "text": "Devlog #5 — Calendar event control complete I focused on finishing the calendar management system for StudyOS. My goal was to make it possible to fully manage Google Calendar events without leaving the app. Building the Event Modal The first major feature I completed was the New Event Modal . Users can now enter: Event title Description Location Start date and time End date and time I originally built the modal using a standard HTML form, but I ran into issues where React would disconnect the form before it could submit. Instead of continuing to fight that problem, I redesigned the modal to use React state and button click handlers. This made creating events much more reliable. Editing and Deleting Events After creating events worked, I added the ability to edit them. Clicking an event now opens the same modal with all of the event information already filled in. Users can: Update event information Delete the event Cancel without making changes This required connecting the app to the Google Calendar Update and Delete API endpoints and refreshing the calendar after every change so the UI always stays up to date. Multiple Calendar Support One feature I really wanted was support for multiple calendars. Instead of always saving events in the primary calendar, the app now retrieves every calendar connected to the user’s Google account. A dropdown menu allows users to choose exactly where a new event should be saved. Bug Fixes Along the way I fixed several issues: Fixed React form submission problems by replacing the form with state-based inputs. Fixed the event modal not updating correctly when switching between events. Fixed the calendar not refreshing after creating, editing, or deleting events. Fixed event selection in the Today , Week , and Month views. Fixed creating events in calendars other than the primary calendar. Current Features The calendar now supports: Today , Week , and Month views Searching events Creating new events Editing existing events Deleting events Selecting which Google Calendar an event belongs to Automatic refresh after every change Next Steps Add recurring event support Add event color customization Add reminders and notifications Improve the calendar interface Add drag-and-drop scheduling I’m really happy with how this update turned out because the calendar has gone from being a read-only viewer to a fully functional event manager."}, {"post_id": 25103, "ts": "2026-07-09T02:57:29Z", "hours": 7.4456, "text": "Devlog #4 – Gmail, Google Classroom, and Calendar Improvements What I Worked On I focused on connecting more Google services to StudyOS and improving how calendar data is displayed. Google Classroom I created a new Classroom page that automatically loads my Google Classroom courses and displays assignments from each class. Features Added Connected to the Google Classroom API. Loaded all enrolled courses. Retrieved coursework from every class. Combined assignments into one list. Sorted assignments by due date. Displayed the class name with each assignment. Problems Solved Fixed OAuth authentication issues. Added the required Google Classroom scopes. Debugged 401 Unauthorized and 403 Permission Denied errors. Learned that teachers can restrict API access to coursework, causing some assignments to be unavailable. Gmail I continued improving Gmail integration. Improvements Better loading of Gmail messages. More reliable Google authentication. Cleaner organization for displaying emails. Google Calendar The calendar received several major improvements. Features Added Combined events from every calendar instead of only the primary calendar. Added search functionality. Added Today, Week, and Month views. Added Previous, Next, and Today navigation buttons. Added support for changing weeks and months without reloading. Sorted all events by date. Bug Fixes Fixed missing events caused by incorrect API parameters. Fixed events not appearing from shared calendars. Fixed date filtering logic. Corrected React state issues with currentDate . Fixed navigation bugs while switching between calendar views. Next Steps Create and edit calendar events directly from StudyOS. Add assignment completion tracking. Display Gmail labels and unread counts. Improve the calendar UI with drag-and-drop support. Connect Google Drive files to assignments."}, {"post_id": 22805, "ts": "2026-07-05T11:55:48Z", "hours": 9.0164, "text": "Devlog #3 — Making the Calendar Page and Dashboard This week, I worked on two of the biggest parts of StudyOS so far: the Calendar page and the Dashboard . Calendar Page I started turning the Calendar page into something more useful than a simple event list. I added different views for Today , Week , and Month , making it easier to see upcoming events in different ways. I also improved how events are displayed by adding: Expandable event descriptions A cleaner event layout A structure that’s easier to build on with more features later These changes make the calendar feel much closer to a real productivity app. Dashboard I also redesigned the Dashboard to work more like a student command center. One of the biggest improvements was turning the upcoming events section into a scrollable card . This keeps the dashboard clean even when there are lots of events and prevents long lists from stretching the page. This new layout also leaves room for future dashboard widgets, such as: AI daily briefing Assignment priority Recent activity What’s Next? Next, I plan to continue improving the Calendar page by adding: Creating events Editing events Deleting events After that, I’ll begin building more dashboard widgets to make StudyOS feel like a true all-in-one student workspace."}, {"post_id": 21852, "ts": "2026-07-04T00:14:51Z", "hours": 2.0331, "text": "Devlog #2 – Switching to React & Adding Google Authentication Today I upgraded StudyOS from a basic HTML/CSS/JavaScript project into a React (Vite) application, and then added Google Sign-In authentication. This was a major step toward turning StudyOS into a real student productivity platform instead of just a static UI. StudyOS is designed as a Student Command Center, where students can eventually manage Gmail, Google Calendar, Drive, Classroom, and assignments all in one place. Part 1 – Switching to React I migrated the project into React using Vite to make it more scalable and closer to how real production apps are built. What I changed Converted project from HTML/CSS/JS → React (Vite) Broke UI into reusable components: Sidebar Header Pages (Dashboard, Gmail, Calendar, etc.) Implemented single-page navigation (no page reloads) Why I switched React makes it much easier to: Manage multiple pages (like Gmail + Calendar + Drive) Handle user login state Build dynamic dashboards Scale the project into a real app Part 2 – Google Authentication After setting up React, I integrated Google Sign-In so users can log into StudyOS using their Google account. What I implemented Installed @react-oauth /google Added JWT decoding to extract user info Configured Google OAuth in React Created login flow using Google Identity Services Fixed OAuth issues including: Displayed user profile after login: Name Profile picture Restricted app access until user is signed in What works now Sidebar navigation between pages Dashboard layout structure Google Sign-In authentication system User session state (logged in / logged out) Profile display in header after login Challenges The biggest issue was Google OAuth configuration. I initially encountered: Error 400: origin_mismatch This happened because the correct localhost URLs were not added in the Google Cloud Console. Fix Added the following to Authorized JavaScript origins: http://localhost:5173 http://127.0.0.1:5173 After fixing this, Google Sign-In worked successfully. Next steps Connect Google Calendar API (real events) Connect Gmail API (inbox preview) Connect Google Drive API (file access) Build Assignment Workspace system Add AI Daily Briefing (smart planning system) Implement “Stay signed in” persistence Improve UI with modern styling (glassmorphism + animations)"}, {"post_id": 21721, "ts": "2026-07-03T20:14:35Z", "hours": 0.7917, "text": "Devlog #1 - Building the Base of StudyOS Time Spent: 45 minutes Today I started building StudyOS , a student productivity app that combines Google Classroom, Gmail, Calendar, Drive, and other Google services into one place. My goal is to reduce the number of tabs students need to keep open and make staying organized much easier. What I accomplished Created the project in VS Code. Built the basic dashboard layout. Added a sidebar for navigation. Created a top navigation bar with a search bar and a placeholder Google Sign-In button. Designed the first dashboard cards: Today’s Summary AI Briefing Focus Session Challenges I spent some time deciding how I wanted the app to be organized. Instead of making another simple dashboard, I decided to build it like a Student Command Center where everything can eventually be managed from one place. Next Steps Create a login page. Add Google Sign-In. Keep users signed in if they choose. Connect Google Calendar. Connect Gmail. Add the AI Daily Briefing. Begin building the Assignment Workspace. I’m really happy with the progress so far. Even though it’s only the first version, I now have a solid foundation to build on. Next I’ll start adding real functionality instead of placeholder content."}]...
|
Title: StudyOS by @zhal | Stardance
Devlogs:
Devl Title: StudyOS by @zhal | Stardance
Devlogs:
Devlog #1 - Building the Base of StudyOS Time Spent: 45 minutes Today I started building StudyOS , a student productivity app that combines Google Classroom, Gmail, Calendar, Drive, and other Google services into one place. My goal is to reduce the number of tabs students need to keep open and make staying organized much easier. What I accomplished Created the project in VS Code. Built the basic dashboard layout. Added a sidebar for navigation. Created a top navigation bar with a search bar and a placeholder Google Sign-In button. Designed the first dashboard cards: Today’s Summary AI Briefing Focus Session Challenges I spent some time deciding how I wanted the app to be organized. Instead of making another simple dashboard, I decided to build it like a Student Command Center where everything can eventually be managed from one place. Next Steps Create a login page. Add Google Sign-In. Keep users signed in if they choose. Connect Google Calendar. Connect Gmail. Add the AI Daily Briefing. Begin building the Assignment Workspace. I’m really happy with the progress so far. Even though it’s only the first version, I now have a solid foundation to build on. Next I’ll start adding real functionality instead of placeholder content.
Devlog #2 – Switching to React & Adding Google Authentication Today I upgraded StudyOS from a basic HTML/CSS/JavaScript project into a React (Vite) application, and then added Google Sign-In authentication. This was a major step toward turning StudyOS into a real student productivity platform instead of just a static UI. StudyOS is designed as a Student Command Center, where students can eventually manage Gmail, Google Calendar, Drive, Classroom, and assignments all in one place. Part 1 – Switching to React I migrated the project into React using Vite to make it more scalable and closer to how real production apps are built. What I changed Converted project from HTML/CSS/JS → React (Vite) Broke UI into reusable components: Sidebar Header Pages (Dashboard, Gmail, Calendar, etc.) Implemented single-page navigation (no page reloads) Why I switched React makes it much easier to: Manage multiple pages (like Gmail + Calendar + Drive) Handle user login state Build dynamic dashboards Scale the project into a real app Part 2 – Google Authentication After setting up React, I integrated Google Sign-In so users can log into StudyOS using their Google account. What I implemented Installed @react-oauth /google Added JWT decoding to extract user info Configured Google OAuth in React Created login flow using Google Identity Services Fixed OAuth issues including: Displayed user profile after login: Name Profile picture Restricted app access until user is signed in What works now Sidebar navigation between pages Dashboard layout structure Google Sign-In authentication system User session state (logged in / logged out) Profile display in header after login Challenges The biggest issue was Google OAuth configuration. I initially encountered: Error 400: origin_mismatch This happened because the correct localhost URLs were not added in the Google Cloud Console. Fix Added the following to Authorized JavaScript origins: http://localhost:5173 http://127.0.0.1:5173 After fixing this, Google Sign-In worked successfully. Next steps Connect Google Calendar API (real events) Connect Gmail API (inbox preview) Connect Google Drive API (file access) Build Assignment Workspace system Add AI Daily Briefing (smart planning system) Implement “Stay signed in” persistence Improve UI with modern styling (glassmorphism + animations)
Devlog #3 — Making the Calendar Page and Dashboard This week, I worked on two of the biggest parts of StudyOS so far: the Calendar page and the Dashboard . Calendar Page I started turning the Calendar page into something more useful than a simple event list. I added different views for Today , Week , and Month , making it easier to see upcoming events in different ways. I also improved how events are displayed by adding: Expandable event descriptions A cleaner event layout A structure that’s easier to build on with more features later These changes make the calendar feel much closer to a real productivity app. Dashboard I also redesigned the Dashboard to work more like a student command center. One of the biggest improvements was turning the upcoming events section into a scrollable card . This keeps the dashboard clean even when there are lots of events and prevents long lists from stretching the page. This new layout also leaves room for future dashboard widgets, such as: AI daily briefing Assignment priority Recent activity What’s Next? Next, I plan to continue improving the Calendar page by adding: Creating events Editing events Deleting events After that, I’ll begin building more dashboard widgets to make StudyOS feel like a true all-in-one student workspace.
Devlog #4 – Gmail, Google Classroom, and Calendar Improvements What I Worked On I focused on connecting more Google services to StudyOS and improving how calendar data is displayed. Google Classroom I created a new Classroom page that automatically loads my Google Classroom courses and displays assignments from each class. Features Added Connected to the Google Classroom API. Loaded all enrolled courses. Retrieved coursework from every class. Combined assignments into one list. Sorted assignments by due date. Displayed the class name with each assignment. Problems Solved Fixed OAuth authentication issues. Added the required Google Classroom scopes. Debugged 401 Unauthorized and 403 Permission Denied errors. Learned that teachers can restrict API access to coursework, causing some assignments to be unavailable. Gmail I continued improving Gmail integration. Improvements Better loading of Gmail messages. More reliable Google authentication. Cleaner organization for displaying emails. Google Calendar The calendar received several major improvements. Features Added Combined events from every calendar instead of only the primary calendar. Added search functionality. Added Today, Week, and Month views. Added Previous, Next, and Today navigation buttons. Added support for changing weeks and months without reloading. Sorted all events by date. Bug Fixes Fixed missing events caused by incorrect API parameters. Fixed events not appearing from shared calendars. Fixed date filtering logic. Corrected React state issues with currentDate . Fixed navigation bugs while switching between calendar views. Next Steps Create and edit calendar events directly from StudyOS. Add assignment completion tracking. Display Gmail labels and unread counts. Improve the calendar UI with drag-and-drop support. Connect Google Drive files to assignments.
Devlog #5 — Calendar event control complete I focused on finishing the calendar management system for StudyOS. My goal was to make it possible to fully manage Google Calendar events without leaving the app. Building the Event Modal The first major feature I completed was the New Event Modal . Users can now enter: Event title Description Location Start date and time End date and time I originally built the modal using a standard HTML form, but I ran into issues where React would disconnect the form before it could submit. Instead of continuing to fight that problem, I redesigned the modal to use React state and button click handlers. This made creating events much more reliable. Editing and Deleting Events After creating events worked, I added the ability to edit them. Clicking an event now opens the same modal with all of the event information already filled in. Users can: Update event information Delete the event Cancel without making changes This required connecting the app to the Google Calendar Update and Delete API endpoints and refreshing the calendar after every change so the UI always stays up to date. Multiple Calendar Support One feature I really wanted was support for multiple calendars. Instead of always saving events in the primary calendar, the app now retrieves every calendar connected to the user’s Google account. A dropdown menu allows users to choose exactly where a new event should be saved. Bug Fixes Along the way I fixed several issues: Fixed React form submission problems by replacing the form with state-based inputs. Fixed the event modal not updating correctly when switching between events. Fixed the calendar not refreshing after creating, editing, or deleting events. Fixed event selection in the Today , Week , and Month views. Fixed creating events in calendars other than the primary calendar. Current Features The calendar now supports: Today , Week , and Month views Searching events Creating new events Editing existing events Deleting events Selecting which Google Calendar an event belongs to Automatic refresh after every change Next Steps Add recurring event support Add event color customization Add reminders and notifications Improve the calendar interface Add drag-and-drop scheduling I’m really happy with how this update turned out because the calendar has gone from being a read-only viewer to a fully functional event manager.
Dev Log #6 – Local AI Integration with Ollama Overview Today I addeed a completely local AI model using Ollama . I researched local large language models and decided to integrate the Llama 3.2 3B model through Ollama. What I Worked On Installed Ollama and downloaded the llama3.2:3b model. Fixed the issue where PowerShell could not recognize the ollama command by updating my system PATH . Learned that Ollama automatically starts its own server, so running ollama serve again caused a port conflict. Created a Node.js backend using Express and CORS . Connected the backend to Ollama’s local API. Updated the React frontend to send AI requests to my local backend instead of OpenRouter. Removed the dependency on paid AI APIs. Challenges One of the biggest challenges was getting the backend running correctly. I accidentally tried to run server.js before creating the file, which caused a MODULE_NOT_FOUND error. After creating the server and installing the required packages, I was able to start it successfully. Another challenge was that the AI initially hallucinated events like holidays and birthdays that weren’t actually on my calendar. To fix this, I rewrote the prompt to clearly instruct the model to only use the calendar events provided and never invent additional information. Improvements I redesigned the AI briefing prompt so it now: Uses only events from the next 7 days . Creates a structured daily briefing. Highlights upcoming due dates, tests, meetings, and deadlines. Suggests what to focus on for the day. Ends with a short motivational message. Avoids generating fake events. Result The AI summary feature now runs entirely on my own computer with: No API keys No usage limits Faster response times Better privacy because calendar data never leaves my computer. The morning briefing is much more useful and feels like a real student assistant instead of a generic chatbot.
Ships:
What did you make? I built StudyOS, an AI-powered student dashboard that connects with Google Calendar to display upcoming events and generate personalized daily briefings. Instead of checking multiple apps, students get a single dashboard with their schedule, upcoming deadlines, and AI-generated advice for the day. (AI is still in beta) What was challenging? The biggest challenge was integrating multiple technologies together. Setting up Google OAuth, retrieving events from every calendar, deploying the website, and running a local AI model with Ollama all required debugging and learning new tools. I also had to figure out how to make the AI generate useful daily briefings instead of generic responses. What are you proud of? I’m most proud that the project actually works end-to-end. Users can sign in with Google, view all of their upcoming calendar events, and receive an AI-generated morning briefing based on their real schedule. What should people know so they can test it? The live demo is available here: https://study-website-88jo-4xbo1kols-zhal8403s-projects.vercel.app/ To fully test the project: Sign in with a Google account. Allow Calendar permissions. Make sure your Google Calendar has a few upcoming events. The dashboard will display your upcoming events and generate a personalized daily briefing based on your schedule. Note: The AI runs locally using Ollama, so the hosted demo currently uses a placeholder briefing. Running the project locally with Ollama enabled provides the full AI experience....
|
1792817600.1676052
|
1792904000.1676052
|
|
35265
|
Sketch-Print by @zhal | Stardance
|
zhal
|
1
|
5.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-18T05:47:14Z", "hours": 5.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "modified 3d printer that can plot and draw whatever you want", "repo": "https://github.com/zhal8403/Sketch-Print", "demo": ""}]...
|
[{"post_id": 29267, "ts": "202 [{"post_id": 29267, "ts": "2026-07-16T02:28:06Z", "hours": 5.0514, "text": "Devlog #1 – SketchPrint: Making an Ender 3 drawing mod I wanted to build something that combined software, hardware, and creativity instead of making another website. I came up with SketchPrint , a project that transforms an Ender 3 3D printer into a pen plotter capable of drawing images, text, and artwork on paper. The project started with researching how pen plotters work and figuring out how I could attach markers to the printer. I designed and printed different pen holder ideas before deciding on a design that securely holds a marker while still allowing the printer to move freely. I also researched different methods for supporting multiple pen colors and explored ideas like a rotating pen carousel. Once the hardware concept was working, I started building the software. I created a React application that lets users upload images and prepares them for drawing. One of the biggest challenges was converting normal images into clean line art that the printer could actually draw. I experimented with multiple tracing libraries and eventually integrated image tracing into the application. I also spent a lot of time adjusting line thickness, scaling, and positioning so drawings would fit correctly on the page. Another major challenge was generating G-code. Since the printer was originally designed to print plastic instead of draw with a marker, I had to learn how plotting G-code works and adapt it for pen movements. I tested different movement speeds, pen heights, and drawing paths while making sure the marker stayed on the paper without dragging or damaging it. Throughout development I encountered many technical issues, including: React import errors Canvas initialization bugs Image processing and tracing issues G-code positioning problems Marker calibration challenges Printer alignment and testing Solving these problems required reading documentation, debugging code, and testing many different approaches before finding solutions that worked reliably. What I’m Most Proud Of I’m most proud that SketchPrint combines mechanical design, software development, and electronics into one project. Instead of only building a website, I created a complete system that takes an uploaded image, processes it into line art, generates G-code, and prepares it for an Ender 3 to recreate with a marker. What People Should Know The project is designed for an Ender 3 configured as a pen plotter. Marker thickness and printer calibration affect drawing quality. Different paper sizes may require scaling adjustments."}]...
|
Title: Sketch-Print by @zhal | Stardance
Devlogs: Title: Sketch-Print by @zhal | Stardance
Devlogs:
Devlog #1 – SketchPrint: Making an Ender 3 drawing mod I wanted to build something that combined software, hardware, and creativity instead of making another website. I came up with SketchPrint , a project that transforms an Ender 3 3D printer into a pen plotter capable of drawing images, text, and artwork on paper. The project started with researching how pen plotters work and figuring out how I could attach markers to the printer. I designed and printed different pen holder ideas before deciding on a design that securely holds a marker while still allowing the printer to move freely. I also researched different methods for supporting multiple pen colors and explored ideas like a rotating pen carousel. Once the hardware concept was working, I started building the software. I created a React application that lets users upload images and prepares them for drawing. One of the biggest challenges was converting normal images into clean line art that the printer could actually draw. I experimented with multiple tracing libraries and eventually integrated image tracing into the application. I also spent a lot of time adjusting line thickness, scaling, and positioning so drawings would fit correctly on the page. Another major challenge was generating G-code. Since the printer was originally designed to print plastic instead of draw with a marker, I had to learn how plotting G-code works and adapt it for pen movements. I tested different movement speeds, pen heights, and drawing paths while making sure the marker stayed on the paper without dragging or damaging it. Throughout development I encountered many technical issues, including: React import errors Canvas initialization bugs Image processing and tracing issues G-code positioning problems Marker calibration challenges Printer alignment and testing Solving these problems required reading documentation, debugging code, and testing many different approaches before finding solutions that worked reliably. What I’m Most Proud Of I’m most proud that SketchPrint combines mechanical design, software development, and electronics into one project. Instead of only building a website, I created a complete system that takes an uploaded image, processes it into line art, generates G-code, and prepares it for an Ender 3 to recreate with a marker. What People Should Know The project is designed for an Ender 3 configured as a pen plotter. Marker thickness and printer calibration affect drawing quality. Different paper sizes may require scaling adjustments.
Ships:
modified 3d printer that can plot and draw whatever you want...
|
1792756606.427711
|
1792843006.427711
|
|
37005
|
Tank by @zhal | Stardance
|
zhal
|
0
|
3.94
|
0
|
[]
|
[{"post_id": 33956, "ts": "202 [{"post_id": 33956, "ts": "2026-07-24T09:45:47Z", "hours": 3.9378, "text": "Devlog 1 – Tank Robot Project Today I started designing and building my simple tank robot. The goal is to create a small tracked robot controlled by an ESP32, with two TT gear motors powered through an L298N motor driver. Progress Designed the base chassis in CAD. Designed the gears and treads. 3D printed the completed parts. Began assembling the robot. Wire the TT motors to the motor driver. Write the ESP32 code to control the motors. Current Status The base of the tank has been completed in CAD, along with the gears and treads. I have not finished designing the top section yet. Once the remaining CAD work is complete, I will print the top and continue assembling the robot. Next Steps Finish designing the top of the chassis. 3D print the remaining parts. Write the ESP32 code to control the motors. Test the tank’s movement and make improvements as needed. Overall, this was a good start to the project. The mechanical design is progressing well, and the next milestone is completing the CAD model so assembly and programming can begin."}]...
|
Title: Tank by @zhal | Stardance
Devlogs:
Devlog Title: Tank by @zhal | Stardance
Devlogs:
Devlog 1 – Tank Robot Project Today I started designing and building my simple tank robot. The goal is to create a small tracked robot controlled by an ESP32, with two TT gear motors powered through an L298N motor driver. Progress Designed the base chassis in CAD. Designed the gears and treads. 3D printed the completed parts. Began assembling the robot. Wire the TT motors to the motor driver. Write the ESP32 code to control the motors. Current Status The base of the tank has been completed in CAD, along with the gears and treads. I have not finished designing the top section yet. Once the remaining CAD work is complete, I will print the top and continue assembling the robot. Next Steps Finish designing the top of the chassis. 3D print the remaining parts. Write the ESP32 code to control the motors. Test the tank’s movement and make improvements as needed. Overall, this was a good start to the project. The mechanical design is progressing well, and the next milestone is completing the CAD model so assembly and programming can begin....
|
1792518627.828424
|
1793123427.828424
|
|
38949
|
S.C.O.U.T. — Smart Companion for Operations, Utili S.C.O.U.T. — Smart Companion for Operations, Utility & Transport by @zhal | Stardance...
|
zhal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: S.C.O.U.T. — Smart Companion for Operations Title: S.C.O.U.T. — Smart Companion for Operations, Utility & Transport by @zhal | Stardance...
|
1792543708.6067758
|
1793148508.6067758
|
|
49471
|
zeypad by @zeyywq | Stardance
|
zeyywq
|
0
|
1.72
|
0
|
[]
|
[{"post_id": 48367, "ts": "202 [{"post_id": 48367, "ts": "2026-08-16T18:00:44Z", "hours": 1.7167, "text": "I made awesome progress on my hackpad project today! First, I finished the schematic and PCB design. Then, while working on the case, after wrestling a bit with 3D models in the KiCad libraries, I decided to skip them and switch to the cloud-based Onshape instead. We measured the PCB dimensions in KiCad as 25.654 x 54.991 mm, added a 0.4 mm tolerance for a sandwich mount design, and started our first sketch in Onshape. The project is slowly coming together!"}]...
|
Title: zeypad by @zeyywq | Stardance
Devlogs:
I m Title: zeypad by @zeyywq | Stardance
Devlogs:
I made awesome progress on my hackpad project today! First, I finished the schematic and PCB design. Then, while working on the case, after wrestling a bit with 3D models in the KiCad libraries, I decided to skip them and switch to the cloud-based Onshape instead. We measured the PCB dimensions in KiCad as 25.654 x 54.991 mm, added a 0.4 mm tolerance for a sandwich mount design, and started our first sketch in Onshape. The project is slowly coming together!...
|
1792594173.197818
|
1793198973.197818
|
|
60109
|
TODO by @zeyra | Stardance
|
zeyra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: TODO by @zeyra | Stardance
|
1792424850.2634838
|
1793029650.2634838
|
|
3173
|
My awesome macropad! by @zeyox | Stardance
|
zeyox
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zeyox | Stardance
|
1792748877.4242675
|
1793353677.4242675
|
|
3288
|
My first slack bot! by @zeyox | Stardance
|
zeyox
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zeyox | Stardance
|
1792712973.8059726
|
1793317773.8059726
|