|
925
|
Snake Game by @haspritarestia | Stardance
|
haspritarestia
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Snake Game by @haspritarestia | Stardance
|
1792695144.203276
|
1793299944.203276
|
|
928
|
Ian Green's Portfolio Site by @academanic | St Ian Green's Portfolio Site by @academanic | Stardance...
|
academanic
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ian Green's Portfolio Site by @academan Title: Ian Green's Portfolio Site by @academanic | Stardance...
|
1792723806.0647194
|
1793328606.0647194
|
|
929
|
My awesome macropad! by @IKE | Stardance
|
IKE
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @IKE | Stardance
|
1792637547.9298494
|
1793242347.9298494
|
|
930
|
LayerLab by @Shreerang | Stardance
|
Shreerang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: LayerLab by @Shreerang | Stardance
|
1792928974.0925229
|
1793792974.0925229
|
|
931
|
RISC-V 32bit CPU by @captaintriton10 | Stardance
|
captaintriton10
|
1
|
17.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-13T20:41:40Z", "hours": 17.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "This was my second attempt at making a working RISC-V CPU, I’m really happy with where the project is currently. The most difficult part so far has been trying to debug it when it isn’t working, but I’ve managed to get assembly to run on it with video output, and also keyboard input. Next, I think I want to work on adding more extensions to the base ISA and writing more complex programs for it.", "repo": "https://github.com/CaptainTriton10/risc-v_v2", "demo": ""}]...
|
[{"post_id": 8201, "ts": "2026 [{"post_id": 8201, "ts": "2026-06-13T17:18:13Z", "hours": 1.6106, "text": "Worked some more on other typical features of a VGA text mode, such as highlighted text and blinking."}, {"post_id": 7699, "ts": "2026-06-12T21:05:48Z", "hours": 5.1781, "text": "As you can see below, I got keyboard input to work, so now I can write programs that use keyboard input. New features: Character colours UART input (keyboard input) It’s pretty cool that I can also write the devlog on the CPU with the custom assembly code I wrote!"}, {"post_id": 5201, "ts": "2026-06-08T21:59:22Z", "hours": 1.5792, "text": "I finally fixed the branch logic, and proved that it works with this simple counter that uses the conditional BGE (branch if greater than or equal) instruction."}, {"post_id": 4881, "ts": "2026-06-08T13:22:18Z", "hours": 5.6975, "text": "Currently working on debugging conditional branch instructions, as the wrong branch address is being targetted. Fortunately, I managed to fix the JAL and JALR jump instructions."}, {"post_id": 2053, "ts": "2026-06-04T10:47:06Z", "hours": 2.4369, "text": "This is a project I’ve been working on already a fair bit, trying to make a half-decent RISC-V CPU for use on the icepi-zero FPGA board (that I got from the previous Flavourtown event :D). This is a testbench I’m running, currently trying to debug jump and branch instructions not working. My next step is adding keyboard input through the UART protocol (universal asynchronous receiver-transmitter)"}]...
|
Title: RISC-V 32bit CPU by @captaintriton10 | Star Title: RISC-V 32bit CPU by @captaintriton10 | Stardance
Devlogs:
This is a project I’ve been working on already a fair bit, trying to make a half-decent RISC-V CPU for use on the icepi-zero FPGA board (that I got from the previous Flavourtown event :D). This is a testbench I’m running, currently trying to debug jump and branch instructions not working. My next step is adding keyboard input through the UART protocol (universal asynchronous receiver-transmitter)
Currently working on debugging conditional branch instructions, as the wrong branch address is being targetted. Fortunately, I managed to fix the JAL and JALR jump instructions.
I finally fixed the branch logic, and proved that it works with this simple counter that uses the conditional BGE (branch if greater than or equal) instruction.
As you can see below, I got keyboard input to work, so now I can write programs that use keyboard input. New features: Character colours UART input (keyboard input) It’s pretty cool that I can also write the devlog on the CPU with the custom assembly code I wrote!
Worked some more on other typical features of a VGA text mode, such as highlighted text and blinking.
Ships:
This was my second attempt at making a working RISC-V CPU, I’m really happy with where the project is currently. The most difficult part so far has been trying to debug it when it isn’t working, but I’ve managed to get assembly to run on it with video output, and also keyboard input. Next, I think I want to work on adding more extensions to the base ISA and writing more complex programs for it....
|
1793138086.1521528
|
1793224486.1521528
|
|
932
|
Fractured by @Accursed_Drifter | Stardance
|
Accursed_Drifter
|
0
|
17.61
|
0
|
[]
|
[{"post_id": 32203, "ts": "202 [{"post_id": 32203, "ts": "2026-07-21T06:54:12Z", "hours": 0.5175, "text": "Devlog #5 It’s been a bit since my last devlog but during that time I’ve been creating a bunch of the lore for my game and I’ve also recolored / redesigned a bunch of my assets (although there is still more to go). Currently I have a base for how I want my character to look like, I did originally want to have a very detailed character but after recoloring him and it took over 4 days to do just that I’ve come to the realization that if I want to have this as a playable demo before stardance ends I’m prolly gonna have to try my best with the free resources I have access to. (I still don’t know how I feel with how the player looks against the tiles) That being said, I think next I’m gonna make a few actual levels so that I can start working on integrating lore into the game and give it life."}, {"post_id": 29336, "ts": "2026-07-16T06:48:43Z", "hours": 4.3933, "text": "Devlog #4 Since my last devlog I’ve added a few new features that I think can be really useful when I end up adding lore and purpose to everything later The first thing I worked on was changing around my animations for right now as I found an editable sprite template on itch.io that i wanted to use so that making an actual character later may be easier. The next thing i worked on was having an attack combo to give the player more than just one attack. the final feature i worked on was making levels. This was by far the hardest thing to code into my game and it isn’t even close. It took multiple tutorial videos and many hours to get all of the code correct and actually working. Now that it’s done though, i can begin experimenting with different free tile sheets to find what type of style would fit my game the best. Next i think i’m going to attempt to code what i believe will be an even harder feature than levels, save states. However if it goes how i think its gonna go i may just end up working on making a main menu system (aka a pause button that works)."}, {"post_id": 28655, "ts": "2026-07-15T01:17:54Z", "hours": 2.2544, "text": "Devlog #3 It’s been a while since my last devlog as i took a break from coding for a few days and writing the code for the enemy ai took a while. So far i’ve finished giving the enemy a basic attack and giving it the abaility to agro the player. Once the player gets close enough the enemy will try to chase then and once they get even closer the attack sequence begins. Next i’m going to work on polishing the current code I have and work on more advanced things for the player like giving him more moves."}, {"post_id": 25155, "ts": "2026-07-09T06:03:34Z", "hours": 3.0983, "text": "Devlog #2 Today was mostly spent redoing how I had the animations structured in order to add some new ones like attacks. After I got finished with the rabbit hole that is animation trees, I finally got a basic light attack finished and i was able to make a test enemy to work on the code for taking damage from the players attacks. The player can now attack anything with a specific function and deal damage to it. This test enemy in particular doesn’t do anything besides takes hits and perish Tomorrow, I think I am going to work on making the enemy have its own attacks and work on adding agro to the enemy. As this project grows I am starting to get a feel on how I want this to be and can hopefully start working on assets soon."}, {"post_id": 24563, "ts": "2026-07-08T07:09:29Z", "hours": 7.3425, "text": "Devlog #1 I am making a godot game in order to learn GS script Currently i worked on making the base for some features like; movement, double jump, wall slide + jump, basic enemies, and a npc dialogue system. Next I need to go over all the code i’ve written in order to polish some bugs and make it neater. The current assets are mostly free assets from itch.io but once i reach a certain point im gonna make whole new sprites and tile sheets."}]...
|
Title: Fractured by @Accursed_Drifter | Stardance
Title: Fractured by @Accursed_Drifter | Stardance
Devlogs:
Devlog #1 I am making a godot game in order to learn GS script Currently i worked on making the base for some features like; movement, double jump, wall slide + jump, basic enemies, and a npc dialogue system. Next I need to go over all the code i’ve written in order to polish some bugs and make it neater. The current assets are mostly free assets from itch.io but once i reach a certain point im gonna make whole new sprites and tile sheets.
Devlog #2 Today was mostly spent redoing how I had the animations structured in order to add some new ones like attacks. After I got finished with the rabbit hole that is animation trees, I finally got a basic light attack finished and i was able to make a test enemy to work on the code for taking damage from the players attacks. The player can now attack anything with a specific function and deal damage to it. This test enemy in particular doesn’t do anything besides takes hits and perish Tomorrow, I think I am going to work on making the enemy have its own attacks and work on adding agro to the enemy. As this project grows I am starting to get a feel on how I want this to be and can hopefully start working on assets soon.
Devlog #3 It’s been a while since my last devlog as i took a break from coding for a few days and writing the code for the enemy ai took a while. So far i’ve finished giving the enemy a basic attack and giving it the abaility to agro the player. Once the player gets close enough the enemy will try to chase then and once they get even closer the attack sequence begins. Next i’m going to work on polishing the current code I have and work on more advanced things for the player like giving him more moves.
Devlog #4 Since my last devlog I’ve added a few new features that I think can be really useful when I end up adding lore and purpose to everything later The first thing I worked on was changing around my animations for right now as I found an editable sprite template on itch.io that i wanted to use so that making an actual character later may be easier. The next thing i worked on was having an attack combo to give the player more than just one attack. the final feature i worked on was making levels. This was by far the hardest thing to code into my game and it isn’t even close. It took multiple tutorial videos and many hours to get all of the code correct and actually working. Now that it’s done though, i can begin experimenting with different free tile sheets to find what type of style would fit my game the best. Next i think i’m going to attempt to code what i believe will be an even harder feature than levels, save states. However if it goes how i think its gonna go i may just end up working on making a main menu system (aka a pause button that works).
Devlog #5 It’s been a bit since my last devlog but during that time I’ve been creating a bunch of the lore for my game and I’ve also recolored / redesigned a bunch of my assets (although there is still more to go). Currently I have a base for how I want my character to look like, I did originally want to have a very detailed character but after recoloring him and it took over 4 days to do just that I’ve come to the realization that if I want to have this as a playable demo before stardance ends I’m prolly gonna have to try my best with the free resources I have access to. (I still don’t know how I feel with how the player looks against the tiles) That being said, I think next I’m gonna make a few actual levels so that I can start working on integrating lore into the game and give it life....
|
1793288870.4621208
|
1793893670.4621208
|
|
933
|
My awesome macropad! by @ReanickaB | Stardance
|
ReanickaB
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ReanickaB | Starda Title: My awesome macropad! by @ReanickaB | Stardance...
|
1792788662.2924695
|
1793393462.2924695
|
|
934
|
My awesome macropad! by @Harry_wct | Stardance
|
Harry_wct
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Harry_wct | Starda Title: My awesome macropad! by @Harry_wct | Stardance...
|
1793181068.569485
|
1793785868.569485
|
|
935
|
Map.fm by @ama | Stardance
|
ama
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Map.fm by @ama | Stardance
|
1793263896.6494339
|
1793868696.6494339
|
|
936
|
Ice Cream by @vessel | Stardance
|
vessel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ice Cream by @vessel | Stardance
|
1792748942.1961145
|
1793353742.1961145
|
|
937
|
My first slack bot! by @kanchankumari1992214 | Sta My first slack bot! by @kanchankumari1992214 | Stardance...
|
kanchankumari1992214
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @kanchankumari199221 Title: My first slack bot! by @kanchankumari1992214 | Stardance...
|
1793227978.112089
|
1793832778.112089
|
|
938
|
My awesome macropad! by @kanchankumari1992214 | St My awesome macropad! by @kanchankumari1992214 | Stardance...
|
kanchankumari1992214
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @kanchankumari19922 Title: My awesome macropad! by @kanchankumari1992214 | Stardance...
|
1793224101.2177787
|
1793828901.2177787
|
|
939
|
LUNAR-HAL by @INiNiDS | Stardance
|
INiNiDS
|
1
|
78.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-29T18:18:07Z", "hours": 78.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Finally shipping this! It honestly took forever and I burned out twice along the way, but I pushed through to get it over the finish line. Try out the live demo or grab the local build. Heads up: the web demo might feel super sluggish since the models are running on Heroku, so expect some delay. Also, all demo sessions share the same persistent worlds! Have Fun!", "repo": "https://github.com/ininids/lunar-hal", "demo": "https://lnhal.ininids.in.rs"}]...
|
[{"post_id": 75310, "ts": "202 [{"post_id": 75310, "ts": "2026-09-29T18:16:50Z", "hours": 5.1756, "text": "Alright, final devlog! Went all-in on bug squashing for this one—crushed a ton of issues, finally got CI completely green and stable, cleared out all the CodeQL alerts, and pushed the demo build. So yeah… I’m officially shipping now!"}, {"post_id": 68044, "ts": "2026-09-14T12:49:45Z", "hours": 12.1378, "text": "DevLog #9: Checkpoint Hardening & Stage 5 GNN Kinematics Convergence * This session was focused on a deep technical milestone: diagnosing a critical engine staging bug in LUNAR-HAL and driving the Stellar GNN-kinematics pipeline through the completion of Stage 5. 1. 🛠️ Staging Architecture & Atomic Checkpoint RCA (Rust) Diagnosed and resolved a critical issue in the --resume workflow where staging logic triggered a self-copy ( src == dst ), truncating output checkpoint weights upon restart. Implemented robust canonical path checking ( std::fs: :canonicalize ) to ensure fully atomic weight persistence across interruption signals ( SIGINT / SIGTERM ). Hardened checkpoint state serialization, eliminating filesystem race conditions during runtime hot-reloads. 2. Stage 5: GNN-Kinematics Training Executed the 200-epoch training run for the galactic velocity prediction model ($v_x, v_y, v_z$ derived from positions + photometry). Validated host telemetry: stable VRAM footprint on local NVIDIA GeForce RTX 5070 (~3.1 GB / 12 GB allocated) with optimal throughput (~30s / epoch). 3. Loss & Convergence Verification Train Loss: Decreased to ~0.7660 . Validation Loss: Reached a clean, stable quasi-stationary plateau at ~0.7694 . Physics Constraint: Invariant equilibrium maintained throughout ( phys_loss ≈ 0.7700 ), demonstrating high generalization without overfitting."}, {"post_id": 45625, "ts": "2026-08-12T07:29:27Z", "hours": 3.5756, "text": "* 🚀 DevLog #8: The Great Pivot — From Game to Technical Stellar Platform * The mission has changed. Following the deployment of the WebOS in DevLog #7, we realized that the “game” mechanics were holding back the true potential of the engine. This update marks our transition from a simulation with combat elements to a high-fidelity technical platform for stellar generation, research, and visualization. We have officially executed the transition plan, gutting the “game” and hardening the “platform.” The Great Purge: lunar-stellar-core The era of lunar-game-backend is over. We have performed a git mv on the heart of the engine to establish a strict architectural boundary. Logic Extraction: We have completely removed all traces of Enemies, Projectiles, HP, Attacks, and the “Attention Map.” The simulation no longer cares if you are “watching” a star; it only cares about the physics. The Core: The new lunar-stellar-core crate is now framework-agnostic. It handles only the technical state: camera math, sector caching, and the pipeline results. Terminology Shift: “World” is now “StarScene.” It’s no longer a level; it’s a coordinate-stable dataset. Unified Multi-Platform Deployment We’ve consolidated our frontend logic. Instead of separate builds, we now have a single Managed Frontend Service with a unified builder. Target Switching: Through the lns utility, we can now hot-swap between web , desktop , and android targets. Android Integration: The platform now supports Android NDK/SDK. We’ve replaced mouse-only logic with Pointer Events , enabling touch-based pan/zoom/selection. Runtime Config: The backend now dynamically injects the correct URL (handling the 10.0.2.2 emulator trap) based on the active platform. Sandbox 2.0: The Admin Overlay The Sandbox is no longer a separate copy of the simulation. It has evolved into a Meta-Management Shell for the real frontend. The Iframe Bridge: The Sandbox now embeds the live lunar-frontend via an iframe. Communication Protocol: We implemented a versioned postMessage protocol in lunar-structures . The Sandbox sends Admin Commands (CreateStar, SetCamera) and receives Scene Events (StarSelected). Permanent SIREN Gallery & Drag-and-Drop We’ve moved from “latest renders” to a persistent filesystem-based catalog . Atomic Persistence: Stars created via AI or manual tools are now saved as GalleryStar DTOs. Each star gets its own directory with metadata, SIREN textures, and thumbnails. True Drag-and-Drop: We’ve implemented a custom drag-session in the WebOS. You can now drag a star from the Gallery into the Sandbox to insert it into the live scene, and vice versa. Found Issues The transition hasn’t been without its casualties. Two “boss-level” bugs have appeared during the implementation of the new WebOS logic: Sandbox Handshake & OS Crash: Currently, the Sandbox is failing to “see” the Frontend service through the iframe bridge. Even worse, attempting to initialize the connection often results in a total OS-level hang , crashing the Testbench entirely. We are currently investigating if this is a circular dependency in the backend or a massive memory leak during the handshake. The “Minimize” Trap: While we implemented WindowLifecycle to keep applications alive in the background using display: none , we hit a critical logic error. Once an app is minimized, the “un-minimize” (maximize) function fails to trigger . The app remains in a state of digital limbo, perfectly preserved but completely inaccessible."}, {"post_id": 41159, "ts": "2026-08-05T06:03:25Z", "hours": 3.4289, "text": "DevLog #7: WebOS Evolution, The Black Room, and “lns” Orchestration This update marks a fundamental shift in how we interact with the simulation ecosystem. We have moved away from static dashboards to a fully dynamic WebOS environment within lunar-testbench , alongside a complete overhaul of our launching utility. Lunar-Testbench: The WebOS Overhaul The Testbench has been reimagined as a “Black Room” —a dark, immersive workspace where everything begins with three spotlights. The Spotlight Mechanic The interface features three dormant flashlights. Service Ignition: Clicking a spotlight “turns it on” and launches its corresponding backend service. Dynamic App Injection: Once a service is active, the specific applications depending on that service manifest below the spotlight. The Sandbox: Our most complex tool, the Sandbox , now requires all three services to be active simultaneously, setting the stage for deep-system integration in future updates. The Dock To manage the chaos of multiple windows, we’ve implemented a Bottom Dock . Every running application is pinned here, allowing for seamless switching between training, validation, and live simulation environments. Orchestration: From “lunar-start” to “lns” The way we boot the engine has been streamlined. We’ve stripped the heavy lifting out of the primary entry point to create a more modular startup flow. lns Utility: lunar-start has been evolved into lns —a lightweight micro-utility. Its sole purpose is to initialize the Testbench and trigger the backend. lunar-start-backend: This is a new, dedicated service that acts as the primary launcher. It monitors and manages the lifecycle of all other applications within the suite, ensuring that when you click a service in the UI, the backend is ready to deploy it."}, {"post_id": 31372, "ts": "2026-07-19T18:15:40Z", "hours": 8.1406, "text": "🚀 DevLog #6: Hyper-Optimization, Core Threat Integration, and New Swarm Archetypes ⚙️ Optimization: The Fight for Nanoseconds With the transition to a full 3D environment and manual entity manipulation, the load on the CPU and memory bus grew exponentially. So we tried to optimize as much as possible. 👾 Integration: Enemies in the Core Loop Previously, hostile entities existed only as isolated test units (testbench). Now, enemy fleets are officially hardcoded into the base simulation loop. Autonomous Background AI: Enemy behavior is no longer bound to the player’s viewport. Strategic fleets live their own lives in the background—conquering systems and harvesting resources—even if you are editing a galaxy millions of light-years away. Dynamic Pathfinding: The toughest challenge was stabilizing AI during manual manipulation. If you grab a planet and toss it in front of an enemy dreadnought, the pathfinding algorithm instantly recalculates a safe bypass vector based on the newly altered gravitational signature of that sector. 🛸 New Threat Archetypes: The Utility-Driven AI Each enemy now operates on a Utility AI system, calculating its next move based on distance, health ratios, and—most importantly—the Player’s Attention . We have categorized the hostile forces into six distinct tactical archetypes: Archetype Role Logic Highlight The Tank Heavy Juggernaut Berserk Logic: Its utility increases as its health drops. It becomes more aggressive the harder you try to kill it. The Thief Rapid Raider Attention-Aware: Only strikes stars when the player is looking away ( t_neglect > 15.0 ). High speed (20.0) allows for quick hit-and-run ops. The Invisible Stealth Saboteur Adaptive Camouflage: Maintains $0.05$ visibility. Only reveals itself when the player’s cursor “scans” over it or during brief power-grid flickers. The Scavenger Opportunistic Parasite Pack Mentality: Heavily prioritizes stars that are already under attack by other units to “steal” the resources. The Backstabber Chaos Agent Infighting: If it detects a fellow enemy with $<35 % $ HP, it will betray its own kind to secure the kill for itself. The Coward Skittish Scout Self-Preservation: Immediately generates an escape vector if the player’s “God-Hand” (cursor) gets too close or a Tank enters its vicinity. 🧠 The “Attention Map” Integration The most advanced part of this integration is how these entities interact with the Lunar-Frontend . We don’t just track positions; we track the player’s focus: d_mouse Factor: Enemies calculate their distance to your cursor. Thieves and Cowards use this to decide when to flee or stay in the shadows. t_neglect Metric: The simulation tracks how long it’s been since you last interacted with a specific star. The longer a sector is neglected, the higher the “utility” for an invasion force to move in. ⚔️ Combat Mechanics: Physical Projectiles vs. Direct Damage To keep the simulation performant while maintaining visual fidelity: Star Assaults: Enemies fire physical Projectile entities. Each has its own speed, radius, and damage value, allowing players to potentially intercept them or warp them with gravitational anomalies. Internal Infighting: When enemies like the Backstabber turn on their allies, the damage is processed via an optimized EnemyDamage buffer, bypassing heavy projectile physics for internal “swarm” calculations. Note: ISP issues and local routing to the Hack Club site still make uploading updates feel like sending signals through a dense asteroid belt."}, {"post_id": 12966, "ts": "2026-06-21T06:54:53Z", "hours": 18.7053, "text": "DevLog #5: God-Mode Editor, Crate Separation, and Stealth Features Following the development of “Mission Control,” the project has transitioned into a full 3D environment. The cosmos is no longer just being generated; it can now be manipulated in real-time. Project “Lunar-Hal”: God-Mode Editor The new 3D editor allows for direct manipulation of the simulation rather than just monitoring metrics through the TestBench. Free-Fly Mode: A fully functional in-engine 3D editor. Users can toggle Creator Mode to navigate through stellar clusters at high speeds. Real-Time Manipulation: Selecting a star allows for immediate overrides of mass, spectral class, and luminosity. The SIREN engine recalculates astrophysics on the fly, updating the frontend visuals without performance drops. Architecture: The Great Crate Separation To manage codebase complexity, the backend has undergone a significant architectural refactor. All core gameplay logic has been isolated into a dedicated, independent Rust crate. Modular Design: Rendering overhead and editor scaffolding are now separated from pure game rules, physics, and state machines. Improved Compilation: Logic changes no longer require recompiling the entire project. Crates now compile in isolation, allowing for faster iteration and cleaner incremental builds. Inventory System and Stealth Mechanics Work has begun on a functional inventory system designed to hold “Creator Tools.” This system moves beyond traditional item management into world manipulation. Drag-and-Drop Reality: Mechanics are being implemented to allow users to grab celestial bodies directly from the viewport to rearrange solar systems manually. Entity Interaction: These telekinetic mechanics are also being tested on combat entities. This allows for manual interaction with hostile fleets, such as testing physics logic by moving units into gravitational anomalies like black hole event horizons. Lunar-Frontend: Enhanced UI The UI has been updated to accommodate the new editor and inventory capabilities: Creator Widgets: The modular sidebar now includes inspection panels for editor controls and inventory management. Optimized Streaming: The frontend provides a seamless bridge between TestBench metrics and the heavy 3D viewport, maintaining high performance during active manipulation. Roadmap The next phase of development will focus on: Running heavy simulations of billions of stars in background threads while maintaining editor stability. Stabilizing enemy pathfinding during manual entity manipulation. Preparing the architecture for multiplayer synchronization. Note: DevLog updates may be sporadic due to local ISP and network routing issues affecting access to the Hack Club site. Space logistics are complex, but terrestrial routing remains a significant challenge."}, {"post_id": 7982, "ts": "2026-06-13T09:54:00Z", "hours": 10.8433, "text": "🚀 DevLog #4: The God Mode Dashboard & Stellar Genesis! If Day 3 was about plugging the matrix straight into the engine’s spine, today we built the ultimate command center around it. No more chaos, no more manual config-wrangling via terminal. We just deployed a full-scale infrastructure for total cosmic control! Here is the tactical breakdown of what just dropped in the engineering bay: ⚙️ Project “TestBench”: Total Control & Validation We got tired of guessing what’s actually happening inside our AI’s digital brains, so we built TestBench—the ultimate proving ground for complete testing, training, and validation of every single AI model in the project. Backend Fusion: The whole thing is hardwired straight into our reactive Rust backend. God-Tier UX: Now, benchmarking a dataset, checking loss curves, validating weights, or fine-tuning a model is a matter of a few clicks without ever leaving the ecosystem. Real-time telemetry monitoring. Honestly? It’s clean, it’s seamless, and it just works. 🌟 Meet SIREN: The Star Architect Our AI fleet just got a massive reinforcement. Say hello to our newest model—SIREN. Her sole, monumental objective is the procedural generation of the stars themselves. No more random glowing spheres. SIREN calculates physics, luminosity, spectral classes, and spawns unique, structured astrophysical objects. The cosmos isn’t just procedural anymore; it’s beautifully complex and scientifically backed. 🎛️ Lunar-Frontend: The Creator’s Control Panel A cosmic backend deserves a killer visual interface. We gave lunar-frontend a massive upgrade to make managing this madness an absolute breeze: The Sidebar: We coded a modular, highly responsive sidebar. All your tools, model toggles, and data streams are now neatly organized and right at your fingertips. Next Stop: Unleashing SIREN onto the global map, syncing its generation directly with TestBench metrics, and forcing the frontend to smoothly render billions of new star systems without dropping a single frame! 🚀"}, {"post_id": 4775, "ts": "2026-06-08T08:22:17Z", "hours": 9.8683, "text": "🚀 DevLog #3: The Neural Awakening & Backend Fusion! 🪐 Day 2 was chaos, but Day 3? We just plugged the matrix straight into the spine of the engine! 🧠✨ Remember that “confused toaster” from the last devlog? Yeah, well, it just evolved into a full-blown stellar intellect. The pipeline is locked, loaded, and absolutely cooking. Here is the tactical breakdown of what just dropped in the engineering bay: 🌌 The Big Brain Upgrade (Model & Data): We didn’t just tweak the model; we completely rebuilt its reality. We scraped, cleaned, and injected a massive new dataset, pushing our local parameter model to the absolute limit. No more hallucinating dead stars — lnai now actually understands the cosmic data it’s processing. 🔗 The Great Backend Fusion: The neural net is officially out of the sandbox and merged with the core Rust backend! We wired the prediction pipelines directly into our engine architecture. It’s fast, it’s memory-safe, and it operates with zero friction. Data is flowing from the neural layers to the backend loops in real-time. 🏎️ Zero Meltdown, Pure Performance: Training and running local models usually turns your rig into a literal space heater, but we optimized the living hell out of the inference pipelines. The memory footprint is clean, the tokens are flying, and your GPU can actually breathe while rendering the cosmos. The foundation is solid, the telemetry is clean, and the local universe finally has a brain that doesn’t just work — it thinks . Next stop: weaponizing this intelligence for procedural generation and forcing that flight physics engine to respect the laws of space! 🛰️🔥"}, {"post_id": 1972, "ts": "2026-06-04T07:13:17Z", "hours": 2.9592, "text": "🚀 DevLog #2: Neural Overdrive & Brainstorming LUNAR-AI! 🪐 Day 1 is in the books, and we are officially cooking! We’re pushing the boundaries of our infinite, local-first universe, and things are getting wild in the engineering bay. Here is the lowdown on what just dropped: 🧠 Project LUNAR-AI (lnai) is ALIVE: We officially laid down the first lines of code for our core AI driver! The mission? Giving your local universe a brain. No external API calls, no corporate clouds—just raw, local intelligence. 📉 Reality Check (The Results): Okay, look… right now, the results are, let’s say, highly questionable . It’s giving “confused toaster” more than “galactic supercomputer,” but hey, Rome wasn’t built in a day, and an infinite universe needs a little chaos first. 🛠️ Absolute Grind Mode: The output might be mid right now, but the workflow is at an all-time high. We are working 25/7, refactoring the neural pipelines, and optimizing the backend to make sure this local LLM integration doesn’t melt your PC. The brain is wired, the bugs are being hunted, and the grind never stops. Next stop: making lnai actually smart and finally getting that flight physics engine to behave! 🛰️✨"}, {"post_id": 717, "ts": "2026-06-02T09:35:55Z", "hours": 3.0953, "text": "🚀 DevLog #1: Ignition & Cosmic Foundations for LUNAR-HAL! 🪐 Day 0 is officially complete. We are building an infinite, AI-driven space sandbox powered completely by your local hardware, and the base is locked down: 🌌 Mission Control: Prepared the repository, set up community standards, and went full open-source under the AGPL v3 license to keep our local engine free forever. 💻 Frontend Setup: Fired up the project using Rust + Dioxus! Built the core architecture and launched the first three foundational viewports: Home, About, and Contact. 🛠️ The Manifesto: Designed a killer glassmorphic UI layout and integrated our “Broke-Tech” framework—proudly rendering procedural worlds directly on your GPU. Zero server costs, zero latency, infinite universe. Next stop: implementing the flight physics and interactive star canvas! 🛰️✨"}]...
|
Title: LUNAR-HAL by @INiNiDS | Stardance
Devlogs: Title: LUNAR-HAL by @INiNiDS | Stardance
Devlogs:
🚀 DevLog #1: Ignition & Cosmic Foundations for LUNAR-HAL! 🪐 Day 0 is officially complete. We are building an infinite, AI-driven space sandbox powered completely by your local hardware, and the base is locked down: 🌌 Mission Control: Prepared the repository, set up community standards, and went full open-source under the AGPL v3 license to keep our local engine free forever. 💻 Frontend Setup: Fired up the project using Rust + Dioxus! Built the core architecture and launched the first three foundational viewports: Home, About, and Contact. 🛠️ The Manifesto: Designed a killer glassmorphic UI layout and integrated our “Broke-Tech” framework—proudly rendering procedural worlds directly on your GPU. Zero server costs, zero latency, infinite universe. Next stop: implementing the flight physics and interactive star canvas! 🛰️✨
🚀 DevLog #2: Neural Overdrive & Brainstorming LUNAR-AI! 🪐 Day 1 is in the books, and we are officially cooking! We’re pushing the boundaries of our infinite, local-first universe, and things are getting wild in the engineering bay. Here is the lowdown on what just dropped: 🧠 Project LUNAR-AI (lnai) is ALIVE: We officially laid down the first lines of code for our core AI driver! The mission? Giving your local universe a brain. No external API calls, no corporate clouds—just raw, local intelligence. 📉 Reality Check (The Results): Okay, look… right now, the results are, let’s say, highly questionable . It’s giving “confused toaster” more than “galactic supercomputer,” but hey, Rome wasn’t built in a day, and an infinite universe needs a little chaos first. 🛠️ Absolute Grind Mode: The output might be mid right now, but the workflow is at an all-time high. We are working 25/7, refactoring the neural pipelines, and optimizing the backend to make sure this local LLM integration doesn’t melt your PC. The brain is wired, the bugs are being hunted, and the grind never stops. Next stop: making lnai actually smart and finally getting that flight physics engine to behave! 🛰️✨
🚀 DevLog #3: The Neural Awakening & Backend Fusion! 🪐 Day 2 was chaos, but Day 3? We just plugged the matrix straight into the spine of the engine! 🧠✨ Remember that “confused toaster” from the last devlog? Yeah, well, it just evolved into a full-blown stellar intellect. The pipeline is locked, loaded, and absolutely cooking. Here is the tactical breakdown of what just dropped in the engineering bay: 🌌 The Big Brain Upgrade (Model & Data): We didn’t just tweak the model; we completely rebuilt its reality. We scraped, cleaned, and injected a massive new dataset, pushing our local parameter model to the absolute limit. No more hallucinating dead stars — lnai now actually understands the cosmic data it’s processing. 🔗 The Great Backend Fusion: The neural net is officially out of the sandbox and merged with the core Rust backend! We wired the prediction pipelines directly into our engine architecture. It’s fast, it’s memory-safe, and it operates with zero friction. Data is flowing from the neural layers to the backend loops in real-time. 🏎️ Zero Meltdown, Pure Performance: Training and running local models usually turns your rig into a literal space heater, but we optimized the living hell out of the inference pipelines. The memory footprint is clean, the tokens are flying, and your GPU can actually breathe while rendering the cosmos. The foundation is solid, the telemetry is clean, and the local universe finally has a brain that doesn’t just work — it thinks . Next stop: weaponizing this intelligence for procedural generation and forcing that flight physics engine to respect the laws of space! 🛰️🔥
🚀 DevLog #4: The God Mode Dashboard & Stellar Genesis! If Day 3 was about plugging the matrix straight into the engine’s spine, today we built the ultimate command center around it. No more chaos, no more manual config-wrangling via terminal. We just deployed a full-scale infrastructure for total cosmic control! Here is the tactical breakdown of what just dropped in the engineering bay: ⚙️ Project “TestBench”: Total Control & Validation We got tired of guessing what’s actually happening inside our AI’s digital brains, so we built TestBench—the ultimate proving ground for complete testing, training, and validation of every single AI model in the project. Backend Fusion: The whole thing is hardwired straight into our reactive Rust backend. God-Tier UX: Now, benchmarking a dataset, checking loss curves, validating weights, or fine-tuning a model is a matter of a few clicks without ever leaving the ecosystem. Real-time telemetry monitoring. Honestly? It’s clean, it’s seamless, and it just works. 🌟 Meet SIREN: The Star Architect Our AI fleet just got a massive reinforcement. Say hello to our newest model—SIREN. Her sole, monumental objective is the procedural generation of the stars themselves. No more random glowing spheres. SIREN calculates physics, luminosity, spectral classes, and spawns unique, structured astrophysical objects. The cosmos isn’t just procedural anymore; it’s beautifully complex and scientifically backed. 🎛️ Lunar-Frontend: The Creator’s Control Panel A cosmic backend deserves a killer visual interface. We gave lunar-frontend a massive upgrade to make managing this madness an absolute breeze: The Sidebar: We coded a modular, highly responsive sidebar. All your tools, model toggles, and data streams are now neatly organized and right at your fingertips. Next Stop: Unleashing SIREN onto the global map, syncing its generation directly with TestBench metrics, and forcing the frontend to smoothly render billions of new star systems without dropping a single frame! 🚀
DevLog #5: God-Mode Editor, Crate Separation, and Stealth Features Following the development of “Mission Control,” the project has transitioned into a full 3D environment. The cosmos is no longer just being generated; it can now be manipulated in real-time. Project “Lunar-Hal”: God-Mode Editor The new 3D editor allows for direct manipulation of the simulation rather than just monitoring metrics through the TestBench. Free-Fly Mode: A fully functional in-engine 3D editor. Users can toggle Creator Mode to navigate through stellar clusters at high speeds. Real-Time Manipulation: Selecting a star allows for immediate overrides of mass, spectral class, and luminosity. The SIREN engine recalculates astrophysics on the fly, updating the frontend visuals without performance drops. Architecture: The Great Crate Separation To manage codebase complexity, the backend has undergone a significant architectural refactor. All core gameplay logic has been isolated into a dedicated, independent Rust crate. Modular Design: Rendering overhead and editor scaffolding are now separated from pure game rules, physics, and state machines. Improved Compilation: Logic changes no longer require recompiling the entire project. Crates now compile in isolation, allowing for faster iteration and cleaner incremental builds. Inventory System and Stealth Mechanics Work has begun on a functional inventory system designed to hold “Creator Tools.” This system moves beyond traditional item management into world manipulation. Drag-and-Drop Reality: Mechanics are being implemented to allow users to grab celestial bodies directly from the viewport to rearrange solar systems manually. Entity Interaction: These telekinetic mechanics are also being tested on combat entities. This allows for manual interaction with hostile fleets, such as testing physics logic by moving units into gravitational anomalies like black hole event horizons. Lunar-Frontend: Enhanced UI The UI has been updated to accommodate the new editor and inventory capabilities: Creator Widgets: The modular sidebar now includes inspection panels for editor controls and inventory management. Optimized Streaming: The frontend provides a seamless bridge between TestBench metrics and the heavy 3D viewport, maintaining high performance during active manipulation. Roadmap The next phase of development will focus on: Running heavy simulations of billions of stars in background threads while maintaining editor stability. Stabilizing enemy pathfinding during manual entity manipulation. Preparing the architecture for multiplayer synchronization. Note: DevLog updates may be sporadic due to local ISP and network routing issues affecting access to the Hack Club site. Space logistics are complex, but terrestrial routing remains a significant challenge.
🚀 DevLog #6: Hyper-Optimization, Core Threat Integration, and New Swarm Archetypes ⚙️ Optimization: The Fight for Nanoseconds With the transition to a full 3D environment and manual entity manipulation, the load on the CPU and memory bus grew exponentially. So we tried to optimize as much as possible. 👾 Integration: Enemies in the Core Loop Previously, hostile entities existed only as isolated test units (testbench). Now, enemy fleets are officially hardcoded into the base simulation loop. Autonomous Background AI: Enemy behavior is no longer bound to the player’s viewport. Strategic fleets live their own lives in the background—conquering systems and harvesting resources—even if you are editing a galaxy millions of light-years away. Dynamic Pathfinding: The toughest challenge was stabilizing AI during manual manipulation. If you grab a planet and toss it in front of an enemy dreadnought, the pathfinding algorithm instantly recalculates a safe bypass vector based on the newly altered gravitational signature of that sector. 🛸 New Threat Archetypes: The Utility-Driven AI Each enemy now operates on a Utility AI system, calculating its next move based on distance, health ratios, and—most importantly—the Player’s Attention . We have categorized the hostile forces into six distinct tactical archetypes: Archetype Role Logic Highlight The Tank Heavy Juggernaut Berserk Logic: Its utility increases as its health drops. It becomes more aggressive the harder you try to kill it. The Thief Rapid Raider Attention-Aware: Only strikes stars when the player is looking away ( t_neglect > 15.0 ). High speed (20.0) allows for quick hit-and-run ops. The Invisible Stealth Saboteur Adaptive Camouflage: Maintains $0.05$ visibility. Only reveals itself when the player’s cursor “scans” over it or during brief power-grid flickers. The Scavenger Opportunistic Parasite Pack Mentality: Heavily prioritizes stars that are already under attack by other units to “steal” the resources. The Backstabber Chaos Agent Infighting: If it detects a fellow enemy with $<35 % $ HP, it will betray its own kind to secure the kill for itself. The Coward Skittish Scout Self-Preservation: Immediately generates an escape vector if the player’s “God-Hand” (cursor) gets too close or a Tank enters its vicinity. 🧠 The “Attention Map” Integration The most advanced part of this integration is how these entities interact with the Lunar-Frontend . We don’t just track positions; we track the player’s focus: d_mouse Factor: Enemies calculate their distance to your cursor. Thieves and Cowards use this to decide when to flee or stay in the shadows. t_neglect Metric: The simulation tracks how long it’s been since you last interacted with a specific star. The longer a sector is neglected, the higher the “utility” for an invasion force to move in. ⚔️ Combat Mechanics: Physical Projectiles vs. Direct Damage To keep the simulation performant while maintaining visual fidelity: Star Assaults: Enemies fire physical Projectile entities. Each has its own speed, radius, and damage value, allowing players to potentially intercept them or warp them with gravitational anomalies. Internal Infighting: When enemies like the Backstabber turn on their allies, the damage is processed via an optimized EnemyDamage buffer, bypassing heavy projectile physics for internal “swarm” calculations. Note: ISP issues and local routing to the Hack Club site still make uploading updates feel like sending signals through a dense asteroid belt.
DevLog #7: WebOS Evolution, The Black Room, and “lns” Orchestration This update marks a fundamental shift in how we interact with the simulation ecosystem. We have moved away from static dashboards to a fully dynamic WebOS environment within lunar-testbench , alongside a complete overhaul of our launching utility. Lunar-Testbench: The WebOS Overhaul The Testbench has been reimagined as a “Black Room” —a dark, immersive workspace where everything begins with three spotlights. The Spotlight Mechanic The interface features three dormant flashlights. Service Ignition: Clicking a spotlight “turns it on” and launches its corresponding backend service. Dynamic App Injection: Once a service is active, the specific applications depending on that service manifest below the spotlight. The Sandbox: Our most complex tool, the Sandbox , now requires all three services to be active simultaneously, setting the stage for deep-system integration in future updates. The Dock To manage the chaos of multiple windows, we’ve implemented a Bottom Dock . Every running application is pinned here, allowing for seamless switching between training, validation, and live simulation environments. Orchestration: From “lunar-start” to “lns” The way we boot the engine has been streamlined. We’ve stripped the heavy lifting out of the primary entry point to create a more modular startup flow. lns Utility: lunar-start has been evolved into lns —a lightweight micro-utility. Its sole purpose is to initialize the Testbench and trigger the backend. lunar-start-backend: This is a new, dedicated service that acts as the primary launcher. It monitors and manages the lifecycle of all other applications within the suite, ensuring that when you click a service in the UI, the backend is ready to deploy it.
* 🚀 DevLog #8: The Great Pivot — From Game to Technical Stellar Platform * The mission has changed. Following the deployment of the WebOS in DevLog #7, we realized that the “game” mechanics were holding back the true potential of the engine. This update marks our transition from a simulation with combat elements to a high-fidelity technical platform for stellar generation, research, and visualization. We have officially executed the transition plan, gutting the “game” and hardening the “platform.” The Great Purge: lunar-stellar-core The era of lunar-game-backend is over. We have performed a git mv on the heart of the engine to establish a strict architectural boundary. Logic Extraction: We have completely removed all traces of Enemies, Projectiles, HP, Attacks, and the “Attention Map.” The simulation no longer cares if you are “watching” a star; it only cares about the physics. The Core: The new lunar-stellar-core crate is now framework-agnostic. It handles only the technical state: camera math, sector caching, and the pipeline results. Terminology Shift: “World” is now “StarScene.” It’s no longer a level; it’s a coordinate-stable dataset. Unified Multi-Platform Deployment We’ve consolidated our frontend logic. Instead of separate builds, we now have a single Managed Frontend Service with a unified builder. Target Switching: Through the lns utility, we can now hot-swap between web , desktop , and android targets. Android Integration: The platform now supports Android NDK/SDK. We’ve replaced mouse-only logic with Pointer Events , enabling touch-based pan/zoom/selection. Runtime Config: The backend now dynamically injects the correct URL (handling the 10.0.2.2 emulator trap) based on the active platform. Sandbox 2.0: The Admin Overlay The Sandbox is no longer a separate copy of the simulation. It has evolved into a Meta-Management Shell for the real frontend. The Iframe Bridge: The Sandbox now embeds the live lunar-frontend via an iframe. Communication Protocol: We implemented a versioned postMessage protocol in lunar-structures . The Sandbox sends Admin Commands (CreateStar, SetCamera) and receives Scene Events (StarSelected). Permanent SIREN Gallery & Drag-and-Drop We’ve moved from “latest renders” to a persistent filesystem-based catalog . Atomic Persistence: Stars created via AI or manual tools are now saved as GalleryStar DTOs. Each star gets its own directory with metadata, SIREN textures, and thumbnails. True Drag-and-Drop: We’ve implemented a custom drag-session in the WebOS. You can now drag a star from the Gallery into the Sandbox to insert it into the live scene, and vice versa. Found Issues The transition hasn’t been without its casualties. Two “boss-level” bugs have appeared during the implementation of the new WebOS logic: Sandbox Handshake & OS Crash: Currently, the Sandbox is failing to “see” the Frontend service through the iframe bridge. Even worse, attempting to initialize the connection often results in a total OS-level hang , crashing the Testbench entirely. We are currently investigating if this is a circular dependency in the backend or a massive memory leak during the handshake. The “Minimize” Trap: While we implemented WindowLifecycle to keep applications alive in the background using display: none , we hit a critical logic error. Once an app is minimized, the “un-minimize” (maximize) function fails to trigger . The app remains in a state of digital limbo, perfectly preserved but completely inaccessible.
DevLog #9: Checkpoint Hardening & Stage 5 GNN Kinematics Convergence * This session was focused on a deep technical milestone: diagnosing a critical engine staging bug in LUNAR-HAL and driving the Stellar GNN-kinematics pipeline through the completion of Stage 5. 1. 🛠️ Staging Architecture & Atomic Checkpoint RCA (Rust) Diagnosed and resolved a critical issue in the --resume workflow where staging logic triggered a self-copy ( src == dst ), truncating output checkpoint weights upon restart. Implemented robust canonical path checking ( std::fs: :canonicalize ) to ensure fully atomic weight persistence across interruption signals ( SIGINT / SIGTERM ). Hardened checkpoint state serialization, eliminating filesystem race conditions during runtime hot-reloads. 2. Stage 5: GNN-Kinematics Training Executed the 200-epoch training run for the galactic velocity prediction model ($v_x, v_y, v_z$ derived from positions + photometry). Validated host telemetry: stable VRAM footprint on local NVIDIA GeForce RTX 5070 (~3.1 GB / 12 GB allocated) with optimal throughput (~30s / epoch). 3. Loss & Convergence Verification Train Loss: Decreased to ~0.7660 . Validation Loss: Reached a clean, stable quasi-stationary plateau at ~0.7694 . Physics Constraint: Invariant equilibrium maintained throughout ( phys_loss ≈ 0.7700 ), demonstrating high generalization without overfitting.
Alright, final devlog! Went all-in on bug squashing for this one—crushed a ton of issues, finally got CI completely green and stable, cleared out all the CodeQL alerts, and pushed the demo build. So yeah… I’m officially shipping now!
Ships:
Finally shipping this! It honestly took forever and I burned out twice along the way, but I pushed through to get it over the finish line. Try out the live demo or grab the local build. Heads up: the web demo might feel super sluggish since the models are running on Heroku, so expect some delay. Also, all demo sessions share the same persistent worlds! Have Fun!...
|
1793152252.9342802
|
1793238652.9342802
|
|
940
|
Spacetex by @stemdood44 | Stardance
|
stemdood44
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Spacetex by @stemdood44 | Stardance
|
1792788639.4259224
|
1793393439.4259224
|
|
941
|
Untitled project by @Ila | Stardance
|
Ila
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Ila | Stardance
|
1793145259.0274227
|
1793750059.0274227
|
|
942
|
Munni and prism by @Munnisparkle | Stardance
|
Munnisparkle
|
0
|
0.35
|
0
|
[]
|
[{"post_id": 208, "ts": "2026- [{"post_id": 208, "ts": "2026-06-01T08:32:11Z", "hours": 0.3517, "text": "Started setting up the project folder and files for Munni and Prism in VS Code! Created index.html, style.css and game.js. now wrote little bit of html i know thats the conversation blw the characters in the game"}]...
|
Title: Munni and prism by @Munnisparkle | Stardanc Title: Munni and prism by @Munnisparkle | Stardance
Devlogs:
Started setting up the project folder and files for Munni and Prism in VS Code! Created index.html, style.css and game.js. now wrote little bit of html i know thats the conversation blw the characters in the game...
|
1792670068.659922
|
1793274868.659922
|
|
943
|
Project See The Voices Nepal's website by @Pas Project See The Voices Nepal's website by @Pasta | Stardance...
|
Pasta
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Project See The Voices Nepal's website Title: Project See The Voices Nepal's website by @Pasta | Stardance...
|
1792630457.32414
|
1793235257.32414
|
|
944
|
Timer! by @TAP | Stardance
|
TAP
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Timer! by @TAP | Stardance
|
1792803031.500145
|
1793407831.500145
|
|
945
|
StudyQuest by @BlackShell | Stardance
|
BlackShell
|
0
|
5.81
|
0
|
[]
|
[{"post_id": 77724, "ts": "202 [{"post_id": 77724, "ts": "2026-10-08T03:02:24Z", "hours": 2.9167, "text": "I developing on mac"}, {"post_id": 2568, "ts": "2026-06-05T04:19:09Z", "hours": 0.9864, "text": "StudyQuest progress Implemented the core progression system: • XP system • Level system • Level up at 100 XP • XP progress bar • Study session tracking • Study time tracking The app now tracks study sessions and study time while rewarding progress with XP and levels. Built with Flutter."}, {"post_id": 2162, "ts": "2026-06-04T14:35:48Z", "hours": 0.8278, "text": "StudyQuest now runs on iOS 📱 Current features: XP system Level system Level up at 100 XP Next features: XP progress bar Study timer Streak tracking Built with Flutter."}, {"post_id": 1951, "ts": "2026-06-04T06:18:37Z", "hours": 1.0806, "text": "Started development on StudyQuest, a gamified study tracker built with Flutter. Today I: Created the Flutter project structure Set up GitHub and pushed the initial code Built the first home screen Added placeholders for XP, levels, study time, and streaks Learned more about Flutter widgets and layout structure Next, I plan to add a study timer and an XP system."}]...
|
Title: StudyQuest by @BlackShell | Stardance
Devl Title: StudyQuest by @BlackShell | Stardance
Devlogs:
Started development on StudyQuest, a gamified study tracker built with Flutter. Today I: Created the Flutter project structure Set up GitHub and pushed the initial code Built the first home screen Added placeholders for XP, levels, study time, and streaks Learned more about Flutter widgets and layout structure Next, I plan to add a study timer and an XP system.
StudyQuest now runs on iOS 📱 Current features: XP system Level system Level up at 100 XP Next features: XP progress bar Study timer Streak tracking Built with Flutter.
StudyQuest progress Implemented the core progression system: • XP system • Level system • Level up at 100 XP • XP progress bar • Study session tracking • Study time tracking The app now tracks study sessions and study time while rewarding progress with XP and levels. Built with Flutter.
I developing on mac...
|
1793249733.386274
|
1793854533.386274
|
|
946
|
MacroPad V4 by @TAP | Stardance
|
TAP
|
0
|
0.73
|
0
|
[]
|
[{"post_id": 25162, "ts": "202 [{"post_id": 25162, "ts": "2026-07-09T06:36:22Z", "hours": 0.7272, "text": "MADE THE SCHEMATIC! This is probably one of the most cutest schematic I have ever made! Its a pretty simple plan tho! This has 3x3 switch matrix, 9 sk6812 mini-e in a daisy chain and an 0.91” OLED"}]...
|
Title: MacroPad V4 by @TAP | Stardance
Devlogs:
M Title: MacroPad V4 by @TAP | Stardance
Devlogs:
MADE THE SCHEMATIC! This is probably one of the most cutest schematic I have ever made! Its a pretty simple plan tho! This has 3x3 switch matrix, 9 sk6812 mini-e in a daisy chain and an 0.91” OLED...
|
1792939933.6606238
|
1793803933.6606238
|
|
947
|
BlackShell Golf by @BlackShell | Stardance
|
BlackShell
|
0
|
7.94
|
0
|
[]
|
[{"post_id": 77965, "ts": "202 [{"post_id": 77965, "ts": "2026-10-09T01:20:22Z", "hours": 2.4283, "text": "Build watch App!!"}, {"post_id": 77722, "ts": "2026-10-08T02:55:39Z", "hours": 5.1039, "text": "Liquid Glass update!!!"}, {"post_id": 212, "ts": "2026-06-01T08:45:03Z", "hours": 0.4108, "text": "Today I prepared BlackShell Golf for Stardance and published the project on GitHub. BlackShell Golf is a Flutter app for live multiplayer golf scoring. Players can create a room, join a room, and track golf rounds together. Today I connected the project repository, organized the codebase, and tested the app in the browser. Next, I plan to improve score saving, round history, and the overall user experience. Screenshot attached."}]...
|
Title: BlackShell Golf by @BlackShell | Stardance
Title: BlackShell Golf by @BlackShell | Stardance
Devlogs:
Today I prepared BlackShell Golf for Stardance and published the project on GitHub. BlackShell Golf is a Flutter app for live multiplayer golf scoring. Players can create a room, join a room, and track golf rounds together. Today I connected the project repository, organized the codebase, and tested the app in the browser. Next, I plan to improve score saving, round history, and the overall user experience. Screenshot attached.
Liquid Glass update!!!
Build watch App!!...
|
1793238468.3275115
|
1793843268.3275115
|
|
948
|
My awesome macropad! by @Kanata | Stardance
|
Kanata
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Kanata | Stardance
|
1792778036.074678
|
1793382836.074678
|
|
949
|
Untitled project by @Kanata | Stardance
|
Kanata
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Kanata | Stardance
|
1792734584.5063086
|
1793339384.5063086
|
|
951
|
Website by @Kanata | Stardance
|
Kanata
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-01T11:45:45Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I created a simple website to learn HTML. It includes headings, links, lists, tables, and a form.The most challenging part was publishing the website with GitHub Pages. I had to learn how GitHub Pages works and how to configure the project correctly.I am proud that I built and published my first website by myself.This project is a beginner HTML practice project. It focuses on learning the basics rather than creating a professional website.", "repo": "https://github.com/k4n474/Website", "demo": "https://k4n474.github.io/Website/"}]...
|
[{"post_id": 230, "ts": "2026- [{"post_id": 230, "ts": "2026-06-01T10:58:25Z", "hours": 0.8114, "text": "I wrote code using a wider variety of tags."}, {"post_id": 204, "ts": "2026-06-01T08:05:04Z", "hours": 0.3136, "text": "I’m creating a simple webpage to learn HTML"}]...
|
Title: Website by @Kanata | Stardance
Devlogs:
I’ Title: Website by @Kanata | Stardance
Devlogs:
I’m creating a simple webpage to learn HTML
I wrote code using a wider variety of tags.
Ships:
I created a simple website to learn HTML. It includes headings, links, lists, tables, and a form.The most challenging part was publishing the website with GitHub Pages. I had to learn how GitHub Pages works and how to configure the project correctly.I am proud that I built and published my first website by myself.This project is a beginner HTML practice project. It focuses on learning the basics rather than creating a professional website....
|
1793303257.8074543
|
1793389657.8074543
|
|
952
|
Defqon Stage Editor by @defqonstage | Stardance
|
defqonstage
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Defqon Stage Editor by @defqonstage | Stard Title: Defqon Stage Editor by @defqonstage | Stardance...
|
1792778051.785657
|
1793382851.785657
|
|
953
|
Untitled project by @shaan | Stardance
|
shaan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @shaan | Stardance
|
1792756221.7080698
|
1793361021.7080698
|
|
954
|
My awesome macropad! by @aaditrai | Stardance
|
aaditrai
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @aaditrai | Stardan Title: My awesome macropad! by @aaditrai | Stardance...
|
1792788583.1426423
|
1793393383.1426423
|
|
955
|
My first slack bot! by @shravs | Stardance
|
shravs
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @shravs | Stardance
|
1792810200.1596885
|
1793415000.1596885
|
|
956
|
not-so-scary-game by @hiral | Stardance
|
hiral
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: not-so-scary-game by @hiral | Stardance
|
1793134143.6836095
|
1793738943.6836095
|
|
957
|
Anti-theft laser detecter by @Srijit | Stardance
|
Srijit
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Anti-theft laser detecter by @Srijit | Star Title: Anti-theft laser detecter by @Srijit | Stardance...
|
1792659088.7670248
|
1793263888.7670248
|
|
958
|
My first slack bot! by @boring-name | Stardance
|
boring-name
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @boring-name | Stard Title: My first slack bot! by @boring-name | Stardance...
|
1793231628.5105429
|
1793836428.5105429
|
|
959
|
Ebeep by @Avizi | Stardance
|
Avizi
|
1
|
85.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-23T10:29:40Z", "hours": 85.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "my project is a “beeper” with an eink display, it features three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday later this month!", "repo": "https://github.com/Av1zi/Ebeep", "demo": ""}]...
|
[{"post_id": 33374, "ts": "202 [{"post_id": 33374, "ts": "2026-07-23T07:45:06Z", "hours": 11.1325, "text": "Devlog #18 - The Final One my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I built two of them and gifted one to my GF for her birthday! so this is it, the last devlog for Ebeep. i finished the Blender showcase animation, check it out ⬇️⬇️⬇️ took way longer than expected since I’ve never really used blender for anything like this before, but I’m happy with how it turned out. (or kicad) as for the PCB, the design is fully done, routed, and ready to export to gerbers, but I decided not to actually order it right now. the perfboard build already works and does the job, and the PCB was mostly a “because I can” side project once I started documenting everything (devlog #16 lol). might revisit it in the future if I ever want to build a v2 or make more of these, but for now the current build is what’s shipping as “done.” looking back this project went through basically everything a project can go through: missed deadlines, a broken 3d printer, a bug that silently deleted my girlfriend’s messages for a week without me noticing, failed prints, finals eating my motivation and somehow it still came out the other side working, on both devices, doing everything I wanted it to do. if I had to do it again I’d probably: start the PCB earlier instead of perfboard + rework set up proper MQTT retained-message handling from day one instead of patching it in later. budget way more time for the case than I did CAD alone ate multiple redesigns and i still needed help from my friend to finish it i really need to work on my CAD skills but honestly, for a project that started as “let’s port some code to an esp32 I’m scared to solder,” I’m really proud of where it landed. whats next? id really love to keep working and making it the best i can (the 3d render is really rough as i had to finish it TODAY and some of the code is still messy), but realistically, nothing planned this is the ‘finish’ line. maybe a better PCB with a good showcase with cleaner code and a case that actually houses the PCB someday, maybe not. either way, thanks to everyone who followed along since the start. TL;DR finished the showcase render, PCB design is complete but staying unbuilt for now, and the project is officially ‘done’. thanks for reading 🎉"}, {"post_id": 32922, "ts": "2026-07-22T12:11:04Z", "hours": 8.3689, "text": "Devlog #17 pcb is done and showcase animation my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! i finished the pcb and refined it! yesterday ish i had like an idea to make an animation in blender to showcase the device for the final devlog so i started working on it nect devlog will be the final one! (i think)"}, {"post_id": 30954, "ts": "2026-07-18T23:27:55Z", "hours": 10.3483, "text": "Devlog #16 documenting (and accidental PCB?) my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! so i finally sat down to start documenting my work, but while doing so… i might have gone a little over the top and started designing a custom PCB for the project ;-;it’s pretty fun ngl, i’m really enjoying working on it! ohh also, i fixed a MAJOR bug in my code. i have absolutely no clue how i didn’t notice it earlier, but when i was trying to fix bugs last week, i accidentally introduced a new one that deleted messages the exact second they arrived. so yeah… i didn’t get any messages from my girlfriend for a whole week lol. oops. and if anyone here knows how to make pcbs please help me i have no clue what im doing thanks!"}, {"post_id": 29566, "ts": "2026-07-16T16:26:24Z", "hours": 1.05, "text": "Devlog #15 Small changes my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together.I’ll be building two of them and gifting one to my GF for her birthday! i a couple of issues with blackjack: * can now display around 11 cards(more than that is extremly unlikely so i didnt bother) * dealer no longer draws cards if u bust * now the split looks much much cleaner now even if one device is disconnected the msg will be stored and displayed when the device connects to the wifi some other stuff i forgot"}, {"post_id": 28397, "ts": "2026-07-14T17:07:08Z", "hours": 3.7961, "text": "Devlog #14 - The project is compleated! (if there arent ane new bugs) my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! what did i do? i added connect 4 & blackJack both of em should work now i fixed a problem with the wifi connection made new art for the connect 4 & blackjack to replace the place holders. i have already gifted the other device and shes probably reading this devlog so hello and sorry it took long all i have to do is finish up the docs and the github page and then were ready to ship"}, {"post_id": 25346, "ts": "2026-07-09T16:06:15Z", "hours": 6.6869, "text": "Devlog #13 The project is completed (mostly) my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together.I’ll be building two of them and gifting one to my GF for her birthday! Just finished building my second ebeep device! The good news are it came out SO much better than the first one, It might not be super obvious from the photos but trust me the difference IRL is HUGE. The Type-C connection actually fits properly this time! and the two devices are communicating great, and I even managed to run multiple rounds of Tic-Tac-Toe. . As for the bad news, It seems like every other day I encounter a new issue usually related to Wi-Fi or server connectivity. hopefully my janky code i wrote so far successfully patched them out. I’m trying to squash as many as possible before I gift one to my girlfriend later this week. If I have time, I’ll try to finish up Connect 4 as well and i think ill give up on the poker game i dont want to delay it any longer lol. . Also, for those who were wondering, we landed in 30th place (out of 36?) at the FRC competition"}, {"post_id": 19344, "ts": "2026-06-30T16:56:56Z", "hours": 4.9703, "text": "Devlog #12 THE FIRST ONE IS DONE my project in short to those who havent seen it yet: My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! I soldered everything up, crammed it into the box, and it works now. hooray! The only issue I had was that the negative terminal on the bottom of the esp32 disconnected when I tried to fit it into the box. I’m now in the process of testing and ironing out bugs. So far i found two the battery readout is weird but it works, and the battery runs out way too quickly, so I’m trying to fix those issues. unfortunately, I don’t know when I’ll be able to finish the second one since the 3D printer broke down (I literally bought it last week ) It took me a while to finish this one since I had an FRC competition to attend and couldnt finish everything in 1 day."}, {"post_id": 16357, "ts": "2026-06-26T16:42:53Z", "hours": 6.3789, "text": "Devlog #11 we are 80% there! my project in short my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up.ill be building two of them and gifting one to my GF on her birthday! what did i do? i finished the CAD (i hope), and started soldering everything together with the help of my dad(hes the best) the electronic plate is coming together nicly its not done yet but its mostly done!! and i will probably finish the first beeper TODAY!"}, {"post_id": 14554, "ts": "2026-06-23T18:34:15Z", "hours": 2.7692, "text": "Devlog #10 i missed the deadline :( (failed print after failed print) my project in short my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday! Her birthday was yesterday, i missed the deadline and my motivation is at an all time low. The code is done (i hope) but the 3d case is so horrible. its way too big and wastes so much material on useless spots and way too little on places in places that need it. the whole thing needs a redesign and I’m working on that but unfortunately ill have to postpone it by at least two days since i have 1 more final exam i need to take. and i just feel awful that i have to give her the birthday present with a week+ delay TL;DR i missed the dead line and I’m really down, the case needs a major redesign and im yet to even start soldering the code probably is done"}, {"post_id": 13239, "ts": "2026-06-21T17:54:28Z", "hours": 2.5981, "text": "Devlog #9 (1 day until GF birthday) TL;DR: finished tic tac toe, added icons to show if the bepper lost internet connection and updated the 3d model my project in short my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday later this month! what did i do? online tic tac toe works now icons to show if the connection is lost and automatically reconnect updated 3d model to actually use M4 screws how do they talk to eachother? i made a comic to demonstrate it cuz ik yall aint reading all that but if u want to read it in more detail: the first player sends to the other a message “TTT_JOIN” in /games then start listening to /games/TTT (channel where all the game communication will happen) the second player will receive that message and will get a notification that someone is waiting to play tic tac toe then if he wants he will join the the game and send a msg on /games/TTT that he joined both screens will update and show the tic tac toe board. each player will take his turn and send a message in /games/TTT with a row and a column of the place he chose to play and the screen will update accordingly. when the game ends they could request a rematch and will start this whole process again"}, {"post_id": 12102, "ts": "2026-06-19T19:09:33Z", "hours": 8.5831, "text": "Devlog 8 (3 DAYS LEFT UNTILL GF BIRTHDAY) CAD IS DONE what did i do? finished the cad hopefully will start printing on sunday when my new 3d printer arrives (and hopefully wont have to change anything bc i have 3 DAYS LEFT ) I REWORKED THE ENTIRE MQTT CODE (made the beeper talk to each other differently in order to make games possible) almost done with the online tic tac toe (the more indepth devlog will be the next one) fixed like 4 bugs and another 2 popped up kill me whats next? finish EVERYTHING before my GF birthday on Tuesday (sorry for this short devlog dont have much to say about the cad model the one on the code will come tmr hopefully)"}, {"post_id": 7523, "ts": "2026-06-12T15:45:53Z", "hours": 4.0075, "text": "Devlog #7 Its a big one what did i do? added a way to set the wifi password from your phone made the beeper actually able to talk and send messages fixed a lot of bugs that popped up after the switch to esp32 added a way to scroll faster for convince me and my friend started designing a case we will 3d print whats next? finish design a 3d printed case maybe finish one of the games side notes: i added a short video with a demo of everything working together would love to hear your thoughts about it background music: In the pool by kensuke ushio (forgor who made the piano cover im using) update on me: physics finals is in 3 days and I’m so cooked might not be able to design the case for a while"}, {"post_id": 6183, "ts": "2026-06-10T11:59:50Z", "hours": 2.0744, "text": "Devlog #6 my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday later this month! what did i do? the esp32 arrived yesterday its much much smaller than i expected and i have no clue how im going to solder it later ;-; anyways so i worked on porting my current code from arduino to esp32, its seems to be working as intended. now i just need to add all the missing features like the mqtt protocol and wifi portal. whats next? add the wifi portal (so i wont have to hardcode the wifi credentials in the code) make the esp32 work with the mqtt protocol design a 3d printed case finish the games (not really a priority right now) update on me: more finals soon yay :/"}, {"post_id": 4877, "ts": "2026-06-08T13:14:45Z", "hours": 1.6892, "text": "Devlog #5! to those haven’t seen my project yet in short: my project is a “beeper” with an eink display ill be building two of them and gifting one to my GF on her birthday later this month! it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up what did i do? i was bored since i cant really work on the project and have to wait for my esp32 to arrive >:( so i went on a side quest and added the game select menu, nothing major i also need to design the icons since they are just place holders from google whats next? wait for esp32 to arrive >:( actually make blackjack and the other games ask my friend to 3d help me 3d model the case update on me: sorry for the long wait i had a bunch of shit 2 do and war with iran ;-;"}, {"post_id": 3074, "ts": "2026-06-05T23:33:08Z", "hours": 2.1186, "text": "Devlog #4! . to those haven’t seen my project yet in short: my project is a “beeper” with an eink display ill be building two of them and gifting one to my GF on her birthday later this month! it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up what did i do? . i tired connecting my current setup to the MQTT broker and make it actually able to talk to other devices BUT IT DIDNT WORK i spent hours debugging it, only to come to the conclusion that i CANT do it with my current setup and i NEED the esp32 to continue coding or at least it will be much easier every day that passes i hate AliExpress even more it should have arrived 4 days ago ;-; the only useful i did is figure out how .gitignore work so now i dont need a hotspot lol whats next? wait for esp32 to arrive >:( update on me: . nothing rely new from yesterday . side note i just noticed ive never actually shown you how the UI i made previously works. so i attached a short walk through"}, {"post_id": 2424, "ts": "2026-06-04T22:02:29Z", "hours": 1.2675, "text": "Devlog #3 . to those haven’t seen my project yet in short: . my project is a “beeper” with an eink display (like the name suggests). ill be building two of them and gifting one to my GF on her birthday later this month! it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up what did i do today? . today i added Wifi! since i still dont have my esp32 (damm you AliExpress and your slow shipping), i wont be able to use the cool web UI library i wanted to use… so i changed my phones hotspot to the most boring name & password i could think of and hard coded those credentials in (i dont know how to hide sensitive info from GitHub and didn’t want to add my real wifi lol) edit: i also added the little wifi ui thingy you see in the picture whats next? i will research more about the MQTT protocol my two devices will use to communicate add end to end encryption (both devices will have a hard coded secret “password” they will use to encrypt and decrypt the messages) if esp arrives soon (WHICH IT SHOULD) ill connect it to the bread board and change the code accordingly and much more just later on id love to hear what your thoughts in the comments :) update on me: today was my computer science finals and it was 5 hours. i was pretty burned out after that so didn’t do that much today either :/ the next couple days are packed with personal stuff and more final exams so u might not hear from me soon… ill try to work on this project at least an hour every day so if u do it will be small changes unfortunately"}, {"post_id": 1723, "ts": "2026-06-03T21:50:03Z", "hours": 1.3117, "text": "Devlog #2 My project Ebeep is starting to take a bit more shape! . my project is a “beeper” with an eink display (like the name suggests). ill be building two of them and gifting one to my GF on her birthday later this month! . i rewrote almost the ENTIRE UI since last time the code i wrote was pretty bad and it had terrible UI. hopefully tomorrow i could work on actually connecting it to the internet and work on basic end to end encryption (maybe?). also i really hope ill get my esp32s soon so i could actually test my code on that instead of my arduino and design my 3d case for it. . today and yesterday werent very productive since my CS finals are tomorrow! so wish me luck!"}, {"post_id": 1088, "ts": "2026-06-02T22:16:57Z", "hours": 5.4681, "text": "day 1 of my ebeep project, i managed to make the eInk display work properly after HOURS of trouble shooting code. (apparently if it says 3.3V only it means dont connect a 5V Arduino to it oops) i managed to make the sick UI hopefully the esp32 and the battery will come soon so i can start designing the case for it"}]...
|
Title: Ebeep by @Avizi | Stardance
Devlogs:
day 1 Title: Ebeep by @Avizi | Stardance
Devlogs:
day 1 of my ebeep project, i managed to make the eInk display work properly after HOURS of trouble shooting code. (apparently if it says 3.3V only it means dont connect a 5V Arduino to it oops) i managed to make the sick UI hopefully the esp32 and the battery will come soon so i can start designing the case for it
Devlog #2 My project Ebeep is starting to take a bit more shape! . my project is a “beeper” with an eink display (like the name suggests). ill be building two of them and gifting one to my GF on her birthday later this month! . i rewrote almost the ENTIRE UI since last time the code i wrote was pretty bad and it had terrible UI. hopefully tomorrow i could work on actually connecting it to the internet and work on basic end to end encryption (maybe?). also i really hope ill get my esp32s soon so i could actually test my code on that instead of my arduino and design my 3d case for it. . today and yesterday werent very productive since my CS finals are tomorrow! so wish me luck!
Devlog #3 . to those haven’t seen my project yet in short: . my project is a “beeper” with an eink display (like the name suggests). ill be building two of them and gifting one to my GF on her birthday later this month! it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up what did i do today? . today i added Wifi! since i still dont have my esp32 (damm you AliExpress and your slow shipping), i wont be able to use the cool web UI library i wanted to use… so i changed my phones hotspot to the most boring name & password i could think of and hard coded those credentials in (i dont know how to hide sensitive info from GitHub and didn’t want to add my real wifi lol) edit: i also added the little wifi ui thingy you see in the picture whats next? i will research more about the MQTT protocol my two devices will use to communicate add end to end encryption (both devices will have a hard coded secret “password” they will use to encrypt and decrypt the messages) if esp arrives soon (WHICH IT SHOULD) ill connect it to the bread board and change the code accordingly and much more just later on id love to hear what your thoughts in the comments :) update on me: today was my computer science finals and it was 5 hours. i was pretty burned out after that so didn’t do that much today either :/ the next couple days are packed with personal stuff and more final exams so u might not hear from me soon… ill try to work on this project at least an hour every day so if u do it will be small changes unfortunately
Devlog #4! . to those haven’t seen my project yet in short: my project is a “beeper” with an eink display ill be building two of them and gifting one to my GF on her birthday later this month! it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up what did i do? . i tired connecting my current setup to the MQTT broker and make it actually able to talk to other devices BUT IT DIDNT WORK i spent hours debugging it, only to come to the conclusion that i CANT do it with my current setup and i NEED the esp32 to continue coding or at least it will be much easier every day that passes i hate AliExpress even more it should have arrived 4 days ago ;-; the only useful i did is figure out how .gitignore work so now i dont need a hotspot lol whats next? wait for esp32 to arrive >:( update on me: . nothing rely new from yesterday . side note i just noticed ive never actually shown you how the UI i made previously works. so i attached a short walk through
Devlog #5! to those haven’t seen my project yet in short: my project is a “beeper” with an eink display ill be building two of them and gifting one to my GF on her birthday later this month! it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up what did i do? i was bored since i cant really work on the project and have to wait for my esp32 to arrive >:( so i went on a side quest and added the game select menu, nothing major i also need to design the icons since they are just place holders from google whats next? wait for esp32 to arrive >:( actually make blackjack and the other games ask my friend to 3d help me 3d model the case update on me: sorry for the long wait i had a bunch of shit 2 do and war with iran ;-;
Devlog #6 my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday later this month! what did i do? the esp32 arrived yesterday its much much smaller than i expected and i have no clue how im going to solder it later ;-; anyways so i worked on porting my current code from arduino to esp32, its seems to be working as intended. now i just need to add all the missing features like the mqtt protocol and wifi portal. whats next? add the wifi portal (so i wont have to hardcode the wifi credentials in the code) make the esp32 work with the mqtt protocol design a 3d printed case finish the games (not really a priority right now) update on me: more finals soon yay :/
Devlog #7 Its a big one what did i do? added a way to set the wifi password from your phone made the beeper actually able to talk and send messages fixed a lot of bugs that popped up after the switch to esp32 added a way to scroll faster for convince me and my friend started designing a case we will 3d print whats next? finish design a 3d printed case maybe finish one of the games side notes: i added a short video with a demo of everything working together would love to hear your thoughts about it background music: In the pool by kensuke ushio (forgor who made the piano cover im using) update on me: physics finals is in 3 days and I’m so cooked might not be able to design the case for a while
Devlog 8 (3 DAYS LEFT UNTILL GF BIRTHDAY) CAD IS DONE what did i do? finished the cad hopefully will start printing on sunday when my new 3d printer arrives (and hopefully wont have to change anything bc i have 3 DAYS LEFT ) I REWORKED THE ENTIRE MQTT CODE (made the beeper talk to each other differently in order to make games possible) almost done with the online tic tac toe (the more indepth devlog will be the next one) fixed like 4 bugs and another 2 popped up kill me whats next? finish EVERYTHING before my GF birthday on Tuesday (sorry for this short devlog dont have much to say about the cad model the one on the code will come tmr hopefully)
Devlog #9 (1 day until GF birthday) TL;DR: finished tic tac toe, added icons to show if the bepper lost internet connection and updated the 3d model my project in short my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday later this month! what did i do? online tic tac toe works now icons to show if the connection is lost and automatically reconnect updated 3d model to actually use M4 screws how do they talk to eachother? i made a comic to demonstrate it cuz ik yall aint reading all that but if u want to read it in more detail: the first player sends to the other a message “TTT_JOIN” in /games then start listening to /games/TTT (channel where all the game communication will happen) the second player will receive that message and will get a notification that someone is waiting to play tic tac toe then if he wants he will join the the game and send a msg on /games/TTT that he joined both screens will update and show the tic tac toe board. each player will take his turn and send a message in /games/TTT with a row and a column of the place he chose to play and the screen will update accordingly. when the game ends they could request a rematch and will start this whole process again
Devlog #10 i missed the deadline :( (failed print after failed print) my project in short my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday! Her birthday was yesterday, i missed the deadline and my motivation is at an all time low. The code is done (i hope) but the 3d case is so horrible. its way too big and wastes so much material on useless spots and way too little on places in places that need it. the whole thing needs a redesign and I’m working on that but unfortunately ill have to postpone it by at least two days since i have 1 more final exam i need to take. and i just feel awful that i have to give her the birthday present with a week+ delay TL;DR i missed the dead line and I’m really down, the case needs a major redesign and im yet to even start soldering the code probably is done
Devlog #11 we are 80% there! my project in short my project is a “beeper” with an eink display, it will feature three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up.ill be building two of them and gifting one to my GF on her birthday! what did i do? i finished the CAD (i hope), and started soldering everything together with the help of my dad(hes the best) the electronic plate is coming together nicly its not done yet but its mostly done!! and i will probably finish the first beeper TODAY!
Devlog #12 THE FIRST ONE IS DONE my project in short to those who havent seen it yet: My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! I soldered everything up, crammed it into the box, and it works now. hooray! The only issue I had was that the negative terminal on the bottom of the esp32 disconnected when I tried to fit it into the box. I’m now in the process of testing and ironing out bugs. So far i found two the battery readout is weird but it works, and the battery runs out way too quickly, so I’m trying to fix those issues. unfortunately, I don’t know when I’ll be able to finish the second one since the 3D printer broke down (I literally bought it last week ) It took me a while to finish this one since I had an FRC competition to attend and couldnt finish everything in 1 day.
Devlog #13 The project is completed (mostly) my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together.I’ll be building two of them and gifting one to my GF for her birthday! Just finished building my second ebeep device! The good news are it came out SO much better than the first one, It might not be super obvious from the photos but trust me the difference IRL is HUGE. The Type-C connection actually fits properly this time! and the two devices are communicating great, and I even managed to run multiple rounds of Tic-Tac-Toe. . As for the bad news, It seems like every other day I encounter a new issue usually related to Wi-Fi or server connectivity. hopefully my janky code i wrote so far successfully patched them out. I’m trying to squash as many as possible before I gift one to my girlfriend later this week. If I have time, I’ll try to finish up Connect 4 as well and i think ill give up on the poker game i dont want to delay it any longer lol. . Also, for those who were wondering, we landed in 30th place (out of 36?) at the FRC competition
Devlog #14 - The project is compleated! (if there arent ane new bugs) my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! what did i do? i added connect 4 & blackJack both of em should work now i fixed a problem with the wifi connection made new art for the connect 4 & blackjack to replace the place holders. i have already gifted the other device and shes probably reading this devlog so hello and sorry it took long all i have to do is finish up the docs and the github page and then were ready to ship
Devlog #15 Small changes my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together.I’ll be building two of them and gifting one to my GF for her birthday! i a couple of issues with blackjack: * can now display around 11 cards(more than that is extremly unlikely so i didnt bother) * dealer no longer draws cards if u bust * now the split looks much much cleaner now even if one device is disconnected the msg will be stored and displayed when the device connects to the wifi some other stuff i forgot
Devlog #16 documenting (and accidental PCB?) my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! so i finally sat down to start documenting my work, but while doing so… i might have gone a little over the top and started designing a custom PCB for the project ;-;it’s pretty fun ngl, i’m really enjoying working on it! ohh also, i fixed a MAJOR bug in my code. i have absolutely no clue how i didn’t notice it earlier, but when i was trying to fix bugs last week, i accidentally introduced a new one that deleted messages the exact second they arrived. so yeah… i didn’t get any messages from my girlfriend for a whole week lol. oops. and if anyone here knows how to make pcbs please help me i have no clue what im doing thanks!
Devlog #17 pcb is done and showcase animation my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I’ll be building two of them and gifting one to my GF for her birthday! i finished the pcb and refined it! yesterday ish i had like an idea to make an animation in blender to showcase the device for the final devlog so i started working on it nect devlog will be the final one! (i think)
Devlog #18 - The Final One my project in short to those who havent seen it yet My project is a “beeper” with an e-ink display. It features three low-profile mechanical switches, an ESP32, a battery, and a 3D-printed case to tie it all together. I built two of them and gifted one to my GF for her birthday! so this is it, the last devlog for Ebeep. i finished the Blender showcase animation, check it out ⬇️⬇️⬇️ took way longer than expected since I’ve never really used blender for anything like this before, but I’m happy with how it turned out. (or kicad) as for the PCB, the design is fully done, routed, and ready to export to gerbers, but I decided not to actually order it right now. the perfboard build already works and does the job, and the PCB was mostly a “because I can” side project once I started documenting everything (devlog #16 lol). might revisit it in the future if I ever want to build a v2 or make more of these, but for now the current build is what’s shipping as “done.” looking back this project went through basically everything a project can go through: missed deadlines, a broken 3d printer, a bug that silently deleted my girlfriend’s messages for a week without me noticing, failed prints, finals eating my motivation and somehow it still came out the other side working, on both devices, doing everything I wanted it to do. if I had to do it again I’d probably: start the PCB earlier instead of perfboard + rework set up proper MQTT retained-message handling from day one instead of patching it in later. budget way more time for the case than I did CAD alone ate multiple redesigns and i still needed help from my friend to finish it i really need to work on my CAD skills but honestly, for a project that started as “let’s port some code to an esp32 I’m scared to solder,” I’m really proud of where it landed. whats next? id really love to keep working and making it the best i can (the 3d render is really rough as i had to finish it TODAY and some of the code is still messy), but realistically, nothing planned this is the ‘finish’ line. maybe a better PCB with a good showcase with cleaner code and a case that actually houses the PCB someday, maybe not. either way, thanks to everyone who followed along since the start. TL;DR finished the showcase render, PCB design is complete but staying unbuilt for now, and the project is officially ‘done’. thanks for reading 🎉
Ships:
my project is a “beeper” with an eink display, it features three low profile mechanical switches, esp32, battery and a 3d printed case to tie it all up. ill be building two of them and gifting one to my GF on her birthday later this month!...
|
1793137907.8825028
|
1793224307.8825028
|
|
960
|
Biothesiometer by @aaditrai | Stardance
|
aaditrai
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Biothesiometer by @aaditrai | Stardance
|
1792655683.729059
|
1793260483.729059
|
|
961
|
SkyBlock Weapons by @lily | Stardance
|
lily
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SkyBlock Weapons by @lily | Stardance
|
1793209771.3713665
|
1793814571.3713665
|
|
962
|
My awesome macropad! by @PhoenixFire | Stardance
|
PhoenixFire
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @PhoenixFire | Star Title: My awesome macropad! by @PhoenixFire | Stardance...
|
1792673313.6861966
|
1793278113.6861966
|
|
964
|
My first slack bot! by @PhoenixFire | Stardance
|
PhoenixFire
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @PhoenixFire | Stard Title: My first slack bot! by @PhoenixFire | Stardance...
|
1793195607.4916434
|
1793800407.4916434
|
|
965
|
My first slack bot! by @kiri | Stardance
|
kiri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @kiri | Stardance
|
1792777776.00065
|
1793382576.00065
|
|
966
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792939656.4251943
|
1793803656.4251943
|
|
967
|
DartLedger by @kiri | Stardance
|
kiri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DartLedger by @kiri | Stardance
|
1793303262.6775887
|
1793908062.6775887
|
|
968
|
Yerba Linux by @ArslaanPathan | Stardance
|
ArslaanPathan
|
0
|
32.13
|
0
|
[]
|
[{"post_id": 66974, "ts": "202 [{"post_id": 66974, "ts": "2026-09-12T23:36:05Z", "hours": 2.4903, "text": "NETWORKING WORKS. LET’S GO YEAHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!!! I GOT IT TO FETCH A DNF REPO Oh and I also just happened to discover that DNF WONT WORK AS MY PM EITHER SO NOW IM SCRAMBLING TO FIND A WORKING ROOTLESS PACKAGE MANAGER BEFORE STARDANCE ENDS ON SEPTEMBER 30TH IVE ALREADY BURNT LIKE A WEEK ON THIS RAAAAAAAAAAAAAAAAAA"}, {"post_id": 63291, "ts": "2026-09-07T01:18:06Z", "hours": 3.5978, "text": "I spent AGES trying to get pkgsrc to work as the package manager. It does NOT build in Yocto. I TAKE BACK EVERYTHING GOOD I SAID ABOUT PKGSRC THE BUILD SYSTEM IS SO SHIT AND IT DOESNT WORK AND IT USES NON STANDARD BUILD AND AAAAHHHHHHHHHHHHHHHHHHHHHH REST IN PISS PKGSRC YOU WILL NOT BE MISSED I ended up using DNF/RPM (yes, the package manager from Fedora!) You will see in the screenshot below that DNF is failing to update repos, that’s because I kind of forgot to get networking working before trying the package manager (also using Fedora repo just for testing, will not be in final one)"}, {"post_id": 59879, "ts": "2026-09-01T21:18:01Z", "hours": 2.7003, "text": "Goodbye GNU, hello BSD! I spent some time modifying my Linux distro BitBake/Yocto recipes to migrate from GNU coreutils (and BusyBox) to FreeBSD coreutils, specifically chimerautils, the ported FreeBSD core utilities used in Chimera Linux. I did this to add some extra security (*BSD is normally more security-focused and scrutinized, afaik) and to align a bit more with UNIX philosophy ^_^"}, {"post_id": 57223, "ts": "2026-08-29T10:09:19Z", "hours": 0.4067, "text": "I spent a LOT of time debugging the build system. Last time I worked on this was 2 months ago, and that was before I switched to Void Linux (musl) from Gentoo. Logged time for this devlog is so low because it’s 99% debugging black magic logs and 1% of actually modifying the configs. Lessons learned: don’t trust the GNU mirrors. don’t trust BitBake to do its job, and don’t set a custom DL_DIR for BitBake because it will not use it properly and cause issues. also do not do Yocto development on musl libc. It turns out that Yocto compilation also just dies on musl so I’m now running the build in Docker (recurring theme with my projects, isn’t it?) I think I’ve almost got the build to start working again, just need to fix some locales in the Docker container and we should be good to go!"}, {"post_id": 56916, "ts": "2026-08-28T22:45:52Z", "hours": 0.7997, "text": "Switching the focus of this project Hey everyone! I know I’ve been gone for a while, I’ve been distracted by many other projects and ideas and also trying to work on the package manager for this distro. (got distracted with that too) I’m not sure what this logged time on this devlog is for, it might be for some few changes I didn’t devlog last time I worked on this project. I think I’m going to switch the focus of this distro from here, to not just be minimalist and a knockoff of Void, but to be a Void-like minimalist distro with secureblue/GrapheneOS-level security. It’s probably going to be hard to pull off but I think it will be worth it. Thanks all!"}, {"post_id": 12730, "ts": "2026-06-20T20:07:43Z", "hours": 0.5997, "text": "I DID IT IT WORKS I CAN LOGIN AS YERBA NOW WITH THE PASSWORD yerba !!!! it was PAM. it’s always PAM. I just needed to install PAM."}, {"post_id": 12294, "ts": "2026-06-20T02:01:10Z", "hours": 0.9867, "text": "I got it to run QEMU with a graphical window, AND I also made a logo!!! I followed the guide from https://anchor.hackclub.com to make this logo, thanks Anchor! I am still trying to figure out why login for yerba doesnt work"}, {"post_id": 11850, "ts": "2026-06-19T08:51:15Z", "hours": 4.0556, "text": "I’ve got privilege escalation to work along with networking (dhcpcd) and am working on getting audio to work! I’m trying to make a non-root user with a password, for some reason Yocto is yelling at me a lot (its been hours, helpppp) (p.s. I do not have a relevant screenshot at the moment, and it has been a long day, so here is a filler red gradient that I have for some reason)"}, {"post_id": 9804, "ts": "2026-06-16T07:29:06Z", "hours": 4.7003, "text": "Sorry I haven’t been devlogging for a while! I got way too focused on getting back to where I was before on the new Yocto build system! I have got Yocto to create a working rootfs and load the runit init system!"}, {"post_id": 6720, "ts": "2026-06-11T08:00:22Z", "hours": 0.4353, "text": "Yep, another clean slate it is. This time, it’s Yocto, and it’s here to stay (insha allah)."}, {"post_id": 6696, "ts": "2026-06-11T06:54:34Z", "hours": 1.7858, "text": "I HATE YOu NIX. AAAAAAAAAAAAAAaAAAAAAAAAAAAAAAAAAAAAAAA STOP LINKING AGAINST /NIX/STORE PATHS iknow nix is meant to be a package manager but WHAT OTHER OPTIONS DO I HAVEEEEE MAKEFILE IS SCUFFED, BUILDROOT IS MORE EMBEDDED, ETC atp im just gonna switch off of nix (yes, clean slate for the distro V2…. yay.. /s) (i mean i guess i wont be fighting with nix)"}, {"post_id": 6114, "ts": "2026-06-10T08:57:58Z", "hours": 0.2614, "text": "IT WORKS IT WORKS IT WORKS THE INIT SYSTEM DOES THE THING AND SHOWS GETTY RUNIT WORKS IT WORKS!!!!!!!!!!!! Edit: The solution was to launch /usr/bin/runit directly instead of using /usr/bin/runit-init. This is not necessarily correct, but /usr/bin/runit-init is currently broken due to Nixpkgs assuming this is a Nix-based distro when it is not. Insha allah later during the development cycle, I will replace the Nixpkgs flake with my own flake that accounts for this. For now, too bad, the distro boots"}, {"post_id": 6108, "ts": "2026-06-10T08:40:27Z", "hours": 1.5533, "text": "I’ve got musl to load into the initramfs, and am working on adding runit as the init system I am very confused as to why runit fails to switch_root, the error is very cryptic EAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"}, {"post_id": 5436, "ts": "2026-06-09T06:30:38Z", "hours": 0.7472, "text": "I GOT THE THING TO WORK!! THE GRAPHICAL TTY!! are you serious rn, it was a single kernel config opt. i spent very very long debugging this. a lot longer than i anticipated. BUT STILL IT WORKED YAYAYAYAYAYAYAYAYAYAY"}, {"post_id": 4766, "ts": "2026-06-08T07:26:58Z", "hours": 1.5283, "text": "IT BOOTS!!! IT FREAKING BOOTS!!!!! THE BUSYBOX BUILD WORKS!! THE ROOTFS BUILDS!! IT LOADS THE SQUASHFS WITH OVERLAYFS!!!! YAYAYAYAYAYAYAYAY"}, {"post_id": 3995, "ts": "2026-06-07T04:15:08Z", "hours": 0.9253, "text": "Made a lot of refactors, and added placeholder targets Also got the kernel build to work!!"}, {"post_id": 3931, "ts": "2026-06-07T01:48:43Z", "hours": 1.7028, "text": "Made a clean slate and switched my distro’s build system to Nix for reproducibility and to get away from my Makefile that used scuffed hacks This doesn’t mean my distro will use Nix or be like NixOS, but it will help improve development speed and quality Finally got it to nix build an initramfs without errors!"}, {"post_id": 714, "ts": "2026-06-02T09:30:38Z", "hours": 1.2764, "text": "Finally got it to create a live ISO and boot with Limine!!!!"}, {"post_id": 681, "ts": "2026-06-02T07:32:05Z", "hours": 0.8617, "text": "Did a bit of debugging and testing, and got the initramfs to boot. TODO: Make it create a squashfs root"}, {"post_id": 232, "ts": "2026-06-01T11:00:28Z", "hours": 0.7181, "text": "Got a basic build system working for my in-progress distro, Yerba Linux Builds the Linux kernel, BusyBox, and creates a minimal BusyBox initramfs that drops you to a shell TODO: Make it create an ISO with GRUB/any bootloader"}]...
|
Title: Yerba Linux by @ArslaanPathan | Stardance
Title: Yerba Linux by @ArslaanPathan | Stardance
Devlogs:
Got a basic build system working for my in-progress distro, Yerba Linux Builds the Linux kernel, BusyBox, and creates a minimal BusyBox initramfs that drops you to a shell TODO: Make it create an ISO with GRUB/any bootloader
Did a bit of debugging and testing, and got the initramfs to boot. TODO: Make it create a squashfs root
Finally got it to create a live ISO and boot with Limine!!!!
Made a clean slate and switched my distro’s build system to Nix for reproducibility and to get away from my Makefile that used scuffed hacks This doesn’t mean my distro will use Nix or be like NixOS, but it will help improve development speed and quality Finally got it to nix build an initramfs without errors!
Made a lot of refactors, and added placeholder targets Also got the kernel build to work!!
IT BOOTS!!! IT FREAKING BOOTS!!!!! THE BUSYBOX BUILD WORKS!! THE ROOTFS BUILDS!! IT LOADS THE SQUASHFS WITH OVERLAYFS!!!! YAYAYAYAYAYAYAYAY
I GOT THE THING TO WORK!! THE GRAPHICAL TTY!! are you serious rn, it was a single kernel config opt. i spent very very long debugging this. a lot longer than i anticipated. BUT STILL IT WORKED YAYAYAYAYAYAYAYAYAYAY
I’ve got musl to load into the initramfs, and am working on adding runit as the init system I am very confused as to why runit fails to switch_root, the error is very cryptic EAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
IT WORKS IT WORKS IT WORKS THE INIT SYSTEM DOES THE THING AND SHOWS GETTY RUNIT WORKS IT WORKS!!!!!!!!!!!! Edit: The solution was to launch /usr/bin/runit directly instead of using /usr/bin/runit-init. This is not necessarily correct, but /usr/bin/runit-init is currently broken due to Nixpkgs assuming this is a Nix-based distro when it is not. Insha allah later during the development cycle, I will replace the Nixpkgs flake with my own flake that accounts for this. For now, too bad, the distro boots
I HATE YOu NIX. AAAAAAAAAAAAAAaAAAAAAAAAAAAAAAAAAAAAAAA STOP LINKING AGAINST /NIX/STORE PATHS iknow nix is meant to be a package manager but WHAT OTHER OPTIONS DO I HAVEEEEE MAKEFILE IS SCUFFED, BUILDROOT IS MORE EMBEDDED, ETC atp im just gonna switch off of nix (yes, clean slate for the distro V2…. yay.. /s) (i mean i guess i wont be fighting with nix)
Yep, another clean slate it is. This time, it’s Yocto, and it’s here to stay (insha allah).
Sorry I haven’t been devlogging for a while! I got way too focused on getting back to where I was before on the new Yocto build system! I have got Yocto to create a working rootfs and load the runit init system!
I’ve got privilege escalation to work along with networking (dhcpcd) and am working on getting audio to work! I’m trying to make a non-root user with a password, for some reason Yocto is yelling at me a lot (its been hours, helpppp) (p.s. I do not have a relevant screenshot at the moment, and it has been a long day, so here is a filler red gradient that I have for some reason)
I got it to run QEMU with a graphical window, AND I also made a logo!!! I followed the guide from https://anchor.hackclub.com to make this logo, thanks Anchor! I am still trying to figure out why login for yerba doesnt work
I DID IT IT WORKS I CAN LOGIN AS YERBA NOW WITH THE PASSWORD yerba !!!! it was PAM. it’s always PAM. I just needed to install PAM.
Switching the focus of this project Hey everyone! I know I’ve been gone for a while, I’ve been distracted by many other projects and ideas and also trying to work on the package manager for this distro. (got distracted with that too) I’m not sure what this logged time on this devlog is for, it might be for some few changes I didn’t devlog last time I worked on this project. I think I’m going to switch the focus of this distro from here, to not just be minimalist and a knockoff of Void, but to be a Void-like minimalist distro with secureblue/GrapheneOS-level security. It’s probably going to be hard to pull off but I think it will be worth it. Thanks all!
I spent a LOT of time debugging the build system. Last time I worked on this was 2 months ago, and that was before I switched to Void Linux (musl) from Gentoo. Logged time for this devlog is so low because it’s 99% debugging black magic logs and 1% of actually modifying the configs. Lessons learned: don’t trust the GNU mirrors. don’t trust BitBake to do its job, and don’t set a custom DL_DIR for BitBake because it will not use it properly and cause issues. also do not do Yocto development on musl libc. It turns out that Yocto compilation also just dies on musl so I’m now running the build in Docker (recurring theme with my projects, isn’t it?) I think I’ve almost got the build to start working again, just need to fix some locales in the Docker container and we should be good to go!
Goodbye GNU, hello BSD! I spent some time modifying my Linux distro BitBake/Yocto recipes to migrate from GNU coreutils (and BusyBox) to FreeBSD coreutils, specifically chimerautils, the ported FreeBSD core utilities used in Chimera Linux. I did this to add some extra security (*BSD is normally more security-focused and scrutinized, afaik) and to align a bit more with UNIX philosophy ^_^
I spent AGES trying to get pkgsrc to work as the package manager. It does NOT build in Yocto. I TAKE BACK EVERYTHING GOOD I SAID ABOUT PKGSRC THE BUILD SYSTEM IS SO SHIT AND IT DOESNT WORK AND IT USES NON STANDARD BUILD AND AAAAHHHHHHHHHHHHHHHHHHHHHH REST IN PISS PKGSRC YOU WILL NOT BE MISSED I ended up using DNF/RPM (yes, the package manager from Fedora!) You will see in the screenshot below that DNF is failing to update repos, that’s because I kind of forgot to get networking working before trying the package manager (also using Fedora repo just for testing, will not be in final one)
NETWORKING WORKS. LET’S GO YEAHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!!! I GOT IT TO FETCH A DNF REPO Oh and I also just happened to discover that DNF WONT WORK AS MY PM EITHER SO NOW IM SCRAMBLING TO FIND A WORKING ROOTLESS PACKAGE MANAGER BEFORE STARDANCE ENDS ON SEPTEMBER 30TH IVE ALREADY BURNT LIKE A WEEK ON THIS RAAAAAAAAAAAAAAAAAA...
|
1792677065.8179553
|
1793281865.8179553
|
|
969
|
Kerr Simulator by @krazyminer001 | Stardance
|
krazyminer001
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Kerr Simulator by @krazyminer001 | Stardanc Title: Kerr Simulator by @krazyminer001 | Stardance...
|
1793174104.5397794
|
1793778904.5397794
|
|
970
|
My awesome macropad! by @rx76d | Stardance
|
rx76d
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @rx76d | Stardance
|
1792914764.9621553
|
1793778764.9621553
|
|
971
|
PFP MAKER by @siddharthan | Stardance
|
siddharthan
|
0
|
9.12
|
0
|
[]
|
[{"post_id": 4168, "ts": "2026 [{"post_id": 4168, "ts": "2026-06-07T11:51:56Z", "hours": 9.1181, "text": "Heya! Guys, take a look at the pfp maker that I made for beest!"}]...
|
Title: PFP MAKER by @siddharthan | Stardance
Devl Title: PFP MAKER by @siddharthan | Stardance
Devlogs:
Heya! Guys, take a look at the pfp maker that I made for beest!...
|
1792738277.1819127
|
1793343077.1819127
|
|
972
|
M’groq by @Trick | Stardance
|
Trick
|
0
|
3.39
|
0
|
[]
|
[{"post_id": 1673, "ts": "2026 [{"post_id": 1673, "ts": "2026-06-03T20:20:34Z", "hours": 0.6069, "text": "i’ve fixed the calculator thingy and by doing so it’s not going to meet any similar problems in the futre i think i’ll release a demo soon (probably going to do a long session after this to improve everything)"}, {"post_id": 1048, "ts": "2026-06-02T21:03:50Z", "hours": 1.4656, "text": "i’ve implemnted file creation, app opening AND website opening, nearly went mad but did it (groq has a passion for calculator tools and refuses to open the normal calculator if i don’t find a solution i’ll ban calculator tools)"}, {"post_id": 747, "ts": "2026-06-02T11:41:28Z", "hours": 1.3153, "text": "i managed to get him working and talking in a pretty natural way and integrated voice, next step is to make sure he can create files on desktop, he’s pretty good at learning so far with all the chats we’ve done. also he creates a file at the tasrt of a chat and stores all chats there so that he remembers (this one is a demo so i started with a new chat)"}]...
|
Title: M’groq by @Trick | Stardance
Devlogs:
i ma Title: M’groq by @Trick | Stardance
Devlogs:
i managed to get him working and talking in a pretty natural way and integrated voice, next step is to make sure he can create files on desktop, he’s pretty good at learning so far with all the chats we’ve done. also he creates a file at the tasrt of a chat and stores all chats there so that he remembers (this one is a demo so i started with a new chat)
i’ve implemnted file creation, app opening AND website opening, nearly went mad but did it (groq has a passion for calculator tools and refuses to open the normal calculator if i don’t find a solution i’ll ban calculator tools)
i’ve fixed the calculator thingy and by doing so it’s not going to meet any similar problems in the futre i think i’ll release a demo soon (probably going to do a long session after this to improve everything)...
|
1793134224.121407
|
1793739024.121407
|
|
973
|
My first slack bot! by @obob | Stardance
|
obob
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @obob | Stardance
|
1793188270.5481167
|
1793793070.5481167
|
|
974
|
My first slack bot! by @Dhyan | Stardance
|
Dhyan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Dhyan | Stardance
|
1792734459.0071332
|
1793339259.0071332
|
|
975
|
JevTalk by @ciaran | Stardance
|
ciaran
|
0
|
5.19
|
0
|
[]
|
[{"post_id": 79672, "ts": "202 [{"post_id": 79672, "ts": "2026-10-15T01:01:48Z", "hours": 0.8447, "text": "The web interface is now in full working order, so now it’s time to make it look pretty."}, {"post_id": 79663, "ts": "2026-10-14T23:56:22Z", "hours": 0.9208, "text": "OHHHH, that’s why it was talking to itself."}, {"post_id": 78003, "ts": "2026-10-09T04:36:29Z", "hours": 3.4222, "text": "I’ve got the main groundwork done. At first i tried just having a model consult Jev but it was really just the model talking, so i had jev select each word from a pool given by 6 luna. After that, sometimes Jev’d start responding as the user, but its mostly fixed. Plus, its so earnest that its kinda just cute. Just needs a web UI."}]...
|
Title: JevTalk by @ciaran | Stardance
Devlogs:
I’ Title: JevTalk by @ciaran | Stardance
Devlogs:
I’ve got the main groundwork done. At first i tried just having a model consult Jev but it was really just the model talking, so i had jev select each word from a pool given by 6 luna. After that, sometimes Jev’d start responding as the user, but its mostly fixed. Plus, its so earnest that its kinda just cute. Just needs a web UI.
OHHHH, that’s why it was talking to itself.
The web interface is now in full working order, so now it’s time to make it look pretty....
|
1792716632.18975
|
1793321432.18975
|
|
976
|
CCPLOS by @QKing | Stardance
|
QKing
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CCPLOS by @QKing | Stardance
|
1793163301.3479702
|
1793768101.3479702
|
|
977
|
Untitled project by @itzstt | Stardance
|
itzstt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @itzstt | Stardance
|
1792615922.0617266
|
1793220722.0617266
|
|
978
|
Untitled project by @aiden | Stardance
|
aiden
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @aiden | Stardance
|
1792648345.5215175
|
1793253145.5215175
|