|
13101
|
Personal Website by @Wiktor | Stardance
|
Wiktor
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Personal Website by @Wiktor | Stardance
|
1793501661.3244562
|
1794106461.3244562
|
|
13102
|
Untitled project by @Virja | Stardance
|
Virja
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Virja | Stardance
|
1793267713.1323178
|
1793872513.1323178
|
|
13103
|
Sylveon WebOS by @ClairePoehner | Stardance
|
ClairePoehner
|
0
|
0.35
|
0
|
[]
|
[{"post_id": 15307, "ts": "202 [{"post_id": 15307, "ts": "2026-06-24T21:15:17Z", "hours": 0.3547, "text": "I built the body and added a picture of Sylveon and some facts about it. I also added a link to the Pokemon Pokedex for Sylveon. I am still unsure on how to preview the website, however."}]...
|
Title: Sylveon WebOS by @ClairePoehner | Stardance Title: Sylveon WebOS by @ClairePoehner | Stardance
Devlogs:
I built the body and added a picture of Sylveon and some facts about it. I also added a link to the Pokemon Pokedex for Sylveon. I am still unsure on how to preview the website, however....
|
1793029776.7285795
|
1793634576.7285795
|
|
13104
|
My very own WebOS by @stephaniecrush9 | Stardance
|
stephaniecrush9
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @stephaniecrush9 | Sta Title: My very own WebOS by @stephaniecrush9 | Stardance...
|
1793379323.4602966
|
1793984123.4602966
|
|
13105
|
My very own WebOS by @darkusernet2223 | Stardance
|
darkusernet2223
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @darkusernet2223 | Sta Title: My very own WebOS by @darkusernet2223 | Stardance...
|
1793407849.442338
|
1794012649.442338
|
|
13106
|
My very own WebOS by @fiona | Stardance
|
fiona
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @fiona | Stardance
|
1793238747.7185552
|
1793843547.7185552
|
|
13107
|
My first slack bot! by @phoenix886 | Stardance
|
phoenix886
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @phoenix886 | Starda Title: My first slack bot! by @phoenix886 | Stardance...
|
1793166588.8080213
|
1793771388.8080213
|
|
13108
|
My awesome macropad! by @Max_ | Stardance
|
Max_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Max_ | Stardance
|
1793173825.2178788
|
1793778625.2178788
|
|
13109
|
Untitled project by @mrjawadhere | Stardance
|
mrjawadhere
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @mrjawadhere | Stardanc Title: Untitled project by @mrjawadhere | Stardance...
|
1793145268.8930135
|
1793750068.8930135
|
|
13110
|
My very own WebOS by @florian | Stardance
|
florian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @florian | Stardance
|
1792929276.5639157
|
1793793276.5639157
|
|
13111
|
Perplexed AI by @Raobotnix | Stardance
|
Raobotnix
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Perplexed AI by @Raobotnix | Stardance
|
1793425684.2874844
|
1794030484.2874844
|
|
13112
|
My very own WebOS (I'll figure out a name even My very own WebOS (I'll figure out a name eventually) by @Amos | Stardance...
|
Amos
|
0
|
0.97
|
0
|
[]
|
[{"post_id": 14573, "ts": "202 [{"post_id": 14573, "ts": "2026-06-23T18:57:41Z", "hours": 0.5914, "text": "I added a top bar (the images and names are placeholders). BTW, I’m just following the template to see how it all fits together, and then once all the pieces are there, I’ll make it unique!"}, {"post_id": 12728, "ts": "2026-06-20T20:03:25Z", "hours": 0.3783, "text": "Just got started on the WebOS project; it’s… a work in progress. I’ll keep trying!"}]...
|
Title: My very own WebOS (I'll figure out a na Title: My very own WebOS (I'll figure out a name eventually) by @Amos | Stardance
Devlogs:
Just got started on the WebOS project; it’s… a work in progress. I’ll keep trying!
I added a top bar (the images and names are placeholders). BTW, I’m just following the template to see how it all fits together, and then once all the pieces are there, I’ll make it unique!...
|
1793364738.6891758
|
1793969538.6891758
|
|
13113
|
Mana Rush by @RohanIyer | Stardance
|
RohanIyer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mana Rush by @RohanIyer | Stardance
|
1793177456.8540437
|
1793782256.8540437
|
|
13114
|
Untitled by @meri | Stardance
|
meri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @meri | Stardance
|
1793357319.5621023
|
1793962119.5621023
|
|
13115
|
My awesome macropad! by @saachikasat | Stardance
|
saachikasat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @saachikasat | Star Title: My awesome macropad! by @saachikasat | Stardance...
|
1792799683.6356287
|
1793404483.6356287
|
|
13116
|
My very own WebOS by @reddyvedaant | Stardance
|
reddyvedaant
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @reddyvedaant | Starda Title: My very own WebOS by @reddyvedaant | Stardance...
|
1793368455.3504124
|
1793973255.3504124
|
|
13117
|
My very own WebOS by @Max_ | Stardance
|
Max_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Max_ | Stardance
|
1793163219.1374943
|
1793768019.1374943
|
|
13118
|
My awesome macropad! by @jonny | Stardance
|
jonny
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @jonny | Stardance
|
1793235304.5751007
|
1793840104.5751007
|
|
13119
|
My very own WebOS by @magomango | Stardance
|
magomango
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @magomango | Stardance
|
1792925294.1860816
|
1793789294.1860816
|
|
13120
|
My very own WebOS by @pheheartscats | Stardance
|
pheheartscats
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @pheheartscats | Stard Title: My very own WebOS by @pheheartscats | Stardance...
|
1793526617.3367841
|
1794131417.3367841
|
|
13121
|
ahmeds resume by @rabieulawal_h | Stardance
|
rabieulawal_h
|
0
|
1.61
|
0
|
[]
|
[{"post_id": 4971, "ts": "2026 [{"post_id": 4971, "ts": "2026-06-08T16:54:07Z", "hours": 1.6139, "text": "i am learning html and css, so i wanted to make a site i thought that making a website to roast my friend will be fun. i just started and hope to make this pretty good"}]...
|
Title: ahmeds resume by @rabieulawal_h | Stardance Title: ahmeds resume by @rabieulawal_h | Stardance
Devlogs:
i am learning html and css, so i wanted to make a site i thought that making a website to roast my friend will be fun. i just started and hope to make this pretty good...
|
1793396981.5141308
|
1794001781.5141308
|
|
13122
|
Health AI Guardian by @charuvikshirsagar | Stardan Health AI Guardian by @charuvikshirsagar | Stardance...
|
charuvikshirsagar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Health AI Guardian by @charuvikshirsagar | Title: Health AI Guardian by @charuvikshirsagar | Stardance...
|
1793512472.7307186
|
1794117272.7307186
|
|
13123
|
My very own WebOS by @Hapis | Stardance
|
Hapis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Hapis | Stardance
|
1793465331.271992
|
1794070131.271992
|
|
13124
|
Cosmic Object Explorer by @ApoorvaDubey | Stardanc Cosmic Object Explorer by @ApoorvaDubey | Stardance...
|
ApoorvaDubey
|
0
|
10.86
|
0
|
[]
|
[{"post_id": 27068, "ts": "202 [{"post_id": 27068, "ts": "2026-07-12T09:06:00Z", "hours": 2.8436, "text": "** Devlog #6** Hey everyone, I pushed some good updates. Improved the semantic search so it’s noticeably faster now. And also fixed a few bugs to make the app more stable especially so it doesn’t crash or slow down badly when multiple requests come in. I kept the same Xenova Transformers embedding model, though I’ll try to find some better alternatives in future. Also added pages so users can comfortably browse the latest information. Did some small UI improvements too so that it feels cleaner. I’ll continue polishing the interface in coming updates. The base model of the app is starting to feel somewhat ready now. Next Steps Planning to add more fun features like the biggest black holes and different or largest sun kinda things. I’m also thinking about adding a space map showing where we are and nearby celestial objects. I’m leaning toward limiting it to about 10 light years for now, it’s not too small or an unreachable distance, it covers the closest star systems (like Alpha Centauri) without getting too overwhelming or performance-heavy. And I can always expand later."}, {"post_id": 16407, "ts": "2026-06-26T18:06:55Z", "hours": 2.9067, "text": "Devlog Update: Fixing the Irrelevant Search Results Bug Hey everyone, As I mentioned in the last devlog, I ran into a significant bug where the search functionality was returning results for any query, completely ignoring whether the content was relevant to space-related themes. The Fix I’ve now resolved the core issue by switching to semantic search . Instead of relying on simple keyword or basic matching, the system now uses embeddings to understand the meaning and context of both the query and the stored data. This ensures that only genuinely relevant space-themed results are returned. For the implementation, I integrated @xenova /transformers (the browser/Node.js friendly Transformers.js library). It allows to run powerful embedding models locally, which is great for privacy and offline capability. Remaining Challenge The main downside right now is that the semantic search is quite data-heavy. It’s putting significant load on memory, especially when handling larger datasets or multiple simultaneous queries. I’ll need to explore optimizations such as: Model quantization Smaller/faster embedding models Caching strategies Possible backend offloading Even with the memory issue still pending, this change fixes a major part of the bug and represents a big step forward in search quality. Thanks for following along more updates soon as I tackle the performance side of things!"}, {"post_id": 12640, "ts": "2026-06-20T17:24:24Z", "hours": 1.7764, "text": "#Devlog 5 – Searching Robert Downey Jr. on my space app and NASA GIBS Integration. A few weeks ago, I integrated Wikipedia into my Cosmic Object Explorer so that users could receive information by combining Wikipedia data with multiple NASA APIs. While polishing the UI today, I encountered a serious bug. I started by searching about Robert Downey Jr. and well not to my surprise, the app returned information. This revealed a significant issue in my implementation. Since Cosmic Object Explorer is intended to be a vertical search engine focused on astronomy and space-related objects, it should only return results within its intended domain. The test reminded me that I had overlooked an important component of the search pipeline, semantic scoping and content filtering. The application was accepting and processing queries outside the astronomy domain instead of restricting results to relevant celestial objects. This is now a high-priority issue, and I will be working on implementing proper filtering and query validation over the next few days. What I Did Today ? 1. Improved and polished the UI for a cleaner and more user-friendly experience. 2. Fixed several client-side bugs. 3. Added support for displaying exoplanet data correctly. 4. Integrated the NASA GIBS API on the server side. 5. Performed additional testing and identified the Wikipedia semantic-scoping bug. Next Steps : 1. The first priority will be to fix the Wikipedia semantic-scoping. 2. Connect the NASA GIBS API to the client side. 3. Continue refining the search experience and overall usability. 4. Add special exploration features, such as the largest black hole or the biggest nebula and other interesting astronomical records and discoveries."}, {"post_id": 10758, "ts": "2026-06-17T17:27:23Z", "hours": 0.7269, "text": "Devlog 4 – Expanding Orbital Data CapabilitiesThis week, I successfully integrated NASA’s TLE (Two-Line Element) API into Cosmic Object Explorer. The application can now retrieve and display real orbital data for satellites and other Earth-orbiting objects, providing users with access to important parameters such as orbital period, eccentricity, inclination, and other tracking information.To make this data more accessible, I also added a user-friendly explanation system that describes what each orbital parameter means. Instead of only displaying technical values, the application now helps users understand concepts like eccentricity, orbital period, and inclination in simple terms.Next, I plan to integrate NASA’s Exoplanet API to expand the range of astronomical objects available in the explorer. Future development will also focus on incorporating additional NASA datasets, improving search functionality, refining the user interface, and introducing new educational features that make complex space science information easier to explore and understand."}, {"post_id": 8106, "ts": "2026-06-13T15:03:16Z", "hours": 0.9386, "text": "Devlog 3 – Expanding the Cosmic Object Explorer Update guys, I have successfully integrated Wikipedia into the Cosmic Object Explorer. Previously, the application relied mainly on NASA’s Images and Video Library API, which was useful for retrieving recent media and related information. Now, search results combine data from both Wikipedia and NASA’s media archives, providing users with a much more complete overview of cosmic objects in a single place. With this update, users can access general background information, scientific context, and NASA imagery without needing to search across multiple websites. This is a significant step toward making the explorer a more comprehensive astronomy research tool. Next Steps Integrate additional NASA APIs to expand the range of available data. Improve and smooth out the search functionality for more accurate results. Add better error handling and support for a wider variety of search queries. Enhance the user interface and overall user experience. Implement caching and performance optimizations to reduce loading times. Introduce special features such as object comparison tools, interactive astronomy facts, personalized discovery suggestions, and richer data visualizations. The project is steadily moving closer to its goal of becoming a single destination for exploring and learning about objects across the universe."}, {"post_id": 6652, "ts": "2026-06-11T04:41:29Z", "hours": 1.19, "text": "Devlog -02: API Changes and Progress Since the last update, I made an important change to the project’s data source. Initially, I planned to use NASA Horizons as the primary API, but for now I have switched to the NASA Images and Video Library API. This allows users to search for astronomical objects and immediately receive relevant images, media, and recent information related to their query. The current prototype successfully fetches and displays results based on user input, making the application more interactive and visually engaging. However, this API only provides recent news, media or mission related updates. To address this, I’m gonna be integrating Wikipedia so that users can get other general knowledge alongside NASA content. Next Steps: Integrate Wikipedia to provide detailed descriptions and background information. Add additional NASA APIs such as APOD, NEO, and other scientific databases. Improve the search system to combine information from multiple sources into a single view. Enhance the user interface and overall user experience. Continue working toward the original goal of creating a comprehensive explorer for cosmic objects and astronomical data. The project is steadily moving closer to becoming a one-stop platform for discovering and learning about objects throughout the universe."}, {"post_id": 6313, "ts": "2026-06-10T16:59:01Z", "hours": 0.4758, "text": "Devlog 1 – The Beginning of Cosmic Object Explorer A few weeks ago, I was searching for detailed information about Hoag’s Object. While basic information was easy to find, locating scientific data, images, and observational details required digging through NASA archives and astronomical databases. After spending hours searching, I thought: Why isn’t there a simple way to explore celestial objects? That idea became “Cosmic Object Explorer”. Cosmic Object Explorer is a web application that allows users to search for celestial objects and access scientific information through a simple interface. Progress So Far Built the frontend user interface Developed a C++ backend search engine Implemented partial search functionality Integrated astronomical data sources Began deployment setup with Vercel Planned Features Search stars, planets, nebulae, galaxies, asteroids, and comets Display object type, distance, and scientific information Show images and observations from astronomical databases Improve search accuracy and database coverage Tech Stack Frontend: HTML, CSS, JavaScript Backend: C++ Deployment: Vercel Next Steps Expand the object database Add image support Create detailed object pages Deploy a public version Cosmic Object Explorer started from a simple frustration while researching space, and I hope it grows into a platform that makes exploring the universe easier for everyone."}]...
|
Title: Cosmic Object Explorer by @ApoorvaDubey | S Title: Cosmic Object Explorer by @ApoorvaDubey | Stardance
Devlogs:
Devlog 1 – The Beginning of Cosmic Object Explorer A few weeks ago, I was searching for detailed information about Hoag’s Object. While basic information was easy to find, locating scientific data, images, and observational details required digging through NASA archives and astronomical databases. After spending hours searching, I thought: Why isn’t there a simple way to explore celestial objects? That idea became “Cosmic Object Explorer”. Cosmic Object Explorer is a web application that allows users to search for celestial objects and access scientific information through a simple interface. Progress So Far Built the frontend user interface Developed a C++ backend search engine Implemented partial search functionality Integrated astronomical data sources Began deployment setup with Vercel Planned Features Search stars, planets, nebulae, galaxies, asteroids, and comets Display object type, distance, and scientific information Show images and observations from astronomical databases Improve search accuracy and database coverage Tech Stack Frontend: HTML, CSS, JavaScript Backend: C++ Deployment: Vercel Next Steps Expand the object database Add image support Create detailed object pages Deploy a public version Cosmic Object Explorer started from a simple frustration while researching space, and I hope it grows into a platform that makes exploring the universe easier for everyone.
Devlog -02: API Changes and Progress Since the last update, I made an important change to the project’s data source. Initially, I planned to use NASA Horizons as the primary API, but for now I have switched to the NASA Images and Video Library API. This allows users to search for astronomical objects and immediately receive relevant images, media, and recent information related to their query. The current prototype successfully fetches and displays results based on user input, making the application more interactive and visually engaging. However, this API only provides recent news, media or mission related updates. To address this, I’m gonna be integrating Wikipedia so that users can get other general knowledge alongside NASA content. Next Steps: Integrate Wikipedia to provide detailed descriptions and background information. Add additional NASA APIs such as APOD, NEO, and other scientific databases. Improve the search system to combine information from multiple sources into a single view. Enhance the user interface and overall user experience. Continue working toward the original goal of creating a comprehensive explorer for cosmic objects and astronomical data. The project is steadily moving closer to becoming a one-stop platform for discovering and learning about objects throughout the universe.
Devlog 3 – Expanding the Cosmic Object Explorer Update guys, I have successfully integrated Wikipedia into the Cosmic Object Explorer. Previously, the application relied mainly on NASA’s Images and Video Library API, which was useful for retrieving recent media and related information. Now, search results combine data from both Wikipedia and NASA’s media archives, providing users with a much more complete overview of cosmic objects in a single place. With this update, users can access general background information, scientific context, and NASA imagery without needing to search across multiple websites. This is a significant step toward making the explorer a more comprehensive astronomy research tool. Next Steps Integrate additional NASA APIs to expand the range of available data. Improve and smooth out the search functionality for more accurate results. Add better error handling and support for a wider variety of search queries. Enhance the user interface and overall user experience. Implement caching and performance optimizations to reduce loading times. Introduce special features such as object comparison tools, interactive astronomy facts, personalized discovery suggestions, and richer data visualizations. The project is steadily moving closer to its goal of becoming a single destination for exploring and learning about objects across the universe.
Devlog 4 – Expanding Orbital Data CapabilitiesThis week, I successfully integrated NASA’s TLE (Two-Line Element) API into Cosmic Object Explorer. The application can now retrieve and display real orbital data for satellites and other Earth-orbiting objects, providing users with access to important parameters such as orbital period, eccentricity, inclination, and other tracking information.To make this data more accessible, I also added a user-friendly explanation system that describes what each orbital parameter means. Instead of only displaying technical values, the application now helps users understand concepts like eccentricity, orbital period, and inclination in simple terms.Next, I plan to integrate NASA’s Exoplanet API to expand the range of astronomical objects available in the explorer. Future development will also focus on incorporating additional NASA datasets, improving search functionality, refining the user interface, and introducing new educational features that make complex space science information easier to explore and understand.
#Devlog 5 – Searching Robert Downey Jr. on my space app and NASA GIBS Integration. A few weeks ago, I integrated Wikipedia into my Cosmic Object Explorer so that users could receive information by combining Wikipedia data with multiple NASA APIs. While polishing the UI today, I encountered a serious bug. I started by searching about Robert Downey Jr. and well not to my surprise, the app returned information. This revealed a significant issue in my implementation. Since Cosmic Object Explorer is intended to be a vertical search engine focused on astronomy and space-related objects, it should only return results within its intended domain. The test reminded me that I had overlooked an important component of the search pipeline, semantic scoping and content filtering. The application was accepting and processing queries outside the astronomy domain instead of restricting results to relevant celestial objects. This is now a high-priority issue, and I will be working on implementing proper filtering and query validation over the next few days. What I Did Today ? 1. Improved and polished the UI for a cleaner and more user-friendly experience. 2. Fixed several client-side bugs. 3. Added support for displaying exoplanet data correctly. 4. Integrated the NASA GIBS API on the server side. 5. Performed additional testing and identified the Wikipedia semantic-scoping bug. Next Steps : 1. The first priority will be to fix the Wikipedia semantic-scoping. 2. Connect the NASA GIBS API to the client side. 3. Continue refining the search experience and overall usability. 4. Add special exploration features, such as the largest black hole or the biggest nebula and other interesting astronomical records and discoveries.
Devlog Update: Fixing the Irrelevant Search Results Bug Hey everyone, As I mentioned in the last devlog, I ran into a significant bug where the search functionality was returning results for any query, completely ignoring whether the content was relevant to space-related themes. The Fix I’ve now resolved the core issue by switching to semantic search . Instead of relying on simple keyword or basic matching, the system now uses embeddings to understand the meaning and context of both the query and the stored data. This ensures that only genuinely relevant space-themed results are returned. For the implementation, I integrated @xenova /transformers (the browser/Node.js friendly Transformers.js library). It allows to run powerful embedding models locally, which is great for privacy and offline capability. Remaining Challenge The main downside right now is that the semantic search is quite data-heavy. It’s putting significant load on memory, especially when handling larger datasets or multiple simultaneous queries. I’ll need to explore optimizations such as: Model quantization Smaller/faster embedding models Caching strategies Possible backend offloading Even with the memory issue still pending, this change fixes a major part of the bug and represents a big step forward in search quality. Thanks for following along more updates soon as I tackle the performance side of things!
** Devlog #6** Hey everyone, I pushed some good updates. Improved the semantic search so it’s noticeably faster now. And also fixed a few bugs to make the app more stable especially so it doesn’t crash or slow down badly when multiple requests come in. I kept the same Xenova Transformers embedding model, though I’ll try to find some better alternatives in future. Also added pages so users can comfortably browse the latest information. Did some small UI improvements too so that it feels cleaner. I’ll continue polishing the interface in coming updates. The base model of the app is starting to feel somewhat ready now. Next Steps Planning to add more fun features like the biggest black holes and different or largest sun kinda things. I’m also thinking about adding a space map showing where we are and nearby celestial objects. I’m leaning toward limiting it to about 10 light years for now, it’s not too small or an unreachable distance, it covers the closest star systems (like Alpha Centauri) without getting too overwhelming or performance-heavy. And I can always expand later....
|
1793163211.1698658
|
1793768011.1698658
|
|
13125
|
Untitled by @moayed-jouini | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @moayed-jouini | Stardance
|
1793307224.7574763
|
1793912024.7574763
|
|
13126
|
CosmoForge by @r0n3l | Stardance
|
r0n3l
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CosmoForge by @r0n3l | Stardance
|
1793300144.1379313
|
1793904944.1379313
|
|
13127
|
Untitled project by @demps | Stardance
|
demps
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @demps | Stardance
|
1793156093.632952
|
1793760893.632952
|
|
13128
|
Study Guide Maker by @kyler_zheng29 | Stardance
|
kyler_zheng29
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Study Guide Maker by @kyler_zheng29 | Stard Title: Study Guide Maker by @kyler_zheng29 | Stardance...
|
1793299951.1573448
|
1793904751.1573448
|
|
13129
|
Moondew Mountains by @samriddhjoneja | Stardance
|
samriddhjoneja
|
2
|
14.0
|
59
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-01T17:17:18Z", "hours": 2.0, "multiplier": 5.52, "payout": 13, "blessing": "neutral", "text": "I made an rpg game . WASD or arrow keys to move, slay all the slimes in all the levels to win. the slimes might drop health. Added a main menu and made slimes more dangerous and fixed some bugs", "repo": "https://github.com/sj6258/Moondew--Mountains", "demo": "https://sj6258.itch.io/moondew-mountains"}, {"ship_num": 2, "ts": "2026-08-27T17:39:36Z", "hours": 12.0, "multiplier": 7.83, "payout": 46, "blessing": "neutral", "text": "I made an RPG game with cute retro graphics. The part which was really challenging and which i am proud of is making the collisions work for the enemy and the HUD heart health display system. WASD to move and E to attack. The goal is to eliminate all the enemies on all 3 levels", "repo": "https://github.com/sj6258/Moondew--Mountains", "demo": "https://sj6258.itch.io/moondew-mountains"}]...
|
[{"post_id": 59696, "ts": "202 [{"post_id": 59696, "ts": "2026-09-01T16:53:57Z", "hours": 2.3514, "text": "Made a Main Menu screen with a settings menu where you can control volume and adjust fullscreen Also changed enemy behaviour and made it more menacing. scaled it up and increase its sight. fixed a bug where the health wouldn’t get dropped correctly when enemy is killed"}, {"post_id": 55669, "ts": "2026-08-27T17:05:00Z", "hours": 0.8497, "text": "Designed th e health mechanics for the player Used the depiction of 5 hearts on the HUD for the player health where each half heart gets taken away for each slime hit. Fixed a bug where the player would get heart after the slime was defeated The slimes now have a 50 percent chance to drop a heart Finally finished my game"}, {"post_id": 55034, "ts": "2026-08-26T13:49:14Z", "hours": 1.3253, "text": "Made the health system for the player where the health gets reduced when damaged by a slime. Health does not regenerate when changing levels also added the UI for health as 5 hearts which deplete accordingly."}, {"post_id": 53721, "ts": "2026-08-24T12:02:27Z", "hours": 1.9056, "text": "Created the transitions between the levels and scenes so that when the player dies the screen fades away and restarts from level 1 Made the player death animation and coded it in the game Fixed a bug where the bridge in level 3 was not working properly Fixed another bug where the players health would remain the same after death and respawn. Added variables and elements for players health Also fixed the player taking damage sound"}, {"post_id": 48052, "ts": "2026-08-16T10:28:10Z", "hours": 1.0256, "text": "Completed Level design made level 2 and level 3. Also made transitions using gdscript and preload cmd. Finished combat mechanics only player health and slime damage is left fixed a bug where it wouldn’t changed scenes or get back to the root scene completed the levels by using a root scene and making inherited scenes . added a bridge sprite to the game"}, {"post_id": 47557, "ts": "2026-08-15T15:11:11Z", "hours": 1.0408, "text": "Started on level 2 and level 3 inherited from root level, made a change in scene transitions so that it changes it automatically using the level no. as int variable Changed Enemy behaviour and increased the detection range Fixed Combat bugs and the enemy would be thrown in the opposite direction"}, {"post_id": 46485, "ts": "2026-08-13T18:36:37Z", "hours": 2.235, "text": "Finished making the player and added a camera that moves with the player with limits. Made the root level from which scenes will be inherited and added overlay decoration Added Y-sorting so that the game feels 3D and normal Fixed collisions for slimes and decorations and also added world borders Fixed some bugs in combat and movement mechanics"}, {"post_id": 9489, "ts": "2026-06-15T20:49:00Z", "hours": 1.1489, "text": "Connected the signals for detection and attack Added attack mechanics to the player so now the player hits the slime and it takes damage and gets pushed back Added health to slime so that it plays destroyed animation after getting hit a few times and evaporates from the game"}, {"post_id": 4984, "ts": "2026-06-08T17:09:10Z", "hours": 2.0567, "text": "Started working on a top down role playing game with 3 levels and slimes as enemies to deal with. Imported the assets Added player and enemy sprites Made the animations for the player and sprites Added collisions and detection box"}]...
|
Title: Moondew Mountains by @samriddhjoneja | Star Title: Moondew Mountains by @samriddhjoneja | Stardance
Devlogs:
Started working on a top down role playing game with 3 levels and slimes as enemies to deal with. Imported the assets Added player and enemy sprites Made the animations for the player and sprites Added collisions and detection box
Connected the signals for detection and attack Added attack mechanics to the player so now the player hits the slime and it takes damage and gets pushed back Added health to slime so that it plays destroyed animation after getting hit a few times and evaporates from the game
Finished making the player and added a camera that moves with the player with limits. Made the root level from which scenes will be inherited and added overlay decoration Added Y-sorting so that the game feels 3D and normal Fixed collisions for slimes and decorations and also added world borders Fixed some bugs in combat and movement mechanics
Started on level 2 and level 3 inherited from root level, made a change in scene transitions so that it changes it automatically using the level no. as int variable Changed Enemy behaviour and increased the detection range Fixed Combat bugs and the enemy would be thrown in the opposite direction
Completed Level design made level 2 and level 3. Also made transitions using gdscript and preload cmd. Finished combat mechanics only player health and slime damage is left fixed a bug where it wouldn’t changed scenes or get back to the root scene completed the levels by using a root scene and making inherited scenes . added a bridge sprite to the game
Created the transitions between the levels and scenes so that when the player dies the screen fades away and restarts from level 1 Made the player death animation and coded it in the game Fixed a bug where the bridge in level 3 was not working properly Fixed another bug where the players health would remain the same after death and respawn. Added variables and elements for players health Also fixed the player taking damage sound
Made the health system for the player where the health gets reduced when damaged by a slime. Health does not regenerate when changing levels also added the UI for health as 5 hearts which deplete accordingly.
Designed th e health mechanics for the player Used the depiction of 5 hearts on the HUD for the player health where each half heart gets taken away for each slime hit. Fixed a bug where the player would get heart after the slime was defeated The slimes now have a 50 percent chance to drop a heart Finally finished my game
Made a Main Menu screen with a settings menu where you can control volume and adjust fullscreen Also changed enemy behaviour and made it more menacing. scaled it up and increase its sight. fixed a bug where the health wouldn’t get dropped correctly when enemy is killed
Ships:
I made an RPG game with cute retro graphics. The part which was really challenging and which i am proud of is making the collisions work for the enemy and the HUD heart health display system. WASD to move and E to attack. The goal is to eliminate all the enemies on all 3 levels
I made an rpg game . WASD or arrow keys to move, slay all the slimes in all the levels to win. the slimes might drop health. Added a main menu and made slimes more dangerous and fixed some bugs...
|
1793523006.884309
|
1793609406.884309
|
|
13130
|
My first slack bot! by @The_King | Stardance
|
The_King
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @The_King | Stardanc Title: My first slack bot! by @The_King | Stardance...
|
1793487085.1756735
|
1794091885.1756735
|
|
13131
|
Custom Blog search engine by @eshark22 | Stardance
|
eshark22
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Custom Blog search engine by @eshark22 | St Title: Custom Blog search engine by @eshark22 | Stardance...
|
1793440438.370905
|
1794045238.370905
|
|
13132
|
My first slack bot! by @Tech | Stardance
|
Tech
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Tech | Stardance
|
1793400710.0713568
|
1794005510.0713568
|
|
13133
|
My awesome macropad! by @DixieV48 | Stardance
|
DixieV48
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @DixieV48 | Stardan Title: My awesome macropad! by @DixieV48 | Stardance...
|
1792806770.1983008
|
1793411570.1983008
|
|
13134
|
Camera Mods by @henryozhao | Stardance
|
henryozhao
|
0
|
7.97
|
0
|
[]
|
[{"post_id": 8901, "ts": "2026 [{"post_id": 8901, "ts": "2026-06-14T20:18:17Z", "hours": 7.9728, "text": "Not polished but finished"}]...
|
Title: Camera Mods by @henryozhao | Stardance
Dev Title: Camera Mods by @henryozhao | Stardance
Devlogs:
Not polished but finished...
|
1793177406.4734335
|
1793782206.4734335
|
|
13135
|
Exelmed by @Tech-Lord | Stardance
|
Tech-Lord
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Exelmed by @Tech-Lord | Stardance
|
1793461754.3026843
|
1794066554.3026843
|
|
13136
|
My awesome macropad! by @royandrew250 | Stardance
|
royandrew250
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @royandrew250 | Sta Title: My awesome macropad! by @royandrew250 | Stardance...
|
1793029812.1946435
|
1793634612.1946435
|
|
13137
|
Uzi controlled by ai by @Smaxbrine | Stardance
|
Smaxbrine
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Uzi controlled by ai by @Smaxbrine | Starda Title: Uzi controlled by ai by @Smaxbrine | Stardance...
|
1793364907.2065377
|
1793969707.2065377
|
|
13138
|
My awesome macropad! by @abelturbobragg_7038 | Sta My awesome macropad! by @abelturbobragg_7038 | Stardance...
|
abelturbobragg_7038
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @abelturbobragg_703 Title: My awesome macropad! by @abelturbobragg_7038 | Stardance...
|
1793238937.4438481
|
1793843737.4438481
|
|
13139
|
My first slack bot! by @FalsePositive | Stardance
|
FalsePositive
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @FalsePositive | Sta Title: My first slack bot! by @FalsePositive | Stardance...
|
1793202900.6325247
|
1793807700.6325247
|
|
13140
|
My first slack bot! by @Kidus | Stardance
|
Kidus
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Kidus | Stardance
|
1793228052.3782015
|
1793832852.3782015
|
|
13141
|
Untitled by @saachikasat | Stardance
|
saachikasat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @saachikasat | Stardance
|
1793447773.5676
|
1794052573.5676
|
|
13142
|
My diy coilgun by @miloogle4365 | Stardance
|
miloogle4365
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My diy coilgun by @miloogle4365 | Stardance
|
1793519283.974559
|
1794124083.974559
|
|
13143
|
My very own WebOS by @Anich | Stardance
|
Anich
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Anich | Stardance
|
1793490701.3885827
|
1794095501.3885827
|
|
13144
|
PIEZOELECTRIC HOVERBOARD by @ABUNASR | Stardance
|
ABUNASR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: PIEZOELECTRIC HOVERBOARD by @ABUNASR | Star Title: PIEZOELECTRIC HOVERBOARD by @ABUNASR | Stardance...
|
1793559248.971798
|
1794164048.971798
|
|
13145
|
E-reader by @lughaidh | Stardance
|
lughaidh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: E-reader by @lughaidh | Stardance
|
1793181024.9005709
|
1793785824.9005709
|
|
13146
|
My very own WebOS by @cameronhart | Stardance
|
cameronhart
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @cameronhart | Stardan Title: My very own WebOS by @cameronhart | Stardance...
|
1793494426.470892
|
1794099226.470892
|
|
13147
|
TS-OS by @DenizCiger | Stardance
|
DenizCiger
|
0
|
7.87
|
0
|
[]
|
[{"post_id": 22376, "ts": "202 [{"post_id": 22376, "ts": "2026-07-04T20:22:42Z", "hours": 3.9172, "text": "I worked quite a bit on some minor QoL tweaks like taskbar pinning, desktop icons, and improved window instance management, however most of my time probably went into the whole ‘file system’ logic. I read a bit about System development online, which taught me about tree structures and optimized child/parent architectures. For this project however we can stay simple as with those few files we likely won’t run into any intense RAM problems anyways. By iterating through the parent nodes until it hits the root node, and from that exploration data, the explorer then constructs the visible path name for the user. A few features are still on the radar, but I’m excited that I’ll soon be able to finish & ship this fun little project and tackle the next challenge!"}, {"post_id": 6828, "ts": "2026-06-11T13:35:11Z", "hours": 2.6711, "text": "Added logic for opening, minimizing & opening windows. Also made windows draggable and focusable. Made sure to make window management logic more robust & future-proof"}, {"post_id": 5468, "ts": "2026-06-09T08:18:33Z", "hours": 1.2847, "text": "Setup the initial project with a basic static window and a taskbar. Then refactored everything to reusable react components to stay organized"}]...
|
Title: TS-OS by @DenizCiger | Stardance
Devlogs:
Title: TS-OS by @DenizCiger | Stardance
Devlogs:
Setup the initial project with a basic static window and a taskbar. Then refactored everything to reusable react components to stay organized
Added logic for opening, minimizing & opening windows. Also made windows draggable and focusable. Made sure to make window management logic more robust & future-proof
I worked quite a bit on some minor QoL tweaks like taskbar pinning, desktop icons, and improved window instance management, however most of my time probably went into the whole ‘file system’ logic. I read a bit about System development online, which taught me about tree structures and optimized child/parent architectures. For this project however we can stay simple as with those few files we likely won’t run into any intense RAM problems anyways. By iterating through the parent nodes until it hits the root node, and from that exploration data, the explorer then constructs the visible path name for the user. A few features are still on the radar, but I’m excited that I’ll soon be able to finish & ship this fun little project and tackle the next challenge!...
|
1793534083.97331
|
1794138883.97331
|
|
13148
|
Open source custom UAV by @alexanderkotcharian | S Open source custom UAV by @alexanderkotcharian | Stardance...
|
alexanderkotcharian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Open source custom UAV by @alexanderkotchar Title: Open source custom UAV by @alexanderkotcharian | Stardance...
|
1793177620.3826666
|
1793782420.3826666
|
|
13149
|
My first slack bot! by @adviksristy | Stardance
|
adviksristy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @adviksristy | Stard Title: My first slack bot! by @adviksristy | Stardance...
|
1793303679.1418636
|
1793908479.1418636
|
|
13150
|
Math survivors by @Ojabyemil | Stardance
|
Ojabyemil
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Math survivors by @Ojabyemil | Stardance
|
1793260311.9391544
|
1793865111.9391544
|