|
34982
|
Frictionless by @zucc | Stardance
|
zucc
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @zucc | Stardance
|
1792724100.6418936
|
1793328900.6418936
|
|
58530
|
Astroza by @zubia_h | Stardance
|
zubia_h
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Astroza by @zubia_h | Stardance
|
1792756074.2665513
|
1793360874.2665513
|
|
63518
|
Virtual Lab by @zubair974 | Stardance
|
zubair974
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Virtual Lab by @zubair974 | Stardance
|
1792442966.800285
|
1793047766.800285
|
|
8767
|
First project by @zubair | Stardance
|
zubair
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: First project by @zubair | Stardance
|
1791823321.3885515
|
1792687321.3885515
|
|
10081
|
Color isolation tracking by @zubair | Stardance
|
zubair
|
0
|
0.29
|
0
|
[]
|
[{"post_id": 3727, "ts": "2026 [{"post_id": 3727, "ts": "2026-06-06T19:29:17Z", "hours": 0.2872, "text": "Added isolation for BLUE color"}]...
|
Title: Color isolation tracking by @zubair | Stard Title: Color isolation tracking by @zubair | Stardance
Devlogs:
Added isolation for BLUE color...
|
1791826810.6134198
|
1792690810.6134198
|
|
48320
|
ISS Waltz by @zubair | Stardance
|
zubair
|
1
|
3.0
|
36
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-16T16:17:15Z", "hours": 3.0, "multiplier": 10.86, "payout": 36, "blessing": "neutral", "text": "I made a website to track the ISS and show its position on a map.", "repo": "https://github.com/skzubairahmed/iss-waltz", "demo": "https://iss-waltz.vercel.app"}]...
|
[{"post_id": 48274, "ts": "202 [{"post_id": 48274, "ts": "2026-08-16T16:11:43Z", "hours": 1.4072, "text": "Completed the project - Added the live map feature(used leaflet for it)."}, {"post_id": 47658, "ts": "2026-08-15T18:15:14Z", "hours": 0.7064, "text": "Made the landing page - Added a landing page with a start button and an ISS animation."}, {"post_id": 47629, "ts": "2026-08-15T17:18:59Z", "hours": 1.2408, "text": "Added test routes - I started by adding test routes to check the position of the ISS and to find the coordinates of the desired city."}]...
|
Title: ISS Waltz by @zubair | Stardance
Devlogs:
Title: ISS Waltz by @zubair | Stardance
Devlogs:
Added test routes - I started by adding test routes to check the position of the ISS and to find the coordinates of the desired city.
Made the landing page - Added a landing page with a start button and an ISS animation.
Completed the project - Added the live map feature(used leaflet for it).
Ships:
I made a website to track the ISS and show its position on a map....
|
1792810532.6867926
|
1792896932.6867926
|
|
49959
|
ZBasic by @zubair | Stardance
|
zubair
|
0
|
0.99
|
0
|
[]
|
[{"post_id": 48702, "ts": "202 [{"post_id": 48702, "ts": "2026-08-17T06:43:17Z", "hours": 0.9917, "text": "Started with the lexer and some basic tokens."}]...
|
Title: ZBasic by @zubair | Stardance
Devlogs:
Sta Title: ZBasic by @zubair | Stardance
Devlogs:
Started with the lexer and some basic tokens....
|
1792612328.550008
|
1793217128.550008
|
|
50475
|
AeroBoard by @zubair | Stardance
|
zubair
|
1
|
12.4
|
158
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-25T16:34:17Z", "hours": 12.0, "multiplier": 12.81, "payout": 158, "blessing": "neutral", "text": "I made an OpenCV based, finger tracking digital whiteboard.", "repo": "https://github.com/skzubairahmed/aeroboard", "demo": "https://github.com/skzubairahmed/aeroboard/releases/tag/v0.1-alpha"}]...
|
[{"post_id": 55207, "ts": "202 [{"post_id": 55207, "ts": "2026-08-26T19:14:11Z", "hours": 0.4033, "text": "Converted the application to a windows application(.exe) using pyinstaller. Changelog e16d378 6ab1958 8e565aa b6590c9"}, {"post_id": 53927, "ts": "2026-08-24T17:03:47Z", "hours": 1.1917, "text": "FINISHED!! Firstly here’s what i used: tracking - mediapipe(through cvzone) gestures - own class drawing - using cv2.line MORE DEATILS IN THE README"}, {"post_id": 53320, "ts": "2026-08-23T19:54:24Z", "hours": 3.5608, "text": "BIG UPDATES!! Added a color menu for selecting between Red, Green and Blue and a button to clear the screen. I made my own AirButtons class for the buttons. Next Up: Using dqeues to draw. Changelog 96c0761 84f8bd5 Changelog f1ba61e 96c0761 84f8bd5"}, {"post_id": 52561, "ts": "2026-08-22T18:54:00Z", "hours": 2.6561, "text": "ADDED TRACKING AND FILTERING So I added the finger tracking using mediapipe(through cvzone) and also added a Kalman filter to remove micro jitters in the finger tracking. Changelog f07975c a14c5f1"}, {"post_id": 51896, "ts": "2026-08-21T19:56:07Z", "hours": 1.8303, "text": "I tested a freeze and restart feature where the webcam can be freezed if its unplugged mid-use and then the program restarts if any other video in is plugged in/available (I have not added it to the main class, just tested it on a test file, will add it to the main file tomorrow :> ) Changelog aa8d61f Changelog aa8d61f"}, {"post_id": 49189, "ts": "2026-08-17T20:35:25Z", "hours": 0.7961, "text": "Tried adding hand processing. I tried to add hand processing using mediapipe but ran into a version conflict, its late tonight so I’ll fix it tomorrow. Changelog 40768b3 f353b08"}, {"post_id": 49124, "ts": "2026-08-17T19:16:26Z", "hours": 2.3122, "text": "Made the basic functions for getting frames and showing the original video feed"}]...
|
Title: AeroBoard by @zubair | Stardance
Devlogs:
Title: AeroBoard by @zubair | Stardance
Devlogs:
Made the basic functions for getting frames and showing the original video feed
Tried adding hand processing. I tried to add hand processing using mediapipe but ran into a version conflict, its late tonight so I’ll fix it tomorrow. Changelog 40768b3 f353b08
I tested a freeze and restart feature where the webcam can be freezed if its unplugged mid-use and then the program restarts if any other video in is plugged in/available (I have not added it to the main class, just tested it on a test file, will add it to the main file tomorrow :> ) Changelog aa8d61f Changelog aa8d61f
ADDED TRACKING AND FILTERING So I added the finger tracking using mediapipe(through cvzone) and also added a Kalman filter to remove micro jitters in the finger tracking. Changelog f07975c a14c5f1
BIG UPDATES!! Added a color menu for selecting between Red, Green and Blue and a button to clear the screen. I made my own AirButtons class for the buttons. Next Up: Using dqeues to draw. Changelog 96c0761 84f8bd5 Changelog f1ba61e 96c0761 84f8bd5
FINISHED!! Firstly here’s what i used: tracking - mediapipe(through cvzone) gestures - own class drawing - using cv2.line MORE DEATILS IN THE README
Converted the application to a windows application(.exe) using pyinstaller. Changelog e16d378 6ab1958 8e565aa b6590c9
Ships:
I made an OpenCV based, finger tracking digital whiteboard....
|
1792849711.242084
|
1792936111.242084
|
|
54370
|
rezistor by @zubair | Stardance
|
zubair
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: rezistor by @zubair | Stardance
|
1792788511.1214545
|
1793393311.1214545
|
|
54797
|
AstroDex by @zubair | Stardance
|
zubair
|
0
|
13.26
|
0
|
[]
|
[{"post_id": 59897, "ts": "202 [{"post_id": 59897, "ts": "2026-09-01T22:11:02Z", "hours": 1.8028, "text": "Updates I did today:- Added support for images to the APOD preview box in home page. Added a “View” button in asteroids table to view more information about an asteroid. Changelog b9bf08e"}, {"post_id": 59193, "ts": "2026-08-31T20:55:37Z", "hours": 0.2925, "text": "A small update:- Added video support to apod page Today I opened the website and realised the website was not displaying the RST launch video as I had only added support for images, so now both videos and images can be displayed. Changelog 7946405"}, {"post_id": 58410, "ts": "2026-08-30T20:24:43Z", "hours": 1.1089, "text": "Here’s what I added this time:- -Users are now able to bookmark asteroids -Users can remove bookmarked asteroids both one at a time, or the user could clear the bookmarks in the main page, I used localStorage to save the bookmarks. Changelog 74658af"}, {"post_id": 58101, "ts": "2026-08-30T13:35:40Z", "hours": 2.4322, "text": "Here’s what I added: Completed the asteroids page. Propagated the database with asteroid data Added a sync state to keep track of the data Added a paginated table to view basic information about the asteroids in the asteroids page. Changelog 218492f 652db07"}, {"post_id": 57651, "ts": "2026-08-29T21:15:44Z", "hours": 3.1061, "text": "Here’s what I did today:- Configured a MongoDB database and added a route to update the database with the NASA Astronomy Picture Of The Day. Added a route to get latest APOD data from the database. Added server-side caching(next-cache) to the apod route to save compute on Edge functions and to save NASA OpenAPI limits. I’ll update the apod data using vercel cron jobs. Finished the APOD page on the website. (And finally I realized that the devlogs are markdown-based, so now I’ll make better devlogs) Thank you :))"}, {"post_id": 56790, "ts": "2026-08-28T18:22:04Z", "hours": 2.1769, "text": "Added a bookmarks card which loads bookmarked items from session-storage, also added a card containing a preview of the NASA-APOD. Added responsiveness. Changelog 459b3b9"}, {"post_id": 56198, "ts": "2026-08-27T20:59:43Z", "hours": 1.8597, "text": "Added custom color themes. Added many new pages. Added responsive sidebar(for normal screens) and bottom bar(for phones/tablets). Changelog 88096b7 24e3994 952566a"}, {"post_id": 55584, "ts": "2026-08-27T15:06:38Z", "hours": 0.4775, "text": "Started working on the navbar. Changelog c7bfb0c 5ba4695 1c4347e ad67b49 f5be447 ad0bb6b ac574c5"}]...
|
Title: AstroDex by @zubair | Stardance
Devlogs:
S Title: AstroDex by @zubair | Stardance
Devlogs:
Started working on the navbar. Changelog c7bfb0c 5ba4695 1c4347e ad67b49 f5be447 ad0bb6b ac574c5
Added custom color themes. Added many new pages. Added responsive sidebar(for normal screens) and bottom bar(for phones/tablets). Changelog 88096b7 24e3994 952566a
Added a bookmarks card which loads bookmarked items from session-storage, also added a card containing a preview of the NASA-APOD. Added responsiveness. Changelog 459b3b9
Here’s what I did today:- Configured a MongoDB database and added a route to update the database with the NASA Astronomy Picture Of The Day. Added a route to get latest APOD data from the database. Added server-side caching(next-cache) to the apod route to save compute on Edge functions and to save NASA OpenAPI limits. I’ll update the apod data using vercel cron jobs. Finished the APOD page on the website. (And finally I realized that the devlogs are markdown-based, so now I’ll make better devlogs) Thank you :))
Here’s what I added: Completed the asteroids page. Propagated the database with asteroid data Added a sync state to keep track of the data Added a paginated table to view basic information about the asteroids in the asteroids page. Changelog 218492f 652db07
Here’s what I added this time:- -Users are now able to bookmark asteroids -Users can remove bookmarked asteroids both one at a time, or the user could clear the bookmarks in the main page, I used localStorage to save the bookmarks. Changelog 74658af
A small update:- Added video support to apod page Today I opened the website and realised the website was not displaying the RST launch video as I had only added support for images, so now both videos and images can be displayed. Changelog 7946405
Updates I did today:- Added support for images to the APOD preview box in home page. Added a “View” button in asteroids table to view more information about an asteroid. Changelog b9bf08e...
|
1792803238.3810167
|
1793408038.3810167
|
|
63291
|
My awesome macropad! by @ztexas_zoey | Stardance
|
ztexas_zoey
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ztexas_zoey | Star Title: My awesome macropad! by @ztexas_zoey | Stardance...
|
1792439692.9978795
|
1793044492.9978795
|
|
27034
|
My very own WebOS by @zsolt_csott | Stardance
|
zsolt_csott
|
0
|
0.45
|
0
|
[]
|
[{"post_id": 21394, "ts": "202 [{"post_id": 21394, "ts": "2026-07-03T09:40:58Z", "hours": 0.4456, "text": "Adding styles to my div"}]...
|
Title: My very own WebOS by @zsolt_csott | Stardan Title: My very own WebOS by @zsolt_csott | Stardance
Devlogs:
Adding styles to my div...
|
1792579821.9402065
|
1793184621.9402065
|
|
2179
|
TeleReader by @zsobix | Stardance
|
zsobix
|
1
|
35.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-14T22:33:48Z", "hours": 35.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Hey, this is TeleReader! A desktop teletext reader! The main inspiration for this project was me watching retro tv documentaries, the Stardance emails, and my last project: “Lidl Plus on desktop” (a desktop implementation of the Lidl Plus loyalty app) I wrote this project in Python, and the GUI with GTK and libadwaita. I tested this on a VM, with a live install of Manjaro linux. The most challenging thing was actually implementing the different teletext services and working around their (sometimes existing) apis. I’m proud of how it turned out, I made some improvements with the UI at the end, so I’m anxious to find out what you think about it!", "repo": "https://github.com/zsobix/teletext", "demo": "https://github.com/zsobix/teletext/releases/latest"}]...
|
[{"post_id": 28578, "ts": "202 [{"post_id": 28578, "ts": "2026-07-14T22:21:06Z", "hours": 2.9003, "text": "Day 14 Today I made some pretty good progress! New features: finally finished the favorites tab bugfixes easter egg……. Everything was pretty easy to implement, maybe the favorites tab was harder than I imagined (I had to let go of the popup message when you add a favorite ) There were ALOT of bugs to fix, like code snippets appearing multiple times, and straight up not functioning code. I also added an easter egg…. try out my app to find out! This is the last devlog before shipping, I tested everything on a live install of manjaro… so there shouldn’t be any issues. (im tiredddd) Changelog feat: add favorites page, bugfixes, and ??? ( 31409b6 ) fix: typo in action ( 6d8d395 ) fix: update action ( 511da3b ) thanks for coming to my final ted talk before the ship! -zsobix"}, {"post_id": 27976, "ts": "2026-07-13T22:46:54Z", "hours": 2.0728, "text": "Day 13!! Wow, i didn’t expect to make this much progress today!!!!! New features: HRT Teletekst (croatian public broadcaster) support Favorites tab (not finished) bug fixes The hardest thing to implement wasn’t even the HRT Teletext support, it was the (still broken) favorites tab! Atleast the favorites tab looks nice (i think) Implementing the teletext service was easy because (you know it) there is an actual api!!!!!!!!!!!!!!!!!!!!!!!!!!!! I didn’t get to ship today because I didn’t get to add all the features I wanted to add. (i want to sleeeeeeeep ) So, features before shipping: more teletext services bugfixes despagettifying my code (almost typed coke) finishing the favorites page thanks for coming to my ted talk -zsobix"}, {"post_id": 27394, "ts": "2026-07-12T22:33:50Z", "hours": 1.7044, "text": "Day 12 Today was better in terms of progress, but I hadn’t had enough freetime… New features: NOS Teletekst (dutch public broadcaster) support info button bugfixes Implementing NOS Teletekst was VERY HARD, because they give the teletext pages in html, so I have to basically copy the german teletext implementation, but not fully because the api response only has partial html, without any styling, so I have to copy the styling from the official website, then combine it with the api response. Other than that, everything went pretty well, even the info page, and yknow why? I read the f**king docs!!!!!!!! (it’s currently midnight as of writing this and my brain isn’t functioning.) I’ll probably ship tomorrow, because I gave up on waiting, and also I hit 30 hours!!!! So, the last minute features I want to implement: add favorites page bugfixes add some more teletext services Changelog chore: update readme ( f85a191 ) feat: add nos teletekst support + about button ( 11fdea9 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 26778, "ts": "2026-07-11T19:27:05Z", "hours": 1.5383, "text": "Day 11 Today also I couldn’t do much so this devlog will be short. New features: TVP Teletext (polish public broadcaster) support BHRT Teletext (bosnian public broadcaster) support bugfixes The most annoying thing I had to do was implementing the bosnian teletext, mostly because, there wasn’t a normal api!!!! So getting the number of subpages, and the next/previous page was pretty hard! Other then that, implementing the polish teletext was actually, well not pretty easy, but not that hard, because you know why…. there was an actual normal working api!!!!!! Well the not easy part was that, the api was just a json file, and a not very good one at that, so implementing the next/previous page functions were not trivial. New features I still want to add: moaar teletext services support bugfixes I gave up on waiting for the weekly shipping stickers, so I’ll probably ship when I get home. (birbs are chirping around me as of writing this ) thanks for coming to my ted talk -zsobix"}, {"post_id": 26172, "ts": "2026-07-10T20:25:44Z", "hours": 0.9139, "text": "Day 10! Today was VERY slow, because I’m currently on a trip and don’t have much time. So, new features: RBB teletext (german regional broadcaster) support MDR teletext (german regional broadcaster) support Teletexto TVE (spanish public broadcaster) support bugfixes The first two teletext services were easy to implement, because I already implemented their API! Teletexto TVE support was also easy to implement mostly because, their html files were readable! (they didn’t even have an api) So yeah, I don’t have much things to say. I still want to add: moar teletext services support (like for poland, netherlands, portugal) bugfixes Changelog my stardance extension broke anyways, thanks for coming to my ted talk -zsobix"}, {"post_id": 25586, "ts": "2026-07-09T22:43:42Z", "hours": 3.0439, "text": "Day 9!! Today I made waaay better progress then the last two days! So recap (new features): KiKa Teletext (german childrens channel) support DR Tekst-TV (Danish public broadcaster) support Arte Teletext (german/french public broadcaster) support ARD Text (german public broadcasting group) support some ui changes in the sidebar bug fixes (there are always some) The most major issue I had was that the DR teletext page doesn’t give the amount of subpages! So I had to rework the SAT.1 system for it to work. Also, because I put all stations in the sidebar, I had to (by hand) name every button, add station switching logic and also make the sidebar scrollable. This weekend, progress will be slower because I will be away from home and I also need suggestions to what to do next…. (I will not be shipping until there is no shipping sticker!!!) I will probably add: an info button (just because) more teletext services easter eggs (mmm eggs) not in the first ship, but I was thinking about implementing an ACTUAL teletext simulator Changelog feat: add dr, kika, ard, and arte support + ui changes ( d3acca6 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 24967, "ts": "2026-07-08T21:09:42Z", "hours": 2.0847, "text": "Day 8!!!!! Today was also a slower day, because I had less time and less ideas, but I have some ideas now! New features: ProSiebenSAT.1 Teletext (german broadcaster) support umm bug fixes Working with the SAT.1 teletext was actually pretty easy, before I realized I had to get the number of subpages on each page! I spent an hour figuring it out, in the end I have to interate over all the next subpages to get the max number of subpages. Anyways I have some new ideas!! So before shipping, I will add: KiKa Teletext (german childrens channel) support (why does a children’s channel have teletext????? especially in 2026???) DR Tekst-TV (Danish public broadcaster) support Arte Teletext (german/french public broadcaster) support ARD(1) Text (german public broadcasting group) support Put all countries/stations in the sidebar with a Gtk.ScrolledWindow (shown in picture) moar bugfixes Changelog feat: add prosiebensat.1 teletext support ( 4226ff0 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 24355, "ts": "2026-07-07T21:18:14Z", "hours": 2.5864, "text": "Day 7! First week complete! Today was a slower day, with not much progress, but I added yle Teksti-TV support. New features: YLE Teksti-TV (Finnish national public broadcaster) support BUG FIXES (there were alot) some UI tweaks testing the biggest problem I faced was, that the yle teletext api was hidden, and I had to search for it. I thought that all the data was on the frontfacing page itself but I was wrong. I don’t have much to say because everything went pretty well. (sidenote: the hungarian public broadcaster is undergoing MAJOR changes, and I don’t think the teletext service will survive the next 3 months ) Changelog feat: add yle finland teletext support ( b290c1c ) thanks for coming to my ted talk -zsobix"}, {"post_id": 23721, "ts": "2026-07-06T20:41:59Z", "hours": 3.9725, "text": "Day 6! Finally added packaging support, also added 3 other teletext services! I could add THREE more teletext services, because they had functional apis!!!! New features: ČT Text (Czech public broadcaster) support SRF Text (Swiss public broadcaster) support SVT Text (Swedish public broadcaster) support Some UI fixes more bugfixes the biggest problem I faced was that the ČT teletext subpages are marked with LETTERS instead of NUMBERS, which makes things (very) HARD. Other than that, everything went pretty well, even the packaging went well, because I (basically) just copied the packaging structure from my older project Lidl Plus on desktop . I made huge progress today, and either tomorrow or when I can get stickers, I will probably ship! Remaining features: despagettifying my code adding more teletext providers some more UI fixes and bugfixes Changelog fix: forgor to add a dot 💀 ( f919029 ) feat: added packaging support, and 3 other teletext services ( 6278dc6 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 23113, "ts": "2026-07-05T21:22:48Z", "hours": 3.61, "text": "Another day, another devlog!! Finally added Rai Televideo support… I did NOT enjoy this, mostly because Rai’s servers are 1 millenium old Sun workstations, and they take a bajillion years to load, and also there is no next page anything, so I have to iterate over all next pages to find the next page. New features: Rai Televideo (Italian public broadcaster) support Rai Televideo regions support Bug fixes My first problem with Rai Televideo was, as I mentioned, the waiting times are UNBEARABLE, so if more than 2 people connect to their servers, they crawl down to a halt. Other problem is that there are REGIONS of Televideo, meaning I had to add a dropdown to select between the regions, which seems pretty easy, right? To be fair, it was pretty easy but I had so many bugs with it, and combined with the wait times, it was a pain. Only good thing about Televideo, is that the teletext pages are images, so I don’t need a browser to render them. (also there are ADS on the non-existing pages so finding real pages is a pain) The things I still want to add is: More Teletext providers support UI Improvements despagettifying my code preparing it to package and also there are alot of unnoticed bugs I need to fix Changelog 5bf2423 thanks for coming to my ted talk -zsobix"}, {"post_id": 22422, "ts": "2026-07-04T21:39:23Z", "hours": 4.1544, "text": "4th Devlog!!! Another long day complete, today’s coding session was 4 hours, which is great! New features: ZDF Text (german public broadcaster) support Sidebar to switch between countries Bottom button bar to switch between stations Fixed some bugs Figuring out ZDF Text was VERY painful, and I WOULD NOT RECOMMEND any sane person to work with that garbage. Working with MTVA Text and their 2012 website was easier than this. Me finally finding the libadwaita docs, and reading through them, I found the geniusly called AdwNavigationSplitView (the sidebar). The main problem with ZDF Text was, that, the teletext pages were in HTML!! which are NOT IMAGES, so I had to use WebKitGTK to render the HTML pages, which makes the whole thing WAAYYYY slower. Changelog 82a66ba thanks for coming to my ted talk -zsobix"}, {"post_id": 21775, "ts": "2026-07-03T21:36:07Z", "hours": 2.7944, "text": "Third devlog!!!!! It’s late at night currently so I can’t write much, but this is what I worked on. ORF (Austrian public broadcaster) Text support MTVA Text (Hungarian public broadcaster) colored buttons support (a bit borked still) Working with websites that don’t have actual api, is, tiring, but i still got it. The only things I want to still work on is: more public broadcaster support (like for Italy and Germany) better looking interface Also, I found the adwaita documentation! (I did not know this existed) Changelog 92a449b thanks for coming to my ted talk -zsobix"}, {"post_id": 20977, "ts": "2026-07-02T18:32:03Z", "hours": 2.0036, "text": "First (normal) devlog, actually second Hey there! I have been working on some things. Firstly, I added basic functionality, like actually viewing teletext pages and navigation. The readme, is, bad. That is something I have to fix. To actually get the teletext pages, i have to scrape this archaic website, which doesn’t even have an api, i had to get the first (DOT HTM!!!!) page then with BeautifulSoup4 get the hidden input tags that had the next and the previous page ids (????), which is peak 2012 development. I still have to make it look prettier and add other teletext services, because now, it still looks barren. Changelog 74da49f thanks for coming to my ted talk -zsobix"}, {"post_id": 20059, "ts": "2026-07-01T15:50:09Z", "hours": 1.6142, "text": "I cannot press enter, so I can’t use markdown very much. Anyways, this is my random project, Teletext on Desktop. It’s literally in the name, it’s (going to be) the Hungarian teletext service (like Ceefax was in the UK) on desktop! I’m currently working on the basics, like deciphering this 2012 website to get the teletext pages, and making a GTK window."}]...
|
Title: TeleReader by @zsobix | Stardance
Devlogs: Title: TeleReader by @zsobix | Stardance
Devlogs:
I cannot press enter, so I can’t use markdown very much. Anyways, this is my random project, Teletext on Desktop. It’s literally in the name, it’s (going to be) the Hungarian teletext service (like Ceefax was in the UK) on desktop! I’m currently working on the basics, like deciphering this 2012 website to get the teletext pages, and making a GTK window.
First (normal) devlog, actually second Hey there! I have been working on some things. Firstly, I added basic functionality, like actually viewing teletext pages and navigation. The readme, is, bad. That is something I have to fix. To actually get the teletext pages, i have to scrape this archaic website, which doesn’t even have an api, i had to get the first (DOT HTM!!!!) page then with BeautifulSoup4 get the hidden input tags that had the next and the previous page ids (????), which is peak 2012 development. I still have to make it look prettier and add other teletext services, because now, it still looks barren. Changelog 74da49f thanks for coming to my ted talk -zsobix
Third devlog!!!!! It’s late at night currently so I can’t write much, but this is what I worked on. ORF (Austrian public broadcaster) Text support MTVA Text (Hungarian public broadcaster) colored buttons support (a bit borked still) Working with websites that don’t have actual api, is, tiring, but i still got it. The only things I want to still work on is: more public broadcaster support (like for Italy and Germany) better looking interface Also, I found the adwaita documentation! (I did not know this existed) Changelog 92a449b thanks for coming to my ted talk -zsobix
4th Devlog!!! Another long day complete, today’s coding session was 4 hours, which is great! New features: ZDF Text (german public broadcaster) support Sidebar to switch between countries Bottom button bar to switch between stations Fixed some bugs Figuring out ZDF Text was VERY painful, and I WOULD NOT RECOMMEND any sane person to work with that garbage. Working with MTVA Text and their 2012 website was easier than this. Me finally finding the libadwaita docs, and reading through them, I found the geniusly called AdwNavigationSplitView (the sidebar). The main problem with ZDF Text was, that, the teletext pages were in HTML!! which are NOT IMAGES, so I had to use WebKitGTK to render the HTML pages, which makes the whole thing WAAYYYY slower. Changelog 82a66ba thanks for coming to my ted talk -zsobix
Another day, another devlog!! Finally added Rai Televideo support… I did NOT enjoy this, mostly because Rai’s servers are 1 millenium old Sun workstations, and they take a bajillion years to load, and also there is no next page anything, so I have to iterate over all next pages to find the next page. New features: Rai Televideo (Italian public broadcaster) support Rai Televideo regions support Bug fixes My first problem with Rai Televideo was, as I mentioned, the waiting times are UNBEARABLE, so if more than 2 people connect to their servers, they crawl down to a halt. Other problem is that there are REGIONS of Televideo, meaning I had to add a dropdown to select between the regions, which seems pretty easy, right? To be fair, it was pretty easy but I had so many bugs with it, and combined with the wait times, it was a pain. Only good thing about Televideo, is that the teletext pages are images, so I don’t need a browser to render them. (also there are ADS on the non-existing pages so finding real pages is a pain) The things I still want to add is: More Teletext providers support UI Improvements despagettifying my code preparing it to package and also there are alot of unnoticed bugs I need to fix Changelog 5bf2423 thanks for coming to my ted talk -zsobix
Day 6! Finally added packaging support, also added 3 other teletext services! I could add THREE more teletext services, because they had functional apis!!!! New features: ČT Text (Czech public broadcaster) support SRF Text (Swiss public broadcaster) support SVT Text (Swedish public broadcaster) support Some UI fixes more bugfixes the biggest problem I faced was that the ČT teletext subpages are marked with LETTERS instead of NUMBERS, which makes things (very) HARD. Other than that, everything went pretty well, even the packaging went well, because I (basically) just copied the packaging structure from my older project Lidl Plus on desktop . I made huge progress today, and either tomorrow or when I can get stickers, I will probably ship! Remaining features: despagettifying my code adding more teletext providers some more UI fixes and bugfixes Changelog fix: forgor to add a dot 💀 ( f919029 ) feat: added packaging support, and 3 other teletext services ( 6278dc6 ) thanks for coming to my ted talk -zsobix
Day 7! First week complete! Today was a slower day, with not much progress, but I added yle Teksti-TV support. New features: YLE Teksti-TV (Finnish national public broadcaster) support BUG FIXES (there were alot) some UI tweaks testing the biggest problem I faced was, that the yle teletext api was hidden, and I had to search for it. I thought that all the data was on the frontfacing page itself but I was wrong. I don’t have much to say because everything went pretty well. (sidenote: the hungarian public broadcaster is undergoing MAJOR changes, and I don’t think the teletext service will survive the next 3 months ) Changelog feat: add yle finland teletext support ( b290c1c ) thanks for coming to my ted talk -zsobix
Day 8!!!!! Today was also a slower day, because I had less time and less ideas, but I have some ideas now! New features: ProSiebenSAT.1 Teletext (german broadcaster) support umm bug fixes Working with the SAT.1 teletext was actually pretty easy, before I realized I had to get the number of subpages on each page! I spent an hour figuring it out, in the end I have to interate over all the next subpages to get the max number of subpages. Anyways I have some new ideas!! So before shipping, I will add: KiKa Teletext (german childrens channel) support (why does a children’s channel have teletext????? especially in 2026???) DR Tekst-TV (Danish public broadcaster) support Arte Teletext (german/french public broadcaster) support ARD(1) Text (german public broadcasting group) support Put all countries/stations in the sidebar with a Gtk.ScrolledWindow (shown in picture) moar bugfixes Changelog feat: add prosiebensat.1 teletext support ( 4226ff0 ) thanks for coming to my ted talk -zsobix
Day 9!! Today I made waaay better progress then the last two days! So recap (new features): KiKa Teletext (german childrens channel) support DR Tekst-TV (Danish public broadcaster) support Arte Teletext (german/french public broadcaster) support ARD Text (german public broadcasting group) support some ui changes in the sidebar bug fixes (there are always some) The most major issue I had was that the DR teletext page doesn’t give the amount of subpages! So I had to rework the SAT.1 system for it to work. Also, because I put all stations in the sidebar, I had to (by hand) name every button, add station switching logic and also make the sidebar scrollable. This weekend, progress will be slower because I will be away from home and I also need suggestions to what to do next…. (I will not be shipping until there is no shipping sticker!!!) I will probably add: an info button (just because) more teletext services easter eggs (mmm eggs) not in the first ship, but I was thinking about implementing an ACTUAL teletext simulator Changelog feat: add dr, kika, ard, and arte support + ui changes ( d3acca6 ) thanks for coming to my ted talk -zsobix
Day 10! Today was VERY slow, because I’m currently on a trip and don’t have much time. So, new features: RBB teletext (german regional broadcaster) support MDR teletext (german regional broadcaster) support Teletexto TVE (spanish public broadcaster) support bugfixes The first two teletext services were easy to implement, because I already implemented their API! Teletexto TVE support was also easy to implement mostly because, their html files were readable! (they didn’t even have an api) So yeah, I don’t have much things to say. I still want to add: moar teletext services support (like for poland, netherlands, portugal) bugfixes Changelog my stardance extension broke anyways, thanks for coming to my ted talk -zsobix
Day 11 Today also I couldn’t do much so this devlog will be short. New features: TVP Teletext (polish public broadcaster) support BHRT Teletext (bosnian public broadcaster) support bugfixes The most annoying thing I had to do was implementing the bosnian teletext, mostly because, there wasn’t a normal api!!!! So getting the number of subpages, and the next/previous page was pretty hard! Other then that, implementing the polish teletext was actually, well not pretty easy, but not that hard, because you know why…. there was an actual normal working api!!!!!! Well the not easy part was that, the api was just a json file, and a not very good one at that, so implementing the next/previous page functions were not trivial. New features I still want to add: moaar teletext services support bugfixes I gave up on waiting for the weekly shipping stickers, so I’ll probably ship when I get home. (birbs are chirping around me as of writing this ) thanks for coming to my ted talk -zsobix
Day 12 Today was better in terms of progress, but I hadn’t had enough freetime… New features: NOS Teletekst (dutch public broadcaster) support info button bugfixes Implementing NOS Teletekst was VERY HARD, because they give the teletext pages in html, so I have to basically copy the german teletext implementation, but not fully because the api response only has partial html, without any styling, so I have to copy the styling from the official website, then combine it with the api response. Other than that, everything went pretty well, even the info page, and yknow why? I read the f**king docs!!!!!!!! (it’s currently midnight as of writing this and my brain isn’t functioning.) I’ll probably ship tomorrow, because I gave up on waiting, and also I hit 30 hours!!!! So, the last minute features I want to implement: add favorites page bugfixes add some more teletext services Changelog chore: update readme ( f85a191 ) feat: add nos teletekst support + about button ( 11fdea9 ) thanks for coming to my ted talk -zsobix
Day 13!! Wow, i didn’t expect to make this much progress today!!!!! New features: HRT Teletekst (croatian public broadcaster) support Favorites tab (not finished) bug fixes The hardest thing to implement wasn’t even the HRT Teletext support, it was the (still broken) favorites tab! Atleast the favorites tab looks nice (i think) Implementing the teletext service was easy because (you know it) there is an actual api!!!!!!!!!!!!!!!!!!!!!!!!!!!! I didn’t get to ship today because I didn’t get to add all the features I wanted to add. (i want to sleeeeeeeep ) So, features before shipping: more teletext services bugfixes despagettifying my code (almost typed coke) finishing the favorites page thanks for coming to my ted talk -zsobix
Day 14 Today I made some pretty good progress! New features: finally finished the favorites tab bugfixes easter egg……. Everything was pretty easy to implement, maybe the favorites tab was harder than I imagined (I had to let go of the popup message when you add a favorite ) There were ALOT of bugs to fix, like code snippets appearing multiple times, and straight up not functioning code. I also added an easter egg…. try out my app to find out! This is the last devlog before shipping, I tested everything on a live install of manjaro… so there shouldn’t be any issues. (im tiredddd) Changelog feat: add favorites page, bugfixes, and ??? ( 31409b6 ) fix: typo in action ( 6d8d395 ) fix: update action ( 511da3b ) thanks for coming to my final ted talk before the ship! -zsobix
Ships:
Hey, this is TeleReader! A desktop teletext reader! The main inspiration for this project was me watching retro tv documentaries, the Stardance emails, and my last project: “Lidl Plus on desktop” (a desktop implementation of the Lidl Plus loyalty app) I wrote this project in Python, and the GUI with GTK and libadwaita. I tested this on a VM, with a live install of Manjaro linux. The most challenging thing was actually implementing the different teletext services and working around their (sometimes existing) apis. I’m proud of how it turned out, I made some improvements with the UI at the end, so I’m anxious to find out what you think about it!...
|
1792828572.8804038
|
1792914972.8804038
|
|
35791
|
zsobix's personal website! by @zsobix | Starda zsobix's personal website! by @zsobix | Stardance...
|
zsobix
|
0
|
3.37
|
0
|
[]
|
[{"post_id": 29441, "ts": "202 [{"post_id": 29441, "ts": "2026-07-16T11:59:17Z", "hours": 2.4289, "text": "First normal and last devlog before the (first) ship! Since my project isn’t going to be rated, and I will only get 10 stardust (for the first ship), I’m not wasting time that could be stardust. Today, I added the basics like: Projects I’m currently working on Basic styling Contact details So yeah, after this ship, I’ll add more stuff. Changelog fix: font pointing to wrong website ( b09e544 ) feat: remade website in a swiss style ( bd61b70 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 29184, "ts": "2026-07-15T22:19:34Z", "hours": 0.9422, "text": "Hey, this is my new website! I’m currently thinking about making it with a Swiss Style. Today I did some research and made just the basics, like adding the font and some spacing!"}]...
|
Title: zsobix's personal website! by @zsobix | Title: zsobix's personal website! by @zsobix | Stardance
Devlogs:
Hey, this is my new website! I’m currently thinking about making it with a Swiss Style. Today I did some research and made just the basics, like adding the font and some spacing!
First normal and last devlog before the (first) ship! Since my project isn’t going to be rated, and I will only get 10 stardust (for the first ship), I’m not wasting time that could be stardust. Today, I added the basics like: Projects I’m currently working on Basic styling Contact details So yeah, after this ship, I’ll add more stuff. Changelog fix: font pointing to wrong website ( b09e544 ) feat: remade website in a swiss style ( bd61b70 ) thanks for coming to my ted talk -zsobix...
|
1792709266.2492418
|
1793314066.2492418
|
|
36547
|
StarScraper by @zsobix | Stardance
|
zsobix
|
0
|
19.03
|
0
|
[]
|
[{"post_id": 33185, "ts": "202 [{"post_id": 33185, "ts": "2026-07-22T21:12:50Z", "hours": 0.4289, "text": "Last minute adjustments So today, I didn’t have much ideas for other projects, so I made some UI tweaks before shipping! And also! I added a new primary color for the light mode! (test my project to find out ) Changelog feat: ui tweaks ( d65d893 ) thanks for coming to my short ted talk -zsobix"}, {"post_id": 32661, "ts": "2026-07-21T23:13:29Z", "hours": 1.5214, "text": "I think this will be the last devlog before shipping I finally added theming!!!! Now, you can burn out your retina at night, with the new light mode! Also, I added customizable outline colors! (not for the light mode, just because there isn’t a color that looks nice with #FFFFFF) This was pretty easy, as I had everything pretty much set up, just needed to add some buttons, and js. (do not look at my js ) Honestly, that is all, I do not have much to say, as there aren’t any bugs, and (i think) it’s ready to ship! Changelog feat: add theming settings ( a44437c ) thanks for coming to my ted talk -zsobix"}, {"post_id": 32052, "ts": "2026-07-20T22:52:16Z", "hours": 1.2067, "text": "I lied… 4th devlog, and more to come! Today was a shorter day, not because i didn’t have time, but because I procrastinated until 10 pm So today, I added: a settings menu, to change search engines! also I fixed a bug with the weather widget Believing in my project, i set it as my new tab, and then I noticed a bug. Specifically, that the geolocation timeout was set to 5 seconds, and it wasn’t showing the error. This was easily fixed, by me adding a zero to the end of the timeout, and showing the GIVEN error message instead of some arbitrary bullshit. Now, the settings took the longest, but it wasn’t so bad! I just had to change the search bar to grab the query string from localstorage, and set a new query url to localstorage when changed in the settings menu! I am planning to finish by adding more options to the settings menu, like custom theme options, hide widgets, and reset all changes button! (also thanks to @water for the words of encouragement!) Changelog feat: add search settings, fix: geolocation timeout now set to 1 minute to not cause errors ( 7c1b9ca ) thanks for coming to my ted talk -zsobix"}, {"post_id": 31499, "ts": "2026-07-19T22:55:16Z", "hours": 5.1728, "text": "Last devlog before ship (i still have to rate 10 times ) I finally finished!!!!! After 14 hours for a project that was supposed to take 3 hours, i finally finished!! So today, i added: Weather info (with the Open-Meteo API) trash buttons for the favorites Your Stardance info (with @jam06452 ’s Stardance API) Honestly, the hardest thing today was working with javascript , especially with the fetch api (now i hate async functions AND js!!!!) Other than that, the hardest thing was, probably the trash buttons? I will not understand people, who write CSS for a living. Why can’t the div go to the bottom of the screen if i say it to do so???? Why do I have to flexbox justify align something then position opacity something to move a div? It was not easy (especially when I’m not really good at JS) to write this shit. So I gave up on adding a settings button, I am NOT messing around with JS/CSS anymore… When I finish rating some other projects, for my previous ship, then I’ll probably ship this. (this dumpster fire was designed on a 4:3 monitor, so most desktop monitors should work!) Also, the website is up! (check the domain ) Changelog fix: add options to geolocation to increase cache and make it faster ( 6823f69 ) feat: add favicon ( d3ab880 ) feat: add darkreader lock to not break css ( 9f38395 ) chore: update readme with picture of project ( 8d85e24 ) Create CNAME ( 4d06d89 ) feat: finalize favorites, add weather, and stardance stats ( 1be2aa4 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 30939, "ts": "2026-07-18T23:00:46Z", "hours": 7.5708, "text": "My longest devlog to date! Wow, a SEVEN HOUR devlog!!!!!!!! I don’t know what I expected but webdev is still not easy!!!!! So, new features: A functional search bar! Favorites! Clock with date! The favorites took the longest time, mostly because i’m a beginner with javascript (like i can understand it, but I don’t know much syntax) Also the search bar took a long time, because I reworked it since yesterday (it was a custom input, now using a standard html input) The clock was pretty easy, just used the standard js date function, i just have to do a “setInterval” for every second. (the search bar google icon implementation was copied from the firefox default homepage) Next steps will be: add a weather panel also add something stardance related Changelog feat: add basics, clock, search bar, and favorites ( cf8e57e ) thanks for coming to my ted talk -zsobix"}, {"post_id": 30402, "ts": "2026-07-17T22:00:32Z", "hours": 3.1317, "text": "First devlog! This project is going to be a stardance inspired new tab page! Despite the 3 hours of coding, i didn’t make much progress, mostly because implementing the search feature took a while (also i got sidetracked centering a div ) So all I did today was: making a search bar centering a div Don’t believe anybody, who says webdev is easy! (“now i understand why web developers are all bald and angry” -said a stardance poet) i have had enough of writing weird xml-ese today…… Changelog initial commit ( 3e7a0dd ) thanks for coming to my ted talk -zsobix"}]...
|
Title: StarScraper by @zsobix | Stardance
Devlogs Title: StarScraper by @zsobix | Stardance
Devlogs:
First devlog! This project is going to be a stardance inspired new tab page! Despite the 3 hours of coding, i didn’t make much progress, mostly because implementing the search feature took a while (also i got sidetracked centering a div ) So all I did today was: making a search bar centering a div Don’t believe anybody, who says webdev is easy! (“now i understand why web developers are all bald and angry” -said a stardance poet) i have had enough of writing weird xml-ese today…… Changelog initial commit ( 3e7a0dd ) thanks for coming to my ted talk -zsobix
My longest devlog to date! Wow, a SEVEN HOUR devlog!!!!!!!! I don’t know what I expected but webdev is still not easy!!!!! So, new features: A functional search bar! Favorites! Clock with date! The favorites took the longest time, mostly because i’m a beginner with javascript (like i can understand it, but I don’t know much syntax) Also the search bar took a long time, because I reworked it since yesterday (it was a custom input, now using a standard html input) The clock was pretty easy, just used the standard js date function, i just have to do a “setInterval” for every second. (the search bar google icon implementation was copied from the firefox default homepage) Next steps will be: add a weather panel also add something stardance related Changelog feat: add basics, clock, search bar, and favorites ( cf8e57e ) thanks for coming to my ted talk -zsobix
Last devlog before ship (i still have to rate 10 times ) I finally finished!!!!! After 14 hours for a project that was supposed to take 3 hours, i finally finished!! So today, i added: Weather info (with the Open-Meteo API) trash buttons for the favorites Your Stardance info (with @jam06452 ’s Stardance API) Honestly, the hardest thing today was working with javascript , especially with the fetch api (now i hate async functions AND js!!!!) Other than that, the hardest thing was, probably the trash buttons? I will not understand people, who write CSS for a living. Why can’t the div go to the bottom of the screen if i say it to do so???? Why do I have to flexbox justify align something then position opacity something to move a div? It was not easy (especially when I’m not really good at JS) to write this shit. So I gave up on adding a settings button, I am NOT messing around with JS/CSS anymore… When I finish rating some other projects, for my previous ship, then I’ll probably ship this. (this dumpster fire was designed on a 4:3 monitor, so most desktop monitors should work!) Also, the website is up! (check the domain ) Changelog fix: add options to geolocation to increase cache and make it faster ( 6823f69 ) feat: add favicon ( d3ab880 ) feat: add darkreader lock to not break css ( 9f38395 ) chore: update readme with picture of project ( 8d85e24 ) Create CNAME ( 4d06d89 ) feat: finalize favorites, add weather, and stardance stats ( 1be2aa4 ) thanks for coming to my ted talk -zsobix
I lied… 4th devlog, and more to come! Today was a shorter day, not because i didn’t have time, but because I procrastinated until 10 pm So today, I added: a settings menu, to change search engines! also I fixed a bug with the weather widget Believing in my project, i set it as my new tab, and then I noticed a bug. Specifically, that the geolocation timeout was set to 5 seconds, and it wasn’t showing the error. This was easily fixed, by me adding a zero to the end of the timeout, and showing the GIVEN error message instead of some arbitrary bullshit. Now, the settings took the longest, but it wasn’t so bad! I just had to change the search bar to grab the query string from localstorage, and set a new query url to localstorage when changed in the settings menu! I am planning to finish by adding more options to the settings menu, like custom theme options, hide widgets, and reset all changes button! (also thanks to @water for the words of encouragement!) Changelog feat: add search settings, fix: geolocation timeout now set to 1 minute to not cause errors ( 7c1b9ca ) thanks for coming to my ted talk -zsobix
I think this will be the last devlog before shipping I finally added theming!!!! Now, you can burn out your retina at night, with the new light mode! Also, I added customizable outline colors! (not for the light mode, just because there isn’t a color that looks nice with #FFFFFF) This was pretty easy, as I had everything pretty much set up, just needed to add some buttons, and js. (do not look at my js ) Honestly, that is all, I do not have much to say, as there aren’t any bugs, and (i think) it’s ready to ship! Changelog feat: add theming settings ( a44437c ) thanks for coming to my ted talk -zsobix
Last minute adjustments So today, I didn’t have much ideas for other projects, so I made some UI tweaks before shipping! And also! I added a new primary color for the light mode! (test my project to find out ) Changelog feat: ui tweaks ( d65d893 ) thanks for coming to my short ted talk -zsobix...
|
1792558119.4516757
|
1793162919.4516757
|
|
39853
|
REALinux by @zsobix | Stardance
|
zsobix
|
0
|
5.05
|
0
|
[]
|
[{"post_id": 40416, "ts": "202 [{"post_id": 40416, "ts": "2026-08-03T22:04:08Z", "hours": 1.2147, "text": "Day threeee!! Today, I didn’t get to add much, but atleast i tried New features: A settings app An about app, using the readme some styling adjustments focus borders This was all pretty easy, for the about app i used a markdown renderer, and the settings app is just a color picker with some js logic. The styling was just adding “position: relative” to the header css to move the windows under the header. And, the focus borders basically was based off of the tutorial, but i implemented my way. I still have to add proper hosting, then i can ship. Changelog feat: add settings and about app + styling ( 58cce27 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 39712, "ts": "2026-08-02T20:54:11Z", "hours": 1.9319, "text": "Day twoooooooo Today I could actually put some time into my project! So, i added: an actual readme licensing for the project and my background image a stardance stats app a weather app some stying The actual hardest thing was figuring out that “onhover” doesnt exist, and i have to use “onmouseover” instead!!!! i love js!!!!!! Everything else was pretty easy, basically just copying the apps from my new page project called “StarScraper”. As I said in the first devlog, i’m designing this project off of my hyprland dotfiles, and I added my background image which I took!!! But, the problem with putting images on the internet, is that there alot of people who just steal images! So I added a CC-BY-NC-SA 4.0 license to try to combat that. I do not want to have just an “All rights reserved” because i think that feels too controlling, i want for people to use my image, but just don’t steal it. pls use my picture with attribution, i think it turned out great. Anyways, this devlog was powered by Paulaner Spezi, and Lemon Estathé, so shoutout to those. I’ll probalbly add more apps, i just need one more devlog to ship, but i also need to rate for my first project, and i hate rating projects! I feel that it was easier on Flavortown, because I was less stressed to not take a BIG hit on my payout from writing a “bad” review, so it just feels too constraining. Changelog feat: add background + licensing, stardance app and weather app ( 3253a32 ) thanks for coming to my ted talk -zsobix"}, {"post_id": 39105, "ts": "2026-08-01T20:18:29Z", "hours": 1.9064, "text": "First webos devlog! I started this project before I went on holiday, and now I’m back, so I can finally start this! So today, I added: Basic features (like a normal header, and css) a movable window! and a working clock Honestly, it wasn’t really hard, i “obtained” the window moving code from w3schools, and the time code from my other project! The hardest thing was actually implementing the moving windows, because i missed a line of css in the tutorial I’m trying to style it of of my hyprland dotfiles, we’ll see how it will look. (today it is 42˚C in my city, so i can’t write that much) Changelog feat: add basics, moving window, and time ( 35a73a2 ) initial commit ( bd294f8 ) thanks for coming to my ted talk -zsobix"}]...
|
Title: REALinux by @zsobix | Stardance
Devlogs:
F Title: REALinux by @zsobix | Stardance
Devlogs:
First webos devlog! I started this project before I went on holiday, and now I’m back, so I can finally start this! So today, I added: Basic features (like a normal header, and css) a movable window! and a working clock Honestly, it wasn’t really hard, i “obtained” the window moving code from w3schools, and the time code from my other project! The hardest thing was actually implementing the moving windows, because i missed a line of css in the tutorial I’m trying to style it of of my hyprland dotfiles, we’ll see how it will look. (today it is 42˚C in my city, so i can’t write that much) Changelog feat: add basics, moving window, and time ( 35a73a2 ) initial commit ( bd294f8 ) thanks for coming to my ted talk -zsobix
Day twoooooooo Today I could actually put some time into my project! So, i added: an actual readme licensing for the project and my background image a stardance stats app a weather app some stying The actual hardest thing was figuring out that “onhover” doesnt exist, and i have to use “onmouseover” instead!!!! i love js!!!!!! Everything else was pretty easy, basically just copying the apps from my new page project called “StarScraper”. As I said in the first devlog, i’m designing this project off of my hyprland dotfiles, and I added my background image which I took!!! But, the problem with putting images on the internet, is that there alot of people who just steal images! So I added a CC-BY-NC-SA 4.0 license to try to combat that. I do not want to have just an “All rights reserved” because i think that feels too controlling, i want for people to use my image, but just don’t steal it. pls use my picture with attribution, i think it turned out great. Anyways, this devlog was powered by Paulaner Spezi, and Lemon Estathé, so shoutout to those. I’ll probalbly add more apps, i just need one more devlog to ship, but i also need to rate for my first project, and i hate rating projects! I feel that it was easier on Flavortown, because I was less stressed to not take a BIG hit on my payout from writing a “bad” review, so it just feels too constraining. Changelog feat: add background + licensing, stardance app and weather app ( 3253a32 ) thanks for coming to my ted talk -zsobix
Day threeee!! Today, I didn’t get to add much, but atleast i tried New features: A settings app An about app, using the readme some styling adjustments focus borders This was all pretty easy, for the about app i used a markdown renderer, and the settings app is just a color picker with some js logic. The styling was just adding “position: relative” to the header css to move the windows under the header. And, the focus borders basically was based off of the tutorial, but i implemented my way. I still have to add proper hosting, then i can ship. Changelog feat: add settings and about app + styling ( 58cce27 ) thanks for coming to my ted talk -zsobix...
|
1792569272.6276617
|
1793174072.6276617
|
|
43967
|
6-key macropad!! by @zsobix | Stardance
|
zsobix
|
0
|
11.56
|
0
|
[]
|
[{"post_id": 46356, "ts": "202 [{"post_id": 46356, "ts": "2026-08-13T15:00:56Z", "hours": 7.0858, "text": "Day three, four, five, six, and seven! ( ) Umm, i didn’t have much time this week to devlog, and also i didn’t feel like writing devlogs, so I’m writing this before my trip! (the days i’m going to reference are the days in the devlog, like first day -> day three) The first day, i rewired the pcb again, then made the bottom plate of the case. The second day, i made the rest of the case, then noticed that the front plate had a humongous forehead, so the next day I rewired the pcb (again). This is pretty normal with pcb design, is what i noticed. The 4th day was spent with case design, and it still had a huge forehead. the next day was spent with forehead smallening surgery, which included: rewiring the pcb remaking the case And it still has a huge ass forehead. The main problems were: the switches, rotary encoder and leds don’t have a cad model in kicad the oled display was in the wrong orientation the led footprint is probably in the wrong orientation I cannot work on the project for the next few days, after that ill probably start setting up the firmware. thanks for coming to my ted talk -zsobix"}, {"post_id": 42911, "ts": "2026-08-07T21:22:33Z", "hours": 3.3872, "text": "Day twooo Today I (basically) finished the schematics!!!! I still have to work on the pcb, because i “finished” it but it still has tons of errors, and the traces are all over the place. I did still have to fight with kicad, especially with adding down the traces. What I discovered, that pcb design is mostly connect the dots, with extra steps. I don’t have much to say, i was very locked in connecting the traces…. thanks for coming to my ted talk -zsobix"}, {"post_id": 42092, "ts": "2026-08-06T17:35:16Z", "hours": 1.0833, "text": "First devlogggggggg! I started making a hackpad!!!! I have no prior pcb knowledge, and i only watched some onshape tutorial, but it’s looking great! I read the hackpad tutorial beforehand, so working with kicad wasn’t that hard. I had to fight with both kicad and onshape, kicad for trying to wire up the switch legs and the xiao, and with onshape to import the plate dxf (it didn’t work ) I can’t work more today, because i have some eye problems. The pcb still looks very barren, so i’ll work on that tomorrow. thanks for coming to my ted talk -zsobix"}]...
|
Title: 6-key macropad!! by @zsobix | Stardance
De Title: 6-key macropad!! by @zsobix | Stardance
Devlogs:
First devlogggggggg! I started making a hackpad!!!! I have no prior pcb knowledge, and i only watched some onshape tutorial, but it’s looking great! I read the hackpad tutorial beforehand, so working with kicad wasn’t that hard. I had to fight with both kicad and onshape, kicad for trying to wire up the switch legs and the xiao, and with onshape to import the plate dxf (it didn’t work ) I can’t work more today, because i have some eye problems. The pcb still looks very barren, so i’ll work on that tomorrow. thanks for coming to my ted talk -zsobix
Day twooo Today I (basically) finished the schematics!!!! I still have to work on the pcb, because i “finished” it but it still has tons of errors, and the traces are all over the place. I did still have to fight with kicad, especially with adding down the traces. What I discovered, that pcb design is mostly connect the dots, with extra steps. I don’t have much to say, i was very locked in connecting the traces…. thanks for coming to my ted talk -zsobix
Day three, four, five, six, and seven! ( ) Umm, i didn’t have much time this week to devlog, and also i didn’t feel like writing devlogs, so I’m writing this before my trip! (the days i’m going to reference are the days in the devlog, like first day -> day three) The first day, i rewired the pcb again, then made the bottom plate of the case. The second day, i made the rest of the case, then noticed that the front plate had a humongous forehead, so the next day I rewired the pcb (again). This is pretty normal with pcb design, is what i noticed. The 4th day was spent with case design, and it still had a huge forehead. the next day was spent with forehead smallening surgery, which included: rewiring the pcb remaking the case And it still has a huge ass forehead. The main problems were: the switches, rotary encoder and leds don’t have a cad model in kicad the oled display was in the wrong orientation the led footprint is probably in the wrong orientation I cannot work on the project for the next few days, after that ill probably start setting up the firmware. thanks for coming to my ted talk -zsobix...
|
1792568954.1686702
|
1793173754.1686702
|
|
26003
|
My awesome macropad! by @zsm3ham | Stardance
|
zsm3ham
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zsm3ham | Stardanc Title: My awesome macropad! by @zsm3ham | Stardance...
|
1792623104.0165327
|
1793227904.0165327
|
|
8187
|
Macropad by @zsm1 | Stardance
|
zsm1
|
1
|
6.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-09T22:47:09Z", "hours": 6.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What I made I designed and built a custom mechanical macropad from the ground up using KiCad, Fusion 360, and custom firmware. The macropad features: 3×3 mechanical key matrix Rotary encoder for volume or other controls OLED display for status information 20 addressable RGB LEDs for underglow lighting Seeed Studio XIAO RP2040 microcontroller Custom PCB and enclosure The project combines electronics design, PCB layout, CAD modeling, and embedded programming into a single project! What I am most proud of I am proud that every major part of the device was custom designed rather than assembled from an existing kit. Seeing the schematic, PCB, enclosure, and firmware come together into a complete product was the most rewarding part of the project. This required me to learn electronic schematic design, PCB routing, CAD modeling, firmware development, aswell as designing for manufacturing (3d printing). Testing Currently this is only designed, not built yet. This post is for approval of the parts. However, it still represents a milestone of having fully designed all the aspects of this macropad! For now, there is no demo video available but the github contains renderings, firmware, and pcb schematics; everything you need to build it yourself.", "repo": "https://github.com/ZSmaster1/macropad", "demo": ""}]...
|
[{"post_id": 5935, "ts": "2026 [{"post_id": 5935, "ts": "2026-06-09T22:22:35Z", "hours": 0.6625, "text": "Completed the hackpad guide! I was going to use QMK but KMK seemed easier to use initally since I dont actually have the physical macropad yet. I also compiled everything onto a github repository for submission. https://github.com/ZSmaster1/macropad"}, {"post_id": 5292, "ts": "2026-06-09T00:44:40Z", "hours": 1.465, "text": "Finished designing the enclosure for the macropad in Fusion 360. To make sure everything fit correctly, I exported the PCB directly from KiCad and imported it into the CAD assembly as a reference. This made it much easier to design around the actual hardware instead of guessing dimensions, as well as aligning the gap on the bottom for the underglow effect. I found models for the switches, rotary encoder, OLED display, and Seeed Studio XIAO on GrabCAD, which ended up saving a lot of time. Having the real component geometry available meant I could check clearances, mounting positions, and connector access. I can finally see the macropad come together! The electronics, PCB, and enclosure all exist together in one assembly, now I just have to write the firmware which I am leaning towards using QMK due to its customization. Any feedback is appreciated!"}, {"post_id": 3940, "ts": "2026-06-07T02:08:51Z", "hours": 1.9939, "text": "Finished the PCB layout and made some final schematic updates. While making the PCB I realized I didn’t have any decoupling capacitors, and since I’m using 20 addressable LEDs, changing them all at once might cause voltage drops and other unexpected issues so I added one 100nf capacitor per 2 LEDs. The PCB layout took longer than expected. I had to learn about vias, ground planes, and different constraints. Routing everything on the 2 layer board took a while and a lot of trace reroutes. Looking at the 3d model of the PCB I can see the macropad slowly coming together. The next step is to design the case around the PCB in Fusion 360."}, {"post_id": 3690, "ts": "2026-06-06T18:53:16Z", "hours": 1.7578, "text": "Finished designing the full macropad schematic in KiCad. The design includes a 3×3 key matrix, a Seeed Studio XIAO microcontroller, rotary encoder, OLED display, and a chain of addressable RGB LEDs for underglow. A surprising amount of time went into learning KiCad itself. Organizing the schematic onto the sheet took longer than expected since I had to learn about nets, labels, power flags, etc. Furthermore I also had to learn about symbols, footprints and the ERC. Next is the PCB where I’ll route the traces and define the physical layout of the board."}]...
|
Title: Macropad by @zsm1 | Stardance
Devlogs:
Fin Title: Macropad by @zsm1 | Stardance
Devlogs:
Finished designing the full macropad schematic in KiCad. The design includes a 3×3 key matrix, a Seeed Studio XIAO microcontroller, rotary encoder, OLED display, and a chain of addressable RGB LEDs for underglow. A surprising amount of time went into learning KiCad itself. Organizing the schematic onto the sheet took longer than expected since I had to learn about nets, labels, power flags, etc. Furthermore I also had to learn about symbols, footprints and the ERC. Next is the PCB where I’ll route the traces and define the physical layout of the board.
Finished the PCB layout and made some final schematic updates. While making the PCB I realized I didn’t have any decoupling capacitors, and since I’m using 20 addressable LEDs, changing them all at once might cause voltage drops and other unexpected issues so I added one 100nf capacitor per 2 LEDs. The PCB layout took longer than expected. I had to learn about vias, ground planes, and different constraints. Routing everything on the 2 layer board took a while and a lot of trace reroutes. Looking at the 3d model of the PCB I can see the macropad slowly coming together. The next step is to design the case around the PCB in Fusion 360.
Finished designing the enclosure for the macropad in Fusion 360. To make sure everything fit correctly, I exported the PCB directly from KiCad and imported it into the CAD assembly as a reference. This made it much easier to design around the actual hardware instead of guessing dimensions, as well as aligning the gap on the bottom for the underglow effect. I found models for the switches, rotary encoder, OLED display, and Seeed Studio XIAO on GrabCAD, which ended up saving a lot of time. Having the real component geometry available meant I could check clearances, mounting positions, and connector access. I can finally see the macropad come together! The electronics, PCB, and enclosure all exist together in one assembly, now I just have to write the firmware which I am leaning towards using QMK due to its customization. Any feedback is appreciated!
Completed the hackpad guide! I was going to use QMK but KMK seemed easier to use initally since I dont actually have the physical macropad yet. I also compiled everything onto a github repository for submission. https://github.com/ZSmaster1/macropad
Ships:
What I made I designed and built a custom mechanical macropad from the ground up using KiCad, Fusion 360, and custom firmware. The macropad features: 3×3 mechanical key matrix Rotary encoder for volume or other controls OLED display for status information 20 addressable RGB LEDs for underglow lighting Seeed Studio XIAO RP2040 microcontroller Custom PCB and enclosure The project combines electronics design, PCB layout, CAD modeling, and embedded programming into a single project! What I am most proud of I am proud that every major part of the device was custom designed rather than assembled from an existing kit. Seeing the schematic, PCB, enclosure, and firmware come together into a complete product was the most rewarding part of the project. This required me to learn electronic schematic design, PCB routing, CAD modeling, firmware development, aswell as designing for manufacturing (3d printing). Testing Currently this is only designed, not built yet. This post is for approval of the parts. However, it still represents a milestone of having fully designed all the aspects of this macropad! For now, there is no demo video available but the github contains renderings, firmware, and pcb schematics; everything you need to build it yourself....
|
1792828216.4039207
|
1792914616.4039207
|
|
55895
|
Pico FIDO Key by @zsigisti | Stardance
|
zsigisti
|
0
|
1.2
|
0
|
[]
|
[{"post_id": 58098, "ts": "202 [{"post_id": 58098, "ts": "2026-08-30T13:32:28Z", "hours": 1.2, "text": "Getting my USB-A breakout to work I am still trying to tidy up my soldering and wiring but it’s finally coming together. Also i had to fix joint #4 from left to right because it didnt make contact properly"}]...
|
Title: Pico FIDO Key by @zsigisti | Stardance
Dev Title: Pico FIDO Key by @zsigisti | Stardance
Devlogs:
Getting my USB-A breakout to work I am still trying to tidy up my soldering and wiring but it’s finally coming together. Also i had to fix joint #4 from left to right because it didnt make contact properly...
|
1792637646.6665382
|
1793242446.6665382
|
|
64143
|
BlueberryLinux by @zsigisti | Stardance
|
zsigisti
|
1
|
45.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-20T16:40:36Z", "hours": 45.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Blueberry Linux is a source-built rolling x86-64 server distro I’ve been working on since May. It isn’t a respin of anything. It has its own package manager (bpm, written in Rust with streaming installs and SHA-256 verification), its own package format, and its own signed repository using an Ed25519 signature over the index. There are 225 package recipes so far, from glibc and binutils upward. It’s also self-hosted in the real sense. The base system is built from Blueberry packages using the Blueberry toolchain, and if a build falls back to a foreign bootstrap, that’s considered a build failure rather than a successful build. I came back to the project after about a month away and spent some time auditing the live infrastructure before getting back to development. I fixed the repository issues I found, published nine package updates, and built something new: you can now try Blueberry directly in your browser at https://try.blueberrylinux.org . The hardest part of this round was actually a near miss. There’s an old copy of bpmrepo.sh sitting on the repository host that predates serial support. It doesn’t emit the |serial| line. It was sitting there looking perfectly usable, and it would have worked. The problem is that using it would have silently removed rollback protection from the signed repository index. Nothing would have obviously failed. The index would still have been signed and the repository would still have worked. I only caught it because I went back and checked what my own client actually expects instead of assuming the existing tool was the right one. The browser shell also had two bugs that took a bit of debugging. First, pty.fork() already calls setsid(), so I was calling it a second time. That resulted in EPERM and killed every session immediately after launch. Then the xterm CDN URLs started returning 404s. The frontend failed before it could even display the actual error, so from the user’s perspective it just sat there saying “connecting…”. I vendored the assets locally and changed the frontend to report asset loading failures properly. The part I’m happiest with is how the browser environment is built. The thing you’re running in the browser is actually assembled from the same packages the distro itself uses. The isolation is also verified rather than assumed. From inside a live session, the router, the hypervisor, and 1.1.1.1 are all unreachable, and only three PIDs are visible. If you want to try it, open https://try.blueberrylinux.org . It’s a real shell on a real Blueberry rootfs. There’s no network access, nothing persists between sessions, and each session is limited to ten minutes. The source is available here: https://github.com/zsigisti/blueberry", "repo": "https://github.com/zsigisti/blueberry", "demo": "https://try.blueberrylinux.org/"}]...
|
[{"post_id": 71299, "ts": "202 [{"post_id": 71299, "ts": "2026-09-20T16:21:40Z", "hours": 45.3069, "text": "Came back to Blueberry after a month and audited the live infrastructure before writing any code.State of the system: the distro is healthy. 225 recipes, valid index signature, and the main mirror is serving real packages.There were two actual issues.The published bpm.index was dated 31 July, so it was seven weeks stale. The other was blueberry-build.timer on the repo host, which had failed every hour since 29 June — 2,217 consecutive failures — because it was still trying to run blueberry-build-server.sh. I deleted that script during the .bpm migration and never disabled the unit.I also initially thought repo1 was broken. It isn’t. Its index is 0 bytes because it’s the BUR community mirror and nothing has been approved there yet. Nginx correctly returns 404 at the origin. That one was just me reading the state incorrectly.Both actual issues are now fixed.I disabled the timer rather than bringing the old script back. I also republished the index with a fresh serial using tools/release/repo-publish.sh. It re-indexes remotely using the hardened bpmrepo.sh, including a count-floor check, timestamped backup, and atomic index + signature swap.I almost used the wrong script. /opt/blueberry/tools/bpmrepo.sh is an orphaned copy from before serial support was added and doesn’t emit the |serial| line. Publishing with that one would have silently removed rollback protection from the signed index.I also did an upstream sweep. 110 of the 225 packages are currently outdated. The first scan hit 11 GitHub HTTP errors because of unauthenticated API rate limiting. Passing a token brought that down to one.I bumped and built nine packages from the current sources and published them:tzdata 2026b -> 2026dcurl 8.21 -> 8.22libcap 2.73 -> 2.78libxml2wireless-regdbless 668 -> 710jq 1.8.2htop 3.5.3nano 8.7.1All nine were built using the Blueberry toolchain with no bootstrap fallback. The changes are on branch pkg-bump-2026-09-20.Three automatic bumps produced incorrect source URLs. ca-certificates tried to fetch a 2026-08 PEM from the 2026-05 path, and expat tried to fetch 2.8.4 from the R_2_8_2 tag. Those were left unpublished rather than shipping the wrong tarball.sqlite needs a manual bump. openssl 3.4.6 -> 4.0.2, perl 5.40 -> 5.44, and gettext 0.26 -> 1.0 are ABI-level changes, so those will get separate passes.There’s also something new: you can try Blueberry directly in your browser. https://try.blueberrylinux.orgNo install and no signup. It’s a real shell running on a real Blueberry rootfs. The rootfs is about 480 MB, assembled by walking the dependency closure from bpm.index and pulling the packages directly from the live mirror. It contains 41 packages, including bpm 1.11.6.The frontend is xterm.js, with an aiohttp WebSocket connected to a PTY, served through Cloudflare.Each session gets an overlay over a read-only rootfs, its own network, PID, mount, and UTS namespaces, a 32 MB tmpfs, and a hard 10-minute limit. There are 12 concurrent sessions allowed, and sessions are torn down when the client disconnects.I also verified the isolation from inside a live session. The router, hypervisor, and 1.1.1.1 are unreachable, and only three PIDs are visible.There were two bugs while building the browser shell.First, pty.fork() already calls setsid(), so my additional setsid() call failed with EPERM and killed every session during startup. The server reported “operation not permitted” and closed the WebSocket before the shell even started.Second, the xterm CDN URLs were returning 404s. The page failed before it could report the error and just sat on “connecting…”. I vendored the assets locally and changed the frontend to report asset load failures explicitly.So the current state is: the repository is publishing again, the dead build timer is gone, the first batch of package updates is built and published, and Blueberry now has a browser-accessible shell for trying out the system without installing anything."}]...
|
Title: BlueberryLinux by @zsigisti | Stardance
De Title: BlueberryLinux by @zsigisti | Stardance
Devlogs:
Came back to Blueberry after a month and audited the live infrastructure before writing any code.State of the system: the distro is healthy. 225 recipes, valid index signature, and the main mirror is serving real packages.There were two actual issues.The published bpm.index was dated 31 July, so it was seven weeks stale. The other was blueberry-build.timer on the repo host, which had failed every hour since 29 June — 2,217 consecutive failures — because it was still trying to run blueberry-build-server.sh. I deleted that script during the .bpm migration and never disabled the unit.I also initially thought repo1 was broken. It isn’t. Its index is 0 bytes because it’s the BUR community mirror and nothing has been approved there yet. Nginx correctly returns 404 at the origin. That one was just me reading the state incorrectly.Both actual issues are now fixed.I disabled the timer rather than bringing the old script back. I also republished the index with a fresh serial using tools/release/repo-publish.sh. It re-indexes remotely using the hardened bpmrepo.sh, including a count-floor check, timestamped backup, and atomic index + signature swap.I almost used the wrong script. /opt/blueberry/tools/bpmrepo.sh is an orphaned copy from before serial support was added and doesn’t emit the |serial| line. Publishing with that one would have silently removed rollback protection from the signed index.I also did an upstream sweep. 110 of the 225 packages are currently outdated. The first scan hit 11 GitHub HTTP errors because of unauthenticated API rate limiting. Passing a token brought that down to one.I bumped and built nine packages from the current sources and published them:tzdata 2026b -> 2026dcurl 8.21 -> 8.22libcap 2.73 -> 2.78libxml2wireless-regdbless 668 -> 710jq 1.8.2htop 3.5.3nano 8.7.1All nine were built using the Blueberry toolchain with no bootstrap fallback. The changes are on branch pkg-bump-2026-09-20.Three automatic bumps produced incorrect source URLs. ca-certificates tried to fetch a 2026-08 PEM from the 2026-05 path, and expat tried to fetch 2.8.4 from the R_2_8_2 tag. Those were left unpublished rather than shipping the wrong tarball.sqlite needs a manual bump. openssl 3.4.6 -> 4.0.2, perl 5.40 -> 5.44, and gettext 0.26 -> 1.0 are ABI-level changes, so those will get separate passes.There’s also something new: you can try Blueberry directly in your browser. https://try.blueberrylinux.orgNo install and no signup. It’s a real shell running on a real Blueberry rootfs. The rootfs is about 480 MB, assembled by walking the dependency closure from bpm.index and pulling the packages directly from the live mirror. It contains 41 packages, including bpm 1.11.6.The frontend is xterm.js, with an aiohttp WebSocket connected to a PTY, served through Cloudflare.Each session gets an overlay over a read-only rootfs, its own network, PID, mount, and UTS namespaces, a 32 MB tmpfs, and a hard 10-minute limit. There are 12 concurrent sessions allowed, and sessions are torn down when the client disconnects.I also verified the isolation from inside a live session. The router, hypervisor, and 1.1.1.1 are unreachable, and only three PIDs are visible.There were two bugs while building the browser shell.First, pty.fork() already calls setsid(), so my additional setsid() call failed with EPERM and killed every session during startup. The server reported “operation not permitted” and closed the WebSocket before the shell even started.Second, the xterm CDN URLs were returning 404s. The page failed before it could report the error and just sat on “connecting…”. I vendored the assets locally and changed the frontend to report asset load failures explicitly.So the current state is: the repository is publishing again, the dead build timer is gone, the first batch of package updates is built and published, and Blueberry now has a browser-accessible shell for trying out the system without installing anything.
Ships:
Blueberry Linux is a source-built rolling x86-64 server distro I’ve been working on since May. It isn’t a respin of anything. It has its own package manager (bpm, written in Rust with streaming installs and SHA-256 verification), its own package format, and its own signed repository using an Ed25519 signature over the index. There are 225 package recipes so far, from glibc and binutils upward. It’s also self-hosted in the real sense. The base system is built from Blueberry packages using the Blueberry toolchain, and if a build falls back to a foreign bootstrap, that’s considered a build failure rather than a successful build. I came back to the project after about a month away and spent some time auditing the live infrastructure before getting back to development. I fixed the repository issues I found, published nine package updates, and built something new: you can now try Blueberry directly in your browser at https://try.blueberrylinux.org . The hardest part of this round was actually a near miss. There’s an old copy of bpmrepo.sh sitting on the repository host that predates serial support. It doesn’t emit the |serial| line. It was sitting there looking perfectly usable, and it would have worked. The problem is that using it would have silently removed rollback protection from the signed repository index. Nothing would have obviously failed. The index would still have been signed and the repository would still have worked. I only caught it because I went back and checked what my own client actually expects instead of assuming the existing tool was the right one. The browser shell also had two bugs that took a bit of debugging. First, pty.fork() already calls setsid(), so I was calling it a second time. That resulted in EPERM and killed every session immediately after launch. Then the xterm CDN URLs started returning 404s. The frontend failed before it could even display the actual error, so from the user’s perspective it just sat there saying “connecting…”. I vendored the assets locally and changed the frontend to report asset loading failures properly. The part I’m happiest with is how the browser environment is built. The thing you’re running in the browser is actually assembled from the same packages the distro itself uses. The isolation is also verified rather than assumed. From inside a live session, the router, the hypervisor, and 1.1.1.1 are all unreachable, and only three PIDs are visible. If you want to try it, open https://try.blueberrylinux.org . It’s a real shell on a real Blueberry rootfs. There’s no network access, nothing persists between sessions, and each session is limited to ten minutes. The source is available here: https://github.com/zsigisti/blueberry...
|
1792814104.6730797
|
1792900504.6730797
|
|
3824
|
ezenc - tui encoder / decoder :3 by @zsharpminor | ezenc - tui encoder / decoder :3 by @zsharpminor | Stardance...
|
zsharpminor
|
1
|
3.0
|
57
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-03T01:36:40Z", "hours": 3.0, "multiplier": 17.7, "payout": 57, "blessing": "neutral", "text": "ezenc is a fully functional encoder and decoder that works entirely in your command line and runs on pipx (you don’t even need to install anything!) it supports 30 ciphers and encryption methods, including everything ranging from simple base64 over the caesar cipher to the most obscure encryption methods you’ve never heard of, fun ones such as the Bacon Cipher, and, of course, SHA keys (just be mindful - it’s not really possible to decrypt those later on!) ezenc was made entirely in Python and is a part of the ez-series of terminal utilities I’m working on! In the past, I’ve made stuff like syt (youtube downloader), sfm (file manager, compressor, transcript fetcher, and paywall bypasser), sss (school site scraper for emails) and ezserial (access your MCU via serial WITHOUT figuring out which port it’s connected to and trying to remember the screen command!) ezenc is the newest addition to this series, and I’d love if you gave it a try! :D with much love, zsharpminor", "repo": "https://github.com/newtontriumphant/ezenc", "demo": "https://pypi.org/project/ez-encrypt/"}]...
|
[{"post_id": 1190, "ts": "2026 [{"post_id": 1190, "ts": "2026-06-03T01:30:58Z", "hours": 0.4008, "text": "Packaged everything on PyPI and getting ready to ship! :D"}, {"post_id": 1148, "ts": "2026-06-03T00:12:19Z", "hours": 0.2811, "text": "The main menu of ezenc is now functional! You can encode and decode in the same command, and it now should fully support 30 encryption methods! :)"}, {"post_id": 1141, "ts": "2026-06-02T23:54:38Z", "hours": 0.8061, "text": "Finally, you can both encode AND decode with ezenc! Now all that’s left to do is to make a main menu for choosing which one, and, of course, making it so that you can encode ANYthing, not just Base64 :3"}, {"post_id": 1119, "ts": "2026-06-02T23:05:12Z", "hours": 0.405, "text": "Added some advanced regex-based cipher detection that attempts to intelligently detect which cipher you’re talking in (this is basically just copy and pasting the encryption code but refactoring it into an actual helper function lmao)"}, {"post_id": 596, "ts": "2026-06-02T02:48:56Z", "hours": 0.6389, "text": "It works! ezenc can now automatically decode any of ~26 languages and hashes that you paste in!"}, {"post_id": 573, "ts": "2026-06-02T02:06:44Z", "hours": 0.3408, "text": "You can now encode and decode B58 with ezenc! Slowly but surely, progress is being made! :)"}, {"post_id": 557, "ts": "2026-06-02T01:41:04Z", "hours": 0.3728, "text": "I’m working on a TUI encoder/decoder for any and all encoding methods! So far, I’ve set up a basic logo and English checker that’s meant to check if your output is plausible (has a high English score) or inplausible (has a low English score, meaning it’s gibberish.)"}]...
|
Title: ezenc - tui encoder / decoder :3 by @zsharp Title: ezenc - tui encoder / decoder :3 by @zsharpminor | Stardance
Devlogs:
I’m working on a TUI encoder/decoder for any and all encoding methods! So far, I’ve set up a basic logo and English checker that’s meant to check if your output is plausible (has a high English score) or inplausible (has a low English score, meaning it’s gibberish.)
You can now encode and decode B58 with ezenc! Slowly but surely, progress is being made! :)
It works! ezenc can now automatically decode any of ~26 languages and hashes that you paste in!
Added some advanced regex-based cipher detection that attempts to intelligently detect which cipher you’re talking in (this is basically just copy and pasting the encryption code but refactoring it into an actual helper function lmao)
Finally, you can both encode AND decode with ezenc! Now all that’s left to do is to make a main menu for choosing which one, and, of course, making it so that you can encode ANYthing, not just Base64 :3
The main menu of ezenc is now functional! You can encode and decode in the same command, and it now should fully support 30 encryption methods! :)
Packaged everything on PyPI and getting ready to ship! :D
Ships:
ezenc is a fully functional encoder and decoder that works entirely in your command line and runs on pipx (you don’t even need to install anything!) it supports 30 ciphers and encryption methods, including everything ranging from simple base64 over the caesar cipher to the most obscure encryption methods you’ve never heard of, fun ones such as the Bacon Cipher, and, of course, SHA keys (just be mindful - it’s not really possible to decrypt those later on!) ezenc was made entirely in Python and is a part of the ez-series of terminal utilities I’m working on! In the past, I’ve made stuff like syt (youtube downloader), sfm (file manager, compressor, transcript fetcher, and paywall bypasser), sss (school site scraper for emails) and ezserial (access your MCU via serial WITHOUT figuring out which port it’s connected to and trying to remember the screen command!) ezenc is the newest addition to this series, and I’d love if you gave it a try! :D with much love, zsharpminor...
|
1792831732.4627182
|
1792918132.4627182
|
|
10274
|
Untitled by @zsharpminor | Stardance
|
zsharpminor
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @zsharpminor | Stardance
|
1792486285.60425
|
1793091085.60425
|
|
54460
|
My awesome macropad! by @zshadow168 | Stardance
|
zshadow168
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zshadow168 | Stard Title: My awesome macropad! by @zshadow168 | Stardance...
|
1792792162.4059734
|
1793396962.4059734
|
|
46053
|
My awesome macropad! by @zsemaj_11 | Stardance
|
zsemaj_11
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zsemaj_11 | Starda Title: My awesome macropad! by @zsemaj_11 | Stardance...
|
1792648451.7366295
|
1793253251.7366295
|
|
34415
|
AdmitGPT by @zs_01117875692 | Stardance
|
zs_01117875692
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AdmitGPT by @zs_01117875692 | Stardance
|
1792608834.761835
|
1793213634.761835
|
|
198
|
Calamity Engine by @zrl | Stardance
|
zrl
|
1
|
21.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-27T20:24:10Z", "hours": 21.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Calamity Engine Alpha v1.1.0 Calamity Engine is a small, portable, 2D game engine made with retro/underpowered platforms in mind, written in C++. I worked on maintaining and updating Calamity Engine with new features, such as multi-window support, raycasts, collision signals, a bunch of refactoring/restructuring, etc… I also wrote 4 new examples that showcase these new features! I recommend checking out the website where you will find (almost) every example compiled to the web, so you can try them out without leaving your browser! Please consider checking it out, I put a lot of work into it.", "repo": "https://github.com/sl4shed/calamity-engine", "demo": "https://calamity.sl4shed.xyz/"}]...
|
[{"post_id": 16912, "ts": "202 [{"post_id": 16912, "ts": "2026-06-27T13:51:30Z", "hours": 11.8522, "text": "Calamity engine devlog 3 we back baby Fixed the github workflow!! I finally figured out what was going on with the github workflow! The issue was that I was using an outdated version of download-emscripten and the emscripten version being downloaded was fried and that would mess up the loading. In the process of fixing the runner, i also migrated it to an arch container for no specific reason other than I like arch. New examples and refactoring I refactored every example (except graphics-settings and multi-window ) to run on console platforms and work with controllers! The code in the examples is now a better resource for learning the ins and outs of Calamity Engine. Input service fixes You can now see what modifiers are active in a key event now (look at InputEventWithModifiers ) visible and enabled properties on Nodes Before alpha 1.1, components (i.e. sprites) handled visibility individually but I decided that I don’t like that and now visibility a property of the node class! It is also inherited down the node tree to the children of the node. I also added the enabled property to Nodes! While visibility affects the rendering, the enabled property basically stops all lifetime functions such as update , physicsUpdate and input along with render . Full Windows support Windows is now fully supported and every issue I have encountered is ironed out. The console is now hidden in release builds, etc, etc New examples I added the graphics-settings , multi-window , button and raycast examples. You can check these out on the website (except for graphics-settings and multi-window because those are desktop specific)! Alpha 1.1 And with this devlog, I will be publishing Calamity Engine 1.1! i really don’t know what else to say so i attached a video of the new node-tree example"}, {"post_id": 8612, "ts": "2026-06-14T09:50:57Z", "hours": 7.24, "text": "Calamity engine devlog 2 i’m back with another fire devlog Physics changes I made a lot of changes to the Physics service, including adding the SegmentShape, Raycasts and overall tidying up the service by creating the PhysicsBody class. Every physics body (Rigidbody, Staticbody) inherits this class. Also, every physics body now has a signal for when the mouse enters and leaves the shape! This allows the creation of ui elements (i.e. look at the button example)! Windows is supported again You can build the game on Windows either using mingw64 or MSVC! There are a couple of issues though… Windows support isn’t necessarily a top priority for me right now, but I will be working on it and hopefully getting it ready for when I create the next release! (also there’s some edge cases regarding the calamity folder on MSVC and especially on mingw64 where you have to manually copy over the dll of every vendored library) Example changes I’m working on tidying up all the example code and adding console platform support to every example! (for example, the node-tree example didn’t have any console support). I also added two new examples - button and raycast. These demonstrate how to use the new additions to the Physics service! Stuff that’s planned for the next minor release I want to fix the GitHub workflow that runs every push, it compiles every example for emscripten and builds the website. But, for some reason, the examples don’t load properly when the runner pushes the website. It works properly when I do it manually and the workflow runs the exact same commands I do… It’s a pretty weird issue and it’s very hard to debug but I want to get it fixed for alpha 1.1. New minor release After I fix the runner and finish tidying up the examples, I will create a new alpha 1.1 release! I don’t know if I will ship the project yet, I don’t think I have enough hours and I kinda want a bigger payout xD that’s it scooby gang. please like and subscribe and make sure to share this devlog to every family member in your vicinity! That also includes your grandmother."}, {"post_id": 383, "ts": "2026-06-01T18:54:17Z", "hours": 1.7694, "text": "Calamity engine devlog 1 Because of a lot of internal changes (i.e. multi-window support), the node-tree example broke :( Saving and loading sprites and textures was broken however i got it working again! Saving and loading any physics shape was also broken but now it’s also fixed! (i still have to fix loading for animated sprites/animations which will also be a pain in the bum bum but it is what it is…) Changes that occurred between Flavortown and Stardance Added multi-window support Started working on 3DS support (wasn’t able to finish in time unfortunately) Added collision detection signals to every physics body Added mouse hover detection signals to every physics body Made an example project of a button Added tracy support Added some QOL functions, such as lookAt() on Transforms “Fixed” github runner that compiles the website (it’s still broken 😭) Goals with development Primarily, I want to ship a more definitive version of Calamity Engine. I want to expand to more platforms, add networking, improve audio, add a ui library among other smaller things. Instead of one big release (alpha 1.0), i will probably be splitting ships across smaller releases (i.e. i want to release an alpha 1.1 version when i’m done with some smaller fixes and physics additions). When all of my goals are achieved with Calamity Engine, I want to work on a separate project that uses Calamity Engine - a cross-platform Navidrome client! I’ve always wanted to use my PSP as a music player but because I can’t be bothered to keep updating my playlist/redownloading music, I never got around to it… I also want to remake simulator canalizare 2019 in Calamity Engine and ship it to whatever platforms my engine will eventually support (technically, PS2 support is possible! Cross platform support really depends on how good the homebrew SDK’s are though. For each and every platform I want to get Calamity working on, I basically have to port spdlog , cereal , fmt and box2d myself unless i get really lucky and there are already maintained packages for all of those like on the PSP .)"}, {"post_id": 26, "ts": "2026-05-31T08:48:10Z", "hours": 0.4903, "text": "calamity engine will resume development on stardance"}]...
|
Title: Calamity Engine by @zrl | Stardance
Devlog Title: Calamity Engine by @zrl | Stardance
Devlogs:
calamity engine will resume development on stardance
Calamity engine devlog 1 Because of a lot of internal changes (i.e. multi-window support), the node-tree example broke :( Saving and loading sprites and textures was broken however i got it working again! Saving and loading any physics shape was also broken but now it’s also fixed! (i still have to fix loading for animated sprites/animations which will also be a pain in the bum bum but it is what it is…) Changes that occurred between Flavortown and Stardance Added multi-window support Started working on 3DS support (wasn’t able to finish in time unfortunately) Added collision detection signals to every physics body Added mouse hover detection signals to every physics body Made an example project of a button Added tracy support Added some QOL functions, such as lookAt() on Transforms “Fixed” github runner that compiles the website (it’s still broken 😭) Goals with development Primarily, I want to ship a more definitive version of Calamity Engine. I want to expand to more platforms, add networking, improve audio, add a ui library among other smaller things. Instead of one big release (alpha 1.0), i will probably be splitting ships across smaller releases (i.e. i want to release an alpha 1.1 version when i’m done with some smaller fixes and physics additions). When all of my goals are achieved with Calamity Engine, I want to work on a separate project that uses Calamity Engine - a cross-platform Navidrome client! I’ve always wanted to use my PSP as a music player but because I can’t be bothered to keep updating my playlist/redownloading music, I never got around to it… I also want to remake simulator canalizare 2019 in Calamity Engine and ship it to whatever platforms my engine will eventually support (technically, PS2 support is possible! Cross platform support really depends on how good the homebrew SDK’s are though. For each and every platform I want to get Calamity working on, I basically have to port spdlog , cereal , fmt and box2d myself unless i get really lucky and there are already maintained packages for all of those like on the PSP .)
Calamity engine devlog 2 i’m back with another fire devlog Physics changes I made a lot of changes to the Physics service, including adding the SegmentShape, Raycasts and overall tidying up the service by creating the PhysicsBody class. Every physics body (Rigidbody, Staticbody) inherits this class. Also, every physics body now has a signal for when the mouse enters and leaves the shape! This allows the creation of ui elements (i.e. look at the button example)! Windows is supported again You can build the game on Windows either using mingw64 or MSVC! There are a couple of issues though… Windows support isn’t necessarily a top priority for me right now, but I will be working on it and hopefully getting it ready for when I create the next release! (also there’s some edge cases regarding the calamity folder on MSVC and especially on mingw64 where you have to manually copy over the dll of every vendored library) Example changes I’m working on tidying up all the example code and adding console platform support to every example! (for example, the node-tree example didn’t have any console support). I also added two new examples - button and raycast. These demonstrate how to use the new additions to the Physics service! Stuff that’s planned for the next minor release I want to fix the GitHub workflow that runs every push, it compiles every example for emscripten and builds the website. But, for some reason, the examples don’t load properly when the runner pushes the website. It works properly when I do it manually and the workflow runs the exact same commands I do… It’s a pretty weird issue and it’s very hard to debug but I want to get it fixed for alpha 1.1. New minor release After I fix the runner and finish tidying up the examples, I will create a new alpha 1.1 release! I don’t know if I will ship the project yet, I don’t think I have enough hours and I kinda want a bigger payout xD that’s it scooby gang. please like and subscribe and make sure to share this devlog to every family member in your vicinity! That also includes your grandmother.
Calamity engine devlog 3 we back baby Fixed the github workflow!! I finally figured out what was going on with the github workflow! The issue was that I was using an outdated version of download-emscripten and the emscripten version being downloaded was fried and that would mess up the loading. In the process of fixing the runner, i also migrated it to an arch container for no specific reason other than I like arch. New examples and refactoring I refactored every example (except graphics-settings and multi-window ) to run on console platforms and work with controllers! The code in the examples is now a better resource for learning the ins and outs of Calamity Engine. Input service fixes You can now see what modifiers are active in a key event now (look at InputEventWithModifiers ) visible and enabled properties on Nodes Before alpha 1.1, components (i.e. sprites) handled visibility individually but I decided that I don’t like that and now visibility a property of the node class! It is also inherited down the node tree to the children of the node. I also added the enabled property to Nodes! While visibility affects the rendering, the enabled property basically stops all lifetime functions such as update , physicsUpdate and input along with render . Full Windows support Windows is now fully supported and every issue I have encountered is ironed out. The console is now hidden in release builds, etc, etc New examples I added the graphics-settings , multi-window , button and raycast examples. You can check these out on the website (except for graphics-settings and multi-window because those are desktop specific)! Alpha 1.1 And with this devlog, I will be publishing Calamity Engine 1.1! i really don’t know what else to say so i attached a video of the new node-tree example
Ships:
Calamity Engine Alpha v1.1.0 Calamity Engine is a small, portable, 2D game engine made with retro/underpowered platforms in mind, written in C++. I worked on maintaining and updating Calamity Engine with new features, such as multi-window support, raycasts, collision signals, a bunch of refactoring/restructuring, etc… I also wrote 4 new examples that showcase these new features! I recommend checking out the website where you will find (almost) every example compiled to the web, so you can try them out without leaving your browser! Please consider checking it out, I put a lot of work into it....
|
1792824647.271906
|
1792911047.271906
|
|
10073
|
2a-kernel by @zrl | Stardance
|
zrl
|
0
|
1.8
|
0
|
[]
|
[{"post_id": 4496, "ts": "2026 [{"post_id": 4496, "ts": "2026-06-07T20:33:33Z", "hours": 1.8036, "text": "2a-kernel devlog 1 One day, I do plan on completing this project, however that day is not today I hate android i hate android i hate android kernels i hate kernels This project is a fork of NP2_Kernel by MiguVT. NP2 Kernel is a “toolchain” to compile any android kernel and apply several patches to it such as ReSukiSU (kernelsu) or susfs4ksu . originally, i wanted to have a custom build of my kernel for the express purpose of hiding root to be able to use Revolut. However, I soon realised that Nothing couldn’t give less of a shit in regards to the Phone (2a) in specific. It seems like every other kernel that they’ve open sourced contains some sort of vendor specific patches but not the 2a kernel! If you try and build it, it straight up just won’t build. Me and my friends (that are smarter than me) have tried basically everything to get the kernel to compile. Including waiting >45mins every time we would build for LTO (link time optimizations) to finish on vmlinux.o (which also took up >30GB of ram/swap space). The best part is, the errors would only happen AFTER LTO and if you tried to disable LTO you would get a totally different set of errors! How wonderful. After trying basically everything i decided to give up and just patch my boot image instead, follow a random guide from XDA and now I suddenly have strong integrity again! Hooray! I guess there was no need for a custom kernel in the first place… (btw, the 1.8 hours that i logged do not include compile times. If they would, it would probably be more like 10 hours :3)"}]...
|
Title: 2a-kernel by @zrl | Stardance
Devlogs:
2a- Title: 2a-kernel by @zrl | Stardance
Devlogs:
2a-kernel devlog 1 One day, I do plan on completing this project, however that day is not today I hate android i hate android i hate android kernels i hate kernels This project is a fork of NP2_Kernel by MiguVT. NP2 Kernel is a “toolchain” to compile any android kernel and apply several patches to it such as ReSukiSU (kernelsu) or susfs4ksu . originally, i wanted to have a custom build of my kernel for the express purpose of hiding root to be able to use Revolut. However, I soon realised that Nothing couldn’t give less of a shit in regards to the Phone (2a) in specific. It seems like every other kernel that they’ve open sourced contains some sort of vendor specific patches but not the 2a kernel! If you try and build it, it straight up just won’t build. Me and my friends (that are smarter than me) have tried basically everything to get the kernel to compile. Including waiting >45mins every time we would build for LTO (link time optimizations) to finish on vmlinux.o (which also took up >30GB of ram/swap space). The best part is, the errors would only happen AFTER LTO and if you tried to disable LTO you would get a totally different set of errors! How wonderful. After trying basically everything i decided to give up and just patch my boot image instead, follow a random guide from XDA and now I suddenly have strong integrity again! Hooray! I guess there was no need for a custom kernel in the first place… (btw, the 1.8 hours that i logged do not include compile times. If they would, it would probably be more like 10 hours :3)...
|
1792587317.7441223
|
1793192117.7441223
|
|
1505
|
My awesome macropad! by @zredmask | Stardance
|
zredmask
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zredmask | Stardan Title: My awesome macropad! by @zredmask | Stardance...
|
1792691430.0300126
|
1793296230.0300126
|
|
1516
|
Untitled by @zredmask | Stardance
|
zredmask
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @zredmask | Stardance
|
1792536739.8092997
|
1793141539.8092997
|
|
33822
|
The land of xo elara by @zoziana | Stardance
|
zoziana
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The land of xo elara by @zoziana | Stardanc Title: The land of xo elara by @zoziana | Stardance...
|
1791827042.1265876
|
1792691042.1265876
|
|
39991
|
My own site! by @zoziana | Stardance
|
zoziana
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zoziana | Stardance
|
1791826766.8440113
|
1792690766.8440113
|
|
26200
|
180lbf Liquid Rocket Engine by @zozaf | Stardance
|
zozaf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 180lbf Liquid Rocket Engine by @zozaf | Sta Title: 180lbf Liquid Rocket Engine by @zozaf | Stardance...
|
1792641287.6930618
|
1793246087.6930618
|
|
8681
|
Hack me Yash by @zoyashrj | Stardance
|
zoyashrj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hack me Yash by @zoyashrj | Stardance
|
1792799564.411043
|
1793404364.411043
|
|
16624
|
My awesome macropad! by @zouken | Stardance
|
zouken
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zouken | Stardance
|
1792810176.095376
|
1793414976.095376
|
|
1717
|
My first slack bot! by @zouhha769 | Stardance
|
zouhha769
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zouhha769 | Stardan Title: My first slack bot! by @zouhha769 | Stardance...
|
1792500555.3648412
|
1793105355.3648412
|
|
48640
|
weirdo's site by @zoro | Stardance
|
zoro
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: weirdo's site by @zoro | Stardance
|
1792558474.7123315
|
1793163274.7123315
|
|
50773
|
n8n locally by @zoro | Stardance
|
zoro
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: n8n locally by @zoro | Stardance
|
1792644544.9473968
|
1793249344.9473968
|
|
18948
|
Cycloidal Gearbox by @zora_s_thind | Stardance
|
zora_s_thind
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cycloidal Gearbox by @zora_s_thind | Starda Title: Cycloidal Gearbox by @zora_s_thind | Stardance...
|
1792536749.1019385
|
1793141549.1019385
|
|
47364
|
Frictionless by @zoputam009 | Stardance
|
zoputam009
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @zoputam009 | Stardance
|
1792511603.256394
|
1793116403.256394
|
|
27979
|
A wind turbine by @zoomyum | Stardance
|
zoomyum
|
0
|
2.48
|
0
|
[]
|
[{"post_id": 19087, "ts": "202 [{"post_id": 19087, "ts": "2026-06-30T09:13:35Z", "hours": 0.3628, "text": "worked on the electronic design materials and wire mapping"}, {"post_id": 19067, "ts": "2026-06-30T08:09:58Z", "hours": 0.9333, "text": "designed the hub adpater to connect fan blades to motor shaft, also designed the tail"}, {"post_id": 19042, "ts": "2026-06-30T06:52:57Z", "hours": 1.1833, "text": "My design of the wind turbine’s top part attaching the motor and wooden post to each other and it is free moving so it can change direction based on wind"}]...
|
Title: A wind turbine by @zoomyum | Stardance
Dev Title: A wind turbine by @zoomyum | Stardance
Devlogs:
My design of the wind turbine’s top part attaching the motor and wooden post to each other and it is free moving so it can change direction based on wind
designed the hub adpater to connect fan blades to motor shaft, also designed the tail
worked on the electronic design materials and wire mapping...
|
1792742106.591698
|
1793346906.591698
|
|
29720
|
My own site! by @zoomyum | Stardance
|
zoomyum
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zoomyum | Stardance
|
1792648340.9534905
|
1793253140.9534905
|
|
29741
|
My very own WebOS by @zoobie | Stardance
|
zoobie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zoobie | Stardance
|
1792576184.569361
|
1793180984.569361
|
|
61028
|
Frictionless by @zonk0933 | Stardance
|
zonk0933
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @zonk0933 | Stardance
|
1792428805.9872634
|
1793033605.9872634
|
|
64875
|
My very own WebOS by @zombieskulltube | Stardance
|
zombieskulltube
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zombieskulltube | Sta Title: My very own WebOS by @zombieskulltube | Stardance...
|
1792450437.6310868
|
1793055237.6310868
|
|
8503
|
My first slack bot! by @zombieking1555 | Stardance
|
zombieking1555
|
1
|
1.0
|
1
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-07T22:22:33Z", "hours": 1.0, "multiplier": 2.15, "payout": 1, "blessing": "neutral", "text": "I made my own Slack bot following the Stardance mission tutorial. This project, although beginner-level, was a challenge to me. It was my first time working with APIs, Hosting, and generally programming with JavaScript. I am proud of my custom Calendar command; it taught me a lot about working with APIs and allowed me to dip my toes past what was provided for me in the tutorial. My bot should be live using Nest and testable by anyone on Slack!", "repo": "https://github.com/zombieking1555/slack-zombot", "demo": "https://hackclub.enterprise.slack.com/archives/C0APH2MMHH7"}]...
|
[{"post_id": 4562, "ts": "2026 [{"post_id": 4562, "ts": "2026-06-07T22:07:19Z", "hours": 0.6578, "text": "First devlog for a project I’m working on - likely last for this project. I wanted to create this project to learn the flow of creating and shipping for the Stardance challenge. Almost everything I did here was entirely new to me: coding in JS, using API keys and tokens, and SSHing to host my bot on Nest. Luckily, I was able to figure out how to have my coding time properly logged to have enough to devlog. My 37 minutes reflect the time I spent tidying the project for shipment, not the 2 and a half hours spent figuring out how to parse a command into API parameters. This Slack bot was a lot of fun, looking forward to devlogging again on my next project."}]...
|
Title: My first slack bot! by @zombieking1555 | St Title: My first slack bot! by @zombieking1555 | Stardance
Devlogs:
First devlog for a project I’m working on - likely last for this project. I wanted to create this project to learn the flow of creating and shipping for the Stardance challenge. Almost everything I did here was entirely new to me: coding in JS, using API keys and tokens, and SSHing to host my bot on Nest. Luckily, I was able to figure out how to have my coding time properly logged to have enough to devlog. My 37 minutes reflect the time I spent tidying the project for shipment, not the 2 and a half hours spent figuring out how to parse a command into API parameters. This Slack bot was a lot of fun, looking forward to devlogging again on my next project.
Ships:
I made my own Slack bot following the Stardance mission tutorial. This project, although beginner-level, was a challenge to me. It was my first time working with APIs, Hosting, and generally programming with JavaScript. I am proud of my custom Calendar command; it taught me a lot about working with APIs and allowed me to dip my toes past what was provided for me in the tutorial. My bot should be live using Nest and testable by anyone on Slack!...
|
1792838945.9539795
|
1792925345.9539795
|
|
13462
|
FlightScope by @zombieking1555 | Stardance
|
zombieking1555
|
0
|
20.72
|
0
|
[]
|
[{"post_id": 13975, "ts": "202 [{"post_id": 13975, "ts": "2026-06-22T22:49:33Z", "hours": 3.4475, "text": "Devlog 6 - Flight Comparison Dashboard! Overview In this cycle, I expanded FlightScope’s analysis capabilities with a new Flight Comparison Dashboard! Now, users can load in two flights at the same time, comparing trajectories and detected flight events side-by-side. These additions make it endlessly easier to analyze design changes, motor selections, and overall flight performance across multiple launches. What’s New Added a dedicated Flight Comparison Dashboard. Implemented dual-flight visualization for altitude, velocity, and orientation telemetry. Added automatic launch detection and time normalization so flights can be compared from liftoff. Implemented automatic event detection for: Motor burnout Apogee Parachute deployment Landing Added event markers directly onto comparison graphs. Added a Comparison Summary table displaying key event timestamps for both flights side-by-side. Improved dashboard responsiveness by moving admin sidebar initialization outside of rendering bottlenecks. Updated docs and README! By the way, FlightScope is fully public on GitHub , go check it out :) Challenges The challenge this time around was making sure the flight comparison dashboard was actually useful , so I spent some time designing features such as time normalization and side-by-side data viewing to make it very clear to the user where flight differences were present. Next Steps Improve flight render with trajectory path Expand visualization tools with synchronized playback and side-by-side flight rendering. So much progress is being made on this funny little program, I’m so very pleased with how FlightScope is coming along! That’s all for now, folks. See you in #7!"}, {"post_id": 12646, "ts": "2026-06-20T17:37:36Z", "hours": 6.2542, "text": "Devlog 5 - Zenith, Azimuth, and Flight Rendering! Overview This development cycle focused on major new steps to improve the dashboard. The biggest addition was a complete 3D flight reconstruction pipeline capable of calculating rocket orientation from telemetry data and rendering the flight path frame-by-frame. What’s New Implemented zenith and azimuth telemetry support to determine rocket orientation throughout flight. Added a 3D rendering engine capable of visualizing rocket orientation and position over time. Created frame-by-frame flight playback controls directly within the dashboard. Added automatic rendering of flight paths using telemetry stored in the FlightScope database. Combined flight frame renders into video playback, adding an additional layer of visualization to flight analysis. Optimized rendering performance through image caching and improved frame loading behavior. Challenges This chunk of progress was heavy on debugging. The first challenge was reconstructing a realistic rocket orientation from flight data. Position alone wasn’t satisfying in replay, so I implemented zenith and azimuth calculations that adds rotational orientation to the flight replay The biggest issue I had, however, was actually combining flight frames into a video and implementing it on the dashboard. Video formats didn’t treat me well, but I figured out the correct pipeline with lots of trial and error and checks of every step of the system. Next Steps Continue improving rendering performance for larger flights. Expand the visualization system with additional flight annotations and overlays. Improve playback controls and timeline navigation. FlightScope has evolved from plotting telemetry to actually visualizing the flight itself. Seeing a rocket fly through a reconstructed 3D trajectory using real telemetry data is a huge milestone for the project, and I’m excited to keep pushing the visualization tools further."}, {"post_id": 9529, "ts": "2026-06-15T22:02:24Z", "hours": 3.12, "text": "Devlog 4 - UI Overhaul, Resilient Data Importing, and OpenRocket Export Compatibility! Overview I’ve spent more time improving FlightScope’s usability and flexibility, focusing on a cleaner code structure, a more resilient data importing pipeline, and compatibility with OpenRocket simulation exports. What’s New Refactored the backend by separating dashboard, database, and data importing logic into dedicated modules. Improved the CSV upload flow to handle more file formats and clean incoming telemetry automatically. Added compatibility with OpenRocket CSV exports, including automatic unit detection and conversion for feet, meters, and Gs. Added safeguards to flight event detection to make analysis more reliable. Created a GitHub README! Go check it out, it’s linked at the bottom of the devlog :) Challenges Getting OpenRocket compatibility working was more difficult than expected due to differences in column names, units, and CSV formatting. I redesigned the import pipeline to standardize telemetry data before it reaches the database, making FlightScope much more flexible. Next Steps Continue refining the FlightScope UI and overall user experience. Add support for more telemetry formats. Expand flight analysis and visualization tools. Make an online demo for you all to try out! (I could have written another 3 devlogs just about my challenges with this… we will save it for next time.) FlightScope is now fully documented on GitHub: https://github.com/zombieking1555/FlightScope devlog 4 in the bag, now that’s some type stuff. And check this demo:"}, {"post_id": 8127, "ts": "2026-06-13T15:56:50Z", "hours": 3.9747, "text": "Devlog 3 - Flight Simulation Overhaul, Data Trimming, and Flight Event Detection! Overview Spent more time improving FlightScope’s flight data pipeline, with a focus on making the test flights more realistic, trimming extra idle data, and detecting key flight events more reliably. What’s New Reworked the flight simulator to generate more realistic telemetry, including pre-launch idle, boost, coast, parachute descent, and post-landing idle. Added acceleration support throughout the database and telemetry pipeline. Implemented automatic detection and annotation for launch, burnout, apogee, parachute deployment, and landing. Trimmed pre-launch and post-landing idle data so plots focus on the active flight window. Regenerated test flights with updated simulation parameters. Challenges Getting event detection to work reliably took some tuning, especially with noisy acceleration data. Landing detection also needed a little extra care so the plots would stop cleanly at touchdown instead of including a lot of extra idle data. Next Steps Tune detection thresholds more easily from the UI. Add tests for the event detection logic. Continue improving the database and telemetry handling. FlightScope is really coming along! I’m excited to see where this project takes me until the next devlog."}, {"post_id": 5995, "ts": "2026-06-10T01:35:21Z", "hours": 1.5639, "text": "Devlog 2 - Database Initialization, Dashboard Pages, and More! Overview Spent more time developing FlightScope, focusing on improving the local flight database structure and making smaller quality-of-life changes to keep the app scalable and easier to maintain. What’s New Added automatic database initialization so flights.db is created locally instead of being stored in GitHub. Added a Database Manager page to view, manage, and delete individual flight records after upload. Refactored several backend functions to improve consistency and prepare the app for future features. Challenges Removing flights.db from GitHub was more challenging than expected (thanks, .gitignore ). This led to the creation of create_db.py , which removes the dependency on a tracked database file and allows FlightScope to generate a local database automatically on startup. Next Steps Expand the FlightScope dashboard with richer flight analysis and visualization tools. Support additional CSV data fields for more detailed and comprehensive flight reviews. It’s been real, see you next devlog."}, {"post_id": 5158, "ts": "2026-06-08T20:51:05Z", "hours": 2.3578, "text": "Devlog 1 - Streamlit uploader + SQLite storage + basic flight plotting Overview Added a Streamlit app that lets me upload flight CSVs, stores telemetry in a local SQLite database, and plots Altitude vs Time . I also added a small test data script that generates synthetic 200 Hz flight logs so I can quickly test the interface without real rocket data. What’s new Streamlit CSV uploader for flight data SQLite database for storing flight metadata and telemetry Altitude vs Time interactive plot using Plotly Synthetic flight generator ( test_data_writer ) producing 200 Hz test flights Data pipeline Upload CSV → validate → parse numeric values Store flight metadata in flights table Store time-series data in telemetry table Query SQLite → render plots in Streamlit Challenges / friction CSV validation required enforcing numeric types for altitude and velocity Handled missing or invalid data during import Added duplicate filename detection to prevent overwriting flights Admin “Clear Database” flow required Streamlit session_state + rerun handling due to UI reset behavior Design decisions Chose SQLite + pandas for simplicity and local-only operation Avoided external database dependencies to keep setup lightweight Kept CSV import as the ingestion layer for flexibility Added synthetic test data generator to speed up UI development and debugging Next Steps Improve the upload UX (showing row counts and import status) Add per-flight summary stats Allowing CSV export from the database. Having a lot of fun with this project, see you in the next devlog!"}]...
|
Title: FlightScope by @zombieking1555 | Stardance
Title: FlightScope by @zombieking1555 | Stardance
Devlogs:
Devlog 1 - Streamlit uploader + SQLite storage + basic flight plotting Overview Added a Streamlit app that lets me upload flight CSVs, stores telemetry in a local SQLite database, and plots Altitude vs Time . I also added a small test data script that generates synthetic 200 Hz flight logs so I can quickly test the interface without real rocket data. What’s new Streamlit CSV uploader for flight data SQLite database for storing flight metadata and telemetry Altitude vs Time interactive plot using Plotly Synthetic flight generator ( test_data_writer ) producing 200 Hz test flights Data pipeline Upload CSV → validate → parse numeric values Store flight metadata in flights table Store time-series data in telemetry table Query SQLite → render plots in Streamlit Challenges / friction CSV validation required enforcing numeric types for altitude and velocity Handled missing or invalid data during import Added duplicate filename detection to prevent overwriting flights Admin “Clear Database” flow required Streamlit session_state + rerun handling due to UI reset behavior Design decisions Chose SQLite + pandas for simplicity and local-only operation Avoided external database dependencies to keep setup lightweight Kept CSV import as the ingestion layer for flexibility Added synthetic test data generator to speed up UI development and debugging Next Steps Improve the upload UX (showing row counts and import status) Add per-flight summary stats Allowing CSV export from the database. Having a lot of fun with this project, see you in the next devlog!
Devlog 2 - Database Initialization, Dashboard Pages, and More! Overview Spent more time developing FlightScope, focusing on improving the local flight database structure and making smaller quality-of-life changes to keep the app scalable and easier to maintain. What’s New Added automatic database initialization so flights.db is created locally instead of being stored in GitHub. Added a Database Manager page to view, manage, and delete individual flight records after upload. Refactored several backend functions to improve consistency and prepare the app for future features. Challenges Removing flights.db from GitHub was more challenging than expected (thanks, .gitignore ). This led to the creation of create_db.py , which removes the dependency on a tracked database file and allows FlightScope to generate a local database automatically on startup. Next Steps Expand the FlightScope dashboard with richer flight analysis and visualization tools. Support additional CSV data fields for more detailed and comprehensive flight reviews. It’s been real, see you next devlog.
Devlog 3 - Flight Simulation Overhaul, Data Trimming, and Flight Event Detection! Overview Spent more time improving FlightScope’s flight data pipeline, with a focus on making the test flights more realistic, trimming extra idle data, and detecting key flight events more reliably. What’s New Reworked the flight simulator to generate more realistic telemetry, including pre-launch idle, boost, coast, parachute descent, and post-landing idle. Added acceleration support throughout the database and telemetry pipeline. Implemented automatic detection and annotation for launch, burnout, apogee, parachute deployment, and landing. Trimmed pre-launch and post-landing idle data so plots focus on the active flight window. Regenerated test flights with updated simulation parameters. Challenges Getting event detection to work reliably took some tuning, especially with noisy acceleration data. Landing detection also needed a little extra care so the plots would stop cleanly at touchdown instead of including a lot of extra idle data. Next Steps Tune detection thresholds more easily from the UI. Add tests for the event detection logic. Continue improving the database and telemetry handling. FlightScope is really coming along! I’m excited to see where this project takes me until the next devlog.
Devlog 4 - UI Overhaul, Resilient Data Importing, and OpenRocket Export Compatibility! Overview I’ve spent more time improving FlightScope’s usability and flexibility, focusing on a cleaner code structure, a more resilient data importing pipeline, and compatibility with OpenRocket simulation exports. What’s New Refactored the backend by separating dashboard, database, and data importing logic into dedicated modules. Improved the CSV upload flow to handle more file formats and clean incoming telemetry automatically. Added compatibility with OpenRocket CSV exports, including automatic unit detection and conversion for feet, meters, and Gs. Added safeguards to flight event detection to make analysis more reliable. Created a GitHub README! Go check it out, it’s linked at the bottom of the devlog :) Challenges Getting OpenRocket compatibility working was more difficult than expected due to differences in column names, units, and CSV formatting. I redesigned the import pipeline to standardize telemetry data before it reaches the database, making FlightScope much more flexible. Next Steps Continue refining the FlightScope UI and overall user experience. Add support for more telemetry formats. Expand flight analysis and visualization tools. Make an online demo for you all to try out! (I could have written another 3 devlogs just about my challenges with this… we will save it for next time.) FlightScope is now fully documented on GitHub: https://github.com/zombieking1555/FlightScope devlog 4 in the bag, now that’s some type stuff. And check this demo:
Devlog 5 - Zenith, Azimuth, and Flight Rendering! Overview This development cycle focused on major new steps to improve the dashboard. The biggest addition was a complete 3D flight reconstruction pipeline capable of calculating rocket orientation from telemetry data and rendering the flight path frame-by-frame. What’s New Implemented zenith and azimuth telemetry support to determine rocket orientation throughout flight. Added a 3D rendering engine capable of visualizing rocket orientation and position over time. Created frame-by-frame flight playback controls directly within the dashboard. Added automatic rendering of flight paths using telemetry stored in the FlightScope database. Combined flight frame renders into video playback, adding an additional layer of visualization to flight analysis. Optimized rendering performance through image caching and improved frame loading behavior. Challenges This chunk of progress was heavy on debugging. The first challenge was reconstructing a realistic rocket orientation from flight data. Position alone wasn’t satisfying in replay, so I implemented zenith and azimuth calculations that adds rotational orientation to the flight replay The biggest issue I had, however, was actually combining flight frames into a video and implementing it on the dashboard. Video formats didn’t treat me well, but I figured out the correct pipeline with lots of trial and error and checks of every step of the system. Next Steps Continue improving rendering performance for larger flights. Expand the visualization system with additional flight annotations and overlays. Improve playback controls and timeline navigation. FlightScope has evolved from plotting telemetry to actually visualizing the flight itself. Seeing a rocket fly through a reconstructed 3D trajectory using real telemetry data is a huge milestone for the project, and I’m excited to keep pushing the visualization tools further.
Devlog 6 - Flight Comparison Dashboard! Overview In this cycle, I expanded FlightScope’s analysis capabilities with a new Flight Comparison Dashboard! Now, users can load in two flights at the same time, comparing trajectories and detected flight events side-by-side. These additions make it endlessly easier to analyze design changes, motor selections, and overall flight performance across multiple launches. What’s New Added a dedicated Flight Comparison Dashboard. Implemented dual-flight visualization for altitude, velocity, and orientation telemetry. Added automatic launch detection and time normalization so flights can be compared from liftoff. Implemented automatic event detection for: Motor burnout Apogee Parachute deployment Landing Added event markers directly onto comparison graphs. Added a Comparison Summary table displaying key event timestamps for both flights side-by-side. Improved dashboard responsiveness by moving admin sidebar initialization outside of rendering bottlenecks. Updated docs and README! By the way, FlightScope is fully public on GitHub , go check it out :) Challenges The challenge this time around was making sure the flight comparison dashboard was actually useful , so I spent some time designing features such as time normalization and side-by-side data viewing to make it very clear to the user where flight differences were present. Next Steps Improve flight render with trajectory path Expand visualization tools with synchronized playback and side-by-side flight rendering. So much progress is being made on this funny little program, I’m so very pleased with how FlightScope is coming along! That’s all for now, folks. See you in #7!...
|
1792662510.1481156
|
1793267310.1481156
|
|
24762
|
FlightScope FlightCore by @zombieking1555 | Starda FlightScope FlightCore by @zombieking1555 | Stardance...
|
zombieking1555
|
0
|
33.41
|
0
|
[]
|
[{"post_id": 67001, "ts": "202 [{"post_id": 67001, "ts": "2026-09-13T01:05:58Z", "hours": 5.9664, "text": "Devlog 7 - FlightCore CAD + Testing Hi again! Since the last devlog, I’ve been working a lot on getting CAD finalized so that printing and assembly can start. With the Flight Computer Tentatively Complete in CAD and more external testing done, FlightScope as a whole is progressing great! FlightCore is shown in the image below. Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope"}, {"post_id": 50321, "ts": "2026-08-19T14:19:26Z", "hours": 4.0847, "text": "Devlog 6 - IT WORKS! Flight computer v1 built I put together real hardware, deployed my code, and waved it around in the air for a little while, and we recorded real data that proves this thing will work. Take a look at the pictures! New Since Last Time The first order of supplies came in, including a lot of flight computer hardware. After a little research and planning, I got the hardware all soldered up. Wrestling with the software program was a blast, and I’m proud to say that Flightscope Flightcore has recorded its first “flight”. What’s next I’m going to be researching for part 2 of the flight computer, aka the ejection charge handler. Hopefully in my next devlog, I don’t have to report any explosions… Conclusion Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope Take a look at the “flight” below (Aka me swinging the flight computer around in the air, then setting it down)!"}, {"post_id": 43648, "ts": "2026-08-09T01:10:46Z", "hours": 6.3414, "text": "Devlog 5 - Giving My Avionics Bay The Love it Deserves & FUNDING It’s been a while, but I’m back at it! I put in a lot more work on the avionics bay, and it’s starting to look like something that would actually work. Always a good sign. AND THERE’S MORE - I notice a new devlog feature, Read more to find out… FlightScope If you’re new here, this is the hardware side of my big summer project, FlightScope. You can find my work on the software side of FlightScope here: https://stardance.hackclub.com/projects/13462 What’s Next There is more time to spend on this CAD before the rocket is complete! In parallel, FlightCore Is Officially Funded! Expect some IRL devlogs soon :) Conclusion Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope"}, {"post_id": 24940, "ts": "2026-07-08T20:30:46Z", "hours": 4.5242, "text": "Devlog 4: If I built my rocket using my CAD, it would nosedive straight into the ground… Overview Hey everybody! Rocket CAD is closing in on completion! I’m still missing some pretty important aerodynamic pieces, but I’ve been able to get some good work done that I’m here to tell you all about! FlightScope If you’re new here, this is the hardware side of my big summer project, FlightScope. You can find my work on the software side of FlightScope here: https://stardance.hackclub.com/projects/13462 What’s New This week I made major progress on the rocket CAD. The biggest improvement was on the FlightCore Avionics bay. The layout is much more finalized, as I’ve designed in for more stability and even added the power switch! Now I can actually turn this thing on, which is a nice step in the right direction Beyond that, I’ve started fitting subassemblies together, getting a sense for packaging on the rocket. See some pictures of it at the bottom of the devlog :) What’s Next The biggest remaining task is designing the fins. Before I commit to a final shape, I’ll be running some simulations to find what allows for the best stability. Conclusion Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope"}, {"post_id": 20022, "ts": "2026-07-01T14:57:43Z", "hours": 1.9956, "text": "Devlog 3 - Avionics Bay V2 Overview Hey everybody! This cycle, I’ve shifted my focus from software to hardware. After getting FlightCore’s subsystem code into a good place, it was time to redesign the avionics bay around the actual components that will be flying. FlightScope If you’re new here, this is the hardware side of my big summer project, FlightScope. You can find my work on the software side of FlightScope here: https://stardance.hackclub.com/projects/13462 What’s New This week I designed the second revision of the FlightCore avionics bay in Onshape. See it in the video at the bottom of the devlog! The redesign includes: A much cleaner component layout. Mounting locations for every PCB. Better spacing for wiring and connectors. A compact sled that fits inside the avionics coupler while keeping everything accessible. What’s Next Now that the avionics bay design is mostly complete, the next step is to finish up the rest of the rocket CAD. Hopefully, I’ll also be ordering FlightCore avionics very soon so test-fit everything and begin validating the software on the actual hardware. Conclusion Thanks for making it this far! If you like what you see, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope"}, {"post_id": 18780, "ts": "2026-06-29T23:58:21Z", "hours": 5.9756, "text": "Devlog 2 - Software Progress Overview Hey everybody, I’ve been on vacation and haven’t been fully locked on Stardance, but I’ve still been able to get some work in that I would love to share with you all. Flightscope If you’re new here, this is the hardware side of my big summer project, Flightscope. Find my other work in this project . What’s New In this chunk of work. I have (for now) completed the subsystem code for FlightCore (my flight computer, powered by an RPi Pico 2). Here is a map of how the program works: ┌────────┐ │ LiPo Battery │ └────┬───┘ │ ▼ ┌───── ───────┐ │ Raspberry Pi Pico 2│ └──────┬── ───┘ │ ┌─────┼──────┐ ▼ ▼ ▼ ┌───┐ ┌────┐ ┌─── ──┐ │ IMU │ │ BMP │ │ microSD│ │Accel│ │Altim. │ │ Logger │ └─┬─┘ └─┬──┘ └──┬── ┘ └── ──┼ ──────┘ ▼ Sample Sensors (200 Hz) │ ▼ Pre-launch Ring Buffer │ ▼ Launch Detection Logic │ ▼ Flight State Machine │ Boost → Coast → Descent │ ▼ Write Flight CSV │ ▼ FlightScope Dashboard │ ▼ Graphs • 3D Replay • Analysis Conclusion Flightcore is making some great progress on the software side, and here’s a picture of the fun I’m having in Onshape designing the avionics sled! Look out for that in the next devlog. Thanks for getting this far! I would love to see what cool things you guys are working on too. Leave a comment, and I would love to check out your projects! Edit: I apologize for the attachment spam, I can’t find the option to delete them."}, {"post_id": 15438, "ts": "2026-06-25T02:48:31Z", "hours": 4.5269, "text": "Devlog 1 - Welcome To FlightCore Overview What’s up, guys! If you have been following my other project, FlightScope, the name of this project will ring a bell. This is the hardware extension for FlightScope, so I can get real data and actually test the app. What am I actually building? FlightCore has 2 main parts: The Flight Computer, which is what is going to collect the flight data and will be housed inside number 2…. A Rocket! I’ll be building a (most likely) low-power rocket that will bring FlightCore up into the sky. With all that out of the way, I’ll tell you what I’ve got done in this first chunk of time. What’s New Began modeling the electronics sled and other rocket parts with Onshape Initialized FlightCores codebase with sensor initialization. P.S. - The GitHub is public! I’ll be storing everything about this project right here . Challenges This project is full of challenges! To name a few: This is my first hardware project, and putting all the electronics I plan to use together is going to be a big one in itself. I haven’t ever used CAD software before (I apologize if my CAD is horrendous. I’m trying, I promise), so modeling everything in Onshape is fun! I’m programming the flight computer with new libraries that are brand new to me, not to mention using C++, which is also something I haven’t used yet. I’m basically jumping off a helicopter into an ocean without knowing how to swim, but the great part about it is I sure will learn a lot and fast! Next Steps Program up the other sensors in the flight computer Figure out how I’m actually going to log the data that these sensors are giving me Continue modeling the rocket and electronics sled in CAD And that’s a wrap for devlog 1! As I’ve said, this project really does have me learning along the way. Any advice would be much appreciated! With that said, I’ll see you all in the next one. See progress on the electronics sled:"}]...
|
Title: FlightScope FlightCore by @zombieking1555 | Title: FlightScope FlightCore by @zombieking1555 | Stardance
Devlogs:
Devlog 1 - Welcome To FlightCore Overview What’s up, guys! If you have been following my other project, FlightScope, the name of this project will ring a bell. This is the hardware extension for FlightScope, so I can get real data and actually test the app. What am I actually building? FlightCore has 2 main parts: The Flight Computer, which is what is going to collect the flight data and will be housed inside number 2…. A Rocket! I’ll be building a (most likely) low-power rocket that will bring FlightCore up into the sky. With all that out of the way, I’ll tell you what I’ve got done in this first chunk of time. What’s New Began modeling the electronics sled and other rocket parts with Onshape Initialized FlightCores codebase with sensor initialization. P.S. - The GitHub is public! I’ll be storing everything about this project right here . Challenges This project is full of challenges! To name a few: This is my first hardware project, and putting all the electronics I plan to use together is going to be a big one in itself. I haven’t ever used CAD software before (I apologize if my CAD is horrendous. I’m trying, I promise), so modeling everything in Onshape is fun! I’m programming the flight computer with new libraries that are brand new to me, not to mention using C++, which is also something I haven’t used yet. I’m basically jumping off a helicopter into an ocean without knowing how to swim, but the great part about it is I sure will learn a lot and fast! Next Steps Program up the other sensors in the flight computer Figure out how I’m actually going to log the data that these sensors are giving me Continue modeling the rocket and electronics sled in CAD And that’s a wrap for devlog 1! As I’ve said, this project really does have me learning along the way. Any advice would be much appreciated! With that said, I’ll see you all in the next one. See progress on the electronics sled:
Devlog 2 - Software Progress Overview Hey everybody, I’ve been on vacation and haven’t been fully locked on Stardance, but I’ve still been able to get some work in that I would love to share with you all. Flightscope If you’re new here, this is the hardware side of my big summer project, Flightscope. Find my other work in this project . What’s New In this chunk of work. I have (for now) completed the subsystem code for FlightCore (my flight computer, powered by an RPi Pico 2). Here is a map of how the program works: ┌────────┐ │ LiPo Battery │ └────┬───┘ │ ▼ ┌───── ───────┐ │ Raspberry Pi Pico 2│ └──────┬── ───┘ │ ┌─────┼──────┐ ▼ ▼ ▼ ┌───┐ ┌────┐ ┌─── ──┐ │ IMU │ │ BMP │ │ microSD│ │Accel│ │Altim. │ │ Logger │ └─┬─┘ └─┬──┘ └──┬── ┘ └── ──┼ ──────┘ ▼ Sample Sensors (200 Hz) │ ▼ Pre-launch Ring Buffer │ ▼ Launch Detection Logic │ ▼ Flight State Machine │ Boost → Coast → Descent │ ▼ Write Flight CSV │ ▼ FlightScope Dashboard │ ▼ Graphs • 3D Replay • Analysis Conclusion Flightcore is making some great progress on the software side, and here’s a picture of the fun I’m having in Onshape designing the avionics sled! Look out for that in the next devlog. Thanks for getting this far! I would love to see what cool things you guys are working on too. Leave a comment, and I would love to check out your projects! Edit: I apologize for the attachment spam, I can’t find the option to delete them.
Devlog 3 - Avionics Bay V2 Overview Hey everybody! This cycle, I’ve shifted my focus from software to hardware. After getting FlightCore’s subsystem code into a good place, it was time to redesign the avionics bay around the actual components that will be flying. FlightScope If you’re new here, this is the hardware side of my big summer project, FlightScope. You can find my work on the software side of FlightScope here: https://stardance.hackclub.com/projects/13462 What’s New This week I designed the second revision of the FlightCore avionics bay in Onshape. See it in the video at the bottom of the devlog! The redesign includes: A much cleaner component layout. Mounting locations for every PCB. Better spacing for wiring and connectors. A compact sled that fits inside the avionics coupler while keeping everything accessible. What’s Next Now that the avionics bay design is mostly complete, the next step is to finish up the rest of the rocket CAD. Hopefully, I’ll also be ordering FlightCore avionics very soon so test-fit everything and begin validating the software on the actual hardware. Conclusion Thanks for making it this far! If you like what you see, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope
Devlog 4: If I built my rocket using my CAD, it would nosedive straight into the ground… Overview Hey everybody! Rocket CAD is closing in on completion! I’m still missing some pretty important aerodynamic pieces, but I’ve been able to get some good work done that I’m here to tell you all about! FlightScope If you’re new here, this is the hardware side of my big summer project, FlightScope. You can find my work on the software side of FlightScope here: https://stardance.hackclub.com/projects/13462 What’s New This week I made major progress on the rocket CAD. The biggest improvement was on the FlightCore Avionics bay. The layout is much more finalized, as I’ve designed in for more stability and even added the power switch! Now I can actually turn this thing on, which is a nice step in the right direction Beyond that, I’ve started fitting subassemblies together, getting a sense for packaging on the rocket. See some pictures of it at the bottom of the devlog :) What’s Next The biggest remaining task is designing the fins. Before I commit to a final shape, I’ll be running some simulations to find what allows for the best stability. Conclusion Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope
Devlog 5 - Giving My Avionics Bay The Love it Deserves & FUNDING It’s been a while, but I’m back at it! I put in a lot more work on the avionics bay, and it’s starting to look like something that would actually work. Always a good sign. AND THERE’S MORE - I notice a new devlog feature, Read more to find out… FlightScope If you’re new here, this is the hardware side of my big summer project, FlightScope. You can find my work on the software side of FlightScope here: https://stardance.hackclub.com/projects/13462 What’s Next There is more time to spend on this CAD before the rocket is complete! In parallel, FlightCore Is Officially Funded! Expect some IRL devlogs soon :) Conclusion Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope
Devlog 6 - IT WORKS! Flight computer v1 built I put together real hardware, deployed my code, and waved it around in the air for a little while, and we recorded real data that proves this thing will work. Take a look at the pictures! New Since Last Time The first order of supplies came in, including a lot of flight computer hardware. After a little research and planning, I got the hardware all soldered up. Wrestling with the software program was a blast, and I’m proud to say that Flightscope Flightcore has recorded its first “flight”. What’s next I’m going to be researching for part 2 of the flight computer, aka the ejection charge handler. Hopefully in my next devlog, I don’t have to report any explosions… Conclusion Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope Take a look at the “flight” below (Aka me swinging the flight computer around in the air, then setting it down)!
Devlog 7 - FlightCore CAD + Testing Hi again! Since the last devlog, I’ve been working a lot on getting CAD finalized so that printing and assembly can start. With the Flight Computer Tentatively Complete in CAD and more external testing done, FlightScope as a whole is progressing great! FlightCore is shown in the image below. Thanks for making it this far! If you’d like to follow along, check out the projects on GitHub or give me a follow! FlightCore Repo: https://github.com/zombieking1555/FlightScope_FlightComputer FlightScope Dashboard Repo: https://github.com/zombieking1555/FlightScope...
|
1792680629.6909533
|
1793285429.6909533
|
|
42736
|
Zolt first project by @zolt | Stardance
|
zolt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Zolt first project by @zolt | Stardance
|
1792522084.8309238
|
1793126884.8309238
|
|
51910
|
ElectroGAN: A Physics-Aware GAN for Cyclic Voltamm ElectroGAN: A Physics-Aware GAN for Cyclic Voltammetry by @zoll_800 | Stardance...
|
zoll_800
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ElectroGAN: A Physics-Aware GAN for Cyclic Title: ElectroGAN: A Physics-Aware GAN for Cyclic Voltammetry by @zoll_800 | Stardance...
|
1792688090.330133
|
1793292890.330133
|