|
4371
|
naran by @boom | Stardance
|
boom
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: naran by @boom | Stardance
|
1793195605.699141
|
1793800405.699141
|
|
4372
|
My awesome macropad! by @Muzz | Stardance
|
Muzz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Muzz | Stardance
|
1793184448.0738208
|
1793789248.0738208
|
|
4373
|
My awesome macropad! by @samuelfoka408 | Stardance
|
samuelfoka408
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @samuelfoka408 | St Title: My awesome macropad! by @samuelfoka408 | Stardance...
|
1793242072.73408
|
1793846872.73408
|
|
4374
|
My awesome macropad! by @Ansar | Stardance
|
Ansar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Ansar | Stardance
|
1793386094.2790086
|
1793990894.2790086
|
|
4375
|
My first slack bot! by @pampam | Stardance
|
pampam
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @pampam | Stardance
|
1792759871.38846
|
1793364671.38846
|
|
4376
|
My awesome macropad! by @mikupiku | Stardance
|
mikupiku
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @mikupiku | Stardan Title: My awesome macropad! by @mikupiku | Stardance...
|
1793418854.2991257
|
1794023654.2991257
|
|
4377
|
My awesome macropad! by @pixeldreamz_s | Stardance
|
pixeldreamz_s
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @pixeldreamz_s | St Title: My awesome macropad! by @pixeldreamz_s | Stardance...
|
1793443741.765034
|
1794048541.765034
|
|
4378
|
VibeBoard by @Ammar | Stardance
|
Ammar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: VibeBoard by @Ammar | Stardance
|
1792781476.6397586
|
1793386276.6397586
|
|
4379
|
Untitled by @achille | Stardance
|
achille
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @achille | Stardance
|
1793238696.1642559
|
1793843496.1642559
|
|
4380
|
Untitled by @hridhaan | Stardance
|
hridhaan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @hridhaan | Stardance
|
1793440224.446849
|
1794045024.446849
|
|
4381
|
My awesome macropad! by @Pom | Stardance
|
Pom
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Pom | Stardance
|
1793487372.1412146
|
1794092172.1412146
|
|
4382
|
aaaa by @Kubik | Stardance
|
Kubik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: aaaa by @Kubik | Stardance
|
1792914821.6562202
|
1793778821.6562202
|
|
4383
|
My awesome macropad! by @wubshet2028 | Stardance
|
wubshet2028
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @wubshet2028 | Star Title: My awesome macropad! by @wubshet2028 | Stardance...
|
1793454634.148565
|
1794059434.148565
|
|
4384
|
My first slack bot! by @wubshet2028 | Stardance
|
wubshet2028
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @wubshet2028 | Stard Title: My first slack bot! by @wubshet2028 | Stardance...
|
1792803175.0068586
|
1793407975.0068586
|
|
4385
|
My awesome macropad! by @Jz | Stardance
|
Jz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Jz | Stardance
|
1793181362.8573942
|
1793786162.8573942
|
|
4386
|
Mimic bionic hand by @bolar_aradhya | Stardance
|
bolar_aradhya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mimic bionic hand by @bolar_aradhya | Stard Title: Mimic bionic hand by @bolar_aradhya | Stardance...
|
1793418803.2653432
|
1794023603.2653432
|
|
4387
|
My first slack bot! by @Bobby | Stardance
|
Bobby
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Bobby | Stardance
|
1793296319.655119
|
1793901119.655119
|
|
4388
|
Untitled project by @kkennzzoo | Stardance
|
kkennzzoo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @kkennzzoo | Stardance
|
1793202637.8636284
|
1793807437.8636284
|
|
4389
|
My awesome macropad! by @The_Redel_Guy | Stardance
|
The_Redel_Guy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @The_Redel_Guy | St Title: My awesome macropad! by @The_Redel_Guy | Stardance...
|
1793278347.9305568
|
1793883147.9305568
|
|
4390
|
My awesome macropad! by @cxlm2023 | Stardance
|
cxlm2023
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @cxlm2023 | Stardan Title: My awesome macropad! by @cxlm2023 | Stardance...
|
1793418785.284625
|
1794023585.284625
|
|
4391
|
NEON-HEIST by @karnaaditya | Stardance
|
karnaaditya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: NEON-HEIST by @karnaaditya | Stardance
|
1793274856.6361814
|
1793879656.6361814
|
|
4392
|
My awesome macropad! by @malpemrecik | Stardance
|
malpemrecik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @malpemrecik | Star Title: My awesome macropad! by @malpemrecik | Stardance...
|
1793145068.0332258
|
1793749868.0332258
|
|
4393
|
Flounder Valley by @Rayed_Ahmed | Stardance
|
Rayed_Ahmed
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Flounder Valley by @Rayed_Ahmed | Stardance
|
1793440621.9168444
|
1794045421.9168444
|
|
4394
|
My awesome macropad! by @Mitchell | Stardance
|
Mitchell
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Mitchell | Stardan Title: My awesome macropad! by @Mitchell | Stardance...
|
1793260527.140475
|
1793865327.140475
|
|
4395
|
My awesome macropad! by @t-nair | Stardance
|
t-nair
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @t-nair | Stardance
|
1793397029.2438712
|
1794001829.2438712
|
|
4396
|
Root by @mihaelatanasov22 | Stardance
|
mihaelatanasov22
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Root by @mihaelatanasov22 | Stardance
|
1793137845.4532168
|
1793742645.4532168
|
|
4397
|
Mini Decibel Tracker by @Chelsey | Stardance
|
Chelsey
|
0
|
1.22
|
0
|
[]
|
[{"post_id": 6018, "ts": "2026 [{"post_id": 6018, "ts": "2026-06-10T02:47:04Z", "hours": 1.2233, "text": "I tried fiddling and coding a small project which is this decibel tracker for analyzing potential sound pollution and averages at school"}]...
|
Title: Mini Decibel Tracker by @Chelsey | Stardanc Title: Mini Decibel Tracker by @Chelsey | Stardance
Devlogs:
I tried fiddling and coding a small project which is this decibel tracker for analyzing potential sound pollution and averages at school...
|
1793199315.4154277
|
1793804115.4154277
|
|
4398
|
Task Tracker by @Curious_Brain | Stardance
|
Curious_Brain
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Task Tracker by @Curious_Brain | Stardance
|
1793184757.7595115
|
1793789557.7595115
|
|
4399
|
Iotbubbler by @Ibo | Stardance
|
Ibo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Iotbubbler by @Ibo | Stardance
|
1792900350.700297
|
1793764350.700297
|
|
4400
|
ACR (Astronomical Character Recognition) by @Hites ACR (Astronomical Character Recognition) by @Hitesh | Stardance...
|
Hitesh
|
1
|
24.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-06T00:17:24Z", "hours": 24.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a image classification model from scratch using TensorFlow and Keras. The model is optimized to find nebulae’s, galaxy’s, moon’s, and planet’s.", "repo": "https://github.com/hiteshv2603-ui/HyzeACR", "demo": "https://hyzeacr.netlify.app"}]...
|
[{"post_id": 3096, "ts": "2026 [{"post_id": 3096, "ts": "2026-06-06T00:15:36Z", "hours": 8.4486, "text": "Building the model turned out to be a lot tougher than I thought. I spent so many hours, sometimes whole days, planning, experimenting, and figuring out how everything would work. My main goal was to make the model bug free and working completely fine. There were times when I wasn’t sure if my code or project would actually work. Some of my friends had made fun of me for working so hard or thought the project was stupid, but I kept going anyway. I want to show them that hard work on even “stupid” projects can turn out good. The hardest parts weren’t technical. I struggled with wanting to give up, worrying I wouldn’t reach my goal, and hearing discouraging words from people close to me. Even so, I kept going. Visiting Hugging Face for inspiration and learning more about how the code worked helped me learn more about OCR and Image Classification models. I’ve learned a lot along the way ngl. After fixing some final bugs, I feel like I’m almost finished with my model. I just need to do a bit more research to make sure I’m headed in the right direction, and of course, I’ll keep posting these devlogs to share my progress/journey!"}, {"post_id": 1940, "ts": "2026-06-04T05:55:16Z", "hours": 15.9544, "text": "I actually timed myself here💀. Ok so there I was, trying to find data/images to train my image classification model, and I ran into a lot of problems😭. The biggest problem was the lack of suitable space images and astronomical text data. I tried Kaggle first, but that failed because most datasets weren’t specific to astronomy. Next I used Hugging Face for the images, and that also failed because most of them were either JSON files or plain text instead of actual space imagery. I finally settled on NASA’s Open Data Archive to get actual space images and train the model, and I even used an image scraper extension to scrape additional images to supplement my training data. I woke up at 4:30 in the morning because of my jetlag and spent those early hours trying to find good datasets, figure out which languages to use, and figure out how to actually get the datasets into my pipeline. After looking different things, I settled on Keras and TensorFlow to create the model since they are pretty good for deep learning and image classification and integrates with the language I’m good at, Python .For the demo and web interface, I used TensorFlow.js so I could deploy it directly in the browser. To make things a little bit simpler and faster, I used Teachable Machine’s scripts to get the model’s TensorFlow.js script by training the model again there, which saved me a lot of time on the export and conversion process. But I was extremely happy with the end result and was amazed at how good my model really was . Despite all the challenges from the jetlag affected morning coding sessions to the frustrating dataset search, the final result performed surprisingly well on astronomical images and I’m excited to keep improving it for my space and AI projects."}]...
|
Title: ACR (Astronomical Character Recognition) by Title: ACR (Astronomical Character Recognition) by @Hitesh | Stardance
Devlogs:
I actually timed myself here💀. Ok so there I was, trying to find data/images to train my image classification model, and I ran into a lot of problems😭. The biggest problem was the lack of suitable space images and astronomical text data. I tried Kaggle first, but that failed because most datasets weren’t specific to astronomy. Next I used Hugging Face for the images, and that also failed because most of them were either JSON files or plain text instead of actual space imagery. I finally settled on NASA’s Open Data Archive to get actual space images and train the model, and I even used an image scraper extension to scrape additional images to supplement my training data. I woke up at 4:30 in the morning because of my jetlag and spent those early hours trying to find good datasets, figure out which languages to use, and figure out how to actually get the datasets into my pipeline. After looking different things, I settled on Keras and TensorFlow to create the model since they are pretty good for deep learning and image classification and integrates with the language I’m good at, Python .For the demo and web interface, I used TensorFlow.js so I could deploy it directly in the browser. To make things a little bit simpler and faster, I used Teachable Machine’s scripts to get the model’s TensorFlow.js script by training the model again there, which saved me a lot of time on the export and conversion process. But I was extremely happy with the end result and was amazed at how good my model really was . Despite all the challenges from the jetlag affected morning coding sessions to the frustrating dataset search, the final result performed surprisingly well on astronomical images and I’m excited to keep improving it for my space and AI projects.
Building the model turned out to be a lot tougher than I thought. I spent so many hours, sometimes whole days, planning, experimenting, and figuring out how everything would work. My main goal was to make the model bug free and working completely fine. There were times when I wasn’t sure if my code or project would actually work. Some of my friends had made fun of me for working so hard or thought the project was stupid, but I kept going anyway. I want to show them that hard work on even “stupid” projects can turn out good. The hardest parts weren’t technical. I struggled with wanting to give up, worrying I wouldn’t reach my goal, and hearing discouraging words from people close to me. Even so, I kept going. Visiting Hugging Face for inspiration and learning more about how the code worked helped me learn more about OCR and Image Classification models. I’ve learned a lot along the way ngl. After fixing some final bugs, I feel like I’m almost finished with my model. I just need to do a bit more research to make sure I’m headed in the right direction, and of course, I’ll keep posting these devlogs to share my progress/journey!
Ships:
I made a image classification model from scratch using TensorFlow and Keras. The model is optimized to find nebulae’s, galaxy’s, moon’s, and planet’s....
|
1793332634.8532434
|
1793419034.8532434
|
|
4401
|
Untitled project by @Radhe | Stardance
|
Radhe
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Radhe | Stardance
|
1793195251.7285657
|
1793800051.7285657
|
|
4402
|
My first slack bot! by @sandeepsarkar316 | Stardan My first slack bot! by @sandeepsarkar316 | Stardance...
|
sandeepsarkar316
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @sandeepsarkar316 | Title: My first slack bot! by @sandeepsarkar316 | Stardance...
|
1793141610.1121278
|
1793746410.1121278
|
|
4403
|
Untitled project by @ntd3 | Stardance
|
ntd3
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @ntd3 | Stardance
|
1793242163.919851
|
1793846963.919851
|
|
4404
|
My awesome macropad! by @phamtuan72az | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @phamtuan72az | Sta Title: My awesome macropad! by @phamtuan72az | Stardance...
|
1793264042.1132388
|
1793868842.1132388
|
|
4405
|
DELPHI TOOLS by @visheshj2005 | Stardance
|
visheshj2005
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: DELPHI TOOLS by @visheshj2005 | Stardance
|
1793288909.862091
|
1793893709.862091
|
|
4406
|
My awesome macropad! by @r_joelvarghese | Stardanc My awesome macropad! by @r_joelvarghese | Stardance...
|
r_joelvarghese
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @r_joelvarghese | S Title: My awesome macropad! by @r_joelvarghese | Stardance...
|
1792950708.3891048
|
1793814708.3891048
|
|
4407
|
My awesome macropad! by @pakkid | Stardance
|
pakkid
|
0
|
0.0
|
0
|
[]
|
[{"post_id": 6081, "ts": "2026 [{"post_id": 6081, "ts": "2026-06-10T07:04:16Z", "hours": 0.0, "text": "I have finally routed some of my PCB and managed to make a somewhat readable Schematic. my PCB is kind of spaghetti tho…"}]...
|
Title: My awesome macropad! by @pakkid | Stardance Title: My awesome macropad! by @pakkid | Stardance
Devlogs:
I have finally routed some of my PCB and managed to make a somewhat readable Schematic. my PCB is kind of spaghetti tho…...
|
1792903945.002781
|
1793767945.002781
|
|
4408
|
Untitled by @ronakd | Stardance
|
ronakd
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ronakd | Stardance
|
1793152452.5701709
|
1793757252.5701709
|
|
4409
|
My awesome macropad! by @qqxzew | Stardance
|
qqxzew
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @qqxzew | Stardance
|
1793404592.9922307
|
1794009392.9922307
|
|
4410
|
My first slack bot! by @Rishabh | Stardance
|
Rishabh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Rishabh | Stardance
|
1793447611.8019493
|
1794052411.8019493
|
|
4411
|
Untitled project by @meyraazenn26 | Stardance
|
meyraazenn26
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @meyraazenn26 | Stardan Title: Untitled project by @meyraazenn26 | Stardance...
|
1793220614.5284162
|
1793825414.5284162
|
|
4412
|
SSSocks by @qqxzew | Stardance
|
qqxzew
|
0
|
9.41
|
0
|
[]
|
[{"post_id": 37828, "ts": "202 [{"post_id": 37828, "ts": "2026-07-30T19:42:18Z", "hours": 5.3622, "text": "last month I had done a lot of work, mainly on my global php/nette skill. Why? I want to find an intership, I know a lot of local IT companies from the Hackatons. And they know me to, but the main problem was the stack. All of them are using php. I had revieved my knowelege of php - and realized that I dont know enought. After month i had returned to my project. I saw bad code and slow solutions, I was not using the correct options introduced by Nette framework but the old and procedure php, like a routers which was writen in index.php. I dont write some new features or change frontend, I had only improve myself."}, {"post_id": 13338, "ts": "2026-06-21T21:06:03Z", "hours": 4.0464, "text": "Devlog: Building SSSocks — Days 1 to 6: Infrastructure to Atomic ReservationsFirst devlog for SSSocks, a high-performance e-commerce backend for premium sock sales. This log covers architecture choices, infrastructure setup, and technical challenges from the first six phases of development.Days 1–2: Infrastructure and CI/CD AutomationThe project focused on isolating the execution environment to ensure consistency across hosts.Configured a local development stack using Docker Compose (PHP-FPM, Nginx, and MySQL).Established an automated CI/CD pipeline using GitHub Actions.Integrated PHPStan for static analysis at Level 8 to enforce strict typing and prevent runtime type mismatches.Day 3: Database Schema and MigrationsDatabase modifications were abstracted using migrations to manage state deterministically.Integrated Phinx for migration and seeding management.Executed the initial relational schema, creating the products table.Implemented core database fields: unique stock keeping units (sku), names, inventory counts (stock), and prices stored as integers representing cents to avoid floating-point inaccuracies.Day 4: Dependency Injection and RefactoringAs the codebase scaled, manual object instantiation was replaced with a cleaner design pattern.Integrated the Nette DI container to manage object lifecycles and decouple classes.Configured service definitions inside config/common.neon.Refactored components like PasswordManager into standalone services managed by the container.Day 5: Presentation Layer and Repository PatternSeparated data access from presentation logic to maintain clean boundaries.Implemented the Repository pattern with ProductRepository handling data retrieval via Nette Database Core.Created ProductSeeder via Phinx to populate the database with standardized test inventory.Integrated the Latte template engine, eliminating inline HTML concatenation and establishing an MVC separation for the product showcase.Day 6: Highload Optimization and Race Condition PreventionThe standard SELECT stock -> UPDATE stock workflow introduces race conditions under concurrent traffic, causing overselling. To achieve atomic inventory reservation under high load, the architecture was refactored:Introduced a Redis instance running on an Alpine image inside the Docker network.Developed a StockManager service acting as an abstraction layer over the Redis memory cache.Wrote an embedded Lua script executed directly inside the single-threaded Redis engine. The script performs read, condition-check, and decrement operations atomically within a single non-blocking transaction.Lualocal current_stock = tonumber(redis.call(‘GET’, KEYS[1])) if current_stock and current_stock >= tonumber(ARGV[1]) then redis.call(‘DECRBY’, KEYS[1], ARGV[1]) return 1 end return 0 Technical Challenges and Bug FixesPSR-4 Case Sensitivity: Encountered class-loading failures during Linux-based CI execution despite code running successfully on a Windows host. Resolved by aligning file naming conventions with uppercase namespaces (Bootstrap.php and StockManager.php).Docker Network DNS Propagation: Encountered a Name or service not known error connecting the PHP container to the new Redis host. Solved by flushing the virtual network topology via docker-compose down && docker-compose up -d.Strict Parameter Compliance: PHPStan Level 8 rejected passing integer parameters into the Predis eval method arguments. Fixed by explicitly casting inventory quantities to strings: (string) $quantity.Current Backlog[ ] Implement an API endpoint structure to accept incoming product selections.[ ] Integrate a validation layer for incoming HTTP POST request payloads.[ ] Design the architecture for the stateful shopping cart session."}]...
|
Title: SSSocks by @qqxzew | Stardance
Devlogs:
De Title: SSSocks by @qqxzew | Stardance
Devlogs:
Devlog: Building SSSocks — Days 1 to 6: Infrastructure to Atomic ReservationsFirst devlog for SSSocks, a high-performance e-commerce backend for premium sock sales. This log covers architecture choices, infrastructure setup, and technical challenges from the first six phases of development.Days 1–2: Infrastructure and CI/CD AutomationThe project focused on isolating the execution environment to ensure consistency across hosts.Configured a local development stack using Docker Compose (PHP-FPM, Nginx, and MySQL).Established an automated CI/CD pipeline using GitHub Actions.Integrated PHPStan for static analysis at Level 8 to enforce strict typing and prevent runtime type mismatches.Day 3: Database Schema and MigrationsDatabase modifications were abstracted using migrations to manage state deterministically.Integrated Phinx for migration and seeding management.Executed the initial relational schema, creating the products table.Implemented core database fields: unique stock keeping units (sku), names, inventory counts (stock), and prices stored as integers representing cents to avoid floating-point inaccuracies.Day 4: Dependency Injection and RefactoringAs the codebase scaled, manual object instantiation was replaced with a cleaner design pattern.Integrated the Nette DI container to manage object lifecycles and decouple classes.Configured service definitions inside config/common.neon.Refactored components like PasswordManager into standalone services managed by the container.Day 5: Presentation Layer and Repository PatternSeparated data access from presentation logic to maintain clean boundaries.Implemented the Repository pattern with ProductRepository handling data retrieval via Nette Database Core.Created ProductSeeder via Phinx to populate the database with standardized test inventory.Integrated the Latte template engine, eliminating inline HTML concatenation and establishing an MVC separation for the product showcase.Day 6: Highload Optimization and Race Condition PreventionThe standard SELECT stock -> UPDATE stock workflow introduces race conditions under concurrent traffic, causing overselling. To achieve atomic inventory reservation under high load, the architecture was refactored:Introduced a Redis instance running on an Alpine image inside the Docker network.Developed a StockManager service acting as an abstraction layer over the Redis memory cache.Wrote an embedded Lua script executed directly inside the single-threaded Redis engine. The script performs read, condition-check, and decrement operations atomically within a single non-blocking transaction.Lualocal current_stock = tonumber(redis.call(‘GET’, KEYS[1])) if current_stock and current_stock >= tonumber(ARGV[1]) then redis.call(‘DECRBY’, KEYS[1], ARGV[1]) return 1 end return 0 Technical Challenges and Bug FixesPSR-4 Case Sensitivity: Encountered class-loading failures during Linux-based CI execution despite code running successfully on a Windows host. Resolved by aligning file naming conventions with uppercase namespaces (Bootstrap.php and StockManager.php).Docker Network DNS Propagation: Encountered a Name or service not known error connecting the PHP container to the new Redis host. Solved by flushing the virtual network topology via docker-compose down && docker-compose up -d.Strict Parameter Compliance: PHPStan Level 8 rejected passing integer parameters into the Predis eval method arguments. Fixed by explicitly casting inventory quantities to strings: (string) $quantity.Current Backlog[ ] Implement an API endpoint structure to accept incoming product selections.[ ] Integrate a validation layer for incoming HTTP POST request payloads.[ ] Design the architecture for the stateful shopping cart session.
last month I had done a lot of work, mainly on my global php/nette skill. Why? I want to find an intership, I know a lot of local IT companies from the Hackatons. And they know me to, but the main problem was the stack. All of them are using php. I had revieved my knowelege of php - and realized that I dont know enought. After month i had returned to my project. I saw bad code and slow solutions, I was not using the correct options introduced by Nette framework but the old and procedure php, like a routers which was writen in index.php. I dont write some new features or change frontend, I had only improve myself....
|
1793156176.9099767
|
1793760976.9099767
|
|
4413
|
Untitled by @Gokul | Stardance
|
Gokul
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Gokul | Stardance
|
1793184884.4306886
|
1793789684.4306886
|
|
4414
|
Remote Access Trojan by @soloplanet | Stardance
|
soloplanet
|
1
|
38.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-01T00:05:54Z", "hours": 38.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a RAT and experimented with shellcode loading. Things I found hard were obfuscating the app, learning how to use indirect syscalls and trying to evade detection. I am proud of getting my best attempt (tar2.0) at best to evade 4/71 detections which were primarily high positive ML engines and Crowdstrike (only 60% confidence) (this eventually increased to 9/71 due to signatures).", "repo": "https://github.com/MasterGoop2000/rat-project/", "demo": "https://github.com/MasterGoop2000/rat-project/releases/tag/v1.0"}]...
|
[{"post_id": 75757, "ts": "202 [{"post_id": 75757, "ts": "2026-09-30T23:54:04Z", "hours": 35.9075, "text": "Shellcode loader"}, {"post_id": 1353, "ts": "2026-06-03T09:49:17Z", "hours": 1.8203, "text": "Remote Access Trojan"}]...
|
Title: Remote Access Trojan by @soloplanet | Stard Title: Remote Access Trojan by @soloplanet | Stardance
Devlogs:
Remote Access Trojan
Shellcode loader
Ships:
I made a RAT and experimented with shellcode loading. Things I found hard were obfuscating the app, learning how to use indirect syscalls and trying to evade detection. I am proud of getting my best attempt (tar2.0) at best to evade 4/71 detections which were primarily high positive ML engines and Crowdstrike (only 60% confidence) (this eventually increased to 9/71 due to signatures)....
|
1793339556.0127833
|
1793425956.0127833
|
|
4415
|
My first slack bot! by @Sap | Stardance
|
Sap
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Sap | Stardance
|
1793141654.3423703
|
1793746454.3423703
|
|
4416
|
Bareless by @d0mkaaa | Stardance
|
d0mkaaa
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Bareless by @d0mkaaa | Stardance
|
1793483479.5545394
|
1794088279.5545394
|
|
4418
|
A drone claw by @WillD | Stardance
|
WillD
|
0
|
0.55
|
0
|
[]
|
[{"post_id": 701, "ts": "2026- [{"post_id": 701, "ts": "2026-06-02T08:23:30Z", "hours": 0.5539, "text": "The research I have the choice of 2 boards, esp32 and raspberry pi zero. Both boards are great! however they both carry limitations (see image above/below). esp32 has great radio reach as antennas can easily be attatched. The raspberry pi has a super easy and user friendly connectivity due to its computer like system. these boards will be the brains of the claw, this will tell the mechanism to open/close when the other device sends a signal wirelessly to the brains - similar to how our brains work (just…not wirelessly :/) However as the handheld device will be a physical (or digital touch) button I believe the esp32 will be a better fit, this is because it will have a longer range which is needed for drones especially if the drone is custom built, the esp32 also doesnt drain battery meaning the device can be lighter - meaning more flight time for the drone as well as a cheaper system (it wont need a lot of batteries or need larger batteries) although the esp has a long radio signal it will still need a LoRa addon, this is because of drones signals."}]...
|
Title: A drone claw by @WillD | Stardance
Devlogs Title: A drone claw by @WillD | Stardance
Devlogs:
The research I have the choice of 2 boards, esp32 and raspberry pi zero. Both boards are great! however they both carry limitations (see image above/below). esp32 has great radio reach as antennas can easily be attatched. The raspberry pi has a super easy and user friendly connectivity due to its computer like system. these boards will be the brains of the claw, this will tell the mechanism to open/close when the other device sends a signal wirelessly to the brains - similar to how our brains work (just…not wirelessly :/) However as the handheld device will be a physical (or digital touch) button I believe the esp32 will be a better fit, this is because it will have a longer range which is needed for drones especially if the drone is custom built, the esp32 also doesnt drain battery meaning the device can be lighter - meaning more flight time for the drone as well as a cheaper system (it wont need a lot of batteries or need larger batteries) although the esp has a long radio signal it will still need a LoRa addon, this is because of drones signals....
|
1792759896.1003654
|
1793364696.1003654
|
|
4419
|
My awesome macropad! by @Hoodie | Stardance
|
Hoodie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Hoodie | Stardance
|
1792803288.9755707
|
1793408088.9755707
|
|
4420
|
My awesome macropad! by @Maycoly | Stardance
|
Maycoly
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Maycoly | Stardanc Title: My awesome macropad! by @Maycoly | Stardance...
|
1792785200.8206224
|
1793390000.8206224
|
|
4421
|
My awesome macropad! by @joycesusatyo | Stardance
|
joycesusatyo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @joycesusatyo | Sta Title: My awesome macropad! by @joycesusatyo | Stardance...
|
1793249555.060094
|
1793854355.060094
|