|
2636
|
My awesome macropad! by @NerdyEar | Stardance
|
NerdyEar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @NerdyEar | Stardan Title: My awesome macropad! by @NerdyEar | Stardance...
|
1792630253.983133
|
1793235053.983133
|
|
2635
|
vision controlled robotic hand by @donovanbruton | vision controlled robotic hand by @donovanbruton | Stardance...
|
donovanbruton
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: vision controlled robotic hand by @donovanb Title: vision controlled robotic hand by @donovanbruton | Stardance...
|
1792781498.037322
|
1793386298.037322
|
|
2634
|
PodPad by @DanngDev | Stardance
|
DanngDev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: PodPad by @DanngDev | Stardance
|
1792785285.09316
|
1793390085.09316
|
|
2633
|
Untitled by @AxelM21 | Stardance
|
AxelM21
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @AxelM21 | Stardance
|
1792749060.907187
|
1793353860.907187
|
|
2632
|
. by @Musa | Stardance
|
Musa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: . by @Musa | Stardance
|
1792770862.6302588
|
1793375662.6302588
|
|
2631
|
Untitled project by @joshualom8 | Stardance
|
joshualom8
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @joshualom8 | Stardance
|
1792947194.5184593
|
1793811194.5184593
|
|
2630
|
My first slack bot! by @pqcat | Stardance
|
pqcat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @pqcat | Stardance
|
1792623168.9838822
|
1793227968.9838822
|
|
2629
|
My awesome macropad! by @issabella_b097 | Stardanc My awesome macropad! by @issabella_b097 | Stardance...
|
issabella_b097
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @issabella_b097 | S Title: My awesome macropad! by @issabella_b097 | Stardance...
|
1792799384.9012284
|
1793404184.9012284
|
|
2628
|
My awesome macropad! by @pqcat | Stardance
|
pqcat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @pqcat | Stardance
|
1793217307.0281262
|
1793822107.0281262
|
|
2627
|
Zazzpad! by @zazzie | Stardance
|
zazzie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Zazzpad! by @zazzie | Stardance
|
1793181016.2813082
|
1793785816.2813082
|
|
2626
|
My awesome macropad! by @TalibN_myNameNoTerrorist My awesome macropad! by @TalibN_myNameNoTerrorist | Stardance...
|
TalibN_myNameNoTerrorist
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @TalibN_myNameNoTer Title: My awesome macropad! by @TalibN_myNameNoTerrorist | Stardance...
|
1793228187.7354488
|
1793832987.7354488
|
|
2625
|
CEDES-16 by @endercass | Stardance
|
endercass
|
0
|
12.25
|
0
|
[]
|
[{"post_id": 3977, "ts": "2026 [{"post_id": 3977, "ts": "2026-06-07T03:37:19Z", "hours": 4.7703, "text": "Added some more rendering stuff and drew a little brick tile. I added methods like BLIT{,K,S} and some memory operations like MEMCPY"}, {"post_id": 1109, "ts": "2026-06-02T22:50:09Z", "hours": 1.9358, "text": "I made an on screen controller for my fantasy console! SDL is not all that hard, but then again this is quite a simple UI. In the future I will probably use textures and proper layouting techniques. For now, this will do though! :3"}, {"post_id": 648, "ts": "2026-06-02T05:04:03Z", "hours": 2.5833, "text": "I started work on the input system! I jumped through a ton of hoops along the way, and experimented with different input pulling methods, but landed on polling once per frame. The same input can be pushed to the stack several times during the frame. I made a little paint game to test it out! it works pretty well, and works on both keyboard and a game controller!"}, {"post_id": 512, "ts": "2026-06-02T00:05:51Z", "hours": 2.9642, "text": "I made langton’s ant in my fantasy console! Langton’s ant isn’t that hard to write, of course, but it did point me to several issues in my stack handling! This fantasy console is implemented in C and is built with strange bugs in mind. The pitfalls caused by the arguably cursed ISA actually help to discourage me, at a personal level, from using LLMs in my code."}]...
|
Title: CEDES-16 by @endercass | Stardance
Devlogs Title: CEDES-16 by @endercass | Stardance
Devlogs:
I made langton’s ant in my fantasy console! Langton’s ant isn’t that hard to write, of course, but it did point me to several issues in my stack handling! This fantasy console is implemented in C and is built with strange bugs in mind. The pitfalls caused by the arguably cursed ISA actually help to discourage me, at a personal level, from using LLMs in my code.
I started work on the input system! I jumped through a ton of hoops along the way, and experimented with different input pulling methods, but landed on polling once per frame. The same input can be pushed to the stack several times during the frame. I made a little paint game to test it out! it works pretty well, and works on both keyboard and a game controller!
I made an on screen controller for my fantasy console! SDL is not all that hard, but then again this is quite a simple UI. In the future I will probably use textures and proper layouting techniques. For now, this will do though! :3
Added some more rendering stuff and drew a little brick tile. I added methods like BLIT{,K,S} and some memory operations like MEMCPY...
|
1792655322.419193
|
1793260122.419193
|
|
2624
|
Custom keyboard by @danielhryn | Stardance
|
danielhryn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Custom keyboard by @danielhryn | Stardance
|
1792734422.564275
|
1793339222.564275
|
|
2623
|
My awesome macropad! by @yeshwanth_purusothaman | My awesome macropad! by @yeshwanth_purusothaman | Stardance...
|
yeshwanth_purusothaman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @yeshwanth_purusoth Title: My awesome macropad! by @yeshwanth_purusothaman | Stardance...
|
1793191907.4652615
|
1793796707.4652615
|
|
2622
|
My awesome macropad! by @Emmanuel | Stardance
|
Emmanuel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Emmanuel | Stardan Title: My awesome macropad! by @Emmanuel | Stardance...
|
1792759976.3201447
|
1793364776.3201447
|
|
2621
|
My awesome macropad! by @requmarin | Stardance
|
requmarin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @requmarin | Starda Title: My awesome macropad! by @requmarin | Stardance...
|
1792795737.7978776
|
1793400537.7978776
|
|
2620
|
Fortune Fetcher by @kavya | Stardance
|
kavya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fortune Fetcher by @kavya | Stardance
|
1792734568.5744028
|
1793339368.5744028
|
|
2619
|
My awesome macropad! by @joschu13 | Stardance
|
joschu13
|
0
|
0.29
|
0
|
[]
|
[{"post_id": 677, "ts": "2026- [{"post_id": 677, "ts": "2026-06-02T07:19:32Z", "hours": 0.2856, "text": "I designed the Switchs in a Keyboard Matrix (4rowsx3collums) and connected them to the XIAO ( Took me about an Hour)"}]...
|
Title: My awesome macropad! by @joschu13 | Stardan Title: My awesome macropad! by @joschu13 | Stardance
Devlogs:
I designed the Switchs in a Keyboard Matrix (4rowsx3collums) and connected them to the XIAO ( Took me about an Hour)...
|
1792630471.8206336
|
1793235271.8206336
|
|
2618
|
test by @DoubleAM | Stardance
|
DoubleAM
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: test by @DoubleAM | Stardance
|
1793303598.699607
|
1793908398.699607
|
|
2617
|
Mossy by @dayfit | Stardance
|
dayfit
|
0
|
112.48
|
0
|
[]
|
[{"post_id": 83073, "ts": "202 [{"post_id": 83073, "ts": "2026-10-26T20:03:37Z", "hours": 2.2531, "text": "Devlog 26 Now extension uses tailwind instead of normal CSS. I guess right now I’ll polish this extension, add few features and ship project in max 2 days (that’s the plan) I’m really busy and working on Mossy is getting pretty hard. Cross your fingers"}, {"post_id": 82316, "ts": "2026-10-24T15:23:15Z", "hours": 9.6608, "text": "Devlog 25 I need new extenstion (old one is really crappy), and there are only 7 days to finish it (not doable right)? So I’ve used AI to generate base code for extension, now I’ll review this whole thing (I’ve partly already did, it was a hassle :d ). It’s much easier to work on it tho, we are using WXT, webext libs and code is really clean (working without them was bad decision, stack is one of the reasons I’m not trying to refactor old extension) Here is list of extension features (it’s intentionally short): Capturing passwords Coping username / password for each entry Filling passwords Logging in (not registering tho) Generating passwords (I’ll work on it soon!) I wanna put my extension on chrome webstore, It will take like 2 days to be accepted probably (that what it took when I tried to do that for flavortown (and it was accepted too late :c) See you around"}, {"post_id": 81070, "ts": "2026-10-19T19:09:33Z", "hours": 1.1372, "text": "Devlog 24 After reading and analizing this flow today, I’ve realized that it’s better to keep each vault with it’s own passkey (one leak won’t expose your all keys). Also right now if you have already registered passkey for that vault you can choose to use exising passkey (so it’ll look it up on your device), or create new one (it might overwrite your old one (for same vault)). After reviewing this PR by myself and finding nothing that would make this insecure, I’ve used GPT Astra 6 as well to review it, so now I’m pretty sure that this branch is ready to go on main. See ya!"}, {"post_id": 80793, "ts": "2026-10-18T20:06:37Z", "hours": 4.1375, "text": "Devlog 23 I added one really important thing. Before, Mossy used a 4-digit PIN to unlock the vault (it was used as a wrapping key (after going through HKDF and Argon2)). It was 10,000 combinations. Argon2 made it take longer, but after some time (a few hours), it could be cracked (if someone had your encrypted encryption key (sounds funny :d)). After this change: We use PRF from WebAuthn (really secure stuff) that uses Touch ID, Windows Hello, or Yubico Security Keys (and others) to give deterministic random bytes. Think of it like a random function that remembers what it returned for which argument. Assuming that an attacker would try to brute-force this encryption key, even with 10^18 tries per second, it’d take 1.8 x 10^51 years to crack it (kinda looooong time). Oh, and for those who can’t or don’t wanna use PRF, I’ve added regular passwords. They’re not as good as PRF, but it still takes a really long time to crack those. Those changes are still in an open PR, but it’s 10 PM, and I need to take a closer look at it tomorrow (already did a code review myself, but I’m kinda sleepy, and I’d like to keep y’all secure <3). See ya!"}, {"post_id": 80415, "ts": "2026-10-17T15:50:11Z", "hours": 7.7453, "text": "Devlog 22 Frontend: Added light, dark, and auto themes support (with settings tab!) Settings tab with themes options and links to request new features Added dashboard onboarding to help users setup their vault and add their first password Reworked key synchronization (now users will provide 6-character code instead of 6-digits code (Also it lacks of ambiguous characters like “l” and “I”) Backend: Complete rework of key-sync microservice (HTTP + SSE instead of WebSockets) (so user can access synchronized passwords up to 5 minutes after they are sent) Improved scallability by completely rethinking key-sync flow (that was kinda tricky)"}, {"post_id": 79105, "ts": "2026-10-12T18:01:50Z", "hours": 10.0319, "text": "Devlog 21 Changelogs Frontend: Standarized colors, boders, shadows, and button styles using globals.css system Updated typography: Syne for body text and Geologica for headings Centered headers navigation links Redesigned home page hero Fixed the footer so it stays at the bottom of the page Added leaf decorations on home page Based on feedback (from flavortown) I’ve decided to add some links to docs and instructions on how to set something up. Backend: Added SSE endpoint for live device enrollment updates I am working on delivering some more things before end of stardance. Stay tuned!"}, {"post_id": 70708, "ts": "2026-09-19T17:00:52Z", "hours": 5.3025, "text": "Devlog 20 Here is what happend after last devlog (lots of improvements :D) On frontend: Improved secured passwords chart, so it does only show integer values, centered chart’s line Added total count of passwords chart (as default mode) Added email verification interface Improved recent actions section Removed website icon from recent action card (API was broken, and it didn’t looked good anyway) On backend: Finished and integrated email verification system (verification link and code expires after 15 minutes) Added limits for incorrect codes, resend cooldowns, and hourly email deliveries Added rate limiting to public verification endpoint Emails are sent asynchronously through RabbitMQ That’s all for now. I’ll focus on design consistency & responsiveness for now."}, {"post_id": 65279, "ts": "2026-09-10T09:25:36Z", "hours": 7.6328, "text": "Devlog 19 It’s been a long time from last devlog. Here is changelog: On frontend: Vault loading, refreshing, selection, etc are now centralized in zustand store Removed redundant useVault hook Now user can select vault from dashboard view Added clearer selected-vault indicators and improved keyboard accessibility Made dashboard vault cards presentational and reusable On backend: Fixed critical bug in resource server logic (refresh token could be used as auth token (very bad :c)) Improved and refactored jwt validation & generation Added correct typ claim in JWT tokens Simplified refresh token claims (some were unused or not necessary) Updated Authentication.md documentation Expanded JWT generation, management, and decoder tests Work in progress: Currently I’m working on new feature, central microservice that will handle sending emails to users This is what I got so far: Batched async communication through RabbitMQ Integration with resend and some templates Retry queue with 30 secounds delay Service requeue mail only if something went wrong with sending (429 or 5XX response), if recipient doesn’t exist, there is no requeue Added tests for duplicates, pending commands, successful sends, permanent failures, and retryable failures. See ya!"}, {"post_id": 59672, "ts": "2026-09-01T16:25:07Z", "hours": 1.7078, "text": "Devlog 18 Mock API is finished, now I’m working on frontend design & consistency Changelog Finished Mock API Renamed RippleButton to Button as it’s generic right now Made Button component generic (support for icon, ghost buttons etc) Replaced all buttons with generic Button component Also I adjusted some colors so design is more consistent. See ya!"}, {"post_id": 59001, "ts": "2026-08-31T16:08:03Z", "hours": 7.1164, "text": "Devlog 17 Device manager is now up and running on production! in code review I noticed: some edge cases (mostly related with multi-threading) user could not change accounts (persisted device id was the issue) probably more, but stardance was down so I couldn’t write this devlog Now I’m working on creating Mock API so frontend development will no longer require running real backend. Stay tuned!"}, {"post_id": 46463, "ts": "2026-08-13T18:01:12Z", "hours": 1.7533, "text": "Devlog 16 Finally device manager is ready to go. Refactored frontend side logic for key-sync to work with new API Fixed bugs, improved error handling (so error message is not misleading) Removed .idea folder from repo Introduced mossy-reactor (way to test micro-services with their dependencies without deploying them to main before tests) Now it’s time to work on frontend features + design (typography, colors, globals <– boring stuff ://)"}, {"post_id": 45388, "ts": "2026-08-11T20:21:14Z", "hours": 3.4439, "text": "Devlog 15 I’ve integrated API with frontend, created new tab for managing devices. Fixed some bugs related to interation of cross-microservice communication (maybe I’ll write some integration tests? who knows) I’ve added detection of OS and device type via user agent (using Yauaa library). Now I’ll have to think about how to create good risk-engine when at same time not storing too much user informations (to keep it privacy-first) If you guys have some idea how to do that let me know! To merge this feature to develop branch I need to fix some really minor bugs. see ya!"}, {"post_id": 44650, "ts": "2026-08-10T15:43:24Z", "hours": 9.4775, "text": "Devlog 14 Soo… Recently I saw that there was no way to add new devices (** facepalm **). From last devlog I created nice enrollment system that will require already verified device to accept new one before trusting it. I’ve utilized JWT scopes for that, so client authenticated with enrollment token can only access specific endpoints. All of that probably sounds pretty easy but e g. I didn’t wanted to duplicate existing code, enrollment token is issued by same /login endpoint etc etc. basically it was quite a hustle. Hopefully, next devlog will be about how I integrated API with frontend (cross your fingers!) BTW: test count jumped from 31 to 72 from last devlog so you can see how big is the difference!"}, {"post_id": 34100, "ts": "2026-07-24T16:02:15Z", "hours": 5.6378, "text": "Devlog 13 Device manager is pretty much ready to go to production from API pov (there are some things that I still need to code tho), from last devlog I integrated it with Auth microservice, with each login / session refreshment it’s checked if given device is blocked, if so, Mossy will refuse to provide user new tokens. PS: look at those green tests (so cool)!"}, {"post_id": 29715, "ts": "2026-07-16T20:09:15Z", "hours": 4.5417, "text": "Hello there! From last devlog I’ve managed to add some features for this new Device Trust Microservice. Right now device can be blocked by another device (it will stop this device from access to account) Nonce challenge is working and has really good test coverage (this whole microservice does too) thanks to TDD I’ve finished implementing controllers & their tests It might look like TDD is slowing me down, but my code is getting really mature (each scenario is prepared). For whole process of developing this MS I didn’t opened insomnia even once - and that’s cool, because running tests without running whole MS (and it’s dependencies) is much faster. See ya!"}, {"post_id": 29114, "ts": "2026-07-15T19:34:36Z", "hours": 10.0033, "text": "Hello everyone, For last 10 hours I’ve made major progress on Mossy development. First of all my custom JWKS system got replaced by Spring Boot OAuth2 Resource Server Starter (looong name isn’t it?), it’ll make future maintance & coding much easier. In futher I’m going to migrate it to use Authorization Server Starter to achive full OAuth2 compatibility. Also I’ve been learning how TDD works, and for last 4 hours I’ve been using it during coding, it makes life so much easier! I’m currently working on new feature - Device Manager, it’s really huge feature (I need to refactor existing Device MS), but it’s really exciting, it’ll show you what devices are added to your account & analyze risk of each login (based on your common IP & MAC & OS & some more) it requires me to change old Device Microservice domain to just key-sync. Also I’ll create 2 new microservices - one called Device Trust (I’m working on it currently), it’ll tell my Authentication system to allow login or not (before cryptography was just for key-sync) by using challenge - client’ll receive randomly generated nonce and it’ll have to sign it with it’s key. Then if everything is alright it’ll ask Risk Engine if it should send user an alert or not (in future it might require MFA from client detected as higher risk) This is my biggest project ever Stay tuned!"}, {"post_id": 12018, "ts": "2026-06-19T16:35:36Z", "hours": 1.5044, "text": "Mossy now supports ssh public keys as well Refactored actions in frontend code to achive cleaner code Added validation of ssh keys"}, {"post_id": 11466, "ts": "2026-06-18T18:57:58Z", "hours": 2.0375, "text": "Mossy now supports SSH keys! Old Add Password form got removed, and replaced by new, cleaner one. Also I’m on my way to refactor code, and make lifting of Mossy’s extension UI. Support for public keys, and other SSH specific features will be introduce later, right now, only private key is supported"}, {"post_id": 10739, "ts": "2026-06-17T17:00:53Z", "hours": 2.2661, "text": "Notes system is ready and works like a charm, I had minor problem with JPA while implementing it ( Cascade.ALL ) fixed issue. Notes are encrypted with vault encryption key, so it’s suitable for sensitive data. Next up I’ll implement usage history!"}, {"post_id": 10186, "ts": "2026-06-16T20:00:41Z", "hours": 2.2619, "text": "Now, I’m working on implementing notes for passwords, backend is already ready, and frontend logic is half-way there, probably I’ll finish everything tommorow. Also I’ve made major refactor in vault request handlers logic by creating AbstractVaultRequestHandler to keep boilerplate-code in one place."}, {"post_id": 10021, "ts": "2026-06-16T15:59:05Z", "hours": 0.8125, "text": "Mossy’s search engine works like a charm!"}, {"post_id": 9322, "ts": "2026-06-15T17:15:42Z", "hours": 0.7514, "text": "Currently, I’m working on a search engine for Mossy using Fuse.js. There are still a few things to implement, such as the UI for query search, and some bugs in the tag search logic to fix."}, {"post_id": 8271, "ts": "2026-06-13T19:19:54Z", "hours": 2.9025, "text": "I’ve finaly finished system of managing tags! I really like how it turned out. Next up I’ll work on searching and filtering passwords!"}, {"post_id": 5828, "ts": "2026-06-09T19:26:39Z", "hours": 2.2906, "text": "Whole tag system is ready on backend, currently I’m working on integrating frontend with API in nice way. stay tuned !!!"}, {"post_id": 5145, "ts": "2026-06-08T20:42:33Z", "hours": 4.7406, "text": "I’ve created vault <—> backend communication for adding, assigning, and getting tags. Also adding logic is ready on frontend. Whole system ’ll be ready by tommorow 😱"}, {"post_id": 2856, "ts": "2026-06-05T18:23:25Z", "hours": 1.3331, "text": "Currently, I’m writing tag management system, that will include CRUD on tags, searching for passwords with tags. Adding tags already works! Also I’ve made really nice roadmap of Mossy Development!"}]...
|
Title: Mossy by @dayfit | Stardance
Devlogs:
Curr Title: Mossy by @dayfit | Stardance
Devlogs:
Currently, I’m writing tag management system, that will include CRUD on tags, searching for passwords with tags. Adding tags already works! Also I’ve made really nice roadmap of Mossy Development!
I’ve created vault <—> backend communication for adding, assigning, and getting tags. Also adding logic is ready on frontend. Whole system ’ll be ready by tommorow 😱
Whole tag system is ready on backend, currently I’m working on integrating frontend with API in nice way. stay tuned !!!
I’ve finaly finished system of managing tags! I really like how it turned out. Next up I’ll work on searching and filtering passwords!
Currently, I’m working on a search engine for Mossy using Fuse.js. There are still a few things to implement, such as the UI for query search, and some bugs in the tag search logic to fix.
Mossy’s search engine works like a charm!
Now, I’m working on implementing notes for passwords, backend is already ready, and frontend logic is half-way there, probably I’ll finish everything tommorow. Also I’ve made major refactor in vault request handlers logic by creating AbstractVaultRequestHandler to keep boilerplate-code in one place.
Notes system is ready and works like a charm, I had minor problem with JPA while implementing it ( Cascade.ALL ) fixed issue. Notes are encrypted with vault encryption key, so it’s suitable for sensitive data. Next up I’ll implement usage history!
Mossy now supports SSH keys! Old Add Password form got removed, and replaced by new, cleaner one. Also I’m on my way to refactor code, and make lifting of Mossy’s extension UI. Support for public keys, and other SSH specific features will be introduce later, right now, only private key is supported
Mossy now supports ssh public keys as well Refactored actions in frontend code to achive cleaner code Added validation of ssh keys
Hello everyone, For last 10 hours I’ve made major progress on Mossy development. First of all my custom JWKS system got replaced by Spring Boot OAuth2 Resource Server Starter (looong name isn’t it?), it’ll make future maintance & coding much easier. In futher I’m going to migrate it to use Authorization Server Starter to achive full OAuth2 compatibility. Also I’ve been learning how TDD works, and for last 4 hours I’ve been using it during coding, it makes life so much easier! I’m currently working on new feature - Device Manager, it’s really huge feature (I need to refactor existing Device MS), but it’s really exciting, it’ll show you what devices are added to your account & analyze risk of each login (based on your common IP & MAC & OS & some more) it requires me to change old Device Microservice domain to just key-sync. Also I’ll create 2 new microservices - one called Device Trust (I’m working on it currently), it’ll tell my Authentication system to allow login or not (before cryptography was just for key-sync) by using challenge - client’ll receive randomly generated nonce and it’ll have to sign it with it’s key. Then if everything is alright it’ll ask Risk Engine if it should send user an alert or not (in future it might require MFA from client detected as higher risk) This is my biggest project ever Stay tuned!
Hello there! From last devlog I’ve managed to add some features for this new Device Trust Microservice. Right now device can be blocked by another device (it will stop this device from access to account) Nonce challenge is working and has really good test coverage (this whole microservice does too) thanks to TDD I’ve finished implementing controllers & their tests It might look like TDD is slowing me down, but my code is getting really mature (each scenario is prepared). For whole process of developing this MS I didn’t opened insomnia even once - and that’s cool, because running tests without running whole MS (and it’s dependencies) is much faster. See ya!
Devlog 13 Device manager is pretty much ready to go to production from API pov (there are some things that I still need to code tho), from last devlog I integrated it with Auth microservice, with each login / session refreshment it’s checked if given device is blocked, if so, Mossy will refuse to provide user new tokens. PS: look at those green tests (so cool)!
Devlog 14 Soo… Recently I saw that there was no way to add new devices (** facepalm **). From last devlog I created nice enrollment system that will require already verified device to accept new one before trusting it. I’ve utilized JWT scopes for that, so client authenticated with enrollment token can only access specific endpoints. All of that probably sounds pretty easy but e g. I didn’t wanted to duplicate existing code, enrollment token is issued by same /login endpoint etc etc. basically it was quite a hustle. Hopefully, next devlog will be about how I integrated API with frontend (cross your fingers!) BTW: test count jumped from 31 to 72 from last devlog so you can see how big is the difference!
Devlog 15 I’ve integrated API with frontend, created new tab for managing devices. Fixed some bugs related to interation of cross-microservice communication (maybe I’ll write some integration tests? who knows) I’ve added detection of OS and device type via user agent (using Yauaa library). Now I’ll have to think about how to create good risk-engine when at same time not storing too much user informations (to keep it privacy-first) If you guys have some idea how to do that let me know! To merge this feature to develop branch I need to fix some really minor bugs. see ya!
Devlog 16 Finally device manager is ready to go. Refactored frontend side logic for key-sync to work with new API Fixed bugs, improved error handling (so error message is not misleading) Removed .idea folder from repo Introduced mossy-reactor (way to test micro-services with their dependencies without deploying them to main before tests) Now it’s time to work on frontend features + design (typography, colors, globals <– boring stuff ://)
Devlog 17 Device manager is now up and running on production! in code review I noticed: some edge cases (mostly related with multi-threading) user could not change accounts (persisted device id was the issue) probably more, but stardance was down so I couldn’t write this devlog Now I’m working on creating Mock API so frontend development will no longer require running real backend. Stay tuned!
Devlog 18 Mock API is finished, now I’m working on frontend design & consistency Changelog Finished Mock API Renamed RippleButton to Button as it’s generic right now Made Button component generic (support for icon, ghost buttons etc) Replaced all buttons with generic Button component Also I adjusted some colors so design is more consistent. See ya!
Devlog 19 It’s been a long time from last devlog. Here is changelog: On frontend: Vault loading, refreshing, selection, etc are now centralized in zustand store Removed redundant useVault hook Now user can select vault from dashboard view Added clearer selected-vault indicators and improved keyboard accessibility Made dashboard vault cards presentational and reusable On backend: Fixed critical bug in resource server logic (refresh token could be used as auth token (very bad :c)) Improved and refactored jwt validation & generation Added correct typ claim in JWT tokens Simplified refresh token claims (some were unused or not necessary) Updated Authentication.md documentation Expanded JWT generation, management, and decoder tests Work in progress: Currently I’m working on new feature, central microservice that will handle sending emails to users This is what I got so far: Batched async communication through RabbitMQ Integration with resend and some templates Retry queue with 30 secounds delay Service requeue mail only if something went wrong with sending (429 or 5XX response), if recipient doesn’t exist, there is no requeue Added tests for duplicates, pending commands, successful sends, permanent failures, and retryable failures. See ya!
Devlog 20 Here is what happend after last devlog (lots of improvements :D) On frontend: Improved secured passwords chart, so it does only show integer values, centered chart’s line Added total count of passwords chart (as default mode) Added email verification interface Improved recent actions section Removed website icon from recent action card (API was broken, and it didn’t looked good anyway) On backend: Finished and integrated email verification system (verification link and code expires after 15 minutes) Added limits for incorrect codes, resend cooldowns, and hourly email deliveries Added rate limiting to public verification endpoint Emails are sent asynchronously through RabbitMQ That’s all for now. I’ll focus on design consistency & responsiveness for now.
Devlog 21 Changelogs Frontend: Standarized colors, boders, shadows, and button styles using globals.css system Updated typography: Syne for body text and Geologica for headings Centered headers navigation links Redesigned home page hero Fixed the footer so it stays at the bottom of the page Added leaf decorations on home page Based on feedback (from flavortown) I’ve decided to add some links to docs and instructions on how to set something up. Backend: Added SSE endpoint for live device enrollment updates I am working on delivering some more things before end of stardance. Stay tuned!
Devlog 22 Frontend: Added light, dark, and auto themes support (with settings tab!) Settings tab with themes options and links to request new features Added dashboard onboarding to help users setup their vault and add their first password Reworked key synchronization (now users will provide 6-character code instead of 6-digits code (Also it lacks of ambiguous characters like “l” and “I”) Backend: Complete rework of key-sync microservice (HTTP + SSE instead of WebSockets) (so user can access synchronized passwords up to 5 minutes after they are sent) Improved scallability by completely rethinking key-sync flow (that was kinda tricky)
Devlog 23 I added one really important thing. Before, Mossy used a 4-digit PIN to unlock the vault (it was used as a wrapping key (after going through HKDF and Argon2)). It was 10,000 combinations. Argon2 made it take longer, but after some time (a few hours), it could be cracked (if someone had your encrypted encryption key (sounds funny :d)). After this change: We use PRF from WebAuthn (really secure stuff) that uses Touch ID, Windows Hello, or Yubico Security Keys (and others) to give deterministic random bytes. Think of it like a random function that remembers what it returned for which argument. Assuming that an attacker would try to brute-force this encryption key, even with 10^18 tries per second, it’d take 1.8 x 10^51 years to crack it (kinda looooong time). Oh, and for those who can’t or don’t wanna use PRF, I’ve added regular passwords. They’re not as good as PRF, but it still takes a really long time to crack those. Those changes are still in an open PR, but it’s 10 PM, and I need to take a closer look at it tomorrow (already did a code review myself, but I’m kinda sleepy, and I’d like to keep y’all secure <3). See ya!
Devlog 24 After reading and analizing this flow today, I’ve realized that it’s better to keep each vault with it’s own passkey (one leak won’t expose your all keys). Also right now if you have already registered passkey for that vault you can choose to use exising passkey (so it’ll look it up on your device), or create new one (it might overwrite your old one (for same vault)). After reviewing this PR by myself and finding nothing that would make this insecure, I’ve used GPT Astra 6 as well to review it, so now I’m pretty sure that this branch is ready to go on main. See ya!
Devlog 25 I need new extenstion (old one is really crappy), and there are only 7 days to finish it (not doable right)? So I’ve used AI to generate base code for extension, now I’ll review this whole thing (I’ve partly already did, it was a hassle :d ). It’s much easier to work on it tho, we are using WXT, webext libs and code is really clean (working without them was bad decision, stack is one of the reasons I’m not trying to refactor old extension) Here is list of extension features (it’s intentionally short): Capturing passwords Coping username / password for each entry Filling passwords Logging in (not registering tho) Generating passwords (I’ll work on it soon!) I wanna put my extension on chrome webstore, It will take like 2 days to be accepted probably (that what it took when I tried to do that for flavortown (and it was accepted too late :c) See you around
Devlog 26 Now extension uses tailwind instead of normal CSS. I guess right now I’ll polish this extension, add few features and ship project in max 2 days (that’s the plan) I’m really busy and working on Mossy is getting pretty hard. Cross your fingers...
|
1793148955.0027301
|
1793753755.0027301
|
|
2616
|
Robert Bot by @erikh | Stardance
|
erikh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Robert Bot by @erikh | Stardance
|
1792648409.672241
|
1793253209.672241
|
|
2615
|
My website by @youshitsune | Stardance
|
youshitsune
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-18T14:32:13Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I have implemented and redesigned my personal website. Add tags, improved the design. I’m really proud of implementing metadata for posts.", "repo": "https://github.com/youshitsune/youshitsune.github.io", "demo": "https://youshitsune.top/"}]...
|
[{"post_id": 11298, "ts": "202 [{"post_id": 11298, "ts": "2026-06-18T14:12:34Z", "hours": 0.7831, "text": "Finally finished the whole redesign, it looks much better, and tag system is working. Now I should start writing new blog posts."}, {"post_id": 10807, "ts": "2026-06-17T18:43:44Z", "hours": 1.505, "text": "Built a better parser for my posts. Next, I need to display tags and make posts searchable by those tags. There is a lot of improvement that could be done for the website design. So back at work."}]...
|
Title: My website by @youshitsune | Stardance
Dev Title: My website by @youshitsune | Stardance
Devlogs:
Built a better parser for my posts. Next, I need to display tags and make posts searchable by those tags. There is a lot of improvement that could be done for the website design. So back at work.
Finally finished the whole redesign, it looks much better, and tag system is working. Now I should start writing new blog posts.
Ships:
I have implemented and redesigned my personal website. Add tags, improved the design. I’m really proud of implementing metadata for posts....
|
1793292615.751736
|
1793379015.751736
|
|
2614
|
Untitled by @vasevang | Stardance
|
vasevang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @vasevang | Stardance
|
1793242098.7120585
|
1793846898.7120585
|
|
2613
|
My first slack bot! by @sonicx180 | Stardance
|
sonicx180
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @sonicx180 | Stardan Title: My first slack bot! by @sonicx180 | Stardance...
|
1792648064.3033319
|
1793252864.3033319
|
|
2612
|
Gam :D by @Chonu | Stardance
|
Chonu
|
0
|
6.02
|
0
|
[]
|
[{"post_id": 1222, "ts": "2026 [{"post_id": 1222, "ts": "2026-06-03T02:28:21Z", "hours": 3.5244, "text": "Today I removed the Arena for a simpler grey background. I implemented hit collision, and hit registration. Also a functional game over that closes your current instance. In terms of movement I made it so that when you let go of any movement keys you glide in the direction you were last moving for a short amount of time. I also added a precision movement mode where holding “shift” lets you move slower for more precise movements. I added the bullets to dodge, I added a new player sprite and an enemy dispensing the bullets."}, {"post_id": 502, "ts": "2026-06-01T23:44:25Z", "hours": 2.4967, "text": "Today, while figuring out godot I implemented a simple movement system with a simple sort of sprint function, I also added collision to the borders of the little arena, and a background sprite. It looks rough right now, but trust the process."}]...
|
Title: Gam :D by @Chonu | Stardance
Devlogs:
Toda Title: Gam :D by @Chonu | Stardance
Devlogs:
Today, while figuring out godot I implemented a simple movement system with a simple sort of sprint function, I also added collision to the borders of the little arena, and a background sprite. It looks rough right now, but trust the process.
Today I removed the Arena for a simpler grey background. I implemented hit collision, and hit registration. Also a functional game over that closes your current instance. In terms of movement I made it so that when you let go of any movement keys you glide in the direction you were last moving for a short amount of time. I also added a precision movement mode where holding “shift” lets you move slower for more precise movements. I added the bullets to dodge, I added a new player sprite and an enemy dispensing the bullets....
|
1792691547.2675705
|
1793296347.2675705
|
|
2611
|
My first slack bot! by @NerdyEar | Stardance
|
NerdyEar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @NerdyEar | Stardanc Title: My first slack bot! by @NerdyEar | Stardance...
|
1793274798.5127995
|
1793879598.5127995
|
|
2610
|
My awesome macropad! by @Radosgra | Stardance
|
Radosgra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Radosgra | Stardan Title: My awesome macropad! by @Radosgra | Stardance...
|
1793170580.2459462
|
1793775380.2459462
|
|
2609
|
first game by @zoie | Stardance
|
zoie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: first game by @zoie | Stardance
|
1792731310.1240535
|
1793336110.1240535
|
|
2608
|
Im Making a game in robloxes engine by @antlions47 Im Making a game in robloxes engine by @antlions4790 | Stardance...
|
antlions4790
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Im Making a game in robloxes engine by @ant Title: Im Making a game in robloxes engine by @antlions4790 | Stardance...
|
1792788874.2947826
|
1793393674.2947826
|
|
2607
|
My first slack bot! by @anshika | Stardance
|
anshika
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @anshika | Stardance
|
1792781478.342297
|
1793386278.342297
|
|
2606
|
Mars Maw by @zenzei | Stardance
|
zenzei
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mars Maw by @zenzei | Stardance
|
1792936061.4634101
|
1793800061.4634101
|
|
2605
|
Untitled project by @sharmnten | Stardance
|
sharmnten
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @sharmnten | Stardance
|
1793270990.2361188
|
1793875790.2361188
|
|
2604
|
Internet Relay Printer by @cyclic | Stardance
|
cyclic
|
0
|
0.34
|
0
|
[]
|
[{"post_id": 13902, "ts": "202 [{"post_id": 13902, "ts": "2026-06-22T19:53:37Z", "hours": 0.345, "text": "I finished the project ( :"}]...
|
Title: Internet Relay Printer by @cyclic | Stardan Title: Internet Relay Printer by @cyclic | Stardance
Devlogs:
I finished the project ( :...
|
1793228044.8927784
|
1793832844.8927784
|
|
2603
|
Untitled by @Gaxthecool | Stardance
|
Gaxthecool
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Gaxthecool | Stardance
|
1792644895.4973788
|
1793249695.4973788
|
|
2602
|
My first slack bot! by @nizar | Stardance
|
nizar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @nizar | Stardance
|
1792806790.4060178
|
1793411590.4060178
|
|
2601
|
alespad by @ales | Stardance
|
ales
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: alespad by @ales | Stardance
|
1792698752.7635207
|
1793303552.7635207
|
|
2600
|
StudentOS by @Gaxthecool | Stardance
|
Gaxthecool
|
1
|
19.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-02T15:38:29Z", "hours": 19.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made an OS that helps students organize their academic life. It has a calculator app, todo-list app, notes app, change background app, ask ai app, and quiz app. Below are some aspects of my project: The challenging part: The challenging part of my project was to troubleshoot bugs and errors that were within my script.js code. I did this through generative ai and using the inspect feature on chrome. Another challenging part was trying to come with a new feature that wasn’t listed in the guide. That feature was to make the welcome screen have a hide/show feature and to have a feature to change the background of the OS. The Feature that I am most proud of: The feature that I am most proud of is the Quiz App. It was the most complex app to design, considering that it had multiple draggable windows within the app itself. I also had to come up with fair and reasonable questions that the users can answer. Overall, I was proud with how this app turned out along with the overall project.", "repo": "https://github.com/gaxthecool/StudentOS", "demo": "https://gaxthecool.github.io/StudentOS/"}]...
|
[{"post_id": 37813, "ts": "202 [{"post_id": 37813, "ts": "2026-07-30T19:18:09Z", "hours": 0.8808, "text": "Day 12: I started working on the Settings App for this project. I also made an icon and movable div for the app. My goal to finish this project is by around the end of this upcoming Wednesday"}, {"post_id": 37175, "ts": "2026-07-29T17:59:00Z", "hours": 1.1114, "text": "Day 11: Succsessfully finished the quiz app with questions for five different subjects: math, science, ela, spanish, and ss. Also made an add button feature to the todo list app( based on feedback from friends/family) for improved UI."}, {"post_id": 36535, "ts": "2026-07-28T18:30:38Z", "hours": 3.4253, "text": "Day 10: Made progress on the Quiz App. The next step is to add questions for ela, science, ss, and spanish subjects and to add a settings app, a new feature that wasn’t mentioned in the guide."}, {"post_id": 35863, "ts": "2026-07-27T16:03:24Z", "hours": 0.8917, "text": "Day 9: Made buttons for each quiz set. Hope to make the actual quizzes soon and add a new feature. Almost about to be published."}, {"post_id": 35197, "ts": "2026-07-26T13:51:40Z", "hours": 1.2514, "text": "Day 8: Started the Quiz App on StudentOS. So far, I have made an icon and window for the app. I also cleaned up the code in my html, css, and javascript files so that users can read it."}, {"post_id": 15808, "ts": "2026-06-25T18:07:58Z", "hours": 1.1156, "text": "Day 7: Notes App added! You can now make savable notes and jot down any ideas you have."}, {"post_id": 15210, "ts": "2026-06-24T18:34:36Z", "hours": 1.5461, "text": "Day 6: Finish ToDo List App. Below is a demo showing the apps functionality. Hope to add more apps soon."}, {"post_id": 14577, "ts": "2026-06-23T19:00:21Z", "hours": 2.1153, "text": "Day 5: Finished Calculator App. This app is designed for students. It has basic operations(+, -, /, *) as well as complex operations, like square roots, exponents, and trig functions."}, {"post_id": 13849, "ts": "2026-06-22T18:06:53Z", "hours": 1.5811, "text": "Day 4: Started Working on the Calculator App. I am following a tutorial for this and have created the display window and calculator buttons(that have not been styled yet). Please leave any feedback you have."}, {"post_id": 11470, "ts": "2026-06-18T19:03:36Z", "hours": 2.1606, "text": "Day 3: I made a window for my todo list and calculator app. I have not added functionality yet, but am trying to get the app selection functionality working first."}, {"post_id": 10786, "ts": "2026-06-17T18:15:49Z", "hours": 2.1342, "text": "Day 2: I have made two unusable app icons and edited some styling to my website. I put all css code and js code in seperate files and things so far are turning out good."}, {"post_id": 10114, "ts": "2026-06-16T18:23:18Z", "hours": 0.8797, "text": "Day 1 of StudentOS. I am basing this off of the WebOS 1 mission. My OS is designed for College/High School Students. This OS changes the things in the Android OS and iOS by limiting distractions and defaulting settings to the needs of the student. Various other default apps will be added like a planner and a study bot to make resources. So far, I have made a Welcome Screen Div and OS wallpaper background."}]...
|
Title: StudentOS by @Gaxthecool | Stardance
Devlo Title: StudentOS by @Gaxthecool | Stardance
Devlogs:
Day 1 of StudentOS. I am basing this off of the WebOS 1 mission. My OS is designed for College/High School Students. This OS changes the things in the Android OS and iOS by limiting distractions and defaulting settings to the needs of the student. Various other default apps will be added like a planner and a study bot to make resources. So far, I have made a Welcome Screen Div and OS wallpaper background.
Day 2: I have made two unusable app icons and edited some styling to my website. I put all css code and js code in seperate files and things so far are turning out good.
Day 3: I made a window for my todo list and calculator app. I have not added functionality yet, but am trying to get the app selection functionality working first.
Day 4: Started Working on the Calculator App. I am following a tutorial for this and have created the display window and calculator buttons(that have not been styled yet). Please leave any feedback you have.
Day 5: Finished Calculator App. This app is designed for students. It has basic operations(+, -, /, *) as well as complex operations, like square roots, exponents, and trig functions.
Day 6: Finish ToDo List App. Below is a demo showing the apps functionality. Hope to add more apps soon.
Day 7: Notes App added! You can now make savable notes and jot down any ideas you have.
Day 8: Started the Quiz App on StudentOS. So far, I have made an icon and window for the app. I also cleaned up the code in my html, css, and javascript files so that users can read it.
Day 9: Made buttons for each quiz set. Hope to make the actual quizzes soon and add a new feature. Almost about to be published.
Day 10: Made progress on the Quiz App. The next step is to add questions for ela, science, ss, and spanish subjects and to add a settings app, a new feature that wasn’t mentioned in the guide.
Day 11: Succsessfully finished the quiz app with questions for five different subjects: math, science, ela, spanish, and ss. Also made an add button feature to the todo list app( based on feedback from friends/family) for improved UI.
Day 12: I started working on the Settings App for this project. I also made an icon and movable div for the app. My goal to finish this project is by around the end of this upcoming Wednesday
Ships:
I made an OS that helps students organize their academic life. It has a calculator app, todo-list app, notes app, change background app, ask ai app, and quiz app. Below are some aspects of my project: The challenging part: The challenging part of my project was to troubleshoot bugs and errors that were within my script.js code. I did this through generative ai and using the inspect feature on chrome. Another challenging part was trying to come with a new feature that wasn’t listed in the guide. That feature was to make the welcome screen have a hide/show feature and to have a feature to change the background of the OS. The Feature that I am most proud of: The feature that I am most proud of is the Quiz App. It was the most complex app to design, considering that it had multiple draggable windows within the app itself. I also had to come up with fair and reasonable questions that the users can answer. Overall, I was proud with how this app turned out along with the overall project....
|
1793141642.2905498
|
1793228042.2905498
|
|
2599
|
My awesome macropad! by @alfie_nicholls | Stardanc My awesome macropad! by @alfie_nicholls | Stardance...
|
alfie_nicholls
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @alfie_nicholls | S Title: My awesome macropad! by @alfie_nicholls | Stardance...
|
1792806807.7723377
|
1793411607.7723377
|
|
2598
|
RaspberryPi Handheld Console by @Joelbu | Stardanc RaspberryPi Handheld Console by @Joelbu | Stardance...
|
Joelbu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: RaspberryPi Handheld Console by @Joelbu | S Title: RaspberryPi Handheld Console by @Joelbu | Stardance...
|
1793191735.317153
|
1793796535.317153
|
|
2597
|
My first slack bot! by @GoshoBobcho | Stardance
|
GoshoBobcho
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-09T14:34:18Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made 24/7 Slack bot. It is very simple. It only has 4 commands and all of them don’t require an input. What I am proud of: Starting the challenge and making my first every online base project. Before i didn’t any javascript and Node.js and how Slack or Nest worked. What I am proud of: I was able to do host everything through the terminal or PowerShell. (Before i only knew how to upload filles to Github by draging them to the browser). It was very fun trying to find my mistakes(Half the times i wrote my repo name wrong). What commands the bot can do: +/pesho-help - displays all the commands +/pesho-ping - check bot latency +/pesho-joke - get a cat fact +/pesho-joke - get a random joke", "repo": "https://github.com/GeorgiPGeorgiev/Slack-bot-Pesho", "demo": "https://app.slack.com/client/E09V59WQY1E/C0B8YSMV9BN"}]...
|
[{"post_id": 4290, "ts": "2026 [{"post_id": 4290, "ts": "2026-06-07T15:28:41Z", "hours": 0.6389, "text": "Finally got the /ping command working. First time doing a project in hack club and it’s very fun"}]...
|
Title: My first slack bot! by @GoshoBobcho | Stard Title: My first slack bot! by @GoshoBobcho | Stardance
Devlogs:
Finally got the /ping command working. First time doing a project in hack club and it’s very fun
Ships:
I made 24/7 Slack bot. It is very simple. It only has 4 commands and all of them don’t require an input. What I am proud of: Starting the challenge and making my first every online base project. Before i didn’t any javascript and Node.js and how Slack or Nest worked. What I am proud of: I was able to do host everything through the terminal or PowerShell. (Before i only knew how to upload filles to Github by draging them to the browser). It was very fun trying to find my mistakes(Half the times i wrote my repo name wrong). What commands the bot can do: +/pesho-help - displays all the commands +/pesho-ping - check bot latency +/pesho-joke - get a cat fact +/pesho-joke - get a random joke...
|
1793293050.6585717
|
1793379450.6585717
|
|
2596
|
Random Number Guesser Game by @Dom | Stardance
|
Dom
|
0
|
2.1
|
0
|
[]
|
[{"post_id": 11064, "ts": "202 [{"post_id": 11064, "ts": "2026-06-18T03:07:59Z", "hours": 2.1025, "text": "Never coded before, so I am trying out python for the first time. Created a game based upon trying to guess a number. There are various difficulties that one can try out as well as a timer to see how fast you were able to guess. I am attempting to add a hint system but still need to work on that. I am currently 2 hours in and any input on how to learn coding languages would be greatly appreciated."}]...
|
Title: Random Number Guesser Game by @Dom | Starda Title: Random Number Guesser Game by @Dom | Stardance
Devlogs:
Never coded before, so I am trying out python for the first time. Created a game based upon trying to guess a number. There are various difficulties that one can try out as well as a timer to see how fast you were able to guess. I am attempting to add a hint system but still need to work on that. I am currently 2 hours in and any input on how to learn coding languages would be greatly appreciated....
|
1792727606.2684011
|
1793332406.2684011
|
|
2595
|
My first slack bot! by @burke1408 | Stardance
|
burke1408
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @burke1408 | Stardan Title: My first slack bot! by @burke1408 | Stardance...
|
1792669858.5681999
|
1793274658.5681999
|
|
2594
|
My awesome macropad! by @ariajohnson913 | Stardanc My awesome macropad! by @ariajohnson913 | Stardance...
|
ariajohnson913
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ariajohnson913 | S Title: My awesome macropad! by @ariajohnson913 | Stardance...
|
1793267345.519869
|
1793872145.519869
|
|
2593
|
Live Space Tracker (working title) by @dspace1015 Live Space Tracker (working title) by @dspace1015 | Stardance...
|
dspace1015
|
1
|
50.33
|
201
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-30T04:46:03Z", "hours": 48.0, "multiplier": 4.22, "payout": 201, "blessing": "neutral", "text": "I made a web app that lets you explore the positions of the planets in the solar system in real time. Change time with (< > /) keys to view the solar system in the past or future. Change your camera with the (c) key to view objects from their own orientation as they rotate around each other. Zoom out and see the positions of stars in our neighborhood. Plug in your home location on the map and you can view your own current night sky. Track the space station in low Earth orbit, and watch when it appears overhead.", "repo": "https://github.com/dspace1015/space", "demo": "https://dspace1015.github.io/space/"}]...
|
[{"post_id": 76034, "ts": "202 [{"post_id": 76034, "ts": "2026-10-02T04:28:06Z", "hours": 2.3267, "text": "Fixed some bugs that came up after launch Added text that when hovered shows controlls (most asked for feature) Fixed(mostly) the constant pop up bug, you may need to refresh the page once but it should be mostly gone by now"}, {"post_id": 75454, "ts": "2026-09-30T04:32:38Z", "hours": 3.7503, "text": "Final devlog for now, finished map view and added camera information I have added camera controls where you can change to view a planet from its own axis or rotation by pressing (c) to cycle through modes, and you can track objects by pressing (t). Also added more information on the ground view, light time calculation and finally the map view where once opened you can change your position by clicking on it."}, {"post_id": 74746, "ts": "2026-09-28T04:07:38Z", "hours": 8.5467, "text": "Finished all the continents, added saturns rings and and Mars and Jupiter’s moons. I have made decent progress, most of my time was spent debugging and optimizing since I’m only using the cpu to render everything. I also added more camera controls so that when you press (c) you can tilt the camera to match the planets axis tilt, or rotate along with it. The final parts I need to add at this point is a menu where you can choose your location and a information panel for the object that you select."}, {"post_id": 74325, "ts": "2026-09-27T05:34:21Z", "hours": 8.4517, "text": "Added continent outlines and object occlusion After spending way too much time trying to figure out webgl and three.js I decided that it was not worth the extra effort for slightly better graphics. Running out of time, I decided to stick to the system that I already had and decided to just draw the coastlines so you can make out the earths orientation better. Right now I have only added N&S America, Antarctica, and Australia. Ill add the rest later but for now this is what I got. Running out of time to ship this so I’m going to add a location selector and call this good."}, {"post_id": 40892, "ts": "2026-08-04T18:15:05Z", "hours": 2.5356, "text": "Added ground perspective and fixed stars Added a feature where you can select a position on the earth and view from there. You do have to manually add your latitude and longitude but eventually you will be able to select from a map or search for a specific city. (The demo shows London UK’s position so I don’t reveal my own) I also fixed the lag from the stars that was making the site slow, now it can display 3500 stars and all the other objects just fine."}, {"post_id": 11528, "ts": "2026-06-18T20:32:13Z", "hours": 5.48, "text": "Added grid based on your location, and stars from the Henry Draper (HD) catalogue. https://in-the-sky.org/data/catalogue.php?cat=HD&const=1&sort=1&view=1&page=1 Unfortunately now the framerate has dropped a lot, so I’ll need to figure out how to handle all the objects separately and only update the planets. Until then that’s enough programming for me today."}, {"post_id": 8955, "ts": "2026-06-14T22:02:27Z", "hours": 2.1864, "text": "Added TLE support https://en.wikipedia.org/wiki/Two-line_element_set (A common file format for earth orbit satellites). I’ve realized that I might have to switch to using a graphics api like webgl to improve the graphics from here, but for now I will focus on functionality. Better graphics should not matter at the moment from a ground level perspective."}, {"post_id": 7557, "ts": "2026-06-12T17:12:34Z", "hours": 6.3506, "text": "Finally added a way to read separate files into the web app. Objects are now stored in json files with all their orbital parameters and physical characteristics. Next steps for this project will be to start adding detail on the planets and reference frame transformations from your local position to space."}, {"post_id": 5140, "ts": "2026-06-08T20:33:11Z", "hours": 2.9439, "text": "You can now click on objects to select them. Orbits now also accurately precess. The moon’s orbit is now close enough to reality to predict solar eclipses, which is accurate enough for this project. All the inner rocky planet’s procession has been implemented as well according to NASA horizon’s approximation. They should now be reasonably accurate a few hundred yrs into the future. Next steps will be adding more objects like Jovian moons and spacecraft, as well as improving graphics."}, {"post_id": 2510, "ts": "2026-06-05T01:16:11Z", "hours": 3.0403, "text": "Added the main 8 planets in the solar system and a time control feature. You can now speed up, slow down, or reverse time to see the solar system on different dates, or reset to the current time. You can also scroll through the list of planets and watch from their perspective. As far as I can tell I succeeded in making the planets positions accurate (or at least enough for my project)."}, {"post_id": 1200, "ts": "2026-06-03T01:43:11Z", "hours": 0.8872, "text": "Added functionality for objects to orbit other objects. Progress is coming along nicely so far, all orbits of type e<1 are displayable and can be centered around any object. The next steps I plan on taking are plugging in the values for our actual solar system and switching camera controls to be centered on planets, then adding time control and other UI."}, {"post_id": 1103, "ts": "2026-06-02T22:39:41Z", "hours": 1.4622, "text": "I added mouse controls, Kepler’s 2nd law, and a grid that will come in handy for identifying places in the sky. Next I will continue to add features for adding celestial bodies and different spacecraft."}, {"post_id": 963, "ts": "2026-06-02T18:53:07Z", "hours": 0.8086, "text": "Added orbit calculations to the planetarium web app so I can start adding other objects in the display. A few more functions will need to be implemented but very soon I should be able to start plugging in data."}, {"post_id": 621, "ts": "2026-06-02T03:49:47Z", "hours": 1.2097, "text": "Starting the basic foundation of the web app, I plan on using only JavaScript and HTML5’s canvas to draw all the objects, using data from celestrack and NASA horizons to find all the data I need. Screenshot is just of a test of the basic 3d drawing function with axis visible. Because it is just night sky objects no fancy 3d engine will be needed."}]...
|
Title: Live Space Tracker (working title) by @dspa Title: Live Space Tracker (working title) by @dspace1015 | Stardance
Devlogs:
Starting the basic foundation of the web app, I plan on using only JavaScript and HTML5’s canvas to draw all the objects, using data from celestrack and NASA horizons to find all the data I need. Screenshot is just of a test of the basic 3d drawing function with axis visible. Because it is just night sky objects no fancy 3d engine will be needed.
Added orbit calculations to the planetarium web app so I can start adding other objects in the display. A few more functions will need to be implemented but very soon I should be able to start plugging in data.
I added mouse controls, Kepler’s 2nd law, and a grid that will come in handy for identifying places in the sky. Next I will continue to add features for adding celestial bodies and different spacecraft.
Added functionality for objects to orbit other objects. Progress is coming along nicely so far, all orbits of type e<1 are displayable and can be centered around any object. The next steps I plan on taking are plugging in the values for our actual solar system and switching camera controls to be centered on planets, then adding time control and other UI.
Added the main 8 planets in the solar system and a time control feature. You can now speed up, slow down, or reverse time to see the solar system on different dates, or reset to the current time. You can also scroll through the list of planets and watch from their perspective. As far as I can tell I succeeded in making the planets positions accurate (or at least enough for my project).
You can now click on objects to select them. Orbits now also accurately precess. The moon’s orbit is now close enough to reality to predict solar eclipses, which is accurate enough for this project. All the inner rocky planet’s procession has been implemented as well according to NASA horizon’s approximation. They should now be reasonably accurate a few hundred yrs into the future. Next steps will be adding more objects like Jovian moons and spacecraft, as well as improving graphics.
Finally added a way to read separate files into the web app. Objects are now stored in json files with all their orbital parameters and physical characteristics. Next steps for this project will be to start adding detail on the planets and reference frame transformations from your local position to space.
Added TLE support https://en.wikipedia.org/wiki/Two-line_element_set (A common file format for earth orbit satellites). I’ve realized that I might have to switch to using a graphics api like webgl to improve the graphics from here, but for now I will focus on functionality. Better graphics should not matter at the moment from a ground level perspective.
Added grid based on your location, and stars from the Henry Draper (HD) catalogue. https://in-the-sky.org/data/catalogue.php?cat=HD&const=1&sort=1&view=1&page=1 Unfortunately now the framerate has dropped a lot, so I’ll need to figure out how to handle all the objects separately and only update the planets. Until then that’s enough programming for me today.
Added ground perspective and fixed stars Added a feature where you can select a position on the earth and view from there. You do have to manually add your latitude and longitude but eventually you will be able to select from a map or search for a specific city. (The demo shows London UK’s position so I don’t reveal my own) I also fixed the lag from the stars that was making the site slow, now it can display 3500 stars and all the other objects just fine.
Added continent outlines and object occlusion After spending way too much time trying to figure out webgl and three.js I decided that it was not worth the extra effort for slightly better graphics. Running out of time, I decided to stick to the system that I already had and decided to just draw the coastlines so you can make out the earths orientation better. Right now I have only added N&S America, Antarctica, and Australia. Ill add the rest later but for now this is what I got. Running out of time to ship this so I’m going to add a location selector and call this good.
Finished all the continents, added saturns rings and and Mars and Jupiter’s moons. I have made decent progress, most of my time was spent debugging and optimizing since I’m only using the cpu to render everything. I also added more camera controls so that when you press (c) you can tilt the camera to match the planets axis tilt, or rotate along with it. The final parts I need to add at this point is a menu where you can choose your location and a information panel for the object that you select.
Final devlog for now, finished map view and added camera information I have added camera controls where you can change to view a planet from its own axis or rotation by pressing (c) to cycle through modes, and you can track objects by pressing (t). Also added more information on the ground view, light time calculation and finally the map view where once opened you can change your position by clicking on it.
Fixed some bugs that came up after launch Added text that when hovered shows controlls (most asked for feature) Fixed(mostly) the constant pop up bug, you may need to refresh the page once but it should be mostly gone by now
Ships:
I made a web app that lets you explore the positions of the planets in the solar system in real time. Change time with (< > /) keys to view the solar system in the past or future. Change your camera with the (c) key to view objects from their own orientation as they rotate around each other. Zoom out and see the positions of stars in our neighborhood. Plug in your home location on the map and you can view your own current night sky. Track the space station in low Earth orbit, and watch when it appears overhead....
|
1793152577.558544
|
1793238977.558544
|
|
2592
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792932748.9415536
|
1793796748.9415536
|
|
2591
|
Fire detection system by @ahamedayyash111 | Starda Fire detection system by @ahamedayyash111 | Stardance...
|
ahamedayyash111
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fire detection system by @ahamedayyash111 | Title: Fire detection system by @ahamedayyash111 | Stardance...
|
1792777656.6909988
|
1793382456.6909988
|
|
2590
|
My first slack bot! by @Temi | Stardance
|
Temi
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-06T12:22:04Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a rudimentary slack bot with a focus on productivity functions. The key functions: /tbot-ping — Checks bot responsiveness and displays latency. /tbot-catfact — Fetches and returns a random cat fact. /tbot-joke — Fetches and returns a random joke. /tbot-weather — Retrieves and displays current weather information. /tbot-todo add — Adds a task to the user’s todo list. /tbot-todo list — Lists all tasks in the user’s todo list. /tbot-todo remove — Removes a task by its number. /tbot-todo clear — Clears the user’s entire todo list. /tbot-help — Displays the list of available commands. This project was quite interesting as it was my first step into coding in java script. This led to my having to figure out a lot of syntax issues and how java script deals with things different to python. This was also my first time have to make sure something is able to run 24/7 through a server so I’m quite interested in getting to understand how servers work. How to test my bot: head to the Hackclub slack and try out any of the commands.", "repo": "https://github.com/StealthTD7/Tbot", "demo": "https://slack.hackclub.com/"}]...
|
[{"post_id": 1325, "ts": "2026 [{"post_id": 1325, "ts": "2026-06-03T08:13:27Z", "hours": 0.9464, "text": "Just got Weather implemented! Had some struggles figuring out how to use the api and managing my github but eventually got weather down. To do list next."}, {"post_id": 973, "ts": "2026-06-02T19:06:18Z", "hours": 0.4361, "text": "Started building a basic Slack bot aiming to implement daily weather reports into the bot while also adding productivity features like todo lists on to the chat bot. But just basic functionality for now."}]...
|
Title: My first slack bot! by @Temi | Stardance
D Title: My first slack bot! by @Temi | Stardance
Devlogs:
Started building a basic Slack bot aiming to implement daily weather reports into the bot while also adding productivity features like todo lists on to the chat bot. But just basic functionality for now.
Just got Weather implemented! Had some struggles figuring out how to use the api and managing my github but eventually got weather down. To do list next.
Ships:
I made a rudimentary slack bot with a focus on productivity functions. The key functions: /tbot-ping — Checks bot responsiveness and displays latency. /tbot-catfact — Fetches and returns a random cat fact. /tbot-joke — Fetches and returns a random joke. /tbot-weather — Retrieves and displays current weather information. /tbot-todo add — Adds a task to the user’s todo list. /tbot-todo list — Lists all tasks in the user’s todo list. /tbot-todo remove — Removes a task by its number. /tbot-todo clear — Clears the user’s entire todo list. /tbot-help — Displays the list of available commands. This project was quite interesting as it was my first step into coding in java script. This led to my having to figure out a lot of syntax issues and how java script deals with things different to python. This was also my first time have to make sure something is able to run 24/7 through a server so I’m quite interested in getting to understand how servers work. How to test my bot: head to the Hackclub slack and try out any of the commands....
|
1793263761.3810015
|
1793350161.3810015
|
|
2589
|
Slackbot by @mahmoud | Stardance
|
mahmoud
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Slackbot by @mahmoud | Stardance
|
1792705811.845564
|
1793310611.845564
|
|
2588
|
nydlsummer by @christian | Stardance
|
christian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: nydlsummer by @christian | Stardance
|
1792781620.838345
|
1793386420.838345
|
|
2587
|
My first slack bot! by @Gus_Kerman_4603 | Stardanc My first slack bot! by @Gus_Kerman_4603 | Stardance...
|
Gus_Kerman_4603
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Gus_Kerman_4603 | S Title: My first slack bot! by @Gus_Kerman_4603 | Stardance...
|
1793166712.8020263
|
1793771512.8020263
|