|
19881
|
My very own WebOS by @Jerry_Yan | Stardance
|
Jerry_Yan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Jerry_Yan | Stardance
|
1793191944.1883383
|
1793796744.1883383
|
|
8250
|
My awesome macropad! by @rafaelmaradiaga4_8469 | S My awesome macropad! by @rafaelmaradiaga4_8469 | Stardance...
|
rafaelmaradiaga4_8469
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @rafaelmaradiaga4_8 Title: My awesome macropad! by @rafaelmaradiaga4_8469 | Stardance...
|
1793191943.2967994
|
1793796743.2967994
|
|
21491
|
My first slack bot! by @Dibyanjali | Stardance
|
Dibyanjali
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Dibyanjali | Starda Title: My first slack bot! by @Dibyanjali | Stardance...
|
1793191942.3286347
|
1793796742.3286347
|
|
29392
|
My very own WebOS by @Griffin_Olowin | Stardance
|
Griffin_Olowin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Griffin_Olowin | Star Title: My very own WebOS by @Griffin_Olowin | Stardance...
|
1793191940.1947036
|
1793796740.1947036
|
|
3181
|
My first slack bot! by @Intersected | Stardance
|
Intersected
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Intersected | Stard Title: My first slack bot! by @Intersected | Stardance...
|
1793191939.2522337
|
1793796739.2522337
|
|
11591
|
My awesome macropad! by @SUGAR_SUGAR | Stardance
|
SUGAR_SUGAR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @SUGAR_SUGAR | Star Title: My awesome macropad! by @SUGAR_SUGAR | Stardance...
|
1793191938.3524423
|
1793796738.3524423
|
|
35226
|
Tuyère aerospike by @Scrapeur34 | Stardance
|
Scrapeur34
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Tuyère aerospike by @Scrapeur34 | Stardance
|
1793191937.4690633
|
1793796737.4690633
|
|
21178
|
Untitled by @kinseyrubenstein | Stardance
|
kinseyrubenstein
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @kinseyrubenstein | Stardance
|
1793191934.7679899
|
1793796734.7679899
|
|
35162
|
DevOS by @UpprCut | Stardance
|
UpprCut
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DevOS by @UpprCut | Stardance
|
1793191933.8365076
|
1793796733.8365076
|
|
14590
|
My awesome macropad! by @Seba | Stardance
|
Seba
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Seba | Stardance
|
1793191932.9391685
|
1793796732.9391685
|
|
8860
|
My first slack bot! by @Raghib | Stardance
|
Raghib
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Raghib | Stardance
|
1793191932.027949
|
1793796732.027949
|
|
35751
|
Promptly by @muhamm38 | Stardance
|
muhamm38
|
0
|
8.61
|
0
|
[]
|
[{"post_id": 76884, "ts": "202 [{"post_id": 76884, "ts": "2026-10-04T22:42:12Z", "hours": 1.88, "text": "Devlog 4 Added saving assignments and marking them complete functionality I’ve made it so assignments save to a JSON file and load when the app is opened. Before this, everything disappeared when I restarted the app. Now when you add an assignment its saved permanently. I also added the ability to mark assignments as complete. I moved the icon to the right side of the card and added a button on the left. When pressed the assignment disapears and goes into the dropdown where completed assignments are. I made it so only the title shows up because the other information isn’t necessary when it’s completed. Lastly, I made it so you can delete assignments permanently by pressing and holding on them. It shows a delete popup and you can delete it from there. That’s all for today! I’ve made a lot of progress and this app is truly building up. The AI input and notifications are still ahead, but the manual assignment flow is becoming more usable. Thanks for reading!"}, {"post_id": 74632, "ts": "2026-09-27T20:26:04Z", "hours": 0.9711, "text": "Devlog 3 Added assignment adding functionality I finished the manual assignment adding for the app. Now when u click the + button in the bottom left corner, a popup shows up where you can input the information to add an assignment. You can add assignment name, class name, due date, and the color you want it to be! I’ve been learning how to use an array to hold the assignments and ForEach to display a card for each one. I was confused at first about how the information would get from the popup to the cards, so seeing something I typed actually appear on the main screen helped it make more sense. I also added the class name field and color picker using what I’d learned from the assignment name field. Once you click save it shows up on the home menu as an assignment card. Right now it saves just for that session so when the canvas is reloaded it all dissapears. Next I’ll be adding saving functionality across multiple sessions so your assignments actually save. After that I’ll be implementing the AI model that can auto create assignments based on screenshots, text, syllabuses, pdfs, etc. I also want to add a dropdown for saved classes so you don’t have to type the same class name every time and an icon picker. Thank you for reading!"}, {"post_id": 72842, "ts": "2026-09-23T20:59:27Z", "hours": 4.1969, "text": "Devlog 2 Moved from Tauri to Xcode. I’ve decided to make an iOS app instead of a desktop app. I made this decision because I feel that there are a lot more resources to help me learn Xcode in comparison to Tauri which doesn’t have that many tutorials and things. I have done a few tutorials and am now redesigning the app in Xcode. I’ve chosen this style for the assignments and added a popup window in the bottom left that when clicked opens up a popup. This popup will be used for adding new assignments and eventually for housing the AI model that will auto generate tasks. This move to Xcode took me a while but I think it will be a good one in the long run especially because phone notifications are looked at way more than desktop ones and I think it will be much better overall. Thanks for reading!"}, {"post_id": 29124, "ts": "2026-07-15T19:48:48Z", "hours": 1.5622, "text": "Devlog 1 I set up the project using Tauri. I chose Tauri because it allows for very lightweight and fast projects to be made. I built a clean simple ui using HTML and CSS styling. It has a simple text area where you can input assignment information and then generate reminders from that. I used OpenRouter free API to integrate AI into it. The app is currently using Google’s free Gemma 4 model. Right now it just takes messy text and returns a clean list of due dates. Next Steps: Convert the AI output to clickable checkboxes to make it tasks you can complete. Use Tauri plugins to add notifications Add screenshot support Flesh out ui more and add a bunch of QOL features. That is all, thank you for reading my 1st devlog!"}]...
|
Title: Promptly by @muhamm38 | Stardance
Devlogs: Title: Promptly by @muhamm38 | Stardance
Devlogs:
Devlog 1 I set up the project using Tauri. I chose Tauri because it allows for very lightweight and fast projects to be made. I built a clean simple ui using HTML and CSS styling. It has a simple text area where you can input assignment information and then generate reminders from that. I used OpenRouter free API to integrate AI into it. The app is currently using Google’s free Gemma 4 model. Right now it just takes messy text and returns a clean list of due dates. Next Steps: Convert the AI output to clickable checkboxes to make it tasks you can complete. Use Tauri plugins to add notifications Add screenshot support Flesh out ui more and add a bunch of QOL features. That is all, thank you for reading my 1st devlog!
Devlog 2 Moved from Tauri to Xcode. I’ve decided to make an iOS app instead of a desktop app. I made this decision because I feel that there are a lot more resources to help me learn Xcode in comparison to Tauri which doesn’t have that many tutorials and things. I have done a few tutorials and am now redesigning the app in Xcode. I’ve chosen this style for the assignments and added a popup window in the bottom left that when clicked opens up a popup. This popup will be used for adding new assignments and eventually for housing the AI model that will auto generate tasks. This move to Xcode took me a while but I think it will be a good one in the long run especially because phone notifications are looked at way more than desktop ones and I think it will be much better overall. Thanks for reading!
Devlog 3 Added assignment adding functionality I finished the manual assignment adding for the app. Now when u click the + button in the bottom left corner, a popup shows up where you can input the information to add an assignment. You can add assignment name, class name, due date, and the color you want it to be! I’ve been learning how to use an array to hold the assignments and ForEach to display a card for each one. I was confused at first about how the information would get from the popup to the cards, so seeing something I typed actually appear on the main screen helped it make more sense. I also added the class name field and color picker using what I’d learned from the assignment name field. Once you click save it shows up on the home menu as an assignment card. Right now it saves just for that session so when the canvas is reloaded it all dissapears. Next I’ll be adding saving functionality across multiple sessions so your assignments actually save. After that I’ll be implementing the AI model that can auto create assignments based on screenshots, text, syllabuses, pdfs, etc. I also want to add a dropdown for saved classes so you don’t have to type the same class name every time and an icon picker. Thank you for reading!
Devlog 4 Added saving assignments and marking them complete functionality I’ve made it so assignments save to a JSON file and load when the app is opened. Before this, everything disappeared when I restarted the app. Now when you add an assignment its saved permanently. I also added the ability to mark assignments as complete. I moved the icon to the right side of the card and added a button on the left. When pressed the assignment disapears and goes into the dropdown where completed assignments are. I made it so only the title shows up because the other information isn’t necessary when it’s completed. Lastly, I made it so you can delete assignments permanently by pressing and holding on them. It shows a delete popup and you can delete it from there. That’s all for today! I’ve made a lot of progress and this app is truly building up. The AI input and notifications are still ahead, but the manual assignment flow is becoming more usable. Thanks for reading!...
|
1793191931.107142
|
1793796731.107142
|
|
29386
|
My awesome macropad! by @afee | Stardance
|
afee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @afee | Stardance
|
1793191930.173599
|
1793796730.173599
|
|
22106
|
Untitled by @srideetya | Stardance
|
srideetya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @srideetya | Stardance
|
1793191929.2523723
|
1793796729.2523723
|
|
18600
|
morse code translator by @hackervyralz | Stardance
|
hackervyralz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: morse code translator by @hackervyralz | St Title: morse code translator by @hackervyralz | Stardance...
|
1793191928.3760004
|
1793796728.3760004
|
|
21410
|
Untitled project by @al_fayzi_zabran | Stardance
|
al_fayzi_zabran
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @al_fayzi_zabran | Star Title: Untitled project by @al_fayzi_zabran | Stardance...
|
1793191927.4788294
|
1793796727.4788294
|
|
36666
|
Untitled project by @Abi123 | Stardance
|
Abi123
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Abi123 | Stardance
|
1793191926.5268366
|
1793796726.5268366
|
|
30115
|
My own site! by @Clement | Stardance
|
Clement
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @Clement | Stardance
|
1793191925.5872557
|
1793796725.5872557
|
|
34815
|
cool by @arthro209 | Stardance
|
arthro209
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: cool by @arthro209 | Stardance
|
1793191924.676017
|
1793796724.676017
|
|
13757
|
Mini Synth by @anis_redmond | Stardance
|
anis_redmond
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mini Synth by @anis_redmond | Stardance
|
1793191923.7495828
|
1793796723.7495828
|
|
33781
|
Untitled project by @m0in | Stardance
|
m0in
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @m0in | Stardance
|
1793191922.8469307
|
1793796722.8469307
|
|
15591
|
My very own WebOS by @Ol1ve | Stardance
|
Ol1ve
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Ol1ve | Stardance
|
1793191921.9646256
|
1793796721.9646256
|
|
2830
|
My first slack bot! by @rojen | Stardance
|
rojen
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @rojen | Stardance
|
1793191921.0340009
|
1793796721.0340009
|
|
26688
|
crash stopper by @colorblinder | Stardance
|
colorblinder
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: crash stopper by @colorblinder | Stardance
|
1793191920.1611564
|
1793796720.1611564
|
|
7926
|
Fate and Fortune by @Kit | Stardance
|
Kit
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fate and Fortune by @Kit | Stardance
|
1793191919.28719
|
1793796719.28719
|
|
10486
|
My awesome macropad! by @srinivasvardhancs8 | Star My awesome macropad! by @srinivasvardhancs8 | Stardance...
|
srinivasvardhancs8
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @srinivasvardhancs8 Title: My awesome macropad! by @srinivasvardhancs8 | Stardance...
|
1793191918.3947408
|
1793796718.3947408
|
|
20871
|
Untitled project by @Trisha | Stardance
|
Trisha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Trisha | Stardance
|
1793191917.4701645
|
1793796717.4701645
|
|
19530
|
My awesome macropad! by @anayvinodmetha | Stardanc My awesome macropad! by @anayvinodmetha | Stardance...
|
anayvinodmetha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @anayvinodmetha | S Title: My awesome macropad! by @anayvinodmetha | Stardance...
|
1793191916.5306635
|
1793796716.5306635
|
|
37655
|
My very own WebOS by @zamborinorman2010 | Stardanc My very own WebOS by @zamborinorman2010 | Stardance...
|
zamborinorman2010
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zamborinorman2010 | S Title: My very own WebOS by @zamborinorman2010 | Stardance...
|
1793191915.6499884
|
1793796715.6499884
|
|
8230
|
MediaNodeRE by @ | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: MediaNodeRE by @ | Stardance
|
1793191914.6876915
|
1793796714.6876915
|
|
3852
|
Untitled project by @yatharth_khurjal | Stardance
|
yatharth_khurjal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @yatharth_khurjal | Sta Title: Untitled project by @yatharth_khurjal | Stardance...
|
1793191913.8054388
|
1793796713.8054388
|
|
22518
|
My awesome macropad! by @vihaankorat287 | Stardanc My awesome macropad! by @vihaankorat287 | Stardance...
|
vihaankorat287
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @vihaankorat287 | S Title: My awesome macropad! by @vihaankorat287 | Stardance...
|
1793191912.928319
|
1793796712.928319
|
|
38657
|
My own site! by @Jessii | Stardance
|
Jessii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @Jessii | Stardance
|
1793191912.053779
|
1793796712.053779
|
|
33379
|
My own site! by @calum_t | Stardance
|
calum_t
|
0
|
1.1
|
0
|
[]
|
[{"post_id": 25956, "ts": "202 [{"post_id": 25956, "ts": "2026-07-10T14:07:53Z", "hours": 1.1017, "text": "Today i started creating the initial layout for my website and also started working on the initial navigation of the web page"}]...
|
Title: My own site! by @calum_t | Stardance
Devlo Title: My own site! by @calum_t | Stardance
Devlogs:
Today i started creating the initial layout for my website and also started working on the initial navigation of the web page...
|
1793191911.1623366
|
1793796711.1623366
|
|
5326
|
Untitled project by @fra | Stardance
|
fra
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @fra | Stardance
|
1793191910.2825289
|
1793796710.2825289
|
|
31615
|
SlickSlackSloe by @IHaveQuestions | Stardance
|
IHaveQuestions
|
0
|
4.46
|
0
|
[]
|
[{"post_id": 24364, "ts": "202 [{"post_id": 24364, "ts": "2026-07-07T21:33:08Z", "hours": 1.9919, "text": "A Lot Of DuckDuckGoing Shortly after my last devlog I found out about Slack block kits. It took a bit of trial and error but I managed to make a matrix of buttons which I will use as the board itself. The action_id troubles I wanted to be able to see which button was pressed. For this I was going to use the action_id from the response payload. It took me a while to figure out how to get it because action_id is not a part of body (either is response_url and many other values that are actually a part of body ) according to VScode but they actually are. Ephemeral Messages I figured that the board shouldn’t be able to be interacted with by anyone so I got the idea to make the message “Only visible to you”. It took me a bit of DuckDuckGoing to get it to work but it works."}, {"post_id": 24185, "ts": "2026-07-07T16:15:27Z", "hours": 2.0656, "text": "Decisions, decisions My first decision was to rewrite the bot in Typescript because I have a bit more experience with it. It took a bit of troubleshooting but I got it working in the end. My second decision was to decide the command syntax. After very little thought I came up with /slickslacksloe command [argument] . This basically means that commands have the syntax /command [argument] but with the prefix slickslacksloe so it’s actually findable in Slack. The first command I made was the /slickslacksloe help command. It displays all available commands and gives a short description. I still haven’t fully decided about how I should show what values arguments can have. Right now its <value1, value2, valueN> but it’s not super clear and it’s a bit ugly. What’s next? I will make a pfp for the bot but that will probably take a while to get to. I’m thinking that the next step will probably be making some tic-tac-toe logic. Storing the board, handling win/lose conditions, and handling several games (from different) users at the same time. I might rework it a bit and make the only command start and make the game be controlled with reactions but I’m not sure."}, {"post_id": 24099, "ts": "2026-07-07T13:41:29Z", "hours": 0.3986, "text": "The Journey Begins I followed the first half of the Slack bot guide. I had some errors because I used quotation mark instead of a backtick. Time to start working on the tic-tac-toe logic."}]...
|
Title: SlickSlackSloe by @IHaveQuestions | Stardan Title: SlickSlackSloe by @IHaveQuestions | Stardance
Devlogs:
The Journey Begins I followed the first half of the Slack bot guide. I had some errors because I used quotation mark instead of a backtick. Time to start working on the tic-tac-toe logic.
Decisions, decisions My first decision was to rewrite the bot in Typescript because I have a bit more experience with it. It took a bit of troubleshooting but I got it working in the end. My second decision was to decide the command syntax. After very little thought I came up with /slickslacksloe command [argument] . This basically means that commands have the syntax /command [argument] but with the prefix slickslacksloe so it’s actually findable in Slack. The first command I made was the /slickslacksloe help command. It displays all available commands and gives a short description. I still haven’t fully decided about how I should show what values arguments can have. Right now its <value1, value2, valueN> but it’s not super clear and it’s a bit ugly. What’s next? I will make a pfp for the bot but that will probably take a while to get to. I’m thinking that the next step will probably be making some tic-tac-toe logic. Storing the board, handling win/lose conditions, and handling several games (from different) users at the same time. I might rework it a bit and make the only command start and make the game be controlled with reactions but I’m not sure.
A Lot Of DuckDuckGoing Shortly after my last devlog I found out about Slack block kits. It took a bit of trial and error but I managed to make a matrix of buttons which I will use as the board itself. The action_id troubles I wanted to be able to see which button was pressed. For this I was going to use the action_id from the response payload. It took me a while to figure out how to get it because action_id is not a part of body (either is response_url and many other values that are actually a part of body ) according to VScode but they actually are. Ephemeral Messages I figured that the board shouldn’t be able to be interacted with by anyone so I got the idea to make the message “Only visible to you”. It took me a bit of DuckDuckGoing to get it to work but it works....
|
1793191909.3376245
|
1793796709.3376245
|
|
7240
|
@lumilla/archivemanager by @lumilla | Stardance
|
lumilla
|
0
|
7.01
|
0
|
[]
|
[{"post_id": 5838, "ts": "2026 [{"post_id": 5838, "ts": "2026-06-09T19:37:43Z", "hours": 4.6114, "text": "Escaping the Fever Dream I’ve moved from Slint to egui for the UI, and I’m feeling much better about it, actually. Don’t get me wrong, slint is very cool, but egui is just easier, has more pre-made libraries and and I’m also a huge fan of the “window-within-a-window” aesthetic (because it feels enterprise) How I managed to spend most of the time was battling with a fever dream. CIDOC CRM is the “International Standard” for cultural heritage data. On paper, it’s perfect and just the thing I want for this. In practice however, it’s… well, a nightmare, let’s say that. I tried to migrate to SurrealDB, since migrating to CIDOC would’ve really required a graph-based database. That went absolutely nowhere at all and I never want to see a graph DB again. Lessons were learned. I now have a working prototype that displays a paginated list of items from the database. It’s rough, but hey it’s something."}, {"post_id": 2298, "ts": "2026-06-04T18:22:52Z", "hours": 2.3958, "text": "Escaping Excel I now kind of run of my local museum. Our current collection management system is a chaotic mess of Excel sheets where item descriptions, dimensions, and statuses are crammed intounorganizeds column. Commercial software vendors want an absurd amount of money to fix this. Screw that. @lumilla /archivemanager aims to be a open-source desktop app to fix this. At this time I spent two and a half hours-ish drafting the foundation of what it will be. I opted to go with Rust to learn new stuff, and because it’s hot and trendy. I have never properly written anything like this before, so I read a lot of docs for my stack of choice (Slint, SeaORM). Learned a lot of new stuff, (e.g. Rust does not want a semicolon on whatever a function returns), came across weird “STATUS_HEAP_CORRUPTION” errors that ceased to exist the moment I tried to fix them. Next up is the real functionality, currently the app is just a rough UI that creates a SQLite database."}]...
|
Title: @lumilla/archivemanager by @lumilla | Stard Title: @lumilla/archivemanager by @lumilla | Stardance
Devlogs:
Escaping Excel I now kind of run of my local museum. Our current collection management system is a chaotic mess of Excel sheets where item descriptions, dimensions, and statuses are crammed intounorganizeds column. Commercial software vendors want an absurd amount of money to fix this. Screw that. @lumilla /archivemanager aims to be a open-source desktop app to fix this. At this time I spent two and a half hours-ish drafting the foundation of what it will be. I opted to go with Rust to learn new stuff, and because it’s hot and trendy. I have never properly written anything like this before, so I read a lot of docs for my stack of choice (Slint, SeaORM). Learned a lot of new stuff, (e.g. Rust does not want a semicolon on whatever a function returns), came across weird “STATUS_HEAP_CORRUPTION” errors that ceased to exist the moment I tried to fix them. Next up is the real functionality, currently the app is just a rough UI that creates a SQLite database.
Escaping the Fever Dream I’ve moved from Slint to egui for the UI, and I’m feeling much better about it, actually. Don’t get me wrong, slint is very cool, but egui is just easier, has more pre-made libraries and and I’m also a huge fan of the “window-within-a-window” aesthetic (because it feels enterprise) How I managed to spend most of the time was battling with a fever dream. CIDOC CRM is the “International Standard” for cultural heritage data. On paper, it’s perfect and just the thing I want for this. In practice however, it’s… well, a nightmare, let’s say that. I tried to migrate to SurrealDB, since migrating to CIDOC would’ve really required a graph-based database. That went absolutely nowhere at all and I never want to see a graph DB again. Lessons were learned. I now have a working prototype that displays a paginated list of items from the database. It’s rough, but hey it’s something....
|
1793191908.3838856
|
1793796708.3838856
|
|
2623
|
My awesome macropad! by @yeshwanth_purusothaman | My awesome macropad! by @yeshwanth_purusothaman | Stardance...
|
yeshwanth_purusothaman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @yeshwanth_purusoth Title: My awesome macropad! by @yeshwanth_purusothaman | Stardance...
|
1793191907.4652615
|
1793796707.4652615
|
|
14587
|
Core XY Pen Plotter by @M01stBread | Stardance
|
M01stBread
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Core XY Pen Plotter by @M01stBread | Starda Title: Core XY Pen Plotter by @M01stBread | Stardance...
|
1793191906.5749207
|
1793796706.5749207
|
|
21845
|
Untitled by @Siddak | Stardance
|
Siddak
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Siddak | Stardance
|
1793191905.6366196
|
1793796705.6366196
|
|
23108
|
My awesome macropad! by @MarkHabib | Stardance
|
MarkHabib
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @MarkHabib | Starda Title: My awesome macropad! by @MarkHabib | Stardance...
|
1793191901.8303964
|
1793796701.8303964
|
|
31445
|
Robotic Arm by @shashvat | Stardance
|
shashvat
|
0
|
38.93
|
0
|
[]
|
[{"post_id": 44949, "ts": "202 [{"post_id": 44949, "ts": "2026-08-11T01:40:34Z", "hours": 3.6514, "text": "Devlog – Day 18 Date: August 9, 2026 Time Worked: 2 hours Today I fixed the wiring issue from my previous session. After tracing through the circuit, I found that the connections were mixed up. Once I corrected the wiring, the servos started responding properly. I then worked with the Bluepad32 library and wrote code that allows an Xbox controller’s joysticks and buttons to control the servos. I ran into several setup and communication issues, but I worked through them and completed the full controller code. With the wiring fixed and the code completed, the project is now ready for the physical build once funding is approved. Next Steps Order the required parts. Begin 3D printing the robotic arm components. Start assembling the arm."}, {"post_id": 44092, "ts": "2026-08-09T17:00:21Z", "hours": 2.2172, "text": "Devlog – Day 17 Date: August 8, 2026 Time Worked: 2 hours Today I started learning how to wire and program servos using an ESP32 in Cirkit. I began with simple push buttons instead of immediately using Bluepad32 and a gaming controller so I could understand the basic wiring and servo control first. I successfully got one servo working, confirming that my basic wiring and code were correct. I also identified a wiring issue with the other servos that I wasn’t able to fix today. I learned more about ESP32 pins, servo-control functions, and how the different components need to be connected. Next Steps Fix the wiring issue with the other servos. Continue practicing servo control. Start learning how to use Bluepad32 with a gaming controller."}, {"post_id": 36573, "ts": "2026-07-28T19:40:48Z", "hours": 8.0378, "text": "Devlog – Day 1 Date: July 27, 2026 Time Worked: 4 hours Today I began planning my custom quadcopter drone project by researching how the entire system works before selecting any parts. I learned how the flight controller, ESCs, motors, GPS, receiver, battery, and power distribution board work together, and compared different options for building a custom transmitter. By the end of the session, I had established the project’s main goals, selected the overall system architecture, and identified the next components to research. Next Steps Select the drone hardware. Research the custom transmitter electronics. Create a complete bill of materials. Begin designing the transmitter enclosure. Devlog – Day 2 Date: July 28, 2026 Time Worked: 4 hours Today I finalized the major hardware for both the drone and the custom controller. I selected the flight stack, motors, propellers, battery, GPS module, and the controller electronics, including the ESP32-C3, HC-12 radio module, battery, charging circuit, and joysticks. I also finalized the project’s electrical architecture, estimated the total project cost, and prepared to move into the CAD design phase. Next Steps Design the carbon fiber drone frame. Design the custom controller enclosure. Create the wiring diagrams. Note: I am posting these updates in my Robotics Arm project section because I accidentally recorded the project time there."}, {"post_id": 35597, "ts": "2026-07-27T04:04:06Z", "hours": 1.7844, "text": "Day 16 – Robotics Arm Project Time Worked: 1 hour 47 min Today I focused on improving the realism and accuracy of my robotic arm CAD assembly. The M3 screw holes and brass heat-set insert mounting points were already designed, so I created CAD models of the actual M3 screws and brass heat-set inserts and added them into the assembly. Adding the hardware models helped me visualize how the final robotic arm will be assembled and gave a more accurate representation of the finished design. While adding these components, I noticed a few small design issues that were not obvious before. Checking the screws and inserts against the parts helped me verify clearances, mounting positions, and overall fit. I fixed these issues before printing to prevent problems during assembly. Next Steps Apply for the Stardance grant once the application system is available again. Submit the design application when the form is working. Order the parts after confirming the budget. Begin the physical build once the parts arrive."}, {"post_id": 34989, "ts": "2026-07-26T04:13:11Z", "hours": 2.5011, "text": "Day 15 – Robotics Arm Project Time Worked: 2.5 hours Today I finalized the bill of materials (BOM) for my robotic arm project and confirmed that all of the required components had been selected. I replaced several Amazon.com items with Amazon.ca alternatives to reduce shipping costs and added a 5x20mm inline fuse kit to protect the ESP32. I also verified that my selected wire and MG90S servos matched my design requirements, so no CAD changes are needed. By the end of the session, the project cost was estimated at $257.10 CAD, and the planning stage was essentially complete. Next Steps: Make the final CAD improvements. Apply for the project grant. Order the parts once funding is approved. Begin the physical build after the parts arrive."}, {"post_id": 34440, "ts": "2026-07-25T04:48:52Z", "hours": 2.76, "text": "Day 14 — Robotic Arm Project Time spent: 2.5 hours Today I worked on creating an animation of my robotic arm to better visualize how all of the joints move together before building the physical prototype. I explored several approaches, including exporting the CAD model for simulation in PyBullet, but ran into issues with the assembly not exporting correctly due to missing joint definitions and material properties. Instead, I used Onshape’s Gear Relation feature to synchronize the movement of multiple joints, allowing me to create a smooth animation driven by a single input. This gave me a simple way to demonstrate the arm’s motion and better understand how the overall mechanism behaves. Next, I’ll continue refining the CAD assembly, prepare the design for 3D printing, and complete the remaining project documentation."}, {"post_id": 33869, "ts": "2026-07-24T04:18:55Z", "hours": 3.2172, "text": "Day 13 — Robotics Arm Project Time spent: 3 hours Today I shifted my focus from designing new parts to improving and validating the existing CAD model. I reviewed every component of the robotic arm, corrected several design issues, and refined parts to improve their fit and overall manufacturability. I also planned the wire routing for the arm, making sure each joint would have enough slack for its full range of motion while reducing the risk of wires being pinched during operation. To finish the session, I began preparing the arm for simulation by exporting the assembly from Onshape using the onshape-to-robot exporter. During this process, I discovered that my assembly mates and material properties still need to be configured correctly before the robot can be successfully simulated in PyBullet. Next, I’ll fix the assembly mates, assign materials to every part, and begin testing the robotic arm in simulation."}, {"post_id": 33326, "ts": "2026-07-23T04:16:34Z", "hours": 2.3856, "text": "Day 12 — Robotics Arm Project Time spent: 2 hours Today I finished troubleshooting the remaining gear meshing issues and completed the full CAD assembly of the robotic arm. After correcting both the gear center distance and tooth alignment, the gears meshed consistently throughout their full range of motion. With those issues resolved, the entire assembly is now functional. The base, shoulder, elbow, wrist, and gripper all move as intended, and the gear-driven parallelogram gripper operates correctly. Next, I’ll perform a final review of every part by checking dimensions against the actual hardware specifications, make any final adjustments if needed, and finish the bill of materials before preparing the design for manufacturing."}, {"post_id": 32684, "ts": "2026-07-22T00:15:49Z", "hours": 4.5364, "text": "Day 11 — Robotics Arm Project Time spent: 4 hours Today’s focus was on finishing the robotic arm’s gripper. After working through several design and assembly issues, I completed a gear-driven parallelogram gripper that keeps the jaws parallel as they open and close. Most of the session was spent troubleshooting gear meshing and assembly constraints. After adjusting the gear alignment and correcting the center distance, the mechanism operated smoothly. I also removed an unnecessary assembly constraint that was causing conflicts, allowing the four-bar linkage to function as intended. Next, I’ll address the remaining issues discovered during testing, finish the full arm assembly, and continue validating the gripper’s motion before moving on to manufacturing."}, {"post_id": 32172, "ts": "2026-07-21T04:53:00Z", "hours": 2.6186, "text": "Day 10 — Robotic Arm Design Time spent: 2 hours 25 minutes Today’s work was focused on designing the robotic arm’s gripper. I finalized the parallel-jaw gripper design after comparing various end-effector options over the past two days. Most of my time was spent positioning the servo inside the gripper housing and designing the gear mechanism that opens and closes the jaws while ensuring everything fit together correctly. Next, I’ll finish the remaining gripper components, verify the gear alignment, and continue completing the full CAD assembly."}, {"post_id": 31484, "ts": "2026-07-19T21:55:50Z", "hours": 4.2011, "text": "Day 9 — Robotics Arm Project Spent: 4 hours Today I finished designing the wrist section of the robotic arm and continued refining the overall CAD model. I also spent time researching different claw and gripper designs to determine which type would be the best fit for handling small, lightweight objects. A large portion of today’s work involved revisiting earlier CAD parts to add missing details, verify dimensions, and improve the overall assembly. I also searched for manufacturer dimension sheets to make sure the parts matched the hardware I plan to use. While assembling the base, I ran into a gear meshing issue where the 18-tooth and 24-tooth gears were interfering at certain rotation angles. After checking the gear ratio, module, and alignment, I narrowed the problem down to the center distance being slightly too tight. I’m now testing a slightly larger spacing to provide additional clearance and reduce the chance of binding. Next, I’ll finish testing the updated gear spacing, choose a final gripper design, and continue designing the end effector before completing the remaining CAD work."}, {"post_id": 30951, "ts": "2026-07-18T23:21:51Z", "hours": 1.0167, "text": "Day 8 — Robotic Arm Project Spent: 1 hour Today I compared the remaining servo options for the robotic arm and decided to replace the MG996R servos with DS3225MG servos. The DS3225MG provides significantly more torque (about 25 kg·cm), is waterproof, and uses metal gears, all while costing less than the MG996R. Since the body dimensions and mounting hole pattern are very similar, I won’t need to redesign any of the existing brackets. I also spent some time optimizing the CAD model by removing unnecessary material from the arm segments. The goal was to reduce filament usage while keeping strength in the areas that experience the highest loads, such as the joints and mounting points. The CAD assembly is now roughly 80% complete. Next, I’ll continue assembling the remaining components and complete the overall arm assembly before moving on to the next stage of the project."}]...
|
Title: Robotic Arm by @shashvat | Stardance
Devlo Title: Robotic Arm by @shashvat | Stardance
Devlogs:
Day 8 — Robotic Arm Project Spent: 1 hour Today I compared the remaining servo options for the robotic arm and decided to replace the MG996R servos with DS3225MG servos. The DS3225MG provides significantly more torque (about 25 kg·cm), is waterproof, and uses metal gears, all while costing less than the MG996R. Since the body dimensions and mounting hole pattern are very similar, I won’t need to redesign any of the existing brackets. I also spent some time optimizing the CAD model by removing unnecessary material from the arm segments. The goal was to reduce filament usage while keeping strength in the areas that experience the highest loads, such as the joints and mounting points. The CAD assembly is now roughly 80% complete. Next, I’ll continue assembling the remaining components and complete the overall arm assembly before moving on to the next stage of the project.
Day 9 — Robotics Arm Project Spent: 4 hours Today I finished designing the wrist section of the robotic arm and continued refining the overall CAD model. I also spent time researching different claw and gripper designs to determine which type would be the best fit for handling small, lightweight objects. A large portion of today’s work involved revisiting earlier CAD parts to add missing details, verify dimensions, and improve the overall assembly. I also searched for manufacturer dimension sheets to make sure the parts matched the hardware I plan to use. While assembling the base, I ran into a gear meshing issue where the 18-tooth and 24-tooth gears were interfering at certain rotation angles. After checking the gear ratio, module, and alignment, I narrowed the problem down to the center distance being slightly too tight. I’m now testing a slightly larger spacing to provide additional clearance and reduce the chance of binding. Next, I’ll finish testing the updated gear spacing, choose a final gripper design, and continue designing the end effector before completing the remaining CAD work.
Day 10 — Robotic Arm Design Time spent: 2 hours 25 minutes Today’s work was focused on designing the robotic arm’s gripper. I finalized the parallel-jaw gripper design after comparing various end-effector options over the past two days. Most of my time was spent positioning the servo inside the gripper housing and designing the gear mechanism that opens and closes the jaws while ensuring everything fit together correctly. Next, I’ll finish the remaining gripper components, verify the gear alignment, and continue completing the full CAD assembly.
Day 11 — Robotics Arm Project Time spent: 4 hours Today’s focus was on finishing the robotic arm’s gripper. After working through several design and assembly issues, I completed a gear-driven parallelogram gripper that keeps the jaws parallel as they open and close. Most of the session was spent troubleshooting gear meshing and assembly constraints. After adjusting the gear alignment and correcting the center distance, the mechanism operated smoothly. I also removed an unnecessary assembly constraint that was causing conflicts, allowing the four-bar linkage to function as intended. Next, I’ll address the remaining issues discovered during testing, finish the full arm assembly, and continue validating the gripper’s motion before moving on to manufacturing.
Day 12 — Robotics Arm Project Time spent: 2 hours Today I finished troubleshooting the remaining gear meshing issues and completed the full CAD assembly of the robotic arm. After correcting both the gear center distance and tooth alignment, the gears meshed consistently throughout their full range of motion. With those issues resolved, the entire assembly is now functional. The base, shoulder, elbow, wrist, and gripper all move as intended, and the gear-driven parallelogram gripper operates correctly. Next, I’ll perform a final review of every part by checking dimensions against the actual hardware specifications, make any final adjustments if needed, and finish the bill of materials before preparing the design for manufacturing.
Day 13 — Robotics Arm Project Time spent: 3 hours Today I shifted my focus from designing new parts to improving and validating the existing CAD model. I reviewed every component of the robotic arm, corrected several design issues, and refined parts to improve their fit and overall manufacturability. I also planned the wire routing for the arm, making sure each joint would have enough slack for its full range of motion while reducing the risk of wires being pinched during operation. To finish the session, I began preparing the arm for simulation by exporting the assembly from Onshape using the onshape-to-robot exporter. During this process, I discovered that my assembly mates and material properties still need to be configured correctly before the robot can be successfully simulated in PyBullet. Next, I’ll fix the assembly mates, assign materials to every part, and begin testing the robotic arm in simulation.
Day 14 — Robotic Arm Project Time spent: 2.5 hours Today I worked on creating an animation of my robotic arm to better visualize how all of the joints move together before building the physical prototype. I explored several approaches, including exporting the CAD model for simulation in PyBullet, but ran into issues with the assembly not exporting correctly due to missing joint definitions and material properties. Instead, I used Onshape’s Gear Relation feature to synchronize the movement of multiple joints, allowing me to create a smooth animation driven by a single input. This gave me a simple way to demonstrate the arm’s motion and better understand how the overall mechanism behaves. Next, I’ll continue refining the CAD assembly, prepare the design for 3D printing, and complete the remaining project documentation.
Day 15 – Robotics Arm Project Time Worked: 2.5 hours Today I finalized the bill of materials (BOM) for my robotic arm project and confirmed that all of the required components had been selected. I replaced several Amazon.com items with Amazon.ca alternatives to reduce shipping costs and added a 5x20mm inline fuse kit to protect the ESP32. I also verified that my selected wire and MG90S servos matched my design requirements, so no CAD changes are needed. By the end of the session, the project cost was estimated at $257.10 CAD, and the planning stage was essentially complete. Next Steps: Make the final CAD improvements. Apply for the project grant. Order the parts once funding is approved. Begin the physical build after the parts arrive.
Day 16 – Robotics Arm Project Time Worked: 1 hour 47 min Today I focused on improving the realism and accuracy of my robotic arm CAD assembly. The M3 screw holes and brass heat-set insert mounting points were already designed, so I created CAD models of the actual M3 screws and brass heat-set inserts and added them into the assembly. Adding the hardware models helped me visualize how the final robotic arm will be assembled and gave a more accurate representation of the finished design. While adding these components, I noticed a few small design issues that were not obvious before. Checking the screws and inserts against the parts helped me verify clearances, mounting positions, and overall fit. I fixed these issues before printing to prevent problems during assembly. Next Steps Apply for the Stardance grant once the application system is available again. Submit the design application when the form is working. Order the parts after confirming the budget. Begin the physical build once the parts arrive.
Devlog – Day 1 Date: July 27, 2026 Time Worked: 4 hours Today I began planning my custom quadcopter drone project by researching how the entire system works before selecting any parts. I learned how the flight controller, ESCs, motors, GPS, receiver, battery, and power distribution board work together, and compared different options for building a custom transmitter. By the end of the session, I had established the project’s main goals, selected the overall system architecture, and identified the next components to research. Next Steps Select the drone hardware. Research the custom transmitter electronics. Create a complete bill of materials. Begin designing the transmitter enclosure. Devlog – Day 2 Date: July 28, 2026 Time Worked: 4 hours Today I finalized the major hardware for both the drone and the custom controller. I selected the flight stack, motors, propellers, battery, GPS module, and the controller electronics, including the ESP32-C3, HC-12 radio module, battery, charging circuit, and joysticks. I also finalized the project’s electrical architecture, estimated the total project cost, and prepared to move into the CAD design phase. Next Steps Design the carbon fiber drone frame. Design the custom controller enclosure. Create the wiring diagrams. Note: I am posting these updates in my Robotics Arm project section because I accidentally recorded the project time there.
Devlog – Day 17 Date: August 8, 2026 Time Worked: 2 hours Today I started learning how to wire and program servos using an ESP32 in Cirkit. I began with simple push buttons instead of immediately using Bluepad32 and a gaming controller so I could understand the basic wiring and servo control first. I successfully got one servo working, confirming that my basic wiring and code were correct. I also identified a wiring issue with the other servos that I wasn’t able to fix today. I learned more about ESP32 pins, servo-control functions, and how the different components need to be connected. Next Steps Fix the wiring issue with the other servos. Continue practicing servo control. Start learning how to use Bluepad32 with a gaming controller.
Devlog – Day 18 Date: August 9, 2026 Time Worked: 2 hours Today I fixed the wiring issue from my previous session. After tracing through the circuit, I found that the connections were mixed up. Once I corrected the wiring, the servos started responding properly. I then worked with the Bluepad32 library and wrote code that allows an Xbox controller’s joysticks and buttons to control the servos. I ran into several setup and communication issues, but I worked through them and completed the full controller code. With the wiring fixed and the code completed, the project is now ready for the physical build once funding is approved. Next Steps Order the required parts. Begin 3D printing the robotic arm components. Start assembling the arm....
|
1793191900.562953
|
1793796700.562953
|
|
7138
|
Antweight Combat Robot by @daryl_jimenez_c | Stard Antweight Combat Robot by @daryl_jimenez_c | Stardance...
|
daryl_jimenez_c
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Antweight Combat Robot by @daryl_jimenez_c Title: Antweight Combat Robot by @daryl_jimenez_c | Stardance...
|
1793191899.6633725
|
1793796699.6633725
|
|
4818
|
idk by @the_ryaan_ahmed | Stardance
|
the_ryaan_ahmed
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: idk by @the_ryaan_ahmed | Stardance
|
1793191898.6781664
|
1793796698.6781664
|
|
2645
|
My awesome macropad! by @AYOMIKUN | Stardance
|
AYOMIKUN
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @AYOMIKUN | Stardan Title: My awesome macropad! by @AYOMIKUN | Stardance...
|
1793191897.78245
|
1793796697.78245
|
|
28423
|
score creator app by @rsupp | Stardance
|
rsupp
|
0
|
11.05
|
0
|
[]
|
[{"post_id": 71613, "ts": "202 [{"post_id": 71613, "ts": "2026-09-21T05:05:53Z", "hours": 0.6344, "text": "I implemented tone.js. It was much faster than my other things—the only problem was needing a buffer between notes. But now I have to work on UI :( and adding more advanced features. (I also began to work on adding bpm and a import score feature but they are not finished yet)"}, {"post_id": 63717, "ts": "2026-09-07T17:31:03Z", "hours": 1.9719, "text": "I fixed the problem that I had with eighth notes by switching from using /e to /8 in vexflow. I am still having some problems with width, but overall it is much better. That is why I decided to start working on adding sound. My basic implementation of Tone.js is working very well currently. The Press to Play button plays the sound. I need to work on more features to make the website easier to use now."}, {"post_id": 57791, "ts": "2026-08-30T02:45:46Z", "hours": 1.9011, "text": "I still cannot figure out how to fix my problem with eighth notes not working. I have tried editing the width values (which fixed the cut off early issue), removing Math.floors in some parts of my code, and more. I also added a clear local storage button for the score for ease of use. I will continue to test to fix the eighth notes."}, {"post_id": 43742, "ts": "2026-08-09T04:59:25Z", "hours": 3.08, "text": "I was able to get the scores to persist on screen. I also was able to add multiple measures to my list of notes without the program crashing, after a bunch of debugging. Currently, I was testing have different lengths for the measures and am having problems with the notes appearing on screen. I was trying to test changing x and width values but that did not work. The built in formatter in vexflow worked a bit better but my score and notes keep getting squished and cut off randomly."}, {"post_id": 40927, "ts": "2026-08-04T19:21:08Z", "hours": 3.3925, "text": "I added a system so the script I am using can actually take in the values the user has inputted. The script can also use this input to create an output of 1 measure of the user input before the program will crash. Another problem is that the 1 measure only appears on screen for a second before it goes away. I will fix these two issues later."}, {"post_id": 29662, "ts": "2026-07-16T18:47:18Z", "hours": 0.0678, "text": "I have not worked on creating a website in a very long time. That is why I focused on creating some buttons that send data to my program, and I also found two libraries that I will most likely use: vexflow.js and Tone.js"}]...
|
Title: score creator app by @rsupp | Stardance
De Title: score creator app by @rsupp | Stardance
Devlogs:
I have not worked on creating a website in a very long time. That is why I focused on creating some buttons that send data to my program, and I also found two libraries that I will most likely use: vexflow.js and Tone.js
I added a system so the script I am using can actually take in the values the user has inputted. The script can also use this input to create an output of 1 measure of the user input before the program will crash. Another problem is that the 1 measure only appears on screen for a second before it goes away. I will fix these two issues later.
I was able to get the scores to persist on screen. I also was able to add multiple measures to my list of notes without the program crashing, after a bunch of debugging. Currently, I was testing have different lengths for the measures and am having problems with the notes appearing on screen. I was trying to test changing x and width values but that did not work. The built in formatter in vexflow worked a bit better but my score and notes keep getting squished and cut off randomly.
I still cannot figure out how to fix my problem with eighth notes not working. I have tried editing the width values (which fixed the cut off early issue), removing Math.floors in some parts of my code, and more. I also added a clear local storage button for the score for ease of use. I will continue to test to fix the eighth notes.
I fixed the problem that I had with eighth notes by switching from using /e to /8 in vexflow. I am still having some problems with width, but overall it is much better. That is why I decided to start working on adding sound. My basic implementation of Tone.js is working very well currently. The Press to Play button plays the sound. I need to work on more features to make the website easier to use now.
I implemented tone.js. It was much faster than my other things—the only problem was needing a buffer between notes. But now I have to work on UI :( and adding more advanced features. (I also began to work on adding bpm and a import score feature but they are not finished yet)...
|
1793191896.8134224
|
1793796696.8134224
|
|
36191
|
Tasks of Red -- WarioWare Game by @theRed | Starda Tasks of Red -- WarioWare Game by @theRed | Stardance...
|
theRed
|
0
|
0.65
|
0
|
[]
|
[{"post_id": 29855, "ts": "202 [{"post_id": 29855, "ts": "2026-07-17T00:26:02Z", "hours": 0.6536, "text": "Started on the Start-Up Menu, will add sprites and polish this up by the next log. Basic functionality was added to the start and quit buttons, settings will be a future addition."}]...
|
Title: Tasks of Red -- WarioWare Game by @theRed | Title: Tasks of Red -- WarioWare Game by @theRed | Stardance
Devlogs:
Started on the Start-Up Menu, will add sprites and polish this up by the next log. Basic functionality was added to the start and quit buttons, settings will be a future addition....
|
1793191895.9209077
|
1793796695.9209077
|
|
863
|
My awesome macropad! by @67 | Stardance
|
67
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @67 | Stardance
|
1793191895.0065594
|
1793796695.0065594
|
|
18397
|
My first slack bot! by @thamidueshan200 | Stardanc My first slack bot! by @thamidueshan200 | Stardance...
|
thamidueshan200
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @thamidueshan200 | S Title: My first slack bot! by @thamidueshan200 | Stardance...
|
1793191894.086044
|
1793796694.086044
|
|
16094
|
E.H & O.S by @RanbirG | Stardance
|
RanbirG
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: E.H & O.S by @RanbirG | Stardance
|
1793191893.1991684
|
1793796693.1991684
|