|
57621
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793767654.0328207
|
1794631654.0328207
|
|
54696
|
mochi_robot_project by @lakshaykhatri780 | Stardan mochi_robot_project by @lakshaykhatri780 | Stardance...
|
lakshaykhatri780
|
1
|
5.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-07T20:28:58Z", "hours": 5.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I am building Mochi, an interactive companion desk robot! So far, I have engineered the core non-blocking state machine framework and custom anime-style blinking expressions on the 0.96” OLED display using an ESP32. The biggest challenge was designing the multi-axis motion and transistor sound circuits without having all the hardware components yet. I am shipping this now to unlock project grant funding so I can buy the dual servo motors, ultrasonic sensor, and speaker modules needed to finish the physical PVC pipe body assembly!", "repo": "https://github.com/lakshaykhatri780-tech/mochi_robot_project", "demo": ""}]...
|
[{"post_id": 63770, "ts": "202 [{"post_id": 63770, "ts": "2026-09-07T18:46:22Z", "hours": 1.0558, "text": "Finally mochi shows expressions"}, {"post_id": 63494, "ts": "2026-09-07T11:50:31Z", "hours": 0.95, "text": "Wiring all my components on prefboard"}, {"post_id": 63428, "ts": "2026-09-07T08:36:10Z", "hours": 0.805, "text": "Making a custom circuit for my mochi"}, {"post_id": 62144, "ts": "2026-09-05T12:15:01Z", "hours": 2.0981, "text": "writting the codes for my mochi expressions"}]...
|
Title: mochi_robot_project by @lakshaykhatri780 | Title: mochi_robot_project by @lakshaykhatri780 | Stardance
Devlogs:
writting the codes for my mochi expressions
Making a custom circuit for my mochi
Wiring all my components on prefboard
Finally mochi shows expressions
Ships:
I am building Mochi, an interactive companion desk robot! So far, I have engineered the core non-blocking state machine framework and custom anime-style blinking expressions on the 0.96” OLED display using an ESP32. The biggest challenge was designing the multi-axis motion and transistor sound circuits without having all the hardware components yet. I am shipping this now to unlock project grant funding so I can buy the dual servo motors, ultrasonic sensor, and speaker modules needed to finish the physical PVC pipe body assembly!...
|
1793767652.488534
|
1793854052.488534
|
|
57612
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793767651.4527388
|
1794631651.4527388
|
|
51432
|
WONDER by @samia | Stardance
|
samia
|
1
|
11.53
|
6
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-02T18:40:24Z", "hours": 5.0, "multiplier": 1.38, "payout": 6, "blessing": "neutral", "text": "I make WONDER. I was trying to find some knowledge about the planets in space but when I saw the info on the internet it was so boring to read all of that. So I thought, why don’t I make something that will give info about the planets but in a wonderful way. It makes people curious about what happens next, so the user will read more without getting bored.", "repo": "https://github.com/samia-siddique/wonder", "demo": "https://wonder-space.vercel.app/"}]...
|
[{"post_id": 64285, "ts": "202 [{"post_id": 64285, "ts": "2026-09-08T15:44:26Z", "hours": 6.5264, "text": "The Jupiter page on my Wonder website!"}, {"post_id": 50402, "ts": "2026-08-19T15:48:26Z", "hours": 4.6319, "text": "I created the WONDER, which makes learning about space easier and makes you wonder about the planets and space."}]...
|
Title: WONDER by @samia | Stardance
Devlogs:
I cr Title: WONDER by @samia | Stardance
Devlogs:
I created the WONDER, which makes learning about space easier and makes you wonder about the planets and space.
The Jupiter page on my Wonder website!
Ships:
I make WONDER. I was trying to find some knowledge about the planets in space but when I saw the info on the internet it was so boring to read all of that. So I thought, why don’t I make something that will give info about the planets but in a wonderful way. It makes people curious about what happens next, so the user will read more without getting bored....
|
1793767650.300931
|
1793854050.300931
|
|
14718
|
My first slack bot! by @Thing6 | Stardance
|
Thing6
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Thing6 | Stardance
|
1793767649.0182967
|
1794372449.0182967
|
|
57608
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793767646.8679864
|
1794631646.8679864
|
|
5496
|
Windows Manager/Browser Control Pad by @max-lobste Windows Manager/Browser Control Pad by @max-lobster | Stardance...
|
max-lobster
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Windows Manager/Browser Control Pad by @max Title: Windows Manager/Browser Control Pad by @max-lobster | Stardance...
|
1793767645.9575796
|
1794372445.9575796
|
|
57605
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793767640.3828926
|
1794631640.3828926
|
|
5880
|
SOTD Bot by @dhruvra | Stardance
|
dhruvra
|
1
|
2.25
|
3
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-03T23:01:26Z", "hours": 2.0, "multiplier": 1.63, "payout": 3, "blessing": "neutral", "text": "I made a bot for Discord that’s able to respond to certain keywords and can generate a song of the day. It remembers what song is generated for the entire day. It also has a minor obsession with J-Rock (the best music genre, of course). The project is coded entirely in Python. Through it, I learned more about how Discord.py works, as well as pulling information from APIs in Discord.", "repo": "https://github.com/qibliusegit/song-of-the-day", "demo": "https://discord.gg/SV7eJkfMjX"}]...
|
[{"post_id": 2270, "ts": "2026 [{"post_id": 2270, "ts": "2026-06-04T17:44:37Z", "hours": 0.2542, "text": "Added some more functionality and details to the bot, so it specifies the date when it prints out the Song of the Day and also just commented more of my code. Since all of these APIs connect to Music Brainz’s ID system for some reason, I may use that to be able to query for general song info."}, {"post_id": 1756, "ts": "2026-06-03T22:54:01Z", "hours": 0.695, "text": "I made it so the bot is able to keep track of songs that have already been selected as Songs of the Day, and also made it so the bot keeps track of the date and won’t generate a new song for the same day if one’s already been selected. These both, of course, only work when the bot is running the entire time."}, {"post_id": 1622, "ts": "2026-06-03T19:13:05Z", "hours": 0.3983, "text": "Devlog #3 I switched to the AudioDB API since it’s IDs are just 8 digit codes, rather than UUIDs like what MusicBrainz has. However, this has come with its own set of problems, mainly being that finding a track takes a minute. Since I’m generating an 8 digit number and not all numbers will actually have songs assigned to them, sometimes I’m just sitting there staring at it find null results over and over again. That, however, is an issue that will be approached once I have the code properly printing the information I want it to. For now, it at least can find a song and turn it into a list. Also, working on two scripts at once (since I would rather not leak my bot token) is a lot harder than I thought it would be, since I’m effectively coding on one file (which gets its time tracked) and debugging on another (which does not get its time tracked)."}, {"post_id": 1327, "ts": "2026-06-03T08:16:09Z", "hours": 0.57, "text": "There surprisingly aren’t many ways to randomly search for a song, and whatever ones do exist continue to fail for some reason. I’m currently using the ISWC code that’s assigned to all musical works, but MusicBrainz API either doesn’t feel like actually using it or there’s something wrong with the API. I guess I’ll find out eventually."}, {"post_id": 1265, "ts": "2026-06-03T04:38:50Z", "hours": 0.3894, "text": "Made it so the bot can respond to keywords. Now to start reading up on various different music APIs to find one which properly suits my needs."}]...
|
Title: SOTD Bot by @dhruvra | Stardance
Devlogs:
Title: SOTD Bot by @dhruvra | Stardance
Devlogs:
Made it so the bot can respond to keywords. Now to start reading up on various different music APIs to find one which properly suits my needs.
There surprisingly aren’t many ways to randomly search for a song, and whatever ones do exist continue to fail for some reason. I’m currently using the ISWC code that’s assigned to all musical works, but MusicBrainz API either doesn’t feel like actually using it or there’s something wrong with the API. I guess I’ll find out eventually.
Devlog #3 I switched to the AudioDB API since it’s IDs are just 8 digit codes, rather than UUIDs like what MusicBrainz has. However, this has come with its own set of problems, mainly being that finding a track takes a minute. Since I’m generating an 8 digit number and not all numbers will actually have songs assigned to them, sometimes I’m just sitting there staring at it find null results over and over again. That, however, is an issue that will be approached once I have the code properly printing the information I want it to. For now, it at least can find a song and turn it into a list. Also, working on two scripts at once (since I would rather not leak my bot token) is a lot harder than I thought it would be, since I’m effectively coding on one file (which gets its time tracked) and debugging on another (which does not get its time tracked).
I made it so the bot is able to keep track of songs that have already been selected as Songs of the Day, and also made it so the bot keeps track of the date and won’t generate a new song for the same day if one’s already been selected. These both, of course, only work when the bot is running the entire time.
Added some more functionality and details to the bot, so it specifies the date when it prints out the Song of the Day and also just commented more of my code. Since all of these APIs connect to Music Brainz’s ID system for some reason, I may use that to be able to query for general song info.
Ships:
I made a bot for Discord that’s able to respond to certain keywords and can generate a song of the day. It remembers what song is generated for the entire day. It also has a minor obsession with J-Rock (the best music genre, of course). The project is coded entirely in Python. Through it, I learned more about how Discord.py works, as well as pulling information from APIs in Discord....
|
1793767639.175358
|
1793854039.175358
|
|
57603
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793767638.3060315
|
1794631638.3060315
|
|
27445
|
My first slack bot! by @harishh | Stardance
|
harishh
|
1
|
2.96
|
1
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-04T06:33:51Z", "hours": 0.0, "multiplier": 1.11, "payout": 1, "blessing": "neutral", "text": "i made a slack bot, it was pretty challenging to understand how this challenge works, because im a complete beginner to this stardance and to coding, so i did use ai to learn stuff, it was a fun project and i will give updates to make this one better, i will make a new game and release it!!!", "repo": "https://github.com/starharish0210-afk/lucid-bot", "demo": "https://hackclub.slack.com/archives/C0P5NE354"}]...
|
[{"post_id": 73829, "ts": "202 [{"post_id": 73829, "ts": "2026-09-26T03:39:00Z", "hours": 2.9558, "text": "I have updated my Slack bot!! - I am sure that my new food command will make your mouths water"}, {"post_id": 21950, "ts": "2026-07-04T04:41:59Z", "hours": 0.4528, "text": "I built Lucid, a Slack bot that runs 24/7 on Hack Club’s Nest server! It started as just a basic ping bot but I kept adding more commands — weather, cat facts, jokes, a cat of the day with a full image card, and even a NASA astronomy picture of the day with space facts. Built it with Node.js and Slack Bolt, deployed it as a systemd service so it never goes down even when my laptop is off. Pretty proud of how it turned out! lets goooooooooooo"}]...
|
Title: My first slack bot! by @harishh | Stardance Title: My first slack bot! by @harishh | Stardance
Devlogs:
I built Lucid, a Slack bot that runs 24/7 on Hack Club’s Nest server! It started as just a basic ping bot but I kept adding more commands — weather, cat facts, jokes, a cat of the day with a full image card, and even a NASA astronomy picture of the day with space facts. Built it with Node.js and Slack Bolt, deployed it as a systemd service so it never goes down even when my laptop is off. Pretty proud of how it turned out! lets goooooooooooo
I have updated my Slack bot!! - I am sure that my new food command will make your mouths water
Ships:
i made a slack bot, it was pretty challenging to understand how this challenge works, because im a complete beginner to this stardance and to coding, so i did use ai to learn stuff, it was a fun project and i will give updates to make this one better, i will make a new game and release it!!!...
|
1793767637.1409776
|
1793854037.1409776
|
|
57585
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793767634.9260402
|
1794631634.9260402
|
|
333
|
ZenPlay by @yadavtejas1947 | Stardance
|
yadavtejas1947
|
0
|
0.28
|
0
|
[]
|
[{"post_id": 11176, "ts": "202 [{"post_id": 11176, "ts": "2026-06-18T08:37:53Z", "hours": 0.2778, "text": "Today just did basic designing of the project and find the best components needed to build the project ."}]...
|
Title: ZenPlay by @yadavtejas1947 | Stardance
Dev Title: ZenPlay by @yadavtejas1947 | Stardance
Devlogs:
Today just did basic designing of the project and find the best components needed to build the project ....
|
1793767634.0577567
|
1794372434.0577567
|
|
57576
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793767631.6082184
|
1794631631.6082184
|
|
72881
|
hacker by @sickfrost | Stardance
|
sickfrost
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: hacker by @sickfrost | Stardance
|
1793767630.269516
|
1794372430.269516
|
|
72880
|
Hackpad by @Sohayeb | Stardance
|
Sohayeb
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hackpad by @Sohayeb | Stardance
|
1793767629.1051822
|
1794372429.1051822
|
|
72879
|
One Jump by @Junior72 | Stardance
|
Junior72
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: One Jump by @Junior72 | Stardance
|
1793767625.583117
|
1794372425.583117
|
|
4712
|
VaultForge Crypto Wallet by @professional_toad | S VaultForge Crypto Wallet by @professional_toad | Stardance...
|
professional_toad
|
2
|
127.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-31T11:50:55Z", "hours": 101.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What did you make? VaultForge is a multi-chain, fully self-custodial crypto wallet with support for Bitcoin, EVM chains (e.g., Arbitrum, Avalanche, Base, BNB Chain, Ethereum, Polygon, etc.), Solana, Tron, and XRP. Additionally, VaultForge has support for swapping (see below screenshot) using Decentralized EXchanges (DEXs) such as Uniswap and Jupiter and DEX aggregators such as LI.FI and Relay. There is also support for transferring stablecoins (crypto tokens pegged to dollars) across chains with Circle’s CCTP v2. Why did I make it? I was frustrated with the lack of consistent support for major chains across crypto wallets and the need to use multiple of them. It turns out it was much harder to make than I thought. What was challenging? By far the hardest part was adding support for swapping and the CCTP features to some extent as it required extensive knowledge of each chain as they all behaved differently and needed a lot of research on each provider’s API. It also took loads of rigorous testing to make absolutely sure that it would work every time before doing a test with real funds (again, see the below screenshot). What are you proud of? I’m really happy with how the wallet onboarding turned out - all though it is quite a small part of the application I think it is quite easy to use and set up the wallet and lets you set up all the common settings such as your base currency and theme (light or dark mode). What should people know so they can test your project? Unfortunately, due to time constraints and the amount of extra code it would require to add this feature, I was not able to add a demo feature to test the wallet without real funds. This might make it hard to test the entirety of the wallet’s features, especially the sending and swapping part. If I had more time, I would definitely try to improve this. Also, due to the slow build times with GitHub Actions, I removed support for Intel Macs. I don’t think many people use them anymore though so I hope it isn’t too big of an issue.", "repo": "https://github.com/kunningKing11/vaultforge", "demo": "https://github.com/kunningKing11/vaultforge/releases"}, {"ship_num": 2, "ts": "2026-06-29T16:59:27Z", "hours": 26.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Fully functional, multi-chain (Bitcoin, EVM, and Solana support with more on the way) wallet. To test this project, please go to the GitHub repository linked to the project.", "repo": "https://github.com/kunningKing11/vaultforge", "demo": "https://github.com/kunningKing11/vaultforge/releases"}]...
|
[{"post_id": 85472, "ts": "202 [{"post_id": 85472, "ts": "2026-10-31T11:37:39Z", "hours": 1.3644, "text": "Devlog #33 - some cleanup i migrated from vite to bun’s built-in bundler and minifier and updated the README."}, {"post_id": 83431, "ts": "2026-10-27T23:12:02Z", "hours": 6.4089, "text": "Devlog 32 - what a grind!!! vaultforge v0.5.0 is finally out ! so many new features i honestly can’t remember all of them! just as a recap vaultforge is available on mac, linux, and windows. i’m on linux so i couldn’t really test the binaries on other oses that well. there’s a .deb and .rpm for linux for debian-based (debian, ubuntu, etc.) and fedora-based (rhel, fedora, bazzite) distros. and yes, before you ask, there is an appimage available. btw github actions is sooooo slow 🐌, especially the mac os x64 runners - grrrrrrr . i’ve been stuck here just waiting for the past 1/2 an hour… i was so frustrated that i decided to completely remove support for itnel macs cuz the build times are like 3x slower. sorry intel mac users. that took so long… finally ready to ship! tbh i mostly just did some ci stuff since last devlog but i also added some nice ui impirovements. guys please give me a good rating 🙏"}, {"post_id": 81422, "ts": "2026-10-21T07:03:36Z", "hours": 0.7881, "text": "Devlog 31 - swapping support for Solana! (partially) there’s now swapping support for solana, at least for DEX aggregators like LI.FI or Relay. i still need to figure out native solana DEX swapping on platforms like Jupiter…"}, {"post_id": 81198, "ts": "2026-10-20T08:10:50Z", "hours": 3.2675, "text": "Devlog 30 - support for swapping (finally!) this took so long!!! i thought i would be done last friday but ig that was overly optimistic… there are still some small things i will fix/improve to make the experience a bit smoother in the coming days. Implementation so i added uniswap support for all supported evm chains; however only for same-chain transactions and only through one pool. this is suboptimal so i want to add cross-chain support and through multiple pools maybe in the future. to make it possible to do cross-chain swaps, i added Relay support (it’s an aggregator) were solvers compete to give a quote. the issue with this is that they charge quite a fee and so i really want to just use uniswap where possible. what’s next better uniswap integration (as mentioned above), plus support for solana potentially jupiter support (it’s a solana DEX) as it has really good rates and high liquidity."}, {"post_id": 80081, "ts": "2026-10-16T05:40:57Z", "hours": 1.2094, "text": "Devlog 29 - more coin icons! specifically for AAVE, Chainlink (LINK), and Uniswap (UNI)."}, {"post_id": 79643, "ts": "2026-10-14T20:01:16Z", "hours": 1.4264, "text": "Devlog 28 - coin icons! it finally looks sooo professional now… just look at those icons! they will also appear in the send and transfer (soon to be swap!) tabs over the coming days. uniswap dex integration is still the top priority though. 🫡 before there weren’t any (they were just grey) and every wallet has them so i made it better ig"}, {"post_id": 79385, "ts": "2026-10-13T19:20:45Z", "hours": 3.1186, "text": "Devlog 27 - CCTP support is here… in like 30 minutes hang tight, it’s coming soon 🚀 i attached some proof , you guys can check out the transaction here more info on this tomorrow after v0.5.0 comes out with the CCTP support. you haven’t seen nothing yet, uniswap support coming next; stay tuned! probably coming in the next week or so…"}, {"post_id": 79016, "ts": "2026-10-12T11:14:38Z", "hours": 2.2986, "text": "Devlog 26 unfortunately, it’s taking longer than i would like to add the swapping and CCTP functionality. i would say i’m about 80% there, but there are quite a few things that i have to think about and as such, i think i will get it working by tomorrow (tuesday). stay tuned! 👀"}, {"post_id": 77760, "ts": "2026-10-08T05:56:13Z", "hours": 2.3114, "text": "Devlog 25 - some progress on the swapping i haven’t had much time in the last few days but i managed to do a big refactor to make the code more modular and cleaner. this is needed so that i can do more complex transactions instead of just basic transfers. i haven’t pushed it to main or committed it yet but it’s basically done. in terms of when CCTP support will ship, I think it will be by the end of sunday."}, {"post_id": 76737, "ts": "2026-10-04T13:27:58Z", "hours": 2.095, "text": "Devlog 24 - adding support for swapping after absolutely grinding on the support for swapping for the past week, here are some updates: 12 commits coming to main soon, about half bug fixes 4/10 things completed that i think are required for adding swapping support (more info below) i’ve also decided on a rough implementation order of swapping-related functionality: CCTP v2 transfers (basically moving USDC stablecoins across chains) Uniswap DEX (the biggest Decentrallized EXchange) Jupiter DEX ( the biggest dex on Solana) NEAR Intents (a cross-chain DEX) LI.FI aggregator (basically tells the walet the best market rates) i know this is kind of an ambitious timeline but i think i can pull it all off before the end of stardance on the 31st of october 🤞. i think i will manage to get CCTP transfers working by friday or sunday, depending on how much time i have."}, {"post_id": 74986, "ts": "2026-09-28T19:35:45Z", "hours": 1.4533, "text": "Devlog 23 15 new commits pushed to main ! still cooking on the integrated swapping support… sorry this is a short devlog; i’m more focused on the coding rn and will post when i’ve done something more substantial."}, {"post_id": 74352, "ts": "2026-09-27T06:58:05Z", "hours": 2.1792, "text": "Devlog 22 since the deadline for stardance has been extended by one month, i decided to keep going and make VaultForge as good as possible over the coming weeks. here’s a quick overview of what i will focus on next: actual swapping, and integration with multiple DEXes (think Jupiter, NEAR Intents, Uniswap, etc.) a better activity view token and chain icons! makes it much easier to differentiate between assets general performance and UI improvements with these new features, especially the integrated swapping, my wallet is finally going to be on par (mostly) with established wallets such as metamask. i’ve already got like 10+ commits since the last release that i will merge to main branch soon…"}, {"post_id": 73472, "ts": "2026-09-25T06:06:46Z", "hours": 1.0978, "text": "Devlog 21 as promised, VaultForge v0.4.0 is out! this brings huge changes to wallet unlock speed, adds ripple support, adds BIP-84 addresses, and loads more. here is the link to the release page if you want to check it out. some interesting stats: there was an increase of >6,000 lines of code which is a more than 50% increase since v0.3.0 . 132 commits since last release. this is probably going to be my second-to-last devlog as i really want to hit the 100-hour mark."}, {"post_id": 72818, "ts": "2026-09-23T20:02:48Z", "hours": 7.05, "text": "Devlog 20 so i finally added ripple support… and migrated everything to React for a much better, cleaner UI. and as always, i am late again. i actually could have finished on friday but i had other things to do (like homework) and i also wanted to migrate to react as well since I decided this will be my last release before the end of stardance, so i really want to add everything i can. this is because after stardance i will take a break of a few months on this project and then come back with a different hack club ysws challenge. the react migration was so big that i decided to use AI this time: the finished App.tsx file containing the react code is over 3090 lines of code (proof is the 2nd attached image)! that’s the largest code file i have ever worked on. since this is a huge change to the ui, i decided to create some before and after comparisons below. anyways, i decided to share some design decisions relating to the migration to react. i knew react was a big framework so it would add a few MB to the app’s file size (about 1-2 MB as of my recent testing) but the app itself is tiny anyway - not even 30 MB - so i thought it was really worth it. it gives you design consistency, more so than tailwindcss, which i needed since the more fun part for me was working on the backend and not the frontend (the user-facing part of the application). plus, the guys who work at coinbase (shoutout to them) made a goated plugin/theme/whatever you call it for react which makes my app have the default coinbase theme that i can tweak (i made the font monospace) which is alone like 70% of the stuff needed for the migration. i promise i will release v0.4.0 tomorrow…"}, {"post_id": 68207, "ts": "2026-09-14T18:12:58Z", "hours": 0.5819, "text": "Devlog 19 still cooking on the ripple support… i think i will be done by friday."}, {"post_id": 66040, "ts": "2026-09-11T16:23:03Z", "hours": 0.4975, "text": "Devlog 18 i finished all the perf improvements! there was one that i left out though bc it probably wouldn’t have helped much in terms of performance and would have been a pain to implement. i am FINALLY going to move on to ripple support for the next few days…"}, {"post_id": 65508, "ts": "2026-09-10T18:18:14Z", "hours": 0.7617, "text": "Devlog 17 perf improvement #3 done! 🎊 now refreshes are fully concurrent, w/ a limit of 4 requests at a time to avoid rate limiting. i haven’t fully tetsed it yet but it feels noticeably faster (like 25-35% faster) until the updated prices & balances are shown. plus, I kind of finished the settings stuff so i’ll be working on ripple support ig…"}, {"post_id": 64935, "ts": "2026-09-09T17:38:35Z", "hours": 2.8842, "text": "Devlog 16 sorry guys, i’m kind of late on this one tbh: I said that I would have the settings improvements, ripple support and all that ready by like monday but clearly nothing has happened since like the weekend. i have decided to delay the timleine by about a week as after some careful consideration I found it was wayyy too aggressive and my fingers can’t keep up with the typing speed i would need for that :) i seriously have no idae whatsoever why I thought it was possible to add that many features in such a short space of time. I know it kind of is but I have school now which means i have much less time for this with homework and studying and stuff. however, today I decided to lock in and actually do this and so I can assure you that i am hard at work doing the settings stuff rn and ripple support is absolutely coming right after that this next release really is going to be a big one… p.s. i attached a screenshot of some of the new commits i worked on (more are coming soon)"}, {"post_id": 62021, "ts": "2026-09-05T07:16:08Z", "hours": 1.6236, "text": "Devlog #15 Since the last devlog, I’ve worked on some more boring stuff: Tauri cleanup and desktop-specific improvements. I moved the application setup and command registration from src-tauri/src/main.rs into a new src-tauri/src/lib.rs . This keeps the entry point organized and follows Tauri’s recommended structure, while main.rs now only launches the library. I also replaced the browser clipboard API with Tauri’s native clipboard manager plugin. Copy buttons now use the desktop clipboard integration. Finally, VaultForge now enforces a single-instance window. If the app is launched while another instance is already open, the new launch focuses the existing main window instead of opening a second copy, which is far more desirable of a behaviour imo as it lets a user find a window without inadvertently opening even more. Plus some more random stuff: I now sign off all my commits As of today (4th of September), I also sign all my commits with a PGP key to verify all commits are made on my laptop and not by someone who hacked my GitHub account or smth - this is definitely overkill but why not Next, I’m continuing the settings improvements before moving on to Ripple support. P.S. I also randomly moved to Neovim as it looks much better than VS Code."}, {"post_id": 61004, "ts": "2026-09-03T18:18:49Z", "hours": 1.7533, "text": "Devlog #14 Not very much since last time; just some refactors and small improvements throughout. You can kind of tell by all the fix/chore/docs changes… btw improved settings is in the works - I think I’ll do some more progress over the next two days, then some actual chain support for Ripple. I’ve decided that I will release v0.4.0 before adding basic Zcash support as it’s been basically a month since last release and I don’t want to keep you guys waiting for those of you who want to download the binaries directly w/o building. Quick summary Now –> ~5 September: settings improvements 5 September –> 7 September: Ripple support 7/8 September: release of VaultForge v0.4.0"}, {"post_id": 59639, "ts": "2026-09-01T15:39:50Z", "hours": 3.5681, "text": "Devlog #13 I finally added different currencies ! Before, all prices were displayed in USD and now they can display in any of the below currencies: USD ($) EUR (€) GBP (£) JPY (¥) Shoutout to the fantastic API I used for this! Previously, I fetched CoinGecko pricing data which came in USD but I needed to convert this data into whatever currency the user chose so I had to find an API. However, there really weren’t any good forex APIs that were free with no rate limits when I searched for one so I turned to ChatGPT to find one and find one it did. This API gives daily central bank rates and even has data going back to 1948 on 201 currencies which is more than enough for this project. I also added the second performance improvement : caching the HTTP request client object to avoid having to recreate it on every API request. As of rn the project roadmap for the near future is this: Finish perf improvements Add basic Ripple (XRP) transaction support Maybe add transparent <=> transparent pool transaction support for Zcash (ZEC) Release VaultForge v0.5.0"}, {"post_id": 58117, "ts": "2026-08-30T13:52:54Z", "hours": 5.2722, "text": "Devlog #12 Quite a bit more to report this time! Since last devlog, I’ve mostly been working on improving actual wallet functionality, fixing some smaller UI issues, and looking into performance. Recent changes Below is a quick summary of what I’ve been working on since the last devlog: Full TRC-20 token support is here! 🎊 Tron is no longer limited to just native TRX transfers, and the token validation/network logic has been updated to support TRC-20 tokens as well. Significantly improved Bitcoin support by adding proper BIP84 account discovery . VaultForge now scans both receive and change addresses, tracks which UTXOs belong to which derived addresses, signs each input with the correct derived key, and refreshes discovery before sending. Anecdote: I use Brave Wallet which did the receive and change addresses thing so my funds didn’t show up in previous versions of VaultForge. However, as of this update, I now am. Wallet unlocking now feels much faster ! Cached balances/prices are shown immediately while fresh data refreshes in the background. Improved asset cards so they show which network an asset belongs to . Assets worth less than $1 are now hidden from the portfolio/assets view unless VaultForge does not have price data for them. Fixed a few UI issues, including dashboard scrolling, refresh errors, escaping asset data (aka preventing XSS) , and copying the currently selected wallet address. Converted the remaining .js config files to TypeScript because apparently I cannot resist refactoring things even when it makes no difference whatsoever. For the first time in this series of devlogs, I’m linking the changes to relevant commits on GitHub wherever possible so you can have a look. Performance improvements I also found a few ways to reduce VaultForge’s roughly 10s full refresh time: Cached unlock (mentioned above): perceived unlock time is now closer to ~1–3s, although balances/prices can still take around the same amount of time to fully refresh in the background. Reuse HTTP clients: should save roughly ~0.2-1.5s by reusing connections. Concurrent provider calls: likely the biggest improvement, potentially bringing a ~10s refresh down to ~3–5s. Refresh prices separately: could make fresh balances appear another ~0.5–2s sooner. Derive Argon2 once: should save roughly a few hundred ms to ~1s on cold unlocks. The above estimated perf improvements are obviously quite variable and depend on a multitude of factors (+ I got ChatGPT to analyze my current code to make an estimate because how else would I do it), but there is definitely still a lot of low-hanging fruit here. Upcoming features Actual settings are still the elephant in the room 😭, so I definitely need to get around to those but since I think this may need a big PR a bit like the previous style improvements, I think I will do this after v0.4.0 (so therefore for v0.5.0 ). Ripple (XRP) support (at least for native token transfers), planned for v0.4.0 . Zcash (ZEC) support: I’ve got a feeling this one will take quite some time so at most I will implement transparent <=> transparent transactions before next release but will have to see. The remaining performance improvements mentioned above."}, {"post_id": 55009, "ts": "2026-08-26T13:12:12Z", "hours": 8.6272, "text": "Devlog #11 What a MASSIVE PR and it’s finally merged ! Hooray! That was the biggest PR I’ve ever created by a big margin. Now I can finally start work on actual features like more support for different blockchains, address types, random extra features that certain chains have… the list goes on. I already have a personal list of 25 different blockchains that I want to add support for, most of which aren’t in the project roadmap simply for the reason that it would make the file overly long and hard to read. * sigh * that will take a long time Not to underestimate what I added with the PR, though - I didn’t spend like 15 hours and do 48 commits for nothing: inside the PR I added Onboarding! 🎊 Lots of (at least in the future) common settings will be selected here to set up your wallet. You can already import an existing wallet or generate a new one (both accept 12, 15, 18, 21, and 24-word recovery phrases) and set an auto-lock timeout and select networks you want or don’t want. Finally, there is also the option to select a theme if you want. New and more prominent splash screen when loading the application. The application itself is super fast so it takes barely any time but to make it look cooler I’ve set a minimum time to display it for to 650 ms. Icons throughout the application to make it look better. Let you copy addresses in the sidebar with one click and list all enabled addresses, not just Ethereum. Squashed some more small UI bugs, especially relating to scrolling in different parts of the application. Although slightly unrelated to the theme of the PR, MUCH better refresh logic and handling. It now respects network selection choices (like the ones you want or don’t want that you selected during onboarding) and tells you exactly which network’s RPC request encountered errors. Perhaps ironically, this was literally the reason I fixed an issue with the Solana RPC. Before this update, it never actually refreshed the balance correctly so it wasn’t working. However, after this change, I was able to identify that the issue was not on my end (yay!) but was actually PublicNode ’s (the RPC I’m using for the majority of chains in this project for consistency, apart from Monad and now Solana) as I assumed it could fetch the user’s token accounts but it couldn’t so I had to switch to using the official Solana RPC which fixed the issue. For anyone who got lost somewhere in the previous paragraph, an RPC is a service that allows you to query data about the state of the blockchain (where crypto transactions are stored) so you can use it to see how much crypto you are holding. Token accounts are basically a weird quirk of Solana where your main account is used to hold Solana which links to associated token accounts (ATAs) , which each hold one token other than Solana. This is by far not a complete list but rather a list of the highlights of this PR; if you want to look at all the changes, please feel free to visit the page linked at the top of this devlog. That said, after this big change, I did say last devlog that I would be getting ready to release version v0.4.0 of this application which is exactly what I will do after adding Tron token support! Quick reminder, after v0.4.0 I am planning to add Ripple (XRP) support, preliminary (meaning like non-shielded probably) support for Zcash and revamp the settings page like I did to the onboarding in this PR. Further out, I will probably focus some more on the in-application swaps to aggregate data from major DEXs (decentralized exchanges) to get the best rates, matching other major wallets w/ more chain support, which would make my wallet actually competitive. 🤞"}, {"post_id": 50515, "ts": "2026-08-19T18:16:53Z", "hours": 6.2019, "text": "Devlog #10 I’m close to finishing the theme improvements (I would say I’m about 90% there) and am doing some general bug fixes and QoL improvements. As such, there isn’t much to log rn except for a few small new features & improvements: Show/hide password button on recovery phrase and password Loads of bug fixes, e.g., inconsistent password strength progress bar on onboarding, preventing the user from typing the Enter key when entering a seed phrase to import, text overflow, etc. Some dependency version bumps If you want to see my progress on this PR (there are already like 30 commits in it - it’s a pretty big PR!), you can do so here . What’s coming next Some final finishing touches on the PR and then I will merge it to main so that it will be in the next release Support for Tron token transfers Support for Ripple The release of VaultForge v0.4.0 either before or after adding support for Ripple transactions A revamp of the settings tab (currently it doesn’t do anything) Support for Zcash"}, {"post_id": 45175, "ts": "2026-08-11T14:25:55Z", "hours": 6.7719, "text": "Devlog #9 Not much to report but I’m still working on improving the theme and the wider interface. You can see my progress here . Recent changes Below is a quick summary of what I’ve been working on since last devlog: Improved fonts ( Tektur for headings, Manrope for body text, and Ubuntu Mono for monospace text) Updated some text across different views for consistency Improved the look and feel of onboarding Added wallet setup flow to onboarding so you can now quickly import or generate a wallet with different seed length options (12, 15, 18, 21, and 24-word seed phrases are all supported now) Theme selection (in onboarding) between four different themes - I know these look a bit AI-generated rn (they are; it would have been frustrating to write out three new themes) but I will make them look a bit better in the future Auto-lock! 🎊 Now, you can easily set an auto-lock option in the onboarding or have none at all Upcoming features I think the elephant in the elephant in the room rn is actual settings which I will be working on over the next few days as currently there are no settings in the literal settings page!"}, {"post_id": 40732, "ts": "2026-08-04T13:27:44Z", "hours": 10.4086, "text": "Devlog #8 That took a lot of time! Over the past two weeks, I have done quite a bit of bug fixing and stopping undesired behaviour, including fixing weird sideways scrolling behaviour on the dashboard portfolio and creating custom scrollbars for less janky behaviour fixing the left sidebar’s contents overflowing vertically when the window height was decreased too much (it now lets you scroll if there is not enough space to fully display its contents) stopping zooming with Ctrl + ... or with trackpad gestures completely fix portfolio allocation percentage bars stuck at zero in the dashboard Along with this, I have done quite some improvement on the CI (especially the release.yaml workflow and pre-commit checks) and some refactoring, including using Lefthook npm install , bun install , Oxlint, Oxfmt validation, TypeScript typechecking, cargo check , and package.json package-lock.json bun.lock src-tauri/Cargo.lock are automatically staged on every commit. The npm install , bun install , and automatic lockfile staging is to ensure consistency between npm and Bun so that both can be used in development and testing. The other checks are for checking (or at least trying to; there could always be edge cases that aren’t covered) that no invalid code gets committed. There is also a maximum commit message subject length (72 characters) and the same for each line of the commit message body to ensure that commit messages stay readable. cargo test , and rust-analyzer analysis on every push to GitHub, since every commit runs the other checks anyway and uncommitted code can’t be pushed refactoring the previously monolithic TypeScript file that contained multiple pages so that each page now gets its own file inside of src/views/ significantly improving release.yaml (the app release workflow for GitHub) so that it now adds a commit count since the last release adds a line count statistic and the change in lines since the previous release allows for release comments and highlights written by me adds a link that links to a GitHub page of all the commits made between the release and the previous one (it already/before this change had all the new commits listed in the release notes with a link to each one) unifying networks.json (the file that contains all the relevant chain information for the TypeScript frontend) with all the scattered equivalent information in the Rust backend; now, the backend references the networks.json file instead Also, you are now able to test out all of these changes as I have just released v0.3.0 of VaultForge! Unfortunately, I haven’t yet worked on any of the theme changes but these are top priority for the next release… As a recap, here are the things that I will be working on for the next release, in order of priority: Updated theme Full Tron support (not just native token sends) Ripple (XRP) support Miscellaneous bug fixes and new features"}, {"post_id": 29564, "ts": "2026-07-16T16:15:34Z", "hours": 7.8725, "text": "Devlog #7 Unfortunately, since I am on holiday, I was not able to complete everything that I wanted to do by the end of last week. However, I was definitely able to make some progress: Progress Tron (TRX) support is here! 🎊 (albeit only native Tron sends are currently supported) some refactoring happened What’s next As I promised last week (but did not manage to complete), I was going to completely redesign the UI to make it more user-friendly and usable and have less of an AI-generated feel. This is because when I initially started this project, I used AI to create a demo app (without any of the signing logic), just to get a sort of structure to build on and add functionality to. However, I have changed pretty much every part of it so far apart from the theme which is why I am going to work on it now/this week. Icons for different currencies and across the application for easily recognisable features Support for Ripple (XRP)"}, {"post_id": 25341, "ts": "2026-07-09T16:00:38Z", "hours": 8.0019, "text": "Devlog #6 Progress Not much to announce rn but so far (since last week/log), I have refactored the code a bit bumped some dependencies made a cool new banner for the project (you can see it on this project’s banner) started work on improving the theme/look of the app fixed some minor issues and bugs, such as EVM nonce processing used the latest nonce from a confirmed block, ignoring the fact that the user may have been fast enough to send two transactions with the same nonce, which would guarantee that at least one transaction will fail BTC preview balance displayed to the user before approving a transaction did not take into account the unspent UTXOs in the calculation Not too exciting but this lays the groundwork for what is to come. 👇🏼 What’s next I will try to add this before the end of this week: a full redesign of the theme full Tron (TRX) support"}, {"post_id": 18461, "ts": "2026-06-29T16:57:39Z", "hours": 1.5761, "text": "Devlog #5 Solana support is here!"}, {"post_id": 17931, "ts": "2026-06-28T21:30:30Z", "hours": 9.9086, "text": "Devlog #4 Support for Solana coming soon, stay tuned! 👀 Since last devlog, I refactored the code a bit and split up all the TypeScript frontend and Rust backend logic into self-contained files, each for a clear purpose. Now, it’s much easier to read and understand the codebase."}, {"post_id": 13869, "ts": "2026-06-22T18:44:00Z", "hours": 1.0944, "text": "Devlog #3 The GitHub repository is public!"}, {"post_id": 13552, "ts": "2026-06-22T05:53:33Z", "hours": 9.5006, "text": "Devlog #2 I added loads of stuff! As promised: CoinGecko pricing data integrated Integrated RPC Progress on the actual transactions (implemented for EVM only so far and I am still working on it) Hardened security: Added a CSP (content security policy) to stop XSS (cross-site scripting) Hardened address validation, including EVM EIP-55 checksum validation Added a “remove wallet data” button Added zeroization for mnemonic/key/salt on lock and clear Coming soon/roadmap: Full support for BTC, EVM, SOL, and TRX chain transfers Actual cross-chain swaps via NEAR Intents Public GitHub repository (the repo hasn’t been made public yet as it’s still not fully working) Full support for more chains, including (but not limited to): Ripple (XRP) Hyperliquid (HYPE) - support for trading perps (perpetuals) Injective (INJ) Algorand (ALGO) Zcash (ZEC) - support transparent AND shielded addresses Monero (XMR) - alternative to Zcash Support for the Open Wallet Standard Native DeFi support: Native Aerodrome Finance LPing (liquidity providing) Native Aave lending (hopefully) Filecoin storage integration so you can easily store, download, and access files stored on Filecoin (hopefully) Integration with Tor for anonymity"}, {"post_id": 6061, "ts": "2026-06-10T05:49:45Z", "hours": 4.1822, "text": "Devlog #1 Just finished the basic UI; more coming soon… Current features already include: Argon2 password hashing to secure wallet Import a wallet seed phrase RPC connection to see how much crypto you’re holding QR code to get people to send stuff to you with a fault tolerance selector, e.g., smaller QR code for 7% data recovery, 25%, 30%, etc. Coming soon: GitHub repository for the project Coming soon: CoinGecko pricing data so you can see how much your crypto is worth Coming soon: actual transactions Coming soon: compatibility with Open Wallet Standard"}]...
|
Title: VaultForge Crypto Wallet by @professional_t Title: VaultForge Crypto Wallet by @professional_toad | Stardance
Devlogs:
Devlog #1 Just finished the basic UI; more coming soon… Current features already include: Argon2 password hashing to secure wallet Import a wallet seed phrase RPC connection to see how much crypto you’re holding QR code to get people to send stuff to you with a fault tolerance selector, e.g., smaller QR code for 7% data recovery, 25%, 30%, etc. Coming soon: GitHub repository for the project Coming soon: CoinGecko pricing data so you can see how much your crypto is worth Coming soon: actual transactions Coming soon: compatibility with Open Wallet Standard
Devlog #2 I added loads of stuff! As promised: CoinGecko pricing data integrated Integrated RPC Progress on the actual transactions (implemented for EVM only so far and I am still working on it) Hardened security: Added a CSP (content security policy) to stop XSS (cross-site scripting) Hardened address validation, including EVM EIP-55 checksum validation Added a “remove wallet data” button Added zeroization for mnemonic/key/salt on lock and clear Coming soon/roadmap: Full support for BTC, EVM, SOL, and TRX chain transfers Actual cross-chain swaps via NEAR Intents Public GitHub repository (the repo hasn’t been made public yet as it’s still not fully working) Full support for more chains, including (but not limited to): Ripple (XRP) Hyperliquid (HYPE) - support for trading perps (perpetuals) Injective (INJ) Algorand (ALGO) Zcash (ZEC) - support transparent AND shielded addresses Monero (XMR) - alternative to Zcash Support for the Open Wallet Standard Native DeFi support: Native Aerodrome Finance LPing (liquidity providing) Native Aave lending (hopefully) Filecoin storage integration so you can easily store, download, and access files stored on Filecoin (hopefully) Integration with Tor for anonymity
Devlog #3 The GitHub repository is public!
Devlog #4 Support for Solana coming soon, stay tuned! 👀 Since last devlog, I refactored the code a bit and split up all the TypeScript frontend and Rust backend logic into self-contained files, each for a clear purpose. Now, it’s much easier to read and understand the codebase.
Devlog #5 Solana support is here!
Devlog #6 Progress Not much to announce rn but so far (since last week/log), I have refactored the code a bit bumped some dependencies made a cool new banner for the project (you can see it on this project’s banner) started work on improving the theme/look of the app fixed some minor issues and bugs, such as EVM nonce processing used the latest nonce from a confirmed block, ignoring the fact that the user may have been fast enough to send two transactions with the same nonce, which would guarantee that at least one transaction will fail BTC preview balance displayed to the user before approving a transaction did not take into account the unspent UTXOs in the calculation Not too exciting but this lays the groundwork for what is to come. 👇🏼 What’s next I will try to add this before the end of this week: a full redesign of the theme full Tron (TRX) support
Devlog #7 Unfortunately, since I am on holiday, I was not able to complete everything that I wanted to do by the end of last week. However, I was definitely able to make some progress: Progress Tron (TRX) support is here! 🎊 (albeit only native Tron sends are currently supported) some refactoring happened What’s next As I promised last week (but did not manage to complete), I was going to completely redesign the UI to make it more user-friendly and usable and have less of an AI-generated feel. This is because when I initially started this project, I used AI to create a demo app (without any of the signing logic), just to get a sort of structure to build on and add functionality to. However, I have changed pretty much every part of it so far apart from the theme which is why I am going to work on it now/this week. Icons for different currencies and across the application for easily recognisable features Support for Ripple (XRP)
Devlog #8 That took a lot of time! Over the past two weeks, I have done quite a bit of bug fixing and stopping undesired behaviour, including fixing weird sideways scrolling behaviour on the dashboard portfolio and creating custom scrollbars for less janky behaviour fixing the left sidebar’s contents overflowing vertically when the window height was decreased too much (it now lets you scroll if there is not enough space to fully display its contents) stopping zooming with Ctrl + ... or with trackpad gestures completely fix portfolio allocation percentage bars stuck at zero in the dashboard Along with this, I have done quite some improvement on the CI (especially the release.yaml workflow and pre-commit checks) and some refactoring, including using Lefthook npm install , bun install , Oxlint, Oxfmt validation, TypeScript typechecking, cargo check , and package.json package-lock.json bun.lock src-tauri/Cargo.lock are automatically staged on every commit. The npm install , bun install , and automatic lockfile staging is to ensure consistency between npm and Bun so that both can be used in development and testing. The other checks are for checking (or at least trying to; there could always be edge cases that aren’t covered) that no invalid code gets committed. There is also a maximum commit message subject length (72 characters) and the same for each line of the commit message body to ensure that commit messages stay readable. cargo test , and rust-analyzer analysis on every push to GitHub, since every commit runs the other checks anyway and uncommitted code can’t be pushed refactoring the previously monolithic TypeScript file that contained multiple pages so that each page now gets its own file inside of src/views/ significantly improving release.yaml (the app release workflow for GitHub) so that it now adds a commit count since the last release adds a line count statistic and the change in lines since the previous release allows for release comments and highlights written by me adds a link that links to a GitHub page of all the commits made between the release and the previous one (it already/before this change had all the new commits listed in the release notes with a link to each one) unifying networks.json (the file that contains all the relevant chain information for the TypeScript frontend) with all the scattered equivalent information in the Rust backend; now, the backend references the networks.json file instead Also, you are now able to test out all of these changes as I have just released v0.3.0 of VaultForge! Unfortunately, I haven’t yet worked on any of the theme changes but these are top priority for the next release… As a recap, here are the things that I will be working on for the next release, in order of priority: Updated theme Full Tron support (not just native token sends) Ripple (XRP) support Miscellaneous bug fixes and new features
Devlog #9 Not much to report but I’m still working on improving the theme and the wider interface. You can see my progress here . Recent changes Below is a quick summary of what I’ve been working on since last devlog: Improved fonts ( Tektur for headings, Manrope for body text, and Ubuntu Mono for monospace text) Updated some text across different views for consistency Improved the look and feel of onboarding Added wallet setup flow to onboarding so you can now quickly import or generate a wallet with different seed length options (12, 15, 18, 21, and 24-word seed phrases are all supported now) Theme selection (in onboarding) between four different themes - I know these look a bit AI-generated rn (they are; it would have been frustrating to write out three new themes) but I will make them look a bit better in the future Auto-lock! 🎊 Now, you can easily set an auto-lock option in the onboarding or have none at all Upcoming features I think the elephant in the elephant in the room rn is actual settings which I will be working on over the next few days as currently there are no settings in the literal settings page!
Devlog #10 I’m close to finishing the theme improvements (I would say I’m about 90% there) and am doing some general bug fixes and QoL improvements. As such, there isn’t much to log rn except for a few small new features & improvements: Show/hide password button on recovery phrase and password Loads of bug fixes, e.g., inconsistent password strength progress bar on onboarding, preventing the user from typing the Enter key when entering a seed phrase to import, text overflow, etc. Some dependency version bumps If you want to see my progress on this PR (there are already like 30 commits in it - it’s a pretty big PR!), you can do so here . What’s coming next Some final finishing touches on the PR and then I will merge it to main so that it will be in the next release Support for Tron token transfers Support for Ripple The release of VaultForge v0.4.0 either before or after adding support for Ripple transactions A revamp of the settings tab (currently it doesn’t do anything) Support for Zcash
Devlog #11 What a MASSIVE PR and it’s finally merged ! Hooray! That was the biggest PR I’ve ever created by a big margin. Now I can finally start work on actual features like more support for different blockchains, address types, random extra features that certain chains have… the list goes on. I already have a personal list of 25 different blockchains that I want to add support for, most of which aren’t in the project roadmap simply for the reason that it would make the file overly long and hard to read. * sigh * that will take a long time Not to underestimate what I added with the PR, though - I didn’t spend like 15 hours and do 48 commits for nothing: inside the PR I added Onboarding! 🎊 Lots of (at least in the future) common settings will be selected here to set up your wallet. You can already import an existing wallet or generate a new one (both accept 12, 15, 18, 21, and 24-word recovery phrases) and set an auto-lock timeout and select networks you want or don’t want. Finally, there is also the option to select a theme if you want. New and more prominent splash screen when loading the application. The application itself is super fast so it takes barely any time but to make it look cooler I’ve set a minimum time to display it for to 650 ms. Icons throughout the application to make it look better. Let you copy addresses in the sidebar with one click and list all enabled addresses, not just Ethereum. Squashed some more small UI bugs, especially relating to scrolling in different parts of the application. Although slightly unrelated to the theme of the PR, MUCH better refresh logic and handling. It now respects network selection choices (like the ones you want or don’t want that you selected during onboarding) and tells you exactly which network’s RPC request encountered errors. Perhaps ironically, this was literally the reason I fixed an issue with the Solana RPC. Before this update, it never actually refreshed the balance correctly so it wasn’t working. However, after this change, I was able to identify that the issue was not on my end (yay!) but was actually PublicNode ’s (the RPC I’m using for the majority of chains in this project for consistency, apart from Monad and now Solana) as I assumed it could fetch the user’s token accounts but it couldn’t so I had to switch to using the official Solana RPC which fixed the issue. For anyone who got lost somewhere in the previous paragraph, an RPC is a service that allows you to query data about the state of the blockchain (where crypto transactions are stored) so you can use it to see how much crypto you are holding. Token accounts are basically a weird quirk of Solana where your main account is used to hold Solana which links to associated token accounts (ATAs) , which each hold one token other than Solana. This is by far not a complete list but rather a list of the highlights of this PR; if you want to look at all the changes, please feel free to visit the page linked at the top of this devlog. That said, after this big change, I did say last devlog that I would be getting ready to release version v0.4.0 of this application which is exactly what I will do after adding Tron token support! Quick reminder, after v0.4.0 I am planning to add Ripple (XRP) support, preliminary (meaning like non-shielded probably) support for Zcash and revamp the settings page like I did to the onboarding in this PR. Further out, I will probably focus some more on the in-application swaps to aggregate data from major DEXs (decentralized exchanges) to get the best rates, matching other major wallets w/ more chain support, which would make my wallet actually competitive. 🤞
Devlog #12 Quite a bit more to report this time! Since last devlog, I’ve mostly been working on improving actual wallet functionality, fixing some smaller UI issues, and looking into performance. Recent changes Below is a quick summary of what I’ve been working on since the last devlog: Full TRC-20 token support is here! 🎊 Tron is no longer limited to just native TRX transfers, and the token validation/network logic has been updated to support TRC-20 tokens as well. Significantly improved Bitcoin support by adding proper BIP84 account discovery . VaultForge now scans both receive and change addresses, tracks which UTXOs belong to which derived addresses, signs each input with the correct derived key, and refreshes discovery before sending. Anecdote: I use Brave Wallet which did the receive and change addresses thing so my funds didn’t show up in previous versions of VaultForge. However, as of this update, I now am. Wallet unlocking now feels much faster ! Cached balances/prices are shown immediately while fresh data refreshes in the background. Improved asset cards so they show which network an asset belongs to . Assets worth less than $1 are now hidden from the portfolio/assets view unless VaultForge does not have price data for them. Fixed a few UI issues, including dashboard scrolling, refresh errors, escaping asset data (aka preventing XSS) , and copying the currently selected wallet address. Converted the remaining .js config files to TypeScript because apparently I cannot resist refactoring things even when it makes no difference whatsoever. For the first time in this series of devlogs, I’m linking the changes to relevant commits on GitHub wherever possible so you can have a look. Performance improvements I also found a few ways to reduce VaultForge’s roughly 10s full refresh time: Cached unlock (mentioned above): perceived unlock time is now closer to ~1–3s, although balances/prices can still take around the same amount of time to fully refresh in the background. Reuse HTTP clients: should save roughly ~0.2-1.5s by reusing connections. Concurrent provider calls: likely the biggest improvement, potentially bringing a ~10s refresh down to ~3–5s. Refresh prices separately: could make fresh balances appear another ~0.5–2s sooner. Derive Argon2 once: should save roughly a few hundred ms to ~1s on cold unlocks. The above estimated perf improvements are obviously quite variable and depend on a multitude of factors (+ I got ChatGPT to analyze my current code to make an estimate because how else would I do it), but there is definitely still a lot of low-hanging fruit here. Upcoming features Actual settings are still the elephant in the room 😭, so I definitely need to get around to those but since I think this may need a big PR a bit like the previous style improvements, I think I will do this after v0.4.0 (so therefore for v0.5.0 ). Ripple (XRP) support (at least for native token transfers), planned for v0.4.0 . Zcash (ZEC) support: I’ve got a feeling this one will take quite some time so at most I will implement transparent <=> transparent transactions before next release but will have to see. The remaining performance improvements mentioned above.
Devlog #13 I finally added different currencies ! Before, all prices were displayed in USD and now they can display in any of the below currencies: USD ($) EUR (€) GBP (£) JPY (¥) Shoutout to the fantastic API I used for this! Previously, I fetched CoinGecko pricing data which came in USD but I needed to convert this data into whatever currency the user chose so I had to find an API. However, there really weren’t any good forex APIs that were free with no rate limits when I searched for one so I turned to ChatGPT to find one and find one it did. This API gives daily central bank rates and even has data going back to 1948 on 201 currencies which is more than enough for this project. I also added the second performance improvement : caching the HTTP request client object to avoid having to recreate it on every API request. As of rn the project roadmap for the near future is this: Finish perf improvements Add basic Ripple (XRP) transaction support Maybe add transparent <=> transparent pool transaction support for Zcash (ZEC) Release VaultForge v0.5.0
Devlog #14 Not very much since last time; just some refactors and small improvements throughout. You can kind of tell by all the fix/chore/docs changes… btw improved settings is in the works - I think I’ll do some more progress over the next two days, then some actual chain support for Ripple. I’ve decided that I will release v0.4.0 before adding basic Zcash support as it’s been basically a month since last release and I don’t want to keep you guys waiting for those of you who want to download the binaries directly w/o building. Quick summary Now –> ~5 September: settings improvements 5 September –> 7 September: Ripple support 7/8 September: release of VaultForge v0.4.0
Devlog #15 Since the last devlog, I’ve worked on some more boring stuff: Tauri cleanup and desktop-specific improvements. I moved the application setup and command registration from src-tauri/src/main.rs into a new src-tauri/src/lib.rs . This keeps the entry point organized and follows Tauri’s recommended structure, while main.rs now only launches the library. I also replaced the browser clipboard API with Tauri’s native clipboard manager plugin. Copy buttons now use the desktop clipboard integration. Finally, VaultForge now enforces a single-instance window. If the app is launched while another instance is already open, the new launch focuses the existing main window instead of opening a second copy, which is far more desirable of a behaviour imo as it lets a user find a window without inadvertently opening even more. Plus some more random stuff: I now sign off all my commits As of today (4th of September), I also sign all my commits with a PGP key to verify all commits are made on my laptop and not by someone who hacked my GitHub account or smth - this is definitely overkill but why not Next, I’m continuing the settings improvements before moving on to Ripple support. P.S. I also randomly moved to Neovim as it looks much better than VS Code.
Devlog 16 sorry guys, i’m kind of late on this one tbh: I said that I would have the settings improvements, ripple support and all that ready by like monday but clearly nothing has happened since like the weekend. i have decided to delay the timleine by about a week as after some careful consideration I found it was wayyy too aggressive and my fingers can’t keep up with the typing speed i would need for that :) i seriously have no idae whatsoever why I thought it was possible to add that many features in such a short space of time. I know it kind of is but I have school now which means i have much less time for this with homework and studying and stuff. however, today I decided to lock in and actually do this and so I can assure you that i am hard at work doing the settings stuff rn and ripple support is absolutely coming right after that this next release really is going to be a big one… p.s. i attached a screenshot of some of the new commits i worked on (more are coming soon)
Devlog 17 perf improvement #3 done! 🎊 now refreshes are fully concurrent, w/ a limit of 4 requests at a time to avoid rate limiting. i haven’t fully tetsed it yet but it feels noticeably faster (like 25-35% faster) until the updated prices & balances are shown. plus, I kind of finished the settings stuff so i’ll be working on ripple support ig…
Devlog 18 i finished all the perf improvements! there was one that i left out though bc it probably wouldn’t have helped much in terms of performance and would have been a pain to implement. i am FINALLY going to move on to ripple support for the next few days…
Devlog 19 still cooking on the ripple support… i think i will be done by friday.
Devlog 20 so i finally added ripple support… and migrated everything to React for a much better, cleaner UI. and as always, i am late again. i actually could have finished on friday but i had other things to do (like homework) and i also wanted to migrate to react as well since I decided this will be my last release before the end of stardance, so i really want to add everything i can. this is because after stardance i will take a break of a few months on this project and then come back with a different hack club ysws challenge. the react migration was so big that i decided to use AI this time: the finished App.tsx file containing the react code is over 3090 lines of code (proof is the 2nd attached image)! that’s the largest code file i have ever worked on. since this is a huge change to the ui, i decided to create some before and after comparisons below. anyways, i decided to share some design decisions relating to the migration to react. i knew react was a big framework so it would add a few MB to the app’s file size (about 1-2 MB as of my recent testing) but the app itself is tiny anyway - not even 30 MB - so i thought it was really worth it. it gives you design consistency, more so than tailwindcss, which i needed since the more fun part for me was working on the backend and not the frontend (the user-facing part of the application). plus, the guys who work at coinbase (shoutout to them) made a goated plugin/theme/whatever you call it for react which makes my app have the default coinbase theme that i can tweak (i made the font monospace) which is alone like 70% of the stuff needed for the migration. i promise i will release v0.4.0 tomorrow…
Devlog 21 as promised, VaultForge v0.4.0 is out! this brings huge changes to wallet unlock speed, adds ripple support, adds BIP-84 addresses, and loads more. here is the link to the release page if you want to check it out. some interesting stats: there was an increase of >6,000 lines of code which is a more than 50% increase since v0.3.0 . 132 commits since last release. this is probably going to be my second-to-last devlog as i really want to hit the 100-hour mark.
Devlog 22 since the deadline for stardance has been extended by one month, i decided to keep going and make VaultForge as good as possible over the coming weeks. here’s a quick overview of what i will focus on next: actual swapping, and integration with multiple DEXes (think Jupiter, NEAR Intents, Uniswap, etc.) a better activity view token and chain icons! makes it much easier to differentiate between assets general performance and UI improvements with these new features, especially the integrated swapping, my wallet is finally going to be on par (mostly) with established wallets such as metamask. i’ve already got like 10+ commits since the last release that i will merge to main branch soon…
Devlog 23 15 new commits pushed to main ! still cooking on the integrated swapping support… sorry this is a short devlog; i’m more focused on the coding rn and will post when i’ve done something more substantial.
Devlog 24 - adding support for swapping after absolutely grinding on the support for swapping for the past week, here are some updates: 12 commits coming to main soon, about half bug fixes 4/10 things completed that i think are required for adding swapping support (more info below) i’ve also decided on a rough implementation order of swapping-related functionality: CCTP v2 transfers (basically moving USDC stablecoins across chains) Uniswap DEX (the biggest Decentrallized EXchange) Jupiter DEX ( the biggest dex on Solana) NEAR Intents (a cross-chain DEX) LI.FI aggregator (basically tells the walet the best market rates) i know this is kind of an ambitious timeline but i think i can pull it all off before the end of stardance on the 31st of october 🤞. i think i will manage to get CCTP transfers working by friday or sunday, depending on how much time i have.
Devlog 25 - some progress on the swapping i haven’t had much time in the last few days but i managed to do a big refactor to make the code more modular and cleaner. this is needed so that i can do more complex transactions instead of just basic transfers. i haven’t pushed it to main or committed it yet but it’s basically done. in terms of when CCTP support will ship, I think it will be by the end of sunday.
Devlog 26 unfortunately, it’s taking longer than i would like to add the swapping and CCTP functionality. i would say i’m about 80% there, but there are quite a few things that i have to think about and as such, i think i will get it working by tomorrow (tuesday). stay tuned! 👀
Devlog 27 - CCTP support is here… in like 30 minutes hang tight, it’s coming soon 🚀 i attached some proof , you guys can check out the transaction here more info on this tomorrow after v0.5.0 comes out with the CCTP support. you haven’t seen nothing yet, uniswap support coming next; stay tuned! probably coming in the next week or so…
Devlog 28 - coin icons! it finally looks sooo professional now… just look at those icons! they will also appear in the send and transfer (soon to be swap!) tabs over the coming days. uniswap dex integration is still the top priority though. 🫡 before there weren’t any (they were just grey) and every wallet has them so i made it better ig
Devlog 29 - more coin icons! specifically for AAVE, Chainlink (LINK), and Uniswap (UNI).
Devlog 30 - support for swapping (finally!) this took so long!!! i thought i would be done last friday but ig that was overly optimistic… there are still some small things i will fix/improve to make the experience a bit smoother in the coming days. Implementation so i added uniswap support for all supported evm chains; however only for same-chain transactions and only through one pool. this is suboptimal so i want to add cross-chain support and through multiple pools maybe in the future. to make it possible to do cross-chain swaps, i added Relay support (it’s an aggregator) were solvers compete to give a quote. the issue with this is that they charge quite a fee and so i really want to just use uniswap where possible. what’s next better uniswap integration (as mentioned above), plus support for solana potentially jupiter support (it’s a solana DEX) as it has really good rates and high liquidity.
Devlog 31 - swapping support for Solana! (partially) there’s now swapping support for solana, at least for DEX aggregators like LI.FI or Relay. i still need to figure out native solana DEX swapping on platforms like Jupiter…
Devlog 32 - what a grind!!! vaultforge v0.5.0 is finally out ! so many new features i honestly can’t remember all of them! just as a recap vaultforge is available on mac, linux, and windows. i’m on linux so i couldn’t really test the binaries on other oses that well. there’s a .deb and .rpm for linux for debian-based (debian, ubuntu, etc.) and fedora-based (rhel, fedora, bazzite) distros. and yes, before you ask, there is an appimage available. btw github actions is sooooo slow 🐌, especially the mac os x64 runners - grrrrrrr . i’ve been stuck here just waiting for the past 1/2 an hour… i was so frustrated that i decided to completely remove support for itnel macs cuz the build times are like 3x slower. sorry intel mac users. that took so long… finally ready to ship! tbh i mostly just did some ci stuff since last devlog but i also added some nice ui impirovements. guys please give me a good rating 🙏
Devlog #33 - some cleanup i migrated from vite to bun’s built-in bundler and minifier and updated the README.
Ships:
Fully functional, multi-chain (Bitcoin, EVM, and Solana support with more on the way) wallet. To test this project, please go to the GitHub repository linked to the project.
What did you make? VaultForge is a multi-chain, fully self-custodial crypto wallet with support for Bitcoin, EVM chains (e.g., Arbitrum, Avalanche, Base, BNB Chain, Ethereum, Polygon, etc.), Solana, Tron, and XRP. Additionally, VaultForge has support for swapping (see below screenshot) using Decentralized EXchanges (DEXs) such as Uniswap and Jupiter and DEX aggregators such as LI.FI and Relay. There is also support for transferring stablecoins (crypto tokens pegged to dollars) across chains with Circle’s CCTP v2. Why did I make it? I was frustrated with the lack of consistent support for major chains across crypto wallets and the need to use multiple of them. It turns out it was much harder to make than I thought. What was challenging? By far the hardest part was adding support for swapping and the CCTP features to some extent as it required extensive knowledge of each chain as they all behaved differently and needed a lot of research on each provider’s API. It also took loads of rigorous testing to make absolutely sure that it would work every time before doing a test with real funds (again, see the below screenshot). What are you proud of? I’m really happy with how the wallet onboarding turned out - all though it is quite a small part of the application I think it is quite easy to use and set up the wallet and lets you set up all the common settings such as your base currency and theme (light or dark mode). What should people know so they can test your project? Unfortunately, due to time constraints and the amount of extra code it would require to add this feature, I was not able to add a demo feature to test the wallet without real funds. This might make it hard to test the entirety of the wallet’s features, especially the sending and swapping part. If I had more time, I would definitely try to improve this. Also, due to the slow build times with GitHub Actions, I removed support for Intel Macs. I don’t think many people use them anymore though so I hope it isn’t too big of an issue....
|
1793764559.4729578
|
1793850959.4729578
|
|
24380
|
CubeTrainer by @EthanCubes | Stardance
|
EthanCubes
|
1
|
45.0
|
447
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-10T01:23:02Z", "hours": 45.0, "multiplier": 10.4, "payout": 447, "blessing": "neutral", "text": "I made a timer and algorithm driller for people who solve Rubik’s cubes (aka speedcubers). I have minimal experience with JavaScript, and since this project is extremely JavaScript heavy (9 JavaScript files with an average of like 150 lines each (max 869 min 25)), it was pretty challenging for me. I’m really proud of how I build most of the application by myself with minimal or no AI assistance. Note that this project is relatively niche and other programs that do the same thing but better already exist.", "repo": "https://github.com/EthanCubes/CubeTrainer", "demo": "https://ethancubes.github.io/CubeTrainer/"}]...
|
[{"post_id": 25631, "ts": "202 [{"post_id": 25631, "ts": "2026-07-10T01:17:26Z", "hours": 0.3631, "text": "Devlog 13: Final devlog before ship I didn’t add much, just fixed some bugs and inconvenient things. For example, the space bar (finally) no longer triggers the dropdown menus. That was very annoying. Also, I added an option to clear all site settings and data, in case you have a outdated save file (no one is going to have that except me probably) that’s messing things up. I also added some things to the README."}, {"post_id": 25617, "ts": "2026-07-10T00:25:25Z", "hours": 2.1794, "text": "Devlog #12: I separated the times for timer mode and driller mode. Since timer mode is intended for timing entire solves and driller mode is intended for only short portions of the solve, it doesn’t make sense for them to be lumped together. I did this by adding another object inside the object for stored solves, and renaming the existing object. So now, inside of the stored solves object, there’s one object named “timer” and another named “driller”, to make it easy to get the correct object for the selected mode. I kept encountering errors on the GitHub Pages, but everything’s fine on Live Server. It’s happened so many times, it’s getting annoying. there’s literally no visual difference why do i still have to include a screenshot"}, {"post_id": 25120, "ts": "2026-07-09T03:48:48Z", "hours": 6.0483, "text": "Devlog #11: You can finally change stuff! I added settings to the web app, including the option to hide certain elements and 3 themes. The settings even stay across sessions, unless you clear solves, in which case the settings will be reset. This was totally intentional to make sure users are mindful about their times and not just spam times and definitely not because I’m too lazy to fix that part of the code. :)"}, {"post_id": 24352, "ts": "2026-07-07T21:16:38Z", "hours": 0.7514, "text": "Devlog #10: So it turns out that much of the code that involves paths and fetching other files were broken. I didn’t realize that until after I posted the devlog yesterday. For the next 24 hours, I proceeded to try everything I could think of to fix it. In the process, I definitely had one or two crashouts somewhat reminiscent to Doggie Acheron 1% . I ended up just having the program fetch the JSON files and the favicon from GitHub instead of the local files. This does come with the downside of difficulties when testing the code when I don’t have wifi but that’s a small tradeoff considering I have wifi pretty often."}, {"post_id": 23798, "ts": "2026-07-06T23:08:34Z", "hours": 8.6786, "text": "Devlog #9: Finally. FINALLY I HAVE EVIDENCE TO BACK UP THAT THIS ISN’T A CSTIMER CLONE. The main feature that I intended to add from the start, and the main reason that I wanted to make this web app in the first place has finally been implemented. It is, of course, the ability to drill algorithms. Yes, it does need more polishing. No, you can’t import your own algorithm sets yet. But you can drill some Roux algorithms, and that’s already better than CSTimer and JPerm.net. Or at least that’s what I tell myself before I go to bed so I don’t feel like a waste of space. This session was definitely the toughest mental challenge I’ve probably ever experienced. I started to code this, but halfway through I just decided to revert some of the changes cause the code was messy and wasn’t working. I reverted the changes back to the left Git commit and discovered that I forgot what I was doing at that time, and also that the code was broken. I proceeded to spend like 3 more hours fixing my broken code, and somehow ended up with something semi-coherent. Features I need to add: Importing algorithm sets Changing the theme Tool to create algorithm sets Probably more but I forgot. (sorry it doesn’t really look much different in the screenshot but I promise I actually did a lot of stuff."}, {"post_id": 21703, "ts": "2026-07-03T20:01:51Z", "hours": 2.9117, "text": "Devlog #8: The window not displays the difference between the current solve and the previous solve. If the user got a faster time, it displays green. If they got a slower time, it displays red (like CSTimer lol). I also added a help window that dims the background when it appears. There’s not much in the help window right now. Bugs The most notable bug(?) I encountered is the thing where some coding languages return weird numbers when dealing with decimals. It turned out like -0.249999999999999999999996 or something like that. I used difference.toPrecision(2); to round it to 3 decimals and I guess it works for now."}, {"post_id": 20386, "ts": "2026-07-01T23:31:48Z", "hours": 3.2872, "text": "Devlog #7: I added box that lists all the solves the user has done, and it even saves when you close the browser or refresh the page. I also made the scramble copyable by clicking on it. I did this with local storage, so I guess it probably isn’t the best way to do it, but I couldn’t find any good tutorials for indexedDB online (probably because of my cooked attention span). I ended up storing the entire object inside a single local storage string. Notable bugs that I fixed -When any of the buttons are pressed with the mouse, any press of the spacebar triggers the button because apparently that’s how buttons work. Retrospectively, I probably could’ve use a CSS property or something idk to prevent this from happening but I just made fake buttons instead."}, {"post_id": 18849, "ts": "2026-06-30T01:31:56Z", "hours": 2.1625, "text": "Devlog #6: I CAN SEE COLOURS! I finally used some CSS, added background colours, and moved some elements. As you can see, the cube net drawing is at the bottom right and the timer and scrambles are centred now. I didn’t have internet for the majority of this, so I lowkey copied a bunch of code from my other project CubeOS, which I have saved locally still. I also added a function to hide all elements when the timer is timing, to help with focus by setting the display to none and switching it back afterwards. Lastly, I wrote a couple of JSON files (with the help of AI when I did have internet for a few minutes) that contain the cubing algorithms that the drilling mode will use. But after I was done writing them I discovered that I don’t know how to actually read files using JavaScript, so I’ll be figuring that out later."}, {"post_id": 18013, "ts": "2026-06-28T23:52:49Z", "hours": 5.0386, "text": "Devlog #5: I spent a couple of hours doing optimizations and adding features that aren’t used yet but will definitely be built upon in the future. The one change that the user can actually see doesn’t work yet because I added the UI for it before the actual functionality was added. I’m going to attach a screenshot and try to see if you can spot the difference. I did try to add a new feature (hence the aforementioned UI change) but I ended up running into a bunch of issues including the following: Functions being called before they’re defined Browser running out of memory somehow Distraction Skill issue (please laugh. i need external validation) Here are the things I need to do still: [] Add a drilling mode that helps you master doing Rubik’s cubes algorithms [] Add ability to upload your own algorithms to drill [] Add ability for the timer to store solves in local story [] Add compatibility with CSTimer.net so that you can export or import timer solves. [] Add a somewhat good GUI"}, {"post_id": 16578, "ts": "2026-06-26T23:22:03Z", "hours": 8.5214, "text": "Devlog #4: I added a net of the scrambled Rubik’s cube to my webpage. Even though a real cube moves in separate pieces, I decided to calculate the cube using the stickers. I used an array to represent all 54 stickers on the cube, and used functions that switched around the stickers to represent turning the cube’s faces. I was originally going to make a function switching around the stickers for every single face turn (there’s 12, not including rotating the entire cube, the middle slice, and the double moves). But after I made the function for turning the top face and it already took up like 100 lines of code, and deciding that I don’t want to get carpal tunnel syndrome when I’m not even an adult, I realized I could just rotate the entire cube and stick with only one face turn. This brought down my code from a potential 1200 lines to only 300. At this point, I’ve spent like 2 hours on making this cube net but there’s still nothing on screen to show for it. So I quickly coded a net of the cube using HTML and CSS and used JavaScript to change each element according to what its color in the array is. Just when everything was just about done, I ran into the biggest problem of this entire session: the net/drawing wasn’t accurate. After about 2 hours of debugging, I discovered I forgot to reset the cube before “scrambling” it again. I literally wrote a function doing just that and I forgot to use it. (I’m reading the page on how to write a devlog and apparently they’re only supposed to be 4-6 sentences… lol)"}, {"post_id": 14806, "ts": "2026-06-24T01:31:37Z", "hours": 1.6894, "text": "Devlog #3: I SWEAR THIS IS NOT INTENDED (ENTIRELY) AS A CSTIMER CLONE. Soooo… I added scrambles to my web app. (You can see the current scramble above the time). I just used JavaScript random to pick from the basic 6 moves a 3x3 Rubik’s cube, as well as a modifier (normal, prime (counterclockwise), and 2 (twice). This move is then checked against the previous move so that there won’t be any cases of someone having to do the same move twice in a row. Every time the timer stops, a new scramble is generated and replaces the old one. Also, I added a delay of one second that the user has to hold to trigger the timer. In addition to that, the timer now changes colour when you’re holding the spacebar down before starting the timer. It’s green if the timer will start when you release it, and red if it’ll just cancel the timer. Wow, this is looking more and more like a CSTimer clone, right? (honestly I agree)"}, {"post_id": 14604, "ts": "2026-06-23T19:31:50Z", "hours": 1.7858, "text": "Devlog #2: I fixed most problems with the timer. It now updates in real time, and you can (and must) use the space bar to activate it. You start it after you release the space bar, and stop it as soon as you press the space bar again, without automatically starting the timer every time you stop it (believe me, that was a problem for a long time). So far, it’s turning out like a CSTimer clone, which isn’t actually what I want at the end of the day. Even though this will probably look like a CSTimer clone for a very long time, eventually I swear I’ll make it have additional functionality."}, {"post_id": 14086, "ts": "2026-06-23T02:11:19Z", "hours": 1.485, "text": "Devlog #1: I’m trying to build a web application that acts like a timer for solving Rubik’s cubes, a scramble generator, and a cubing algorithm driller. This coding session, I built a timer (or is it called a stopwatch?). It’s not that good, and you have to physically click a button with your mouse to start and stop the timer. It also does not update live and displays the time in milliseconds, which is… not the best. I’ll improve on it later though. I’ve gained a bit of JavaScript experience from my WebOS project, so this was honestly not that hard. It was very satisfying to code though. The actual web page still looks ugly though, I’ll style it after I add the bulk of the functionality probably."}]...
|
Title: CubeTrainer by @EthanCubes | Stardance
Dev Title: CubeTrainer by @EthanCubes | Stardance
Devlogs:
Devlog #1: I’m trying to build a web application that acts like a timer for solving Rubik’s cubes, a scramble generator, and a cubing algorithm driller. This coding session, I built a timer (or is it called a stopwatch?). It’s not that good, and you have to physically click a button with your mouse to start and stop the timer. It also does not update live and displays the time in milliseconds, which is… not the best. I’ll improve on it later though. I’ve gained a bit of JavaScript experience from my WebOS project, so this was honestly not that hard. It was very satisfying to code though. The actual web page still looks ugly though, I’ll style it after I add the bulk of the functionality probably.
Devlog #2: I fixed most problems with the timer. It now updates in real time, and you can (and must) use the space bar to activate it. You start it after you release the space bar, and stop it as soon as you press the space bar again, without automatically starting the timer every time you stop it (believe me, that was a problem for a long time). So far, it’s turning out like a CSTimer clone, which isn’t actually what I want at the end of the day. Even though this will probably look like a CSTimer clone for a very long time, eventually I swear I’ll make it have additional functionality.
Devlog #3: I SWEAR THIS IS NOT INTENDED (ENTIRELY) AS A CSTIMER CLONE. Soooo… I added scrambles to my web app. (You can see the current scramble above the time). I just used JavaScript random to pick from the basic 6 moves a 3x3 Rubik’s cube, as well as a modifier (normal, prime (counterclockwise), and 2 (twice). This move is then checked against the previous move so that there won’t be any cases of someone having to do the same move twice in a row. Every time the timer stops, a new scramble is generated and replaces the old one. Also, I added a delay of one second that the user has to hold to trigger the timer. In addition to that, the timer now changes colour when you’re holding the spacebar down before starting the timer. It’s green if the timer will start when you release it, and red if it’ll just cancel the timer. Wow, this is looking more and more like a CSTimer clone, right? (honestly I agree)
Devlog #4: I added a net of the scrambled Rubik’s cube to my webpage. Even though a real cube moves in separate pieces, I decided to calculate the cube using the stickers. I used an array to represent all 54 stickers on the cube, and used functions that switched around the stickers to represent turning the cube’s faces. I was originally going to make a function switching around the stickers for every single face turn (there’s 12, not including rotating the entire cube, the middle slice, and the double moves). But after I made the function for turning the top face and it already took up like 100 lines of code, and deciding that I don’t want to get carpal tunnel syndrome when I’m not even an adult, I realized I could just rotate the entire cube and stick with only one face turn. This brought down my code from a potential 1200 lines to only 300. At this point, I’ve spent like 2 hours on making this cube net but there’s still nothing on screen to show for it. So I quickly coded a net of the cube using HTML and CSS and used JavaScript to change each element according to what its color in the array is. Just when everything was just about done, I ran into the biggest problem of this entire session: the net/drawing wasn’t accurate. After about 2 hours of debugging, I discovered I forgot to reset the cube before “scrambling” it again. I literally wrote a function doing just that and I forgot to use it. (I’m reading the page on how to write a devlog and apparently they’re only supposed to be 4-6 sentences… lol)
Devlog #5: I spent a couple of hours doing optimizations and adding features that aren’t used yet but will definitely be built upon in the future. The one change that the user can actually see doesn’t work yet because I added the UI for it before the actual functionality was added. I’m going to attach a screenshot and try to see if you can spot the difference. I did try to add a new feature (hence the aforementioned UI change) but I ended up running into a bunch of issues including the following: Functions being called before they’re defined Browser running out of memory somehow Distraction Skill issue (please laugh. i need external validation) Here are the things I need to do still: [] Add a drilling mode that helps you master doing Rubik’s cubes algorithms [] Add ability to upload your own algorithms to drill [] Add ability for the timer to store solves in local story [] Add compatibility with CSTimer.net so that you can export or import timer solves. [] Add a somewhat good GUI
Devlog #6: I CAN SEE COLOURS! I finally used some CSS, added background colours, and moved some elements. As you can see, the cube net drawing is at the bottom right and the timer and scrambles are centred now. I didn’t have internet for the majority of this, so I lowkey copied a bunch of code from my other project CubeOS, which I have saved locally still. I also added a function to hide all elements when the timer is timing, to help with focus by setting the display to none and switching it back afterwards. Lastly, I wrote a couple of JSON files (with the help of AI when I did have internet for a few minutes) that contain the cubing algorithms that the drilling mode will use. But after I was done writing them I discovered that I don’t know how to actually read files using JavaScript, so I’ll be figuring that out later.
Devlog #7: I added box that lists all the solves the user has done, and it even saves when you close the browser or refresh the page. I also made the scramble copyable by clicking on it. I did this with local storage, so I guess it probably isn’t the best way to do it, but I couldn’t find any good tutorials for indexedDB online (probably because of my cooked attention span). I ended up storing the entire object inside a single local storage string. Notable bugs that I fixed -When any of the buttons are pressed with the mouse, any press of the spacebar triggers the button because apparently that’s how buttons work. Retrospectively, I probably could’ve use a CSS property or something idk to prevent this from happening but I just made fake buttons instead.
Devlog #8: The window not displays the difference between the current solve and the previous solve. If the user got a faster time, it displays green. If they got a slower time, it displays red (like CSTimer lol). I also added a help window that dims the background when it appears. There’s not much in the help window right now. Bugs The most notable bug(?) I encountered is the thing where some coding languages return weird numbers when dealing with decimals. It turned out like -0.249999999999999999999996 or something like that. I used difference.toPrecision(2); to round it to 3 decimals and I guess it works for now.
Devlog #9: Finally. FINALLY I HAVE EVIDENCE TO BACK UP THAT THIS ISN’T A CSTIMER CLONE. The main feature that I intended to add from the start, and the main reason that I wanted to make this web app in the first place has finally been implemented. It is, of course, the ability to drill algorithms. Yes, it does need more polishing. No, you can’t import your own algorithm sets yet. But you can drill some Roux algorithms, and that’s already better than CSTimer and JPerm.net. Or at least that’s what I tell myself before I go to bed so I don’t feel like a waste of space. This session was definitely the toughest mental challenge I’ve probably ever experienced. I started to code this, but halfway through I just decided to revert some of the changes cause the code was messy and wasn’t working. I reverted the changes back to the left Git commit and discovered that I forgot what I was doing at that time, and also that the code was broken. I proceeded to spend like 3 more hours fixing my broken code, and somehow ended up with something semi-coherent. Features I need to add: Importing algorithm sets Changing the theme Tool to create algorithm sets Probably more but I forgot. (sorry it doesn’t really look much different in the screenshot but I promise I actually did a lot of stuff.
Devlog #10: So it turns out that much of the code that involves paths and fetching other files were broken. I didn’t realize that until after I posted the devlog yesterday. For the next 24 hours, I proceeded to try everything I could think of to fix it. In the process, I definitely had one or two crashouts somewhat reminiscent to Doggie Acheron 1% . I ended up just having the program fetch the JSON files and the favicon from GitHub instead of the local files. This does come with the downside of difficulties when testing the code when I don’t have wifi but that’s a small tradeoff considering I have wifi pretty often.
Devlog #11: You can finally change stuff! I added settings to the web app, including the option to hide certain elements and 3 themes. The settings even stay across sessions, unless you clear solves, in which case the settings will be reset. This was totally intentional to make sure users are mindful about their times and not just spam times and definitely not because I’m too lazy to fix that part of the code. :)
Devlog #12: I separated the times for timer mode and driller mode. Since timer mode is intended for timing entire solves and driller mode is intended for only short portions of the solve, it doesn’t make sense for them to be lumped together. I did this by adding another object inside the object for stored solves, and renaming the existing object. So now, inside of the stored solves object, there’s one object named “timer” and another named “driller”, to make it easy to get the correct object for the selected mode. I kept encountering errors on the GitHub Pages, but everything’s fine on Live Server. It’s happened so many times, it’s getting annoying. there’s literally no visual difference why do i still have to include a screenshot
Devlog 13: Final devlog before ship I didn’t add much, just fixed some bugs and inconvenient things. For example, the space bar (finally) no longer triggers the dropdown menus. That was very annoying. Also, I added an option to clear all site settings and data, in case you have a outdated save file (no one is going to have that except me probably) that’s messing things up. I also added some things to the README.
Ships:
I made a timer and algorithm driller for people who solve Rubik’s cubes (aka speedcubers). I have minimal experience with JavaScript, and since this project is extremely JavaScript heavy (9 JavaScript files with an average of like 150 lines each (max 869 min 25)), it was pretty challenging for me. I’m really proud of how I build most of the application by myself with minimal or no AI assistance. Note that this project is relatively niche and other programs that do the same thing but better already exist....
|
1793764558.2244544
|
1793850958.2244544
|
|
29160
|
My first slack bot! by @shane8 | Stardance
|
shane8
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @shane8 | Stardance
|
1793764557.323419
|
1794369357.323419
|
|
18573
|
My very own WebOS by @michael67 | Stardance
|
michael67
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @michael67 | Stardance
|
1793764556.44779
|
1794369356.44779
|
|
904
|
Girlfriend Simulator by @snehasish | Stardance
|
|
2
|
37.0
|
434
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-03T20:03:26Z", "hours": 9.0, "multiplier": 15.93, "payout": 148, "blessing": "neutral", "text": "Major Updates for Girlfriend Simulator Note: This is the final update (ship) and no more updates will be made in future to this project. Main Updates Girlfriend Memories: Your Girlfriend remembers every small detail you share about yourself in her chat. Persistent Relationship Profile: Your girlfriend also remembers how you treated her on your last conversation and her mood really depends on that the next time you have a conversation with her Your own Models: Your girlfriend can run on your own API key. By default uses Google Gemini 2.5 Flash (so you will need a Gemini API Key). This removes any limits to daily conversations (capped at 20 when using not-your-model. Mood Aware User Interface: Your chat colors, themes and styling changes based on your girlfriend’s mood. Helps you understand what situation you’re currently in XD", "repo": "https://github.com/snhsish/gfsim", "demo": "https://gfsim.snehasish.xyz"}, {"ship_num": 2, "ts": "2026-06-08T09:27:01Z", "hours": 28.0, "multiplier": 12.02, "payout": 286, "blessing": "neutral", "text": "I built a Girlfriend Simulator which simulates a start-to-end relationship with your personally characterized girlfriend (powered by different fine-grained AI models). Why is it different from an AI wrapper or asking ChatGPT to “pretend to be my girlfriend?”: Well, the experience here is more natural and more likely-to-be-a-real-girlfriend type xi. Problems faced: getting the model to be more natural. I had fine-tuned a Qwen model which performed pretty well and NATURAL when replying as girlfriend, but due to high costing I cannot be putting it out in the public for free usage, so I had to use a fine-grained Qwen model (system prompt) Some pages / features are still not completed, but the chat experience is working completely fine!", "repo": "https://github.com/snhsish/gfsim", "demo": "https://gfsim.snehasish.xyz"}]...
|
[{"post_id": 13566, "ts": "202 [{"post_id": 13566, "ts": "2026-06-22T06:36:28Z", "hours": 4.0833, "text": "Girlfriend Simulator : Major Update This update is all about feature improvement. What’s New Persistent Relationship Profile Previously relationship state was ephemeral, i.e. everytime you started a new chat, your relationship state was back to NORMAL. But now things have changed. A persistent relationship state has been introduced. Your behavioral rating is now taken more seriously. How you reply, how you react and how you understand her, matters now Inactivity Tracking Your latest message is now tracked by the system to set your girlfriend’s mood. If you have ghosted her for long, it must have affected her behaviour. This lets her react naturally to absences (cold, sarcastic, or confrontational depending on health/mood). Mood-aware UI The UI of the chat changes according to your girlfriend’s mood now. So you get a hint when to make her feel wanted and when to make her laugh."}, {"post_id": 11313, "ts": "2026-06-18T14:40:13Z", "hours": 3.2144, "text": "You can now configure and bring in your own API Keys Currently only Gemini API Key is supported which uses the gemini-2.5-flash model Why bring in your own keys? Well there’s a 20 message per user daily limit when using the server provided model. But you definitely might want to talk to your GF more than just 20 messages a day right :) So if you bring in your own keys, you can chat without any limits! You can view usages of your own keys from the Usage page itself ( /account/usage ) Are my keys safe? Your keys are stored in your browser’s localStorage. It’s not sent to our servers at all. (You can verify checking the opensource code anyways!) ALSO, thanks to some of you guys who tried out the simulator, tried to jailbreak and manipulate the models, it helped me understand the system a little more. ALSO, the sim is completely SFW - even if you go NSFW. LYG<3"}, {"post_id": 5578, "ts": "2026-06-09T12:56:21Z", "hours": 2.0533, "text": "Your can now view your Girlfriend’s “Memories”. Memories are basically a collection of details (birthday, job description, reminders, etc.) you mention/share about yourself in chat. It is stored, so that it can be passed as context for your girlfriend. So now she actually remembers the “small details about you”. Uses a second LLM call which analyzes your messages to check if any important “detail” about you has been sent, so your girlfriend remembers it. You can always delete the sensitive ones and recommended."}, {"post_id": 4490, "ts": "2026-06-07T20:25:51Z", "hours": 10.8542, "text": "Lot of updates: Chat persistence: Your chats with your GF are now permanently stored in cloud, so you can access the chats anytime. Chats infinite scroll: To not display all your 100k messages with your GF at once and break stuff, infinite scroll has been added to chat to load old chats on demand Add reaction to messages: You can now react to messages from your girlfriend (and there’s a chance she might get pssed off from that and reply about it). Also your girlfriend can react to your messages too now. * You can currently only react to message groups and now individual message bubble, it’ll be fixed in a future update. Added no-reply handler: SO BASICALLY you can be left ON-SEEN or ON-DELIVERED by your girlfriend if you misbehave lol Some bug fixes: add limit to user message input, GF’s side texts not being stored in DB, etc. Some UI/UX optimizations alongside system prompt optimizations for the MODEL. * I really want to optimize the system prompt even further more ’cause currently it uses almost 1k tokens per message which feels quiet unoptimized and over-usage of tokens"}, {"post_id": 3331, "ts": "2026-06-06T06:38:09Z", "hours": 6.5922, "text": "Added: Account Page: where you can update your OWN profile details like your avatar, name, description, DOB, MBTI, zodiac, etc. which will let your girlfriend know about you and your personality (from your description of you) User Welcome Screen and Navigation Tour: For better UX and understandibility, I have added a welcome screen modal with three steps explaining what the app is about and how it works + sidebar tour for explaining what each link does Signout button in account page Next:: Public Use Launch"}, {"post_id": 2181, "ts": "2026-06-04T15:13:05Z", "hours": 5.2556, "text": "made the usage page which shows tokens and messages for the past 14 days also here are some sample girlfriend responses which felt natural to me"}, {"post_id": 762, "ts": "2026-06-02T12:29:59Z", "hours": 1.7394, "text": "chats now work model: qwen the model smh replies and added multi message support"}, {"post_id": 414, "ts": "2026-06-01T20:18:42Z", "hours": 1.0042, "text": "updated message input and added attachment input (menu), emoji selector and GIF picker also implemented auto-height increment for the message input textarea and enter-is-send and shift-enter-is-not-send for the message input next: send the message and get a response (basic) via VERCEL AI SDK + Gemini Google API"}, {"post_id": 341, "ts": "2026-06-01T17:20:30Z", "hours": 2.1508, "text": "setup and designed the app interface and the chat page with beautiful starter texts to send to your AI girlfriend and get the convo started. next: design the chat input section along"}, {"post_id": 184, "ts": "2026-06-01T06:32:25Z", "hours": 0.5367, "text": "Added user authentication (login page) using Google OAuth (better-auth + supabase) setup"}]...
|
Title: Girlfriend Simulator by @snehasish | Starda Title: Girlfriend Simulator by @snehasish | Stardance
Devlogs:
Added user authentication (login page) using Google OAuth (better-auth + supabase) setup
setup and designed the app interface and the chat page with beautiful starter texts to send to your AI girlfriend and get the convo started. next: design the chat input section along
updated message input and added attachment input (menu), emoji selector and GIF picker also implemented auto-height increment for the message input textarea and enter-is-send and shift-enter-is-not-send for the message input next: send the message and get a response (basic) via VERCEL AI SDK + Gemini Google API
chats now work model: qwen the model smh replies and added multi message support
made the usage page which shows tokens and messages for the past 14 days also here are some sample girlfriend responses which felt natural to me
Added: Account Page: where you can update your OWN profile details like your avatar, name, description, DOB, MBTI, zodiac, etc. which will let your girlfriend know about you and your personality (from your description of you) User Welcome Screen and Navigation Tour: For better UX and understandibility, I have added a welcome screen modal with three steps explaining what the app is about and how it works + sidebar tour for explaining what each link does Signout button in account page Next:: Public Use Launch
Lot of updates: Chat persistence: Your chats with your GF are now permanently stored in cloud, so you can access the chats anytime. Chats infinite scroll: To not display all your 100k messages with your GF at once and break stuff, infinite scroll has been added to chat to load old chats on demand Add reaction to messages: You can now react to messages from your girlfriend (and there’s a chance she might get pssed off from that and reply about it). Also your girlfriend can react to your messages too now. * You can currently only react to message groups and now individual message bubble, it’ll be fixed in a future update. Added no-reply handler: SO BASICALLY you can be left ON-SEEN or ON-DELIVERED by your girlfriend if you misbehave lol Some bug fixes: add limit to user message input, GF’s side texts not being stored in DB, etc. Some UI/UX optimizations alongside system prompt optimizations for the MODEL. * I really want to optimize the system prompt even further more ’cause currently it uses almost 1k tokens per message which feels quiet unoptimized and over-usage of tokens
Your can now view your Girlfriend’s “Memories”. Memories are basically a collection of details (birthday, job description, reminders, etc.) you mention/share about yourself in chat. It is stored, so that it can be passed as context for your girlfriend. So now she actually remembers the “small details about you”. Uses a second LLM call which analyzes your messages to check if any important “detail” about you has been sent, so your girlfriend remembers it. You can always delete the sensitive ones and recommended.
You can now configure and bring in your own API Keys Currently only Gemini API Key is supported which uses the gemini-2.5-flash model Why bring in your own keys? Well there’s a 20 message per user daily limit when using the server provided model. But you definitely might want to talk to your GF more than just 20 messages a day right :) So if you bring in your own keys, you can chat without any limits! You can view usages of your own keys from the Usage page itself ( /account/usage ) Are my keys safe? Your keys are stored in your browser’s localStorage. It’s not sent to our servers at all. (You can verify checking the opensource code anyways!) ALSO, thanks to some of you guys who tried out the simulator, tried to jailbreak and manipulate the models, it helped me understand the system a little more. ALSO, the sim is completely SFW - even if you go NSFW. LYG<3
Girlfriend Simulator : Major Update This update is all about feature improvement. What’s New Persistent Relationship Profile Previously relationship state was ephemeral, i.e. everytime you started a new chat, your relationship state was back to NORMAL. But now things have changed. A persistent relationship state has been introduced. Your behavioral rating is now taken more seriously. How you reply, how you react and how you understand her, matters now Inactivity Tracking Your latest message is now tracked by the system to set your girlfriend’s mood. If you have ghosted her for long, it must have affected her behaviour. This lets her react naturally to absences (cold, sarcastic, or confrontational depending on health/mood). Mood-aware UI The UI of the chat changes according to your girlfriend’s mood now. So you get a hint when to make her feel wanted and when to make her laugh.
Ships:
I built a Girlfriend Simulator which simulates a start-to-end relationship with your personally characterized girlfriend (powered by different fine-grained AI models). Why is it different from an AI wrapper or asking ChatGPT to “pretend to be my girlfriend?”: Well, the experience here is more natural and more likely-to-be-a-real-girlfriend type xi. Problems faced: getting the model to be more natural. I had fine-tuned a Qwen model which performed pretty well and NATURAL when replying as girlfriend, but due to high costing I cannot be putting it out in the public for free usage, so I had to use a fine-grained Qwen model (system prompt) Some pages / features are still not completed, but the chat experience is working completely fine!
Major Updates for Girlfriend Simulator Note: This is the final update (ship) and no more updates will be made in future to this project. Main Updates Girlfriend Memories: Your Girlfriend remembers every small detail you share about yourself in her chat. Persistent Relationship Profile: Your girlfriend also remembers how you treated her on your last conversation and her mood really depends on that the next time you have a conversation with her Your own Models: Your girlfriend can run on your own API key. By default uses Google Gemini 2.5 Flash (so you will need a Gemini API Key). This removes any limits to daily conversations (capped at 20 when using not-your-model. Mood Aware User Interface: Your chat colors, themes and styling changes based on your girlfriend’s mood. Helps you understand what situation you’re currently in XD...
|
1793764555.2431095
|
1793850955.2431095
|
|
30956
|
PreShoot by @DanielLiu | Stardance
|
DanielLiu
|
1
|
0.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-05T15:54:42Z", "hours": 0.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "PreShoot is a personalized AI creative assistant built for creators who struggle with knowing what to post. Instead of giving generic ideas, PreShoot learns your style, niche, gear, and platform, then turns a single photo into tailored, ready-to-film content concepts. Each idea comes with clear creative direction — including shot breakdowns, angles, pacing, lighting suggestions, and editing style — designed around how you actually create. The goal is simple: remove creative uncertainty and help creators stay consistent, improve content quality, and execute faster without overthinking what to post next. PreShoot is built for modern creators, from short-form content on TikTok and Instagram to more structured storytelling on YouTube. Less guessing. More creating.", "repo": "https://github.com/Dan904312/PRESHOOT", "demo": "https://preshoot.vercel.app"}]...
|
[{"post_id": 22798, "ts": "202 [{"post_id": 22798, "ts": "2026-07-05T11:41:31Z", "hours": 0.2811, "text": "I recently got my landing page up!! It is vibe coded by claude and lowkey looks kinda bad but I’ll make it better!!"}]...
|
Title: PreShoot by @DanielLiu | Stardance
Devlogs Title: PreShoot by @DanielLiu | Stardance
Devlogs:
I recently got my landing page up!! It is vibe coded by claude and lowkey looks kinda bad but I’ll make it better!!
Ships:
PreShoot is a personalized AI creative assistant built for creators who struggle with knowing what to post. Instead of giving generic ideas, PreShoot learns your style, niche, gear, and platform, then turns a single photo into tailored, ready-to-film content concepts. Each idea comes with clear creative direction — including shot breakdowns, angles, pacing, lighting suggestions, and editing style — designed around how you actually create. The goal is simple: remove creative uncertainty and help creators stay consistent, improve content quality, and execute faster without overthinking what to post next. PreShoot is built for modern creators, from short-form content on TikTok and Instagram to more structured storytelling on YouTube. Less guessing. More creating....
|
1793764554.11026
|
1793850954.11026
|
|
57574
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764553.2533884
|
1794628553.2533884
|
|
25447
|
Frictionless by @maliha | Stardance
|
maliha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @maliha | Stardance
|
1793764552.3549533
|
1794369352.3549533
|
|
46856
|
pi - web os by @NotSuspiciousProgrammer | Stardanc pi - web os by @NotSuspiciousProgrammer | Stardance...
|
NotSuspiciousProgrammer
|
2
|
9.0
|
24
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-14T00:06:08Z", "hours": 6.0, "multiplier": 3.5, "payout": 24, "blessing": "neutral", "text": "I made a PI-THEMED WEB-OS!! The most challenging part was the script for making “windows” draggable; I had to look through some tutorials for that. Either way, as a professional pi enthusiast, I’m pretty excited for this pi theme! As part of the WebOS2 Mission, I have more than three new features from what I submitted to WebOS1. Some of them include the Settings App, Bible App, and sound effects that say the next digit of pi each time you open/close an app. That part was very fun :P I hope you enjoy my Pi webOS! Please provide feedback on my project, whether you’re a pi enthusiast or not :)", "repo": "https://github.com/kpoovakan/piwebos", "demo": "https://kpoovakan.github.io/piwebos"}, {"ship_num": 2, "ts": "2026-08-11T23:36:39Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a pi-themed “operating system” that can run in a web browser! The hardest part for me was making the windows draggable, since I ran into some bugs even while following the guide. Thanks to some clarification in a W3Schools article, I managed to fix those bugs. I have some features in this OS that the guide doesn’t list, one which is the app that plays music. The other is the helpful text at the bottom of the screen (telling you where the apps can be opened!) that disappears when an app is opened. I enjoyed making this pi-themed “operating system”. I hope you enjoy exploring it!", "repo": "https://github.com/kpoovakan/piwebos", "demo": "https://kpoovakan.github.io/piwebos"}]...
|
[{"post_id": 67747, "ts": "202 [{"post_id": 67747, "ts": "2026-09-13T23:59:20Z", "hours": 1.6781, "text": "I updated my README! Now it has two images, a setup guide, and an organized table for my “apps”. There’s also a features list and a small credits section. I also went through my code and fixed all the bugs I could find. Time to ship!!"}, {"post_id": 66994, "ts": "2026-09-13T00:24:00Z", "hours": 3.9725, "text": "I added more apps to my webOS! Now it has a pi app, games, a web app, an e-mail redirect, a file manager, a notepad, a calculator, a Turbowarp redirect, a music app, YouTube, maps, a flight tracker redirect, a Bible app, and a settings app. The settings app lets you customize things like the time format and sound effect preferences."}, {"post_id": 45470, "ts": "2026-08-11T23:27:57Z", "hours": 0.8372, "text": "I added the content to my three applications! Now, there’s an app with stuff about pi, an app featuring my other coding projects, and a section to play popular classical piano pieces."}, {"post_id": 45452, "ts": "2026-08-11T22:21:00Z", "hours": 1.5489, "text": "I added more CSS styles and customization. I also made the “windows” draggable with JavaScript, and I added buttons to open and close the app placeholders. Next I’ll be adding things to the apps themselves!"}, {"post_id": 45398, "ts": "2026-08-11T20:32:05Z", "hours": 0.325, "text": "Added core code for my pi-themed web OS! I created a blue color palette for the CSS, added placeholder tags for what shall soon become the OS apps, and implemented a pi-themed background."}]...
|
Title: pi - web os by @NotSuspiciousProgrammer | S Title: pi - web os by @NotSuspiciousProgrammer | Stardance
Devlogs:
Added core code for my pi-themed web OS! I created a blue color palette for the CSS, added placeholder tags for what shall soon become the OS apps, and implemented a pi-themed background.
I added more CSS styles and customization. I also made the “windows” draggable with JavaScript, and I added buttons to open and close the app placeholders. Next I’ll be adding things to the apps themselves!
I added the content to my three applications! Now, there’s an app with stuff about pi, an app featuring my other coding projects, and a section to play popular classical piano pieces.
I added more apps to my webOS! Now it has a pi app, games, a web app, an e-mail redirect, a file manager, a notepad, a calculator, a Turbowarp redirect, a music app, YouTube, maps, a flight tracker redirect, a Bible app, and a settings app. The settings app lets you customize things like the time format and sound effect preferences.
I updated my README! Now it has two images, a setup guide, and an organized table for my “apps”. There’s also a features list and a small credits section. I also went through my code and fixed all the bugs I could find. Time to ship!!
Ships:
I made a pi-themed “operating system” that can run in a web browser! The hardest part for me was making the windows draggable, since I ran into some bugs even while following the guide. Thanks to some clarification in a W3Schools article, I managed to fix those bugs. I have some features in this OS that the guide doesn’t list, one which is the app that plays music. The other is the helpful text at the bottom of the screen (telling you where the apps can be opened!) that disappears when an app is opened. I enjoyed making this pi-themed “operating system”. I hope you enjoy exploring it!
I made a PI-THEMED WEB-OS!! The most challenging part was the script for making “windows” draggable; I had to look through some tutorials for that. Either way, as a professional pi enthusiast, I’m pretty excited for this pi theme! As part of the WebOS2 Mission, I have more than three new features from what I submitted to WebOS1. Some of them include the Settings App, Bible App, and sound effects that say the next digit of pi each time you open/close an app. That part was very fun :P I hope you enjoy my Pi webOS! Please provide feedback on my project, whether you’re a pi enthusiast or not :)...
|
1793764551.089428
|
1793850951.089428
|
|
57571
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764550.2241228
|
1794628550.2241228
|
|
54669
|
BLACKBOX (complain filing application) by @Fabulou BLACKBOX (complain filing application) by @FabulousHippoOfOrangeLake | Stardance...
|
FabulousHippoOfOrangeLake
|
1
|
22.5
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-09T16:28:54Z", "hours": 15.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a python desktop app for student feedback, issue and complain management. The main idea was to provide students with one core place to report problems. Students use their roll number for logins, they can upvote issues to show its urgency, they can change their own password. There is also a separate admin dashboard with issues organised cleanly according to priority. I am proud of using Custom Tkinter for the first time but not proud of having 1200 lines of code in one file! I hope u find this project worthy and fun to use!", "repo": "https://github.com/sharmashashwat27-source/BLACKBOX", "demo": "https://github.com/sharmashashwat27-source/BLACKBOX/releases/tag/custom-Tkinter"}]...
|
[{"post_id": 72698, "ts": "202 [{"post_id": 72698, "ts": "2026-09-23T15:05:48Z", "hours": 7.5047, "text": "DEVLOG #9 idk SO i added so may features and it was such a pain in the ass to retain feature when adding new ones i kept messing up here and there and even forgot to call the simplest of functions. But now i’m here and this is what I added: Different types of admin (headmaster, housemaster senior master etc.) feature to chose who u want to submit the report too feature to forward the issue (as an admin) - if the particular admin finds its not for him logging in if ur in guest mode and logging out if ur in student mode my reports and all reports button added a view issue button which lets u view the full issue instead of the dot expanding thing i had before lastly the stupidest but most needed asterisk while entering passwords."}, {"post_id": 64289, "ts": "2026-09-08T15:59:34Z", "hours": 0.8783, "text": "DEVLOG#9 So today I finished the new gui design it isn’t as good and as clean as my refernce but I am still happ with it i even added the code from where the gui redesign started. by the way i had to change this exact code numerous timessssss. This devlog includes the most time i spent vibe coding , and regretted………….. So i hope to add 2-3 more features like allowing admins to change the password(maybe) and I hope to ship this project by day after tommorow :)"}, {"post_id": 63630, "ts": "2026-09-07T15:37:46Z", "hours": 1.7175, "text": "DEVLOG#8 Today I fixed ALL of the mistakes like when u get the admin passowrd wrong whilst changing the status of a Issue report shitt was working great i hope to ship this before the 10th buutttttttttttttt….. Life isn’t so easy, I wanted to UPGRADE the GUI one last time to make it look like a decent application and I am still in the middle of that but i will definitely update u according to my progress. Here my inspiration ( not where i am rn ) I am aiming for smthing like this for my app"}, {"post_id": 60904, "ts": "2026-09-03T15:40:22Z", "hours": 1.0444, "text": "DEVLOG #8 So today I gave the same functions i gave to student view yesterday to admin view but better I added a priority calculator, a show more show less thing from yesterday and the filter thingy"}, {"post_id": 60289, "ts": "2026-09-02T15:47:16Z", "hours": 1.0939, "text": "DEVOG#7 This took way more time than it should have, so when i ran the program today I realized that the filter function wasn’t working properly and to fix i ended up removing the show show less option which i got working after loads of struggles due to some of the STUPIDEST mistakes…"}, {"post_id": 59638, "ts": "2026-09-01T15:38:45Z", "hours": 2.1444, "text": "DEVLOG #6 SO today consisted of me correcting my stupid mistakes again…. But this time I actually fixed everything and I also added a show more, show less option/button because too much text was ending up pushing the upvote button off the screen, making it IMPOSSIBLE to upvote. I also add a feature that lets the users sort and classify the problems so its easier to manage rather than having like 20+ problems on your page and having to read through ALL of themm.. Along with that I even took the concept of taking urgency as input out of the equation as I didn’t want people to be writing “The urgency is 9999 bro trust me”; to deal with such larpers I added basic yet effective limiters…"}, {"post_id": 59536, "ts": "2026-09-01T12:40:57Z", "hours": 0.8722, "text": "DEVLOG#5 So I basically worked on adding a function to chage the status of a problem, something only admins can access. Liittle did I know I would mess up half of the code smhw, even Chatgpt wasn’t helping but after fixing some of the stupidest mistakes I got the code running, but yes there are still some problemss…"}, {"post_id": 57405, "ts": "2026-08-29T15:28:54Z", "hours": 1.0681, "text": "DEVLOG#4 so today included touching up and finessing because i forgot to add features, i also added a change password function messed around with customtkinter but failed miserably hope to do some absolute legendary progress tomorrow."}, {"post_id": 56566, "ts": "2026-08-28T11:29:59Z", "hours": 3.6278, "text": "DEVLOG#3 Absolutely Legendary progress, almost done with the final GUI looks awesome. I also worked on major backend code addes passwords and login statements for both students and admins and i also ensured that one person cannot upvote on an issue more than once. I also added guest mode. Tomorrow will include making loads of changes and making the GUI better!"}, {"post_id": 55581, "ts": "2026-08-27T15:05:38Z", "hours": 1.0158, "text": "DEVLOG#2 So today was a mess because I had to go around fighting teachers in my school just so I could have my OWN LAPTOP, a big pain in the *ss but all of that stuff aside. Today’s progress was decent i worked on the GUI alot messed around with Tkinter diferrent sizes and style and I also added a admin tab to the website which is still in progress because I ran into numerous errors and I am still pinpointing my mistakes. Along with the admin tab I added a login interface type of thig and that turned out to be a task because again MY FIRST TIME designing an OAUTH. Hope to improve the GUI a lotttttt!!!!!!! but i am satisfied with what i have right now. till we meet againnnnnn………."}, {"post_id": 55107, "ts": "2026-08-26T15:47:57Z", "hours": 1.0783, "text": "DEVLOG#1 First time working with JSON and Tkinter till now i have coded the frontend of the app to some extent and hope to start working on the backend soon. This was also my first time using JSON, I used it to make kind of like a database which store previous complains and uses this stored data to develop a combined report of similar issues. Lovely experience, but not going to lie Gemini helped me out a lot to spot my mistakes in like every 20-25 lines and it turned out to be somewhat a pain but I hope that JSON and Tkinter will help me developing future projects."}]...
|
Title: BLACKBOX (complain filing application) by @ Title: BLACKBOX (complain filing application) by @FabulousHippoOfOrangeLake | Stardance
Devlogs:
DEVLOG#1 First time working with JSON and Tkinter till now i have coded the frontend of the app to some extent and hope to start working on the backend soon. This was also my first time using JSON, I used it to make kind of like a database which store previous complains and uses this stored data to develop a combined report of similar issues. Lovely experience, but not going to lie Gemini helped me out a lot to spot my mistakes in like every 20-25 lines and it turned out to be somewhat a pain but I hope that JSON and Tkinter will help me developing future projects.
DEVLOG#2 So today was a mess because I had to go around fighting teachers in my school just so I could have my OWN LAPTOP, a big pain in the *ss but all of that stuff aside. Today’s progress was decent i worked on the GUI alot messed around with Tkinter diferrent sizes and style and I also added a admin tab to the website which is still in progress because I ran into numerous errors and I am still pinpointing my mistakes. Along with the admin tab I added a login interface type of thig and that turned out to be a task because again MY FIRST TIME designing an OAUTH. Hope to improve the GUI a lotttttt!!!!!!! but i am satisfied with what i have right now. till we meet againnnnnn……….
DEVLOG#3 Absolutely Legendary progress, almost done with the final GUI looks awesome. I also worked on major backend code addes passwords and login statements for both students and admins and i also ensured that one person cannot upvote on an issue more than once. I also added guest mode. Tomorrow will include making loads of changes and making the GUI better!
DEVLOG#4 so today included touching up and finessing because i forgot to add features, i also added a change password function messed around with customtkinter but failed miserably hope to do some absolute legendary progress tomorrow.
DEVLOG#5 So I basically worked on adding a function to chage the status of a problem, something only admins can access. Liittle did I know I would mess up half of the code smhw, even Chatgpt wasn’t helping but after fixing some of the stupidest mistakes I got the code running, but yes there are still some problemss…
DEVLOG #6 SO today consisted of me correcting my stupid mistakes again…. But this time I actually fixed everything and I also added a show more, show less option/button because too much text was ending up pushing the upvote button off the screen, making it IMPOSSIBLE to upvote. I also add a feature that lets the users sort and classify the problems so its easier to manage rather than having like 20+ problems on your page and having to read through ALL of themm.. Along with that I even took the concept of taking urgency as input out of the equation as I didn’t want people to be writing “The urgency is 9999 bro trust me”; to deal with such larpers I added basic yet effective limiters…
DEVOG#7 This took way more time than it should have, so when i ran the program today I realized that the filter function wasn’t working properly and to fix i ended up removing the show show less option which i got working after loads of struggles due to some of the STUPIDEST mistakes…
DEVLOG #8 So today I gave the same functions i gave to student view yesterday to admin view but better I added a priority calculator, a show more show less thing from yesterday and the filter thingy
DEVLOG#8 Today I fixed ALL of the mistakes like when u get the admin passowrd wrong whilst changing the status of a Issue report shitt was working great i hope to ship this before the 10th buutttttttttttttt….. Life isn’t so easy, I wanted to UPGRADE the GUI one last time to make it look like a decent application and I am still in the middle of that but i will definitely update u according to my progress. Here my inspiration ( not where i am rn ) I am aiming for smthing like this for my app
DEVLOG#9 So today I finished the new gui design it isn’t as good and as clean as my refernce but I am still happ with it i even added the code from where the gui redesign started. by the way i had to change this exact code numerous timessssss. This devlog includes the most time i spent vibe coding , and regretted………….. So i hope to add 2-3 more features like allowing admins to change the password(maybe) and I hope to ship this project by day after tommorow :)
DEVLOG #9 idk SO i added so may features and it was such a pain in the ass to retain feature when adding new ones i kept messing up here and there and even forgot to call the simplest of functions. But now i’m here and this is what I added: Different types of admin (headmaster, housemaster senior master etc.) feature to chose who u want to submit the report too feature to forward the issue (as an admin) - if the particular admin finds its not for him logging in if ur in guest mode and logging out if ur in student mode my reports and all reports button added a view issue button which lets u view the full issue instead of the dot expanding thing i had before lastly the stupidest but most needed asterisk while entering passwords.
Ships:
I made a python desktop app for student feedback, issue and complain management. The main idea was to provide students with one core place to report problems. Students use their roll number for logins, they can upvote issues to show its urgency, they can change their own password. There is also a separate admin dashboard with issues organised cleanly according to priority. I am proud of using Custom Tkinter for the first time but not proud of having 1200 lines of code in one file! I hope u find this project worthy and fun to use!...
|
1793764548.9643962
|
1793850948.9643962
|
|
1850
|
ladybug dreams by @ladybug | Stardance
|
ladybug
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ladybug dreams by @ladybug | Stardance
|
1793764548.0866604
|
1794369348.0866604
|
|
57567
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764547.2278144
|
1794628547.2278144
|
|
57566
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764546.364831
|
1794628546.364831
|
|
39020
|
Underwater Website by @Marousoz | Stardance
|
Marousoz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Underwater Website by @Marousoz | Stardance
|
1793764545.4734771
|
1794369345.4734771
|
|
57559
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764544.6189191
|
1794628544.6189191
|
|
27423
|
Adobe Lightroom Clone by @catlover125r | Stardance
|
catlover125r
|
1
|
4.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-28T06:55:21Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Open-source, catalog-based, non-destructive RAW photo editor (Lightroom-class), GPLv3, 100% local AI. Engine in Rust, one wgpu shader codebase, ONNX Runtime for all ML. This repo contains the Phase-0 spike + a working Phase-1 (MVP) with a real desktop GUI — proven end-to-end on Apple Silicon (Metal + CoreML): crates/raw-decode — LibRaw → linear 16-bit RGB + metadata probe, via a stable C-ABI shim. crates/recipe — serde parametric edit-recipe (sparse, identity-default). crates/catalog — SQLite catalog: import folders of RAWs (with EXIF), read/write recipes, idempotent. crates/gpu — wgpu develop pipeline (WB, exposure, contrast, highlights/shadows/whites/blacks, vibrance/saturation, dehaze, 8-band HSL, post-crop vignette, grain), shared by the live preview and headless export. Preview == export. cargo run -p gpu –example modtest checks the modules. crates/app — egui desktop app: a Library grid (background-decoded thumbnails) and a Develop view with live sliders driving the GPU pipeline, plus the import / –recipe / –export / –selftest headless CLI. crates/ai-smoke — ONNX Runtime + CoreML EP smoke test for SAM2. catalog/schema.sql — full SQLite catalog schema (Task 3). docs/ — stack decisions, recipe format, develop pipeline, model packaging.", "repo": "https://github.com/catlover125r/AdobeMaybeLight", "demo": "https://github.com/catlover125r/AdobeMaybeLight/releases/tag/v0.1.0"}]...
|
[{"post_id": 17440, "ts": "202 [{"post_id": 17440, "ts": "2026-06-28T06:52:08Z", "hours": 3.8881, "text": "It’s looking good. I used Rust for the first time to make this project. As you can see below, the sliders work well!"}]...
|
Title: Adobe Lightroom Clone by @catlover125r | St Title: Adobe Lightroom Clone by @catlover125r | Stardance
Devlogs:
It’s looking good. I used Rust for the first time to make this project. As you can see below, the sliders work well!
Ships:
Open-source, catalog-based, non-destructive RAW photo editor (Lightroom-class), GPLv3, 100% local AI. Engine in Rust, one wgpu shader codebase, ONNX Runtime for all ML. This repo contains the Phase-0 spike + a working Phase-1 (MVP) with a real desktop GUI — proven end-to-end on Apple Silicon (Metal + CoreML): crates/raw-decode — LibRaw → linear 16-bit RGB + metadata probe, via a stable C-ABI shim. crates/recipe — serde parametric edit-recipe (sparse, identity-default). crates/catalog — SQLite catalog: import folders of RAWs (with EXIF), read/write recipes, idempotent. crates/gpu — wgpu develop pipeline (WB, exposure, contrast, highlights/shadows/whites/blacks, vibrance/saturation, dehaze, 8-band HSL, post-crop vignette, grain), shared by the live preview and headless export. Preview == export. cargo run -p gpu –example modtest checks the modules. crates/app — egui desktop app: a Library grid (background-decoded thumbnails) and a Develop view with live sliders driving the GPU pipeline, plus the import / –recipe / –export / –selftest headless CLI. crates/ai-smoke — ONNX Runtime + CoreML EP smoke test for SAM2. catalog/schema.sql — full SQLite catalog schema (Task 3). docs/ — stack decisions, recipe format, develop pipeline, model packaging....
|
1793764543.4365716
|
1793850943.4365716
|
|
13633
|
ConeOS by @Cone | Stardance
|
Cone
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ConeOS by @Cone | Stardance
|
1793764542.550113
|
1794369342.550113
|
|
57556
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764541.694814
|
1794628541.694814
|
|
57545
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764540.8257031
|
1794628540.8257031
|
|
57539
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764539.9469223
|
1794628539.9469223
|
|
3366
|
Starfish by @sai_was_taken | Stardance
|
sai_was_taken
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Starfish by @sai_was_taken | Stardance
|
1793764539.07391
|
1794369339.07391
|
|
57530
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764538.2212565
|
1794628538.2212565
|
|
26767
|
Angel's WebOS by @angelneupane | Stardance
|
angelneupane
|
1
|
4.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-03T13:04:09Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I present the AngelOS! I created a webOS with 4 app windows, which are: DateTime Window My LinkedIn A to-do list A coin flip app that uses the Math.random() function to pick heads or tails at random and tells the user if they win or lose. The greatest difficulty I faced was setting up hackatime on github codespaces. After I had that part down, everything was smooth. Figuring out how to implement the coin flip function was a challenge, too. Before deciding on the coin flip app, I tried creating a CPS counter app, but it was too difficult, so I dropped the idea.", "repo": "https://github.com/angelneupane/AngelOS", "demo": "https://angelneupane.github.io/AngelOS/"}]...
|
[{"post_id": 21461, "ts": "202 [{"post_id": 21461, "ts": "2026-07-03T12:46:54Z", "hours": 0.6733, "text": "Devlog [5] Created a coinflip app using the Math.random() function."}, {"post_id": 21400, "ts": "2026-07-03T10:07:39Z", "hours": 1.4547, "text": "Devlog [4] Added a button to close the windows and added icons to open specific windows and made a simple to-do list app that uses tag."}, {"post_id": 20769, "ts": "2026-07-02T13:46:16Z", "hours": 0.7914, "text": "Devlog [3] Changed the inline CSS that was common for all elements to Internal CSS, added the drag window feature, added headers to each window, made separate windows for date and time and LinkedIn, changed the background image, added multiple classes to classify div as draggable and windows."}, {"post_id": 20186, "ts": "2026-07-01T18:51:22Z", "hours": 0.4386, "text": "Devlog[2] Created a div for the heading, my LinkedIn profile and the date and time function and made it kinda fit the theme."}, {"post_id": 20161, "ts": "2026-07-01T18:20:39Z", "hours": 0.6114, "text": "Devlog[1] I added a background image to the body, added a heading and attached a link to github.com. Most of the time was spent trying to set up hackatime because I just couldn’t get it to work right."}]...
|
Title: Angel's WebOS by @angelneupane | Starda Title: Angel's WebOS by @angelneupane | Stardance
Devlogs:
Devlog[1] I added a background image to the body, added a heading and attached a link to github.com. Most of the time was spent trying to set up hackatime because I just couldn’t get it to work right.
Devlog[2] Created a div for the heading, my LinkedIn profile and the date and time function and made it kinda fit the theme.
Devlog [3] Changed the inline CSS that was common for all elements to Internal CSS, added the drag window feature, added headers to each window, made separate windows for date and time and LinkedIn, changed the background image, added multiple classes to classify div as draggable and windows.
Devlog [4] Added a button to close the windows and added icons to open specific windows and made a simple to-do list app that uses tag.
Devlog [5] Created a coinflip app using the Math.random() function.
Ships:
I present the AngelOS! I created a webOS with 4 app windows, which are: DateTime Window My LinkedIn A to-do list A coin flip app that uses the Math.random() function to pick heads or tails at random and tells the user if they win or lose. The greatest difficulty I faced was setting up hackatime on github codespaces. After I had that part down, everything was smooth. Figuring out how to implement the coin flip function was a challenge, too. Before deciding on the coin flip app, I tried creating a CPS counter app, but it was too difficult, so I dropped the idea....
|
1793764536.9569235
|
1793850936.9569235
|
|
57524
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764536.0792007
|
1794628536.0792007
|
|
29857
|
IndianOS by @sk_zaidji | Stardance
|
sk_zaidji
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-03T14:33:45Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I built IndianOS, a browser-based desktop operating system inspired by India using HTML, CSS, and JavaScript. It includes a desktop interface, Start Menu, draggable windows, Files, Notes, Calculator, a live IST clock, a boot screen, notification toasts, an About window, and support for maximizing windows by double-clicking the title bar. The most challenging part was implementing the draggable window system. I had to manage mouse events, calculate the correct window position while dragging, and handle the window stacking order (z-index) so the active window always appears on top. I also worked on making the maximize/restore behavior smooth and ensuring all the UI components worked together. I’m proud that I built a complete desktop-like experience from scratch without using any frameworks. The project has an original Indian-inspired theme, a clean interface, and several extra features beyond the basic tutorial, such as the boot screen, notification toasts, About window, and window maximize functionality. It gave me a much better understanding of JavaScript event handling and UI development.", "repo": "https://github.com/MdZaidji/my-first-webos", "demo": "https://mdzaidji.github.io/my-first-webos/"}]...
|
[{"post_id": 21492, "ts": "202 [{"post_id": 21492, "ts": "2026-07-03T13:57:55Z", "hours": 0.9119, "text": "🚀 Devlog #3 – Final Polish & Completion Today I completed IndianOS and focused on polishing the overall user experience.What I added🚀 Boot screen with a loading animation before the desktop appears.🔔 Notification toasts that display when applications are opened.🪟 Double-click on a window title bar to maximize and restore windows.ℹ️ An About IndianOS window with project information.🎨 Improved the desktop layout, taskbar, and window styling for a cleaner, more modern look.ChallengesThe biggest challenge was making the window system feel smooth and responsive. I refined the dragging logic, improved window layering with z-index, and made sure maximizing and restoring windows worked correctly without affecting other open applications.What I learnedManaging DOM events for draggable interfaces.Using JavaScript to control window states and interactions.Improving UI/UX with small visual details like animations and notifications.Organizing HTML, CSS, and JavaScript into a simple desktop-style application.Final Features🖥️ Desktop Interface📋 Start Menu🪟 Multiple Draggable Windows📁 Files App📝 Notes App🧮 Calculator🕒 Live IST Clock🚀 Boot Screen🔔 Notification Toasts🪟 Double-click to Maximize Windowsℹ️ About IndianOSBuilding IndianOS was a fun way to learn more about DOM manipulation, event handling, and designing a desktop-like interface entirely with HTML, CSS, and JavaScript. This project also gave me experience structuring a larger frontend project while keeping the interface simple and responsive."}, {"post_id": 21460, "ts": "2026-07-03T12:46:29Z", "hours": 1.0086, "text": "Devlog 2 – Window Manager Today I implemented the core of IndianOS: draggable windows. I built separate windows for Files, Notes, and Calculator, added close buttons, and made windows come to the front when clicked. The biggest challenge was handling dragging smoothly without affecting other windows, but after debugging the mouse events I got it working."}, {"post_id": 21427, "ts": "2026-07-03T11:35:16Z", "hours": 1.1467, "text": "Devlog 1 – Starting IndianOS 🇮🇳 Today I started building IndianOS, a browser-based desktop operating system inspired by India. Instead of copying the tutorial exactly, I wanted to create my own look and feel.So far I have:Created the project structure.Built the desktop layout.Added desktop icons.Added a taskbar with a live IST clock.Chosen an India-inspired theme for the UI.Next, I’ll work on draggable windows and build the core applications like Files, Notes, and Calculator."}]...
|
Title: IndianOS by @sk_zaidji | Stardance
Devlogs Title: IndianOS by @sk_zaidji | Stardance
Devlogs:
Devlog 1 – Starting IndianOS 🇮🇳 Today I started building IndianOS, a browser-based desktop operating system inspired by India. Instead of copying the tutorial exactly, I wanted to create my own look and feel.So far I have:Created the project structure.Built the desktop layout.Added desktop icons.Added a taskbar with a live IST clock.Chosen an India-inspired theme for the UI.Next, I’ll work on draggable windows and build the core applications like Files, Notes, and Calculator.
Devlog 2 – Window Manager Today I implemented the core of IndianOS: draggable windows. I built separate windows for Files, Notes, and Calculator, added close buttons, and made windows come to the front when clicked. The biggest challenge was handling dragging smoothly without affecting other windows, but after debugging the mouse events I got it working.
🚀 Devlog #3 – Final Polish & Completion Today I completed IndianOS and focused on polishing the overall user experience.What I added🚀 Boot screen with a loading animation before the desktop appears.🔔 Notification toasts that display when applications are opened.🪟 Double-click on a window title bar to maximize and restore windows.ℹ️ An About IndianOS window with project information.🎨 Improved the desktop layout, taskbar, and window styling for a cleaner, more modern look.ChallengesThe biggest challenge was making the window system feel smooth and responsive. I refined the dragging logic, improved window layering with z-index, and made sure maximizing and restoring windows worked correctly without affecting other open applications.What I learnedManaging DOM events for draggable interfaces.Using JavaScript to control window states and interactions.Improving UI/UX with small visual details like animations and notifications.Organizing HTML, CSS, and JavaScript into a simple desktop-style application.Final Features🖥️ Desktop Interface📋 Start Menu🪟 Multiple Draggable Windows📁 Files App📝 Notes App🧮 Calculator🕒 Live IST Clock🚀 Boot Screen🔔 Notification Toasts🪟 Double-click to Maximize Windowsℹ️ About IndianOSBuilding IndianOS was a fun way to learn more about DOM manipulation, event handling, and designing a desktop-like interface entirely with HTML, CSS, and JavaScript. This project also gave me experience structuring a larger frontend project while keeping the interface simple and responsive.
Ships:
I built IndianOS, a browser-based desktop operating system inspired by India using HTML, CSS, and JavaScript. It includes a desktop interface, Start Menu, draggable windows, Files, Notes, Calculator, a live IST clock, a boot screen, notification toasts, an About window, and support for maximizing windows by double-clicking the title bar. The most challenging part was implementing the draggable window system. I had to manage mouse events, calculate the correct window position while dragging, and handle the window stacking order (z-index) so the active window always appears on top. I also worked on making the maximize/restore behavior smooth and ensuring all the UI components worked together. I’m proud that I built a complete desktop-like experience from scratch without using any frameworks. The project has an original Indian-inspired theme, a clean interface, and several extra features beyond the basic tutorial, such as the boot screen, notification toasts, About window, and window maximize functionality. It gave me a much better understanding of JavaScript event handling and UI development....
|
1793764534.9047296
|
1793850934.9047296
|
|
57523
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764534.0290895
|
1794628534.0290895
|
|
57477
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764530.6339653
|
1794628530.6339653
|
|
38869
|
Han-Yang's page by @Han-Yang | Stardance
|
Han-Yang
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-24T17:30:22Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a simple 3 page website showing my hobbies, interests, and contacts.", "repo": "https://github.com/hydraprimus/My-personal-Site", "demo": "https://hydraprimus.github.io/My-personal-Site/"}]...
|
[{"post_id": 34140, "ts": "202 [{"post_id": 34140, "ts": "2026-07-24T17:19:59Z", "hours": 1.1225, "text": "I added a hobbies and contact section to my page. I removed the interests, cus that’s kind of the same thing as hobbies. Also all the navbar buttons work now and also change color when hovering!"}, {"post_id": 33735, "ts": "2026-07-23T21:46:30Z", "hours": 0.765, "text": "just finished making and styling the home page for my website."}]...
|
Title: Han-Yang's page by @Han-Yang | Stardanc Title: Han-Yang's page by @Han-Yang | Stardance
Devlogs:
just finished making and styling the home page for my website.
I added a hobbies and contact section to my page. I removed the interests, cus that’s kind of the same thing as hobbies. Also all the navbar buttons work now and also change color when hovering!
Ships:
I made a simple 3 page website showing my hobbies, interests, and contacts....
|
1793764529.5044544
|
1793850929.5044544
|
|
57476
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764528.6372237
|
1794628528.6372237
|
|
48104
|
KC16 by @Kxrtik1315 | Stardance
|
Kxrtik1315
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-16T11:18:33Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "i built KC16, a fully custom Slack bot powered by Node.js and @slack /bolt that literally runs 24/7 on a linux Hack Club Nest container. what was challenging? honestly the slack api config was an absolute fkng nightmare to navigate, and dealing with systemd service network timeouts almost took me out, but we survived it fr. i’m proud asf that it’s now completely bulletproof and lives on a server so it responds even when my laptop is shut. you can test it rn by dropping /kc16-ping in the chat to check latency, or hit it with /kc16-catfact, /kc16-joke, or /kc16-8ball to see it in action. zero slacking, just pure peak engineering.", "repo": "https://github.com/Kxrtik13-A19/KC16", "demo": "https://hackclub.enterprise.slack.com/archives/C0BQCTH9RL3"}]...
|
[{"post_id": 48063, "ts": "202 [{"post_id": 48063, "ts": "2026-08-16T10:50:14Z", "hours": 0.2825, "text": "the absolute worst part of dev is always the config but we survived it fr. spent way too much time in the slack api dashboard registering these slash commands one by one. but tbh looking at this list of all my bot’s commands mapped out with their descriptions is satisfying asf. got ping, help, catfact, joke, cybernetics, soccer, 8ball, dog, and roll fully registered so slack actually knows wtf to do when i type them. backend admin work is finally done, holy cramp. everything is completely locked in and ready for production."}, {"post_id": 48026, "ts": "2026-08-16T09:53:05Z", "hours": 0.4292, "text": "bro writing out all this logic was a grind but finally all commands and coding is done 🗣️🔥 ten full slash commands slammed into index.js and the bolt app is officially ready for action. setting up the axios fetches for the random dog api and doing the javascript math for the dice rolls took a hot sec but the code is looking super clean. vs code terminal finally spitting out ‘kc16 bolt app is running and ready for action!’ is a massive w for today. stardance hours are pumped up and my fingers are dead fr. time to touch some grass."}]...
|
Title: KC16 by @Kxrtik1315 | Stardance
Devlogs:
b Title: KC16 by @Kxrtik1315 | Stardance
Devlogs:
bro writing out all this logic was a grind but finally all commands and coding is done 🗣️🔥 ten full slash commands slammed into index.js and the bolt app is officially ready for action. setting up the axios fetches for the random dog api and doing the javascript math for the dice rolls took a hot sec but the code is looking super clean. vs code terminal finally spitting out ‘kc16 bolt app is running and ready for action!’ is a massive w for today. stardance hours are pumped up and my fingers are dead fr. time to touch some grass.
the absolute worst part of dev is always the config but we survived it fr. spent way too much time in the slack api dashboard registering these slash commands one by one. but tbh looking at this list of all my bot’s commands mapped out with their descriptions is satisfying asf. got ping, help, catfact, joke, cybernetics, soccer, 8ball, dog, and roll fully registered so slack actually knows wtf to do when i type them. backend admin work is finally done, holy cramp. everything is completely locked in and ready for production.
Ships:
i built KC16, a fully custom Slack bot powered by Node.js and @slack /bolt that literally runs 24/7 on a linux Hack Club Nest container. what was challenging? honestly the slack api config was an absolute fkng nightmare to navigate, and dealing with systemd service network timeouts almost took me out, but we survived it fr. i’m proud asf that it’s now completely bulletproof and lives on a server so it responds even when my laptop is shut. you can test it rn by dropping /kc16-ping in the chat to check latency, or hit it with /kc16-catfact, /kc16-joke, or /kc16-8ball to see it in action. zero slacking, just pure peak engineering....
|
1793764527.5030677
|
1793850927.5030677
|
|
57460
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764526.6277478
|
1794628526.6277478
|
|
57456
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793764525.753026
|
1794628525.753026
|