|
16551
|
micro:bit Hackpad! by @THEbluefirestudios | Starda micro:bit Hackpad! by @THEbluefirestudios | Stardance...
|
THEbluefirestudios
|
0
|
2.14
|
0
|
[]
|
[{"post_id": 8546, "ts": "2026 [{"post_id": 8546, "ts": "2026-06-14T06:34:03Z", "hours": 2.1447, "text": "Wow, this 3D -printerless Hackpad is becoming very messy. Before you call me stupid, the customs on PCBs and 3D printed parts here in India is ENORMOUS, and I am brokie brokie. Mybe I’ll make a proper hackpad soon."}]...
|
Title: micro:bit Hackpad! by @THEbluefirestudios | Title: micro:bit Hackpad! by @THEbluefirestudios | Stardance
Devlogs:
Wow, this 3D -printerless Hackpad is becoming very messy. Before you call me stupid, the customs on PCBs and 3D printed parts here in India is ENORMOUS, and I am brokie brokie. Mybe I’ll make a proper hackpad soon....
|
1793199251.066756
|
1793804051.066756
|
|
16552
|
Space Sticker Maker by @0xtaufeeq | Stardance
|
0xtaufeeq
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Space Sticker Maker by @0xtaufeeq | Stardan Title: Space Sticker Maker by @0xtaufeeq | Stardance...
|
1793451285.4985483
|
1794056085.4985483
|
|
16553
|
GlobalTranslate by @faayesha43 | Stardance
|
faayesha43
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: GlobalTranslate by @faayesha43 | Stardance
|
1793800253.9688227
|
1794405053.9688227
|
|
16554
|
Untitled project by @praji29 | Stardance
|
praji29
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @praji29 | Stardance
|
1793339836.9165905
|
1793944636.9165905
|
|
16555
|
AMP-X by @Phoenixeyez | Stardance
|
Phoenixeyez
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AMP-X by @Phoenixeyez | Stardance
|
1793767666.2994106
|
1794372466.2994106
|
|
16556
|
My awesome macropad! by @ahadamin | Stardance
|
ahadamin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ahadamin | Stardan Title: My awesome macropad! by @ahadamin | Stardance...
|
1793188057.3168106
|
1793792857.3168106
|
|
16557
|
My first slack bot! by @Di | Stardance
|
Di
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Di | Stardance
|
1793195409.165939
|
1793800209.165939
|
|
16558
|
My very own WebOS by @rafif21 | Stardance
|
rafif21
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @rafif21 | Stardance
|
1793263959.5114834
|
1793868759.5114834
|
|
16559
|
My first slack bot! by @jaydenharvey | Stardance
|
jaydenharvey
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @jaydenharvey | Star Title: My first slack bot! by @jaydenharvey | Stardance...
|
1793483396.0867994
|
1794088196.0867994
|
|
16560
|
My very own WebOS by @JanaHungreder | Stardance
|
JanaHungreder
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @JanaHungreder | Stard Title: My very own WebOS by @JanaHungreder | Stardance...
|
1793217264.7002668
|
1793822064.7002668
|
|
16561
|
StydyCrusades by @shahid007 | Stardance
|
shahid007
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: StydyCrusades by @shahid007 | Stardance
|
1793364993.8956604
|
1793969793.8956604
|
|
16562
|
Modular Tester by @sjpark01 | Stardance
|
sjpark01
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Modular Tester by @sjpark01 | Stardance
|
1792929018.5233033
|
1793793018.5233033
|
|
16563
|
Electricty Generator planted in the Road. by @Hone Electricty Generator planted in the Road. by @HoneyBadgerF1 | Stardance...
|
HoneyBadgerF1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Electricty Generator planted in the Road. b Title: Electricty Generator planted in the Road. by @HoneyBadgerF1 | Stardance...
|
1793260304.4138865
|
1793865104.4138865
|
|
16564
|
ReapingOS by @alessilo | Stardance
|
alessilo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ReapingOS by @alessilo | Stardance
|
1793296334.5478804
|
1793901134.5478804
|
|
16565
|
My very own WebOS by @goob_erm | Stardance
|
goob_erm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @goob_erm | Stardance
|
1793159728.2669718
|
1793764528.2669718
|
|
16566
|
My First German Website by @rosikur | Stardance
|
rosikur
|
1
|
2.0
|
2
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-11T16:37:25Z", "hours": 2.0, "multiplier": 1.02, "payout": 2, "blessing": "neutral", "text": "I made my very first Website in school and wanted to share it with you guys it took so long for this little becuase i made some typos and bugs and took half an hour to publish maybe i´ll add js too someday lovve Rossi", "repo": "https://github.com/rosikur/My-website", "demo": "https://rosikur.github.io/My-website/"}]...
|
[{"post_id": 6916, "ts": "2026 [{"post_id": 6916, "ts": "2026-06-11T16:16:32Z", "hours": 1.5889, "text": "JavaScript going to continue working tmrw"}]...
|
Title: My First German Website by @rosikur | Stard Title: My First German Website by @rosikur | Stardance
Devlogs:
JavaScript going to continue working tmrw
Ships:
I made my very first Website in school and wanted to share it with you guys it took so long for this little becuase i made some typos and bugs and took half an hour to publish maybe i´ll add js too someday lovve Rossi...
|
1793785903.8181129
|
1793872303.8181129
|
|
16567
|
bob shot by @gamanm | Stardance
|
gamanm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: bob shot by @gamanm | Stardance
|
1793361357.7674055
|
1793966157.7674055
|
|
16568
|
My very own WebOS by @aeroonyx | Stardance
|
aeroonyx
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @aeroonyx | Stardance
|
1793177451.6867821
|
1793782251.6867821
|
|
16569
|
Untitled by @sniperpsycho7 | Stardance
|
sniperpsycho7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @sniperpsycho7 | Stardance
|
1793559135.609732
|
1794163935.609732
|
|
16570
|
My first slack bot! by @Azizbek | Stardance
|
Azizbek
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Azizbek | Stardance
|
1793505398.2303493
|
1794110198.2303493
|
|
16571
|
mocha by @Glitchy | Stardance
|
Glitchy
|
1
|
101.0
|
1806
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-13T18:57:02Z", "hours": 101.0, "multiplier": 17.94, "payout": 1806, "blessing": "neutral", "text": "I made a package manager for Windows, which is somewhat backwards compatible with scoop packages. To be honest there’s still a lot of work that I want to do, but I have exams and college application coming up soon so I can’t. That’s not to say I’m not happy with the state of the ship. At the very least it has all the core features that a package manager should have, but there are still a lot of bugs which is why this is only v0.0.1. The biggest challenge by far was trying to figure out how Scoop does things internally. A lot of stuff just doesn’t have documentation, so you have to dig through the really messy PowerShell source code.", "repo": "https://github.com/Protract-123/mocha", "demo": "https://github.com/Protract-123/mocha/releases/latest"}]...
|
[{"post_id": 67579, "ts": "202 [{"post_id": 67579, "ts": "2026-09-13T18:33:17Z", "hours": 1.7761, "text": "So I wrote a README, added a license (MIT of course) and setup CI/CD so that releases are automatically built and deployed. Honestly I forgot how hard it is to write a good README. You need to get a lot of information through without it looking like a wall of text."}, {"post_id": 67267, "ts": "2026-09-13T10:36:48Z", "hours": 5.8047, "text": "I forgot to make a devlog in between so this will be like 2 bigger devlogs. I parallelized bucket updates, which speeds it up quite a bit. This also allowed me to try out parallelism even more, which I plan to apply throughout the CLI later on. I also added configuration options for the runners which mocha shim will use to run certain file types. For example, you can set the python-runner to select the python version that’ll be used to run python scripts that are shimmed. Downloads now have a progress bar, so you don’t need to wonder whether something is happening or not during a long download. Finally env_set is fully supported since I added the relevant variable parsing. This was pretty much just me cleaning out the TODO list before I ship. I also did a lot of smaller bug fixes and refactors as seen below. fix(commands): prevent app installation if already installed (cb27d07) fix(commands): fix config opening with “start” (74f3679) fix(commands): correctly handle non-apps when upgrading (f7419f6) fix: make LogOutput go to Stdout not Stderr (bc10357) fix: handle empty versions correctly (2287da9) fix(pkg): remove correct temp dir (33189b6) fix(shim): warn for unknown shim extension (622c2b4) fix: skip downloads with no hash by default (69d4e35) fix: use correct timeout for downloads (44e527b) fix: drop unnecessary return value from GetExecutableEntries (9fd845c) fix(config): remove unused option (1339971) fix(commands): don’t error for valid results (87c4d6c) refactor(config): rename variables/functions (f253d9d) fix: use unique temp directories (a159e23) refactor: use fmt.Fprintln directly (d2d54bf)"}, {"post_id": 65401, "ts": "2026-09-10T14:55:22Z", "hours": 2.5386, "text": "Lots of small bug fixes and changes, I’ll just list them out: feat(cmd): allow removal of multiple shims in one execution (f2fae3f) fix(manifest): correctly ignore invalid shortcut entries (6a08478) fix(fileops): use correct registry type (5d5d796) fix(config): seed config with defaults (9dfaaff) fix(cmd): use correct release sources (a2a9ba1) fix(cmd): use bucket from install info (5a9109b) I also added support for more file types being shimmed, which helps a lot with compatibility. The file types are .py , .bat , .cmd , .jar and .ps1 ."}, {"post_id": 52474, "ts": "2026-08-22T16:37:15Z", "hours": 4.6758, "text": "Lot of time going into this devlog, but it makes sense since I did do a lot. I did this sweeping refactor of the entire commands module which moved around a lot of code. Essentially each command now gets it’s own directory under the commands module that represents it’s children/parents. For example commands/shim/remove/cmd.go contains code for the mocha shim remove command. Each cmd.go contains a Command struct that has the relevant fields and functions attached to it. This structure just makes things more organized and also means adding test files will be a bit easier since functionality is now isolated. I also sorted out the shim binary. So essentially https://github.com/ScoopInstaller/Shim offers different version of the shim binary which can be installed. Previously I hard coded the code to install cpp v0.1.0 but now users can run mocha shim binary releases to see the options and mocha shim binary setup to install their chosen binary. This also means we actually get the latest releases from GitHub."}, {"post_id": 51141, "ts": "2026-08-20T17:11:51Z", "hours": 3.6722, "text": "Finally got a bit of time to do a bit of development. First thing I did was remove a field from install.json to match scoop . This means that mocha should be a drop in replacement for existing scoop installs. Then I added partial support for env_set and env_add_path . The main thing I need to do to complete the feature is parse variables and replace them with the appropriate paths. These 2 fields are some of the last manifest fields I need to support besides pre/post (un)install hooks."}, {"post_id": 34596, "ts": "2026-07-25T13:39:02Z", "hours": 2.5778, "text": "My summer break has ended so development is going to be a lot slower from now. I added mocha outdated so you can list outdated apps before upgrading them to a newer version. Besides that I tweaked a lot of stuff related to CLI output. For example I changed search to output one table, and simply outputting exact matches at the top of that table. I also changed a lot of messages which were using LogOutput to LogInfo so they use the correct color and output to stderr and not stdout ."}, {"post_id": 31801, "ts": "2026-07-20T14:04:04Z", "hours": 1.5481, "text": "Not sure why I didn’t do this earlier, but I’ve added success messages to commands where it makes sense. Also added a success color to the config so you can change what the success color is. I do still need to improve CLI output quite a bit, but it’s slowly getting there."}, {"post_id": 30693, "ts": "2026-07-18T14:02:54Z", "hours": 2.1922, "text": "I’m writing this one right before F1 Qualifying at Spa! Continuing with the trend of some of my recent work, I improved what table outputs look like to be a little bit more readable. We now use proper separators in the form of Unicode Box Drawing Characters . I also made column alignment configurable, which improves legibility for some commands like mocha bucket list and mocha cache show . I’ve attached an image of the scoop and mocha versions of bucket list so you can compare for yourself."}, {"post_id": 30286, "ts": "2026-07-17T18:51:34Z", "hours": 3.4797, "text": "I love refactoring!!!! I’ll probably end up spending another 20 hours just on refactoring because it’s so fun!!!! This time around I wanted to refactor the code so that our commands orchestrate stuff instead of the helper functions. For example, pkg.Install would first download a package, then install it, and then link it through shims and shortcuts all by itself. This causes issues because it means error messages become slightly worse, and it creates a class of bugs due to edge cases where we don’t necessarily want this order of orchestration. Hence I did a lot of refactoring in the pkg module. I also ended up adding a way to skip verification of downloads when downloading, installing or updating a package through --skip-verify . It’s a useful option in situations where there is a malformed manifest or simply no hash to begin with."}, {"post_id": 30054, "ts": "2026-07-17T10:28:53Z", "hours": 4.6269, "text": "mocha now supports a user defined theme for output colors. In the process I ended up doing a lot of stuff related to the config. First thing I did was swap to fatih/color for colored output, since it handles stuff like colors in command prompt and removing color when output is piped. Then I refactored the config module. Earlier I would pass around a MochaConfiguration object through every function. Now I use a config singleton that’s accessible from any function. Why? Because it means I don’t need to pass the object every time I want to log information. Also means I don’t need to pass mochaDir through almost every function in the codebase. Getting user defined themes was a bit complicated because I needed a good way to handle a default theme so output doesn’t look bad if parsing fails. I handled this by only using the configured theme if every color resolves properly. Otherwise output falls back to the already loaded default theme. Due to this you still get colored output even if there are errors or warning before the configuration and theme is loaded."}, {"post_id": 29066, "ts": "2026-07-15T18:30:47Z", "hours": 4.7214, "text": "So I’ve been doing a bit of refactoring, a bit of bug fixing and a bit of optimization. Essentially just polishing mocha before I work on the next feature. Here’s some of the stuff I did: created tests for ParseRefString to validate behavior cache manifest json between info calls since I/O is really slow bumped dependency versions refactored manifest/info.go Besides that I fixed the uninstall flow since it was really bugged after the latest changes. Essentially mocha would uninstall apps with incorrect info. It would also try to remove shims/shortcuts for apps which don’t have any active shims/shortcuts. I then added a bit of logging since the uninstall command didn’t give any user output for whatever reason (i forgot to earlier)."}, {"post_id": 27086, "ts": "2026-07-12T10:29:45Z", "hours": 6.4975, "text": "This is going to be the equivalent of 2 devlogs since I thought I made one earlier for persists but I didn’t. New feature! We now handle persist items in order to store data between versions. These are files which are persisted between versions of an app. Lets take git as an example to explain why persist exists. Say you want to make sure your git config isn’t deleted every time you update. The issue with this is that the config file is saved in the version specfic directory. To resolve this we can keep the config in $MOCHA_DIR/persist and then symlink the config to where it needs to be, which is essentially what persist tells us to do. Since we handled persist items last time we can now implement mocha upgrade to update apps. The way scoop handles updates is by first removing anything that references the app, like shortcuts or shims . Then we just follow the install process from scratch. This leaves the old version available in case a user wants to revert versions due to a bug, while also updating to the latest available version. This can be seen in the video below, which shows me updating llama.cpp-hip-radeon ."}, {"post_id": 23572, "ts": "2026-07-06T16:39:13Z", "hours": 3.53, "text": "We now create shortcuts! This means any GUI apps should show up properly in the start menu, just like they do when you install with scoop . All I really had to do was a bit of orchestration since I decided to vendor in an implementation from https://github.com/jxeng/shortcut Besides that I expanded the number of apps that are supported by implementing a bit of code that handle architecture specific bin fields, along with bin fields which store 2D arrays. I also cleared up some of the TODO items. I swapped the junction implementation to an implementation from https://github.com/nyaosorg/go-windows-junction since we were previously shelling out to CLI. That and I added a bit more zip bomb protection For the purposes of the video below I changed the location which shortcuts get put to my desktop. It’ll probably be configurable, and match scoop by putting shortcuts in the startup menu by default"}, {"post_id": 22839, "ts": "2026-07-05T13:36:18Z", "hours": 3.3089, "text": "As I mentioned in the previous devlog I added good help information to every bit of the CLI. It’s surprisingly difficult to write good help messages which explains everything to users in a few words I also changed the behaviour of the mocha cache clear command to not clear all cache by default. That’s now gated behind the --all flag in order to match scoop a bit more"}, {"post_id": 21420, "ts": "2026-07-03T11:02:24Z", "hours": 1.0722, "text": "Typically I don’t want to make devlogs for small stuff like this, but this is something I found really cool. So I was working on help messages for all the commands when I realized that mocha bucket list felt a bit slower than pretty much every other command. This is because we need to shell out to git 2 times per bucket, and I had 4 buckets added. While 8 git commands might not sound like a lot, it was enough to make mocha bucket list feel slow. So what I did is I parallelized the metadata fetching through an errgroup . Instead of fetching the metadata for each bucket in order, we fetch the metadata for all 4 buckets simultaneously. This led to a big performance uplift. About 3 times faster than the old version of mocha , and just over 12 times faster than scoop for this operation. See the video below."}, {"post_id": 21386, "ts": "2026-07-03T09:17:07Z", "hours": 2.2464, "text": "I finished up mocha uninstall and mocha list , which means you can actually manage installed apps instead of manually deleting them. There’s not much that goes into mocha uninstall . You just need to remove the relevant shims and app directories since the apps that mocha supports are all portable. mocha list is similarly simple. It’s just loops over the directories in $MOCHA_DIR/apps and looks for apps along with the versions installed for each app."}, {"post_id": 19910, "ts": "2026-07-01T10:53:02Z", "hours": 5.4625, "text": "So I added support for more apps by implementing more extractors. This means in theory any apps which don’t need a pre-install or post-install should work. To be more specific, I handle a few more properties on manifests. Those being extract_dir and innosetup , which inform how an app needs to be installed. I also implement 7zip and innounp as extractors to support more file formats which applications are distributed in. Of course there’s still a lot of work before I consider this ready for public use. I need to create commands for some basic operations like uninstalling, updating and listing apps. I also need to handle shortcuts otherwise GUI apps can’t be accessed from the start menu. Besides that I need to improve the user experience. As you can see in the video below mocha just sort of dumps everything to the console even if it’s not relevant. Help menus are also critical to get working properly."}, {"post_id": 18238, "ts": "2026-06-29T09:51:16Z", "hours": 3.7839, "text": "Finished up the code cleanup in commands , fileops and manifests . I did catch a few edge cases and some incorrect behavior in the process, which is why I always spend so much time reviewing code. I did use AI to assist with code review because I think it’s an area where AI shines. AI is really good at finding small errors or inconsistencies in the codebase which I probably wouldn’t notice. For example, it identified that the ManifestReferences argument was not a required argument for the download command, which meant no help message was displayed on incorrect usage like the other commands. One big thing I will work on eventually is console output. Right now errors are well formatted but a lot of the time commands just run stuff without providing a lot of insight into what actions they are taking which isn’t great. Even the help menu is pretty useless right now (see the image below). Extra context: A manifest reference is a pointer to an app (e.g. main/ [email protected] )"}, {"post_id": 17027, "ts": "2026-06-27T17:10:53Z", "hours": 5.3025, "text": "Before working on more features and expanding the amount of apps mocha actually supports I wanted to go through the codebase and do a lot of cleanup since the codebase is quite messy. There are silly mistakes in some files and bad implementations in others. Hence the time I spent during this period was focused on moving code to where it should be and cleaning up some edge cases, specifically related to the bucket , config and shim modules. A good example of this is moving the code to get the active config to the config module instead of leaving it in main.go . Next up will be refactoring the commands , fileops , and manifest modules. I don’t have much to show so I figured I would present a feature I added but didn’t show earlier: the ability to skip cache hits with the --force flag when installing or downloading an app. Some context I forgot to add initially: I renamed the app module to manifest since I felt it was more accurate to what it actually handles scope wise."}, {"post_id": 15814, "ts": "2026-06-25T18:17:50Z", "hours": 2.5558, "text": "Huge milestone!!! I’ve gotten mocha install working for very basic apps! This means the entire process of downloading a file, then extracting it, then creating a junction and finally creating a shim now works for basic pieces of software! So in terms of what I actually did this devlog, I added cache hits to the download command since it’s relevant to the install command. I then implemented the aforementioned .zip extraction and junction creation. Then all that was left was a bit of orchestration, getting everything to work together properly. See a working install of innounp using mocha install below!"}, {"post_id": 15668, "ts": "2026-06-25T14:03:10Z", "hours": 0.7572, "text": "mocha update is another command which does very little but is very important. All it does is update the known_buckets file, and run git pull on all added buckets to update them. It can also update just the buckets you specify if you pass in an argument. I do need to improve the output of the command since it outputs raw git right now, but at least it’s functional. See the demo below."}, {"post_id": 14392, "ts": "2026-06-23T14:41:51Z", "hours": 6.9436, "text": "Spent a bit longer between devlogs this time, but it was worth it. So I realized the error messages were really bad. I was pretty much just passing errors up the call stack without adding any context, which isn’t great since it means our error messages will be useless to people reading them I therefore went through every single file of the codebase and wrote good error messages which add a bit of context every time we pass it up the call stack. I also did a bit of refactoring where I thought it would be worth it. For example in the shim module I now set the PE subsystem of the shim binary while it’s in memory instead of writing to disk twice. A few good examples of what the new error messages look like can be seen in the video below."}, {"post_id": 13054, "ts": "2026-06-21T10:47:05Z", "hours": 3.4069, "text": "Shims are simple in concept, complicated in reality. So essentially a shim in mocha is just an executable which calls another executable. It’s similar to a shortcut in that sense, except it shows up in $PATH Thankfully the scoop project already has a repository with 4 different implementations for the shim binary, so I can just have mocha shim download one of those binaries. The complicated part was the PE Subsystem. The PE subsystem is basically a bit of info in each binary which tells Windows whether it’s a console application, or a GUI application. We need to set the PE subsystem of the shim exe to the PE subsystem of the binary we are calling for Windows to execute the binary properly. Hence I need to read and write raw binary data. All of this is just the implementation for exe shims. Scoop itself contains implementations for .bat/.cmd , .ps1 , .jar , .py and linux binaries , all of which have wildly different implementations compared to .exe shims. The video below shows the working set of mocha shim commands (those being add , remove and list )."}, {"post_id": 12032, "ts": "2026-06-19T16:57:37Z", "hours": 1.8778, "text": "mocha cache is a simple command. It shows you what files are currently in $MOCHA_DIR/cache directory and it clears them out. One thing I noticed was that scoop cache show actually displays raw bytes instead of human readable file sizes for each cache entry, which is a bit odd since the total they display is human readable. Therefore I made my implementation mocha cache list display human readable sizes since that’s a more reasonable default."}, {"post_id": 11234, "ts": "2026-06-18T11:50:44Z", "hours": 2.2589, "text": "Fuzzy search is really really good. While implementing mocha search I noticed the results returned by scoop search were in alphabetical order, which doesn’t make a lot of sense. If I do scoop search git the first result should probably be git As a result my implementation of search uses github.com/sahilm/fuzzy which is a small library which provides a fuzzy search implementation. Scoop also checks for binary name matches, e.g. package biodiff can provide a binary called git-biodiff and show up in search results. I decided to remove this for now, since I personally find it a bit unnecessary. scoop search also lists all search results, which is okay when results are sorted alphabetically but doesn’t make sense when searches are relevance based. Therefore, by default mocha search will list exact matches plus the 20 most relevant search results. This can be overridden by the --count argument, where setting it to 0 displays all results. A demonstration of mocha search vs scoop search can be seen in the video below."}, {"post_id": 10748, "ts": "2026-06-17T17:14:41Z", "hours": 2.1597, "text": "I finished up mocha download , which surprisingly does a bit more than simply downloading files. The first thing it does is well… download the file. This is a bit more complicated than it seems though, since we need to identify the right file to download based on cpu architecture. Hence the very cursed JSON parsing I had to create. After downloading a file, we also do a hash check. We support the 4 types of file hashes which scoop support, those being sha256 , sha512 , md5 and sha1 . Currently files get downloaded to the $MOCHA_DIR/cache directory like in scoop, however we don’t actually check if there’s anything cached which can lead to repeated downloads. That’s something I’ll need to fix later on"}, {"post_id": 10131, "ts": "2026-06-16T18:54:22Z", "hours": 1.4081, "text": "I was working on the mocha download command so I can sort out fetching files, and during it I realized my current app format makes things a bit weird. mocha cat previously took in a flag for bucket through -b and a name. Scoop on the other hand uses an application reference in the format bucket/name@version . Scoop’s format is really important for downloads and installs, so it didn’t make sense to not standardize it between mocha download and mocha cat . Hence this shorter devlog! See the video below for the new usage (version numbers are ignored for mocha cat )."}, {"post_id": 10004, "ts": "2026-06-16T15:21:57Z", "hours": 2.9753, "text": "I did a bit of refactoring to split the core functionality from the command files. This means that the code for downloading and deleting buckets is separated from the code for the various commands. I’m doing this primarily for better code organization, and also to prevent import cycles. I also finished up the config system I mentioned last time. It’ll be one of the bigger improvements over scoop, which has a basic set of configuration options. TOML was the obvious choice for the config format since it is really easy to read and write. I made sure that you can put it in any of the standard locations, such as %APPDATA% and .config or in $MOCHA_DIR . Running mocha config will open the configuration in your preferred app, and also generate the default config if a configuration hasn’t been detected in any of the valid locations. Currently the configuration can be used to make mocha cat run an external program for printing manifests to stdout . See the video below for an example using bat"}, {"post_id": 8826, "ts": "2026-06-14T17:52:54Z", "hours": 2.6147, "text": "So this is a spot where I think the improvements over scoop start becoming really apparent. The scoop cat command simply prints an app’s manifest to console. However due to the long startup time of PowerShell scripts (scoop is written in PowerShell) basic stuff like scoop cat takes a second. mocha cat on the other hand is nearly instantaneous since it’s a compiled binary with almost 0 startup time. You can see how this plays out in real usage in the video below. I also half baked a config system, but it’s not finished so I’ll talk about that in the next devlog."}, {"post_id": 8586, "ts": "2026-06-14T08:48:35Z", "hours": 2.85, "text": "I finished off the remaining mocha bucket subcommands, those being add , rm and list . These commands manage “buckets” which are pretty much just package sources. mocha bucket add uses git to clone the relevant bucket into the [MOCHA_DIR]/buckets directory. By default MOCHA_DIR is [USER]/mocha mocha bucket list simply loops over the [MOCHA_DIR]/buckets directory and gets relevant info for each bucket. mocha bucket rm removes a bucket by just deleting the folder containing the bucket. For example, removing the main bucket deletes [MOCHA_DIR]/buckets/main"}, {"post_id": 8208, "ts": "2026-06-13T17:32:25Z", "hours": 2.0261, "text": "I started off with something a bit simple: mocha bucket known The known bucket list in scoop is a list of buckets which are known by the package manager in advance. These buckets don’t require the full URL to be used when using scoop bucket sub-commands. For example instead of running scoop bucket add https://github.com/ScoopInstaller/Main you can instead run scoop bucket add main As seen in the video below, mocha bucket known doesn’t do much. First it downloads buckets.json if it doesn’t exist. Then it parses the json and outputs it to console."}]...
|
Title: mocha by @Glitchy | Stardance
Devlogs:
I s Title: mocha by @Glitchy | Stardance
Devlogs:
I started off with something a bit simple: mocha bucket known The known bucket list in scoop is a list of buckets which are known by the package manager in advance. These buckets don’t require the full URL to be used when using scoop bucket sub-commands. For example instead of running scoop bucket add https://github.com/ScoopInstaller/Main you can instead run scoop bucket add main As seen in the video below, mocha bucket known doesn’t do much. First it downloads buckets.json if it doesn’t exist. Then it parses the json and outputs it to console.
I finished off the remaining mocha bucket subcommands, those being add , rm and list . These commands manage “buckets” which are pretty much just package sources. mocha bucket add uses git to clone the relevant bucket into the [MOCHA_DIR]/buckets directory. By default MOCHA_DIR is [USER]/mocha mocha bucket list simply loops over the [MOCHA_DIR]/buckets directory and gets relevant info for each bucket. mocha bucket rm removes a bucket by just deleting the folder containing the bucket. For example, removing the main bucket deletes [MOCHA_DIR]/buckets/main
So this is a spot where I think the improvements over scoop start becoming really apparent. The scoop cat command simply prints an app’s manifest to console. However due to the long startup time of PowerShell scripts (scoop is written in PowerShell) basic stuff like scoop cat takes a second. mocha cat on the other hand is nearly instantaneous since it’s a compiled binary with almost 0 startup time. You can see how this plays out in real usage in the video below. I also half baked a config system, but it’s not finished so I’ll talk about that in the next devlog.
I did a bit of refactoring to split the core functionality from the command files. This means that the code for downloading and deleting buckets is separated from the code for the various commands. I’m doing this primarily for better code organization, and also to prevent import cycles. I also finished up the config system I mentioned last time. It’ll be one of the bigger improvements over scoop, which has a basic set of configuration options. TOML was the obvious choice for the config format since it is really easy to read and write. I made sure that you can put it in any of the standard locations, such as %APPDATA% and .config or in $MOCHA_DIR . Running mocha config will open the configuration in your preferred app, and also generate the default config if a configuration hasn’t been detected in any of the valid locations. Currently the configuration can be used to make mocha cat run an external program for printing manifests to stdout . See the video below for an example using bat
I was working on the mocha download command so I can sort out fetching files, and during it I realized my current app format makes things a bit weird. mocha cat previously took in a flag for bucket through -b and a name. Scoop on the other hand uses an application reference in the format bucket/name@version . Scoop’s format is really important for downloads and installs, so it didn’t make sense to not standardize it between mocha download and mocha cat . Hence this shorter devlog! See the video below for the new usage (version numbers are ignored for mocha cat ).
I finished up mocha download , which surprisingly does a bit more than simply downloading files. The first thing it does is well… download the file. This is a bit more complicated than it seems though, since we need to identify the right file to download based on cpu architecture. Hence the very cursed JSON parsing I had to create. After downloading a file, we also do a hash check. We support the 4 types of file hashes which scoop support, those being sha256 , sha512 , md5 and sha1 . Currently files get downloaded to the $MOCHA_DIR/cache directory like in scoop, however we don’t actually check if there’s anything cached which can lead to repeated downloads. That’s something I’ll need to fix later on
Fuzzy search is really really good. While implementing mocha search I noticed the results returned by scoop search were in alphabetical order, which doesn’t make a lot of sense. If I do scoop search git the first result should probably be git As a result my implementation of search uses github.com/sahilm/fuzzy which is a small library which provides a fuzzy search implementation. Scoop also checks for binary name matches, e.g. package biodiff can provide a binary called git-biodiff and show up in search results. I decided to remove this for now, since I personally find it a bit unnecessary. scoop search also lists all search results, which is okay when results are sorted alphabetically but doesn’t make sense when searches are relevance based. Therefore, by default mocha search will list exact matches plus the 20 most relevant search results. This can be overridden by the --count argument, where setting it to 0 displays all results. A demonstration of mocha search vs scoop search can be seen in the video below.
mocha cache is a simple command. It shows you what files are currently in $MOCHA_DIR/cache directory and it clears them out. One thing I noticed was that scoop cache show actually displays raw bytes instead of human readable file sizes for each cache entry, which is a bit odd since the total they display is human readable. Therefore I made my implementation mocha cache list display human readable sizes since that’s a more reasonable default.
Shims are simple in concept, complicated in reality. So essentially a shim in mocha is just an executable which calls another executable. It’s similar to a shortcut in that sense, except it shows up in $PATH Thankfully the scoop project already has a repository with 4 different implementations for the shim binary, so I can just have mocha shim download one of those binaries. The complicated part was the PE Subsystem. The PE subsystem is basically a bit of info in each binary which tells Windows whether it’s a console application, or a GUI application. We need to set the PE subsystem of the shim exe to the PE subsystem of the binary we are calling for Windows to execute the binary properly. Hence I need to read and write raw binary data. All of this is just the implementation for exe shims. Scoop itself contains implementations for .bat/.cmd , .ps1 , .jar , .py and linux binaries , all of which have wildly different implementations compared to .exe shims. The video below shows the working set of mocha shim commands (those being add , remove and list ).
Spent a bit longer between devlogs this time, but it was worth it. So I realized the error messages were really bad. I was pretty much just passing errors up the call stack without adding any context, which isn’t great since it means our error messages will be useless to people reading them I therefore went through every single file of the codebase and wrote good error messages which add a bit of context every time we pass it up the call stack. I also did a bit of refactoring where I thought it would be worth it. For example in the shim module I now set the PE subsystem of the shim binary while it’s in memory instead of writing to disk twice. A few good examples of what the new error messages look like can be seen in the video below.
mocha update is another command which does very little but is very important. All it does is update the known_buckets file, and run git pull on all added buckets to update them. It can also update just the buckets you specify if you pass in an argument. I do need to improve the output of the command since it outputs raw git right now, but at least it’s functional. See the demo below.
Huge milestone!!! I’ve gotten mocha install working for very basic apps! This means the entire process of downloading a file, then extracting it, then creating a junction and finally creating a shim now works for basic pieces of software! So in terms of what I actually did this devlog, I added cache hits to the download command since it’s relevant to the install command. I then implemented the aforementioned .zip extraction and junction creation. Then all that was left was a bit of orchestration, getting everything to work together properly. See a working install of innounp using mocha install below!
Before working on more features and expanding the amount of apps mocha actually supports I wanted to go through the codebase and do a lot of cleanup since the codebase is quite messy. There are silly mistakes in some files and bad implementations in others. Hence the time I spent during this period was focused on moving code to where it should be and cleaning up some edge cases, specifically related to the bucket , config and shim modules. A good example of this is moving the code to get the active config to the config module instead of leaving it in main.go . Next up will be refactoring the commands , fileops , and manifest modules. I don’t have much to show so I figured I would present a feature I added but didn’t show earlier: the ability to skip cache hits with the --force flag when installing or downloading an app. Some context I forgot to add initially: I renamed the app module to manifest since I felt it was more accurate to what it actually handles scope wise.
Finished up the code cleanup in commands , fileops and manifests . I did catch a few edge cases and some incorrect behavior in the process, which is why I always spend so much time reviewing code. I did use AI to assist with code review because I think it’s an area where AI shines. AI is really good at finding small errors or inconsistencies in the codebase which I probably wouldn’t notice. For example, it identified that the ManifestReferences argument was not a required argument for the download command, which meant no help message was displayed on incorrect usage like the other commands. One big thing I will work on eventually is console output. Right now errors are well formatted but a lot of the time commands just run stuff without providing a lot of insight into what actions they are taking which isn’t great. Even the help menu is pretty useless right now (see the image below). Extra context: A manifest reference is a pointer to an app (e.g. main/ [email protected] )
So I added support for more apps by implementing more extractors. This means in theory any apps which don’t need a pre-install or post-install should work. To be more specific, I handle a few more properties on manifests. Those being extract_dir and innosetup , which inform how an app needs to be installed. I also implement 7zip and innounp as extractors to support more file formats which applications are distributed in. Of course there’s still a lot of work before I consider this ready for public use. I need to create commands for some basic operations like uninstalling, updating and listing apps. I also need to handle shortcuts otherwise GUI apps can’t be accessed from the start menu. Besides that I need to improve the user experience. As you can see in the video below mocha just sort of dumps everything to the console even if it’s not relevant. Help menus are also critical to get working properly.
I finished up mocha uninstall and mocha list , which means you can actually manage installed apps instead of manually deleting them. There’s not much that goes into mocha uninstall . You just need to remove the relevant shims and app directories since the apps that mocha supports are all portable. mocha list is similarly simple. It’s just loops over the directories in $MOCHA_DIR/apps and looks for apps along with the versions installed for each app.
Typically I don’t want to make devlogs for small stuff like this, but this is something I found really cool. So I was working on help messages for all the commands when I realized that mocha bucket list felt a bit slower than pretty much every other command. This is because we need to shell out to git 2 times per bucket, and I had 4 buckets added. While 8 git commands might not sound like a lot, it was enough to make mocha bucket list feel slow. So what I did is I parallelized the metadata fetching through an errgroup . Instead of fetching the metadata for each bucket in order, we fetch the metadata for all 4 buckets simultaneously. This led to a big performance uplift. About 3 times faster than the old version of mocha , and just over 12 times faster than scoop for this operation. See the video below.
As I mentioned in the previous devlog I added good help information to every bit of the CLI. It’s surprisingly difficult to write good help messages which explains everything to users in a few words I also changed the behaviour of the mocha cache clear command to not clear all cache by default. That’s now gated behind the --all flag in order to match scoop a bit more
We now create shortcuts! This means any GUI apps should show up properly in the start menu, just like they do when you install with scoop . All I really had to do was a bit of orchestration since I decided to vendor in an implementation from https://github.com/jxeng/shortcut Besides that I expanded the number of apps that are supported by implementing a bit of code that handle architecture specific bin fields, along with bin fields which store 2D arrays. I also cleared up some of the TODO items. I swapped the junction implementation to an implementation from https://github.com/nyaosorg/go-windows-junction since we were previously shelling out to CLI. That and I added a bit more zip bomb protection For the purposes of the video below I changed the location which shortcuts get put to my desktop. It’ll probably be configurable, and match scoop by putting shortcuts in the startup menu by default
This is going to be the equivalent of 2 devlogs since I thought I made one earlier for persists but I didn’t. New feature! We now handle persist items in order to store data between versions. These are files which are persisted between versions of an app. Lets take git as an example to explain why persist exists. Say you want to make sure your git config isn’t deleted every time you update. The issue with this is that the config file is saved in the version specfic directory. To resolve this we can keep the config in $MOCHA_DIR/persist and then symlink the config to where it needs to be, which is essentially what persist tells us to do. Since we handled persist items last time we can now implement mocha upgrade to update apps. The way scoop handles updates is by first removing anything that references the app, like shortcuts or shims . Then we just follow the install process from scratch. This leaves the old version available in case a user wants to revert versions due to a bug, while also updating to the latest available version. This can be seen in the video below, which shows me updating llama.cpp-hip-radeon .
So I’ve been doing a bit of refactoring, a bit of bug fixing and a bit of optimization. Essentially just polishing mocha before I work on the next feature. Here’s some of the stuff I did: created tests for ParseRefString to validate behavior cache manifest json between info calls since I/O is really slow bumped dependency versions refactored manifest/info.go Besides that I fixed the uninstall flow since it was really bugged after the latest changes. Essentially mocha would uninstall apps with incorrect info. It would also try to remove shims/shortcuts for apps which don’t have any active shims/shortcuts. I then added a bit of logging since the uninstall command didn’t give any user output for whatever reason (i forgot to earlier).
mocha now supports a user defined theme for output colors. In the process I ended up doing a lot of stuff related to the config. First thing I did was swap to fatih/color for colored output, since it handles stuff like colors in command prompt and removing color when output is piped. Then I refactored the config module. Earlier I would pass around a MochaConfiguration object through every function. Now I use a config singleton that’s accessible from any function. Why? Because it means I don’t need to pass the object every time I want to log information. Also means I don’t need to pass mochaDir through almost every function in the codebase. Getting user defined themes was a bit complicated because I needed a good way to handle a default theme so output doesn’t look bad if parsing fails. I handled this by only using the configured theme if every color resolves properly. Otherwise output falls back to the already loaded default theme. Due to this you still get colored output even if there are errors or warning before the configuration and theme is loaded.
I love refactoring!!!! I’ll probably end up spending another 20 hours just on refactoring because it’s so fun!!!! This time around I wanted to refactor the code so that our commands orchestrate stuff instead of the helper functions. For example, pkg.Install would first download a package, then install it, and then link it through shims and shortcuts all by itself. This causes issues because it means error messages become slightly worse, and it creates a class of bugs due to edge cases where we don’t necessarily want this order of orchestration. Hence I did a lot of refactoring in the pkg module. I also ended up adding a way to skip verification of downloads when downloading, installing or updating a package through --skip-verify . It’s a useful option in situations where there is a malformed manifest or simply no hash to begin with.
I’m writing this one right before F1 Qualifying at Spa! Continuing with the trend of some of my recent work, I improved what table outputs look like to be a little bit more readable. We now use proper separators in the form of Unicode Box Drawing Characters . I also made column alignment configurable, which improves legibility for some commands like mocha bucket list and mocha cache show . I’ve attached an image of the scoop and mocha versions of bucket list so you can compare for yourself.
Not sure why I didn’t do this earlier, but I’ve added success messages to commands where it makes sense. Also added a success color to the config so you can change what the success color is. I do still need to improve CLI output quite a bit, but it’s slowly getting there.
My summer break has ended so development is going to be a lot slower from now. I added mocha outdated so you can list outdated apps before upgrading them to a newer version. Besides that I tweaked a lot of stuff related to CLI output. For example I changed search to output one table, and simply outputting exact matches at the top of that table. I also changed a lot of messages which were using LogOutput to LogInfo so they use the correct color and output to stderr and not stdout .
Finally got a bit of time to do a bit of development. First thing I did was remove a field from install.json to match scoop . This means that mocha should be a drop in replacement for existing scoop installs. Then I added partial support for env_set and env_add_path . The main thing I need to do to complete the feature is parse variables and replace them with the appropriate paths. These 2 fields are some of the last manifest fields I need to support besides pre/post (un)install hooks.
Lot of time going into this devlog, but it makes sense since I did do a lot. I did this sweeping refactor of the entire commands module which moved around a lot of code. Essentially each command now gets it’s own directory under the commands module that represents it’s children/parents. For example commands/shim/remove/cmd.go contains code for the mocha shim remove command. Each cmd.go contains a Command struct that has the relevant fields and functions attached to it. This structure just makes things more organized and also means adding test files will be a bit easier since functionality is now isolated. I also sorted out the shim binary. So essentially https://github.com/ScoopInstaller/Shim offers different version of the shim binary which can be installed. Previously I hard coded the code to install cpp v0.1.0 but now users can run mocha shim binary releases to see the options and mocha shim binary setup to install their chosen binary. This also means we actually get the latest releases from GitHub.
Lots of small bug fixes and changes, I’ll just list them out: feat(cmd): allow removal of multiple shims in one execution (f2fae3f) fix(manifest): correctly ignore invalid shortcut entries (6a08478) fix(fileops): use correct registry type (5d5d796) fix(config): seed config with defaults (9dfaaff) fix(cmd): use correct release sources (a2a9ba1) fix(cmd): use bucket from install info (5a9109b) I also added support for more file types being shimmed, which helps a lot with compatibility. The file types are .py , .bat , .cmd , .jar and .ps1 .
I forgot to make a devlog in between so this will be like 2 bigger devlogs. I parallelized bucket updates, which speeds it up quite a bit. This also allowed me to try out parallelism even more, which I plan to apply throughout the CLI later on. I also added configuration options for the runners which mocha shim will use to run certain file types. For example, you can set the python-runner to select the python version that’ll be used to run python scripts that are shimmed. Downloads now have a progress bar, so you don’t need to wonder whether something is happening or not during a long download. Finally env_set is fully supported since I added the relevant variable parsing. This was pretty much just me cleaning out the TODO list before I ship. I also did a lot of smaller bug fixes and refactors as seen below. fix(commands): prevent app installation if already installed (cb27d07) fix(commands): fix config opening with “start” (74f3679) fix(commands): correctly handle non-apps when upgrading (f7419f6) fix: make LogOutput go to Stdout not Stderr (bc10357) fix: handle empty versions correctly (2287da9) fix(pkg): remove correct temp dir (33189b6) fix(shim): warn for unknown shim extension (622c2b4) fix: skip downloads with no hash by default (69d4e35) fix: use correct timeout for downloads (44e527b) fix: drop unnecessary return value from GetExecutableEntries (9fd845c) fix(config): remove unused option (1339971) fix(commands): don’t error for valid results (87c4d6c) refactor(config): rename variables/functions (f253d9d) fix: use unique temp directories (a159e23) refactor: use fmt.Fprintln directly (d2d54bf)
So I wrote a README, added a license (MIT of course) and setup CI/CD so that releases are automatically built and deployed. Honestly I forgot how hard it is to write a good README. You need to get a lot of information through without it looking like a wall of text.
Ships:
I made a package manager for Windows, which is somewhat backwards compatible with scoop packages. To be honest there’s still a lot of work that I want to do, but I have exams and college application coming up soon so I can’t. That’s not to say I’m not happy with the state of the ship. At the very least it has all the core features that a package manager should have, but there are still a lot of bugs which is why this is only v0.0.1. The biggest challenge by far was trying to figure out how Scoop does things internally. A lot of stuff just doesn’t have documentation, so you have to dig through the really messy PowerShell source code....
|
1793674540.6252565
|
1793760940.6252565
|
|
16572
|
My very own WebOS by @virajmoharle | Stardance
|
virajmoharle
|
0
|
3.35
|
0
|
[]
|
[{"post_id": 10846, "ts": "202 [{"post_id": 10846, "ts": "2026-06-17T19:52:14Z", "hours": 3.3522, "text": "had trouble making a url for my website. If anyone knows please help. Getting closer to finishing this project."}]...
|
Title: My very own WebOS by @virajmoharle | Starda Title: My very own WebOS by @virajmoharle | Stardance
Devlogs:
had trouble making a url for my website. If anyone knows please help. Getting closer to finishing this project....
|
1793526544.134848
|
1794131344.134848
|
|
16573
|
passive buzzer by @Abbas | Stardance
|
Abbas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: passive buzzer by @Abbas | Stardance
|
1793282209.3143995
|
1793887009.3143995
|
|
16574
|
My very own WebOS by @AxelC | Stardance
|
AxelC
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @AxelC | Stardance
|
1793476405.074739
|
1794081205.074739
|
|
16575
|
My awesome macropad! by @Dafni | Stardance
|
Dafni
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Dafni | Stardance
|
1793407629.2736406
|
1794012429.2736406
|
|
16576
|
Frictionless by @Sharkle | Stardance
|
Sharkle
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @Sharkle | Stardance
|
1793778879.4997213
|
1794383679.4997213
|
|
16577
|
My awesome macropad! by @shagunmishra998 | Stardan My awesome macropad! by @shagunmishra998 | Stardance...
|
shagunmishra998
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @shagunmishra998 | Title: My awesome macropad! by @shagunmishra998 | Stardance...
|
1793458089.9158392
|
1794062889.9158392
|
|
16578
|
My first slack bot! by @xXArtemisXx | Stardance
|
xXArtemisXx
|
0
|
0.27
|
0
|
[]
|
[{"post_id": 6903, "ts": "2026 [{"post_id": 6903, "ts": "2026-06-11T15:58:48Z", "hours": 0.2714, "text": "Hi! I’m new to coding and I’m trying to figure out how to create a slackbot. For some reason the commands aren’t working and I’m not sure how to fix them. I did everything according to the instructions. Does anyone know a potential reason why it’s not working?"}]...
|
Title: My first slack bot! by @xXArtemisXx | Stard Title: My first slack bot! by @xXArtemisXx | Stardance
Devlogs:
Hi! I’m new to coding and I’m trying to figure out how to create a slackbot. For some reason the commands aren’t working and I’m not sure how to fix them. I did everything according to the instructions. Does anyone know a potential reason why it’s not working?...
|
1793228058.1988902
|
1793832858.1988902
|
|
16579
|
My awesome macropad! by @Don | Stardance
|
Don
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Don | Stardance
|
1793530166.3801606
|
1794134966.3801606
|
|
16580
|
HoneyGuard by @Chiragb | Stardance
|
Chiragb
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: HoneyGuard by @Chiragb | Stardance
|
1793400901.0452116
|
1794005701.0452116
|
|
16581
|
macropad :3 by @goob_erm | Stardance
|
goob_erm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: macropad :3 by @goob_erm | Stardance
|
1793465577.0148342
|
1794070377.0148342
|
|
16582
|
Starry Eyes by @tamyy | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Starry Eyes by @tamyy | Stardance
|
1793479792.5029883
|
1794084592.5029883
|
|
16583
|
Frictionless by @avraham | Stardance
|
avraham
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @avraham | Stardance
|
1793447260.485308
|
1794052060.485308
|
|
16584
|
My first slack bot! by @doominik | Stardance
|
doominik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @doominik | Stardanc Title: My first slack bot! by @doominik | Stardance...
|
1793213553.8283474
|
1793818353.8283474
|
|
16585
|
My first slack bot! by @avraham | Stardance
|
avraham
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @avraham | Stardance
|
1793238617.2262106
|
1793843417.2262106
|
|
16586
|
My very own WebOS by @Marvino | Stardance
|
Marvino
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Marvino | Stardance
|
1793206115.6276543
|
1793810915.6276543
|
|
16587
|
Ineluctabilis by @BelalElenbabi1 | Stardance
|
BelalElenbabi1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ineluctabilis by @BelalElenbabi1 | Stardanc Title: Ineluctabilis by @BelalElenbabi1 | Stardance...
|
1793512144.2940984
|
1794116944.2940984
|
|
16588
|
Untitled project by @Akshara_Raj | Stardance
|
Akshara_Raj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Akshara_Raj | Stardanc Title: Untitled project by @Akshara_Raj | Stardance...
|
1793191751.9860253
|
1793796551.9860253
|
|
16589
|
My awesome macropad! by @BlackyCool | Stardance
|
BlackyCool
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @BlackyCool | Stard Title: My awesome macropad! by @BlackyCool | Stardance...
|
1793238708.3338735
|
1793843508.3338735
|
|
16590
|
StartupOS Backend API by @to_aarav_g | Stardance
|
to_aarav_g
|
1
|
14.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-27T15:11:20Z", "hours": 14.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "🚀 Shipped a major update to StartupOS Backend ! After weeks of debugging, refactoring, and production testing, the backend powering StartupOS is now production-ready. What shipped: ✅ Authentication with session persistence ✅ AI provider router with automatic failover ✅ Blueprint generation APIs ✅ Website generation APIs ✅ Competitor intelligence APIs ✅ Daily founder briefs ✅ Dashboard APIs ✅ Production-grade error handling and logging ✅ Railway deployment with PostgreSQL + Prisma ✅ Full end-to-end testing Tech Stack ⚡ Fastify ⚡ TypeScript ⚡ Prisma ORM ⚡ PostgreSQL ⚡ Railway ⚡ Docker StartupOS Backend now reliably powers the entire founder journey—from startup idea to launch-ready business. Built with lots of coffee, debugging, and persistence ☕🚀 #HackClub #Stardance #Backend #Fastify #TypeScript #Prisma #PostgreSQL #AI", "repo": "", "demo": ""}]...
|
[{"post_id": 16111, "ts": "202 [{"post_id": 16111, "ts": "2026-06-26T06:20:22Z", "hours": 8.2789, "text": "🚀 Shipped a major milestone for StartupOS Backend today!StartupOS Backend powers the entire StartupOS platform — an AI startup copilot that helps founders go from idea → blueprint → launch.What I worked on:✅ Fixed production deployment issues on Railway✅ Added robust AI provider failover across multiple providers✅ Implemented persistent website generation and retrieval APIs✅ Added competitor intelligence and daily brief endpoints✅ Improved error handling and graceful fallbacks across services✅ Fixed authentication/session issues and added token refresh support✅ Added production logging and route debugging utilities✅ Removed Redis dependency from critical flows to improve reliability✅ Performed full end-to-end QA on productionTech Stack:FastifyTypeScriptPrisma ORMPostgreSQLRailwayDockerMulti-provider AI Router (Gemini, Groq, OpenRouter, NIM)Current Status:🎉 Backend is now production-ready for beta users.All core flows are working:AuthenticationStartup creationBlueprint generationWebsite generationCompetitor intelligenceDaily briefsDashboard APIsReady for real user testing 🚀#Stardance #HackClub #TypeScript #Fastify #Prisma #PostgreSQL #AI #WebDev #StartupOS"}, {"post_id": 11967, "ts": "2026-06-19T15:09:48Z", "hours": 5.2864, "text": "🚀 Big StartupOS milestone today!After rebuilding the backend and fixing countless issues, StartupOS can now:✅ Generate startup blueprints✅ Generate actual multi-page websites with AI✅ Validate the generated HTML✅ Deploy websites to VercelThe journey now looks like:Idea → Blueprint → Website → Deploy → Public URLFeels amazing seeing StartupOS go from generating plans to generating real websites. 🎉Hours today: 5"}]...
|
Title: StartupOS Backend API by @to_aarav_g | Star Title: StartupOS Backend API by @to_aarav_g | Stardance
Devlogs:
🚀 Big StartupOS milestone today!After rebuilding the backend and fixing countless issues, StartupOS can now:✅ Generate startup blueprints✅ Generate actual multi-page websites with AI✅ Validate the generated HTML✅ Deploy websites to VercelThe journey now looks like:Idea → Blueprint → Website → Deploy → Public URLFeels amazing seeing StartupOS go from generating plans to generating real websites. 🎉Hours today: 5
🚀 Shipped a major milestone for StartupOS Backend today!StartupOS Backend powers the entire StartupOS platform — an AI startup copilot that helps founders go from idea → blueprint → launch.What I worked on:✅ Fixed production deployment issues on Railway✅ Added robust AI provider failover across multiple providers✅ Implemented persistent website generation and retrieval APIs✅ Added competitor intelligence and daily brief endpoints✅ Improved error handling and graceful fallbacks across services✅ Fixed authentication/session issues and added token refresh support✅ Added production logging and route debugging utilities✅ Removed Redis dependency from critical flows to improve reliability✅ Performed full end-to-end QA on productionTech Stack:FastifyTypeScriptPrisma ORMPostgreSQLRailwayDockerMulti-provider AI Router (Gemini, Groq, OpenRouter, NIM)Current Status:🎉 Backend is now production-ready for beta users.All core flows are working:AuthenticationStartup creationBlueprint generationWebsite generationCompetitor intelligenceDaily briefsDashboard APIsReady for real user testing 🚀#Stardance #HackClub #TypeScript #Fastify #Prisma #PostgreSQL #AI #WebDev #StartupOS
Ships:
🚀 Shipped a major update to StartupOS Backend ! After weeks of debugging, refactoring, and production testing, the backend powering StartupOS is now production-ready. What shipped: ✅ Authentication with session persistence ✅ AI provider router with automatic failover ✅ Blueprint generation APIs ✅ Website generation APIs ✅ Competitor intelligence APIs ✅ Daily founder briefs ✅ Dashboard APIs ✅ Production-grade error handling and logging ✅ Railway deployment with PostgreSQL + Prisma ✅ Full end-to-end testing Tech Stack ⚡ Fastify ⚡ TypeScript ⚡ Prisma ORM ⚡ PostgreSQL ⚡ Railway ⚡ Docker StartupOS Backend now reliably powers the entire founder journey—from startup idea to launch-ready business. Built with lots of coffee, debugging, and persistence ☕🚀 #HackClub #Stardance #Backend #Fastify #TypeScript #Prisma #PostgreSQL #AI...
|
1793775493.3423178
|
1793861893.3423178
|
|
16591
|
PromptCraft by @shahid007 | Stardance
|
shahid007
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: PromptCraft by @shahid007 | Stardance
|
1793231607.5303037
|
1793836407.5303037
|
|
16592
|
My awesome macropad! by @Ramcharan | Stardance
|
Ramcharan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Ramcharan | Starda Title: My awesome macropad! by @Ramcharan | Stardance...
|
1793782564.8744965
|
1794387364.8744965
|
|
16593
|
cross wind auto correction system by @abdullah_alo cross wind auto correction system by @abdullah_alomar | Stardance...
|
abdullah_alomar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: cross wind auto correction system by @abdul Title: cross wind auto correction system by @abdullah_alomar | Stardance...
|
1793444153.022484
|
1794048953.022484
|
|
16594
|
Untitled by @Mebelikewenm | Stardance
|
Mebelikewenm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Mebelikewenm | Stardance
|
1793271000.1406279
|
1793875800.1406279
|
|
16595
|
StarOS by @Alafandri | Stardance
|
Alafandri
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-15T20:15:59Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a webOS that is very magical and really cool! It wasn’t that challenging to make but I obviously ran into small problems that I was able to very quickly fix. I am proud of the final result cause the design and look of it turned out to be better than I expected. What people should know when they test the project is that I hope you enjoy what I have made!", "repo": "https://github.com/Alafandri/StarOS", "demo": "https://alafandri.github.io/StarOS/"}]...
|
[{"post_id": 7110, "ts": "2026 [{"post_id": 7110, "ts": "2026-06-11T21:36:35Z", "hours": 0.2611, "text": "Devlog 3 version 1.0 StarOS is ready!! yipeeee. I am so excited to make it public for all of you. I had a lot of fun making it and I hope you have fun using it. I know that there isn’t that much to do there yet but I will definetly update it after I finish my next project."}, {"post_id": 7091, "ts": "2026-06-11T21:19:04Z", "hours": 0.2958, "text": "Devlog 2 StarOS v0.5 StarOS is almost done! I have one more app planned to add into it and after that I am planning on publishing it!"}, {"post_id": 7073, "ts": "2026-06-11T20:59:11Z", "hours": 1.4842, "text": "Devlog 1 StarOS v0.00001.1 Hello there everyone! This is my very first devlog here and it is about StarOS for which I have just completed all of the basic stuff for it to function. Next I plan on making the OS look more cleaner and prettier! See you soon!"}]...
|
Title: StarOS by @Alafandri | Stardance
Devlogs:
Title: StarOS by @Alafandri | Stardance
Devlogs:
Devlog 1 StarOS v0.00001.1 Hello there everyone! This is my very first devlog here and it is about StarOS for which I have just completed all of the basic stuff for it to function. Next I plan on making the OS look more cleaner and prettier! See you soon!
Devlog 2 StarOS v0.5 StarOS is almost done! I have one more app planned to add into it and after that I am planning on publishing it!
Devlog 3 version 1.0 StarOS is ready!! yipeeee. I am so excited to make it public for all of you. I had a lot of fun making it and I hope you have fun using it. I know that there isn’t that much to do there yet but I will definetly update it after I finish my next project.
Ships:
I made a webOS that is very magical and really cool! It wasn’t that challenging to make but I obviously ran into small problems that I was able to very quickly fix. I am proud of the final result cause the design and look of it turned out to be better than I expected. What people should know when they test the project is that I hope you enjoy what I have made!...
|
1793728550.6308258
|
1793814950.6308258
|
|
16596
|
My very own WebOS by @MehranFaisal | Stardance
|
MehranFaisal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @MehranFaisal | Starda Title: My very own WebOS by @MehranFaisal | Stardance...
|
1793512125.3914468
|
1794116925.3914468
|
|
16597
|
My first slack bot! by @Dija | Stardance
|
Dija
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Dija | Stardance
|
1793195612.1178806
|
1793800412.1178806
|
|
16598
|
The snitch! by @tatva | Stardance
|
tatva
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The snitch! by @tatva | Stardance
|
1793400588.5550938
|
1794005388.5550938
|
|
16599
|
My very own WebOS by @Bj | Stardance
|
Bj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Bj | Stardance
|
1793184888.0410154
|
1793789688.0410154
|
|
16600
|
My first slack bot! by @ThaoVi | Stardance
|
ThaoVi
|
0
|
0.36
|
0
|
[]
|
[{"post_id": 7706, "ts": "2026 [{"post_id": 7706, "ts": "2026-06-12T21:19:03Z", "hours": 0.3622, "text": "it’s working!"}]...
|
Title: My first slack bot! by @ThaoVi | Stardance
Title: My first slack bot! by @ThaoVi | Stardance
Devlogs:
it’s working!...
|
1793166902.2511563
|
1793771702.2511563
|