|
15646
|
My first slack bot! by @starfish_1567 | Stardance
|
starfish_1567
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @starfish_1567 | Sta Title: My first slack bot! by @starfish_1567 | Stardance...
|
1793450905.8755727
|
1794055705.8755727
|
|
15966
|
My first slack bot! by @starfish08second | Stardan My first slack bot! by @starfish08second | Stardance...
|
starfish08second
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @starfish08second | Title: My first slack bot! by @starfish08second | Stardance...
|
1793425714.7482207
|
1794030514.7482207
|
|
35325
|
No Nicotine! by @stardust_stella | Stardance
|
stardust_stella
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: No Nicotine! by @stardust_stella | Stardanc Title: No Nicotine! by @stardust_stella | Stardance...
|
1793292802.7523193
|
1793897602.7523193
|
|
35630
|
Learning the Ropes! by @stardust_stella | Stardanc Learning the Ropes! by @stardust_stella | Stardance...
|
stardust_stella
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Learning the Ropes! by @stardust_stella | S Title: Learning the Ropes! by @stardust_stella | Stardance...
|
1793444045.0562303
|
1794048845.0562303
|
|
25113
|
Obstacle-Detecting-Glasses by @stardancetest | Sta Obstacle-Detecting-Glasses by @stardancetest | Stardance...
|
stardancetest
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Obstacle-Detecting-Glasses by @stardancetes Title: Obstacle-Detecting-Glasses by @stardancetest | Stardance...
|
1793501434.8338518
|
1794106234.8338518
|
|
49992
|
apkauto by @stardancerlol | Stardance
|
stardancerlol
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: apkauto by @stardancerlol | Stardance
|
1793314627.4711692
|
1793919427.4711692
|
|
8231
|
Sun by @stardance_jun5 | Stardance
|
stardance_jun5
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Sun by @stardance_jun5 | Stardance
|
1793440343.0794733
|
1794045143.0794733
|
|
35139
|
Frictionless by @stardance_jul14 | Stardance
|
stardance_jul14
|
0
|
0.8
|
0
|
[]
|
[{"post_id": 36287, "ts": "202 [{"post_id": 36287, "ts": "2026-07-28T09:19:13Z", "hours": 0.8017, "text": "woof"}]...
|
Title: Frictionless by @stardance_jul14 | Stardanc Title: Frictionless by @stardance_jul14 | Stardance
Devlogs:
woof...
|
1793235114.415178
|
1793839914.415178
|
|
42642
|
My very own WebOS by @stardance1 | Stardance
|
stardance1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @stardance1 | Stardanc Title: My very own WebOS by @stardance1 | Stardance...
|
1793882905.0324273
|
1794487705.0324273
|
|
33923
|
Static Bytes by @stardance001 | Stardance
|
stardance001
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Static Bytes by @stardance001 | Stardance
|
1793231753.1391919
|
1793836553.1391919
|
|
41832
|
My own site! by @starburst | Stardance
|
starburst
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @starburst | Stardance
|
1793789310.427176
|
1794394110.427176
|
|
44181
|
My own site! by @starboy | Stardance
|
starboy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @starboy | Stardance
|
1793260203.0817327
|
1793865003.0817327
|
|
47770
|
My own site! by @starbound | Stardance
|
starbound
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @starbound | Stardance
|
1793912046.7301872
|
1794516846.7301872
|
|
47777
|
goofy ahh website by @starbound | Stardance
|
starbound
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: goofy ahh website by @starbound | Stardance
|
1793912065.9233382
|
1794516865.9233382
|
|
47783
|
goofy ahh website prequel by @starbound | Stardanc goofy ahh website prequel by @starbound | Stardance...
|
starbound
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: goofy ahh website prequel by @starbound | S Title: goofy ahh website prequel by @starbound | Stardance...
|
1793912090.1476886
|
1794516890.1476886
|
|
57874
|
My first slack bot! by @starbomb | Stardance
|
starbomb
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @starbomb | Stardanc Title: My first slack bot! by @starbomb | Stardance...
|
1793461718.8274791
|
1794066518.8274791
|
|
67786
|
My own site! by @star_girl | Stardance
|
star_girl
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @star_girl | Stardance
|
1793735341.9244332
|
1794340141.9244332
|
|
18096
|
My very own WebOS by @star | Stardance
|
star
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @star | Stardance
|
1793339592.3321466
|
1793944392.3321466
|
|
29780
|
CLI Password Generator by @stant | Stardance
|
stant
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CLI Password Generator by @stant | Stardanc Title: CLI Password Generator by @stant | Stardance...
|
1793433052.827793
|
1794037852.827793
|
|
22431
|
My very own WebOS by @stanleyet | Stardance
|
stanleyet
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @stanleyet | Stardance
|
1793811177.1613443
|
1794415977.1613443
|
|
30579
|
microWMS by @stanislaw_stask | Stardance
|
stanislaw_stask
|
0
|
19.72
|
0
|
[]
|
[{"post_id": 28871, "ts": "202 [{"post_id": 28871, "ts": "2026-07-15T13:14:01Z", "hours": 19.7247, "text": "Created inventory manager for IN/OUT operations."}]...
|
Title: microWMS by @stanislaw_stask | Stardance
D Title: microWMS by @stanislaw_stask | Stardance
Devlogs:
Created inventory manager for IN/OUT operations....
|
1793501824.817417
|
1794106624.817417
|
|
35202
|
listhist by @staneko | Stardance
|
staneko
|
0
|
20.76
|
0
|
[]
|
[{"post_id": 39239, "ts": "202 [{"post_id": 39239, "ts": "2026-08-02T02:33:44Z", "hours": 9.9197, "text": "Welcome back to my listening history tracking project! You are now reading the third entry, and I’ve achieved a great milestone - the listening history tracking actually works. You can query your listening history and it will be fed back to you in JSON, supporting specific queries like a start date, an end date, a limit on the number of entries, etc. (i actually ran out of examples.) This JSON history endpoint does something that was very cool to implement; it gets the history entries, but obviously, those entries aren’t everything that a client needs to display them to the user. They consist merely of an entry ID, a track ID, and a date. The client would need to fetch the track details, then the album details, and then the artist details on its own, which would make for a lot of requests, considering that people usually listen to more than one track per day. So this would mean that, had the client not implemented some sort of caching, if you listened to, say, 25 tracks in a day and then queried your history, you would end up at a beautiful n_entries * len([\"track\", \"album\", \"artist\"]) = 25 * 3 = 75 requests! Which is insane. This listening history endpoint reduces this number to 1 . Yes, ONE request. This is done by directly including the necessary tracks, albums, and artists in the response, and the client can just iterate over the arrays of these resources and parse them into a hashmap keyed by their respective IDs. Pretty neat! So had you listened to a track, like “Keep The Streets Empty For Me” by Fever Ray from their album Fever Ray, the (prettified) response from the endpoint would look like this: { \"entries\" : [ { \"id\" : 3 , \"track_id\" : 8 , \"date\" : \"2026-08-02T02:27:13.727572Z\" } ], \"tracks\" : [ { \"id\" : 8 , \"title\" : \"Keep The Streets Empty For Me\" , \"artist_id\" : 2 , \"album_id\" : 4 , \"genre\" : \"Electronic\" } ], \"albums\" : [ { \"id\" : 4 , \"name\" : \"Fever Ray\" , \"artist_id\" : 2 } ], \"artist\" : [ { \"id\" : 2 , \"name\" : \"Fever Ray\" } ] } Looking at this, I’ve just realized that I probably need to make the genre column an array, since tracks usually exhibit properties of many different genres at once… that’s a problem for future me Obviously I’ve improved the code a bit here and there, the Compose configuration now actually makes the backend wait for the database so there isn’t a race condition (which may have been there for a few weeks…), and the data schema has changed a bit so that it makes more sense. There is now also a web app, but that is far from finished as it stands and so instead I’ve included a screenshot of the Firefox devtools I used to poke at my API and the successful response I finally got in the end."}, {"post_id": 31408, "ts": "2026-07-19T19:02:34Z", "hours": 8.4661, "text": "Welcome to my second devlog regarding listhist! Since the last entry, I’ve rewritten the shared client code to take advantage of the Rust type system much more. I’ve written quite a bit of Haskell in the past few weeks and I love the strong type system of the language; however, monadic I/O and especially the mixture of pure and impure exceptions makes my head hurt, which is why I decided to instead write this project mostly in Go and Rust. Either way, this means that without logging in, you can’t query endpoints which require an access token; so, for example, in order to create an album in the system, you have to do something like this: let client = listhist_client :: Client :: new ( \"your_base_url\" ); Now, client is of type Client<Unauthorized> . You can then call Client::login : let client = client .login ( \"username\" , \"password\" ) .await ? ; Now client is of type Client<Authorized> and you can actually create an album! let album = client .create_album ( ... ) .await ? ; Oh yeah, the client is now also asynchronous and therefore much more flexible… but that’s not as exciting. The other exciting thing that I managed to add to the repo is a Containerfile and a Compose file, so spinning up an instance, whether for testing or “for real” is super easy. So in this regard, I think I’ve achieved what I wrote about in the last entry. Now, the next step is polishing the existing code, resolving the TODO / FIXME items I have left for myself, adding some tests, etc. It’s boring work, but I believe that if I do it sooner than later, it will come back around and I can catch some of the more annoying bugs early on. And then I want to make a web interface for easy viewing of the data. The CLI should be the main way to enter listening history entries into the system, automatically of course (probably through MPRIS, custom player hooks and some Windows-specific mechanism), but viewing of the data should be possible from any device, without having to install the CLI. So, the web interface will be a relatively simple, fully client-sided web application, probably written with something like Preact. I have a lot of things planned for listhist, maybe even a friends system, which would be very exciting to have! Stay tuned for upcoming updates."}, {"post_id": 29623, "ts": "2026-07-16T17:55:24Z", "hours": 2.3742, "text": "Hi, I’m making a project to track my listening history over all the devices I use to listen to music because I don’t use Spotify or YouTube Music. Think something like last.fm if you’ve ever used it, but a little simpler. please just imagine that you’ve been following along for a while now, i may or may not have forgotten to set up hackatime and log my work ; _ ; Anyways, the project is written in Go for the backend and Rust for the client library and the CLI that currently uses it. I’ve so far fleshed out the basic structure of what the data should look like, I have a database schema, yada yada… I also had FFI bindings so that I could use the client library from other code like WebAssembly so that I could have a web client! However… I’m currently going over the code, resolving some of the // TODO comments that I left for myself and kind of realized that the FFI is… completely… and utterly… out of date… So I deleted it. And I’m also going to rewrite parts of the FFI interface which just sort of duplicated the Rust-native structures with derive macros, which I’ve been wanting to learn for a long, long time now! …That is, when I get to it. For now, I’m going to try to get listhist into a functional state so that you (yes, YOU!) can try it out for yourself. Don’t worry, I won’t make you download anything, unless you decide you want to use listhist (wink wink) One of the main goals of the project is to make it easily self-hostable, so while I will provide an instance of my own, if you really like listhist, you will be able to do so easily with an OCI-compliant container image and maybe a Compose file. Thank you for reading this first devlog and I hope to see you here again!"}]...
|
Title: listhist by @staneko | Stardance
Devlogs:
Title: listhist by @staneko | Stardance
Devlogs:
Hi, I’m making a project to track my listening history over all the devices I use to listen to music because I don’t use Spotify or YouTube Music. Think something like last.fm if you’ve ever used it, but a little simpler. please just imagine that you’ve been following along for a while now, i may or may not have forgotten to set up hackatime and log my work ; _ ; Anyways, the project is written in Go for the backend and Rust for the client library and the CLI that currently uses it. I’ve so far fleshed out the basic structure of what the data should look like, I have a database schema, yada yada… I also had FFI bindings so that I could use the client library from other code like WebAssembly so that I could have a web client! However… I’m currently going over the code, resolving some of the // TODO comments that I left for myself and kind of realized that the FFI is… completely… and utterly… out of date… So I deleted it. And I’m also going to rewrite parts of the FFI interface which just sort of duplicated the Rust-native structures with derive macros, which I’ve been wanting to learn for a long, long time now! …That is, when I get to it. For now, I’m going to try to get listhist into a functional state so that you (yes, YOU!) can try it out for yourself. Don’t worry, I won’t make you download anything, unless you decide you want to use listhist (wink wink) One of the main goals of the project is to make it easily self-hostable, so while I will provide an instance of my own, if you really like listhist, you will be able to do so easily with an OCI-compliant container image and maybe a Compose file. Thank you for reading this first devlog and I hope to see you here again!
Welcome to my second devlog regarding listhist! Since the last entry, I’ve rewritten the shared client code to take advantage of the Rust type system much more. I’ve written quite a bit of Haskell in the past few weeks and I love the strong type system of the language; however, monadic I/O and especially the mixture of pure and impure exceptions makes my head hurt, which is why I decided to instead write this project mostly in Go and Rust. Either way, this means that without logging in, you can’t query endpoints which require an access token; so, for example, in order to create an album in the system, you have to do something like this: let client = listhist_client :: Client :: new ( "your_base_url" ); Now, client is of type Client<Unauthorized> . You can then call Client::login : let client = client .login ( "username" , "password" ) .await ? ; Now client is of type Client<Authorized> and you can actually create an album! let album = client .create_album ( ... ) .await ? ; Oh yeah, the client is now also asynchronous and therefore much more flexible… but that’s not as exciting. The other exciting thing that I managed to add to the repo is a Containerfile and a Compose file, so spinning up an instance, whether for testing or “for real” is super easy. So in this regard, I think I’ve achieved what I wrote about in the last entry. Now, the next step is polishing the existing code, resolving the TODO / FIXME items I have left for myself, adding some tests, etc. It’s boring work, but I believe that if I do it sooner than later, it will come back around and I can catch some of the more annoying bugs early on. And then I want to make a web interface for easy viewing of the data. The CLI should be the main way to enter listening history entries into the system, automatically of course (probably through MPRIS, custom player hooks and some Windows-specific mechanism), but viewing of the data should be possible from any device, without having to install the CLI. So, the web interface will be a relatively simple, fully client-sided web application, probably written with something like Preact. I have a lot of things planned for listhist, maybe even a friends system, which would be very exciting to have! Stay tuned for upcoming updates.
Welcome back to my listening history tracking project! You are now reading the third entry, and I’ve achieved a great milestone - the listening history tracking actually works. You can query your listening history and it will be fed back to you in JSON, supporting specific queries like a start date, an end date, a limit on the number of entries, etc. (i actually ran out of examples.) This JSON history endpoint does something that was very cool to implement; it gets the history entries, but obviously, those entries aren’t everything that a client needs to display them to the user. They consist merely of an entry ID, a track ID, and a date. The client would need to fetch the track details, then the album details, and then the artist details on its own, which would make for a lot of requests, considering that people usually listen to more than one track per day. So this would mean that, had the client not implemented some sort of caching, if you listened to, say, 25 tracks in a day and then queried your history, you would end up at a beautiful n_entries * len(["track", "album", "artist"]) = 25 * 3 = 75 requests! Which is insane. This listening history endpoint reduces this number to 1 . Yes, ONE request. This is done by directly including the necessary tracks, albums, and artists in the response, and the client can just iterate over the arrays of these resources and parse them into a hashmap keyed by their respective IDs. Pretty neat! So had you listened to a track, like “Keep The Streets Empty For Me” by Fever Ray from their album Fever Ray, the (prettified) response from the endpoint would look like this: { "entries" : [ { "id" : 3 , "track_id" : 8 , "date" : "2026-08-02T02:27:13.727572Z" } ], "tracks" : [ { "id" : 8 , "title" : "Keep The Streets Empty For Me" , "artist_id" : 2 , "album_id" : 4 , "genre" : "Electronic" } ], "albums" : [ { "id" : 4 , "name" : "Fever Ray" , "artist_id" : 2 } ], "artist" : [ { "id" : 2 , "name" : "Fever Ray" } ] } Looking at this, I’ve just realized that I probably need to make the genre column an array, since tracks usually exhibit properties of many different genres at once… that’s a problem for future me Obviously I’ve improved the code a bit here and there, the Compose configuration now actually makes the backend wait for the database so there isn’t a race condition (which may have been there for a few weeks…), and the data schema has changed a bit so that it makes more sense. There is now also a web app, but that is far from finished as it stands and so instead I’ve included a screenshot of the Firefox devtools I used to poke at my API and the successful response I finally got in the end....
|
1793490621.801794
|
1794095421.801794
|
|
44333
|
Sagitarius by @staneko | Stardance
|
staneko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Sagitarius by @staneko | Stardance
|
1793267646.4099236
|
1793872446.4099236
|
|
45250
|
blogus by @staneko | Stardance
|
staneko
|
0
|
5.58
|
0
|
[]
|
[{"post_id": 48089, "ts": "202 [{"post_id": 48089, "ts": "2026-08-16T11:42:10Z", "hours": 5.5767, "text": "blogus This is the first entry in the devlog of blogus , my static blog generator. I’ve laid the foundation of the project, which you can see in the screenshot. The binary reads the directory you give it (or the cwd). Then, it transforms the contained Markdown files into HTML. You can then access every article at <host>/<article-title> , with link support and scripting. Styling and font support is planned. I want to add support for hot-reloading and discovery of articles, recursive discovery (meaning you can nest articles into directories), and some other neat stuff. I’ll make a page with the planned features, so I can track it as well. It’s currently in a not-very-up-to-date text file, so that’s my next goal."}]...
|
Title: blogus by @staneko | Stardance
Devlogs:
bl Title: blogus by @staneko | Stardance
Devlogs:
blogus This is the first entry in the devlog of blogus , my static blog generator. I’ve laid the foundation of the project, which you can see in the screenshot. The binary reads the directory you give it (or the cwd). Then, it transforms the contained Markdown files into HTML. You can then access every article at <host>/<article-title> , with link support and scripting. Styling and font support is planned. I want to add support for hot-reloading and discovery of articles, recursive discovery (meaning you can nest articles into directories), and some other neat stuff. I’ll make a page with the planned features, so I can track it as well. It’s currently in a not-very-up-to-date text file, so that’s my next goal....
|
1793324906.2716424
|
1793929706.2716424
|
|
47239
|
What the Monad? by @staneko | Stardance
|
staneko
|
1
|
3.0
|
21
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-13T04:07:21Z", "hours": 3.0, "multiplier": 7.07, "payout": 21, "blessing": "neutral", "text": "I’ve written a write-up on what monads, as in the CS concept, actually are, how to use them, how to work with them, and how to appreciate them. I haven’t used any JS framework; the site is just static HTML with a bit of CSS. I’m pretty proud of my work so far, the site looks nice, and I believe I’ve also included a fair bit of additional reading for the interested.", "repo": "https://github.com/stanekondrej/what-the-monad", "demo": "https://wtm.stanek.lol"}]...
|
[{"post_id": 46118, "ts": "202 [{"post_id": 46118, "ts": "2026-08-13T03:58:39Z", "hours": 3.0006, "text": "What the Monad? - the first version I’ve just finished the first version of my write-up, “What the Monad?” (do i put an exclamation mark here after the quotes or what) Monads are something that is super interesting to me and actually made me want to study theoretical mathematics and category theory specifically in the future. They are one of the reasons I’ve fallen in love with Haskell; However, when I first encountered them very early on in my journey to Learn Me Some Haskell For Great Good, they baffled me. They seemed like an impenetrable, incomprehensible concept, but after I got familiar with them, I realized that they are actually not only pretty great, but also not too hard to grasp (at least as a CS concept… the category theory is still beyond me :D) I’ve seen many articles on this topic and even some videos on YouTube, but none of them explain them in quite the way I would like it. So, I’ve written this little write-up. It’s a simple static website with a sprinkle of CSS to make it easier to read. I will improve the examples in the write-up incrementally, but this is my first kind of “release” that I’m more or less content with."}]...
|
Title: What the Monad? by @staneko | Stardance
De Title: What the Monad? by @staneko | Stardance
Devlogs:
What the Monad? - the first version I’ve just finished the first version of my write-up, “What the Monad?” (do i put an exclamation mark here after the quotes or what) Monads are something that is super interesting to me and actually made me want to study theoretical mathematics and category theory specifically in the future. They are one of the reasons I’ve fallen in love with Haskell; However, when I first encountered them very early on in my journey to Learn Me Some Haskell For Great Good, they baffled me. They seemed like an impenetrable, incomprehensible concept, but after I got familiar with them, I realized that they are actually not only pretty great, but also not too hard to grasp (at least as a CS concept… the category theory is still beyond me :D) I’ve seen many articles on this topic and even some videos on YouTube, but none of them explain them in quite the way I would like it. So, I’ve written this little write-up. It’s a simple static website with a sprinkle of CSS to make it easier to read. I will improve the examples in the write-up incrementally, but this is my first kind of “release” that I’m more or less content with.
Ships:
I’ve written a write-up on what monads, as in the CS concept, actually are, how to use them, how to work with them, and how to appreciate them. I haven’t used any JS framework; the site is just static HTML with a bit of CSS. I’m pretty proud of my work so far, the site looks nice, and I believe I’ve also included a fair bit of additional reading for the interested....
|
1793857641.3563504
|
1793944041.3563504
|
|
47533
|
AndroidTmp by @staneko | Stardance
|
staneko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AndroidTmp by @staneko | Stardance
|
1793886676.1515028
|
1794491476.1515028
|
|
51250
|
ConsentTool by @staneko | Stardance
|
staneko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ConsentTool by @staneko | Stardance
|
1793382956.3515599
|
1793987756.3515599
|
|
24987
|
My awesome macropad! by @stand | Stardance
|
stand
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stand | Stardance
|
1793335859.9307668
|
1793940659.9307668
|
|
63355
|
My first slack bot! by @stancuvandrei1980 | Starda My first slack bot! by @stancuvandrei1980 | Stardance...
|
stancuvandrei1980
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @stancuvandrei1980 | Title: My first slack bot! by @stancuvandrei1980 | Stardance...
|
1793660184.018208
|
1794264984.018208
|
|
63470
|
DNA-Analizer by @stancuvandrei1980 | Stardance
|
stancuvandrei1980
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DNA-Analizer by @stancuvandrei1980 | Starda Title: DNA-Analizer by @stancuvandrei1980 | Stardance...
|
1793663327.7979255
|
1794268127.7979255
|
|
25994
|
My awesome macropad! by @stancupatrick13 | Stardan My awesome macropad! by @stancupatrick13 | Stardance...
|
stancupatrick13
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stancupatrick13 | Title: My awesome macropad! by @stancupatrick13 | Stardance...
|
1793533688.729994
|
1794138488.729994
|
|
42368
|
Frictionless by @stanciuilie09 | Stardance
|
stanciuilie09
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @stanciuilie09 | Stardance
|
1793854082.1316395
|
1794458882.1316395
|
|
42373
|
Auto-Seringe by @stanciuilie09 | Stardance
|
stanciuilie09
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Auto-Seringe by @stanciuilie09 | Stardance
|
1793854093.7323241
|
1794458893.7323241
|
|
46035
|
CYCLOIDAL DRIVE POINT GENERATOR by @stanciuilie09 CYCLOIDAL DRIVE POINT GENERATOR by @stanciuilie09 | Stardance...
|
stanciuilie09
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CYCLOIDAL DRIVE POINT GENERATOR by @stanciu Title: CYCLOIDAL DRIVE POINT GENERATOR by @stanciuilie09 | Stardance...
|
1793364843.415884
|
1793969643.415884
|
|
59046
|
my APOD site by @stalinhack | Stardance
|
stalinhack
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: my APOD site by @stalinhack | Stardance
|
1793526793.708977
|
1794131593.708977
|
|
6412
|
My awesome macropad! by @stalari | Stardance
|
stalari
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stalari | Stardanc Title: My awesome macropad! by @stalari | Stardance...
|
1793814833.9439828
|
1794419633.9439828
|
|
34400
|
Frictionless by @stagnantjass1 | Stardance
|
stagnantjass1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @stagnantjass1 | Stardance
|
1793767709.5684457
|
1794372509.5684457
|
|
59974
|
Untitled project by @staffa | Stardance
|
staffa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @staffa | Stardance
|
1793638492.0744116
|
1794243292.0744116
|
|
50539
|
My awesome macropad! by @stabish | Stardance
|
stabish
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stabish | Stardanc Title: My awesome macropad! by @stabish | Stardance...
|
1793346836.8160346
|
1793951636.8160346
|
|
4068
|
Untitled project by @st4r21722 | Stardance
|
st4r21722
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @st4r21722 | Stardance
|
1793832481.9334457
|
1794437281.9334457
|
|
6529
|
My first slack bot! by @st4r21722 | Stardance
|
st4r21722
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @st4r21722 | Stardan Title: My first slack bot! by @st4r21722 | Stardance...
|
1793512593.0783334
|
1794117393.0783334
|
|
39269
|
sub 250 g rocket drone by @st28052010 | Stardance
|
st28052010
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: sub 250 g rocket drone by @st28052010 | Sta Title: sub 250 g rocket drone by @st28052010 | Stardance...
|
1793289427.4733963
|
1793894227.4733963
|
|
57467
|
Glimpses of India by @sswatthakur778 | Stardance
|
sswatthakur778
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Glimpses of India by @sswatthakur778 | Star Title: Glimpses of India by @sswatthakur778 | Stardance...
|
1793440506.7427928
|
1794045306.7427928
|
|
48832
|
My own site! by @ssup_pankaj | Stardance
|
ssup_pankaj
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @ssup_pankaj | Stardance
|
1793249278.102815
|
1793854078.102815
|
|
20276
|
My awesome macropad! by @ssulaymon18 | Stardance
|
ssulaymon18
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ssulaymon18 | Star Title: My awesome macropad! by @ssulaymon18 | Stardance...
|
1793321747.6534796
|
1793926547.6534796
|
|
20277
|
Untitled by @ssulaymon18 | Stardance
|
ssulaymon18
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ssulaymon18 | Stardance
|
1793357621.4254518
|
1793962421.4254518
|
|
20672
|
My very own WebOS by @ssulaymon18 | Stardance
|
ssulaymon18
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @ssulaymon18 | Stardan Title: My very own WebOS by @ssulaymon18 | Stardance...
|
1793523425.3345513
|
1794128225.3345513
|
|
22631
|
Khiva website by @ssulaymon18 | Stardance
|
ssulaymon18
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Khiva website by @ssulaymon18 | Stardance
|
1793911869.788976
|
1794516669.788976
|
|
54609
|
MacPad by @sst | Stardance
|
sst
|
0
|
3.7
|
0
|
[]
|
[{"post_id": 57680, "ts": "202 [{"post_id": 57680, "ts": "2026-08-29T22:16:03Z", "hours": 1.7833, "text": "PCB Design After a grueling 2 hours of figuring out how to use KiCad’s designing system, I finally completed the PCB. The hardest part was definitely figuring out the wiring… and getting familiar with the tools of the app. I tried to place the XIAO 2040 on the bottom of the board… but I ran into way too many problems. I figured I’d rather just move it to the side and have a nice place to add art / rest my hand :) As for the use cases of this macropad, I plan on using it for three main things: a: shortcuts on my computer (obvi), b: CONTROLLING MY KINDLE! You can set up an HTTP server on your kindle if its jailbroken, using koreader. I plan on connecting the MacPad to a Rasberry Pi, which will sort of be the control hub, and that PI will send the signals to my kindle."}, {"post_id": 56791, "ts": "2026-08-28T18:24:55Z", "hours": 1.1833, "text": "Finished the first step. After learning the basics of KiCad and watching some tutorials, I finally completed the PCB schematic. I managed to fit all my components in – an LCD, 9 switches and a rotary encoder WITH the switch – into the 11 GPIO pins the Xiao board offers. Excited to complete this build!"}, {"post_id": 56191, "ts": "2026-08-27T20:34:55Z", "hours": 0.7333, "text": "First Entry - The Tutorial My goal is to make a sleek, and minimal keypad that captures the design of apple products while still maintaining the customizability of custom keyboards. Today, I focused on setting up KiCad (which was way harder than I anticipated) and completing the tutorial. I now have a pretty decent understanding of how to wire everything together."}]...
|
Title: MacPad by @sst | Stardance
Devlogs:
First Title: MacPad by @sst | Stardance
Devlogs:
First Entry - The Tutorial My goal is to make a sleek, and minimal keypad that captures the design of apple products while still maintaining the customizability of custom keyboards. Today, I focused on setting up KiCad (which was way harder than I anticipated) and completing the tutorial. I now have a pretty decent understanding of how to wire everything together.
Finished the first step. After learning the basics of KiCad and watching some tutorials, I finally completed the PCB schematic. I managed to fit all my components in – an LCD, 9 switches and a rotary encoder WITH the switch – into the 11 GPIO pins the Xiao board offers. Excited to complete this build!
PCB Design After a grueling 2 hours of figuring out how to use KiCad’s designing system, I finally completed the PCB. The hardest part was definitely figuring out the wiring… and getting familiar with the tools of the app. I tried to place the XIAO 2040 on the bottom of the board… but I ran into way too many problems. I figured I’d rather just move it to the side and have a nice place to add art / rest my hand :) As for the use cases of this macropad, I plan on using it for three main things: a: shortcuts on my computer (obvi), b: CONTROLLING MY KINDLE! You can set up an HTTP server on your kindle if its jailbroken, using koreader. I plan on connecting the MacPad to a Rasberry Pi, which will sort of be the control hub, and that PI will send the signals to my kindle....
|
1793555408.7101789
|
1794160208.7101789
|
|
27214
|
My awesome macropad! by @ssstttccchhh | Stardance
|
ssstttccchhh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ssstttccchhh | Sta Title: My awesome macropad! by @ssstttccchhh | Stardance...
|
1793955213.1583645
|
1794560013.1583645
|