|
44850
|
My very own WebOS by @zzz_ | Stardance
|
zzz_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zzz_ | Stardance
|
1792601670.2824814
|
1793206470.2824814
|
|
44851
|
Dimensiun by @zzz_ | Stardance
|
zzz_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Dimensiun by @zzz_ | Stardance
|
1792601671.138004
|
1793206471.138004
|
|
59334
|
WarioWare Game by @zzz | Stardance
|
zzz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @zzz | Stardance
|
1792795639.1104343
|
1793400439.1104343
|
|
65288
|
My awesome macropad! by @zzng | Stardance
|
zzng
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zzng | Stardance
|
1792453890.8169599
|
1793058690.8169599
|
|
9378
|
thoroutine by @zzbytes | Stardance
|
zzbytes
|
0
|
2.07
|
0
|
[]
|
[{"post_id": 4364, "ts": "2026 [{"post_id": 4364, "ts": "2026-06-07T17:39:30Z", "hours": 2.0736, "text": "Just got done with the base of my threading/coroutine library, but still a long way away from it being completed! It’s supposed to be cross-platform, though only Linux is supported as of currently (I know, cross-platform library being platform locked is ironic)."}]...
|
Title: thoroutine by @zzbytes | Stardance
Devlogs Title: thoroutine by @zzbytes | Stardance
Devlogs:
Just got done with the base of my threading/coroutine library, but still a long way away from it being completed! It’s supposed to be cross-platform, though only Linux is supported as of currently (I know, cross-platform library being platform locked is ironic)....
|
1792774388.2061894
|
1793379188.2061894
|
|
27211
|
A: Programming Language by @zzbytes | Stardance
|
zzbytes
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A: Programming Language by @zzbytes | Stard Title: A: Programming Language by @zzbytes | Stardance...
|
1792515259.326255
|
1793120059.326255
|
|
54360
|
Untitled project by @zz222157 | Stardance
|
zz222157
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @zz222157 | Stardance
|
1791825719.779214
|
1792689719.779214
|
|
33118
|
Birdie feeder bot by @zyxtai_0 | Stardance
|
zyxtai_0
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Birdie feeder bot by @zyxtai_0 | Stardance
|
1792526132.5824955
|
1793130932.5824955
|
|
66839
|
a website by @zynix | Stardance
|
zynix
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: a website by @zynix | Stardance
|
1792461278.4469109
|
1793066078.4469109
|
|
67070
|
Zynix Portfolio by @zynix | Stardance
|
zynix
|
0
|
0.28
|
0
|
[]
|
[{"post_id": 75644, "ts": "202 [{"post_id": 75644, "ts": "2026-09-30T17:08:02Z", "hours": 0.2817, "text": "Day 1 :i started making my website using html and css .i used html to make pages (made 4 page) and css for making text and navbar colourfull"}]...
|
Title: Zynix Portfolio by @zynix | Stardance
Devl Title: Zynix Portfolio by @zynix | Stardance
Devlogs:
Day 1 :i started making my website using html and css .i used html to make pages (made 4 page) and css for making text and navbar colourfull...
|
1792464600.5361652
|
1793069400.5361652
|
|
39211
|
MGSC Website by @zyluxXD | Stardance
|
zyluxXD
|
0
|
1.19
|
0
|
[]
|
[{"post_id": 34282, "ts": "202 [{"post_id": 34282, "ts": "2026-07-24T21:09:15Z", "hours": 1.1872, "text": "Finished the basic site structure, will add anims and other things."}]...
|
Title: MGSC Website by @zyluxXD | Stardance
Devlo Title: MGSC Website by @zyluxXD | Stardance
Devlogs:
Finished the basic site structure, will add anims and other things....
|
1792738359.2902968
|
1793343159.2902968
|
|
39303
|
My own site! by @zyluxXD | Stardance
|
zyluxXD
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zyluxXD | Stardance
|
1792784993.9575737
|
1793389793.9575737
|
|
39374
|
notsponsored by @zyluxXD | Stardance
|
zyluxXD
|
0
|
8.0
|
0
|
[]
|
[{"post_id": 37762, "ts": "202 [{"post_id": 37762, "ts": "2026-07-30T17:55:50Z", "hours": 1.0, "text": "Bugs. bugs. bugs. Literally the most annoying things ever, both in real life and in programming. Watched YouTube videos, found ones w/ sponsors, and if it wasn’t detected by the local detection, fix it. Fixed bug where SponsorBlock-based detection was making the skipping not work. And I also added this lil popup window that lets you customize from where detections are, as well as a inwards time trim. The inwards time trim is nice because its customizable and lets you see just a little bit of the sponsor part, so you don’t miss any other content."}, {"post_id": 37320, "ts": "2026-07-29T22:48:36Z", "hours": 2.0, "text": "I added part of the UI (yay!!!!). Now when a sponsor is upcoming, this little popup shows. If you click any button, it disappears and doesn’t skip the sponsor. (Also yes that’s a Minecraft video in the background) I still need to add the main UI and some other stuff. Other things I did: Fixed random bug in local detection Fixed bug where no skipping occurs if a ad had previously played"}, {"post_id": 36564, "ts": "2026-07-28T19:21:58Z", "hours": 5.0, "text": "Finally finished the local detection algorithm! this took quite a while to do, and this wasn’t even the first algorithm I had to make for this. So originally, I made a thing where it loads a small sentence transformer in the background, and uses the video transcript to create vector embedding, on which it uses for detection. This worked sometimes, but it also failed a lot of the times. I kinda gave up on that approach since it didn’t seem like it was going to go anywhere, so instead I decided to build a non-ml version that uses hysterics and an analysis algorithm to find out segments that are sponsors. But this algorithm is just a backup, as the main source of detection is the existing SponsorBlock API, which uses user reports to skip video sponsors. However, as this can’t work for any video, the local fallback is there! I also made it be able to actually skip a sponsored segment too. Next steps are probably adding a UI, improving extension frontend, improving browser support, and making it more robust. (rn the photo is just the extension loaded in because it doesn’t have a UI yet)"}]...
|
Title: notsponsored by @zyluxXD | Stardance
Devlo Title: notsponsored by @zyluxXD | Stardance
Devlogs:
Finally finished the local detection algorithm! this took quite a while to do, and this wasn’t even the first algorithm I had to make for this. So originally, I made a thing where it loads a small sentence transformer in the background, and uses the video transcript to create vector embedding, on which it uses for detection. This worked sometimes, but it also failed a lot of the times. I kinda gave up on that approach since it didn’t seem like it was going to go anywhere, so instead I decided to build a non-ml version that uses hysterics and an analysis algorithm to find out segments that are sponsors. But this algorithm is just a backup, as the main source of detection is the existing SponsorBlock API, which uses user reports to skip video sponsors. However, as this can’t work for any video, the local fallback is there! I also made it be able to actually skip a sponsored segment too. Next steps are probably adding a UI, improving extension frontend, improving browser support, and making it more robust. (rn the photo is just the extension loaded in because it doesn’t have a UI yet)
I added part of the UI (yay!!!!). Now when a sponsor is upcoming, this little popup shows. If you click any button, it disappears and doesn’t skip the sponsor. (Also yes that’s a Minecraft video in the background) I still need to add the main UI and some other stuff. Other things I did: Fixed random bug in local detection Fixed bug where no skipping occurs if a ad had previously played
Bugs. bugs. bugs. Literally the most annoying things ever, both in real life and in programming. Watched YouTube videos, found ones w/ sponsors, and if it wasn’t detected by the local detection, fix it. Fixed bug where SponsorBlock-based detection was making the skipping not work. And I also added this lil popup window that lets you customize from where detections are, as well as a inwards time trim. The inwards time trim is nice because its customizable and lets you see just a little bit of the sponsor part, so you don’t miss any other content....
|
1791823825.132639
|
1792687825.132639
|
|
39799
|
start by @zyluxXD | Stardance
|
zyluxXD
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-26T00:04:11Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made Start, a minimalist and clean New Tab page for any browser. It uses NASA APOD as the background image. It also includes the current time (in 24HR format) with the background image title below, and has a bookmark manager for quick website access.", "repo": "https://github.com/ZyluxXD/start", "demo": "https://zyluxxd.github.io/start/"}]...
|
[{"post_id": 34897, "ts": "202 [{"post_id": 34897, "ts": "2026-07-26T00:00:42Z", "hours": 0.3578, "text": "Finished the README, uploaded to GitHub, and deployed the page."}, {"post_id": 34887, "ts": "2026-07-25T23:30:54Z", "hours": 1.2747, "text": "Devlog #2 I polished the website CSS a lot, and added a copyright. I also added a bookmarks system for websites. I also added a loading screen that shows until the image is loaded. Got the help of Codex to fix a weird GPU rendering bug on the blur effect behind the text."}, {"post_id": 34853, "ts": "2026-07-25T21:50:36Z", "hours": 0.4864, "text": "Devlog #1 Completed the basic structure, aswell as the time, image, image info, and image title."}]...
|
Title: start by @zyluxXD | Stardance
Devlogs:
Dev Title: start by @zyluxXD | Stardance
Devlogs:
Devlog #1 Completed the basic structure, aswell as the time, image, image info, and image title.
Devlog #2 I polished the website CSS a lot, and added a copyright. I also added a bookmarks system for websites. I also added a loading screen that shows until the image is loaded. Got the help of Codex to fix a weird GPU rendering bug on the blur effect behind the text.
Finished the README, uploaded to GitHub, and deployed the page.
Ships:
I made Start, a minimalist and clean New Tab page for any browser. It uses NASA APOD as the background image. It also includes the current time (in 24HR format) with the background image title below, and has a bookmark manager for quick website access....
|
1792835539.0776663
|
1792921939.0776663
|
|
55984
|
MDS by @zyluxXD | Stardance
|
zyluxXD
|
1
|
16.0
|
210
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-08T04:49:43Z", "hours": 16.0, "multiplier": 13.31, "payout": 210, "blessing": "neutral", "text": "I made MDS (Meme Delivery Service), a Python Slack bot that fetches programming memes from ProgrammerHumor! It can post a daily batch automatically, or you can use /memes to request anywhere from 1–10 memes from the home, hot, random, or search feeds. There’s also optional LLM moderation and a Show sources button that links back to the original memes! While making this, there were quite a few moving parts to connect, such as scraping the memes, downloading the images, and uploading them to Slack. Handling errors were quite tedious aswell, including unavailable images, moderation errors, and commands used in channels where the bot hasn’t been invited. Overall, I’m happy with how the whole posting system came together! Daily posts interweave the home and hot feeds, and you can configure the schedule, cooldowns, and moderation. Memes :) Anyways, you, yes YOU should try it TODAY, RIGHT NOW. Just join #mds-playground on the Hack Club Slack and check the pinned message! Ty for reading this :D", "repo": "https://github.com/ZyluxXD/MDS", "demo": "https://app.slack.com/client/E09V59WQY1E/C0C6TQZGQ95"}]...
|
[{"post_id": 77741, "ts": "202 [{"post_id": 77741, "ts": "2026-10-08T04:22:20Z", "hours": 0.4175, "text": "Last minute bugfixing!!!! I’m sure all of y’all had atleast one experience before where you discovered a new bug AFTER finalizing everything . That just happened to me when I realized if MDS isn’t in a channel, it just ghosts you and leaves a error in the console. Yeah, not great, so I added this nice little message if that happens, and also just improved a lil bit of the reliability on the slack side of things. Ready to ship, I think"}, {"post_id": 77454, "ts": "2026-10-07T02:16:13Z", "hours": 6.4686, "text": "Spaghetti and bugs really don’t go well together. Don’t believe me? Try it out… Yeah, you see now? So that is precisely why I cleared out the spaghetti and bugs out of my code! Yes. That took a long time. So basically, I reorganized the fetching, moderation, downloading, and Slack posting code so it is actually readable. I also replaced the scattered dictionaries with actual data models and cleaned up how settings are loaded and checked. Less guessing what some random variable contains. Yay!! On the actual bot side, images now download in parallel, broken or oversized downloads get skipped, and /memes has configurable cooldowns for users and channels. I also improved the source button’s link back to the uploaded post, made the daily posting time configurable, and added separate moderation controls for daily posts and slash commands. All those boring things that suddenly become very interesting when they break And last and probably least , I wrote a README with installation instructions, configuration details, and command examples, added an example .env file and license, and gave MDS a logo and banner! So now you can actually figure out how to run it without having to read through all my code first. well you probably could read it now after the refactor You’re welcome. Anyways, MDS is getting pretty close to being ready to ship!!"}, {"post_id": 66271, "ts": "2026-09-12T00:34:20Z", "hours": 2.4236, "text": "Well, well, well. Look who we have here. (You, reading this devlog). So what I did this time was add the slash commands! Yay!! So basically now there is a ‘/memes’ command that lets you summon a collection of memes in your current channel! You can specify what page of ProgrammerHumor you want it from (like home, hot, random), or you can use a search query! Also I kinda messed up my git, as in my last 2 commits I forgot to actually add the files, so I guess I now have two less commits. Anyways, I also improved reliability, logging, and all those boring things."}, {"post_id": 63213, "ts": "2026-09-06T21:52:10Z", "hours": 2.1831, "text": "After getting ragebaited by LangChain for a while, I’m happy to announce that I have finally completed the LLM moderation feature. Now you can finally rest assured that the memes being sent are appropriate! It is off by default, since you obviously need an llm endpoint to use it, but it is nice to have! Later I may add a setting to control how strict the moderation is. I additionally improved the overall reliability of the app, and made it easier to use as well as easier to understand what’s going on!"}, {"post_id": 59908, "ts": "2026-09-01T22:49:44Z", "hours": 1.7822, "text": "LLMs, the cause of the ram shortage, are now a vital (kinda) part of my app. So basically in the about 2 hours ish of this devlog, I managed to implement the first half of the LLM moderation & ranking feature. I first using the OpenAI API, but then switched to langchain to allow support for other API specifications! But yeah, this feature is pretty time consuming to implement… Also, the screenshot this time is just some code as I don’t wanna add yet another screenshot of the app, with the LLM feature not even implemented yet."}, {"post_id": 57717, "ts": "2026-08-29T23:40:13Z", "hours": 1.1853, "text": "Waiter waiter, more upgrades! Alright, so before I jump to the complicated stuff, I just improved the overall code structure by making it more readable and spread apart, added better logging capabilities, as well as added the core feature: scheduled meme posting, and finally, improved the source links button & overall reliability."}, {"post_id": 57628, "ts": "2026-08-29T20:41:34Z", "hours": 1.3381, "text": "Finished the basic structure of the Slack bot; I got it working and posting memes along with a basic scraper, and a sources button. This is a very basic demo for now, there is so much more to come!"}]...
|
Title: MDS by @zyluxXD | Stardance
Devlogs:
Finis Title: MDS by @zyluxXD | Stardance
Devlogs:
Finished the basic structure of the Slack bot; I got it working and posting memes along with a basic scraper, and a sources button. This is a very basic demo for now, there is so much more to come!
Waiter waiter, more upgrades! Alright, so before I jump to the complicated stuff, I just improved the overall code structure by making it more readable and spread apart, added better logging capabilities, as well as added the core feature: scheduled meme posting, and finally, improved the source links button & overall reliability.
LLMs, the cause of the ram shortage, are now a vital (kinda) part of my app. So basically in the about 2 hours ish of this devlog, I managed to implement the first half of the LLM moderation & ranking feature. I first using the OpenAI API, but then switched to langchain to allow support for other API specifications! But yeah, this feature is pretty time consuming to implement… Also, the screenshot this time is just some code as I don’t wanna add yet another screenshot of the app, with the LLM feature not even implemented yet.
After getting ragebaited by LangChain for a while, I’m happy to announce that I have finally completed the LLM moderation feature. Now you can finally rest assured that the memes being sent are appropriate! It is off by default, since you obviously need an llm endpoint to use it, but it is nice to have! Later I may add a setting to control how strict the moderation is. I additionally improved the overall reliability of the app, and made it easier to use as well as easier to understand what’s going on!
Well, well, well. Look who we have here. (You, reading this devlog). So what I did this time was add the slash commands! Yay!! So basically now there is a ‘/memes’ command that lets you summon a collection of memes in your current channel! You can specify what page of ProgrammerHumor you want it from (like home, hot, random), or you can use a search query! Also I kinda messed up my git, as in my last 2 commits I forgot to actually add the files, so I guess I now have two less commits. Anyways, I also improved reliability, logging, and all those boring things.
Spaghetti and bugs really don’t go well together. Don’t believe me? Try it out… Yeah, you see now? So that is precisely why I cleared out the spaghetti and bugs out of my code! Yes. That took a long time. So basically, I reorganized the fetching, moderation, downloading, and Slack posting code so it is actually readable. I also replaced the scattered dictionaries with actual data models and cleaned up how settings are loaded and checked. Less guessing what some random variable contains. Yay!! On the actual bot side, images now download in parallel, broken or oversized downloads get skipped, and /memes has configurable cooldowns for users and channels. I also improved the source button’s link back to the uploaded post, made the daily posting time configurable, and added separate moderation controls for daily posts and slash commands. All those boring things that suddenly become very interesting when they break And last and probably least , I wrote a README with installation instructions, configuration details, and command examples, added an example .env file and license, and gave MDS a logo and banner! So now you can actually figure out how to run it without having to read through all my code first. well you probably could read it now after the refactor You’re welcome. Anyways, MDS is getting pretty close to being ready to ship!!
Last minute bugfixing!!!! I’m sure all of y’all had atleast one experience before where you discovered a new bug AFTER finalizing everything . That just happened to me when I realized if MDS isn’t in a channel, it just ghosts you and leaves a error in the console. Yeah, not great, so I added this nice little message if that happens, and also just improved a lil bit of the reliability on the slack side of things. Ready to ship, I think
Ships:
I made MDS (Meme Delivery Service), a Python Slack bot that fetches programming memes from ProgrammerHumor! It can post a daily batch automatically, or you can use /memes to request anywhere from 1–10 memes from the home, hot, random, or search feeds. There’s also optional LLM moderation and a Show sources button that links back to the original memes! While making this, there were quite a few moving parts to connect, such as scraping the memes, downloading the images, and uploading them to Slack. Handling errors were quite tedious aswell, including unavailable images, moderation errors, and commands used in channels where the bot hasn’t been invited. Overall, I’m happy with how the whole posting system came together! Daily posts interweave the home and hot feeds, and you can configure the schedule, cooldowns, and moderation. Memes :) Anyways, you, yes YOU should try it TODAY, RIGHT NOW. Just join #mds-playground on the Hack Club Slack and check the pinned message! Ty for reading this :D...
|
1792853643.7677176
|
1792940043.7677176
|
|
19407
|
UltraHawk by @zykron1 | Stardance
|
zykron1
|
0
|
3.0
|
0
|
[]
|
[{"post_id": 13465, "ts": "202 [{"post_id": 13465, "ts": "2026-06-22T01:30:24Z", "hours": 3.0, "text": "UltraHawk Current CAD"}]...
|
Title: UltraHawk by @zykron1 | Stardance
Devlogs: Title: UltraHawk by @zykron1 | Stardance
Devlogs:
UltraHawk Current CAD...
|
1791822093.0706573
|
1792686093.0706573
|
|
59113
|
CERAMv3 by @zykron1 | Stardance
|
zykron1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CERAMv3 by @zykron1 | Stardance
|
1792784944.7519238
|
1793389744.7519238
|
|
8375
|
My first slack bot! by @zydsonek123 | Stardance
|
zydsonek123
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zydsonek123 | Stard Title: My first slack bot! by @zydsonek123 | Stardance...
|
1792734660.008953
|
1793339460.008953
|
|
63346
|
WarioWare Game by @zyd_33 | Stardance
|
zyd_33
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @zyd_33 | Stardance
|
1792442842.4759831
|
1793047642.4759831
|
|
64966
|
A by @zyca0221 | Stardance
|
zyca0221
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A by @zyca0221 | Stardance
|
1792453647.7999437
|
1793058447.7999437
|
|
69962
|
My very own WebOS by @zybyte_retr0 | Stardance
|
zybyte_retr0
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zybyte_retr0 | Starda Title: My very own WebOS by @zybyte_retr0 | Stardance...
|
1792120626.3409083
|
1792725426.3409083
|
|
7028
|
My awesome macropad! by @zxxz999_2 | Stardance
|
zxxz999_2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zxxz999_2 | Starda Title: My awesome macropad! by @zxxz999_2 | Stardance...
|
1792759994.0363193
|
1793364794.0363193
|
|
36242
|
My own site! by @zx_dr4gon | Stardance
|
zx_dr4gon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zx_dr4gon | Stardance
|
1792605141.2242525
|
1793209941.2242525
|
|
36245
|
My first slack bot! by @zx_dr4gon | Stardance
|
zx_dr4gon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zx_dr4gon | Stardan Title: My first slack bot! by @zx_dr4gon | Stardance...
|
1792554806.3459687
|
1793159606.3459687
|
|
31661
|
Operator's Mouse by @zx10rk3ito | Stardance
|
zx10rk3ito
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Operator's Mouse by @zx10rk3ito | Stard Title: Operator's Mouse by @zx10rk3ito | Stardance...
|
1792785264.4461691
|
1793390064.4461691
|
|
31674
|
The Operator's Mouse by @zx10rk3ito | Stardanc The Operator's Mouse by @zx10rk3ito | Stardance...
|
zx10rk3ito
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The Operator's Mouse by @zx10rk3ito | S Title: The Operator's Mouse by @zx10rk3ito | Stardance...
|
1792601406.3068266
|
1793206206.3068266
|
|
25073
|
Video game about asteroids by @zw662 | Stardance
|
zw662
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Video game about asteroids by @zw662 | Star Title: Video game about asteroids by @zw662 | Stardance...
|
1791826765.91609
|
1792690765.91609
|
|
25095
|
My very own WebOS by @zw662 | Stardance
|
zw662
|
0
|
2.0
|
0
|
[]
|
[{"post_id": 18561, "ts": "202 [{"post_id": 18561, "ts": "2026-06-29T19:10:07Z", "hours": 2.0, "text": "Followed Part 1 of the hack club webOS jam batch tutorial, set up the starting screen of my ROBOT OS file, kicked off the official Hack Club webOS Jam batch tutorial. Also successfully initialized the repository structure and verified the local workspace configuration."}]...
|
Title: My very own WebOS by @zw662 | Stardance
De Title: My very own WebOS by @zw662 | Stardance
Devlogs:
Followed Part 1 of the hack club webOS jam batch tutorial, set up the starting screen of my ROBOT OS file, kicked off the official Hack Club webOS Jam batch tutorial. Also successfully initialized the repository structure and verified the local workspace configuration....
|
1791821565.228768
|
1792685565.228768
|
|
39341
|
My own site! by @zw662 | Stardance
|
zw662
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-25T01:09:00Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made my own website on a GitHub repo and deployed on Github pages. The most challenging aspect of my project is learning css and how to write the style sheet. That was one aspect that was challenging, since I had been confused on how I should format the website without making it look cluttered. I am proud of the fact that I was able to complete the website in the course of a day, since I had originally expected this process to take much longer.", "repo": "https://github.com/Not-A-Robot-Really/My-own-site", "demo": "https://not-a-robot-really.github.io/My-own-site/"}]...
|
[{"post_id": 34372, "ts": "202 [{"post_id": 34372, "ts": "2026-07-25T01:03:55Z", "hours": 1.0, "text": "My Own Website 🤖 This is my first personal website that I made using HTML and CSS while learning how to code.What I usedHTML for the structureCSS for the styling (blue and white theme)No JavaScript yet, (maybe later when I learn it) AI was used to check my code for bugs, fix any errors I was “stumped” on, and as inspiration for multiple possible color schemes and some aspects of UI. As you can see, I eventually settled on blue and white. Sections: About Me - a little overview about myself and things I like Projects - stuff I’ve made so far Contact - how to reach me (email and github)"}]...
|
Title: My own site! by @zw662 | Stardance
Devlogs Title: My own site! by @zw662 | Stardance
Devlogs:
My Own Website 🤖 This is my first personal website that I made using HTML and CSS while learning how to code.What I usedHTML for the structureCSS for the styling (blue and white theme)No JavaScript yet, (maybe later when I learn it) AI was used to check my code for bugs, fix any errors I was “stumped” on, and as inspiration for multiple possible color schemes and some aspects of UI. As you can see, I eventually settled on blue and white. Sections: About Me - a little overview about myself and things I like Projects - stuff I’ve made so far Contact - how to reach me (email and github)
Ships:
I made my own website on a GitHub repo and deployed on Github pages. The most challenging aspect of my project is learning css and how to write the style sheet. That was one aspect that was challenging, since I had been confused on how I should format the website without making it look cluttered. I am proud of the fact that I was able to complete the website in the course of a day, since I had originally expected this process to take much longer....
|
1792882110.8419895
|
1793746110.8419895
|
|
68301
|
My very own WebOS by @zvr | Stardance
|
zvr
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zvr | Stardance
|
1792471785.8353636
|
1793076585.8353636
|
|
300
|
cool project by @zvan | Stardance
|
zvan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: cool project by @zvan | Stardance
|
1792493719.05231
|
1793098519.05231
|
|
16316
|
Linux on my samsung tablet >:3 by @zuzuka | Sta Linux on my samsung tablet >:3 by @zuzuka | Stardance...
|
zuzuka
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Linux on my samsung tablet >:3 by @zuzuk Title: Linux on my samsung tablet >:3 by @zuzuka | Stardance...
|
1792421336.6123738
|
1793026136.6123738
|
|
35975
|
platform by @zuza | Stardance
|
zuza
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: platform by @zuza | Stardance
|
1792612168.9213092
|
1793216968.9213092
|
|
35981
|
cook by @zuza | Stardance
|
zuza
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: cook by @zuza | Stardance
|
1792547538.8641648
|
1793152338.8641648
|
|
43298
|
Castle by @zuryurbina | Stardance
|
zuryurbina
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Castle by @zuryurbina | Stardance
|
1792540410.956243
|
1793145210.956243
|
|
55071
|
robotic hand by @zury | Stardance
|
zury
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: robotic hand by @zury | Stardance
|
1792482525.581107
|
1793087325.581107
|
|
67985
|
brazo mecanico by @zury | Stardance
|
zury
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: brazo mecanico by @zury | Stardance
|
1792468425.2651181
|
1793073225.2651181
|
|
67986
|
brazo mecanico by @zury | Stardance
|
zury
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: brazo mecanico by @zury | Stardance
|
1792468426.1028466
|
1793073226.1028466
|
|
36098
|
My own site! by @zuraizibrahim1234 | Stardance
|
zuraizibrahim1234
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zuraizibrahim1234 | Starda Title: My own site! by @zuraizibrahim1234 | Stardance...
|
1792518828.645239
|
1793123628.645239
|
|
59880
|
my_warioware_game by @zunno_francesco | Stardance
|
zunno_francesco
|
0
|
0.83
|
0
|
[]
|
[{"post_id": 64348, "ts": "202 [{"post_id": 64348, "ts": "2026-09-08T17:28:11Z", "hours": 0.8333, "text": "first time coding a game pls give me advice were to learn something asap"}]...
|
Title: my_warioware_game by @zunno_francesco | Sta Title: my_warioware_game by @zunno_francesco | Stardance
Devlogs:
first time coding a game pls give me advice were to learn something asap...
|
1792421569.0093815
|
1793026369.0093815
|
|
59895
|
On_baseOS by @zunno_francesco | Stardance
|
zunno_francesco
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: On_baseOS by @zunno_francesco | Stardance
|
1792421578.3932803
|
1793026378.3932803
|
|
41074
|
Android Portrait Mode by @zunair_charolia | Starda Android Portrait Mode by @zunair_charolia | Stardance...
|
zunair_charolia
|
0
|
61.76
|
0
|
[]
|
[{"post_id": 55162, "ts": "202 [{"post_id": 55162, "ts": "2026-08-26T17:15:29Z", "hours": 7.3611, "text": "I have highly refined the depth map algorithm, which has helped my project with the final result a ton. The computer keys are still the worst-case scenario from what I’ve tested, but it even handles them much better than the previous method. In order to achieve such a drastic difference, I have used a correction algorithm and an infill algorithm (see previous journal where parts were black (undefined). One of the big problems with the keyboard was that it would create a halo. Bokeh is still sharp, but it is also unfocused. This caused the SML algorithm to fail and create these “rings” around the true depth. To mitigate this, the correction algorithm calculates the edge of it’s own region. If a region is thick enough (this is a constant within the code), it is marked as trustworthy. Thin ribbons will fail this test.The black parts (missing data) is solved using an infill algorithm. It uses the original photo as a guide and assumes that if two adjacent pixels have the same color, they probably belong to the same object and should have the same depth. For every unsolved pixel, it looks at it’s neighbours and calculates the “color weight” (closeness in color). If the pixel has a high color weight, it likely belongs to the same object. If it has a low color weight, it is likely something like an edge. This process is repeated 40 times to ensure the entire frame is filled."}, {"post_id": 52725, "ts": "2026-08-23T01:26:37Z", "hours": 2.6831, "text": "After using AI, I have completed the blurring logic. (For this in particular, I used AI a little more than usual. I’m not a fan of it myself, but I’m in a time crunch, and the logic is a little complicated.) However, the results have turned out… Interesting. I will definitely have to double-check exactly what it did, though I do know the general gist. It uses CoC (circle of confusion… Confusion ) to blur parts that are not in focus. However, it seems that some adjustments have to be made, either to my focus algorithm or to the blurring logic. Most probably, I need to fix both. This is definitely something I need to look into… This is nowhere near perfect."}, {"post_id": 52403, "ts": "2026-08-22T15:05:19Z", "hours": 8.0944, "text": "Focus sweeping and creating a depth map now work successfully! I have stored the frames from each focus sweep in cache rather than storing them in memory, as storing them in memory caused the app to crash on some devices. The sweeps are then processed and stored in physical, non-cache storage along with the original image. I have also been able to create a depth map that shows the depth in an image. However, the depth map will need calibration, as the algorithm does not perform well in low light (it uses SML, but it does not seem to remove artifacts well, and blank areas are a problem). Since I am running out of time (1 day left), I will focus on creating the blur using the depth map and the original picture. I did use AI to make parts of this (mainly on how to extract the Y plane, save it, then read it, as that was confusing)."}, {"post_id": 50630, "ts": "2026-08-19T21:39:15Z", "hours": 4.9303, "text": "I am currently attempting to take individual images for depth. I am using AI to help me here, along with previous repos, as the CameraX and Camera2 APIs are not very extensive or well-written and are very confusing to use. I am also running into many problems in my code at the moment. My code is crashing due to the amount of memory used, and the camera preview is not the correct size anymore. I have also implemented a shutter button to allow me to capture images."}, {"post_id": 48370, "ts": "2026-08-16T18:06:15Z", "hours": 8.6883, "text": "I have now implemented tap-to-focus in my preview! Implementing this came with many bugs, mainly in handling tap-to-focus on fixed-focus devices and in creating the fade-in/out animation. There were also a couple of bugs in the preview that were much harder to fix, which varied across phones (I am testing on the Samsung S24 Ultra, Pixel 10 Pro XL, and Pixel 7 Pro, with the Pixel phones being the primary ones). These bugs were mainly the screen disappearing occasionally and not being able to click on a Logical Camera to see the underlying physical camera when there were no Physical Cameras within the Logical Camera."}, {"post_id": 46428, "ts": "2026-08-13T17:04:11Z", "hours": 8.5947, "text": "I have now added the camera preview! This proved to be much harder to do than it originally seemed. In order to show the preview, I had to switch to using CameraX API instead of using Camera2. This was because I constantly ran into glitches where the preview was stretched, or rotating the preview would cause problems. I have also made the orientation always portrait when in the camera preview. This helps the fluidity of the UI as you will not see the screen tilting animation when turning the phone (usually, camera software only tilts the icons or buttons). At the moment, the preview only shows the camera feed. I also used AI to help me with the logic for the camera preview and changing my project from Camera2 to CameraX."}, {"post_id": 44060, "ts": "2026-08-09T16:06:41Z", "hours": 5.0483, "text": "All previous glitches have been fixed. I had a problem where one Logical button would cause all buttons to show their Physical buttons. I also fixed other possible edge cases I overlooked that may cause my app to use more memory than it needs. I also slightly redesigned my buttons after realizing that Cards can be clickable. The different colour in the screenshot is simply because I changed my phone’s Material You theme (all colours are based on your phone’s theme by default). Small changes such as uneven padding for main cards and smaller padding for smaller cards helps the viewer group the cards. Rounding numbers for readability and a change in title have also been added."}, {"post_id": 43500, "ts": "2026-08-08T20:04:51Z", "hours": 8.0508, "text": "Ran into some problems… Thought I got the view and logic right for the buttons, but it seems I did not. Time to redo the button styling and logic! (I’m fried)"}, {"post_id": 41949, "ts": "2026-08-06T14:07:22Z", "hours": 8.3056, "text": "Finished the basis for my project. Time to start working on the camera preview and handling the physical lenses separately."}]...
|
Title: Android Portrait Mode by @zunair_charolia | Title: Android Portrait Mode by @zunair_charolia | Stardance
Devlogs:
Finished the basis for my project. Time to start working on the camera preview and handling the physical lenses separately.
Ran into some problems… Thought I got the view and logic right for the buttons, but it seems I did not. Time to redo the button styling and logic! (I’m fried)
All previous glitches have been fixed. I had a problem where one Logical button would cause all buttons to show their Physical buttons. I also fixed other possible edge cases I overlooked that may cause my app to use more memory than it needs. I also slightly redesigned my buttons after realizing that Cards can be clickable. The different colour in the screenshot is simply because I changed my phone’s Material You theme (all colours are based on your phone’s theme by default). Small changes such as uneven padding for main cards and smaller padding for smaller cards helps the viewer group the cards. Rounding numbers for readability and a change in title have also been added.
I have now added the camera preview! This proved to be much harder to do than it originally seemed. In order to show the preview, I had to switch to using CameraX API instead of using Camera2. This was because I constantly ran into glitches where the preview was stretched, or rotating the preview would cause problems. I have also made the orientation always portrait when in the camera preview. This helps the fluidity of the UI as you will not see the screen tilting animation when turning the phone (usually, camera software only tilts the icons or buttons). At the moment, the preview only shows the camera feed. I also used AI to help me with the logic for the camera preview and changing my project from Camera2 to CameraX.
I have now implemented tap-to-focus in my preview! Implementing this came with many bugs, mainly in handling tap-to-focus on fixed-focus devices and in creating the fade-in/out animation. There were also a couple of bugs in the preview that were much harder to fix, which varied across phones (I am testing on the Samsung S24 Ultra, Pixel 10 Pro XL, and Pixel 7 Pro, with the Pixel phones being the primary ones). These bugs were mainly the screen disappearing occasionally and not being able to click on a Logical Camera to see the underlying physical camera when there were no Physical Cameras within the Logical Camera.
I am currently attempting to take individual images for depth. I am using AI to help me here, along with previous repos, as the CameraX and Camera2 APIs are not very extensive or well-written and are very confusing to use. I am also running into many problems in my code at the moment. My code is crashing due to the amount of memory used, and the camera preview is not the correct size anymore. I have also implemented a shutter button to allow me to capture images.
Focus sweeping and creating a depth map now work successfully! I have stored the frames from each focus sweep in cache rather than storing them in memory, as storing them in memory caused the app to crash on some devices. The sweeps are then processed and stored in physical, non-cache storage along with the original image. I have also been able to create a depth map that shows the depth in an image. However, the depth map will need calibration, as the algorithm does not perform well in low light (it uses SML, but it does not seem to remove artifacts well, and blank areas are a problem). Since I am running out of time (1 day left), I will focus on creating the blur using the depth map and the original picture. I did use AI to make parts of this (mainly on how to extract the Y plane, save it, then read it, as that was confusing).
After using AI, I have completed the blurring logic. (For this in particular, I used AI a little more than usual. I’m not a fan of it myself, but I’m in a time crunch, and the logic is a little complicated.) However, the results have turned out… Interesting. I will definitely have to double-check exactly what it did, though I do know the general gist. It uses CoC (circle of confusion… Confusion ) to blur parts that are not in focus. However, it seems that some adjustments have to be made, either to my focus algorithm or to the blurring logic. Most probably, I need to fix both. This is definitely something I need to look into… This is nowhere near perfect.
I have highly refined the depth map algorithm, which has helped my project with the final result a ton. The computer keys are still the worst-case scenario from what I’ve tested, but it even handles them much better than the previous method. In order to achieve such a drastic difference, I have used a correction algorithm and an infill algorithm (see previous journal where parts were black (undefined). One of the big problems with the keyboard was that it would create a halo. Bokeh is still sharp, but it is also unfocused. This caused the SML algorithm to fail and create these “rings” around the true depth. To mitigate this, the correction algorithm calculates the edge of it’s own region. If a region is thick enough (this is a constant within the code), it is marked as trustworthy. Thin ribbons will fail this test.The black parts (missing data) is solved using an infill algorithm. It uses the original photo as a guide and assumes that if two adjacent pixels have the same color, they probably belong to the same object and should have the same depth. For every unsolved pixel, it looks at it’s neighbours and calculates the “color weight” (closeness in color). If the pixel has a high color weight, it likely belongs to the same object. If it has a low color weight, it is likely something like an edge. This process is repeated 40 times to ensure the entire frame is filled....
|
1791825777.4169664
|
1792689777.4169664
|
|
32463
|
My own site! by @zumrad | Stardance
|
zumrad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zumrad | Stardance
|
1792712988.621446
|
1793317788.621446
|
|
27488
|
My awesome macropad! by @zulucool42 | Stardance
|
zulucool42
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zulucool42 | Stard Title: My awesome macropad! by @zulucool42 | Stardance...
|
1792727642.6019762
|
1793332442.6019762
|
|
27489
|
My very own WebOS by @zulucool42 | Stardance
|
zulucool42
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zulucool42 | Stardanc Title: My very own WebOS by @zulucool42 | Stardance...
|
1792486087.243807
|
1793090887.243807
|
|
64766
|
My awesome macropad! by @zuiz | Stardance
|
zuiz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zuiz | Stardance
|
1792450348.7270136
|
1793055148.7270136
|
|
26835
|
My very own WebOS by @zuhashan29 | Stardance
|
zuhashan29
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zuhashan29 | Stardanc Title: My very own WebOS by @zuhashan29 | Stardance...
|
1792702241.5793366
|
1793307041.5793366
|
|
52371
|
Machine learning rain calculator model. by @zuhair Machine learning rain calculator model. by @zuhair_chattha | Stardance...
|
zuhair_chattha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Machine learning rain calculator model. by Title: Machine learning rain calculator model. by @zuhair_chattha | Stardance...
|
1792705925.4341664
|
1793310725.4341664
|
|
54997
|
first slack bot by @zuhair_chattha | Stardance
|
zuhair_chattha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: first slack bot by @zuhair_chattha | Starda Title: first slack bot by @zuhair_chattha | Stardance...
|
1792478899.9166713
|
1793083699.9166713
|
|
21715
|
Debugger by @zuhair | Stardance
|
zuhair
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Debugger by @zuhair | Stardance
|
1792500560.4267752
|
1793105360.4267752
|