|
2286
|
Untitled by @Joeryon2011 | Stardance
|
Joeryon2011
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Joeryon2011 | Stardance
|
1792576127.8311024
|
1793180927.8311024
|
|
2285
|
Wired Speaker by @Juniper | Stardance
|
Juniper
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Wired Speaker by @Juniper | Stardance
|
1792597644.183514
|
1793202444.183514
|
|
2284
|
Phone for calls and texting by @Simon | Stardance
|
Simon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Phone for calls and texting by @Simon | Sta Title: Phone for calls and texting by @Simon | Stardance...
|
1793141663.9753978
|
1793746463.9753978
|
|
2283
|
My awesome macropad! by @khyati | Stardance
|
khyati
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @khyati | Stardance
|
1793174089.8707187
|
1793778889.8707187
|
|
2282
|
N/A by @AydenFauteaux | Stardance
|
AydenFauteaux
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: N/A by @AydenFauteaux | Stardance
|
1792795674.3086264
|
1793400474.3086264
|
|
2281
|
e by @prad | Stardance
|
prad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: e by @prad | Stardance
|
1792561726.5611644
|
1793166526.5611644
|
|
2280
|
Robo by @Ayushi | Stardance
|
Ayushi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Robo by @Ayushi | Stardance
|
1792734606.358434
|
1793339406.358434
|
|
2279
|
Robotic arm by @Lizardguy | Stardance
|
Lizardguy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Robotic arm by @Lizardguy | Stardance
|
1792716816.1600838
|
1793321616.1600838
|
|
2278
|
Untitled by @Jxsh | Stardance
|
Jxsh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Jxsh | Stardance
|
1792565465.6064944
|
1793170265.6064944
|
|
2277
|
I want to create project that help peaple to creat I want to create project that help peaple to create cv and find jop by @omaradel123232432 | Stardance...
|
omaradel123232432
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: I want to create project that help peaple t Title: I want to create project that help peaple to create cv and find jop by @omaradel123232432 | Stardance...
|
1792637671.7191718
|
1793242471.7191718
|
|
2276
|
My awesome macropad! by @KNYCS | Stardance
|
KNYCS
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @KNYCS | Stardance
|
1792684105.153911
|
1793288905.153911
|
|
2275
|
My awesome macropad! by @Thisisnull | Stardance
|
Thisisnull
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Thisisnull | Stard Title: My awesome macropad! by @Thisisnull | Stardance...
|
1792723795.3615742
|
1793328595.3615742
|
|
2274
|
STARBOARD by @Mando328 | Stardance
|
Mando328
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: STARBOARD by @Mando328 | Stardance
|
1792885775.0797088
|
1793749775.0797088
|
|
2273
|
My first slack bot! by @harshitchand998 | Stardanc My first slack bot! by @harshitchand998 | Stardance...
|
harshitchand998
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @harshitchand998 | S Title: My first slack bot! by @harshitchand998 | Stardance...
|
1792601542.919817
|
1793206342.919817
|
|
2272
|
MinecraftIsInfinite by @GameLord2011 | Stardance
|
GameLord2011
|
0
|
3.99
|
0
|
[]
|
[{"post_id": 2223, "ts": "2026 [{"post_id": 2223, "ts": "2026-06-04T16:42:23Z", "hours": 0.8783, "text": "Almost done wat."}, {"post_id": 1567, "ts": "2026-06-03T17:44:05Z", "hours": 1.0914, "text": "Added some not-entirely-working-at-the-moment-but-they-will-kinda-serve-a-purpose-later-if-the-mixed-in-methods-are-the-problematic-ones-i-really-hope-this-is-not-a-waste-of-time mixins."}, {"post_id": 933, "ts": "2026-06-02T18:03:23Z", "hours": 1.15, "text": "Removed first world border, will work on the second one soon."}, {"post_id": 355, "ts": "2026-06-01T17:47:05Z", "hours": 0.8664, "text": "Removed client side world border rendering logic."}]...
|
Title: MinecraftIsInfinite by @GameLord2011 | Star Title: MinecraftIsInfinite by @GameLord2011 | Stardance
Devlogs:
Removed client side world border rendering logic.
Removed first world border, will work on the second one soon.
Added some not-entirely-working-at-the-moment-but-they-will-kinda-serve-a-purpose-later-if-the-mixed-in-methods-are-the-problematic-ones-i-really-hope-this-is-not-a-waste-of-time mixins.
Almost done wat....
|
1792777931.7617638
|
1793382731.7617638
|
|
2271
|
My first slack bot! by @nickje2010 | Stardance
|
nickje2010
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @nickje2010 | Starda Title: My first slack bot! by @nickje2010 | Stardance...
|
1792615684.2967184
|
1793220484.2967184
|
|
2270
|
Life is wonderful by @ss3128872 | Stardance
|
ss3128872
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Life is wonderful by @ss3128872 | Stardance
|
1792554539.6524887
|
1793159339.6524887
|
|
2269
|
image_editor by @nlktech | Stardance
|
nlktech
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: image_editor by @nlktech | Stardance
|
1793174029.487974
|
1793778829.487974
|
|
2268
|
Matcha Linux by @DoMax | Stardance
|
DoMax
|
2
|
50.0
|
831
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-12T17:35:30Z", "hours": 23.0, "multiplier": 15.71, "payout": 424, "blessing": "neutral", "text": "3 months since the last release! Here’s how Matcha Linux improved: New install flow : It can finally be installed on real hardware Package installation is now more robust, handling package installation properly, with APK tags Many new bugfixes within the matcha-calamares package regarding mounting, cleanup, package management and more Installer optimizations - Live install environment uses only 2.5GB of RAM, allowing for 3GB of RAM support! (Huge improvement btw) Bloat removal - The current build features a stripped version of GNOME without, saving both RAM and disk space. Some packages were replaced in favor of alternatives OpenGL version checking - Some of the system components require OpenGL 4.3+ and GPUs that don’t support it now offload the rendering to CPU to avoid crashes NEW Requirements Memory : 3GB of RAM Storage : 5GB free disk space for installation UEFI Firmware : Required, legacy BIOS not supported Known Limitations If there is more than one iso9660 filesystem mounted while installing, the installer will trigger an error Since the current requirement for GPU-driven OpenGL rendering is OpenGL 4.3+, some systems might feel sluggish due to the CPU doing all the work I hope you enjoy testing and using Matcha Linux :D", "repo": "https://github.com/domasles/matcha-linux", "demo": "https://github.com/domasles/matcha-linux/releases/tag/2026.09.11"}, {"ship_num": 2, "ts": "2026-06-09T22:16:00Z", "hours": 27.0, "multiplier": 15.16, "payout": 407, "blessing": "neutral", "text": "I engineered Matcha Linux - a fresh, fast, and fluid desktop OS built on top of Alpine Linux to combat software bloat and give any x86_64 UEFI hardware a life with a gorgeous and usable GNOME experience. It idles at JUST 1.5GB of RAM! The OS includes a custom port of Calamares installer specifically made for Matcha Linux (which probably took the most amount of work), and a heavily customized unique GNOME desktop. Navigating the initial release was a rollercoaster of debugging broken services, installer locales, build and install issues, encryption, swap configuration and ISO permissions, but the stable 2026.06.09 build is officially live, works out-of-the-box. Before testing it live or in a VM (4GB RAM, 10GB storage minimum, UEFI only), note that native glibc apps require a quick Distrobox container setup to run on Alpine.", "repo": "https://github.com/domasles/matcha-linux", "demo": "https://github.com/domasles/matcha-linux/releases/tag/2026.09.11"}]...
|
[{"post_id": 66191, "ts": "202 [{"post_id": 66191, "ts": "2026-09-11T21:09:11Z", "hours": 9.8739, "text": "Pre-ship devlog This post is about everything that recently happened with Matcha Linux 1. New terminal app! Yes, gnome-console got boring, so I replaced it! With none other than ghostty . It’s great - has hardware rendering support, native integration with Kitty image rendering (so fastfetch renders the logo properly) and MANY color themes, one of which happens to perfectly match Matcha’s look and feel. 2. Package management Since ghostty is from Alpine’s edge repos, I had to find a native way of tagging the packages both while building the iso, and installing the system. Previous approach blindly installed every package from live ISO. This works only when every package is designed to be sourced from the stable branch. One edge package and updates (or maybe the whole system) breaks! Now, a helper file helps install the necessary packages both onto the ISO and later system’s disk. Since packages are installed by their names, not separate files from some medium, the installation can also be way more accurate and, in some cases, more compact. 3. OpenGL checks Ghostty loves OpenGL. But it relies on OpenGL 4.3+, and on hardware that doesn’t support this - crashes. Luckily, if GPU bridge fails, CPU can handle OpenGL operations just as well! Matcha Linux, starting from today, is expecting hardware to support OpenGL 4.3+ to utilize the GPU for OpenGL APIs. Anything older than 2013-ish (which goes on par with UEFI requirement) would fail. In case of that happening, I added conditional rendering to use the CPU as a fallback. For now, however, it’s system-wide (to support any other software built with OpenGL 4.3+). OpenGL ES is not supported on the GPU at the moment. 4. Bugfixes!! Who doesn’t love when their software just… Works? The upgraded matcha-calamares installer now has a full cleanup stage, correctly catches errors regarding the install ISO presence, also has fixes for many other mount and install issues that could happen in earlier releases. Bottom line I love building this Linux distro. The challenges I have to face and the amount of operation ordering I have to do helps me improve. Structure is one of the skills I think humanity is yet to fully master, and i hope that one day, it can. As for the future of Matcha, it will continue to grow! Tech never sleeps, new releases need updates, and Matcha mustn’t be left behind. I also have more ambitious stuff planned (like an update manager and distrobox install module for calamares), and they are the only thing I’m afraid of implementing. For now, I’ll stick to making Matcha Linux as stable as possible, and then focus on something more exciting. I hope more people find this distro to test, daily drive and share the feedback! Always exciting to engage with communities."}, {"post_id": 63003, "ts": "2026-09-06T15:55:04Z", "hours": 10.5983, "text": "3GB RAM milestone!! How I managed to achieve 3GB RAM usage in the live environment (but at the same time - break a couple things) Stage 1 - package optimization Probably not a surprise to you that Gnome desktop environment is a heavy beast. Well, as it turns out, it bundles a bunch of stuff that’s not technically required to run the system. Alpine package gnome adds many apps (like calendar, weather and more) that aren’t relevant anymore. However, even though unused, they take up space, and in Alpine, the live environment installs every package onto ram to provide a diskless environment. At first I tried making a filesystem capable of loading packages from mounted iso as it’s necessary for the install either way, but optimizing package selection turned out to be easier (besides - who has a 64bit system with less than 6GB ram these days?) Stage 2 - package loading The fact that package selection is optimized to reduce Gnome’s bloat wasn’t enough to make the install environment lighter. Alpine has a file /etc/apk/world in which every package that should be installed is defined. Utilizing it I could control what packages must appear within the live system, and which - not (because you probably don’t need a heavy browser before installing the system). Stage 3 - things break if you’re too brave And they broke for me too. Certain admin functionality (like some polkit integrations) don’t work anymore due to the limited selection (and probably some hidden dependencies) of packages. I think I have diagnozed the issue though - testing suggests that it could be the missing linux-pam package or some dbus initialization race conditions. Other important updates Besides implementing optimizations to the image (consequences of which I can hopefully fix), I also made sure to update extensions, as well as the matcha-calamares package that now has a broader support for systems and reduces crashes. The building pipeline was also slightly tweaked. Either way, I’m off to fixing the issue, so see you in the next devlog!"}, {"post_id": 6344, "ts": "2026-06-10T17:58:42Z", "hours": 2.6097, "text": "Today, when one Hack Clubber pointed out that they wish to try Matcha Linux on Hyper-V, I thought it would work. Turns out I was completely wrong! Linux, built with the LTS kernel instead of VM-specific (Virt), breaks on Hyper-V due to inability to pass the framebuffer through Hyper-V’s exceptional drivers (or so I think). The minimal terminal works, but flickers due to GDM trying to restart every few ms. Implementing a dual-ISO build pipeline I fixed this issue and also made Matcha Linux and its packages work on top of a new Alpine (v3.24) release. Thought it would be harder, but both Alpine itself, and Gnome 50 play along very well! Also added Hyper-V specific instructions to the README."}, {"post_id": 5905, "ts": "2026-06-09T21:37:53Z", "hours": 5.8019, "text": "It builds, it runs, it WORKS! I was really surprised with how this OS turned out. After what seemed like a rollercoaster of issues that had me stumped for a while, and countless hours of debugging, I STILL managed to deliver a working product this soon. It relieved me, and I can consider myself both lucky and proud. After fixing all said issues in the previous devlogs, I present Matcha Linux 2026.06.09 - the initial release. Matcha Linux was made to combat e-waste, hardware pricing increase and provide a beautiful yet customizable experience to absolutely anyone! By being able to run it on any x86_64 UEFI-compatible piece of hardware, using very few resources, Matcha Linux aims to be the primary choice for people trying to escape bloat. What was fixed since the last devlog: Swap not working due to a service not being run on boot Locales not being correctly set up due to a missing installer module Additional tweaks: Reworked the permission system to be more reliable and controllable (when building the live ISO image) Implemented a proper post-install reboot mechanism by tweaking installer’s configuration Refactored build source files to be more compact, added comments where necessary Removed keyboard configuration from the installer due to it not being well integrated with GNOME Cleaned up repositories, added better documentation, published first working release files I consider this experience a lesson not only about Linux, but also the need of doing things sequentally, planning and always going forward, no matter what challenge waits up front. Do I have something else planned for the future? YES! But these things may be quite difficult: A custom installer module to provide the setup for Distrobox (to run almost any Linux app (by default they won’t run unless installed through APK and are within Alpine Linux repositories. Running layered Debian, Arch or Fedora boxes creates disposable and highly capable environments)) A custom updater program (probably won’t be integrated this summer) Further debugging and engaging with the community I hope this project inspires many people to build projects and solve problems for the whole world. Open source, as it should be."}, {"post_id": 4584, "ts": "2026-06-07T22:33:32Z", "hours": 4.8797, "text": "Several bugs fixed! (And one drawback taken) First off, with the fixes: Installer UI no longer crashes when selecting a swap option or entering encryption details (the issue was only persistent on legacy BIOS boot and without a certain configuration file (bootloader.conf, that got added)) Encryption finally works! Can’t show in the devlog image, but a disk can be encrypted and decrypted with LUKS properly A non-encrypted approach of installation is also viable and works as it should Drawback (the sad part): Since I couldn’t get legacy BIOS to not crash the installer in a mentioned case, after strong considerations I have decided that Matcha Linux will only officially support EFI, and enforced this behaviour in the build pipeline This gets along the philosophy of using modern lightweight standards that Matcha tries to utilize, so it’s not much of a loss What remains broken: Swap memory does not seem to be working in the installed system, even when the necessary files ARE created by the installer Timezones don’t still work properly After fixing said issues the project will be ready to ship. Hopefully it shouldn’t take more than a week"}, {"post_id": 3405, "ts": "2026-06-06T10:02:47Z", "hours": 2.0461, "text": "I have successfully resolved the issues found in the earlier build, and everything works (almost) flawlessly now! New things: Cleaned up build scripts to make them more portable and more easily readable Implemented package exclusion when installing the OS Customized the default dock apps list Improved branding by implementing FastFetch configuration However, I have noticed some bugs that are worth taking a look into: When setting up the disk with swap space, the installer crashes. Maybe just a package missing that handles this LUKS encryption does not work Timezone setup is useless as it doesn’t set up the timezone (manual setup is working post-install, but the installer SHOULD set that up) After fixing those, Matcha Linux can finally ship!"}, {"post_id": 2736, "ts": "2026-06-05T14:28:43Z", "hours": 9.1078, "text": "Since the last devlog, I put in a LOT of work to make the whole OS build properly This includes: Setting up a well-working approach for installing Matcha Calamares installer to the live system Adding a README to (almost) all repositories related to this project Customizing the installer Tweaking a few things for smoother performance Next steps are: Removing hardcoded references to just make the images “build and run” Reflecting ways of optimization Excluding unnecessary stuff from the installed system Testing everything for the final time Shipping! Wish me luck, now I’m heading out, polishing this project"}, {"post_id": 1081, "ts": "2026-06-02T21:55:39Z", "hours": 1.3753, "text": "FINALLY did I fix the system running incorrectly Turns out, the problem was a faulty overlay that kept overwriting user account files, thus revoking the ability for some system services to run! Now the system installs beautifully, runs even prettier, only thing left is to test whether there is no junk in a fresh system and the user is set up correctly and if the startup times could be improved (unless it’s VirtualBox-specific) Other goals haven’t changed since the last devlog, but I am starting to question if I really need to write software for this distribution myself (for issuing updates, etc…) because the process should be fairly straightforward"}, {"post_id": 844, "ts": "2026-06-02T15:19:59Z", "hours": 3.6919, "text": "First devlog, and with good news already! After successfully porting Calamares installer over to Alpine Linux, today I also made it install the system correctly The issue was bad grub configuration that either did not mount the system or did not load ext4 kernel module With that resolved (and a bit of a rework on live iso build profile) Matcha Linux is one step closer to being at least usabe post-install Remaining issues are: Incorrect group and user creation process due to which dbus service can’t launch (critical) Remaining steps are: Testing if other core services that depend on dbus launch after fixing the issue Testing the system and whether everything copies correctly Future plans: Customizing the installer Adding a DistroBox Debian shell by default for app compatibility Making an updater app"}]...
|
Title: Matcha Linux by @DoMax | Stardance
Devlogs Title: Matcha Linux by @DoMax | Stardance
Devlogs:
First devlog, and with good news already! After successfully porting Calamares installer over to Alpine Linux, today I also made it install the system correctly The issue was bad grub configuration that either did not mount the system or did not load ext4 kernel module With that resolved (and a bit of a rework on live iso build profile) Matcha Linux is one step closer to being at least usabe post-install Remaining issues are: Incorrect group and user creation process due to which dbus service can’t launch (critical) Remaining steps are: Testing if other core services that depend on dbus launch after fixing the issue Testing the system and whether everything copies correctly Future plans: Customizing the installer Adding a DistroBox Debian shell by default for app compatibility Making an updater app
FINALLY did I fix the system running incorrectly Turns out, the problem was a faulty overlay that kept overwriting user account files, thus revoking the ability for some system services to run! Now the system installs beautifully, runs even prettier, only thing left is to test whether there is no junk in a fresh system and the user is set up correctly and if the startup times could be improved (unless it’s VirtualBox-specific) Other goals haven’t changed since the last devlog, but I am starting to question if I really need to write software for this distribution myself (for issuing updates, etc…) because the process should be fairly straightforward
Since the last devlog, I put in a LOT of work to make the whole OS build properly This includes: Setting up a well-working approach for installing Matcha Calamares installer to the live system Adding a README to (almost) all repositories related to this project Customizing the installer Tweaking a few things for smoother performance Next steps are: Removing hardcoded references to just make the images “build and run” Reflecting ways of optimization Excluding unnecessary stuff from the installed system Testing everything for the final time Shipping! Wish me luck, now I’m heading out, polishing this project
I have successfully resolved the issues found in the earlier build, and everything works (almost) flawlessly now! New things: Cleaned up build scripts to make them more portable and more easily readable Implemented package exclusion when installing the OS Customized the default dock apps list Improved branding by implementing FastFetch configuration However, I have noticed some bugs that are worth taking a look into: When setting up the disk with swap space, the installer crashes. Maybe just a package missing that handles this LUKS encryption does not work Timezone setup is useless as it doesn’t set up the timezone (manual setup is working post-install, but the installer SHOULD set that up) After fixing those, Matcha Linux can finally ship!
Several bugs fixed! (And one drawback taken) First off, with the fixes: Installer UI no longer crashes when selecting a swap option or entering encryption details (the issue was only persistent on legacy BIOS boot and without a certain configuration file (bootloader.conf, that got added)) Encryption finally works! Can’t show in the devlog image, but a disk can be encrypted and decrypted with LUKS properly A non-encrypted approach of installation is also viable and works as it should Drawback (the sad part): Since I couldn’t get legacy BIOS to not crash the installer in a mentioned case, after strong considerations I have decided that Matcha Linux will only officially support EFI, and enforced this behaviour in the build pipeline This gets along the philosophy of using modern lightweight standards that Matcha tries to utilize, so it’s not much of a loss What remains broken: Swap memory does not seem to be working in the installed system, even when the necessary files ARE created by the installer Timezones don’t still work properly After fixing said issues the project will be ready to ship. Hopefully it shouldn’t take more than a week
It builds, it runs, it WORKS! I was really surprised with how this OS turned out. After what seemed like a rollercoaster of issues that had me stumped for a while, and countless hours of debugging, I STILL managed to deliver a working product this soon. It relieved me, and I can consider myself both lucky and proud. After fixing all said issues in the previous devlogs, I present Matcha Linux 2026.06.09 - the initial release. Matcha Linux was made to combat e-waste, hardware pricing increase and provide a beautiful yet customizable experience to absolutely anyone! By being able to run it on any x86_64 UEFI-compatible piece of hardware, using very few resources, Matcha Linux aims to be the primary choice for people trying to escape bloat. What was fixed since the last devlog: Swap not working due to a service not being run on boot Locales not being correctly set up due to a missing installer module Additional tweaks: Reworked the permission system to be more reliable and controllable (when building the live ISO image) Implemented a proper post-install reboot mechanism by tweaking installer’s configuration Refactored build source files to be more compact, added comments where necessary Removed keyboard configuration from the installer due to it not being well integrated with GNOME Cleaned up repositories, added better documentation, published first working release files I consider this experience a lesson not only about Linux, but also the need of doing things sequentally, planning and always going forward, no matter what challenge waits up front. Do I have something else planned for the future? YES! But these things may be quite difficult: A custom installer module to provide the setup for Distrobox (to run almost any Linux app (by default they won’t run unless installed through APK and are within Alpine Linux repositories. Running layered Debian, Arch or Fedora boxes creates disposable and highly capable environments)) A custom updater program (probably won’t be integrated this summer) Further debugging and engaging with the community I hope this project inspires many people to build projects and solve problems for the whole world. Open source, as it should be.
Today, when one Hack Clubber pointed out that they wish to try Matcha Linux on Hyper-V, I thought it would work. Turns out I was completely wrong! Linux, built with the LTS kernel instead of VM-specific (Virt), breaks on Hyper-V due to inability to pass the framebuffer through Hyper-V’s exceptional drivers (or so I think). The minimal terminal works, but flickers due to GDM trying to restart every few ms. Implementing a dual-ISO build pipeline I fixed this issue and also made Matcha Linux and its packages work on top of a new Alpine (v3.24) release. Thought it would be harder, but both Alpine itself, and Gnome 50 play along very well! Also added Hyper-V specific instructions to the README.
3GB RAM milestone!! How I managed to achieve 3GB RAM usage in the live environment (but at the same time - break a couple things) Stage 1 - package optimization Probably not a surprise to you that Gnome desktop environment is a heavy beast. Well, as it turns out, it bundles a bunch of stuff that’s not technically required to run the system. Alpine package gnome adds many apps (like calendar, weather and more) that aren’t relevant anymore. However, even though unused, they take up space, and in Alpine, the live environment installs every package onto ram to provide a diskless environment. At first I tried making a filesystem capable of loading packages from mounted iso as it’s necessary for the install either way, but optimizing package selection turned out to be easier (besides - who has a 64bit system with less than 6GB ram these days?) Stage 2 - package loading The fact that package selection is optimized to reduce Gnome’s bloat wasn’t enough to make the install environment lighter. Alpine has a file /etc/apk/world in which every package that should be installed is defined. Utilizing it I could control what packages must appear within the live system, and which - not (because you probably don’t need a heavy browser before installing the system). Stage 3 - things break if you’re too brave And they broke for me too. Certain admin functionality (like some polkit integrations) don’t work anymore due to the limited selection (and probably some hidden dependencies) of packages. I think I have diagnozed the issue though - testing suggests that it could be the missing linux-pam package or some dbus initialization race conditions. Other important updates Besides implementing optimizations to the image (consequences of which I can hopefully fix), I also made sure to update extensions, as well as the matcha-calamares package that now has a broader support for systems and reduces crashes. The building pipeline was also slightly tweaked. Either way, I’m off to fixing the issue, so see you in the next devlog!
Pre-ship devlog This post is about everything that recently happened with Matcha Linux 1. New terminal app! Yes, gnome-console got boring, so I replaced it! With none other than ghostty . It’s great - has hardware rendering support, native integration with Kitty image rendering (so fastfetch renders the logo properly) and MANY color themes, one of which happens to perfectly match Matcha’s look and feel. 2. Package management Since ghostty is from Alpine’s edge repos, I had to find a native way of tagging the packages both while building the iso, and installing the system. Previous approach blindly installed every package from live ISO. This works only when every package is designed to be sourced from the stable branch. One edge package and updates (or maybe the whole system) breaks! Now, a helper file helps install the necessary packages both onto the ISO and later system’s disk. Since packages are installed by their names, not separate files from some medium, the installation can also be way more accurate and, in some cases, more compact. 3. OpenGL checks Ghostty loves OpenGL. But it relies on OpenGL 4.3+, and on hardware that doesn’t support this - crashes. Luckily, if GPU bridge fails, CPU can handle OpenGL operations just as well! Matcha Linux, starting from today, is expecting hardware to support OpenGL 4.3+ to utilize the GPU for OpenGL APIs. Anything older than 2013-ish (which goes on par with UEFI requirement) would fail. In case of that happening, I added conditional rendering to use the CPU as a fallback. For now, however, it’s system-wide (to support any other software built with OpenGL 4.3+). OpenGL ES is not supported on the GPU at the moment. 4. Bugfixes!! Who doesn’t love when their software just… Works? The upgraded matcha-calamares installer now has a full cleanup stage, correctly catches errors regarding the install ISO presence, also has fixes for many other mount and install issues that could happen in earlier releases. Bottom line I love building this Linux distro. The challenges I have to face and the amount of operation ordering I have to do helps me improve. Structure is one of the skills I think humanity is yet to fully master, and i hope that one day, it can. As for the future of Matcha, it will continue to grow! Tech never sleeps, new releases need updates, and Matcha mustn’t be left behind. I also have more ambitious stuff planned (like an update manager and distrobox install module for calamares), and they are the only thing I’m afraid of implementing. For now, I’ll stick to making Matcha Linux as stable as possible, and then focus on something more exciting. I hope more people find this distro to test, daily drive and share the feedback! Always exciting to engage with communities.
Ships:
I engineered Matcha Linux - a fresh, fast, and fluid desktop OS built on top of Alpine Linux to combat software bloat and give any x86_64 UEFI hardware a life with a gorgeous and usable GNOME experience. It idles at JUST 1.5GB of RAM! The OS includes a custom port of Calamares installer specifically made for Matcha Linux (which probably took the most amount of work), and a heavily customized unique GNOME desktop. Navigating the initial release was a rollercoaster of debugging broken services, installer locales, build and install issues, encryption, swap configuration and ISO permissions, but the stable 2026.06.09 build is officially live, works out-of-the-box. Before testing it live or in a VM (4GB RAM, 10GB storage minimum, UEFI only), note that native glibc apps require a quick Distrobox container setup to run on Alpine.
3 months since the last release! Here’s how Matcha Linux improved: New install flow : It can finally be installed on real hardware Package installation is now more robust, handling package installation properly, with APK tags Many new bugfixes within the matcha-calamares package regarding mounting, cleanup, package management and more Installer optimizations - Live install environment uses only 2.5GB of RAM, allowing for 3GB of RAM support! (Huge improvement btw) Bloat removal - The current build features a stripped version of GNOME without, saving both RAM and disk space. Some packages were replaced in favor of alternatives OpenGL version checking - Some of the system components require OpenGL 4.3+ and GPUs that don’t support it now offload the rendering to CPU to avoid crashes NEW Requirements Memory : 3GB of RAM Storage : 5GB free disk space for installation UEFI Firmware : Required, legacy BIOS not supported Known Limitations If there is more than one iso9660 filesystem mounted while installing, the installer will trigger an error Since the current requirement for GPU-driven OpenGL rendering is OpenGL 4.3+, some systems might feel sluggish due to the CPU doing all the work I hope you enjoy testing and using Matcha Linux :D...
|
1793123498.549076
|
1793209898.549076
|
|
2267
|
My first slack bot! by @umut | Stardance
|
umut
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @umut | Stardance
|
1792666206.7347827
|
1793271006.7347827
|
|
2266
|
My awesome macropad! by @Abrish | Stardance
|
Abrish
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Abrish | Stardance
|
1792608599.3579123
|
1793213399.3579123
|
|
2265
|
Bean2Space (DIY Rocket) by @TGA25dev | Stardance
|
TGA25dev
|
0
|
44.29
|
0
|
[]
|
[{"post_id": 74447, "ts": "202 [{"post_id": 74447, "ts": "2026-09-27T12:09:07Z", "hours": 1.2717, "text": "Devlog # 15 What’s new ? Parachute ! I’ve worked an hour on the parachute design and I think it came pretty good, I’ve tested it from a very low altitude and it seems to work well so I’m pretty happy with it. It’s made out of a tyvek security suit and I’ve used nylon cables for the lines."}, {"post_id": 74412, "ts": "2026-09-27T10:36:40Z", "hours": 1.1864, "text": "Devlog #14.1 What’s new ? Nothing really important in this devlog tbh, again lot’s of tests in the code, debugging and trying new things (that didn’t worked..) I’ve also replaced the imu temperature value in the live telemetry by the mcu temperature because it’s a more important value to know and monitor. Cool things are coming! (like the parachute design )"}, {"post_id": 73492, "ts": "2026-09-25T07:23:31Z", "hours": 2.6869, "text": "Devlog #14 What’s new ? I’ve been working mainly on software those days, I had a few issues with the program running on battery, once it was started I couldn’t connect it again with the cable. To fix that I’ve added another main script that runs when the chip is powered on and adds a timer to et me interrupt boot sequence if needed. Then, I’ve worked on a collector for the ground station whose role is to grab the data of the other esp32 by serial and save it to a csv file (it can then be readed by the dashboard for example) Due to the collector needing a new telemetry parsing structure I’ve also updated how telemetry sequences are written and printed in the ground station main file Also, I’ve been doing some tests with the state detection algorithm to try if it detected well the different flight states (I literally threw the electronics in the air and almost smashed them on the ground, but it’s ok at least it worked well) See you for the next devlog!"}, {"post_id": 70864, "ts": "2026-09-19T21:49:22Z", "hours": 3.7017, "text": "Devlog #13 What’s new ? A lot of work today as I’ve finished the soldering part!! Now the flight computer is done and mounted into the 3D printed sled, it was my first time soldering like that and I think it came pretty decent (though cable management looks horrible to me). The only thing that didn’t work when I powered it was the led, I spent a long time trying to understand what was wrong to finally realize that I had fried it… I replaced it with a new one and the issue was solved! (also changed the color by the way) Appart from soldering I’ve also added a setting to disable buzzer or led on startup and an internal temperature watchdog to monitor the temperature and prevent the chip from overheating What’s next ? As I said earlier the project is almost finished! Yet I still need to add a few more features, fix some bugs and print the last parts"}, {"post_id": 70602, "ts": "2026-09-19T13:03:41Z", "hours": 3.0914, "text": "Devlog #12 Wow it’s really been a while since last devlog.. so ? What’s new ? Well I’ve been working on a dasboard for the rocket, it uses Streamlit to display data and gathers data from a csv file that is saved on the computer. csv file is written by a local script that uses serial to catch data from the ground station via usb-c I’ve also been improving CAD model a little bit, that includes fillets for the fins and modifications to the instruments rack Also fixed a bug where calibration offsets weren’t applied properly, optimized some code and tried a lot of things in the main script. What’s next ? Last week I’ve started soldering the components to the perfboard so Lapse devlog is coming very soon, I’m planning to finish this in a few days Once soldering is done I will test out the software in “real” conditions and print the missing parts of the rocket Stay tuned ! ✨"}, {"post_id": 55639, "ts": "2026-08-27T16:28:56Z", "hours": 4.0294, "text": "Devlog #11 What’s new? I initially planned on adding an SD Card module but after fighting with it for almost two hours I couldn’t get it to work, it uses SPI but I don’t know why it refused cooperate.. Then I improved the wireless transmission system by adding sequence numbers and the rocket state to the packets. Everything was working fine until it totally stopped working. I spent another hour trying to debug only to finally plug the external antenas into both ESPs which fixed the issue.. Finally I’ve moved the rocket state detection to a separate module so the main file remains clean and is easier to debug What’s next? Now that those issues are solved I’m going to create a nice dashboard I will run on my computer to display live data charts and logs, I don’t know how I’m going to design it but hopefully it will look great On the screenshot you can see on the left logs from the rocket and on the right the live data that is pulled from the ground station by serial connection."}, {"post_id": 53065, "ts": "2026-08-23T13:58:43Z", "hours": 1.4889, "text": "Devlog #10 What’s new ? First of all I now have the missing funds to complete the project, that’s pretty insane and I’m really happy and proud about it Second, I’v been working again on the external pods as the measurements for the camera were wrong and it didn’t fitted at all. I’m going to print that part to test it out but it should now be fixed."}, {"post_id": 47185, "ts": "2026-08-14T22:02:08Z", "hours": 3.4086, "text": "Devlog #9.2 What’s new ? Some tweaks on CAD README ! I’v spent quite a lot of time writing the readme file, hope it’s good! I’v added several sections with a lot of details and renders from Fusion."}, {"post_id": 41273, "ts": "2026-08-05T11:52:29Z", "hours": 0.4667, "text": "Devlog #9.1 What’s new ? I’v added a mount for the shock cord, I will put a screw and attach the cord to it. the screw will go in those holes. Both mounts will be printed separately and then glued with expoxy On the bottom of the engine stage I’v also added 4 holes to attach the cord to"}, {"post_id": 41245, "ts": "2026-08-05T10:25:58Z", "hours": 1.9014, "text": "Devlog #9 What’s new ? CAD: I’v updated the top cover of the trigger system box because the new fire button I’v chose needed a bigger hole Wirings: I’v made two schematics, one for the flight computer on wokwi and another for the trigger station on draw.io. Took me a bit of time to understand how to create both diagrams since it’s the first time I use those websites but I think it came pretty good. What’s nex ? First I’m gonna address some issues I’v seen on the design especially in the engine stage Then when it’s done I’ll double check my BOM file is correct and I will probably submit for funding"}, {"post_id": 40804, "ts": "2026-08-04T15:43:03Z", "hours": 4.6297, "text": "Devlog #8 What’s new ? This time I’v designed the component’s sled/rack: The sled will first slide in the main tube and then be attached using 4 M3 screws as you can see on both sides (I’ll also use 4 other screws to secure the soldering board on the rack itself.) I will then add heat inserts when building. On the other side of the sled the lipo battery will be secured using velcro straps. And on the middle I’v added 2 “windows” for cable management. As you can see I’v also added 3 holes (the triangle pattern) on the main tube, they’r static port holes and will be used to ensure the pressure inside the rocket is the same as outside (for the pressure sensor to get correct data) EDIT: I just realized I forgot to upload the screenshot showing that and now I can’t… What’s next ? I think I might now submit the project for funding as I am missing some critical pieces to build the rocket. I’ll also probably tweak some things in the design and log a few hours more. After than I will continue to code the flight computer. Stay tuned! 🚀"}, {"post_id": 38862, "ts": "2026-08-01T12:57:15Z", "hours": 5.9436, "text": "Devlog #7 What’s new ? I worked a lot on CAD for the past 10h of work, lot’s of headaches because of the pods (and because I forgot to hit record on lapse) but here’s what I made : It took me a lot of time to work on the pods because I couldn’t find a good aerodynamic design. So I designed it, re-designed it and re-re-redisigned it. Finally I have something working though it’s not perfect, I should tweak some things to make it even better. I also worked on designing the ground trigger system, basically it’s a box that will host the batteries to ignite the rocket, a security lock with a key and the fire button. It wasn’t very hard but it also took me a bit of time to find the correct diameters for the components. What’s next ? Well I think I will polish the designs perhaps add new things and fix some others, once thats done I will submit for funding to get the rest of the components I need. Stay tuned!"}, {"post_id": 27079, "ts": "2026-07-12T09:53:23Z", "hours": 1.1592, "text": "Devlog #6 What’s new ? The rocket has now a state tracking system, what this does is that it takes the altitude, calculates the velocity and then deduces the rocket’s state (iddle, in flight, descending etc etc..) It took me some time to understand how velocity could be used and calculated and I also had to implement smpoothing systems to prevent the noise from the sensors to give me weird values I’v also added a “demo mode”, it simulates fake telemetry (altitude) so I can test the status tracking system What’s next ? Well I don’t really know, I’v been strugling with live logs and I don’t really know how I could implement that, I’ll see what’s missing and what I can do to improve the rocket Below is a screenshot of the terminal’s output, because I’m not going to take another picture of the harware as nothing really changed.. I’ll try to do better next devlog!"}, {"post_id": 19365, "ts": "2026-06-30T17:17:45Z", "hours": 1.9311, "text": "Devlog #5 CAD!! Well so today I opened Fusion360 and entirely remodeled all the parts of the rocket. I had mesh files from OpenRocket but I needed to turn them into solid shapes. I will probably have to spend more time on Fusion because I’m not sure the shoulder for the main stage is well designed and will fit properly. Also, I might need to design something to keep the engine inside the tube so it doesn’t move."}, {"post_id": 16833, "ts": "2026-06-27T10:23:39Z", "hours": 1.815, "text": "Devlog #4 What’s new On each run the rocket is now assigned a random flight number for better identification (also added in transmitted packets, you’l see later why) Zombie connections are now killed before starting everything to prevent issues with unclosed sockets Clock chip frequency has been reduced (the esp is heating a lot I need to find why and fix the performances..) I’v added new telemetry packet flags to distinguish between telemetry and messages (I’ll probably forward live logs from the rocket to the ground station using that) What’s coming Well, pretty much everything I said before (performances, live logs, telemetry saving in csv files, charts..) Also going to try to start the CAD in Fusion360"}, {"post_id": 15646, "ts": "2026-06-25T13:22:40Z", "hours": 2.2681, "text": "Devlog #3 What’s new I was looking at the telemetry data and noticed relative pressure mesurement was uncorrect so I fixed it (took me a moment to understand why..) - Also fixed gyro x value calculation that was wrong Now the main chip broadcasts it’s telemetry so it can be read by the other chip on the ground I’v added new buttons to the dashboard to stop Wifi and start ESPNow transmission Anddd last but not least, the rocket has now an internal clock which is for now used as timestamp when packets are sent What’s on the picture The “ground station” (white cable) which is an ESP32 C3 My breadboard with all the components which will be in the rocket (just noticed buzzer cable was disconnected)"}, {"post_id": 15539, "ts": "2026-06-25T08:01:32Z", "hours": 1.2831, "text": "Devlog #2 What’s new I’v started working on live wireless transmission so I could have live data transmission from the rocket to a ground station (another ESP32). I can now broadcast data from the rocket and it’s read by the ground station. I’v added new options on the dashboard, I can now remotely start the calibration process – it will be useful on ground before the launch And now ? Now I am going to improve the dashboard by addind new options and probably telemetry Probably going to cleanup some code and put things in other files for better readability"}, {"post_id": 12518, "ts": "2026-06-20T13:17:26Z", "hours": 2.0281, "text": "1st devlog! Made basic CAD in OpenRocket software to design the rocket’s body and fins. It helped me understanding how aerodynamics will affect the rocket during the flight Started the software part, I use Python paired with a XIAO ESP32 S3 as main flight computer. I also have a BMP280 and an MPU6050 as main flight instruments. I’v added getter functions for telemetry and setters for calibration. Also added the main file with a startup function and wifi manager for wireless ground control."}]...
|
Title: Bean2Space (DIY Rocket) by @TGA25dev | Star Title: Bean2Space (DIY Rocket) by @TGA25dev | Stardance
Devlogs:
1st devlog! Made basic CAD in OpenRocket software to design the rocket’s body and fins. It helped me understanding how aerodynamics will affect the rocket during the flight Started the software part, I use Python paired with a XIAO ESP32 S3 as main flight computer. I also have a BMP280 and an MPU6050 as main flight instruments. I’v added getter functions for telemetry and setters for calibration. Also added the main file with a startup function and wifi manager for wireless ground control.
Devlog #2 What’s new I’v started working on live wireless transmission so I could have live data transmission from the rocket to a ground station (another ESP32). I can now broadcast data from the rocket and it’s read by the ground station. I’v added new options on the dashboard, I can now remotely start the calibration process – it will be useful on ground before the launch And now ? Now I am going to improve the dashboard by addind new options and probably telemetry Probably going to cleanup some code and put things in other files for better readability
Devlog #3 What’s new I was looking at the telemetry data and noticed relative pressure mesurement was uncorrect so I fixed it (took me a moment to understand why..) - Also fixed gyro x value calculation that was wrong Now the main chip broadcasts it’s telemetry so it can be read by the other chip on the ground I’v added new buttons to the dashboard to stop Wifi and start ESPNow transmission Anddd last but not least, the rocket has now an internal clock which is for now used as timestamp when packets are sent What’s on the picture The “ground station” (white cable) which is an ESP32 C3 My breadboard with all the components which will be in the rocket (just noticed buzzer cable was disconnected)
Devlog #4 What’s new On each run the rocket is now assigned a random flight number for better identification (also added in transmitted packets, you’l see later why) Zombie connections are now killed before starting everything to prevent issues with unclosed sockets Clock chip frequency has been reduced (the esp is heating a lot I need to find why and fix the performances..) I’v added new telemetry packet flags to distinguish between telemetry and messages (I’ll probably forward live logs from the rocket to the ground station using that) What’s coming Well, pretty much everything I said before (performances, live logs, telemetry saving in csv files, charts..) Also going to try to start the CAD in Fusion360
Devlog #5 CAD!! Well so today I opened Fusion360 and entirely remodeled all the parts of the rocket. I had mesh files from OpenRocket but I needed to turn them into solid shapes. I will probably have to spend more time on Fusion because I’m not sure the shoulder for the main stage is well designed and will fit properly. Also, I might need to design something to keep the engine inside the tube so it doesn’t move.
Devlog #6 What’s new ? The rocket has now a state tracking system, what this does is that it takes the altitude, calculates the velocity and then deduces the rocket’s state (iddle, in flight, descending etc etc..) It took me some time to understand how velocity could be used and calculated and I also had to implement smpoothing systems to prevent the noise from the sensors to give me weird values I’v also added a “demo mode”, it simulates fake telemetry (altitude) so I can test the status tracking system What’s next ? Well I don’t really know, I’v been strugling with live logs and I don’t really know how I could implement that, I’ll see what’s missing and what I can do to improve the rocket Below is a screenshot of the terminal’s output, because I’m not going to take another picture of the harware as nothing really changed.. I’ll try to do better next devlog!
Devlog #7 What’s new ? I worked a lot on CAD for the past 10h of work, lot’s of headaches because of the pods (and because I forgot to hit record on lapse) but here’s what I made : It took me a lot of time to work on the pods because I couldn’t find a good aerodynamic design. So I designed it, re-designed it and re-re-redisigned it. Finally I have something working though it’s not perfect, I should tweak some things to make it even better. I also worked on designing the ground trigger system, basically it’s a box that will host the batteries to ignite the rocket, a security lock with a key and the fire button. It wasn’t very hard but it also took me a bit of time to find the correct diameters for the components. What’s next ? Well I think I will polish the designs perhaps add new things and fix some others, once thats done I will submit for funding to get the rest of the components I need. Stay tuned!
Devlog #8 What’s new ? This time I’v designed the component’s sled/rack: The sled will first slide in the main tube and then be attached using 4 M3 screws as you can see on both sides (I’ll also use 4 other screws to secure the soldering board on the rack itself.) I will then add heat inserts when building. On the other side of the sled the lipo battery will be secured using velcro straps. And on the middle I’v added 2 “windows” for cable management. As you can see I’v also added 3 holes (the triangle pattern) on the main tube, they’r static port holes and will be used to ensure the pressure inside the rocket is the same as outside (for the pressure sensor to get correct data) EDIT: I just realized I forgot to upload the screenshot showing that and now I can’t… What’s next ? I think I might now submit the project for funding as I am missing some critical pieces to build the rocket. I’ll also probably tweak some things in the design and log a few hours more. After than I will continue to code the flight computer. Stay tuned! 🚀
Devlog #9 What’s new ? CAD: I’v updated the top cover of the trigger system box because the new fire button I’v chose needed a bigger hole Wirings: I’v made two schematics, one for the flight computer on wokwi and another for the trigger station on draw.io. Took me a bit of time to understand how to create both diagrams since it’s the first time I use those websites but I think it came pretty good. What’s nex ? First I’m gonna address some issues I’v seen on the design especially in the engine stage Then when it’s done I’ll double check my BOM file is correct and I will probably submit for funding
Devlog #9.1 What’s new ? I’v added a mount for the shock cord, I will put a screw and attach the cord to it. the screw will go in those holes. Both mounts will be printed separately and then glued with expoxy On the bottom of the engine stage I’v also added 4 holes to attach the cord to
Devlog #9.2 What’s new ? Some tweaks on CAD README ! I’v spent quite a lot of time writing the readme file, hope it’s good! I’v added several sections with a lot of details and renders from Fusion.
Devlog #10 What’s new ? First of all I now have the missing funds to complete the project, that’s pretty insane and I’m really happy and proud about it Second, I’v been working again on the external pods as the measurements for the camera were wrong and it didn’t fitted at all. I’m going to print that part to test it out but it should now be fixed.
Devlog #11 What’s new? I initially planned on adding an SD Card module but after fighting with it for almost two hours I couldn’t get it to work, it uses SPI but I don’t know why it refused cooperate.. Then I improved the wireless transmission system by adding sequence numbers and the rocket state to the packets. Everything was working fine until it totally stopped working. I spent another hour trying to debug only to finally plug the external antenas into both ESPs which fixed the issue.. Finally I’ve moved the rocket state detection to a separate module so the main file remains clean and is easier to debug What’s next? Now that those issues are solved I’m going to create a nice dashboard I will run on my computer to display live data charts and logs, I don’t know how I’m going to design it but hopefully it will look great On the screenshot you can see on the left logs from the rocket and on the right the live data that is pulled from the ground station by serial connection.
Devlog #12 Wow it’s really been a while since last devlog.. so ? What’s new ? Well I’ve been working on a dasboard for the rocket, it uses Streamlit to display data and gathers data from a csv file that is saved on the computer. csv file is written by a local script that uses serial to catch data from the ground station via usb-c I’ve also been improving CAD model a little bit, that includes fillets for the fins and modifications to the instruments rack Also fixed a bug where calibration offsets weren’t applied properly, optimized some code and tried a lot of things in the main script. What’s next ? Last week I’ve started soldering the components to the perfboard so Lapse devlog is coming very soon, I’m planning to finish this in a few days Once soldering is done I will test out the software in “real” conditions and print the missing parts of the rocket Stay tuned ! ✨
Devlog #13 What’s new ? A lot of work today as I’ve finished the soldering part!! Now the flight computer is done and mounted into the 3D printed sled, it was my first time soldering like that and I think it came pretty decent (though cable management looks horrible to me). The only thing that didn’t work when I powered it was the led, I spent a long time trying to understand what was wrong to finally realize that I had fried it… I replaced it with a new one and the issue was solved! (also changed the color by the way) Appart from soldering I’ve also added a setting to disable buzzer or led on startup and an internal temperature watchdog to monitor the temperature and prevent the chip from overheating What’s next ? As I said earlier the project is almost finished! Yet I still need to add a few more features, fix some bugs and print the last parts
Devlog #14 What’s new ? I’ve been working mainly on software those days, I had a few issues with the program running on battery, once it was started I couldn’t connect it again with the cable. To fix that I’ve added another main script that runs when the chip is powered on and adds a timer to et me interrupt boot sequence if needed. Then, I’ve worked on a collector for the ground station whose role is to grab the data of the other esp32 by serial and save it to a csv file (it can then be readed by the dashboard for example) Due to the collector needing a new telemetry parsing structure I’ve also updated how telemetry sequences are written and printed in the ground station main file Also, I’ve been doing some tests with the state detection algorithm to try if it detected well the different flight states (I literally threw the electronics in the air and almost smashed them on the ground, but it’s ok at least it worked well) See you for the next devlog!
Devlog #14.1 What’s new ? Nothing really important in this devlog tbh, again lot’s of tests in the code, debugging and trying new things (that didn’t worked..) I’ve also replaced the imu temperature value in the live telemetry by the mcu temperature because it’s a more important value to know and monitor. Cool things are coming! (like the parachute design )
Devlog # 15 What’s new ? Parachute ! I’ve worked an hour on the parachute design and I think it came pretty good, I’ve tested it from a very low altitude and it seems to work well so I’m pretty happy with it. It’s made out of a tyvek security suit and I’ve used nylon cables for the lines....
|
1792561911.7863793
|
1793166711.7863793
|
|
2264
|
Untitled by @saisnithik | Stardance
|
saisnithik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @saisnithik | Stardance
|
1792734426.5029757
|
1793339226.5029757
|
|
2263
|
My awesome macropad! by @aayush | Stardance
|
aayush
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @aayush | Stardance
|
1792547640.8304338
|
1793152440.8304338
|
|
2262
|
SendIt - Transfer Files Easily by @sobaankh | Star SendIt - Transfer Files Easily by @sobaankh | Stardance...
|
sobaankh
|
0
|
4.39
|
0
|
[]
|
[{"post_id": 1089, "ts": "2026 [{"post_id": 1089, "ts": "2026-06-02T22:19:21Z", "hours": 2.7956, "text": "Made this beautiful hero section and changed the navbar to give it somewhat sci-fi vibe!"}, {"post_id": 958, "ts": "2026-06-02T18:45:20Z", "hours": 1.5958, "text": "My First React App! Made the Navbar… This is going to be funn!"}]...
|
Title: SendIt - Transfer Files Easily by @sobaankh Title: SendIt - Transfer Files Easily by @sobaankh | Stardance
Devlogs:
My First React App! Made the Navbar… This is going to be funn!
Made this beautiful hero section and changed the navbar to give it somewhat sci-fi vibe!...
|
1792540293.516893
|
1793145093.516893
|
|
2261
|
asd by @Cheetah | Stardance
|
Cheetah
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: asd by @Cheetah | Stardance
|
1792608477.7736304
|
1793213277.7736304
|
|
2260
|
Interplanetary Transfer Calculator (ITC) by @lucie Interplanetary Transfer Calculator (ITC) by @lucienackerly | Stardance...
|
lucienackerly
|
0
|
1.74
|
0
|
[]
|
[{"post_id": 15818, "ts": "202 [{"post_id": 15818, "ts": "2026-06-25T18:21:34Z", "hours": 1.7447, "text": "DevLog #1 Hey everyone, this is my Interplanetary Transfer Calculator (ITC) what it does is take a Hohmann transfer (soon bi-elliptic and other transfers) and it calculates everything for a Hohmann transfer, even calculates how much time it takes how long it takes to get to planet to planet. it has data for our Sol system and the Proxima Centauri system. in the CSV files I added the Radius, Mass, Semi-major Axis, Eccentricity, inclination, orbital period, and the Gravity of each planet. I am big into aerospace engineering, and I really wanted to make a new and improved version of my original version of this. I will soon add the files to a github."}]...
|
Title: Interplanetary Transfer Calculator (ITC) by Title: Interplanetary Transfer Calculator (ITC) by @lucienackerly | Stardance
Devlogs:
DevLog #1 Hey everyone, this is my Interplanetary Transfer Calculator (ITC) what it does is take a Hohmann transfer (soon bi-elliptic and other transfers) and it calculates everything for a Hohmann transfer, even calculates how much time it takes how long it takes to get to planet to planet. it has data for our Sol system and the Proxima Centauri system. in the CSV files I added the Radius, Mass, Semi-major Axis, Eccentricity, inclination, orbital period, and the Gravity of each planet. I am big into aerospace engineering, and I really wanted to make a new and improved version of my original version of this. I will soon add the files to a github....
|
1792562021.4235034
|
1793166821.4235034
|
|
2259
|
Spiders by @Tweearchit | Stardance
|
Tweearchit
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Spiders by @Tweearchit | Stardance
|
1793144902.1333733
|
1793749702.1333733
|
|
2258
|
Wrapper for Python in UEFI! by @Deepesh | Stardanc Wrapper for Python in UEFI! by @Deepesh | Stardance...
|
Deepesh
|
0
|
0.33
|
0
|
[]
|
[{"post_id": 3633, "ts": "2026 [{"post_id": 3633, "ts": "2026-06-06T17:26:49Z", "hours": 0.3333, "text": "Check out github.com/deepeshx9/python-efi-wrapper. I am working on wrapper Rust app that aims to take in a .py MicroPython or CPython file and create a bootable .efi app or even a bootable USB! from a .py file. For Initial Days, I just taped together testbed scripts for my ARM64 host (WSL) with x64 target. Stay tuned."}]...
|
Title: Wrapper for Python in UEFI! by @Deepesh | S Title: Wrapper for Python in UEFI! by @Deepesh | Stardance
Devlogs:
Check out github.com/deepeshx9/python-efi-wrapper. I am working on wrapper Rust app that aims to take in a .py MicroPython or CPython file and create a bootable .efi app or even a bootable USB! from a .py file. For Initial Days, I just taped together testbed scripts for my ARM64 host (WSL) with x64 target. Stay tuned....
|
1792547323.0901942
|
1793152123.0901942
|
|
2257
|
voice by @pamm | Stardance
|
pamm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: voice by @pamm | Stardance
|
1792781279.8528914
|
1793386079.8528914
|
|
2256
|
My awesome macropad! by @DPAK | Stardance
|
DPAK
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @DPAK | Stardance
|
1792547295.0479448
|
1793152095.0479448
|
|
2255
|
My awesome macropad! by @Aguy_503 | Stardance
|
Aguy_503
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Aguy_503 | Stardan Title: My awesome macropad! by @Aguy_503 | Stardance...
|
1792594363.525981
|
1793199163.525981
|
|
2254
|
N by @Stefan | Stardance
|
Stefan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: N by @Stefan | Stardance
|
1792788673.5784168
|
1793393473.5784168
|
|
2253
|
Stardump by @GaminGokil | Stardance
|
GaminGokil
|
1
|
8.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-08T07:54:06Z", "hours": 8.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Stardump - an interactive space to dump all of your thoughts and worries to then explode after you complete them. This was a challenge, especially when I used pure html for the entire project, and the code is a bit messy (however Claude helped me through it all!)", "repo": "https://github.com/GaminGokil/Stardump", "demo": "https://gamingokil.github.io/Stardump/"}]...
|
[{"post_id": 2902, "ts": "2026 [{"post_id": 2902, "ts": "2026-06-05T20:09:18Z", "hours": 0.5, "text": "Minor UI / Quality of life change Credit to @StarCoder for the Idea The welcome screen can now be dismissed by clicking anywhere Added a small button in the bottom right that takes you back to the welcome screen Try it out here: https://gamingokil.github.io/Stardump/ Thank you to @StarCoder for the Idea! Check out the project and drop any suggestions in the comments below! I’ll try my best to implement them and credit you."}, {"post_id": 2557, "ts": "2026-06-05T03:20:10Z", "hours": 0.4006, "text": "Minor / UI update Added the ability to charge up the supernova! The huge explosion can now be charged with particles coming from outside the screen into the center in a center dot. You can try it out here: https://gamingokil.github.io/Stardump/ PLEASE make some suggestions in the comments for future improvements - like any UI changes you would like to see!"}, {"post_id": 2221, "ts": "2026-06-04T16:39:38Z", "hours": 0.8108, "text": "Minor UI update Made some minor UI changes in order to make it look less like AI slop - let me know if its good and what should I change! Future changes: Make some galaxies float by in the background to add some visual spice Add more functionality to the thought stars (Like making them collide!) Remember, you can always try it out here: https://gamingokil.github.io/Stardump/ Make some suggestions in the comments for what I should do!"}, {"post_id": 1937, "ts": "2026-06-04T05:43:02Z", "hours": 1.5817, "text": "HUGE UPDATE Added a feature where it explodes the whole screen and all of your worries on one big BOOM! creates a bipolar supernova in the middle of the screen that explodes and creates a ring that explodes the stars (both in the background and the stars you created) Explode your worries here! https://gamingokil.github.io/Stardump/"}, {"post_id": 1884, "ts": "2026-06-04T03:17:41Z", "hours": 0.4356, "text": "Added multiple galaxies as favicons for the website!!! it now cycles between 17 different galaxies for the website favicon. try it out now: https://gamingokil.github.io/Stardump/"}, {"post_id": 1760, "ts": "2026-06-03T23:04:21Z", "hours": 1.4239, "text": "Added a start page to help new users through the website! Added an infinite canvas so your not limited to just your screen. Added zooming out and in. Added a double click where you can reset your screen to where your stars are if you get lost. Remember to try it out here! https://gamingokil.github.io/Stardump/"}, {"post_id": 607, "ts": "2026-06-02T03:22:02Z", "hours": 3.3097, "text": "Introducing stardump - a place where you can dump your thoughts and then explode them in supernovas once your done. Finished with the prototype - you can go play around with it right now! Future improvements on the way - introduction page and more fun things to do with your idea stars! try it out now! : https://gamingokil.github.io/Stardump/"}]...
|
Title: Stardump by @GaminGokil | Stardance
Devlog Title: Stardump by @GaminGokil | Stardance
Devlogs:
Introducing stardump - a place where you can dump your thoughts and then explode them in supernovas once your done. Finished with the prototype - you can go play around with it right now! Future improvements on the way - introduction page and more fun things to do with your idea stars! try it out now! : https://gamingokil.github.io/Stardump/
Added a start page to help new users through the website! Added an infinite canvas so your not limited to just your screen. Added zooming out and in. Added a double click where you can reset your screen to where your stars are if you get lost. Remember to try it out here! https://gamingokil.github.io/Stardump/
Added multiple galaxies as favicons for the website!!! it now cycles between 17 different galaxies for the website favicon. try it out now: https://gamingokil.github.io/Stardump/
HUGE UPDATE Added a feature where it explodes the whole screen and all of your worries on one big BOOM! creates a bipolar supernova in the middle of the screen that explodes and creates a ring that explodes the stars (both in the background and the stars you created) Explode your worries here! https://gamingokil.github.io/Stardump/
Minor UI update Made some minor UI changes in order to make it look less like AI slop - let me know if its good and what should I change! Future changes: Make some galaxies float by in the background to add some visual spice Add more functionality to the thought stars (Like making them collide!) Remember, you can always try it out here: https://gamingokil.github.io/Stardump/ Make some suggestions in the comments for what I should do!
Minor / UI update Added the ability to charge up the supernova! The huge explosion can now be charged with particles coming from outside the screen into the center in a center dot. You can try it out here: https://gamingokil.github.io/Stardump/ PLEASE make some suggestions in the comments for future improvements - like any UI changes you would like to see!
Minor UI / Quality of life change Credit to @StarCoder for the Idea The welcome screen can now be dismissed by clicking anywhere Added a small button in the bottom right that takes you back to the welcome screen Try it out here: https://gamingokil.github.io/Stardump/ Thank you to @StarCoder for the Idea! Check out the project and drop any suggestions in the comments below! I’ll try my best to implement them and credit you.
Ships:
Stardump - an interactive space to dump all of your thoughts and worries to then explode after you complete them. This was a challenge, especially when I used pure html for the entire project, and the code is a bit messy (however Claude helped me through it all!)...
|
1793141453.821756
|
1793227853.821756
|
|
2252
|
My first slack bot! by @moomoomoov | Stardance
|
moomoomoov
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @moomoomoov | Starda Title: My first slack bot! by @moomoomoov | Stardance...
|
1793195388.5280373
|
1793800188.5280373
|
|
2251
|
Arduino Sibling Security System by @MiloMatter | S Arduino Sibling Security System by @MiloMatter | Stardance...
|
MiloMatter
|
0
|
1.24
|
0
|
[]
|
[{"post_id": 1903, "ts": "2026 [{"post_id": 1903, "ts": "2026-06-04T03:58:06Z", "hours": 0.7225, "text": "Okay, I have compiled all my parts and am ready to build the full system! I have gotten my hands on yet another arduino UNO, so my possibilities just got bigger! All sensors check out well, and I am writing the first draft of the first draft of the final code! :)"}, {"post_id": 1259, "ts": "2026-06-03T04:09:48Z", "hours": 0.5142, "text": "starting on an ultrasonic sensor detection!"}]...
|
Title: Arduino Sibling Security System by @MiloMat Title: Arduino Sibling Security System by @MiloMatter | Stardance
Devlogs:
starting on an ultrasonic sensor detection!
Okay, I have compiled all my parts and am ready to build the full system! I have gotten my hands on yet another arduino UNO, so my possibilities just got bigger! All sensors check out well, and I am writing the first draft of the first draft of the final code! :)...
|
1792583581.0973978
|
1793188381.0973978
|
|
2250
|
CryptoSplitter by @dimk | Stardance
|
dimk
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CryptoSplitter by @dimk | Stardance
|
1792670059.1101224
|
1793274859.1101224
|
|
2249
|
MahouShoujo SakuraSan by @edda | Stardance
|
edda
|
0
|
19.12
|
0
|
[]
|
[{"post_id": 72919, "ts": "202 [{"post_id": 72919, "ts": "2026-09-24T01:31:04Z", "hours": 5.3903, "text": "various screenshots :) most of the work i’ve done has been on the engine and artworks. these are a few screenshots (not in order) of the opening cutscene, and the main menu"}, {"post_id": 46618, "ts": "2026-08-14T00:07:16Z", "hours": 3.4572, "text": "Spent ages getting a typewriter effect working, and added some sfx, composed a song, and here we are :D we have the intro (the first dark bit) and then the test dialogue afterwards (yes, i know the choice boxes are super janky, that’s the next thing im fixing). and yeah our main character is super angsty and not very nice but she has her reasons i promise you normally you probably would not hear the whole song because that beginning blurb is pretty short, but it also plays later on"}, {"post_id": 28919, "ts": "2026-07-15T14:55:32Z", "hours": 4.1708, "text": "Lots of changes have happened since I last devlogged! I fixed the physics, added GUI, collectables, level hazards, changed the background (via prerendered models I made in Blockbench and then rendered in Blender), and extended the map and made it so the camera follows the player. Also, made it so collectables/level stuff spawn via placing them in Tiled instead of me just having to manually input coordinates. Next up, enemies and CPU follower! :D"}, {"post_id": 22437, "ts": "2026-07-04T22:05:00Z", "hours": 2.0325, "text": "after like… forever… of trying to get this freaking map to scale properly… i finally got it. oh my gosh. it was literally one argument i had gotten wrong. literally ONE oh my gosh. end me /silly also ignore the fact the player is suctioned to the upper screen, i am sTILL trying to fix physics."}, {"post_id": 5132, "ts": "2026-06-08T20:25:29Z", "hours": 0.7814, "text": "Fixed the dialogue boxes! Probably won’t get much done this upcoming week, though, I’m on vacationnnnn to the beachhhh~ yay! Fancy shmancy text wrapping for now, wow. I did a little bit on the platformer section, but the tilesets hate me right now I fear."}, {"post_id": 1015, "ts": "2026-06-02T20:08:17Z", "hours": 1.1114, "text": "Finally finished the desktop integration stuff, and put it into the actual main file. It works! More or less- the platformer segment is a little broken, but that’s from the physics screwing up and not the new screen stuff. I plan on fixing it up next time, probably later on tonight or tomorrow, because I’ve been coding for a while already and am getting a bit tired lol Here’s a screenshot of the visual novel segment of the game (The textboxes are going to be slightly reworked, because right now they can’t fit much text at all.)"}, {"post_id": 965, "ts": "2026-06-02T18:54:18Z", "hours": 0.6175, "text": "Menu screen is more or less complete! This is still in the alternate file I made for modifications that lacks any actual interactibility, but once I get everything sorted, I’ll replace a lot of the code for the visuals in the main project folder with the stuff in here. Also, the menu animates now! Though, of course, you can’t see it in a screenshot lol"}, {"post_id": 883, "ts": "2026-06-02T16:36:17Z", "hours": 1.2936, "text": "So, originally, Mahou Shoujo Sakura San (As the full title is called) was being made for a different console than PC. However, I really wanted to get the game actually. working. And there were some annoying technical difficulties getting in the way! So, now I’m making a desktop port, and I just copied its files to a secondary location for whenever I want to continue with the console version. Then I realized, ah frick, if I’m going to make a desktop port, I now have to account for window sizing and generally changing up how it’s displayed, since the PC displays differently than the game’s original console. So I made a THIRD copy (albeit extremely stripped down, containing just the .vscode with the launch.json, all the image files, and an extremely barebones main.lua that basically just loads the files) and got to it. Lo and behold! A resizable main menu screen! Missing its buttons and not animated, but you know what, I’ll take what I can get for now! ^^ (Yes the border is annoying, I know. However, I realllly don’t want to stretch the images too horribly. I’ll make it look nice, I promise!)"}, {"post_id": 397, "ts": "2026-06-01T19:38:14Z", "hours": 0.2617, "text": "Finally managed to get VSCode to work with Love2d, holy cow that was. weirdly difficult. or maybe im slow lol"}]...
|
Title: MahouShoujo SakuraSan by @edda | Stardance
Title: MahouShoujo SakuraSan by @edda | Stardance
Devlogs:
Finally managed to get VSCode to work with Love2d, holy cow that was. weirdly difficult. or maybe im slow lol
So, originally, Mahou Shoujo Sakura San (As the full title is called) was being made for a different console than PC. However, I really wanted to get the game actually. working. And there were some annoying technical difficulties getting in the way! So, now I’m making a desktop port, and I just copied its files to a secondary location for whenever I want to continue with the console version. Then I realized, ah frick, if I’m going to make a desktop port, I now have to account for window sizing and generally changing up how it’s displayed, since the PC displays differently than the game’s original console. So I made a THIRD copy (albeit extremely stripped down, containing just the .vscode with the launch.json, all the image files, and an extremely barebones main.lua that basically just loads the files) and got to it. Lo and behold! A resizable main menu screen! Missing its buttons and not animated, but you know what, I’ll take what I can get for now! ^^ (Yes the border is annoying, I know. However, I realllly don’t want to stretch the images too horribly. I’ll make it look nice, I promise!)
Menu screen is more or less complete! This is still in the alternate file I made for modifications that lacks any actual interactibility, but once I get everything sorted, I’ll replace a lot of the code for the visuals in the main project folder with the stuff in here. Also, the menu animates now! Though, of course, you can’t see it in a screenshot lol
Finally finished the desktop integration stuff, and put it into the actual main file. It works! More or less- the platformer segment is a little broken, but that’s from the physics screwing up and not the new screen stuff. I plan on fixing it up next time, probably later on tonight or tomorrow, because I’ve been coding for a while already and am getting a bit tired lol Here’s a screenshot of the visual novel segment of the game (The textboxes are going to be slightly reworked, because right now they can’t fit much text at all.)
Fixed the dialogue boxes! Probably won’t get much done this upcoming week, though, I’m on vacationnnnn to the beachhhh~ yay! Fancy shmancy text wrapping for now, wow. I did a little bit on the platformer section, but the tilesets hate me right now I fear.
after like… forever… of trying to get this freaking map to scale properly… i finally got it. oh my gosh. it was literally one argument i had gotten wrong. literally ONE oh my gosh. end me /silly also ignore the fact the player is suctioned to the upper screen, i am sTILL trying to fix physics.
Lots of changes have happened since I last devlogged! I fixed the physics, added GUI, collectables, level hazards, changed the background (via prerendered models I made in Blockbench and then rendered in Blender), and extended the map and made it so the camera follows the player. Also, made it so collectables/level stuff spawn via placing them in Tiled instead of me just having to manually input coordinates. Next up, enemies and CPU follower! :D
Spent ages getting a typewriter effect working, and added some sfx, composed a song, and here we are :D we have the intro (the first dark bit) and then the test dialogue afterwards (yes, i know the choice boxes are super janky, that’s the next thing im fixing). and yeah our main character is super angsty and not very nice but she has her reasons i promise you normally you probably would not hear the whole song because that beginning blurb is pretty short, but it also plays later on
various screenshots :) most of the work i’ve done has been on the engine and artworks. these are a few screenshots (not in order) of the opening cutscene, and the main menu...
|
1792572563.9751484
|
1793177363.9751484
|
|
2248
|
My first slack bot! by @saisnithik | Stardance
|
saisnithik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @saisnithik | Starda Title: My first slack bot! by @saisnithik | Stardance...
|
1792738365.2763374
|
1793343165.2763374
|
|
2247
|
Untitled by @Vimthusiast | Stardance
|
Vimthusiast
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Vimthusiast | Stardance
|
1792601339.3848512
|
1793206139.3848512
|
|
2246
|
My first slack bot! by @Aline | Stardance
|
Aline
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Aline | Stardance
|
1793184942.834853
|
1793789742.834853
|
|
2245
|
My awesome macropad! by @Cozy | Stardance
|
Cozy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Cozy | Stardance
|
1792540220.6991897
|
1793145020.6991897
|
|
2244
|
My first slack bot! by @Joeryon2011 | Stardance
|
Joeryon2011
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Joeryon2011 | Stard Title: My first slack bot! by @Joeryon2011 | Stardance...
|
1793159577.0843964
|
1793764377.0843964
|
|
2243
|
Cardlogic by @Reena | Stardance
|
Reena
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cardlogic by @Reena | Stardance
|
1792788677.837713
|
1793393477.837713
|
|
2242
|
ATOM main hub by @projects311 | Stardance
|
projects311
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ATOM main hub by @projects311 | Stardance
|
1793181094.560212
|
1793785894.560212
|
|
2241
|
astroid for birthday by @nightfury6099 | Stardance
|
nightfury6099
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: astroid for birthday by @nightfury6099 | St Title: astroid for birthday by @nightfury6099 | Stardance...
|
1792558253.575757
|
1793163053.575757
|
|
2240
|
My first slack bot! by @bluecorexux | Stardance
|
bluecorexux
|
1
|
8.0
|
13
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-29T06:19:36Z", "hours": 8.0, "multiplier": 1.57, "payout": 13, "blessing": "neutral", "text": "This is my first JS project. I spent two weeks learning the language and built this. The challenging parts weren’t the Slack API — it was the stuff around it. Handling permission errors without crashing, figuring out that Gemini and OpenAI have completely different API formats, and setting up a Linux server to keep it running 24/7 after my laptop closes. To test it, install it to your workspace using the “Add to Slack” button in the README. Commands are limited for now so the README covers everything in under a minute. Start with /haaitzzabot-ping to check it is alive, then try /haaitzzabot-summarize", "repo": "https://github.com/bluecore7/haaitzzabot", "demo": "https://slack.com/oauth/v2/authorize?client_id=2210535565.11300283767236&scope=channels:join,app_mentions:read,channels:history,channels:read,chat:write,commands,groups:history,groups:read,im:read,mpim:read&user_scope="}]...
|
[{"post_id": 18168, "ts": "202 [{"post_id": 18168, "ts": "2026-06-29T06:06:58Z", "hours": 1.8003, "text": "Devlog 3 Built an OAuth server using Express so users can install the bot into their own Slack workspaces via an “Add to Slack” button. Got a shallow knowledge on how OAuth works and learnt how to build a express server to catch the code and proceed with OAuth Deployed it as a second systemd daemon on Hack Club’s server. Now both the bot and the OAuth server run 24/7 without my laptop being on."}, {"post_id": 17859, "ts": "2026-06-28T20:01:56Z", "hours": 1.2742, "text": "Devlog 2 Turns out one AI provider isn’t enough — so I added OpenAI support to the /summarize command via the -model flag. The interesting part wasn’t the API call itself. It was realising that Gemini and OpenAI have completely different request formats — different URLs, different auth methods, different JSON body structures. So I had to refactor the whole AI section: pulled the Gemini logic into its own askGemini() function, then built an askOpenAI() twin next to it. Also learned the hard way that OpenAI’s free tier doesn’t exist for developers. Got a clean 429 back . Finally SSHed into Hack Club’s server, set the bot up as a systemd service, and now it just… runs. 24/7."}, {"post_id": 15719, "ts": "2026-06-25T16:00:14Z", "hours": 5.3742, "text": "Dev Log 1 Joined Stardance at the start of June — now it’s about to end. Spent a month learning a language that took its developer 10 days to prototype! Finally shipped my first JS project: a Slack bot. Still a bash loyalist at heart, so I built a CLI parser (a minimal implementation) that lets users interact with the bot like a command-line tool. I’ve added a /summarize command to help me triage unread messages across Slack. It fetches the last n hours of messages ( -time flag) from a target channel (selectable via -channel flag), pipes them to the Gemini API, and lets users fine-tune the AI’s output with a custom -prompt flag. The dopamine hit of shipping this without blindly dumping AI-generated code was unmatched — the kind of serotonin you only get from debugging your own stack traces at 1 AM. And somewhere along the way, I learned to collaborate with the weirdo."}]...
|
Title: My first slack bot! by @bluecorexux | Stard Title: My first slack bot! by @bluecorexux | Stardance
Devlogs:
Dev Log 1 Joined Stardance at the start of June — now it’s about to end. Spent a month learning a language that took its developer 10 days to prototype! Finally shipped my first JS project: a Slack bot. Still a bash loyalist at heart, so I built a CLI parser (a minimal implementation) that lets users interact with the bot like a command-line tool. I’ve added a /summarize command to help me triage unread messages across Slack. It fetches the last n hours of messages ( -time flag) from a target channel (selectable via -channel flag), pipes them to the Gemini API, and lets users fine-tune the AI’s output with a custom -prompt flag. The dopamine hit of shipping this without blindly dumping AI-generated code was unmatched — the kind of serotonin you only get from debugging your own stack traces at 1 AM. And somewhere along the way, I learned to collaborate with the weirdo.
Devlog 2 Turns out one AI provider isn’t enough — so I added OpenAI support to the /summarize command via the -model flag. The interesting part wasn’t the API call itself. It was realising that Gemini and OpenAI have completely different request formats — different URLs, different auth methods, different JSON body structures. So I had to refactor the whole AI section: pulled the Gemini logic into its own askGemini() function, then built an askOpenAI() twin next to it. Also learned the hard way that OpenAI’s free tier doesn’t exist for developers. Got a clean 429 back . Finally SSHed into Hack Club’s server, set the bot up as a systemd service, and now it just… runs. 24/7.
Devlog 3 Built an OAuth server using Express so users can install the bot into their own Slack workspaces via an “Add to Slack” button. Got a shallow knowledge on how OAuth works and learnt how to build a express server to catch the code and proceed with OAuth Deployed it as a second systemd daemon on Hack Club’s server. Now both the bot and the OAuth server run 24/7 without my laptop being on.
Ships:
This is my first JS project. I spent two weeks learning the language and built this. The challenging parts weren’t the Slack API — it was the stuff around it. Handling permission errors without crashing, figuring out that Gemini and OpenAI have completely different API formats, and setting up a Linux server to keep it running 24/7 after my laptop closes. To test it, install it to your workspace using the “Add to Slack” button in the README. Commands are limited for now so the README covers everything in under a minute. Start with /haaitzzabot-ping to check it is alive, then try /haaitzzabot-summarize...
|
1793087672.4571328
|
1793174072.4571328
|
|
2239
|
vibeflo by @mobolajiajagunna | Stardance
|
mobolajiajagunna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: vibeflo by @mobolajiajagunna | Stardance
|
1792561692.2522602
|
1793166492.2522602
|
|
2238
|
My first slack bot! by @muntasirmahmud364 | Starda My first slack bot! by @muntasirmahmud364 | Stardance...
|
muntasirmahmud364
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @muntasirmahmud364 | Title: My first slack bot! by @muntasirmahmud364 | Stardance...
|
1792695260.9550474
|
1793300060.9550474
|
|
2237
|
My awesome macropad! by @saisnithik | Stardance
|
saisnithik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @saisnithik | Stard Title: My awesome macropad! by @saisnithik | Stardance...
|
1792748885.3649998
|
1793353685.3649998
|