|
17601
|
My very own WebOS by @theEclipse | Stardance
|
theEclipse
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @theEclipse | Stardanc Title: My very own WebOS by @theEclipse | Stardance...
|
1793490692.4592686
|
1794095492.4592686
|
|
17602
|
My very own WebOS by @Vanshika31 | Stardance
|
Vanshika31
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Vanshika31 | Stardanc Title: My very own WebOS by @Vanshika31 | Stardance...
|
1793335771.5226505
|
1793940571.5226505
|
|
17603
|
Untitled by @arno | Stardance
|
arno
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @arno | Stardance
|
1793548085.1014075
|
1794152885.1014075
|
|
17604
|
Untitled by @arno | Stardance
|
arno
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @arno | Stardance
|
1793342863.7029693
|
1793947663.7029693
|
|
17605
|
Helix by @arnsv | Stardance
|
arnsv
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Helix by @arnsv | Stardance
|
1793328521.7810163
|
1793933321.7810163
|
|
17606
|
My awesome macropad! by @Vanshika31 | Stardance
|
Vanshika31
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Vanshika31 | Stard Title: My awesome macropad! by @Vanshika31 | Stardance...
|
1793242544.157727
|
1793847344.157727
|
|
17607
|
My awesome macropad! by @sathvika | Stardance
|
sathvika
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sathvika | Stardan Title: My awesome macropad! by @sathvika | Stardance...
|
1793789734.9909892
|
1794394534.9909892
|
|
17608
|
Untitled project by @SammyD | Stardance
|
SammyD
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @SammyD | Stardance
|
1793188509.683475
|
1793793309.683475
|
|
17609
|
ayaan-malik-portfolio by @amalik_ellahi | Stardanc ayaan-malik-portfolio by @amalik_ellahi | Stardance...
|
amalik_ellahi
|
1
|
0.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-18T15:48:47Z", "hours": 0.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Built a personal portfolio website with a dark, shadowy design. Includes about me, skills, projects, and contact sections. Making the dark theme look polished while keeping text readable. Balancing contrast, spacing, and shadow effects. A cohesive dark aesthetic with smooth visual details. A cohesive dark aesthetic with smooth visual details. A modern, easy-to-use layout. To test it out, Open in a browser and check desktop/mobile responsiveness. Verify links, project cards, and contact actions. Ensure text remains readable on the dark background.", "repo": "https://github.com/amalikellahi-dot/ayaan-malik-portfolio", "demo": "https://amalikellahi-dot.github.io/ayaan-malik-portfolio/"}]...
|
[{"post_id": 11348, "ts": "202 [{"post_id": 11348, "ts": "2026-06-18T15:40:47Z", "hours": 0.2153, "text": "Worked on my Ayaan Malik personal portfolio website. I’m building a dark, game-inspired “status window” style portfolio that introduces who I am, my interests, and my personal brand in a more unique way. Today I focused on the homepage layout, navigation, images, visual theme, and overall polish so the site feels less like a basic template and more like something that actually represents me. I also worked on making the design cleaner, more organized, and ready to eventually deploy through GitHub Pages."}]...
|
Title: ayaan-malik-portfolio by @amalik_ellahi | S Title: ayaan-malik-portfolio by @amalik_ellahi | Stardance
Devlogs:
Worked on my Ayaan Malik personal portfolio website. I’m building a dark, game-inspired “status window” style portfolio that introduces who I am, my interests, and my personal brand in a more unique way. Today I focused on the homepage layout, navigation, images, visual theme, and overall polish so the site feels less like a basic template and more like something that actually represents me. I also worked on making the design cleaner, more organized, and ready to eventually deploy through GitHub Pages.
Ships:
Built a personal portfolio website with a dark, shadowy design. Includes about me, skills, projects, and contact sections. Making the dark theme look polished while keeping text readable. Balancing contrast, spacing, and shadow effects. A cohesive dark aesthetic with smooth visual details. A cohesive dark aesthetic with smooth visual details. A modern, easy-to-use layout. To test it out, Open in a browser and check desktop/mobile responsiveness. Verify links, project cards, and contact actions. Ensure text remains readable on the dark background....
|
1793713984.0997124
|
1793800384.0997124
|
|
17610
|
Untitled by @sathvika | Stardance
|
sathvika
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @sathvika | Stardance
|
1793350217.2880144
|
1793955017.2880144
|
|
17611
|
My awesome macropad! by @akifozcelik | Stardance
|
akifozcelik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @akifozcelik | Star Title: My awesome macropad! by @akifozcelik | Stardance...
|
1793184727.2730944
|
1793789527.2730944
|
|
17612
|
Untitled by @akifozcelik | Stardance
|
akifozcelik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @akifozcelik | Stardance
|
1793238465.6584487
|
1793843265.6584487
|
|
17613
|
My very own WebOS by @sathvika | Stardance
|
sathvika
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @sathvika | Stardance
|
1793436486.1332457
|
1794041286.1332457
|
|
17614
|
Productivity Extension by @amalik_ellahi | Stardan Productivity Extension by @amalik_ellahi | Stardance...
|
amalik_ellahi
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-15T19:05:24Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "A Chrome extension that blocks YouTube/TikTok/Instagram/Reddit for 15 minutes so you actually focus on LeetCode. Getting the Chrome extension blocking rules to work right with Manifest V3. The UI looks clean and the timer saves if you close Chrome mid-session. Clone the repo, go to chrome://extensions, enable Developer mode, load the chrome-extension folder unpacked. Try the demo at https://amalikellahi-dot.github.io/ayaan-malik-extension/", "repo": "https://github.com/amalikellahi-dot/ayaan-malik-extension", "demo": "https://amalikellahi-dot.github.io/ayaan-malik-extension/"}]...
|
[{"post_id": 9059, "ts": "2026 [{"post_id": 9059, "ts": "2026-06-15T03:52:08Z", "hours": 0.7839, "text": "Built a quick 15‑minute focus timer + Chrome blocker to stop me from getting lost on YouTube/TikTok/Instagram/Reddit while I grind LeetCode. It’s an MVP so I kept it short and simple — gonna add custom times, whitelists, and scheduling later."}]...
|
Title: Productivity Extension by @amalik_ellahi | Title: Productivity Extension by @amalik_ellahi | Stardance
Devlogs:
Built a quick 15‑minute focus timer + Chrome blocker to stop me from getting lost on YouTube/TikTok/Instagram/Reddit while I grind LeetCode. It’s an MVP so I kept it short and simple — gonna add custom times, whitelists, and scheduling later.
Ships:
A Chrome extension that blocks YouTube/TikTok/Instagram/Reddit for 15 minutes so you actually focus on LeetCode. Getting the Chrome extension blocking rules to work right with Manifest V3. The UI looks clean and the timer saves if you close Chrome mid-session. Clone the repo, go to chrome://extensions, enable Developer mode, load the chrome-extension folder unpacked. Try the demo at https://amalikellahi-dot.github.io/ayaan-malik-extension/...
|
1793728478.031761
|
1793814878.031761
|
|
17615
|
Deskimon by @rickastley414 | Stardance
|
rickastley414
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Deskimon by @rickastley414 | Stardance
|
1793850793.1760705
|
1794714793.1760705
|
|
17616
|
Rayan's macropad by @RayanR | Stardance
|
RayanR
|
1
|
0.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-18T03:54:10Z", "hours": 0.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a Macropad that has 4 keypad switches and i made it to start PCB and CAD designing. I am proud to say this is my first designed PCB and ot truly feels like an acomplishment.", "repo": "https://github.com/Rayanrathi/Rayan-s-macropad", "demo": ""}]...
|
[{"post_id": 11084, "ts": "202 [{"post_id": 11084, "ts": "2026-06-18T03:52:05Z", "hours": 0.2819, "text": "I worked on my final moments in submission for hackpad"}]...
|
Title: Rayan's macropad by @RayanR | Stardance Title: Rayan's macropad by @RayanR | Stardance
Devlogs:
I worked on my final moments in submission for hackpad
Ships:
I made a Macropad that has 4 keypad switches and i made it to start PCB and CAD designing. I am proud to say this is my first designed PCB and ot truly feels like an acomplishment....
|
1793735658.674045
|
1793822058.674045
|
|
17617
|
My first slack bot! by @namikaze | Stardance
|
namikaze
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @namikaze | Stardanc Title: My first slack bot! by @namikaze | Stardance...
|
1793494215.854545
|
1794099015.854545
|
|
17618
|
My first slack bot! by @muratman | Stardance
|
muratman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @muratman | Stardanc Title: My first slack bot! by @muratman | Stardance...
|
1793455073.3659601
|
1794059873.3659601
|
|
17619
|
Untitled by @Cesare | Stardance
|
Cesare
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Cesare | Stardance
|
1793260357.6722016
|
1793865157.6722016
|
|
17620
|
My very own WebOS by @Ashrita | Stardance
|
Ashrita
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Ashrita | Stardance
|
1793361077.874853
|
1793965877.874853
|
|
17621
|
My very own WebOS by @Melvin_Tori | Stardance
|
Melvin_Tori
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Melvin_Tori | Stardan Title: My very own WebOS by @Melvin_Tori | Stardance...
|
1793512195.692035
|
1794116995.692035
|
|
17622
|
All-in-One Student Site by @Mridul_K | Stardance
|
Mridul_K
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: All-in-One Student Site by @Mridul_K | Star Title: All-in-One Student Site by @Mridul_K | Stardance...
|
1793400690.033011
|
1794005490.033011
|
|
17623
|
SEC: Interactive Space Exploration Portfolio by @x SEC: Interactive Space Exploration Portfolio by @xvadelax | Stardance...
|
xvadelax
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SEC: Interactive Space Exploration Portfoli Title: SEC: Interactive Space Exploration Portfolio by @xvadelax | Stardance...
|
1793245866.0983753
|
1793850666.0983753
|
|
17624
|
My awesome macropad! by @Kaia | Stardance
|
Kaia
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Kaia | Stardance
|
1793195566.4936967
|
1793800366.4936967
|
|
17625
|
Frictionless by @Blink | Stardance
|
Blink
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @Blink | Stardance
|
1793411530.1351366
|
1794016330.1351366
|
|
17626
|
SmartSchedule AI by @chahatesh | Stardance
|
chahatesh
|
3
|
13.0
|
56
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-02T20:06:10Z", "hours": 5.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "This is my third ship so I kind of have ideas but based on my feedback what people wanted was a dashboard feature so I added a dashboard back. I also just made it look a lot better, figured out a bunch of bugs, and fixed those and now it looks like a real product.", "repo": "https://github.com/chahatesh/SmartSchedule", "demo": "https://smartschedule.wasmer.app/"}, {"ship_num": 2, "ts": "2026-07-25T16:43:16Z", "hours": 4.0, "multiplier": 17.78, "payout": 37, "blessing": "cursed", "text": "For this next ship, I mostly changed the overall design of the app. In the last review, it was said that the app looked a little too AI-generated, which is fair since I had used AI to help generate the CSS. So, I redid the CSS myself to make the app look much better. I am not the strongest at CSS, so it still has a slightly older look, but I think it turned out fine. I also added a demo mode, which was an important improvement because one of the main pieces of feedback was that users had to make an account and sign in every time. With demo mode, they can try the app without needing an account. Another issue I worked on was the AI not always calling tools correctly. That took a lot of time to fix, but after a lot of work, I got it working properly. I also put more emphasis on voice typing, because that is one of the main features of the app. It makes everything faster and easier since users can just talk instead of typing everything out.", "repo": "https://github.com/chahatesh/SmartSchedule", "demo": "https://smartschedule.wasmer.app/"}, {"ship_num": 3, "ts": "2026-06-20T13:00:59Z", "hours": 4.0, "multiplier": 4.39, "payout": 19, "blessing": "neutral", "text": "I created Smart Schedule AI, a calendar and scheduling platform that combines a web application, an AI assistant, and a dedicated hardware device. Users can create events by chatting with the AI in natural language, and the events are automatically added to their calendar. I also developed a Smart Schedule Device using an ESP32-C3 and a 0.96” OLED display that connects to a user’s account and displays their next upcoming event. One of the biggest challenges was getting the website and hardware device to communicate reliably. I needed a way for users to connect the device to Wi-Fi without requiring complicated setup steps. To solve this, I implemented USB-based communication that allows Wi-Fi credentials to be sent directly to the device during setup. Another challenge was configuring the cloud database and account system so that each device could securely retrieve data from the correct user account. I am proud that I was able to create a complete system that combines software, hardware, cloud services, and AI into a single project. The device successfully synchronizes with the website and displays upcoming events in real time. I’m also proud that I was able to design a simple user experience where scheduling can be done through conversation instead of manually creating every calendar event. What should people know so they can test your project? To test Smart Schedule AI, users should create an account on the website and add a few events using the AI assistant or calendar interface. The Smart Schedule Device must be connected to a computer using USB to configure Wi-Fi credentials during setup. Once connected to Wi-Fi, the device will automatically synchronize with the user’s account and display their next scheduled event. Testers should verify that newly created events appear correctly on both the website and the device and that updates synchronize properly between them.", "repo": "https://github.com/chahatesh/SmartSchedule", "demo": "https://smartschedule.wasmer.app/"}]...
|
[{"post_id": 39673, "ts": "202 [{"post_id": 39673, "ts": "2026-08-02T20:05:02Z", "hours": 0.0, "text": "Dev Log 10 - Ship 3!!! What I did was really simple. I just made a dashboard that shows you things that you’ve done today things you have upcoming and your day"}, {"post_id": 39600, "ts": "2026-08-02T18:07:38Z", "hours": 3.0, "text": "Dev Log 9 - update Okay this took longer than I would expect because the existing thing that I coded was kind of off so I had to add a bunch of things. The CSS was kind of weird but I got it to work. It took a while but I made it kind of like a 3D effect. All that’s left to do is to add the dashboard so you can see what’s happening today but I think it looks decent. I didn’t change its color scheme. I just made it feel more modern and better."}, {"post_id": 34680, "ts": "2026-07-25T16:20:28Z", "hours": 1.0, "text": "Devlog 8 - Ship 2 So based on last ship the biggest think was that people did not like the set up of the app and that it look bad so i made it diffrent and now I think it is better also i added a demo mode so you can test with out making a acount only change was that it was saved in local storage BTW - if you are reading this this is a egg"}, {"post_id": 31465, "ts": "2026-07-19T20:49:27Z", "hours": 2.0, "text": "Dev log 7 I revamped the entire website and make it look better and cleaner"}, {"post_id": 15648, "ts": "2026-06-25T13:27:42Z", "hours": 0.0, "text": "Dev Log #5 - I Got Rejected After waiting about 3–4 days, I finally got a response on my project. Unfortunately, there was also a power outage during that time, so I lost a day and couldn’t check Stardance. When I finally logged in, I found out that my project had been denied. The reason? My AI API key had been revoked. At first, I was confused because everything had been working before. I checked whether I had accidentally uploaded an old version of the app, but everything was up to date. Then I checked the files on my PC and found the same issue there. For about 20 minutes, I went through the code trying to figure out what had broken. Eventually, I decided to check my AI provider’s dashboard. That’s when I discovered that my API key had been revoked, which meant the website could no longer communicate with the AI model. Once I found the problem, the fix was straightforward. I generated a new API key, updated the website configuration, and tested everything again. After a few tests, the AI features were working normally and the project was back online. To prevent this from happening again, I only stored the new API key on the live website and removed it from GitHub. This keeps the key private and reduces the chance of it being exposed or automatically revoked."}, {"post_id": 12502, "ts": "2026-06-20T12:57:27Z", "hours": 0.0, "text": "Dev Log #5 – Device Integration Complete & First Shipment Today marked a major milestone for Smart Schedule AI. I completed the integration between the Smart Schedule web platform and the Smart Schedule Device, allowing events from a user’s account to be displayed directly on the device’s OLED screen. One challenge was configuring Wi-Fi on the device. To solve this, I implemented a USB communication system that allows users to connect the Smart Schedule Device to a computer and securely send Wi-Fi credentials to the ESP32-C3. This provides a simple setup experience and ensures the device can connect to the internet and synchronize with the user’s calendar. – Completed Tasks Finished website-to-device integration Connected Smart Schedule accounts with physical devices Implemented USB communication for Wi-Fi setup Improved device synchronization and event retrieval Tested event updates between the website and hardware Finalized device firmware for deployment – Hardware Configuration ESP32-C3 0.96” OLED Display Rechargeable Battery Charging Module Power Switch – Manufacturing & Shipping After completing final testing, I assembled and packaged the first Smart Schedule Device. All hardware, firmware, and website components were verified and prepared for use. With testing complete, the device was packaged and shipped, marking the first fully functional Smart Schedule AI system deployment. Current Status ✅ Website Complete ✅ Device Complete ✅ Account Integration Working ✅ Wi-Fi Setup Implemented ✅ Event Synchronization Working ✅ First Device Shipped –Next Steps Improve onboarding experience Add support for multiple devices per account Expand AI scheduling capabilities Continue testing with real-world usage This milestone represents the first complete end-to-end Smart Schedule AI ecosystem, combining the web application, AI assistant, cloud synchronization, and dedicated hardware display into a single working product. 🚀"}, {"post_id": 11538, "ts": "2026-06-18T20:45:07Z", "hours": 0.0, "text": "Dev Log #4: Building the Reminder Device Today, I focused on designing, modeling, and programming the reminder device that connects to the AI calendar system. The device attaches to a user’s account and displays their upcoming events, allowing them to quickly see what they need to do next without opening the website. One of the biggest challenges was getting the ESP32-C3 to communicate with Firebase correctly. Firebase relies heavily on JSON data, and I spent a lot of time figuring out how to properly format, send, and read the data coming from the database. Small mistakes in the JSON structure could prevent the device from receiving event information, making debugging especially frustrating.Although the device itself is fairly simple, getting it to reliably connect to Wi-Fi, communicate with Firebase, and display the correct upcoming event took a lot more testing than I originally expected. By the end of this session, the device was successfully syncing with user accounts and displaying upcoming calendar events."}, {"post_id": 11034, "ts": "2026-06-18T01:56:55Z", "hours": 1.0, "text": "Dev Log #3: Building the Website Disclaimer: The coding-time tracker for this project is inaccurate by approximately 5–6 hours due to starting this project before stardance. This week, I focused on building the main website for the AI calendar system. The website now includes a calendar interface where users can view and manage events, an AI chat section that allows users to create events through natural conversation, and a device pairing page for connecting an ESP32-C3 reminder device. The biggest challenge I ran into was getting the AI to properly use tool calls. Sometimes the AI clearly understood what the user wanted, but instead of calling the event-creation function, it would simply respond with text describing what it would do. This led to a lot of testing and experimentation with prompts, tool definitions, and API settings until the AI consistently triggered the correct functions. By the end of this development session, the website was functional, the AI could create events through tool calls, and the device pairing system was successfully integrated into the interface."}, {"post_id": 9452, "ts": "2026-06-15T20:20:08Z", "hours": 0.0, "text": "Dev Log #2: Fighting the API I thought adding the Grok API would be one of the easier parts of the project. It turns out I was wrong. Since I had never worked with the API before, a lot of my time was spent tracking down small syntax mistakes. The API was very specific about how requests needed to be formatted, and even tiny errors could cause everything to fail. For example, at one point I wrote: payload = { \"model\": GROQ_MODEL, \"messages\": [{\"role\": \"user\", \"content\": message}] \"temperature\": 2, \"max_tokens\": 500, } I forgot the comma after “message}]” which caused an error and took me longer than I’d like to admit to find. The frustrating part was that the code usually looked correct at first glance. I would spend time checking API keys, debugging functions, and rereading documentation, only to discover that the issue was a single missing character. Now I know to read the documentation more and also if you like this project like and follow me."}, {"post_id": 8744, "ts": "2026-06-14T15:24:30Z", "hours": 0.0, "text": "Dev Log 1 Discamer time is off by about 5 hours- joined Stardance midway through development. The project is an AI-powered calendar assistant that allows users to create and manage events through natural conversation. Users can speak to the AI, and their speech is transcribed into text before being sent to an AI model such as Grok or Llama. The AI analyzes the request and generates tool calls to create, edit, or manage calendar events automatically. After the tool call is executed, the calendar is updated and the user receives confirmation. I also worked on integrating a companion reminder device that provides physical notifications for upcoming events. One of the most interesting parts of the project was building and understanding the AI pipeline that connects speech recognition, AI processing, tool calling, and calendar management into a seamless user experience."}]...
|
Title: SmartSchedule AI by @chahatesh | Stardance
Title: SmartSchedule AI by @chahatesh | Stardance
Devlogs:
Dev Log 1 Discamer time is off by about 5 hours- joined Stardance midway through development. The project is an AI-powered calendar assistant that allows users to create and manage events through natural conversation. Users can speak to the AI, and their speech is transcribed into text before being sent to an AI model such as Grok or Llama. The AI analyzes the request and generates tool calls to create, edit, or manage calendar events automatically. After the tool call is executed, the calendar is updated and the user receives confirmation. I also worked on integrating a companion reminder device that provides physical notifications for upcoming events. One of the most interesting parts of the project was building and understanding the AI pipeline that connects speech recognition, AI processing, tool calling, and calendar management into a seamless user experience.
Dev Log #2: Fighting the API I thought adding the Grok API would be one of the easier parts of the project. It turns out I was wrong. Since I had never worked with the API before, a lot of my time was spent tracking down small syntax mistakes. The API was very specific about how requests needed to be formatted, and even tiny errors could cause everything to fail. For example, at one point I wrote: payload = { "model": GROQ_MODEL, "messages": [{"role": "user", "content": message}] "temperature": 2, "max_tokens": 500, } I forgot the comma after “message}]” which caused an error and took me longer than I’d like to admit to find. The frustrating part was that the code usually looked correct at first glance. I would spend time checking API keys, debugging functions, and rereading documentation, only to discover that the issue was a single missing character. Now I know to read the documentation more and also if you like this project like and follow me.
Dev Log #3: Building the Website Disclaimer: The coding-time tracker for this project is inaccurate by approximately 5–6 hours due to starting this project before stardance. This week, I focused on building the main website for the AI calendar system. The website now includes a calendar interface where users can view and manage events, an AI chat section that allows users to create events through natural conversation, and a device pairing page for connecting an ESP32-C3 reminder device. The biggest challenge I ran into was getting the AI to properly use tool calls. Sometimes the AI clearly understood what the user wanted, but instead of calling the event-creation function, it would simply respond with text describing what it would do. This led to a lot of testing and experimentation with prompts, tool definitions, and API settings until the AI consistently triggered the correct functions. By the end of this development session, the website was functional, the AI could create events through tool calls, and the device pairing system was successfully integrated into the interface.
Dev Log #4: Building the Reminder Device Today, I focused on designing, modeling, and programming the reminder device that connects to the AI calendar system. The device attaches to a user’s account and displays their upcoming events, allowing them to quickly see what they need to do next without opening the website. One of the biggest challenges was getting the ESP32-C3 to communicate with Firebase correctly. Firebase relies heavily on JSON data, and I spent a lot of time figuring out how to properly format, send, and read the data coming from the database. Small mistakes in the JSON structure could prevent the device from receiving event information, making debugging especially frustrating.Although the device itself is fairly simple, getting it to reliably connect to Wi-Fi, communicate with Firebase, and display the correct upcoming event took a lot more testing than I originally expected. By the end of this session, the device was successfully syncing with user accounts and displaying upcoming calendar events.
Dev Log #5 – Device Integration Complete & First Shipment Today marked a major milestone for Smart Schedule AI. I completed the integration between the Smart Schedule web platform and the Smart Schedule Device, allowing events from a user’s account to be displayed directly on the device’s OLED screen. One challenge was configuring Wi-Fi on the device. To solve this, I implemented a USB communication system that allows users to connect the Smart Schedule Device to a computer and securely send Wi-Fi credentials to the ESP32-C3. This provides a simple setup experience and ensures the device can connect to the internet and synchronize with the user’s calendar. – Completed Tasks Finished website-to-device integration Connected Smart Schedule accounts with physical devices Implemented USB communication for Wi-Fi setup Improved device synchronization and event retrieval Tested event updates between the website and hardware Finalized device firmware for deployment – Hardware Configuration ESP32-C3 0.96” OLED Display Rechargeable Battery Charging Module Power Switch – Manufacturing & Shipping After completing final testing, I assembled and packaged the first Smart Schedule Device. All hardware, firmware, and website components were verified and prepared for use. With testing complete, the device was packaged and shipped, marking the first fully functional Smart Schedule AI system deployment. Current Status ✅ Website Complete ✅ Device Complete ✅ Account Integration Working ✅ Wi-Fi Setup Implemented ✅ Event Synchronization Working ✅ First Device Shipped –Next Steps Improve onboarding experience Add support for multiple devices per account Expand AI scheduling capabilities Continue testing with real-world usage This milestone represents the first complete end-to-end Smart Schedule AI ecosystem, combining the web application, AI assistant, cloud synchronization, and dedicated hardware display into a single working product. 🚀
Dev Log #5 - I Got Rejected After waiting about 3–4 days, I finally got a response on my project. Unfortunately, there was also a power outage during that time, so I lost a day and couldn’t check Stardance. When I finally logged in, I found out that my project had been denied. The reason? My AI API key had been revoked. At first, I was confused because everything had been working before. I checked whether I had accidentally uploaded an old version of the app, but everything was up to date. Then I checked the files on my PC and found the same issue there. For about 20 minutes, I went through the code trying to figure out what had broken. Eventually, I decided to check my AI provider’s dashboard. That’s when I discovered that my API key had been revoked, which meant the website could no longer communicate with the AI model. Once I found the problem, the fix was straightforward. I generated a new API key, updated the website configuration, and tested everything again. After a few tests, the AI features were working normally and the project was back online. To prevent this from happening again, I only stored the new API key on the live website and removed it from GitHub. This keeps the key private and reduces the chance of it being exposed or automatically revoked.
Dev log 7 I revamped the entire website and make it look better and cleaner
Devlog 8 - Ship 2 So based on last ship the biggest think was that people did not like the set up of the app and that it look bad so i made it diffrent and now I think it is better also i added a demo mode so you can test with out making a acount only change was that it was saved in local storage BTW - if you are reading this this is a egg
Dev Log 9 - update Okay this took longer than I would expect because the existing thing that I coded was kind of off so I had to add a bunch of things. The CSS was kind of weird but I got it to work. It took a while but I made it kind of like a 3D effect. All that’s left to do is to add the dashboard so you can see what’s happening today but I think it looks decent. I didn’t change its color scheme. I just made it feel more modern and better.
Dev Log 10 - Ship 3!!! What I did was really simple. I just made a dashboard that shows you things that you’ve done today things you have upcoming and your day
Ships:
I created Smart Schedule AI, a calendar and scheduling platform that combines a web application, an AI assistant, and a dedicated hardware device. Users can create events by chatting with the AI in natural language, and the events are automatically added to their calendar. I also developed a Smart Schedule Device using an ESP32-C3 and a 0.96” OLED display that connects to a user’s account and displays their next upcoming event. One of the biggest challenges was getting the website and hardware device to communicate reliably. I needed a way for users to connect the device to Wi-Fi without requiring complicated setup steps. To solve this, I implemented USB-based communication that allows Wi-Fi credentials to be sent directly to the device during setup. Another challenge was configuring the cloud database and account system so that each device could securely retrieve data from the correct user account. I am proud that I was able to create a complete system that combines software, hardware, cloud services, and AI into a single project. The device successfully synchronizes with the website and displays upcoming events in real time. I’m also proud that I was able to design a simple user experience where scheduling can be done through conversation instead of manually creating every calendar event. What should people know so they can test your project? To test Smart Schedule AI, users should create an account on the website and add a few events using the AI assistant or calendar interface. The Smart Schedule Device must be connected to a computer using USB to configure Wi-Fi credentials during setup. Once connected to Wi-Fi, the device will automatically synchronize with the user’s account and display their next scheduled event. Testers should verify that newly created events appear correctly on both the website and the device and that updates synchronize properly between them.
For this next ship, I mostly changed the overall design of the app. In the last review, it was said that the app looked a little too AI-generated, which is fair since I had used AI to help generate the CSS. So, I redid the CSS myself to make the app look much better. I am not the strongest at CSS, so it still has a slightly older look, but I think it turned out fine. I also added a demo mode, which was an important improvement because one of the main pieces of feedback was that users had to make an account and sign in every time. With demo mode, they can try the app without needing an account. Another issue I worked on was the AI not always calling tools correctly. That took a lot of time to fix, but after a lot of work, I got it working properly. I also put more emphasis on voice typing, because that is one of the main features of the app. It makes everything faster and easier since users can just talk instead of typing everything out.
This is my third ship so I kind of have ideas but based on my feedback what people wanted was a dashboard feature so I added a dashboard back. I also just made it look a lot better, figured out a bunch of bugs, and fixed those and now it looks like a real product....
|
1793775595.5525901
|
1794639595.5525901
|
|
17627
|
My very own WebOS by @yonis_quantamleads | Stardan My very own WebOS by @yonis_quantamleads | Stardance...
|
yonis_quantamleads
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @yonis_quantamleads | Title: My very own WebOS by @yonis_quantamleads | Stardance...
|
1793782260.3521993
|
1794387060.3521993
|
|
17628
|
My very own WebOS by @codecookermintz | Stardance
|
codecookermintz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @codecookermintz | Sta Title: My very own WebOS by @codecookermintz | Stardance...
|
1793300212.3152993
|
1793905012.3152993
|
|
17629
|
My very own WebOS by @llele | Stardance
|
llele
|
0
|
1.34
|
0
|
[]
|
[{"post_id": 8517, "ts": "2026 [{"post_id": 8517, "ts": "2026-06-14T05:09:04Z", "hours": 1.3439, "text": "I would put a pic but i have nothing but like html right now and it looks super boring😭 I’ve only done the little pop up welcome screen that’s going to be inspired by the victorious pear phone and the rest of the time i’ve just been trying to figure out what i’m doing fr. Just imagine the photo fr"}]...
|
Title: My very own WebOS by @llele | Stardance
De Title: My very own WebOS by @llele | Stardance
Devlogs:
I would put a pic but i have nothing but like html right now and it looks super boring😭 I’ve only done the little pop up welcome screen that’s going to be inspired by the victorious pear phone and the rest of the time i’ve just been trying to figure out what i’m doing fr. Just imagine the photo fr...
|
1793836524.3476305
|
1794441324.3476305
|
|
17630
|
Untitled by @1 | Stardance
|
1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @1 | Stardance
|
1793188406.6745012
|
1793793206.6745012
|
|
17631
|
Untitled by @Leah | Stardance
|
Leah
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Leah | Stardance
|
1793317854.9533443
|
1793922654.9533443
|
|
17632
|
Frictionless by @aaronhanqin | Stardance
|
aaronhanqin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @aaronhanqin | Stardance
|
1793480114.4185054
|
1794084914.4185054
|
|
17633
|
My awesome macropad! by @aja343642 | Stardance
|
aja343642
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @aja343642 | Starda Title: My awesome macropad! by @aja343642 | Stardance...
|
1793476340.6326199
|
1794081140.6326199
|
|
17634
|
My very own WebOS by @pujita_sunkara | Stardance
|
pujita_sunkara
|
0
|
1.4
|
0
|
[]
|
[{"post_id": 8732, "ts": "2026 [{"post_id": 8732, "ts": "2026-06-14T14:52:06Z", "hours": 0.28, "text": "Today I worked on my WebOS project, improving the desktop layout and making the window system more functional. I kept the welcome screen on the desktop and made sure apps can be opened from the dock. Next I want to improve app interactions, add smoother window behavior, and expand features like settings and search."}, {"post_id": 8727, "ts": "2026-06-14T14:31:12Z", "hours": 1.1153, "text": "Today I worked on my WebOS project, a browser-based operating system built with HTML. I improved the desktop by organizing the layout with a top bar, dock, and draggable-style windows. I also made sure the welcome screen stays on the desktop while other apps like Notes, Search, and Settings can open from the dock. Next steps for my project are improving the app system."}]...
|
Title: My very own WebOS by @pujita_sunkara | Star Title: My very own WebOS by @pujita_sunkara | Stardance
Devlogs:
Today I worked on my WebOS project, a browser-based operating system built with HTML. I improved the desktop by organizing the layout with a top bar, dock, and draggable-style windows. I also made sure the welcome screen stays on the desktop while other apps like Notes, Search, and Settings can open from the dock. Next steps for my project are improving the app system.
Today I worked on my WebOS project, improving the desktop layout and making the window system more functional. I kept the welcome screen on the desktop and made sure apps can be opened from the dock. Next I want to improve app interactions, add smoother window behavior, and expand features like settings and search....
|
1793868495.8221722
|
1794473295.8221722
|
|
17635
|
Weather API Dashboard by @SaathvikSowmyanarayanan Weather API Dashboard by @SaathvikSowmyanarayanan | Stardance...
|
SaathvikSowmyanarayanan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Weather API Dashboard by @SaathvikSowmyanar Title: Weather API Dashboard by @SaathvikSowmyanarayanan | Stardance...
|
1793854247.8537374
|
1794718247.8537374
|
|
17636
|
RB19 F1 RC Car by @YALFitian | Stardance
|
YALFitian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: RB19 F1 RC Car by @YALFitian | Stardance
|
1793379282.498546
|
1793984082.498546
|
|
17637
|
Venator WebOS by @Chase_Mutz | Stardance
|
Chase_Mutz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Venator WebOS by @Chase_Mutz | Stardance
|
1793217369.718202
|
1793822169.718202
|
|
17638
|
Dynamic Disco by @skiwi | Stardance
|
skiwi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Dynamic Disco by @skiwi | Stardance
|
1793792829.7976975
|
1794397629.7976975
|
|
17639
|
Minecraft Challenge Mod by @timon | Stardance
|
timon
|
1
|
13.0
|
174
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-15T18:11:10Z", "hours": 13.0, "multiplier": 13.04, "payout": 174, "blessing": "neutral", "text": "I made a Minecraft Challenges Mod with Fabric. You have multiple challegnes such as shared damage among your friends, ice track udner you and more. Additionally you can add a randomizer to your challenge which makes it that every block drop is different from the original one. Try it out with /challenges", "repo": "https://github.com/Facticee/challenges-mod", "demo": "https://modrinth.com/mod/challenge-mod"}]...
|
[{"post_id": 9353, "ts": "2026 [{"post_id": 9353, "ts": "2026-06-15T18:09:27Z", "hours": 2.0, "text": "I finished the Mod! There were a few bugs left, where whe nyou would rejoin, the randomizer wouldnt work but i could fix it pretty easily."}, {"post_id": 8148, "ts": "2026-06-13T16:15:55Z", "hours": 2.0, "text": "I added two new challenges. one is pretty simple. Every time you jump you get a random item dropped to you. mixin into jumpFromGround, grab a random item from the registry and spawn it. (might also have been easier with just giving it to the player but it works for now. i will go into testing later if one has bugs) the second one is the ice trail. you can sneak to toggle it on and off and a 3x3 platform of ice spawns under you wherever you walk. The ice will only replace air blocks and not existing blocks / blockentities. getting the sneak toggle to work was annoying as to mixin into a sneak method didnt work because i couldnt find the right class. ended up using client.options.keyShift.isDown in a client tick event."}, {"post_id": 8027, "ts": "2026-06-13T12:00:35Z", "hours": 2.0, "text": "The first challegne “shared life” is done. The core mechanic is when a player takes damage, everyone else gets the same amount. sounds simple, but it took me quiet a bit to get that right. the method i needed to use is called hurtServer in 26.x, not hurt like every tutorial says (cause of old yarn mappings like alr said in last devlog). @Inject (method = [“hurtServer”], at = [At(“TAIL”)]) private fun onHurtServer(level: ServerLevel, source: DamageSource, amount: Float, cir: CallbackInfoReturnable) { if (!cir.returnValue) return if (ChallengeState.activeChallenge !is SharedLifeChallenge) return val entity = this as? ServerPlayer ?: return if (source.directEntity == null && source.entity == null) return SharedLifeChallenge.onPlayerHurt(entity, amount) } the directEntity == null check is to prevent an infinite loop. When we deal damage to the other players, that would trigger the mixin again. Generic damage (the kind I use to pass the damage to other players) has no entity source so we can filter it out that way."}, {"post_id": 7726, "ts": "2026-06-12T21:53:39Z", "hours": 5.0, "text": "I have been building a challenges mod for minecraft 26.x and the idea is pretty simple. You type /challenges, a menu opens, you pick a challenge and it changes the gameplay. First challenge I am working on is shared life, where damage shared with every player. Getting it running was honestly kind of a pain. 26.x doesnt need yarn mappings anymore since mojang ships unobfuscated now. Which sounds great until you realize nearly every of the classes isnt the same as yarn mappings and nothing matches the (now outdated) tutorials. For example: hurt() is now hurtServer(), GuiGraphics is GuiGraphicsExtractor. I used AI to help look stuff up which sped things up a lot but even that was not always right. I am finished with the Menu and I started with the challenge code."}]...
|
Title: Minecraft Challenge Mod by @timon | Stardan Title: Minecraft Challenge Mod by @timon | Stardance
Devlogs:
I have been building a challenges mod for minecraft 26.x and the idea is pretty simple. You type /challenges, a menu opens, you pick a challenge and it changes the gameplay. First challenge I am working on is shared life, where damage shared with every player. Getting it running was honestly kind of a pain. 26.x doesnt need yarn mappings anymore since mojang ships unobfuscated now. Which sounds great until you realize nearly every of the classes isnt the same as yarn mappings and nothing matches the (now outdated) tutorials. For example: hurt() is now hurtServer(), GuiGraphics is GuiGraphicsExtractor. I used AI to help look stuff up which sped things up a lot but even that was not always right. I am finished with the Menu and I started with the challenge code.
The first challegne “shared life” is done. The core mechanic is when a player takes damage, everyone else gets the same amount. sounds simple, but it took me quiet a bit to get that right. the method i needed to use is called hurtServer in 26.x, not hurt like every tutorial says (cause of old yarn mappings like alr said in last devlog). @Inject (method = [“hurtServer”], at = [At(“TAIL”)]) private fun onHurtServer(level: ServerLevel, source: DamageSource, amount: Float, cir: CallbackInfoReturnable) { if (!cir.returnValue) return if (ChallengeState.activeChallenge !is SharedLifeChallenge) return val entity = this as? ServerPlayer ?: return if (source.directEntity == null && source.entity == null) return SharedLifeChallenge.onPlayerHurt(entity, amount) } the directEntity == null check is to prevent an infinite loop. When we deal damage to the other players, that would trigger the mixin again. Generic damage (the kind I use to pass the damage to other players) has no entity source so we can filter it out that way.
I added two new challenges. one is pretty simple. Every time you jump you get a random item dropped to you. mixin into jumpFromGround, grab a random item from the registry and spawn it. (might also have been easier with just giving it to the player but it works for now. i will go into testing later if one has bugs) the second one is the ice trail. you can sneak to toggle it on and off and a 3x3 platform of ice spawns under you wherever you walk. The ice will only replace air blocks and not existing blocks / blockentities. getting the sneak toggle to work was annoying as to mixin into a sneak method didnt work because i couldnt find the right class. ended up using client.options.keyShift.isDown in a client tick event.
I finished the Mod! There were a few bugs left, where whe nyou would rejoin, the randomizer wouldnt work but i could fix it pretty easily.
Ships:
I made a Minecraft Challenges Mod with Fabric. You have multiple challegnes such as shared damage among your friends, ice track udner you and more. Additionally you can add a randomizer to your challenge which makes it that every block drop is different from the original one. Try it out with /challenges...
|
1793775602.2867894
|
1794639602.2867894
|
|
17640
|
My very own WebOS by @tridev | Stardance
|
tridev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @tridev | Stardance
|
1793767811.3166044
|
1794372611.3166044
|
|
17641
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792947049.6962063
|
1793811049.6962063
|
|
17642
|
CRJ700 by @op2 | Stardance
|
op2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CRJ700 by @op2 | Stardance
|
1793224376.7642236
|
1793829176.7642236
|
|
17643
|
Speedmath by @oriondev | Stardance
|
oriondev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Speedmath by @oriondev | Stardance
|
1793389831.0315552
|
1793994631.0315552
|
|
17644
|
🐈Cat lover Slack bot by @mygulash | Stardance
|
mygulash
|
1
|
1.0
|
2
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-13T19:23:18Z", "hours": 1.0, "multiplier": 2.98, "payout": 2, "blessing": "neutral", "text": "My first ever project with Hack Club!✨ For my first project i chose creating a slack bot. My slack bot really really loves cats and it shows🐈He will gladly send you cat fun facts, images and even memes! After few hours of work i finally finished the code and could deploy it with nest so it runs 24/7. (The hackatime timer says it took me like 50 minutes even though i worked on it for like 4 hours… lol) For a beginner it was quite challenging to understand stuff like permissions and redirect URLs but Im happy to announce that its ready to ship! :D If you´re interested in this cat loving slack bot you can learn more about it in the read.me: https://github.com/Mygulash/LiborTheSlackBot/blob/main/README.md I hope that the cat memes, images and fun facts will make your day better :)🐈 Have a lovely day and pet your cat!✨", "repo": "https://github.com/Mygulash/LiborTheSlackBot", "demo": "https://hackclub.enterprise.slack.com/archives/C0B9Y31KHST"}]...
|
[{"post_id": 8060, "ts": "2026 [{"post_id": 8060, "ts": "2026-06-13T13:39:19Z", "hours": 0.7325, "text": "Finished the code for my Catloving Slack bot and now i´m waiting for my nest to get approved so i can host it ✨"}]...
|
Title: 🐈Cat lover Slack bot by @mygulash | Stardan Title: 🐈Cat lover Slack bot by @mygulash | Stardance
Devlogs:
Finished the code for my Catloving Slack bot and now i´m waiting for my nest to get approved so i can host it ✨
Ships:
My first ever project with Hack Club!✨ For my first project i chose creating a slack bot. My slack bot really really loves cats and it shows🐈He will gladly send you cat fun facts, images and even memes! After few hours of work i finally finished the code and could deploy it with nest so it runs 24/7. (The hackatime timer says it took me like 50 minutes even though i worked on it for like 4 hours… lol) For a beginner it was quite challenging to understand stuff like permissions and redirect URLs but Im happy to announce that its ready to ship! :D If you´re interested in this cat loving slack bot you can learn more about it in the read.me: https://github.com/Mygulash/LiborTheSlackBot/blob/main/README.md I hope that the cat memes, images and fun facts will make your day better :)🐈 Have a lovely day and pet your cat!✨...
|
1793822018.607708
|
1793908418.607708
|
|
17645
|
Draw Your Planet by @pujita_sunkara | Stardance
|
pujita_sunkara
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-14T03:11:40Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Draw Your Planet is a small space-themed drawing game where users can create their own planet. You can draw freely on the canvas, clear your drawing, and use a glow effect to make the planet look cooler. The project was built with HTML, CSS, JavaScript, and Python. One challenge was getting the drawing feature to work smoothly and making sure the glow effect looked good. I learned more about working with user input and designing interactive projects. In the future, I would like to add more colors, brush options, and a way to save drawings.", "repo": "https://github.com/pujitasunkara-jpg/web-os", "demo": "https://pujitasunkara-jpg.github.io/web-os/"}]...
|
[{"post_id": 8332, "ts": "2026 [{"post_id": 8332, "ts": "2026-06-13T21:01:34Z", "hours": 0.5981, "text": "I made a small interactive game where you can draw your own planet. You can sketch freely, clear the screen, and use a glow effect. It’s a fun space-project built using HTML and Python."}]...
|
Title: Draw Your Planet by @pujita_sunkara | Stard Title: Draw Your Planet by @pujita_sunkara | Stardance
Devlogs:
I made a small interactive game where you can draw your own planet. You can sketch freely, clear the screen, and use a glow effect. It’s a fun space-project built using HTML and Python.
Ships:
Draw Your Planet is a small space-themed drawing game where users can create their own planet. You can draw freely on the canvas, clear your drawing, and use a glow effect to make the planet look cooler. The project was built with HTML, CSS, JavaScript, and Python. One challenge was getting the drawing feature to work smoothly and making sure the glow effect looked good. I learned more about working with user input and designing interactive projects. In the future, I would like to add more colors, brush options, and a way to save drawings....
|
1793858001.0173483
|
1793944401.0173483
|
|
17646
|
My First Star Dream App by @SRIkalla | Stardance
|
SRIkalla
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My First Star Dream App by @SRIkalla | Star Title: My First Star Dream App by @SRIkalla | Stardance...
|
1793181265.811089
|
1793786065.811089
|
|
17647
|
My awesome macropad! by @Lalitchandra | Stardance
|
Lalitchandra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Lalitchandra | Sta Title: My awesome macropad! by @Lalitchandra | Stardance...
|
1793526914.367043
|
1794131714.367043
|
|
17648
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792932540.6862912
|
1793796540.6862912
|
|
17649
|
Untitled project by @Marre | Stardance
|
Marre
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Marre | Stardance
|
1793868975.5714192
|
1794732975.5714192
|
|
17650
|
Airplane Fun by @georgeo58 | Stardance
|
georgeo58
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Airplane Fun by @georgeo58 | Stardance
|
1793829186.036864
|
1794433986.036864
|