|
13451
|
amaOS by @ama | Stardance
|
ama
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: amaOS by @ama | Stardance
|
1793562737.2661464
|
1794167537.2661464
|
|
13452
|
My very own WebOS by @raggyp456 | Stardance
|
raggyp456
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @raggyp456 | Stardance
|
1793227906.3155694
|
1793832706.3155694
|
|
13453
|
My very own WebOS by @Ramon | Stardance
|
Ramon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Ramon | Stardance
|
1793263835.658127
|
1793868635.658127
|
|
13454
|
My awesome macropad! by @ThornyFern | Stardance
|
ThornyFern
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ThornyFern | Stard Title: My awesome macropad! by @ThornyFern | Stardance...
|
1793396971.1843808
|
1794001771.1843808
|
|
13455
|
My first slack bot! by @rehanhabbu | Stardance
|
rehanhabbu
|
2
|
2.0
|
2
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-06T19:14:51Z", "hours": 1.0, "multiplier": 1.13, "payout": 1, "blessing": "neutral", "text": "Slack Bot for StarDance: A custom Slack bot built for Stardance using Node.js, Slack’s Bolt framework, and Socket Mode. Mostly just fun commands. Commands /rsb-ping - Check the latency between your machine and Slack. /rsb-quest - Pulls a random side quest from the Bored API /rsb-coinflip - Flips a digital coin to settle arguments instantly. /rsb-countdown [YYYY-MM-DD] - Counts down the exact number of days left until the deadline. /rsb-help - Lists everything this construct can do. Also include QWEN2.0:5b AI model via DM’s to the bot, although it is extremely slow as it is running CPU only on nest. (Like VERY slow. I said hi at 11:50 and it responded at 12:44)", "repo": "https://github.com/Catsarepro21/Hackclubslacbot", "demo": "https://hackclub.enterprise.slack.com/archives/C08E083LZ9A"}, {"ship_num": 2, "ts": "2026-06-10T16:05:33Z", "hours": 1.0, "multiplier": 1.5, "payout": 1, "blessing": "neutral", "text": "I made a Slack Bot to do fun little commands. Things such as a coin flip, a time-till a date command, and a quest command that gives the user a random quest!", "repo": "https://github.com/Catsarepro21/Hackclubslacbot", "demo": "https://hackclub.enterprise.slack.com/archives/C08E083LZ9A"}]...
|
[{"post_id": 6904, "ts": "2026 [{"post_id": 6904, "ts": "2026-06-11T16:03:26Z", "hours": 0.6814, "text": "Fixed the demo URL by allowing direct messages to the bot and using that. Also because I can DM the bot now, I added an OLLAMA model running QWEN2:5b, although because it it running in CPU only mode it is extremally slow"}, {"post_id": 6292, "ts": "2026-06-10T16:04:24Z", "hours": 0.3361, "text": "Hosted the bot on nest and tested, works great!"}, {"post_id": 5929, "ts": "2026-06-09T22:08:02Z", "hours": 0.6567, "text": "Made the slack-bot and added some fun commands that I like, waiting on approval of Nest to finish this project!"}]...
|
Title: My first slack bot! by @rehanhabbu | Starda Title: My first slack bot! by @rehanhabbu | Stardance
Devlogs:
Made the slack-bot and added some fun commands that I like, waiting on approval of Nest to finish this project!
Hosted the bot on nest and tested, works great!
Fixed the demo URL by allowing direct messages to the bot and using that. Also because I can DM the bot now, I added an OLLAMA model running QWEN2:5b, although because it it running in CPU only mode it is extremally slow
Ships:
I made a Slack Bot to do fun little commands. Things such as a coin flip, a time-till a date command, and a quest command that gives the user a random quest!
Slack Bot for StarDance: A custom Slack bot built for Stardance using Node.js, Slack’s Bolt framework, and Socket Mode. Mostly just fun commands. Commands /rsb-ping - Check the latency between your machine and Slack. /rsb-quest - Pulls a random side quest from the Bored API /rsb-coinflip - Flips a digital coin to settle arguments instantly. /rsb-countdown [YYYY-MM-DD] - Counts down the exact number of days left until the deadline. /rsb-help - Lists everything this construct can do. Also include QWEN2.0:5b AI model via DM’s to the bot, although it is extremely slow as it is running CPU only on nest. (Like VERY slow. I said hi at 11:50 and it responded at 12:44)...
|
1793526715.407874
|
1793613115.407874
|
|
13456
|
Untitled by @violette_lalanne75 | Stardance
|
violette_lalanne75
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @violette_lalanne75 | Stardance
|
1793526881.682154
|
1794131681.682154
|
|
13457
|
My first WebOS! by @MattyO | Stardance
|
MattyO
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first WebOS! by @MattyO | Stardance
|
1793411429.8110151
|
1794016229.8110151
|
|
13458
|
My awesome macropad! by @99 | Stardance
|
99
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @99 | Stardance
|
1793188315.5590882
|
1793793115.5590882
|
|
13459
|
My awesome macropad! by @j80066326 | Stardance
|
j80066326
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @j80066326 | Starda Title: My awesome macropad! by @j80066326 | Stardance...
|
1793400841.5856473
|
1794005641.5856473
|
|
13460
|
Untitled by @Mang0 | Stardance
|
Mang0
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Mang0 | Stardance
|
1793184859.2228913
|
1793789659.2228913
|
|
13461
|
Netty by @crann | Stardance
|
crann
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Netty by @crann | Stardance
|
1793540940.2321045
|
1794145740.2321045
|
|
13462
|
FlightScope by @zombieking1555 | Stardance
|
zombieking1555
|
0
|
20.72
|
0
|
[]
|
[{"post_id": 13975, "ts": "202 [{"post_id": 13975, "ts": "2026-06-22T22:49:33Z", "hours": 3.4475, "text": "Devlog 6 - Flight Comparison Dashboard! Overview In this cycle, I expanded FlightScope’s analysis capabilities with a new Flight Comparison Dashboard! Now, users can load in two flights at the same time, comparing trajectories and detected flight events side-by-side. These additions make it endlessly easier to analyze design changes, motor selections, and overall flight performance across multiple launches. What’s New Added a dedicated Flight Comparison Dashboard. Implemented dual-flight visualization for altitude, velocity, and orientation telemetry. Added automatic launch detection and time normalization so flights can be compared from liftoff. Implemented automatic event detection for: Motor burnout Apogee Parachute deployment Landing Added event markers directly onto comparison graphs. Added a Comparison Summary table displaying key event timestamps for both flights side-by-side. Improved dashboard responsiveness by moving admin sidebar initialization outside of rendering bottlenecks. Updated docs and README! By the way, FlightScope is fully public on GitHub , go check it out :) Challenges The challenge this time around was making sure the flight comparison dashboard was actually useful , so I spent some time designing features such as time normalization and side-by-side data viewing to make it very clear to the user where flight differences were present. Next Steps Improve flight render with trajectory path Expand visualization tools with synchronized playback and side-by-side flight rendering. So much progress is being made on this funny little program, I’m so very pleased with how FlightScope is coming along! That’s all for now, folks. See you in #7!"}, {"post_id": 12646, "ts": "2026-06-20T17:37:36Z", "hours": 6.2542, "text": "Devlog 5 - Zenith, Azimuth, and Flight Rendering! Overview This development cycle focused on major new steps to improve the dashboard. The biggest addition was a complete 3D flight reconstruction pipeline capable of calculating rocket orientation from telemetry data and rendering the flight path frame-by-frame. What’s New Implemented zenith and azimuth telemetry support to determine rocket orientation throughout flight. Added a 3D rendering engine capable of visualizing rocket orientation and position over time. Created frame-by-frame flight playback controls directly within the dashboard. Added automatic rendering of flight paths using telemetry stored in the FlightScope database. Combined flight frame renders into video playback, adding an additional layer of visualization to flight analysis. Optimized rendering performance through image caching and improved frame loading behavior. Challenges This chunk of progress was heavy on debugging. The first challenge was reconstructing a realistic rocket orientation from flight data. Position alone wasn’t satisfying in replay, so I implemented zenith and azimuth calculations that adds rotational orientation to the flight replay The biggest issue I had, however, was actually combining flight frames into a video and implementing it on the dashboard. Video formats didn’t treat me well, but I figured out the correct pipeline with lots of trial and error and checks of every step of the system. Next Steps Continue improving rendering performance for larger flights. Expand the visualization system with additional flight annotations and overlays. Improve playback controls and timeline navigation. FlightScope has evolved from plotting telemetry to actually visualizing the flight itself. Seeing a rocket fly through a reconstructed 3D trajectory using real telemetry data is a huge milestone for the project, and I’m excited to keep pushing the visualization tools further."}, {"post_id": 9529, "ts": "2026-06-15T22:02:24Z", "hours": 3.12, "text": "Devlog 4 - UI Overhaul, Resilient Data Importing, and OpenRocket Export Compatibility! Overview I’ve spent more time improving FlightScope’s usability and flexibility, focusing on a cleaner code structure, a more resilient data importing pipeline, and compatibility with OpenRocket simulation exports. What’s New Refactored the backend by separating dashboard, database, and data importing logic into dedicated modules. Improved the CSV upload flow to handle more file formats and clean incoming telemetry automatically. Added compatibility with OpenRocket CSV exports, including automatic unit detection and conversion for feet, meters, and Gs. Added safeguards to flight event detection to make analysis more reliable. Created a GitHub README! Go check it out, it’s linked at the bottom of the devlog :) Challenges Getting OpenRocket compatibility working was more difficult than expected due to differences in column names, units, and CSV formatting. I redesigned the import pipeline to standardize telemetry data before it reaches the database, making FlightScope much more flexible. Next Steps Continue refining the FlightScope UI and overall user experience. Add support for more telemetry formats. Expand flight analysis and visualization tools. Make an online demo for you all to try out! (I could have written another 3 devlogs just about my challenges with this… we will save it for next time.) FlightScope is now fully documented on GitHub: https://github.com/zombieking1555/FlightScope devlog 4 in the bag, now that’s some type stuff. And check this demo:"}, {"post_id": 8127, "ts": "2026-06-13T15:56:50Z", "hours": 3.9747, "text": "Devlog 3 - Flight Simulation Overhaul, Data Trimming, and Flight Event Detection! Overview Spent more time improving FlightScope’s flight data pipeline, with a focus on making the test flights more realistic, trimming extra idle data, and detecting key flight events more reliably. What’s New Reworked the flight simulator to generate more realistic telemetry, including pre-launch idle, boost, coast, parachute descent, and post-landing idle. Added acceleration support throughout the database and telemetry pipeline. Implemented automatic detection and annotation for launch, burnout, apogee, parachute deployment, and landing. Trimmed pre-launch and post-landing idle data so plots focus on the active flight window. Regenerated test flights with updated simulation parameters. Challenges Getting event detection to work reliably took some tuning, especially with noisy acceleration data. Landing detection also needed a little extra care so the plots would stop cleanly at touchdown instead of including a lot of extra idle data. Next Steps Tune detection thresholds more easily from the UI. Add tests for the event detection logic. Continue improving the database and telemetry handling. FlightScope is really coming along! I’m excited to see where this project takes me until the next devlog."}, {"post_id": 5995, "ts": "2026-06-10T01:35:21Z", "hours": 1.5639, "text": "Devlog 2 - Database Initialization, Dashboard Pages, and More! Overview Spent more time developing FlightScope, focusing on improving the local flight database structure and making smaller quality-of-life changes to keep the app scalable and easier to maintain. What’s New Added automatic database initialization so flights.db is created locally instead of being stored in GitHub. Added a Database Manager page to view, manage, and delete individual flight records after upload. Refactored several backend functions to improve consistency and prepare the app for future features. Challenges Removing flights.db from GitHub was more challenging than expected (thanks, .gitignore ). This led to the creation of create_db.py , which removes the dependency on a tracked database file and allows FlightScope to generate a local database automatically on startup. Next Steps Expand the FlightScope dashboard with richer flight analysis and visualization tools. Support additional CSV data fields for more detailed and comprehensive flight reviews. It’s been real, see you next devlog."}, {"post_id": 5158, "ts": "2026-06-08T20:51:05Z", "hours": 2.3578, "text": "Devlog 1 - Streamlit uploader + SQLite storage + basic flight plotting Overview Added a Streamlit app that lets me upload flight CSVs, stores telemetry in a local SQLite database, and plots Altitude vs Time . I also added a small test data script that generates synthetic 200 Hz flight logs so I can quickly test the interface without real rocket data. What’s new Streamlit CSV uploader for flight data SQLite database for storing flight metadata and telemetry Altitude vs Time interactive plot using Plotly Synthetic flight generator ( test_data_writer ) producing 200 Hz test flights Data pipeline Upload CSV → validate → parse numeric values Store flight metadata in flights table Store time-series data in telemetry table Query SQLite → render plots in Streamlit Challenges / friction CSV validation required enforcing numeric types for altitude and velocity Handled missing or invalid data during import Added duplicate filename detection to prevent overwriting flights Admin “Clear Database” flow required Streamlit session_state + rerun handling due to UI reset behavior Design decisions Chose SQLite + pandas for simplicity and local-only operation Avoided external database dependencies to keep setup lightweight Kept CSV import as the ingestion layer for flexibility Added synthetic test data generator to speed up UI development and debugging Next Steps Improve the upload UX (showing row counts and import status) Add per-flight summary stats Allowing CSV export from the database. Having a lot of fun with this project, see you in the next devlog!"}]...
|
Title: FlightScope by @zombieking1555 | Stardance
Title: FlightScope by @zombieking1555 | Stardance
Devlogs:
Devlog 1 - Streamlit uploader + SQLite storage + basic flight plotting Overview Added a Streamlit app that lets me upload flight CSVs, stores telemetry in a local SQLite database, and plots Altitude vs Time . I also added a small test data script that generates synthetic 200 Hz flight logs so I can quickly test the interface without real rocket data. What’s new Streamlit CSV uploader for flight data SQLite database for storing flight metadata and telemetry Altitude vs Time interactive plot using Plotly Synthetic flight generator ( test_data_writer ) producing 200 Hz test flights Data pipeline Upload CSV → validate → parse numeric values Store flight metadata in flights table Store time-series data in telemetry table Query SQLite → render plots in Streamlit Challenges / friction CSV validation required enforcing numeric types for altitude and velocity Handled missing or invalid data during import Added duplicate filename detection to prevent overwriting flights Admin “Clear Database” flow required Streamlit session_state + rerun handling due to UI reset behavior Design decisions Chose SQLite + pandas for simplicity and local-only operation Avoided external database dependencies to keep setup lightweight Kept CSV import as the ingestion layer for flexibility Added synthetic test data generator to speed up UI development and debugging Next Steps Improve the upload UX (showing row counts and import status) Add per-flight summary stats Allowing CSV export from the database. Having a lot of fun with this project, see you in the next devlog!
Devlog 2 - Database Initialization, Dashboard Pages, and More! Overview Spent more time developing FlightScope, focusing on improving the local flight database structure and making smaller quality-of-life changes to keep the app scalable and easier to maintain. What’s New Added automatic database initialization so flights.db is created locally instead of being stored in GitHub. Added a Database Manager page to view, manage, and delete individual flight records after upload. Refactored several backend functions to improve consistency and prepare the app for future features. Challenges Removing flights.db from GitHub was more challenging than expected (thanks, .gitignore ). This led to the creation of create_db.py , which removes the dependency on a tracked database file and allows FlightScope to generate a local database automatically on startup. Next Steps Expand the FlightScope dashboard with richer flight analysis and visualization tools. Support additional CSV data fields for more detailed and comprehensive flight reviews. It’s been real, see you next devlog.
Devlog 3 - Flight Simulation Overhaul, Data Trimming, and Flight Event Detection! Overview Spent more time improving FlightScope’s flight data pipeline, with a focus on making the test flights more realistic, trimming extra idle data, and detecting key flight events more reliably. What’s New Reworked the flight simulator to generate more realistic telemetry, including pre-launch idle, boost, coast, parachute descent, and post-landing idle. Added acceleration support throughout the database and telemetry pipeline. Implemented automatic detection and annotation for launch, burnout, apogee, parachute deployment, and landing. Trimmed pre-launch and post-landing idle data so plots focus on the active flight window. Regenerated test flights with updated simulation parameters. Challenges Getting event detection to work reliably took some tuning, especially with noisy acceleration data. Landing detection also needed a little extra care so the plots would stop cleanly at touchdown instead of including a lot of extra idle data. Next Steps Tune detection thresholds more easily from the UI. Add tests for the event detection logic. Continue improving the database and telemetry handling. FlightScope is really coming along! I’m excited to see where this project takes me until the next devlog.
Devlog 4 - UI Overhaul, Resilient Data Importing, and OpenRocket Export Compatibility! Overview I’ve spent more time improving FlightScope’s usability and flexibility, focusing on a cleaner code structure, a more resilient data importing pipeline, and compatibility with OpenRocket simulation exports. What’s New Refactored the backend by separating dashboard, database, and data importing logic into dedicated modules. Improved the CSV upload flow to handle more file formats and clean incoming telemetry automatically. Added compatibility with OpenRocket CSV exports, including automatic unit detection and conversion for feet, meters, and Gs. Added safeguards to flight event detection to make analysis more reliable. Created a GitHub README! Go check it out, it’s linked at the bottom of the devlog :) Challenges Getting OpenRocket compatibility working was more difficult than expected due to differences in column names, units, and CSV formatting. I redesigned the import pipeline to standardize telemetry data before it reaches the database, making FlightScope much more flexible. Next Steps Continue refining the FlightScope UI and overall user experience. Add support for more telemetry formats. Expand flight analysis and visualization tools. Make an online demo for you all to try out! (I could have written another 3 devlogs just about my challenges with this… we will save it for next time.) FlightScope is now fully documented on GitHub: https://github.com/zombieking1555/FlightScope devlog 4 in the bag, now that’s some type stuff. And check this demo:
Devlog 5 - Zenith, Azimuth, and Flight Rendering! Overview This development cycle focused on major new steps to improve the dashboard. The biggest addition was a complete 3D flight reconstruction pipeline capable of calculating rocket orientation from telemetry data and rendering the flight path frame-by-frame. What’s New Implemented zenith and azimuth telemetry support to determine rocket orientation throughout flight. Added a 3D rendering engine capable of visualizing rocket orientation and position over time. Created frame-by-frame flight playback controls directly within the dashboard. Added automatic rendering of flight paths using telemetry stored in the FlightScope database. Combined flight frame renders into video playback, adding an additional layer of visualization to flight analysis. Optimized rendering performance through image caching and improved frame loading behavior. Challenges This chunk of progress was heavy on debugging. The first challenge was reconstructing a realistic rocket orientation from flight data. Position alone wasn’t satisfying in replay, so I implemented zenith and azimuth calculations that adds rotational orientation to the flight replay The biggest issue I had, however, was actually combining flight frames into a video and implementing it on the dashboard. Video formats didn’t treat me well, but I figured out the correct pipeline with lots of trial and error and checks of every step of the system. Next Steps Continue improving rendering performance for larger flights. Expand the visualization system with additional flight annotations and overlays. Improve playback controls and timeline navigation. FlightScope has evolved from plotting telemetry to actually visualizing the flight itself. Seeing a rocket fly through a reconstructed 3D trajectory using real telemetry data is a huge milestone for the project, and I’m excited to keep pushing the visualization tools further.
Devlog 6 - Flight Comparison Dashboard! Overview In this cycle, I expanded FlightScope’s analysis capabilities with a new Flight Comparison Dashboard! Now, users can load in two flights at the same time, comparing trajectories and detected flight events side-by-side. These additions make it endlessly easier to analyze design changes, motor selections, and overall flight performance across multiple launches. What’s New Added a dedicated Flight Comparison Dashboard. Implemented dual-flight visualization for altitude, velocity, and orientation telemetry. Added automatic launch detection and time normalization so flights can be compared from liftoff. Implemented automatic event detection for: Motor burnout Apogee Parachute deployment Landing Added event markers directly onto comparison graphs. Added a Comparison Summary table displaying key event timestamps for both flights side-by-side. Improved dashboard responsiveness by moving admin sidebar initialization outside of rendering bottlenecks. Updated docs and README! By the way, FlightScope is fully public on GitHub , go check it out :) Challenges The challenge this time around was making sure the flight comparison dashboard was actually useful , so I spent some time designing features such as time normalization and side-by-side data viewing to make it very clear to the user where flight differences were present. Next Steps Improve flight render with trajectory path Expand visualization tools with synchronized playback and side-by-side flight rendering. So much progress is being made on this funny little program, I’m so very pleased with how FlightScope is coming along! That’s all for now, folks. See you in #7!...
|
1793382541.9433553
|
1793987341.9433553
|
|
13463
|
XFly by @SollRak | Stardance
|
SollRak
|
0
|
0.0
|
0
|
[]
|
[{"post_id": 13343, "ts": "202 [{"post_id": 13343, "ts": "2026-06-21T21:15:21Z", "hours": 0.0, "text": "Battery Holder V1 (or Final, Idk) - Hey guys,here is the drone battery holder. The concept is very simple: its purpose is to securely hold the battery in place during flight. The design was intentionally kept straightforward, without relying on complex mechanical systems or advanced engineering features. This approach makes the part easier to print and assemble."}, {"post_id": 13280, "ts": "2026-06-21T18:59:35Z", "hours": 0.0, "text": "Motor Suport V1 - I started by researching existing models and selected one that looked simpler and easier to assemble. My main goal was to make the parts easy to remove and maintain, so I adapted the design with that in mind. This version is based on a straightforward template that prioritizes accessibility and practical mounting. It will serve as the support for the SunnySky X2814 900KV motor, ensuring a secure fit while still allowing quick disassembly when needed."}, {"post_id": 12809, "ts": "2026-06-20T23:25:20Z", "hours": 0.0, "text": "Hi guys, I’ve started the XFly quadcopter structure project. Basically, this structure connects the arm with a mounting connector. The drone’s design will be quite simple, just a few connectors. The most complex part will be the software, as I intend to use this drone in competitions like the Matlab Minidrone, which involves autonomous drones with embedded computer vision."}]...
|
Title: XFly by @SollRak | Stardance
Devlogs:
Hi g Title: XFly by @SollRak | Stardance
Devlogs:
Hi guys, I’ve started the XFly quadcopter structure project. Basically, this structure connects the arm with a mounting connector. The drone’s design will be quite simple, just a few connectors. The most complex part will be the software, as I intend to use this drone in competitions like the Matlab Minidrone, which involves autonomous drones with embedded computer vision.
Motor Suport V1 - I started by researching existing models and selected one that looked simpler and easier to assemble. My main goal was to make the parts easy to remove and maintain, so I adapted the design with that in mind. This version is based on a straightforward template that prioritizes accessibility and practical mounting. It will serve as the support for the SunnySky X2814 900KV motor, ensuring a secure fit while still allowing quick disassembly when needed.
Battery Holder V1 (or Final, Idk) - Hey guys,here is the drone battery holder. The concept is very simple: its purpose is to securely hold the battery in place during flight. The design was intentionally kept straightforward, without relying on complex mechanical systems or advanced engineering features. This approach makes the part easier to print and assemble....
|
1792943317.5487022
|
1793807317.5487022
|
|
13464
|
My awesome macropad! by @Imani | Stardance
|
Imani
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Imani | Stardance
|
1793537740.5730338
|
1794142540.5730338
|
|
13465
|
Untitled by @ProjectSTAR | Stardance
|
ProjectSTAR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ProjectSTAR | Stardance
|
1793180898.3134887
|
1793785698.3134887
|
|
13466
|
My very own WebOS by @leighbee | Stardance
|
leighbee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @leighbee | Stardance
|
1793321624.9034083
|
1793926424.9034083
|
|
13467
|
The Sorta - Sorting Robot by @ProjectSTAR | Starda The Sorta - Sorting Robot by @ProjectSTAR | Stardance...
|
ProjectSTAR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The Sorta - Sorting Robot by @ProjectSTAR | Title: The Sorta - Sorting Robot by @ProjectSTAR | Stardance...
|
1793512155.7479722
|
1794116955.7479722
|
|
13468
|
Untitled by @tymon3310 | Stardance
|
tymon3310
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @tymon3310 | Stardance
|
1793458567.332632
|
1794063367.332632
|
|
13469
|
BLOB - The Slack Bot by @Cris | Stardance
|
Cris
|
1
|
6.0
|
61
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-12T20:42:25Z", "hours": 6.0, "multiplier": 9.67, "payout": 61, "blessing": "neutral", "text": "I made a cool little Slack bot that is both a chatbot and a useful, fun tool for Slack.", "repo": "https://github.com/crislazy/SlackBLOB", "demo": "https://app.slack.com/client/E09V59WQY1E/C0BA35BLDNC"}]...
|
[{"post_id": 7680, "ts": "2026 [{"post_id": 7680, "ts": "2026-06-12T20:35:40Z", "hours": 2.4289, "text": "Devlog 4 Note: This may be the final devlog What did I do? I moved the chatbot from mentioning the bot to running /blob-talk <message> and limited the AI bot only to the testing channel( #crislzys-testing-channel ). I also changed the storing method for the AI history to sqlite3 and added /blob-reset that resets your chat history. I added a welcoming messaging feature that can be enabled running /blob-setwelcome On (Default is off). I also updated the /blob-about command and the README.md file. I modified the code making it a little bit better to read. What will I add? Probably nothing for now but in the future this bot may receive updates. Where can I test the bot? The bot can be tested in #crislzys-testing-channel on HackClub’s Slack Used Packages @slack /bolt axios dotenv sqlite3 License MIT"}, {"post_id": 6438, "ts": "2026-06-10T20:30:30Z", "hours": 1.5158, "text": "Devlog 3 Note: This project is still a work in progress and may contain bugs or incomplete features. What did I do? I added the following slash commands: /blob-about : This command basically gives the uptime of the bot and a few info. I also replaced the @ping responses with an ai chatbot using the HackClub AI API. (ChatGPT helped me a bit because i couldn’t figure out how to add a history to the chat) Note: The AI chatbot feature may be removed in the future. And also the responses are a bit slow. I also updated the /blob-help command with these new commands and I added a pfp to the bot. What will I add? Right now I don’t know what I could add but tomorrow I may come up with some new ideas. Where can I test the bot? The bot can be tested in #crislzys-testing-channel on HackClub’s Slack Used Packages @slack /bolt axios dotenv License MIT"}, {"post_id": 6093, "ts": "2026-06-10T07:41:00Z", "hours": 0.7869, "text": "Devlog 2 Note: This project is still a work in progress and may contain bugs or incomplete features. What did I do? I added the following slash commands: /blob-8ball : This command is basically 8ball /blob-whoami : Returns you name(ex: “crislzy”) and your SlackID I also updated the /blob-help command with these new commands. What will I add? I was thinking of adding more responses to pings and also adding a command that used AI(using HackClub’s AI API). And probably some new slash commands that are usefull and fun. Also, I would want to add a pfp for the bot and a description. Where can I test the bot? The bot can be tested in #crislzys-testing-channel on HackClub’s Slack Used Packages @slack /bolt axios dotenv License MIT"}, {"post_id": 5479, "ts": "2026-06-09T08:47:02Z", "hours": 1.5517, "text": "Devlog 1 What did I do? I added a help command, a catfact command and a ping command. I also made the bot respond to pings. I also hosted the bot on nest. And can be tested in #crislzys-testing-channel on HackClub’s Slack What will I add? Good question… Probably , I will add some fun commands like 8Ball , a calculator and also a “What Is My SlackID” command. I will also make the code cleaner and adding a README and maybe also an MIT LICENSE."}]...
|
Title: BLOB - The Slack Bot by @Cris | Stardance
Title: BLOB - The Slack Bot by @Cris | Stardance
Devlogs:
Devlog 1 What did I do? I added a help command, a catfact command and a ping command. I also made the bot respond to pings. I also hosted the bot on nest. And can be tested in #crislzys-testing-channel on HackClub’s Slack What will I add? Good question… Probably , I will add some fun commands like 8Ball , a calculator and also a “What Is My SlackID” command. I will also make the code cleaner and adding a README and maybe also an MIT LICENSE.
Devlog 2 Note: This project is still a work in progress and may contain bugs or incomplete features. What did I do? I added the following slash commands: /blob-8ball : This command is basically 8ball /blob-whoami : Returns you name(ex: “crislzy”) and your SlackID I also updated the /blob-help command with these new commands. What will I add? I was thinking of adding more responses to pings and also adding a command that used AI(using HackClub’s AI API). And probably some new slash commands that are usefull and fun. Also, I would want to add a pfp for the bot and a description. Where can I test the bot? The bot can be tested in #crislzys-testing-channel on HackClub’s Slack Used Packages @slack /bolt axios dotenv License MIT
Devlog 3 Note: This project is still a work in progress and may contain bugs or incomplete features. What did I do? I added the following slash commands: /blob-about : This command basically gives the uptime of the bot and a few info. I also replaced the @ping responses with an ai chatbot using the HackClub AI API. (ChatGPT helped me a bit because i couldn’t figure out how to add a history to the chat) Note: The AI chatbot feature may be removed in the future. And also the responses are a bit slow. I also updated the /blob-help command with these new commands and I added a pfp to the bot. What will I add? Right now I don’t know what I could add but tomorrow I may come up with some new ideas. Where can I test the bot? The bot can be tested in #crislzys-testing-channel on HackClub’s Slack Used Packages @slack /bolt axios dotenv License MIT
Devlog 4 Note: This may be the final devlog What did I do? I moved the chatbot from mentioning the bot to running /blob-talk <message> and limited the AI bot only to the testing channel( #crislzys-testing-channel ). I also changed the storing method for the AI history to sqlite3 and added /blob-reset that resets your chat history. I added a welcoming messaging feature that can be enabled running /blob-setwelcome On (Default is off). I also updated the /blob-about command and the README.md file. I modified the code making it a little bit better to read. What will I add? Probably nothing for now but in the future this bot may receive updates. Where can I test the bot? The bot can be tested in #crislzys-testing-channel on HackClub’s Slack Used Packages @slack /bolt axios dotenv sqlite3 License MIT
Ships:
I made a cool little Slack bot that is both a chatbot and a useful, fun tool for Slack....
|
1793490553.3882601
|
1793576953.3882601
|
|
13470
|
OpenCalc by @cory_pearl | Stardance
|
cory_pearl
|
1
|
4.33
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-04T15:30:21Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a graphing calculator with an ESP32. The firmware is done and I just finished a desaign of the hardware after many months and am ready to order! It is a little out of my budget so I am trying to apply for this grant. This is my first ever PCB so I am very eager to order. I hope you like what you see and support me!", "repo": "https://github.com/CoryPearl/opencalc", "demo": "https://corypearl.github.io/opencalc/blog.html"}]...
|
[{"post_id": 41143, "ts": "202 [{"post_id": 41143, "ts": "2026-08-05T05:11:41Z", "hours": 0.3308, "text": "I updated some firmware to work with a newly designed, more power efficent button matrix."}, {"post_id": 40787, "ts": "2026-08-04T15:24:31Z", "hours": 4.1258, "text": "I’ve worked on the PCB"}]...
|
Title: OpenCalc by @cory_pearl | Stardance
Devlog Title: OpenCalc by @cory_pearl | Stardance
Devlogs:
I’ve worked on the PCB
I updated some firmware to work with a newly designed, more power efficent button matrix.
Ships:
I made a graphing calculator with an ESP32. The firmware is done and I just finished a desaign of the hardware after many months and am ready to order! It is a little out of my budget so I am trying to apply for this grant. This is my first ever PCB so I am very eager to order. I hope you like what you see and support me!...
|
1793469073.168554
|
1793555473.168554
|
|
13471
|
Chess Engine by @GoldenElf | Stardance
|
GoldenElf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Chess Engine by @GoldenElf | Stardance
|
1793494519.78965
|
1794099319.78965
|
|
13472
|
Snake Game by @Steve_Luvis | Stardance
|
Steve_Luvis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Snake Game by @Steve_Luvis | Stardance
|
1793490449.1207583
|
1794095249.1207583
|
|
13473
|
Scoundrel card game by @dabdudetheman | Stardance
|
dabdudetheman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Scoundrel card game by @dabdudetheman | Sta Title: Scoundrel card game by @dabdudetheman | Stardance...
|
1793451234.0600224
|
1794056034.0600224
|
|
13474
|
Slates - slack notes bot by @tymon3310 | Stardance
|
tymon3310
|
1
|
2.0
|
8
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-09T21:44:15Z", "hours": 2.0, "multiplier": 4.1, "payout": 8, "blessing": "neutral", "text": "I made a slates - SLAck noTES - its in python and it was my first python project, but i think it went well", "repo": "https://github.com/Tymon3310/slates", "demo": "https://hackclub.enterprise.slack.com/archives/C0B9F4802MV"}]...
|
[{"post_id": 5908, "ts": "2026 [{"post_id": 5908, "ts": "2026-06-09T21:41:42Z", "hours": 0.7731, "text": "So i finally finished this bot, and even added multi-ping thing"}, {"post_id": 5221, "ts": "2026-06-08T22:37:34Z", "hours": 1.1892, "text": "So bot is working, but not perfect, like yyy it doesnt respond to @mentions - ikd why, also added good thing"}]...
|
Title: Slates - slack notes bot by @tymon3310 | St Title: Slates - slack notes bot by @tymon3310 | Stardance
Devlogs:
So bot is working, but not perfect, like yyy it doesnt respond to @mentions - ikd why, also added good thing
So i finally finished this bot, and even added multi-ping thing
Ships:
I made a slates - SLAck noTES - its in python and it was my first python project, but i think it went well...
|
1793566058.8260894
|
1793652458.8260894
|
|
13475
|
My awesome macropad! by @mjwheeler10310 | Stardanc My awesome macropad! by @mjwheeler10310 | Stardance...
|
mjwheeler10310
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @mjwheeler10310 | S Title: My awesome macropad! by @mjwheeler10310 | Stardance...
|
1793382562.75673
|
1793987362.75673
|
|
13476
|
Cyberdeck by @Alan | Stardance
|
Alan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cyberdeck by @Alan | Stardance
|
1793155659.2277634
|
1793760459.2277634
|
|
13477
|
Untitled by @Mang0 | Stardance
|
Mang0
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Mang0 | Stardance
|
1793364488.9655576
|
1793969288.9655576
|
|
13478
|
CalculOS by @davidv3767 | Stardance
|
davidv3767
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CalculOS by @davidv3767 | Stardance
|
1792921888.6742861
|
1793785888.6742861
|
|
13479
|
My awesome macropad! by @humancurry | Stardance
|
humancurry
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @humancurry | Stard Title: My awesome macropad! by @humancurry | Stardance...
|
1793314291.9065511
|
1793919091.9065511
|
|
13480
|
Ghost fighter 2D by @AustinSproutz | Stardance
|
AustinSproutz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ghost fighter 2D by @AustinSproutz | Starda Title: Ghost fighter 2D by @AustinSproutz | Stardance...
|
1793300141.4186049
|
1793904941.4186049
|
|
13481
|
Jmsa hydro hub by @lucasambroise27 | Stardance
|
lucasambroise27
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Jmsa hydro hub by @lucasambroise27 | Starda Title: Jmsa hydro hub by @lucasambroise27 | Stardance...
|
1793411496.881535
|
1794016296.881535
|
|
13482
|
milesOS by @miles_s_aguilar | Stardance
|
|
1
|
5.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-19T07:40:59Z", "hours": 5.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "First ship of my OS! Try it out! I ported my pokemon walking simulator into it, just to really test the capabilities of the browser. There is a notes app which also saves your notes to your browser, and an about me section as well. I plan to add more to this in the future", "repo": "https://github.com/stackofdoggos/DoggoOS", "demo": "https://milesaguilar.com/OS/"}]...
|
[{"post_id": 11751, "ts": "202 [{"post_id": 11751, "ts": "2026-06-19T04:14:10Z", "hours": 1.3164, "text": "Working on hosting – just waiting for SSL Certificate to be issued :) Also went ahead and implemented my pokemon project in here"}, {"post_id": 6321, "ts": "2026-06-10T17:13:26Z", "hours": 0.8036, "text": "Finished the fourth part of the webOS Jam! I’m thinking that maybe I want to pivot to a pokemon-themed browser? I’m really not sure, but I want a unifying theme that I like… but is still representative of me. At least the apps will be pokemon-themed. Anyways, I added a Kartana-themed notes app. I thought Kartana would be appropriate since it’s a pokemon modelled after origami!"}, {"post_id": 5740, "ts": "2026-06-09T17:15:37Z", "hours": 0.8353, "text": "Just finished the 3rd part of the webOS Jam. Along with achieving the required tasks, I included a macOS-inspired traffic light button menu in the header. This is the 2nd (in addition to the dog gif) improvement I have made over the guide. Something that was challenging to perfect was the little icons (specifically the chevrons) within each of the buttons. I’m not sure if I want to continue with a strictly macOS design philosophy, though. I anticipate I’ll add a finder and other advanced functionality. If I abide by a macOS design philosophy, that might make the UI unecessarily bloated so I might do some paper sketches of something that looks like macOS but is more simplistic. We’ll see, though!"}, {"post_id": 5244, "ts": "2026-06-08T23:07:49Z", "hours": 1.5997, "text": "First 2 Parts of webOS Jam! Added middle div, background image, and top bar. A challenge that I undertook for the top bar was adding the gif of the dog in the center."}]...
|
Title: milesOS by @miles_s_aguilar | Stardance
De Title: milesOS by @miles_s_aguilar | Stardance
Devlogs:
First 2 Parts of webOS Jam! Added middle div, background image, and top bar. A challenge that I undertook for the top bar was adding the gif of the dog in the center.
Just finished the 3rd part of the webOS Jam. Along with achieving the required tasks, I included a macOS-inspired traffic light button menu in the header. This is the 2nd (in addition to the dog gif) improvement I have made over the guide. Something that was challenging to perfect was the little icons (specifically the chevrons) within each of the buttons. I’m not sure if I want to continue with a strictly macOS design philosophy, though. I anticipate I’ll add a finder and other advanced functionality. If I abide by a macOS design philosophy, that might make the UI unecessarily bloated so I might do some paper sketches of something that looks like macOS but is more simplistic. We’ll see, though!
Finished the fourth part of the webOS Jam! I’m thinking that maybe I want to pivot to a pokemon-themed browser? I’m really not sure, but I want a unifying theme that I like… but is still representative of me. At least the apps will be pokemon-themed. Anyways, I added a Kartana-themed notes app. I thought Kartana would be appropriate since it’s a pokemon modelled after origami!
Working on hosting – just waiting for SSL Certificate to be issued :) Also went ahead and implemented my pokemon project in here
Ships:
First ship of my OS! Try it out! I ported my pokemon walking simulator into it, just to really test the capabilities of the browser. There is a notes app which also saves your notes to your browser, and an about me section as well. I plan to add more to this in the future...
|
1793570144.43794
|
1793656544.43794
|
|
13483
|
My awesome macropad! by @mach67443 | Stardance
|
mach67443
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @mach67443 | Starda Title: My awesome macropad! by @mach67443 | Stardance...
|
1793170317.8600283
|
1793775117.8600283
|
|
13484
|
Flamel Puzzle Box by @falcon | Stardance
|
falcon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Flamel Puzzle Box by @falcon | Stardance
|
1793134111.3148794
|
1793738911.3148794
|
|
13485
|
Untitled project by @drew_reasons | Stardance
|
drew_reasons
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @drew_reasons | Stardan Title: Untitled project by @drew_reasons | Stardance...
|
1793339839.6791863
|
1793944639.6791863
|
|
13486
|
My Custon Terminal by @suleymansade | Stardance
|
suleymansade
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My Custon Terminal by @suleymansade | Stard Title: My Custon Terminal by @suleymansade | Stardance...
|
1793530354.8989174
|
1794135154.8989174
|
|
13487
|
My awesome macropad! by @1696699 | Stardance
|
1696699
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @1696699 | Stardanc Title: My awesome macropad! by @1696699 | Stardance...
|
1793357762.0147123
|
1793962562.0147123
|
|
13488
|
AI Ethics for Beginners by @Maram | Stardance
|
Maram
|
0
|
1.1
|
0
|
[]
|
[{"post_id": 17152, "ts": "202 [{"post_id": 17152, "ts": "2026-06-27T20:53:50Z", "hours": 0.4294, "text": "🧠 Devlog #2 — Overcoming Technical Hurdles & Mastering the Workflow🛠️ The Hidden Challenge: Configuring the EnvironmentIn my previous Devlog, I mentioned my readiness to integrate tracking tools into my workflow. However, reality always has a way of testing a developer’s persistence! Today, I faced my first real DevOps/configuration challenge while trying to connect VS Code with the Hackatime servers.Instead of the smooth automatic setup, the configuration stalled, and I was met with frozen extension prompts. For a moment, it felt overwhelming, but this project is all about problem-solving.🔧 Going Under the Hood (Manual Configuration)Instead of giving up, I decided to go deeper into the environment settings:I bypassed the frozen UI and manually accessed the hidden configurations using Ctrl + Shift + P to open the .wakatime.cfg file.I successfully updated the configuration manually, embedding my unique API key and directing the API URL straight to the Hack Club server ( https://hackatime.hackclub.com/api/v1).During this setup, I also successfully integrated GitHub authentication within VS Code, creating a secure loop for my code sync and backup.⏳ Understanding the Logic of the Arcade DashboardAfter fixing the configuration, I noticed the Arcade dashboard still showed 0 Total hours. I learned an important lesson about how developer platforms work: the system requires a minimum of 15 minutes of continuous, active coding to send the first stable “heartbeat” and unlock the devlog link.This taught me that persistence is key, and instead of staring at a static counter, I needed to focus on what matters most—writing code!✨ Reflection: The Mindset of a DeveloperIf Version 1.0 of AI Ethics for Beginners taught me how to write HTML/CSS, today’s challenge taught me how to think like a real engineer. Debugging connection issues, modifying config files, and understanding data syncing are crucial parts of the real-world development workflow.Every error is just a lesson in disguise, and I am now more confident than ever as I continue building this project! 🚀"}, {"post_id": 17123, "ts": "2026-06-27T20:08:59Z", "hours": 0.6728, "text": "🧠 Devlog #1 — The Beginning of AI Ethics for Beginners 🌱 The Start: First Steps as a Beginner When I first started this project, I felt both excited and overwhelmed. The idea of building a complete educational website about AI Ethics was inspiring, but also challenging for someone still early in their coding journey. The challenge wasn’t just writing code—it was understanding how to turn a complex topic like “AI Ethics” into a simple, interactive, and beginner-friendly experience. HTML felt relatively easy to start with, while CSS required more trial and error to achieve a clean and structured design. JavaScript was the most challenging part, especially when implementing interactive features like Dark Mode and the AI Quiz. 🧩 The Biggest Development Challenge: Responsiveness My biggest challenge was making the website fully responsive across different devices. At first, some elements overlapped and the layout broke on mobile screens. This pushed me to rethink the structure of my design and experiment with Flexbox and Grid multiple times. Over time, I learned that good development is not only about writing code, but also about planning layouts and thinking in a structured way before implementation. Seeing the website finally adapt smoothly to both mobile and desktop screens felt like a real breakthrough moment for me. 🧭 Hackatime & First-Time Workflow Experience I want to mention that I did not track my development hours on Hackatime during the first two weeks of this project. As a beginner, this was my first time working with a structured time-tracking system, and my main focus was fully understanding the codebase and completing Version 1.0 in a stable and functional state. Because of this, I prioritized building the project first before integrating workflow tools like Hackatime. Now that the foundation is complete, I am ready to gradually integrate better tracking and organization into future updates. 🔄 Linking Version 1.0 to Future Development Version 1.0 represents the foundation of this project—focused on structure, clarity, and core functionality. Moving forward, I plan to evolve it into a more interactive and refined experience by improving the UI, expanding content, and adding more dynamic features. This project has taught me that development is an iterative process, where progress happens step by step rather than all at once. ✨ Reflection Writing my first Devlog has been an important milestone in my learning journey. I’ve learned that programming is not just about writing clean code—it’s about problem-solving, persistence, and continuous improvement. More importantly, this project helped me shift my mindset. I now see myself not just as a beginner, but as an aspiring developer actively building real and meaningful projects. 🚀"}]...
|
Title: AI Ethics for Beginners by @Maram | Stardan Title: AI Ethics for Beginners by @Maram | Stardance
Devlogs:
🧠 Devlog #1 — The Beginning of AI Ethics for Beginners 🌱 The Start: First Steps as a Beginner When I first started this project, I felt both excited and overwhelmed. The idea of building a complete educational website about AI Ethics was inspiring, but also challenging for someone still early in their coding journey. The challenge wasn’t just writing code—it was understanding how to turn a complex topic like “AI Ethics” into a simple, interactive, and beginner-friendly experience. HTML felt relatively easy to start with, while CSS required more trial and error to achieve a clean and structured design. JavaScript was the most challenging part, especially when implementing interactive features like Dark Mode and the AI Quiz. 🧩 The Biggest Development Challenge: Responsiveness My biggest challenge was making the website fully responsive across different devices. At first, some elements overlapped and the layout broke on mobile screens. This pushed me to rethink the structure of my design and experiment with Flexbox and Grid multiple times. Over time, I learned that good development is not only about writing code, but also about planning layouts and thinking in a structured way before implementation. Seeing the website finally adapt smoothly to both mobile and desktop screens felt like a real breakthrough moment for me. 🧭 Hackatime & First-Time Workflow Experience I want to mention that I did not track my development hours on Hackatime during the first two weeks of this project. As a beginner, this was my first time working with a structured time-tracking system, and my main focus was fully understanding the codebase and completing Version 1.0 in a stable and functional state. Because of this, I prioritized building the project first before integrating workflow tools like Hackatime. Now that the foundation is complete, I am ready to gradually integrate better tracking and organization into future updates. 🔄 Linking Version 1.0 to Future Development Version 1.0 represents the foundation of this project—focused on structure, clarity, and core functionality. Moving forward, I plan to evolve it into a more interactive and refined experience by improving the UI, expanding content, and adding more dynamic features. This project has taught me that development is an iterative process, where progress happens step by step rather than all at once. ✨ Reflection Writing my first Devlog has been an important milestone in my learning journey. I’ve learned that programming is not just about writing clean code—it’s about problem-solving, persistence, and continuous improvement. More importantly, this project helped me shift my mindset. I now see myself not just as a beginner, but as an aspiring developer actively building real and meaningful projects. 🚀
🧠 Devlog #2 — Overcoming Technical Hurdles & Mastering the Workflow🛠️ The Hidden Challenge: Configuring the EnvironmentIn my previous Devlog, I mentioned my readiness to integrate tracking tools into my workflow. However, reality always has a way of testing a developer’s persistence! Today, I faced my first real DevOps/configuration challenge while trying to connect VS Code with the Hackatime servers.Instead of the smooth automatic setup, the configuration stalled, and I was met with frozen extension prompts. For a moment, it felt overwhelming, but this project is all about problem-solving.🔧 Going Under the Hood (Manual Configuration)Instead of giving up, I decided to go deeper into the environment settings:I bypassed the frozen UI and manually accessed the hidden configurations using Ctrl + Shift + P to open the .wakatime.cfg file.I successfully updated the configuration manually, embedding my unique API key and directing the API URL straight to the Hack Club server ( https://hackatime.hackclub.com/api/v1).During this setup, I also successfully integrated GitHub authentication within VS Code, creating a secure loop for my code sync and backup.⏳ Understanding the Logic of the Arcade DashboardAfter fixing the configuration, I noticed the Arcade dashboard still showed 0 Total hours. I learned an important lesson about how developer platforms work: the system requires a minimum of 15 minutes of continuous, active coding to send the first stable “heartbeat” and unlock the devlog link.This taught me that persistence is key, and instead of staring at a static counter, I needed to focus on what matters most—writing code!✨ Reflection: The Mindset of a DeveloperIf Version 1.0 of AI Ethics for Beginners taught me how to write HTML/CSS, today’s challenge taught me how to think like a real engineer. Debugging connection issues, modifying config files, and understanding data syncing are crucial parts of the real-world development workflow.Every error is just a lesson in disguise, and I am now more confident than ever as I continue building this project! 🚀...
|
1793476528.1493144
|
1794081328.1493144
|
|
13489
|
espell by @aster | Stardance
|
aster
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: espell by @aster | Stardance
|
1793537373.5031576
|
1794142173.5031576
|
|
13490
|
Awesome Tanks: Reloaded by @Roly_Poly | Stardance
|
Roly_Poly
|
0
|
5.99
|
0
|
[]
|
[{"post_id": 15396, "ts": "202 [{"post_id": 15396, "ts": "2026-06-25T01:04:50Z", "hours": 1.2519, "text": "Sadly, I am not allotted enough time to work and therefore will be quitting the project. I may work on it, but I cannot meet the deadline. :( I’m thinking about instead working on a system to automatically read cards from games (Specifically battle games) and determine the outcome. This would mainly be used for games such as Star Wars Epic Duels, and Unmatched. I would also hope to add a hp tracker. If you want to work on it, please let me know! Here’s the github: https://github.com/RolyPolyLabs/awesome-tanks-reloaded"}, {"post_id": 6007, "ts": "2026-06-10T02:15:07Z", "hours": 2.2333, "text": "Added a music playlist, a way to set if you want sound or music on, and a button that links to Waterflame’s YouTube channel."}, {"post_id": 5405, "ts": "2026-06-09T04:55:14Z", "hours": 2.5003, "text": "So far, an animated Menu image has been added, with BG music. Next order of business it the text, and buttons."}]...
|
Title: Awesome Tanks: Reloaded by @Roly_Poly | Sta Title: Awesome Tanks: Reloaded by @Roly_Poly | Stardance
Devlogs:
So far, an animated Menu image has been added, with BG music. Next order of business it the text, and buttons.
Added a music playlist, a way to set if you want sound or music on, and a button that links to Waterflame’s YouTube channel.
Sadly, I am not allotted enough time to work and therefore will be quitting the project. I may work on it, but I cannot meet the deadline. :( I’m thinking about instead working on a system to automatically read cards from games (Specifically battle games) and determine the outcome. This would mainly be used for games such as Star Wars Epic Duels, and Unmatched. I would also hope to add a hp tracker. If you want to work on it, please let me know! Here’s the github: https://github.com/RolyPolyLabs/awesome-tanks-reloaded...
|
1793559149.9799147
|
1794163949.9799147
|
|
13491
|
Web OS All About Me by @wintermute | Stardance
|
wintermute
|
0
|
5.99
|
0
|
[]
|
[{"post_id": 7742, "ts": "2026 [{"post_id": 7742, "ts": "2026-06-12T22:36:45Z", "hours": 4.5061, "text": "Made welcome sign-in app, and library of my most played Steam games. Next: Make a projects library Wallpaper switcher My accounts app"}, {"post_id": 5275, "ts": "2026-06-09T00:03:39Z", "hours": 1.4883, "text": "Made basic taskbar"}]...
|
Title: Web OS All About Me by @wintermute | Starda Title: Web OS All About Me by @wintermute | Stardance
Devlogs:
Made basic taskbar
Made welcome sign-in app, and library of my most played Steam games. Next: Make a projects library Wallpaper switcher My accounts app...
|
1793450993.3080616
|
1794055793.3080616
|
|
13492
|
MaximusOS by @maximus4i | Stardance
|
maximus4i
|
0
|
3.22
|
0
|
[]
|
[{"post_id": 5884, "ts": "2026 [{"post_id": 5884, "ts": "2026-06-09T20:50:17Z", "hours": 1.5092, "text": "MaximusOS - Devlog 2 Put the welcome page into a window Added a background image Added a top(?)bar with a Cantaloupe, OS name and live time For the width of the taskbar I eyeballed it and used 98.7vw which, while it isnt the most elegant solution, works for me. Anything else I tried for the width resulted in it being too big and wider than the actual screen."}, {"post_id": 5735, "ts": "2026-06-09T17:11:14Z", "hours": 1.7097, "text": "MaximusOS – Devlog 1 What I built Personal intro page (MaximusOS) – HTML/CSS, no frameworks Added my intro, my NAI project with a screenshot, and basic styling Why Following the WebOS 1 mission from the missions tab. First time actually learning HTML properly rather than just having AI write everything."}]...
|
Title: MaximusOS by @maximus4i | Stardance
Devlog Title: MaximusOS by @maximus4i | Stardance
Devlogs:
MaximusOS – Devlog 1 What I built Personal intro page (MaximusOS) – HTML/CSS, no frameworks Added my intro, my NAI project with a screenshot, and basic styling Why Following the WebOS 1 mission from the missions tab. First time actually learning HTML properly rather than just having AI write everything.
MaximusOS - Devlog 2 Put the welcome page into a window Added a background image Added a top(?)bar with a Cantaloupe, OS name and live time For the width of the taskbar I eyeballed it and used 98.7vw which, while it isnt the most elegant solution, works for me. Anything else I tried for the width resulted in it being too big and wider than the actual screen....
|
1793534051.673773
|
1794138851.673773
|
|
13493
|
My very own WebOS by @Alan | Stardance
|
Alan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Alan | Stardance
|
1793407664.4837859
|
1794012464.4837859
|
|
13494
|
a gaus rifle by @peruviancorn1 | Stardance
|
peruviancorn1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: a gaus rifle by @peruviancorn1 | Stardance
|
1793231286.7636378
|
1793836086.7636378
|
|
13495
|
My very own WebOS by @NitorDei | Stardance
|
NitorDei
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @NitorDei | Stardance
|
1793181375.8405185
|
1793786175.8405185
|
|
13496
|
My very own WebOS by @Super | Stardance
|
Super
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Super | Stardance
|
1793480160.657113
|
1794084960.657113
|
|
13497
|
Untitled by @funfofacts | Stardance
|
funfofacts
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @funfofacts | Stardance
|
1793288922.7486959
|
1793893722.7486959
|
|
13498
|
20026 by @miles_s_aguilar | Stardance
|
|
1
|
1.39
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-10T17:39:25Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "A website in the theme of Jon Bois’ 17776 and 20020!!! I like how plain it looks. Functional. Please go check out his works if you like what you see.", "repo": "https://github.com/stackofdoggos/GYWP-Website", "demo": "https://milesaguilar.com/GYWP"}]...
|
[{"post_id": 26119, "ts": "202 [{"post_id": 26119, "ts": "2026-07-10T18:32:09Z", "hours": 0.3864, "text": "Hotfix: Fixed image not loading bug"}, {"post_id": 26075, "ts": "2026-07-10T17:36:12Z", "hours": 1.4347, "text": "20026 - A speculative fiction homage to Jon Bois’ 17776 and 20020 If you go read those works, this will make a lot more sense. Anyways, I decided to code an homage to Bois’ writing in order to hopefully get more people interested in anticipation of his next book, 50007! On my site, you’ll see I tried to emulate his style and wrote some sample text that paraphrases some of his work. The feature I decided to include was an API that fetched football games!"}]...
|
Title: 20026 by @miles_s_aguilar | Stardance
Devl Title: 20026 by @miles_s_aguilar | Stardance
Devlogs:
20026 - A speculative fiction homage to Jon Bois’ 17776 and 20020 If you go read those works, this will make a lot more sense. Anyways, I decided to code an homage to Bois’ writing in order to hopefully get more people interested in anticipation of his next book, 50007! On my site, you’ll see I tried to emulate his style and wrote some sample text that paraphrases some of his work. The feature I decided to include was an API that fetched football games!
Hotfix: Fixed image not loading bug
Ships:
A website in the theme of Jon Bois’ 17776 and 20020!!! I like how plain it looks. Functional. Please go check out his works if you like what you see....
|
1793468979.6403198
|
1793555379.6403198
|
|
13499
|
My very own WebOS by @Yusyra | Stardance
|
Yusyra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Yusyra | Stardance
|
1793256992.9114397
|
1793861792.9114397
|
|
13500
|
VocalFlow by @dxnkey | Stardance
|
dxnkey
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: VocalFlow by @dxnkey | Stardance
|
1793569788.8486314
|
1794174588.8486314
|