|
5451
|
Chess.com stats slack bot by @marcsello | Stardanc Chess.com stats slack bot by @marcsello | Stardance...
|
marcsello
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-02T22:33:39Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a Slack bot that returns data from the chess.com api. This is my first backend project and it was a lot of fun.", "repo": "https://github.com/MarcselloDev/chesscomstatsslackbot", "demo": "https://hackclub.enterprise.slack.com/archives/C0B7SD8GBTQ"}]...
|
[{"post_id": 1094, "ts": "2026 [{"post_id": 1094, "ts": "2026-06-02T22:26:19Z", "hours": 1.4853, "text": "Created the Slack Bot Commands: /chesscomprofile Displays stats about a user on Chess.com. /chesscomgames Displays the last 3 games of a user on Chess.com in the current month. /chesscompuzzle Returns a link to a random daily puzzle on Chess.com."}]...
|
Title: Chess.com stats slack bot by @marcsello | S Title: Chess.com stats slack bot by @marcsello | Stardance
Devlogs:
Created the Slack Bot Commands: /chesscomprofile Displays stats about a user on Chess.com. /chesscomgames Displays the last 3 games of a user on Chess.com in the current month. /chesscompuzzle Returns a link to a random daily puzzle on Chess.com.
Ships:
I made a Slack bot that returns data from the chess.com api. This is my first backend project and it was a lot of fun....
|
1793879432.1311631
|
1793965832.1311631
|
|
5452
|
My first slack bot! by @llint | Stardance
|
llint
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @llint | Stardance
|
1793552248.6887877
|
1794157048.6887877
|
|
5453
|
Untitled project by @hasib_noori | Stardance
|
hasib_noori
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @hasib_noori | Stardanc Title: Untitled project by @hasib_noori | Stardance...
|
1793465394.3952918
|
1794070194.3952918
|
|
5454
|
Macro pad! by @stephenfromcolorado | Stardance
|
stephenfromcolorado
|
0
|
0.29
|
0
|
[]
|
[{"post_id": 1107, "ts": "2026 [{"post_id": 1107, "ts": "2026-06-02T22:45:16Z", "hours": 0.2878, "text": "I made the pcb for the macro pad ts took like a hour but freeking hacka time is so bad"}]...
|
Title: Macro pad! by @stephenfromcolorado | Starda Title: Macro pad! by @stephenfromcolorado | Stardance
Devlogs:
I made the pcb for the macro pad ts took like a hour but freeking hacka time is so bad...
|
1793404272.8029988
|
1794009072.8029988
|
|
5455
|
Robotic Actuator by @cloudcake8 | Stardance
|
cloudcake8
|
0
|
3.41
|
0
|
[]
|
[{"post_id": 8960, "ts": "2026 [{"post_id": 8960, "ts": "2026-06-14T22:13:58Z", "hours": 1.6961, "text": "finally figured out why my 2 phases werent looking right so the feaaturescript im using to generate the cyclodial profile only generates it with one tooth fully “in”, making it so that if i want another disc exactly 180 degrees out of phase, i need to have an even amount of pins and an odd amount of teeth for it to work so instead of 16:1 i’m running 15:1 and im switching from 2 bearings to 1 pressfit bearing because i thought about it and there really isn’t any thrust forces present in the gearbox so its probably fine, i might add some sort of bearing retainment though just in case, otherwise its just going to be retaining compounded in"}, {"post_id": 8564, "ts": "2026-06-14T07:15:59Z", "hours": 0.8597, "text": "ok so i want to run ball bearings for all of my pins on the cycloid, did some preliminary research and right now with my cycloid disc setup it would have required 196 individual bearings (but i think i can get it down by a lot by narrowing my cyclodial discs) theres a lot im confused about but im working it out slowly, specifically how do i make sure my output shaft is strong enough to support a whole joint"}, {"post_id": 4057, "ts": "2026-06-07T07:29:55Z", "hours": 0.8506, "text": "figuring out what motors and how the structure of the gearbox will look like doing some research on motors, i am choosing the WK8110 frameless outrunner frameless because i want to fit a cyclodial reduction inside of it (mini cheetah style) outrunner because they have more torque (i am trying to target high torque without too much of a reduction ratio so i can have some backdrivability so whatever joint this is on acts as if its connected directly to the motor, hence the “quasi” direct drive) i think i’ll also use some cheap motor controller, most likely a simpleFOC board of some sort (aliexpress clones), because they are super cheap and i think they should be good enough for at least testing on a desk. if i do testing and they explode on me or can’t handle the current or something, i’ll splurge on some vesc based motor controller OR maybe an odrive board (or odrive clone on aliexpress) for the complete robot of whatever i’m making (quadruped?) i’ve found i want to target around ~16:1 for the ratio, because lowkey these motors have like no torque from their spec sheets so i need a higher ratio than ideal (to get all the benefits of “quasi direct drive” its ideal to have a lower ratio so its a more direct connection to the motor kinda), this ratio should get me around 40 ish max nm of torque (woah! lowkey a lot!) so maybe i can do some jumps or something if the robot is light enough not sure about what encoder setup i’ll use, did some digging on amazon for bearings and bushings to support everything, i think i’ll do m4 or m3 sleeve bushings for the outer pins and the inner pins, and some random bearing for the inner eccentric bearing and i’ll support everything with massive bearings so that the outrunner is properly alligned to the stator (need to find 90mm id bearings that arent really expensive, or figure out how to package cheaper smaller bearings to constrain the motor) i just spent a lot of time thinking about how everything will package and rotating around the model to think about it from different angles not sure what material i will do the cycloid discs out of (probably just 6061 alu, laser cut from some online service), and for the enclosure i think i’ll do some nylon composite filament for strength and heat resistance (or maybe just PLA for this prototype) otherwise, i think this session gave me a pretty solid mental image of what the whole actuator will look like and i’m excited to design the rest of it"}]...
|
Title: Robotic Actuator by @cloudcake8 | Stardance Title: Robotic Actuator by @cloudcake8 | Stardance
Devlogs:
figuring out what motors and how the structure of the gearbox will look like doing some research on motors, i am choosing the WK8110 frameless outrunner frameless because i want to fit a cyclodial reduction inside of it (mini cheetah style) outrunner because they have more torque (i am trying to target high torque without too much of a reduction ratio so i can have some backdrivability so whatever joint this is on acts as if its connected directly to the motor, hence the “quasi” direct drive) i think i’ll also use some cheap motor controller, most likely a simpleFOC board of some sort (aliexpress clones), because they are super cheap and i think they should be good enough for at least testing on a desk. if i do testing and they explode on me or can’t handle the current or something, i’ll splurge on some vesc based motor controller OR maybe an odrive board (or odrive clone on aliexpress) for the complete robot of whatever i’m making (quadruped?) i’ve found i want to target around ~16:1 for the ratio, because lowkey these motors have like no torque from their spec sheets so i need a higher ratio than ideal (to get all the benefits of “quasi direct drive” its ideal to have a lower ratio so its a more direct connection to the motor kinda), this ratio should get me around 40 ish max nm of torque (woah! lowkey a lot!) so maybe i can do some jumps or something if the robot is light enough not sure about what encoder setup i’ll use, did some digging on amazon for bearings and bushings to support everything, i think i’ll do m4 or m3 sleeve bushings for the outer pins and the inner pins, and some random bearing for the inner eccentric bearing and i’ll support everything with massive bearings so that the outrunner is properly alligned to the stator (need to find 90mm id bearings that arent really expensive, or figure out how to package cheaper smaller bearings to constrain the motor) i just spent a lot of time thinking about how everything will package and rotating around the model to think about it from different angles not sure what material i will do the cycloid discs out of (probably just 6061 alu, laser cut from some online service), and for the enclosure i think i’ll do some nylon composite filament for strength and heat resistance (or maybe just PLA for this prototype) otherwise, i think this session gave me a pretty solid mental image of what the whole actuator will look like and i’m excited to design the rest of it
ok so i want to run ball bearings for all of my pins on the cycloid, did some preliminary research and right now with my cycloid disc setup it would have required 196 individual bearings (but i think i can get it down by a lot by narrowing my cyclodial discs) theres a lot im confused about but im working it out slowly, specifically how do i make sure my output shaft is strong enough to support a whole joint
finally figured out why my 2 phases werent looking right so the feaaturescript im using to generate the cyclodial profile only generates it with one tooth fully “in”, making it so that if i want another disc exactly 180 degrees out of phase, i need to have an even amount of pins and an odd amount of teeth for it to work so instead of 16:1 i’m running 15:1 and im switching from 2 bearings to 1 pressfit bearing because i thought about it and there really isn’t any thrust forces present in the gearbox so its probably fine, i might add some sort of bearing retainment though just in case, otherwise its just going to be retaining compounded in...
|
1793872039.8604002
|
1794476839.8604002
|
|
5456
|
ATLAS by @Scout | Stardance
|
Scout
|
1
|
1.33
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-08T20:27:31Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "This is ATLAS, a Image search and geo recognition tool that uses VLMs (Visual Language Models) to scan a string of images, guess where they were taken, and supply estimated coordinates. (As said in my Dev log the coordinates may be off wildly, this is a known issue being worked on currently) The code is being worked on every week and major updates are to come, V3.3 is not the final model. I plan a V4 very soon…", "repo": "https://github.com/ScoutV41/ATLAS", "demo": "https://github.com/ScoutV41/ATLAS/releases/tag/D1"}]...
|
[{"post_id": 25712, "ts": "202 [{"post_id": 25712, "ts": "2026-07-10T04:30:44Z", "hours": 0.3333, "text": "D-LOG #2 (Based on work from the past month, was on vaca sorry for taking forever) Build: ATLASV3.3(L) Biggest changes: Full luminance curve pre-pass Instead of just thresholding each frame’s brightness individually, the script now buckets every image into 5-minute slots, builds a brightness curve across the entire dataset, and derives actual sunrise/sunset intervals from where the curve crosses DAY_THRESHOLD (20.0). There’s also a MIN_DAY_DURATION floor (1 hour) so a passing cloud or a lens flare can’t fake a fake “day.” Anything outside a real daylight window gets logged as NIGHT_CURVE_SKIPPED and skipped before the VLM even sees it saves a ton of compute on a big folder. Results get merged: Shadow angle -> circular mean across models, flagged DISAGREE if spread > 45° Shadow length / density / rock texture / volcanic features -> majority vote Plant types / rock colors -> unioned into one combined list Latitude derivation Previous versions only estimated longitude. v3.3 adds a day-length-based latitude calc, it finds the longest daylight interval in the dataset, converts that duration into a sunset hour angle, and solves for latitude using solar declination for the day of year. Search area validation Both derived coordinates now get checked against a Haversine distance from a defined SEARCH_CENTER / SEARCH_RADIUS_KM, with a clean ✅ / ❌ status line and a fallback bounding box printed if the point lands outside the circle. Habitat classifier got smarter HABITAT_RULES is now a proper rule list -> each biome match is a lambda checking keyword hits across plant types, rock color, and vegetation density instead of a flat tally. Sonoran/Chihuahuan/Mojave/Colorado Plateau/Cascades/Sierra-Great Basin/High Desert/Mixed Conifer are all still in there, just with tighter matching logic. Parser resilience parse_field() handles models that randomly bold their output ( SHADOW_ANGLE: etc.) and normalizes stray ° symbols and none/n/a/null variants down to “unknown” so downstream math doesn’t choke on garbage strings. Known issue, flagging this for myself before I forget The longitude calc in main() is currently hardcoded, not pulling from the actual solar_noon_avg computed earlier in the run: day_of_year = 138 # May 18th eot = 3.65 # Verified EoT for Day 1 noon_secs = 84495 # Verified 23:28:15 UTC trajectory That’s leftover from debugging against the sample dataset, it means every run right now spits out the same longitude regardless of what images you actually feed it, which is obviously not the goal. Latitude is properly dynamic (built off intervals from the real daylight curve), longitude isn’t yet. Top priority fix for the next patch, need to swap those three constants for the real per-dataset solar_noon_avg / Julian day / EoT calc instead of the frozen debug values. Next up Wire the real solar_noon_avg (already computed in compute_solar_noon()) into the longitude block instead of the hardcoded Day 1 constants Maybe expand HABITAT_RULES matching beyond simple keyword hits, closer to weighted scoring Look into whether internvl2_5-4b is pulling its weight in the ensemble or just adding runtime for marginal disagreement value"}, {"post_id": 2525, "ts": "2026-06-05T01:55:27Z", "hours": 1.4319, "text": "Devlog - 01 A few weeks ago I almost helped find $20K buried somewhere in the American southwest. ATLAS is the image recognition pipeline I built to try. It Works by taking a feed of images (50+ for best results, I used 625 for my tests) sending them through Various Local VLMs for inference. (Via LM Studio) I’ve been working on this project for weeks, decided to share it with everyone here. Currently I am working on Version 3.3. Previous models of ATLAS only utilized one VLM for inference, I had noticed the outputs to be significantly off course. So In V3.3 I designed it to use an ensemble system. Instead of using one model, it cross checks data between 2 or more. Then determines the winning output from all models. This way if one model hallucinates and the others don’t, Your data wont be skewed… Though I am still working out some bugs, as V3.3 has been off course by a MARGIN. It runs a user defined boundary. So instead of having to manually check coordinates yourself you’d know if it was incorrect instantly. Though V3.3 doesn’t really respect the boundary, so I need to get that fixed. -(My latest test ran 4,355Km off target. this is a known geometry bug in the coordinate derivation, not the inference pipeline itself) The speed at which ATLAS Processes images depends entirely on your hardware and number/type of model(s) you are using. Example: (Using qwen 2.5 7B (Q4_K_M), and Moondream 2 (Q4) 600 Frames Estimated Times Best tier GPU: RTX 4090, Dual RTX 3090s, Mac Studio M3 Ultra, etc… Runtime: Qwen 2.5 7B ~0.25 seconds Moondream2 ~0.08 seconds Total: 3 to 4 minutes High Tier GPU: RTX 4080, RTX 4070 Ti Super, M3 Max, etc… Runtime Qwen 2.5 7B ~0.60 seconds Moondream2 ~0.20 seconds Total: 6 to 8 minutes Mid tier GPU: RTX 4060 Ti (16GB), RTX 4070, M3 Pro, etc… Runtime Qwen 2.5 7B ~2.00 seconds Moondream2 ~0.50 seconds Total: 22 to 30 minutes Low tier GPU: RTX 3050, GTX 1660 Super, Base M1/M2 Mac, etc… Runtime: Qwen 2.5 7B ~5.00 seconds Moondream2 ~1.20 seconds Total: 1 to 1.5 hours CPU Only: Core i9 / Ryzen 9 (32GB DDR5 RAM), etc… Runtime: Qwen 2.5 7B ~35.00 seconds Moondream2 ~7.00 seconds Total: 6 to 8 hours (tested on RX 9070 XT 16GB) Updated features: Global Luminance Profiling: maps brightness across the entire dataset to skip night frames before inference, saves ~10% compute Triple-Model Consensus Pass: runs 3 VLMs in parallel and cross-checks outputs to filter hallucinations Orbital Mechanics Longitude Tracking: derives longitude from solar noon timing in image timestamps Haversine Validator: checks derived coordinates against the search boundary using spherical earth math Currently working on fixing shadow angle calculation (Keeps returning unknown for certain vectors), and Search area constraint bias. (Image shows V3.3 running with a Tri-Qwen ensemble)"}]...
|
Title: ATLAS by @Scout | Stardance
Devlogs:
Devlo Title: ATLAS by @Scout | Stardance
Devlogs:
Devlog - 01 A few weeks ago I almost helped find $20K buried somewhere in the American southwest. ATLAS is the image recognition pipeline I built to try. It Works by taking a feed of images (50+ for best results, I used 625 for my tests) sending them through Various Local VLMs for inference. (Via LM Studio) I’ve been working on this project for weeks, decided to share it with everyone here. Currently I am working on Version 3.3. Previous models of ATLAS only utilized one VLM for inference, I had noticed the outputs to be significantly off course. So In V3.3 I designed it to use an ensemble system. Instead of using one model, it cross checks data between 2 or more. Then determines the winning output from all models. This way if one model hallucinates and the others don’t, Your data wont be skewed… Though I am still working out some bugs, as V3.3 has been off course by a MARGIN. It runs a user defined boundary. So instead of having to manually check coordinates yourself you’d know if it was incorrect instantly. Though V3.3 doesn’t really respect the boundary, so I need to get that fixed. -(My latest test ran 4,355Km off target. this is a known geometry bug in the coordinate derivation, not the inference pipeline itself) The speed at which ATLAS Processes images depends entirely on your hardware and number/type of model(s) you are using. Example: (Using qwen 2.5 7B (Q4_K_M), and Moondream 2 (Q4) 600 Frames Estimated Times Best tier GPU: RTX 4090, Dual RTX 3090s, Mac Studio M3 Ultra, etc… Runtime: Qwen 2.5 7B ~0.25 seconds Moondream2 ~0.08 seconds Total: 3 to 4 minutes High Tier GPU: RTX 4080, RTX 4070 Ti Super, M3 Max, etc… Runtime Qwen 2.5 7B ~0.60 seconds Moondream2 ~0.20 seconds Total: 6 to 8 minutes Mid tier GPU: RTX 4060 Ti (16GB), RTX 4070, M3 Pro, etc… Runtime Qwen 2.5 7B ~2.00 seconds Moondream2 ~0.50 seconds Total: 22 to 30 minutes Low tier GPU: RTX 3050, GTX 1660 Super, Base M1/M2 Mac, etc… Runtime: Qwen 2.5 7B ~5.00 seconds Moondream2 ~1.20 seconds Total: 1 to 1.5 hours CPU Only: Core i9 / Ryzen 9 (32GB DDR5 RAM), etc… Runtime: Qwen 2.5 7B ~35.00 seconds Moondream2 ~7.00 seconds Total: 6 to 8 hours (tested on RX 9070 XT 16GB) Updated features: Global Luminance Profiling: maps brightness across the entire dataset to skip night frames before inference, saves ~10% compute Triple-Model Consensus Pass: runs 3 VLMs in parallel and cross-checks outputs to filter hallucinations Orbital Mechanics Longitude Tracking: derives longitude from solar noon timing in image timestamps Haversine Validator: checks derived coordinates against the search boundary using spherical earth math Currently working on fixing shadow angle calculation (Keeps returning unknown for certain vectors), and Search area constraint bias. (Image shows V3.3 running with a Tri-Qwen ensemble)
D-LOG #2 (Based on work from the past month, was on vaca sorry for taking forever) Build: ATLASV3.3(L) Biggest changes: Full luminance curve pre-pass Instead of just thresholding each frame’s brightness individually, the script now buckets every image into 5-minute slots, builds a brightness curve across the entire dataset, and derives actual sunrise/sunset intervals from where the curve crosses DAY_THRESHOLD (20.0). There’s also a MIN_DAY_DURATION floor (1 hour) so a passing cloud or a lens flare can’t fake a fake “day.” Anything outside a real daylight window gets logged as NIGHT_CURVE_SKIPPED and skipped before the VLM even sees it saves a ton of compute on a big folder. Results get merged: Shadow angle -> circular mean across models, flagged DISAGREE if spread > 45° Shadow length / density / rock texture / volcanic features -> majority vote Plant types / rock colors -> unioned into one combined list Latitude derivation Previous versions only estimated longitude. v3.3 adds a day-length-based latitude calc, it finds the longest daylight interval in the dataset, converts that duration into a sunset hour angle, and solves for latitude using solar declination for the day of year. Search area validation Both derived coordinates now get checked against a Haversine distance from a defined SEARCH_CENTER / SEARCH_RADIUS_KM, with a clean ✅ / ❌ status line and a fallback bounding box printed if the point lands outside the circle. Habitat classifier got smarter HABITAT_RULES is now a proper rule list -> each biome match is a lambda checking keyword hits across plant types, rock color, and vegetation density instead of a flat tally. Sonoran/Chihuahuan/Mojave/Colorado Plateau/Cascades/Sierra-Great Basin/High Desert/Mixed Conifer are all still in there, just with tighter matching logic. Parser resilience parse_field() handles models that randomly bold their output ( SHADOW_ANGLE: etc.) and normalizes stray ° symbols and none/n/a/null variants down to “unknown” so downstream math doesn’t choke on garbage strings. Known issue, flagging this for myself before I forget The longitude calc in main() is currently hardcoded, not pulling from the actual solar_noon_avg computed earlier in the run: day_of_year = 138 # May 18th eot = 3.65 # Verified EoT for Day 1 noon_secs = 84495 # Verified 23:28:15 UTC trajectory That’s leftover from debugging against the sample dataset, it means every run right now spits out the same longitude regardless of what images you actually feed it, which is obviously not the goal. Latitude is properly dynamic (built off intervals from the real daylight curve), longitude isn’t yet. Top priority fix for the next patch, need to swap those three constants for the real per-dataset solar_noon_avg / Julian day / EoT calc instead of the frozen debug values. Next up Wire the real solar_noon_avg (already computed in compute_solar_noon()) into the longitude block instead of the hardcoded Day 1 constants Maybe expand HABITAT_RULES matching beyond simple keyword hits, closer to weighted scoring Look into whether internvl2_5-4b is pulling its weight in the ensemble or just adding runtime for marginal disagreement value
Ships:
This is ATLAS, a Image search and geo recognition tool that uses VLMs (Visual Language Models) to scan a string of images, guess where they were taken, and supply estimated coordinates. (As said in my Dev log the coordinates may be off wildly, this is a known issue being worked on currently) The code is being worked on every week and major updates are to come, V3.3 is not the final model. I plan a V4 very soon…...
|
1793865272.701105
|
1793951672.701105
|
|
5457
|
A Bluey themed Hackpad by @Gopike | Stardance
|
Gopike
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A Bluey themed Hackpad by @Gopike | Stardan Title: A Bluey themed Hackpad by @Gopike | Stardance...
|
1793785877.079648
|
1794390677.079648
|
|
5458
|
Untitled by @pngyn | Stardance
|
pngyn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @pngyn | Stardance
|
1793235067.2179997
|
1793839867.2179997
|
|
5459
|
My first slack bot! by @spookfish | Stardance
|
spookfish
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @spookfish | Stardan Title: My first slack bot! by @spookfish | Stardance...
|
1793573286.8935394
|
1794178086.8935394
|
|
5460
|
My awesome macropad! by @leanne_nis | Stardance
|
leanne_nis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @leanne_nis | Stard Title: My awesome macropad! by @leanne_nis | Stardance...
|
1793393363.6658263
|
1793998163.6658263
|
|
5461
|
My first slack bot! by @leanne_nis | Stardance
|
leanne_nis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @leanne_nis | Starda Title: My first slack bot! by @leanne_nis | Stardance...
|
1793829336.6743739
|
1794434136.6743739
|
|
5462
|
Untitled project by @leanne_nis | Stardance
|
leanne_nis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @leanne_nis | Stardance
|
1793393598.2886987
|
1793998398.2886987
|
|
5463
|
/HEXpi/ by @moorejn4 | Stardance
|
moorejn4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: /HEXpi/ by @moorejn4 | Stardance
|
1793458381.6703637
|
1794063181.6703637
|
|
5464
|
Cosmic platforms by @Vicmin_7 | Stardance
|
Vicmin_7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cosmic platforms by @Vicmin_7 | Stardance
|
1793443768.9017642
|
1794048568.9017642
|
|
5465
|
Soldering Hot Plate by @ondy | Stardance
|
ondy
|
0
|
5.32
|
0
|
[]
|
[{"post_id": 48051, "ts": "202 [{"post_id": 48051, "ts": "2026-08-16T10:28:04Z", "hours": 3.6211, "text": "devlog 1.0 Finally we are moving from the planning part to the hardware one, the reason last devlog was 2 months ago is that hardware is really time consuming and i didnt have much time this summer. Anyway since i dont have access to a 3d printer i had to be creative: so i made the base out of wood, its a hardwood and (hopefully) shouldnt char. I know it looks uneven but trust the process, the part thats sticking out will be used for controls. The hotplate it self is lifted by 3 big blots to isolate it from the rest. I was also testing the thermistor actually works the way i intended and everything seems to be working just fine(check las devlog schematic for more info). In the next few days i will finally start soldering everything and hopefully i can get this thing working by the end of Stardance😭"}, {"post_id": 3000, "ts": "2026-06-05T22:33:53Z", "hours": 1.0542, "text": "devlog 0.1 - made complete wiring diagram from components i researched in the last devlog, had to add varistor + fuse for protection and resistor with the NTC thermistor to make voltage divider; currently waiting for components to arrive; this is just a simple wiring diagram dont look too closely at it😭🙏"}, {"post_id": 1550, "ts": "2026-06-03T17:13:31Z", "hours": 0.645, "text": "devlog 0.0 - spent some time researching specific hardware components to make sure they will work together, some of those were real hassle - next time can i start designing the wire layout –had to use this boring ah image😭🙏"}]...
|
Title: Soldering Hot Plate by @ondy | Stardance
D Title: Soldering Hot Plate by @ondy | Stardance
Devlogs:
devlog 0.0 - spent some time researching specific hardware components to make sure they will work together, some of those were real hassle - next time can i start designing the wire layout –had to use this boring ah image😭🙏
devlog 0.1 - made complete wiring diagram from components i researched in the last devlog, had to add varistor + fuse for protection and resistor with the NTC thermistor to make voltage divider; currently waiting for components to arrive; this is just a simple wiring diagram dont look too closely at it😭🙏
devlog 1.0 Finally we are moving from the planning part to the hardware one, the reason last devlog was 2 months ago is that hardware is really time consuming and i didnt have much time this summer. Anyway since i dont have access to a 3d printer i had to be creative: so i made the base out of wood, its a hardwood and (hopefully) shouldnt char. I know it looks uneven but trust the process, the part thats sticking out will be used for controls. The hotplate it self is lifted by 3 big blots to isolate it from the rest. I was also testing the thermistor actually works the way i intended and everything seems to be working just fine(check las devlog schematic for more info). In the next few days i will finally start soldering everything and hopefully i can get this thing working by the end of Stardance😭...
|
1793332191.9416063
|
1793936991.9416063
|
|
5466
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793882870.3248725
|
1794746870.3248725
|
|
5467
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793782363.4096985
|
1794646363.4096985
|
|
5468
|
My awesome macropad! by @chloez | Stardance
|
chloez
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @chloez | Stardance
|
1793213457.0160809
|
1793818257.0160809
|
|
5469
|
My awesome macropad! by @izzynife | Stardance
|
izzynife
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @izzynife | Stardan Title: My awesome macropad! by @izzynife | Stardance...
|
1793260220.8080404
|
1793865020.8080404
|
|
5470
|
My first slack bot! by @silvi | Stardance
|
silvi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @silvi | Stardance
|
1793469267.137269
|
1794074067.137269
|
|
5471
|
My awesome macropad! by @JxxobTr333 | Stardance
|
JxxobTr333
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @JxxobTr333 | Stard Title: My awesome macropad! by @JxxobTr333 | Stardance...
|
1793317753.2853482
|
1793922553.2853482
|
|
5472
|
Ethashi by @NellowTCS | Stardance
|
NellowTCS
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ethashi by @NellowTCS | Stardance
|
1793933581.8261933
|
1794797581.8261933
|
|
5473
|
Untitled project by @iamthehacker | Stardance
|
iamthehacker
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @iamthehacker | Stardan Title: Untitled project by @iamthehacker | Stardance...
|
1793537738.4427667
|
1794142538.4427667
|
|
5474
|
My awesome macropad! by @tterbg13 | Stardance
|
tterbg13
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tterbg13 | Stardan Title: My awesome macropad! by @tterbg13 | Stardance...
|
1793476610.8007305
|
1794081410.8007305
|
|
5475
|
Untitled project by @The_Cubidian | Stardance
|
The_Cubidian
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @The_Cubidian | Stardan Title: Untitled project by @The_Cubidian | Stardance...
|
1793231676.6263812
|
1793836476.6263812
|
|
5476
|
My awesome macropad! by @Honque | Stardance
|
Honque
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Honque | Stardance
|
1793321736.7611296
|
1793926536.7611296
|
|
5477
|
Untitled project by @hillary | Stardance
|
hillary
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @hillary | Stardance
|
1793436867.28444
|
1794041667.28444
|
|
5478
|
ctf bot by @rena | Stardance
|
rena
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ctf bot by @rena | Stardance
|
1793217206.3219647
|
1793822006.3219647
|
|
5479
|
Sysadmin over ssh by @CoastStarlight | Stardance
|
CoastStarlight
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Sysadmin over ssh by @CoastStarlight | Star Title: Sysadmin over ssh by @CoastStarlight | Stardance...
|
1793440420.040458
|
1794045220.040458
|
|
5480
|
Jarned V1 by @Jarned | Stardance
|
Jarned
|
1
|
8.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-08T20:44:48Z", "hours": 8.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a small but functional hackpad with 5 keys, a volume knob and an OLED screen. The part that I found the most challenging was the KiCad and it’s routing tool. While I am now fairly good at it, I was definitely struggling at the start. The part that I’m the most proud of is the KMK python itself. I had never used it, I didn’t let AI write a single line of code for me and I managed to do it with the help of google and their documentation. I hope to get a grant from Outpost to get the materials to build my project.", "repo": "https://github.com/Jarned-rs/Jarned-V1", "demo": ""}]...
|
[{"post_id": 5142, "ts": "2026 [{"post_id": 5142, "ts": "2026-06-08T20:35:09Z", "hours": 1.6825, "text": "Devlog #4 (final) I have reached the end of this amazing (in some ways) project. In this time I managed to organise all my files and write an actual README and make some final tweaks. While my project isn’t the best or the most skilled, I think that I did very well for this being my first project of this sort ever. For the last time- Jarned"}, {"post_id": 4970, "ts": "2026-06-08T16:53:15Z", "hours": 2.6533, "text": "Devlog #3 Managed to finally finish my case and the code! (still in shock how I managed to string my 8 braincells together to make it work). All that remains is file management… The case is basic but functional and has 5 key spaces, a rotary encoder and an OLED. I honestly think that it could be better but for a first project I’m proud of it. The code is also extremely basic with all the keys set to F13 onwards so I can create my own shortcuts through Windows. Let’s hope that they approve my project! Jarned"}, {"post_id": 2887, "ts": "2026-06-05T19:47:18Z", "hours": 2.6356, "text": "Devlog #2 - Jarned V1 After dealing with my 41 errors, deleting my work twice, asking too many stupid questions to Claude. I got my KiCad exported and started my 3D model I haven’t used a 3D modelling engine in about 2 years… so let’s just say that I couldn’t draw a rectangle for 20 mins. However, it seems like my braincells have started to function and I have started my top section of the case. Let’s hope that my good luck continues Jarned"}, {"post_id": 2214, "ts": "2026-06-04T16:25:45Z", "hours": 0.7158, "text": "Devlog #1 - Jarned V1 Today, I made my initial design for my PCB using the basic guide. While it still has too many errors to count, my 5 push switches, my OLED screen and my rotary encoder seem to be coming together after reading a whole books worth of KiCad tutorials where people who know way more than me debate over the smallest of things. The PCB seems simple yet DRC keeps on giving me an error which forces me to start over!"}]...
|
Title: Jarned V1 by @Jarned | Stardance
Devlogs:
Title: Jarned V1 by @Jarned | Stardance
Devlogs:
Devlog #1 - Jarned V1 Today, I made my initial design for my PCB using the basic guide. While it still has too many errors to count, my 5 push switches, my OLED screen and my rotary encoder seem to be coming together after reading a whole books worth of KiCad tutorials where people who know way more than me debate over the smallest of things. The PCB seems simple yet DRC keeps on giving me an error which forces me to start over!
Devlog #2 - Jarned V1 After dealing with my 41 errors, deleting my work twice, asking too many stupid questions to Claude. I got my KiCad exported and started my 3D model I haven’t used a 3D modelling engine in about 2 years… so let’s just say that I couldn’t draw a rectangle for 20 mins. However, it seems like my braincells have started to function and I have started my top section of the case. Let’s hope that my good luck continues Jarned
Devlog #3 Managed to finally finish my case and the code! (still in shock how I managed to string my 8 braincells together to make it work). All that remains is file management… The case is basic but functional and has 5 key spaces, a rotary encoder and an OLED. I honestly think that it could be better but for a first project I’m proud of it. The code is also extremely basic with all the keys set to F13 onwards so I can create my own shortcuts through Windows. Let’s hope that they approve my project! Jarned
Devlog #4 (final) I have reached the end of this amazing (in some ways) project. In this time I managed to organise all my files and write an actual README and make some final tweaks. While my project isn’t the best or the most skilled, I think that I did very well for this being my first project of this sort ever. For the last time- Jarned
Ships:
I made a small but functional hackpad with 5 keys, a volume knob and an OLED screen. The part that I found the most challenging was the KiCad and it’s routing tool. While I am now fairly good at it, I was definitely struggling at the start. The part that I’m the most proud of is the KMK python itself. I had never used it, I didn’t let AI write a single line of code for me and I managed to do it with the help of google and their documentation. I hope to get a grant from Outpost to get the materials to build my project....
|
1793857947.938272
|
1793944347.938272
|
|
5481
|
My first slack bot! by @rafaeram | Stardance
|
rafaeram
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @rafaeram | Stardanc Title: My first slack bot! by @rafaeram | Stardance...
|
1793926258.849879
|
1794531058.849879
|
|
5482
|
Untitled by @rafaeram | Stardance
|
rafaeram
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @rafaeram | Stardance
|
1793282147.5350845
|
1793886947.5350845
|
|
5483
|
qbPad by @cubie | Stardance
|
cubie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: qbPad by @cubie | Stardance
|
1793414960.7978678
|
1794019760.7978678
|
|
5484
|
CoastlineGuessr by @sss | Stardance
|
sss
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CoastlineGuessr by @sss | Stardance
|
1793235033.9864469
|
1793839833.9864469
|
|
5485
|
My awesome macropad! by @Neev | Stardance
|
Neev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Neev | Stardance
|
1793919308.6571786
|
1794524108.6571786
|
|
5486
|
My first slack bot! by @RedThread14 | Stardance
|
RedThread14
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @RedThread14 | Stard Title: My first slack bot! by @RedThread14 | Stardance...
|
1793569725.0437465
|
1794174525.0437465
|
|
5487
|
My awesome macropad! by @stella | Stardance
|
stella
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stella | Stardance
|
1793426001.466852
|
1794030801.466852
|
|
5488
|
FPGA Retro Emulator by @njfdev | Stardance
|
njfdev
|
0
|
2.34
|
0
|
[]
|
[{"post_id": 1675, "ts": "2026 [{"post_id": 1675, "ts": "2026-06-03T20:25:32Z", "hours": 1.9186, "text": "Got some basic audio wave production!! I ended up using the miniaudio.h header library and manually figured out how to produce square, triangle, sawtooth, and noise waves. These are the key ones I need for my NES emulator!"}, {"post_id": 1021, "ts": "2026-06-02T20:17:58Z", "hours": 0.4167, "text": "Just got started with my retro console hardware emulation project! For now, I have setup a project with Verilator and have a very basic working C++ project."}]...
|
Title: FPGA Retro Emulator by @njfdev | Stardance
Title: FPGA Retro Emulator by @njfdev | Stardance
Devlogs:
Just got started with my retro console hardware emulation project! For now, I have setup a project with Verilator and have a very basic working C++ project.
Got some basic audio wave production!! I ended up using the miniaudio.h header library and manually figured out how to produce square, triangle, sawtooth, and noise waves. These are the key ones I need for my NES emulator!...
|
1793465719.257261
|
1794070519.257261
|
|
5489
|
tuff macropad by @sayer | Stardance
|
sayer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: tuff macropad by @sayer | Stardance
|
1793299834.585164
|
1793904634.585164
|
|
5490
|
Untitled project by @rajesh | Stardance
|
rajesh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @rajesh | Stardance
|
1793479752.351673
|
1794084552.351673
|
|
5491
|
My first slack bot! by @Aster_ | Stardance
|
Aster_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Aster_ | Stardance
|
1793357758.3304577
|
1793962558.3304577
|
|
5492
|
Untitled project by @zoey_zhang | Stardance
|
zoey_zhang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @zoey_zhang | Stardance
|
1793382754.6167083
|
1793987554.6167083
|
|
5493
|
My first slack bot! by @haugenquinn | Stardance
|
haugenquinn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @haugenquinn | Stard Title: My first slack bot! by @haugenquinn | Stardance...
|
1793541003.670236
|
1794145803.670236
|
|
5494
|
My awesome macropad! by @shadxen-fx | Stardance
|
shadxen-fx
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @shadxen-fx | Stard Title: My awesome macropad! by @shadxen-fx | Stardance...
|
1793472592.2593367
|
1794077392.2593367
|
|
5495
|
My first slack bot! by @Camc | Stardance
|
Camc
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Camc | Stardance
|
1793285345.1174066
|
1793890145.1174066
|
|
5496
|
Windows Manager/Browser Control Pad by @max-lobste Windows Manager/Browser Control Pad by @max-lobster | Stardance...
|
max-lobster
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Windows Manager/Browser Control Pad by @max Title: Windows Manager/Browser Control Pad by @max-lobster | Stardance...
|
1793767645.9575796
|
1794372445.9575796
|
|
5497
|
NixOS by @janekmusin | Stardance
|
janekmusin
|
0
|
24.36
|
0
|
[]
|
[{"post_id": 30117, "ts": "202 [{"post_id": 30117, "ts": "2026-07-17T13:03:39Z", "hours": 0.9781, "text": "I finally bit the bullet and set up nixos on my desktop (hostname Victim). With that, there’s (almost) nothing stopping me from working on some more serious projects. Aside from that, I don’t really remember what I have been doing since last devlog, because I went on small Distrohoping arc and worked on some other projects, in other YSWSes. Discovery of the devlog: Fedora Rawhide. I never liked fedora, because of how slow it updates, but rawhide fixes that. Still, in my opinion it is last gen distribution, with manual updates and imperative system management, so I can’t recommend it. Happy Hacking!"}, {"post_id": 24731, "ts": "2026-07-08T14:36:22Z", "hours": 4.2647, "text": "I meant to write this devlog much sooner. I created proper modules for desktop environment. I did that in last monday, it took around 2 hours. After that I realized that there’re several issues that needs fixing. I had to take an almost week long break because of reasons and after it, I worked on some other project. Now, when I could I fixed those, bugs, but that quickly snowballed to adding new features, troubleshooting newly introduced bugs and even contributing an upstream fix to one of the programs I use (which still haven’t been merged :(). I’m trying to treat those devlogs more like blogs. Let me know if you like that. Discovery of the devlog: Startpage. Startpage is a search engine with focus on openness, just like DDG, which I used before. I find the results in it much better than DDG, mainly because it uses Google as upstream search provider instead of Bing. Happy Hacking!"}, {"post_id": 18367, "ts": "2026-06-29T14:27:09Z", "hours": 4.5689, "text": "Nushell is working! Obviously it’s not all I’ve been doing this 4 hours. You know the story: You write down a few things you want to improve, but while implementing one thing you notice three more that need a fix and later after 4 hours you don’t even remember what you have been working on. Maybe it’s just me, this project is also something very special for me, as it’s declaration of my working machine, for at least next few years, if not lifetime. If you’re reading this devlog on stardance frontpage, let me know if you like this format of dividing a devlog on a few hardly related parts, some of which are completely detached from the actual project. Saying it out-loud makes it look not like good idea. In my search for objectively™ best shell I tried all the mainstream ones, but in my opinion nothing (Ehem, elvish, ehem) comes close to nushell. It has almost all the features of fish and other modern shells, while adding unique and better way of interacting with data. I feel like I’m slowly finishing this project, there’s not much to do. Obviously this is one of those things that are always in development, because it is well, my personal system. Each time I want to add a package, I need to interact with my configuration and it’s a good thing. Happy Hacking!"}, {"post_id": 15181, "ts": "2026-06-24T17:46:39Z", "hours": 4.8486, "text": "I FINALLY GOT RID OF SPECIAL ARGS! Okay here’s why that change is important (I need to wait for CI to pass, so I have around 30 minutes of “free time”): Special args are variables that can be passed to modules. You have to explicitly “send” and explicitly “receive” them, which makes them kinda bad. They’re also non modular, meaning they can break without sender. I finally bit the bullet and moved to module based system. The advantages of them are as follows: No explicit receiving required Easier to create complicated expressions with Can be limited to a few values only Values can be something other than strings Officially supported by flake-parts, the framework I’m using More portable Generally they’re a superior options and I’m happy I implemented them. There’re still many things I want to work on: Plasma and Niri desktops with modules for DE configuration Nushell with modules for shell configuration Improving docs More hosts Other projects :) I forgot something for sure, but I’m honestly surprised that I could recall only so few things. Anyway, happy hacking!"}, {"post_id": 13624, "ts": "2026-06-22T10:42:43Z", "hours": 4.8506, "text": "Not always you have something big to talk about in a devlog This is yet again devlog full of minor, non interesting changes. I have been mainly troubleshooting my server (which btw is still not finished. which is wild), but I did many other things along that. Now I’m trying to move back to Plasma and implement proper module system. I expect that to be quite time consuming task, but… nothing. It’s just going to be time consuming. Another idea is changing the shell to nushell, so that’s second on the agenda. From the things unrelated to project itself, I changed my IDE from vscode to zed. I have lots of other projects in mind, so I will work on this in meantime. I don’t even have anything to show, so I will just add a screenshot of my editor. Dotfiles aren’t sexy."}, {"post_id": 8603, "ts": "2026-06-14T09:32:54Z", "hours": 4.8478, "text": "A massive, misc fixes PR shipped! It fixed a lot of small pain points and improved some existing features. The whole list of changed things is available on the screenshot. There’s so much to do now that I don’t know if I want to pause for a moment and work on other project."}]...
|
Title: NixOS by @janekmusin | Stardance
Devlogs:
Title: NixOS by @janekmusin | Stardance
Devlogs:
A massive, misc fixes PR shipped! It fixed a lot of small pain points and improved some existing features. The whole list of changed things is available on the screenshot. There’s so much to do now that I don’t know if I want to pause for a moment and work on other project.
Not always you have something big to talk about in a devlog This is yet again devlog full of minor, non interesting changes. I have been mainly troubleshooting my server (which btw is still not finished. which is wild), but I did many other things along that. Now I’m trying to move back to Plasma and implement proper module system. I expect that to be quite time consuming task, but… nothing. It’s just going to be time consuming. Another idea is changing the shell to nushell, so that’s second on the agenda. From the things unrelated to project itself, I changed my IDE from vscode to zed. I have lots of other projects in mind, so I will work on this in meantime. I don’t even have anything to show, so I will just add a screenshot of my editor. Dotfiles aren’t sexy.
I FINALLY GOT RID OF SPECIAL ARGS! Okay here’s why that change is important (I need to wait for CI to pass, so I have around 30 minutes of “free time”): Special args are variables that can be passed to modules. You have to explicitly “send” and explicitly “receive” them, which makes them kinda bad. They’re also non modular, meaning they can break without sender. I finally bit the bullet and moved to module based system. The advantages of them are as follows: No explicit receiving required Easier to create complicated expressions with Can be limited to a few values only Values can be something other than strings Officially supported by flake-parts, the framework I’m using More portable Generally they’re a superior options and I’m happy I implemented them. There’re still many things I want to work on: Plasma and Niri desktops with modules for DE configuration Nushell with modules for shell configuration Improving docs More hosts Other projects :) I forgot something for sure, but I’m honestly surprised that I could recall only so few things. Anyway, happy hacking!
Nushell is working! Obviously it’s not all I’ve been doing this 4 hours. You know the story: You write down a few things you want to improve, but while implementing one thing you notice three more that need a fix and later after 4 hours you don’t even remember what you have been working on. Maybe it’s just me, this project is also something very special for me, as it’s declaration of my working machine, for at least next few years, if not lifetime. If you’re reading this devlog on stardance frontpage, let me know if you like this format of dividing a devlog on a few hardly related parts, some of which are completely detached from the actual project. Saying it out-loud makes it look not like good idea. In my search for objectively™ best shell I tried all the mainstream ones, but in my opinion nothing (Ehem, elvish, ehem) comes close to nushell. It has almost all the features of fish and other modern shells, while adding unique and better way of interacting with data. I feel like I’m slowly finishing this project, there’s not much to do. Obviously this is one of those things that are always in development, because it is well, my personal system. Each time I want to add a package, I need to interact with my configuration and it’s a good thing. Happy Hacking!
I meant to write this devlog much sooner. I created proper modules for desktop environment. I did that in last monday, it took around 2 hours. After that I realized that there’re several issues that needs fixing. I had to take an almost week long break because of reasons and after it, I worked on some other project. Now, when I could I fixed those, bugs, but that quickly snowballed to adding new features, troubleshooting newly introduced bugs and even contributing an upstream fix to one of the programs I use (which still haven’t been merged :(). I’m trying to treat those devlogs more like blogs. Let me know if you like that. Discovery of the devlog: Startpage. Startpage is a search engine with focus on openness, just like DDG, which I used before. I find the results in it much better than DDG, mainly because it uses Google as upstream search provider instead of Bing. Happy Hacking!
I finally bit the bullet and set up nixos on my desktop (hostname Victim). With that, there’s (almost) nothing stopping me from working on some more serious projects. Aside from that, I don’t really remember what I have been doing since last devlog, because I went on small Distrohoping arc and worked on some other projects, in other YSWSes. Discovery of the devlog: Fedora Rawhide. I never liked fedora, because of how slow it updates, but rawhide fixes that. Still, in my opinion it is last gen distribution, with manual updates and imperative system management, so I can’t recommend it. Happy Hacking!...
|
1793296383.8027759
|
1793901183.8027759
|
|
5498
|
Macropad v1.0 by @omerq | Stardance
|
omerq
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Macropad v1.0 by @omerq | Stardance
|
1793299977.425536
|
1793904777.425536
|
|
5499
|
My first slack bot! by @JaydenP | Stardance
|
JaydenP
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @JaydenP | Stardance
|
1793288984.3297276
|
1793893784.3297276
|
|
5500
|
My awesome macropad! by @sherri16212345 | Stardanc My awesome macropad! by @sherri16212345 | Stardance...
|
sherri16212345
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sherri16212345 | S Title: My awesome macropad! by @sherri16212345 | Stardance...
|
1793433319.2628043
|
1794038119.2628043
|