|
18201
|
My awesome macropad! by @Harikesh | Stardance
|
Harikesh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Harikesh | Stardan Title: My awesome macropad! by @Harikesh | Stardance...
|
1793573424.9549236
|
1794178224.9549236
|
|
18202
|
Player_AI_Datapack by @Aschelin9 | Stardance
|
Aschelin9
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Player_AI_Datapack by @Aschelin9 | Stardanc Title: Player_AI_Datapack by @Aschelin9 | Stardance...
|
1793908293.4296458
|
1794513093.4296458
|
|
18203
|
XDQ-001 by @Cipher012 | Stardance
|
Cipher012
|
0
|
15.68
|
0
|
[]
|
[{"post_id": 45969, "ts": "202 [{"post_id": 45969, "ts": "2026-08-12T19:57:05Z", "hours": 2.0447, "text": "Devlog #7 Subject: Upgrading the Sensor Suite & Advanced Vario Estimation Date: 8/12 After starting to making the BOM and other details for the drone i diced to making an update of the hardware I updated the PCB IMU to an industrial-grade Bosch BMI088 (with GYRO CS on PA4 and ACC CS on PA4) and swapped the barometer for an SPL06-001 (BARO CS on PA0, MAG CS on PA3). This hardware revision allowed us to introduce major firmware variations: Firmware V003 ( XDQ-001F_V003.ino ) : Direct hardware support and pinout re-routing for the new BMI088 (dual-die SPI mode 0/3) and SPL06-001 barometer drivers. Firmware V004 ( XDQ-001F_V004.ino ) : Advanced sensor fusion algorithms including a 3rd-order Complementary Altitude & Vario Estimator (fusing SPL06 baro and BMI088 AccelZ at 1kHz for lag-free vertical speed estimation) and a PT2 (2nd-order) Low-Pass Notch Filter on the BMI088 gyro to suppress motor vibration noise before the PID loop. š XDQ-001 Devlog: Sensor Suite Overhaul & Vario Fusion Here is a quick update on the latest hardware and firmware milestones for the XDQ-001 flight platform. 1. PCB Hardware Upgrade (August 12th) We upgraded the onboard sensor suite to industrial-grade components. The FCB now houses a Bosch BMI088 IMU (separate gyro/accel dies for superior vibration resistance) and a Goertek SPL06-001 high-resolution barometer. The SPI CS routing was updated accordingly (GYRO CS & ACC CS on PA4, MAG CS on PA3, BARO CS on PA0). 2. Driver Integration & V003 Firmware (August 12th) With new hardware comes updated firmware. We wrote dedicated drivers for the BMI088 (handling its dual SPI Mode 0 / Mode 3 requirements and Ā±24G / Ā±2000 dps scaling) and the SPL06-001 (decoding its 18-byte calibration array). All of this was packed into XDQ-001F_V003.ino , keeping V002 safe as a backup. 3. 3rd-Order Vario & Altitude Fusion (August 12th) Why get better hardware if you arenāt going to push it? In XDQ-001F_V004.ino , we built a 3rd-order Complementary Altitude/Vario Estimator that runs inside the 1kHz ISR. It fuses earth-frame Z acceleration with barometric pressure to calculate instantaneous vertical velocity ( climbRate_mps ). Altitude lock during autonomous waypoint missions is now smoother than ever without any altitude lag. 4. PT2 Gyro Filtering & Tuning (August 12th) To clean up motor noise before it hits the PID controllers and the SO(3) geometric attitude loop, we added a 2nd-order Low-Pass Filter (PT2) with a 90Hz cutoff directly on the BMI088 gyro channels. We also re-tuned Mahonyās Adaptive Accel Gating to leverage the Ā±24G dynamic range during aggressive maneuvers."}, {"post_id": 39193, "ts": "2026-08-02T00:00:21Z", "hours": 7.35, "text": "š XDQ-001 Devlog: The Last Month I know I disappeared for a month. Here is a quick, easy-to-read update on what Iāve recently been developing for the XDQ-001 drone. I have focused on simulating, visualizing, and refining the control and navigation algorithms to ensure smooth flight and navigation, as well as robustness under extreme conditions. 1. Teaching the Drone to Balance (July 19th) We kicked things off by focusing on the droneās āattitudeāābasically, how it balances and tilts in the air. We built the core logic (PID controllers) so the drone can stay stable even if we send it aggressive commands. To make sure everything was working right, we also set up some visual tools to watch the simulation data in real time. 2. Navigating and Visualizing the Path (July 26th) Next up: Navigation! We connected our new balancing act with algorithms that tell the drone where to go. To actually see what the droneās ābrainā was planning, we built some cool Python scripts that render 3D flight paths. We also made some nice flowcharts (using Mermaid) to keep our ideas organized. 3. Automated Virtual Flights (July 26th) Nobody wants to test untested code on a real, expensive drone. So, we built a pipeline that automatically runs the drone through different virtual missions: Route (following waypoints) , Orbit (flying in circles) , and RTL (Return to Launch) . We also added tools that check how accurate the droneās internal GPS and sensors are during these flights. Now, it can test itself before we ever take it outside! 4. Making the Drone Tougher (August 1st) The real world is messyāthereās wind, vibrations, and sensor noise. To deal with this, we added something called Accel Gating . Basically, if the drone gets hit by a sudden gust of wind or a sensor throws a crazy number, the drone is now smart enough to say, āThat data looks wrong, Iām ignoring it.ā We ran dozens of automated stress tests (adding fake wind and latency) to prove it works. 5. Ready for the Real World (August 1st) Finally, we moved all this tested, simulated code over to the actual drone firmware ( XDQ-001F_V002.ino ). Everything compiled perfectly and is officially loaded onto the real hardware."}, {"post_id": 20239, "ts": "2026-07-01T19:47:08Z", "hours": 1.5264, "text": "Devlog #5 Subject: Finishing the PCB Date: 7/1 I finally finished re-routing the PCB; it was one of my most challenging tasks, as I had to manage various signal lines (SPI, UART, USB) while prioritizing noise control and isolation to prevent interference with the traces. The board is essentially a flight controller (FCB) featuring an IMU, magnetometer, barometer, MCU, and flash memory, along with external connectors for the ESC, radio, GPS, etc. It measures 45x50mmācompact compared to commercial double-sided flight controllersāand is a 4-layer board."}, {"post_id": 19580, "ts": "2026-06-30T22:32:42Z", "hours": 1.1353, "text": "Devlog #4 Subject: Rerouting the PCB Date: 6/30 Today, I wanted to redo the PCB routing and component placement to reduce noise and the amount of copper and vias used. I am trying to simplify the PCB placement and routing, aiming to use the fewest possible vias and clean connections."}, {"post_id": 17740, "ts": "2026-06-28T17:38:52Z", "hours": 0.7967, "text": "Devlog #3 Subject: Start to making the firmware and nav algorithms Date: 6/28 I have started developing the droneās firmwareāincluding PID control and navigation algorithmsāby basing it on and modifying the firmware from my previous fixed-wing project to adapt it for a rotary-wing drone. I also incorporated new filters and algorithms to leverage the STM32F4ās capabilities and optimize flash memory management."}, {"post_id": 14032, "ts": "2026-06-23T00:29:37Z", "hours": 0.7833, "text": "Devlog #2 Subject: Finishing CAD & Adding Fasteners Date: 6/22/2026 I was finalizing the CAD modeling; in this case, the only things I hadnāt done were drilling the holes for the countersunk screws, threading, rounding the chassis, and conducting motion studies to see how the drone behaves."}, {"post_id": 10326, "ts": "2026-06-17T00:07:17Z", "hours": 2.0408, "text": "Devlog #1 Date: 6/16/2026 Subject: Making CAD Design I decided to discard the original design I had created due to a reorganization of the FCB Iām going to use. I redid the unfinished models, like the frame, and adjusted the size to minimize this. However, space management is a problem; accommodating the ESC, FCB, external GPS, and radio can become a hassle if I donāt carefully plan the placement of each component. Iām starting to brainstorm ideas for my own navigation and management algorithm, primarily as an alternative to Betaflight and other similar software."}]...
|
Title: XDQ-001 by @Cipher012 | Stardance
Devlogs: Title: XDQ-001 by @Cipher012 | Stardance
Devlogs:
Devlog #1 Date: 6/16/2026 Subject: Making CAD Design I decided to discard the original design I had created due to a reorganization of the FCB Iām going to use. I redid the unfinished models, like the frame, and adjusted the size to minimize this. However, space management is a problem; accommodating the ESC, FCB, external GPS, and radio can become a hassle if I donāt carefully plan the placement of each component. Iām starting to brainstorm ideas for my own navigation and management algorithm, primarily as an alternative to Betaflight and other similar software.
Devlog #2 Subject: Finishing CAD & Adding Fasteners Date: 6/22/2026 I was finalizing the CAD modeling; in this case, the only things I hadnāt done were drilling the holes for the countersunk screws, threading, rounding the chassis, and conducting motion studies to see how the drone behaves.
Devlog #3 Subject: Start to making the firmware and nav algorithms Date: 6/28 I have started developing the droneās firmwareāincluding PID control and navigation algorithmsāby basing it on and modifying the firmware from my previous fixed-wing project to adapt it for a rotary-wing drone. I also incorporated new filters and algorithms to leverage the STM32F4ās capabilities and optimize flash memory management.
Devlog #4 Subject: Rerouting the PCB Date: 6/30 Today, I wanted to redo the PCB routing and component placement to reduce noise and the amount of copper and vias used. I am trying to simplify the PCB placement and routing, aiming to use the fewest possible vias and clean connections.
Devlog #5 Subject: Finishing the PCB Date: 7/1 I finally finished re-routing the PCB; it was one of my most challenging tasks, as I had to manage various signal lines (SPI, UART, USB) while prioritizing noise control and isolation to prevent interference with the traces. The board is essentially a flight controller (FCB) featuring an IMU, magnetometer, barometer, MCU, and flash memory, along with external connectors for the ESC, radio, GPS, etc. It measures 45x50mmācompact compared to commercial double-sided flight controllersāand is a 4-layer board.
š XDQ-001 Devlog: The Last Month I know I disappeared for a month. Here is a quick, easy-to-read update on what Iāve recently been developing for the XDQ-001 drone. I have focused on simulating, visualizing, and refining the control and navigation algorithms to ensure smooth flight and navigation, as well as robustness under extreme conditions. 1. Teaching the Drone to Balance (July 19th) We kicked things off by focusing on the droneās āattitudeāābasically, how it balances and tilts in the air. We built the core logic (PID controllers) so the drone can stay stable even if we send it aggressive commands. To make sure everything was working right, we also set up some visual tools to watch the simulation data in real time. 2. Navigating and Visualizing the Path (July 26th) Next up: Navigation! We connected our new balancing act with algorithms that tell the drone where to go. To actually see what the droneās ābrainā was planning, we built some cool Python scripts that render 3D flight paths. We also made some nice flowcharts (using Mermaid) to keep our ideas organized. 3. Automated Virtual Flights (July 26th) Nobody wants to test untested code on a real, expensive drone. So, we built a pipeline that automatically runs the drone through different virtual missions: Route (following waypoints) , Orbit (flying in circles) , and RTL (Return to Launch) . We also added tools that check how accurate the droneās internal GPS and sensors are during these flights. Now, it can test itself before we ever take it outside! 4. Making the Drone Tougher (August 1st) The real world is messyāthereās wind, vibrations, and sensor noise. To deal with this, we added something called Accel Gating . Basically, if the drone gets hit by a sudden gust of wind or a sensor throws a crazy number, the drone is now smart enough to say, āThat data looks wrong, Iām ignoring it.ā We ran dozens of automated stress tests (adding fake wind and latency) to prove it works. 5. Ready for the Real World (August 1st) Finally, we moved all this tested, simulated code over to the actual drone firmware ( XDQ-001F_V002.ino ). Everything compiled perfectly and is officially loaded onto the real hardware.
Devlog #7 Subject: Upgrading the Sensor Suite & Advanced Vario Estimation Date: 8/12 After starting to making the BOM and other details for the drone i diced to making an update of the hardware I updated the PCB IMU to an industrial-grade Bosch BMI088 (with GYRO CS on PA4 and ACC CS on PA4) and swapped the barometer for an SPL06-001 (BARO CS on PA0, MAG CS on PA3). This hardware revision allowed us to introduce major firmware variations: Firmware V003 ( XDQ-001F_V003.ino ) : Direct hardware support and pinout re-routing for the new BMI088 (dual-die SPI mode 0/3) and SPL06-001 barometer drivers. Firmware V004 ( XDQ-001F_V004.ino ) : Advanced sensor fusion algorithms including a 3rd-order Complementary Altitude & Vario Estimator (fusing SPL06 baro and BMI088 AccelZ at 1kHz for lag-free vertical speed estimation) and a PT2 (2nd-order) Low-Pass Notch Filter on the BMI088 gyro to suppress motor vibration noise before the PID loop. š XDQ-001 Devlog: Sensor Suite Overhaul & Vario Fusion Here is a quick update on the latest hardware and firmware milestones for the XDQ-001 flight platform. 1. PCB Hardware Upgrade (August 12th) We upgraded the onboard sensor suite to industrial-grade components. The FCB now houses a Bosch BMI088 IMU (separate gyro/accel dies for superior vibration resistance) and a Goertek SPL06-001 high-resolution barometer. The SPI CS routing was updated accordingly (GYRO CS & ACC CS on PA4, MAG CS on PA3, BARO CS on PA0). 2. Driver Integration & V003 Firmware (August 12th) With new hardware comes updated firmware. We wrote dedicated drivers for the BMI088 (handling its dual SPI Mode 0 / Mode 3 requirements and Ā±24G / Ā±2000 dps scaling) and the SPL06-001 (decoding its 18-byte calibration array). All of this was packed into XDQ-001F_V003.ino , keeping V002 safe as a backup. 3. 3rd-Order Vario & Altitude Fusion (August 12th) Why get better hardware if you arenāt going to push it? In XDQ-001F_V004.ino , we built a 3rd-order Complementary Altitude/Vario Estimator that runs inside the 1kHz ISR. It fuses earth-frame Z acceleration with barometric pressure to calculate instantaneous vertical velocity ( climbRate_mps ). Altitude lock during autonomous waypoint missions is now smoother than ever without any altitude lag. 4. PT2 Gyro Filtering & Tuning (August 12th) To clean up motor noise before it hits the PID controllers and the SO(3) geometric attitude loop, we added a 2nd-order Low-Pass Filter (PT2) with a 90Hz cutoff directly on the BMI088 gyro channels. We also re-tuned Mahonyās Adaptive Accel Gating to leverage the Ā±24G dynamic range during aggressive maneuvers....
|
1793458384.3967953
|
1794063184.3967953
|
|
18204
|
My first slack bot! by @TalibN_myNameNoTerrorist | My first slack bot! by @TalibN_myNameNoTerrorist | Stardance...
|
TalibN_myNameNoTerrorist
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @TalibN_myNameNoTerr Title: My first slack bot! by @TalibN_myNameNoTerrorist | Stardance...
|
1793422234.8924854
|
1794027034.8924854
|
|
18205
|
My very own WebOS by @tanush_kulkarni_47 | Stardan My very own WebOS by @tanush_kulkarni_47 | Stardance...
|
tanush_kulkarni_47
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @tanush_kulkarni_47 | Title: My very own WebOS by @tanush_kulkarni_47 | Stardance...
|
1793364962.1693995
|
1793969762.1693995
|
|
18206
|
Lume Tufte by @ethmarks | Stardance
|
ethmarks
|
1
|
15.0
|
246
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-30T01:30:57Z", "hours": 15.0, "multiplier": 16.18, "payout": 246, "blessing": "neutral", "text": "This is a theme for the Lume static site generator based on Tufte CSS . To try the Tufte theme, visit the demo page: https://ethmarks.github.io/lume_tufte/ . I submitted this PR to the official Lume theme registry to add the Tufte theme, which was accepted. It has its own page on the official Lume site: https://lume.land/theme/tufte/ I used several optimization tricks, such as statically analyzing the content of each page at build time to infer which font files to preload, to maximize performance, accessibility, best practices, and SEO. Because of this, the theme earns perfect 100s on Google Lighthouse , which the official Lighthouse documentation describes as āextremely challenging to achieve and not expectedā . I wrote 5000+ words of documentation across the README and demo articles. I wrote Lume CMS config for every aspect of the theme to allow for no-code content management.", "repo": "https://github.com/ethmarks/lume_tufte", "demo": "https://ethmarks.github.io/lume_tufte/"}]...
|
[{"post_id": 10827, "ts": "202 [{"post_id": 10827, "ts": "2026-06-17T19:27:41Z", "hours": 3.2611, "text": "1.0.0 Unless I think of more stuff to add, this is probably my last devlog before shipping. Lume Theme Registry A few hours ago, the PR that I created last devlog was merged into the official Lume theme registry, so you can now install my theme with a single command using Lume init, and it now has its own dedicated page on the official Lume website: https://lume.land/theme/tufte/ . README I added a How it Works section that explains how the Lume theme architecture works behind-the-scenes (spoiler: itās just remote files) and explains what each of the 18 included plugins do. I updated the quickstart to use the Lume init command. I added a Showcase section that lists the sites that use this theme. It seemed kind of weird to exclusively list the Tufte theme site itself, so I also switched one of my documentation sites to use the Tufte theme. I added a shields.io badge to the top of the README that links to the themeās page on the Lume website. shields.io relies on simple-icons for its logos, but simple-icons doesnāt have the Lume logo for some reason, so had to Base64-encode an SVG of the Lume logo in order to get the badge to work. Next steps Iām not going to ship this project juuuuust yet in case I think of any missing features that I ought to add, but I probably will soon."}, {"post_id": 10144, "ts": "2026-06-16T19:07:43Z", "hours": 0.5644, "text": "Theme Registry PR I just created a PR to add my theme to the official theme registry for Lume: https://github.com/lumeland/themes/pull/10 . Why If my theme isnāt in the official registry, the best way for users install it is to clone my entire repo, which is silly, bad for separation of concerns, and just generally worse for UX. git clone https://github.com/ethmarks/lume_tufte.git cd lume_tufte deno task serve But if I get my theme into the theme registry, users can install it using the official Lume init command, which is much better in every way: deno run -A https://lume.land/init.ts --theme = tufte Conclusion From my interactions with him in the past, the Lume maintainer (Oscar) seems like an extremely nice dude who seems to respond fairly quickly, so I shouldnāt have to wait too long before he either accepts my PR or suggests changes that I can go implement. Meanwhile, Iāll probably continue working on the README."}, {"post_id": 9742, "ts": "2026-06-16T05:10:31Z", "hours": 6.5114, "text": "README, optimizations, and more Since my last devlog: I wrote the README. I optimized the theme until it earned perfect 100s in every category on Lighthouse on every page. I added a light mode. I added support for tables of contents. I added RSS feed generation. I rewrote one of the demo blog posts. I added styles for HTML tables Link to the diff between last devlog and this one Optimization Most of the work I did today is pretty self-explanatory from my little summary, but the optimization work probably merits elaboration. So while I was writing the README, I had the idea to include the Lighthouse scores. When I checked, they were 100/100/100/92 on mobile and 92/100/100/92 on desktop. ā100s on Lighthouse in some fieldsā doesnāt sound nearly as nice as ā100s on Lighthouse in every fieldā, so I decided to start optimizing. Lighthouse told me that the SEO problem was a lack of descriptions, and the desktop performance problem was excessive network requests and chained network requests. SEO problem I fixed the lack of descriptions by adding descriptions. Simple as that. I wrote descriptions for all of the existing pages, added a description field to the CMS config, and added a mention of it in the usage guide. The network requests and chained requests were a bit trickier to solve. Performance problems The cause of the excessive network requests was that, even though the homepage didnāt use the KaTeX or Nueglow styles, they were still being imported. I solved that with a per-page check that runs at build time. Each page only imports the Nueglow stylesheet if it contains code blocks, and it only imports the KaTeX stylesheet if the page contains math blocks. Hereās a link to the relevant section of code . I think that itās a pretty clever solution because it selectively removes the unnecessary CSS requests without using client-side JS or anything like that. I used a similar approach to solve the chained requests. What was happening is that in order to download the woff2 files, the browser first had to download the CSS files, so it took twice as long because they couldnāt be downloaded in parallel. Font preloads are the way to solve this. The only problem is that if I preload too many font files, the browser will have download font files even if they arenāt used on the page. But if I preload too few, then the network requests are still chained. My solution was to have it check which font files each page needs and selectively preload only those font files. Hereās the relevant code if you want to see my implementation. Again, this solves the problem of unnecessary requests and chained requests without adding any client-side JS. Iām glad that Lume and Vento are such powerful tools that I can easily do programmatic optimizations like this. Next Steps I think that the next thing I should do is submit my theme to the official Lume theme repo. That way I can simplify the installation process down to one command."}, {"post_id": 8924, "ts": "2026-06-14T20:55:26Z", "hours": 5.1553, "text": "Hi there! This is a project Iāve been working on for the past week. Itās a theme for Lume SSG based on Tufte CSS. Btw, I did the majority of the work before I started using Hackatime, so Iāve been working on it for a lot longer than 5 hours. Iām just going to briefly tell you about everything that I did before I started tracking with Hackatime. I looked through the Lume source code to figure out how the poorly-documented theme APIs work. I copied the tufte.css file into the project. Then I downloaded the font .tff files, compressed them into .woff2 files, and wrote css font-face rules for them. I made some Vento layouts. I created, styled, and wrote the logic for the site header. I wrote the blog post and blog index layouts and created the BlogList component. I started installing Lume plugins like KaTeX and Nueglow. I started writing the āUsing this themeā post. I created the tufte-sections and tufte-notes plugins for markdown-it. I began heavily tweaking and customizing tufte.css. I transcribed every word of the TufteCSS homepage from HTML to Markdown. I started configuring LumeCMS. Most of what Iāve done since then (whatās reflected in the 5 hours Iāve logged with this devlog) has been a lot of writing, mainly in the Using this theme post. Iāve also been adjusting the LumeCMS config a lot. I think that the next thing that Iāll do is write the README. Thanks for reading!"}]...
|
Title: Lume Tufte by @ethmarks | Stardance
Devlog Title: Lume Tufte by @ethmarks | Stardance
Devlogs:
Hi there! This is a project Iāve been working on for the past week. Itās a theme for Lume SSG based on Tufte CSS. Btw, I did the majority of the work before I started using Hackatime, so Iāve been working on it for a lot longer than 5 hours. Iām just going to briefly tell you about everything that I did before I started tracking with Hackatime. I looked through the Lume source code to figure out how the poorly-documented theme APIs work. I copied the tufte.css file into the project. Then I downloaded the font .tff files, compressed them into .woff2 files, and wrote css font-face rules for them. I made some Vento layouts. I created, styled, and wrote the logic for the site header. I wrote the blog post and blog index layouts and created the BlogList component. I started installing Lume plugins like KaTeX and Nueglow. I started writing the āUsing this themeā post. I created the tufte-sections and tufte-notes plugins for markdown-it. I began heavily tweaking and customizing tufte.css. I transcribed every word of the TufteCSS homepage from HTML to Markdown. I started configuring LumeCMS. Most of what Iāve done since then (whatās reflected in the 5 hours Iāve logged with this devlog) has been a lot of writing, mainly in the Using this theme post. Iāve also been adjusting the LumeCMS config a lot. I think that the next thing that Iāll do is write the README. Thanks for reading!
README, optimizations, and more Since my last devlog: I wrote the README. I optimized the theme until it earned perfect 100s in every category on Lighthouse on every page. I added a light mode. I added support for tables of contents. I added RSS feed generation. I rewrote one of the demo blog posts. I added styles for HTML tables Link to the diff between last devlog and this one Optimization Most of the work I did today is pretty self-explanatory from my little summary, but the optimization work probably merits elaboration. So while I was writing the README, I had the idea to include the Lighthouse scores. When I checked, they were 100/100/100/92 on mobile and 92/100/100/92 on desktop. ā100s on Lighthouse in some fieldsā doesnāt sound nearly as nice as ā100s on Lighthouse in every fieldā, so I decided to start optimizing. Lighthouse told me that the SEO problem was a lack of descriptions, and the desktop performance problem was excessive network requests and chained network requests. SEO problem I fixed the lack of descriptions by adding descriptions. Simple as that. I wrote descriptions for all of the existing pages, added a description field to the CMS config, and added a mention of it in the usage guide. The network requests and chained requests were a bit trickier to solve. Performance problems The cause of the excessive network requests was that, even though the homepage didnāt use the KaTeX or Nueglow styles, they were still being imported. I solved that with a per-page check that runs at build time. Each page only imports the Nueglow stylesheet if it contains code blocks, and it only imports the KaTeX stylesheet if the page contains math blocks. Hereās a link to the relevant section of code . I think that itās a pretty clever solution because it selectively removes the unnecessary CSS requests without using client-side JS or anything like that. I used a similar approach to solve the chained requests. What was happening is that in order to download the woff2 files, the browser first had to download the CSS files, so it took twice as long because they couldnāt be downloaded in parallel. Font preloads are the way to solve this. The only problem is that if I preload too many font files, the browser will have download font files even if they arenāt used on the page. But if I preload too few, then the network requests are still chained. My solution was to have it check which font files each page needs and selectively preload only those font files. Hereās the relevant code if you want to see my implementation. Again, this solves the problem of unnecessary requests and chained requests without adding any client-side JS. Iām glad that Lume and Vento are such powerful tools that I can easily do programmatic optimizations like this. Next Steps I think that the next thing I should do is submit my theme to the official Lume theme repo. That way I can simplify the installation process down to one command.
Theme Registry PR I just created a PR to add my theme to the official theme registry for Lume: https://github.com/lumeland/themes/pull/10 . Why If my theme isnāt in the official registry, the best way for users install it is to clone my entire repo, which is silly, bad for separation of concerns, and just generally worse for UX. git clone https://github.com/ethmarks/lume_tufte.git cd lume_tufte deno task serve But if I get my theme into the theme registry, users can install it using the official Lume init command, which is much better in every way: deno run -A https://lume.land/init.ts --theme = tufte Conclusion From my interactions with him in the past, the Lume maintainer (Oscar) seems like an extremely nice dude who seems to respond fairly quickly, so I shouldnāt have to wait too long before he either accepts my PR or suggests changes that I can go implement. Meanwhile, Iāll probably continue working on the README.
1.0.0 Unless I think of more stuff to add, this is probably my last devlog before shipping. Lume Theme Registry A few hours ago, the PR that I created last devlog was merged into the official Lume theme registry, so you can now install my theme with a single command using Lume init, and it now has its own dedicated page on the official Lume website: https://lume.land/theme/tufte/ . README I added a How it Works section that explains how the Lume theme architecture works behind-the-scenes (spoiler: itās just remote files) and explains what each of the 18 included plugins do. I updated the quickstart to use the Lume init command. I added a Showcase section that lists the sites that use this theme. It seemed kind of weird to exclusively list the Tufte theme site itself, so I also switched one of my documentation sites to use the Tufte theme. I added a shields.io badge to the top of the README that links to the themeās page on the Lume website. shields.io relies on simple-icons for its logos, but simple-icons doesnāt have the Lume logo for some reason, so had to Base64-encode an SVG of the Lume logo in order to get the badge to work. Next steps Iām not going to ship this project juuuuust yet in case I think of any missing features that I ought to add, but I probably will soon.
Ships:
This is a theme for the Lume static site generator based on Tufte CSS . To try the Tufte theme, visit the demo page: https://ethmarks.github.io/lume_tufte/ . I submitted this PR to the official Lume theme registry to add the Tufte theme, which was accepted. It has its own page on the official Lume site: https://lume.land/theme/tufte/ I used several optimization tricks, such as statically analyzing the content of each page at build time to infer which font files to preload, to maximize performance, accessibility, best practices, and SEO. Because of this, the theme earns perfect 100s on Google Lighthouse , which the official Lighthouse documentation describes as āextremely challenging to achieve and not expectedā . I wrote 5000+ words of documentation across the README and demo articles. I wrote Lume CMS config for every aspect of the theme to allow for no-code content management....
|
1793872219.7118204
|
1793958619.7118204
|
|
18207
|
FNAF6 Bot by @theEclipse | Stardance
|
theEclipse
|
0
|
3.65
|
0
|
[]
|
[{"post_id": 9072, "ts": "2026 [{"post_id": 9072, "ts": "2026-06-15T04:40:23Z", "hours": 0.3819, "text": "Created a function to check the balance at the start of each night. This is super helpful when it comes to determining whether or not we can buy certain utilities."}, {"post_id": 9044, "ts": "2026-06-15T03:04:47Z", "hours": 2.2022, "text": "Finally added all the different sound effects that the bot needs to detect. This will help in some aspects such as animatronic detection or when a task is done."}, {"post_id": 8381, "ts": "2026-06-13T22:45:59Z", "hours": 1.0692, "text": "Automatically bought the sanitation station!"}]...
|
Title: FNAF6 Bot by @theEclipse | Stardance
Devlo Title: FNAF6 Bot by @theEclipse | Stardance
Devlogs:
Automatically bought the sanitation station!
Finally added all the different sound effects that the bot needs to detect. This will help in some aspects such as animatronic detection or when a task is done.
Created a function to check the balance at the start of each night. This is super helpful when it comes to determining whether or not we can buy certain utilities....
|
1793768058.0541213
|
1794372858.0541213
|
|
18208
|
Formula Theory & Automotive Design by @muthusu Formula Theory & Automotive Design by @muthusubhash | Stardance...
|
muthusubhash
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Formula Theory & Automotive Design by @ Title: Formula Theory & Automotive Design by @muthusubhash | Stardance...
|
1793220948.933399
|
1793825748.933399
|
|
18209
|
StardustArm by @Praknoor | Stardance
|
Praknoor
|
1
|
23.29
|
63
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-29T12:58:26Z", "hours": 7.0, "multiplier": 8.66, "payout": 63, "blessing": "neutral", "text": "StardustArm is a NASA-themed zero-gravity robotic arm simulator built with MuJoCo ā a 6-DOF MEPhi arm on a spaceship reaching and grabbing floating target spheres, with both a hand-coded IK controller and a SAC+HER reinforcement learning pipeline. The hardest problems were getting the IK to actually converge (joint angles were only set as PD targets, never applied directly to qpos, so the arm would approach then drift away), hiding the obstacle spheres so they didnāt look like extra target balls, and keeping the ball from slipping and flying out of the single-jaw gripper. Iām most proud of the full-stack integration ā damped least-squares IK, minimum-jerk trajectories, floating base thrusters, vision detection, obstacle avoidance, and RL training all working together for a cohesive on-orbit servicing demo. To test it, cd stardance, pip install mujoco gymnasium stable-baselines3 sb3-contrib tensorboard glfw PyOpenGL, then python main.py for the IK controller or python train_sac.py ārun my_run ātimesteps 500000 for RL training; left-drag orbits the camera, right-drag zooms, ESC exits.", "repo": "https://github.com/GurnoorLog/StardustArm", "demo": "https://stardustarm.gurnoor.hackclub.app/"}]...
|
[{"post_id": 47533, "ts": "202 [{"post_id": 47533, "ts": "2026-08-15T14:41:04Z", "hours": 12.5214, "text": "just mad esome improvments gng, now u can place the ballā¦. i need to make it also live in the website nowā¦ā¦damn it took me so much time to figure out this šššš"}, {"post_id": 37505, "ts": "2026-07-30T09:33:34Z", "hours": 3.7692, "text": "just made it onlineā¦ā¦.and tweaked a bitā¦ā¦ā¦ https://stardustarm.gurnoor.hackclub.app/"}, {"post_id": 14656, "ts": "2026-06-23T20:48:55Z", "hours": 7.2478, "text": "this is stardust____a robotic arm simulator in MuJoCoā¦ā¦..it took me so much time just to figure out the phy behind it , and also how to apply it to the modelā¦..oh well hope u like itā¦ā¦.had fun"}]...
|
Title: StardustArm by @Praknoor | Stardance
Devlo Title: StardustArm by @Praknoor | Stardance
Devlogs:
this is stardust____a robotic arm simulator in MuJoCoā¦ā¦..it took me so much time just to figure out the phy behind it , and also how to apply it to the modelā¦..oh well hope u like itā¦ā¦.had fun
just made it onlineā¦ā¦.and tweaked a bitā¦ā¦ā¦ https://stardustarm.gurnoor.hackclub.app/
just mad esome improvments gng, now u can place the ballā¦. i need to make it also live in the website nowā¦ā¦damn it took me so much time to figure out this šššš
Ships:
StardustArm is a NASA-themed zero-gravity robotic arm simulator built with MuJoCo ā a 6-DOF MEPhi arm on a spaceship reaching and grabbing floating target spheres, with both a hand-coded IK controller and a SAC+HER reinforcement learning pipeline. The hardest problems were getting the IK to actually converge (joint angles were only set as PD targets, never applied directly to qpos, so the arm would approach then drift away), hiding the obstacle spheres so they didnāt look like extra target balls, and keeping the ball from slipping and flying out of the single-jaw gripper. Iām most proud of the full-stack integration ā damped least-squares IK, minimum-jerk trajectories, floating base thrusters, vision detection, obstacle avoidance, and RL training all working together for a cohesive on-orbit servicing demo. To test it, cd stardance, pip install mujoco gymnasium stable-baselines3 sb3-contrib tensorboard glfw PyOpenGL, then python main.py for the IK controller or python train_sac.py ārun my_run ātimesteps 500000 for RL training; left-drag orbits the camera, right-drag zooms, ESC exits....
|
1793724867.761501
|
1793811267.761501
|
|
18210
|
My awesome macropad! by @BryanNMSilva | Stardance
|
BryanNMSilva
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @BryanNMSilva | Sta Title: My awesome macropad! by @BryanNMSilva | Stardance...
|
1793900902.6147594
|
1794505702.6147594
|
|
18211
|
RoboArm by @Snippet | Stardance
|
Snippet
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: RoboArm by @Snippet | Stardance
|
1793281686.887095
|
1793886486.887095
|
|
18212
|
Clickly by @sebastiancanosanchez7 | Stardance
|
sebastiancanosanchez7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Clickly by @sebastiancanosanchez7 | Stardan Title: Clickly by @sebastiancanosanchez7 | Stardance...
|
1793238932.1033633
|
1793843732.1033633
|
|
18213
|
My first slack bot! by @driti | Stardance
|
driti
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @driti | Stardance
|
1793566280.846165
|
1794171080.846165
|
|
18214
|
My awesome macropad! by @lithusukug | Stardance
|
lithusukug
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @lithusukug | Stard Title: My awesome macropad! by @lithusukug | Stardance...
|
1793883261.9147346
|
1794488061.9147346
|
|
18215
|
My first slack bot! by @jasmine001 | Stardance
|
jasmine001
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @jasmine001 | Starda Title: My first slack bot! by @jasmine001 | Stardance...
|
1793365046.315093
|
1793969846.315093
|
|
18216
|
You vs You by @arjunprabhu | Stardance
|
arjunprabhu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: You vs You by @arjunprabhu | Stardance
|
1793246086.3217332
|
1793850886.3217332
|
|
18217
|
My very own WebOS by @jonathan | Stardance
|
jonathan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @jonathan | Stardance
|
1793890161.010847
|
1794754161.010847
|
|
18218
|
Custom Web Os by @jonathan | Stardance
|
jonathan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Custom Web Os by @jonathan | Stardance
|
1793897274.8864942
|
1794761274.8864942
|
|
18219
|
Worst macropad in the world! by @gerardodaguilar09 Worst macropad in the world! by @gerardodaguilar09 | Stardance...
|
gerardodaguilar09
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Worst macropad in the world! by @gerardodag Title: Worst macropad in the world! by @gerardodaguilar09 | Stardance...
|
1793267678.8350089
|
1793872478.8350089
|
|
18220
|
My first slack bot! by @isadora | Stardance
|
isadora
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @isadora | Stardance
|
1793342906.7848845
|
1793947706.7848845
|
|
18221
|
mini music player! by @sleepymeep | Stardance
|
sleepymeep
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: mini music player! by @sleepymeep | Stardan Title: mini music player! by @sleepymeep | Stardance...
|
1793328463.9869251
|
1793933263.9869251
|
|
18222
|
Cyberdeck by @s0meone | Stardance
|
s0meone
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cyberdeck by @s0meone | Stardance
|
1793504966.4360979
|
1794109766.4360979
|
|
18223
|
Frictionless by @dhivya | Stardance
|
dhivya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @dhivya | Stardance
|
1793234962.9090302
|
1793839762.9090302
|
|
18224
|
My awesome macropad! by @mattliepins | Stardance
|
mattliepins
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @mattliepins | Star Title: My awesome macropad! by @mattliepins | Stardance...
|
1793807467.8082902
|
1794412267.8082902
|
|
18225
|
Untitled by @arjunprabhu | Stardance
|
arjunprabhu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @arjunprabhu | Stardance
|
1793494385.1335182
|
1794099185.1335182
|
|
18226
|
My very own WebOS by @Vaanya | Stardance
|
Vaanya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Vaanya | Stardance
|
1793839970.3403006
|
1794444770.3403006
|
|
18227
|
MegaLife by @bad-indentation | Stardance
|
bad-indentation
|
0
|
4.01
|
0
|
[]
|
[{"post_id": 8437, "ts": "2026 [{"post_id": 8437, "ts": "2026-06-14T01:15:36Z", "hours": 1.6214, "text": "Finished the first iteration of the Rust backend, passed some tests, and linked it to the UI. It definitely works, for the signature GoL patterns (blocks, loaves, gliders, etc.) are emerging, but the system is still quite unable to handle the 1000x1000 grid I had hoped for. The bottleneck may simply be the PyO3 interface, or (very likely) there may be much room for optimization in my Rust code."}, {"post_id": 8363, "ts": "2026-06-13T22:06:26Z", "hours": 2.3856, "text": "Wrote most of the Python frontend using Pygame (graphics are neither my forte nor my passion, and I wanted to focus on the internal logic). Also began working on a Rust struct accessible via PyO3 which encapsulates and mutates the GoL grid. This is really my first go at PyO3 and Maturin (or any cross-language project, for that matter), but it seems Python and Rust have been communicating nicely so far."}]...
|
Title: MegaLife by @bad-indentation | Stardance
D Title: MegaLife by @bad-indentation | Stardance
Devlogs:
Wrote most of the Python frontend using Pygame (graphics are neither my forte nor my passion, and I wanted to focus on the internal logic). Also began working on a Rust struct accessible via PyO3 which encapsulates and mutates the GoL grid. This is really my first go at PyO3 and Maturin (or any cross-language project, for that matter), but it seems Python and Rust have been communicating nicely so far.
Finished the first iteration of the Rust backend, passed some tests, and linked it to the UI. It definitely works, for the signature GoL patterns (blocks, loaves, gliders, etc.) are emerging, but the system is still quite unable to handle the 1000x1000 grid I had hoped for. The bottleneck may simply be the PyO3 interface, or (very likely) there may be much room for optimization in my Rust code....
|
1793393559.5172217
|
1793998359.5172217
|
|
18228
|
Lando Norris Fan OS by @F1_ms | Stardance
|
F1_ms
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-21T18:31:03Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What did you make? I built Lando Norris Fan WebOS, an interactive, simulated desktop operating system themed around F1 driver Lando Norris (LN4). Running entirely in the browser, it features a glassmorphic taskbar with a live real-time clock, draggable windows, and three core applications: Welcome Screen: A landing page with links to Landoās social media. Race Weekends (F1 Calendar): An app showing upcoming/past 2026 races and active race reports. F1 Standings: A beautiful dashboard tracking the latest 2026 championship points for drivers and teams. What was challenging? One of the biggest hurdles was managing window layers (z-index) so that clicking any window automatically brings it to the top. I also struggled with JavaScript event listeners not firing correctly due to a script loading conflict (type=āmoduleā vs standard scripts), which caused the close buttons to freeze. I resolved this by building a dedicated debugging script checker that automatically verifies button IDs and implements safety click fallbacks. What are you proud of? I am incredibly proud of building the F1 Standings App! I structured the tabs myself to let users toggle between Drivers and Constructors. I customized the styling using custom CSS so that championship leaders (like Kimi Antonelli) have a golden-shimmer highlight, podium positions look like gold, silver, and bronze, and Lando/McLaren have the iconic signature orange branding. What should people know so they can test your project? Double-click the desktop icons to launch apps! You can drag windows around by clicking and holding their headers. Click anywhere inside an open window to bring it to the foreground. Use the navigation buttons inside the apps to toggle between Calendar/Reports or Drivers/Teams. Click the ā button on the top right of any window to close it.", "repo": "https://github.com/F1ms-maker/Webos", "demo": "https://f1ms-maker.github.io/Webos/"}]...
|
[{"post_id": 13259, "ts": "202 [{"post_id": 13259, "ts": "2026-06-21T18:26:36Z", "hours": 0.3069, "text": "Finishing Last Infos"}, {"post_id": 8633, "ts": "2026-06-14T10:59:00Z", "hours": 1.5644, "text": "Some good Progress and the first App!!!"}, {"post_id": 8400, "ts": "2026-06-13T23:31:55Z", "hours": 1.0858, "text": "Finished for Today first steps done"}]...
|
Title: Lando Norris Fan OS by @F1_ms | Stardance
Title: Lando Norris Fan OS by @F1_ms | Stardance
Devlogs:
Finished for Today first steps done
Some good Progress and the first App!!!
Finishing Last Infos
Ships:
What did you make? I built Lando Norris Fan WebOS, an interactive, simulated desktop operating system themed around F1 driver Lando Norris (LN4). Running entirely in the browser, it features a glassmorphic taskbar with a live real-time clock, draggable windows, and three core applications: Welcome Screen: A landing page with links to Landoās social media. Race Weekends (F1 Calendar): An app showing upcoming/past 2026 races and active race reports. F1 Standings: A beautiful dashboard tracking the latest 2026 championship points for drivers and teams. What was challenging? One of the biggest hurdles was managing window layers (z-index) so that clicking any window automatically brings it to the top. I also struggled with JavaScript event listeners not firing correctly due to a script loading conflict (type=āmoduleā vs standard scripts), which caused the close buttons to freeze. I resolved this by building a dedicated debugging script checker that automatically verifies button IDs and implements safety click fallbacks. What are you proud of? I am incredibly proud of building the F1 Standings App! I structured the tabs myself to let users toggle between Drivers and Constructors. I customized the styling using custom CSS so that championship leaders (like Kimi Antonelli) have a golden-shimmer highlight, podium positions look like gold, silver, and bronze, and Lando/McLaren have the iconic signature orange branding. What should people know so they can test your project? Double-click the desktop icons to launch apps! You can drag windows around by clicking and holding their headers. Click anywhere inside an open window to bring it to the foreground. Use the navigation buttons inside the apps to toggle between Calendar/Reports or Drivers/Teams. Click the ā button on the top right of any window to close it....
|
1793735400.4125438
|
1793821800.4125438
|
|
18229
|
Spectronix: Multimodal Spectral Fusion and Band Re Spectronix: Multimodal Spectral Fusion and Band Reduction for Deep-LearningāGuided Intraoperative Cancer-Margin Detectio by @Arhaan | Stardance...
|
Arhaan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Spectronix: Multimodal Spectral Fusion and Title: Spectronix: Multimodal Spectral Fusion and Band Reduction for Deep-LearningāGuided Intraoperative Cancer-Margin Detectio by @Arhaan | Stardance...
|
1793501414.8737872
|
1794106214.8737872
|
|
18230
|
My very own WebOS by @Pranaav2014 | Stardance
|
Pranaav2014
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Pranaav2014 | Stardan Title: My very own WebOS by @Pranaav2014 | Stardance...
|
1793281768.4880264
|
1793886568.4880264
|
|
18231
|
Untitled project by @saiprajwalbellamkonda | Stard Untitled project by @saiprajwalbellamkonda | Stardance...
|
saiprajwalbellamkonda
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @saiprajwalbellamkonda Title: Untitled project by @saiprajwalbellamkonda | Stardance...
|
1793357684.2402928
|
1793962484.2402928
|
|
18232
|
Untitled by @arjunprabhu | Stardance
|
arjunprabhu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @arjunprabhu | Stardance
|
1793364665.7621477
|
1793969465.7621477
|
|
18233
|
My very own WebOS by @Saadiya | Stardance
|
Saadiya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Saadiya | Stardance
|
1793307445.2233763
|
1793912245.2233763
|
|
18234
|
My awesome macropad! by @Rhea | Stardance
|
Rhea
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Rhea | Stardance
|
1793335930.4062123
|
1793940730.4062123
|
|
18235
|
Custom cheap pnp by @Simon_ | Stardance
|
Simon_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Custom cheap pnp by @Simon_ | Stardance
|
1793314402.8892097
|
1793919202.8892097
|
|
18236
|
My very own WebOS by @heian | Stardance
|
heian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @heian | Stardance
|
1793868453.2674754
|
1794732453.2674754
|
|
18237
|
My very own WebOS by @arjunprabhu3 | Stardance
|
arjunprabhu3
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @arjunprabhu3 | Starda Title: My very own WebOS by @arjunprabhu3 | Stardance...
|
1793339524.4197333
|
1793944324.4197333
|
|
18238
|
My very own WebOS by @Renscal | Stardance
|
Renscal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Renscal | Stardance
|
1793300153.3973477
|
1793904953.3973477
|
|
18239
|
My first slack bot! by @JDap | Stardance
|
JDap
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @JDap | Stardance
|
1793390051.2518482
|
1793994851.2518482
|
|
18240
|
An Ideal Macropad by @shankarnoone | Stardance
|
shankarnoone
|
0
|
0.28
|
0
|
[]
|
[{"post_id": 14545, "ts": "202 [{"post_id": 14545, "ts": "2026-06-23T18:14:09Z", "hours": 0.2797, "text": "First Devlog!"}]...
|
Title: An Ideal Macropad by @shankarnoone | Starda Title: An Ideal Macropad by @shankarnoone | Stardance
Devlogs:
First Devlog!...
|
1793519701.4370341
|
1794124501.4370341
|
|
18241
|
Frictionless by @bilalqaiser | Stardance
|
bilalqaiser
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @bilalqaiser | Stardance
|
1793321449.6363194
|
1793926249.6363194
|
|
18242
|
Frictionless by @shankarnoone | Stardance
|
shankarnoone
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @shankarnoone | Stardance
|
1793501444.4578364
|
1794106244.4578364
|
|
18243
|
My first slack bot! by @syedshahmeerali2 | Stardan My first slack bot! by @syedshahmeerali2 | Stardance...
|
syedshahmeerali2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @syedshahmeerali2 | Title: My first slack bot! by @syedshahmeerali2 | Stardance...
|
1793328836.1312804
|
1793933636.1312804
|
|
18244
|
My awesome macropad! by @alice | Stardance
|
alice
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @alice | Stardance
|
1793519769.7106822
|
1794124569.7106822
|
|
18245
|
Untitled by @arjunprabhu | Stardance
|
arjunprabhu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @arjunprabhu | Stardance
|
1793389941.1533754
|
1793994741.1533754
|
|
18246
|
My very own WebOS by @arjunprabhu | Stardance
|
arjunprabhu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @arjunprabhu | Stardan Title: My very own WebOS by @arjunprabhu | Stardance...
|
1793310704.220706
|
1793915504.220706
|
|
18247
|
My awesome macropad! by @The_Blue_Reverberation | My awesome macropad! by @The_Blue_Reverberation | Stardance...
|
The_Blue_Reverberation
|
0
|
5.7
|
0
|
[]
|
[{"post_id": 59904, "ts": "202 [{"post_id": 59904, "ts": "2026-09-01T22:35:44Z", "hours": 5.7025, "text": "well this took a lot more than it should have for a box with buttons, as painful as this was i gotta say its decently fun, i havenāt made the screen do stuff yet iāll tweak it all when the package arrives expect firmware updates on github every now and then (lapse tweaked the hell out so the pcb progress wasnāt recorded thankfully i have other plugins for onshape and vsc), my genius ahh forgot to include all the images in the devlog so check out the projects readme for all the info"}]...
|
Title: My awesome macropad! by @The_Blue_Reverbera Title: My awesome macropad! by @The_Blue_Reverberation | Stardance
Devlogs:
well this took a lot more than it should have for a box with buttons, as painful as this was i gotta say its decently fun, i havenāt made the screen do stuff yet iāll tweak it all when the package arrives expect firmware updates on github every now and then (lapse tweaked the hell out so the pcb progress wasnāt recorded thankfully i have other plugins for onshape and vsc), my genius ahh forgot to include all the images in the devlog so check out the projects readme for all the info...
|
1793501450.5912597
|
1794106250.5912597
|
|
18248
|
My awesome macropad! by @Isholo | Stardance
|
Isholo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Isholo | Stardance
|
1793498004.7027144
|
1794102804.7027144
|
|
18249
|
My very own WebOS by @mlaurasarmentov | Stardance
|
mlaurasarmentov
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @mlaurasarmentov | Sta Title: My very own WebOS by @mlaurasarmentov | Stardance...
|
1793451338.4791574
|
1794056138.4791574
|
|
18250
|
Powerblock Auth by @Powerblock | Stardance
|
Powerblock
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-22T16:46:12Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "This is a Authentication frontend and Manager for the Godot game engine and Nakama. I built this because itās REALLY annoying to set up good Nakama authentication. Right now it only supports Email and Device ID but as I use new libraries I will probably add it here :). Please report any issues. Thanks!", "repo": "https://github.com/Powerblock2000/PowerblockAuth", "demo": "https://powerblock2000.github.io/PowerblockAuth/WEBSITE/r2/index.html"}]...
|
[{"post_id": 8812, "ts": "2026 [{"post_id": 8812, "ts": "2026-06-14T17:18:24Z", "hours": 1.0456, "text": "Finished README and website Check it out at: https://powerblock2000.github.io/PowerblockAuth/ Ready to ship waiting on voting to openā¦"}, {"post_id": 8473, "ts": "2026-06-14T02:48:02Z", "hours": 1.2483, "text": "Finished Frontend and Backend, getting bugs now ššŖ²"}, {"post_id": 8414, "ts": "2026-06-13T23:56:09Z", "hours": 0.7017, "text": "Working on the Nakama session lifecycle"}]...
|
Title: Powerblock Auth by @Powerblock | Stardance
Title: Powerblock Auth by @Powerblock | Stardance
Devlogs:
Working on the Nakama session lifecycle
Finished Frontend and Backend, getting bugs now ššŖ²
Finished README and website Check it out at: https://powerblock2000.github.io/PowerblockAuth/ Ready to ship waiting on voting to openā¦
Ships:
This is a Authentication frontend and Manager for the Godot game engine and Nakama. I built this because itās REALLY annoying to set up good Nakama authentication. Right now it only supports Email and Device ID but as I use new libraries I will probably add it here :). Please report any issues. Thanks!...
|
1793858053.133449
|
1793944453.133449
|