NEW BOT Телеграм, страница

Can a tiny server running FastAPI/SQLite survive the hug of death?
https://www.reddit.com/r/programming/comments/1ncan42/can_a_tiny_server_running_fastapisqlite_survive/

I run tiny indie apps on a Linux box. On a good day, I get ~300 visitors. But what if I hit a lot of traffic? Could my box survive the hug of death? So I load tested it: Reads? 100 RPS with no errors. Writes? Fine after enabling WAL. Search? Broke… until I switched to SQLite FTS5.  submitted by /u/IntelligentHope9866 (https://www.reddit.com/user/IntelligentHope9866)
[link] (https://rafaelviana.com/posts/hug-of-death) [comments] (https://www.reddit.com/r/programming/comments/1ncan42/can_a_tiny_server_running_fastapisqlite_survive/)

1 view09:40

Reddit Programming

Signal Secure Backups
https://www.reddit.com/r/programming/comments/1ncb4hj/signal_secure_backups/

submitted by /u/cheerfulboy (https://www.reddit.com/user/cheerfulboy)
[link] (https://signal.org/blog/introducing-secure-backups/) [comments] (https://www.reddit.com/r/programming/comments/1ncb4hj/signal_secure_backups/)

1 view09:41

Reddit Programming

Incident Report for Anthropic
https://www.reddit.com/r/programming/comments/1ncb4wu/incident_report_for_anthropic/

submitted by /u/cheerfulboy (https://www.reddit.com/user/cheerfulboy)
[link] (https://status.anthropic.com/incidents/72f99lh1cj2c) [comments] (https://www.reddit.com/r/programming/comments/1ncb4wu/incident_report_for_anthropic/)

1 view09:42

Reddit Programming

chalk + debug just got owned on npm… and honestly, this is the nightmare I’ve been expecting
https://www.reddit.com/r/programming/comments/1nccr9m/chalk_debug_just_got_owned_on_npm_and_honestly/

I’ve been around long enough to remember event-stream in 2018, ua-parser-js in 2021, all those “oh crap” moments when a dependency we trusted turned toxic overnight. And now.....?? it's chalk and debug. Two of the most boring, everyday libraries in the JS world.
One phishing email → maintainer creds stolen → new versions published → hidden payload inside.
And here’s the kicker: it didn’t break anything. While the tests, passed.. CI was green... linters, dead silent. We all would’ve shipped it, no questions asked. The payload was nasty but clever for sure... obfuscated code scanning for wallet addresses, swapping them with lookalikes tied to the attacker. So your log-coloring library suddenly moonlights as a crypto thief. That’s what makes my stomach drop. Because as a dev, the workflow is designed to trust the green checkmarks. And yesterday proved those green checks mean nothing when the foundation is poisoned upstream. We love to say “keep dependencies updated.” But that advice is starting to feel like a joke. Updating blindly is how you pull this crap straight into prod. What’s the fix? Honestly, I don’t have a silver bullet. But I know this: Pipelines need context, not just pass/fail. If debug starts calling window.ethereum, something should scream. Security can’t be “some team’s job.” It has to live inside the same workflow where we merge PRs. And maybe we stop pretending that npm install is ever “safe” without deeper inspection. This isnt a weird edge case. It’s the pattern now. And if we don’t adapt, we’ll just keep rolling the dice until the next dependency burns us in production. Anyone else feel like we’re building faster than we can secure the ground under us?  submitted by /u/divson1319 (https://www.reddit.com/user/divson1319)
[link] (https://www.codeant.ai/blogs/npm-chalk-debug-supply-chain-attack) [comments] (https://www.reddit.com/r/programming/comments/1nccr9m/chalk_debug_just_got_owned_on_npm_and_honestly/)

1 view09:43

Reddit Programming

Flow-Run System Design: Building an LLM Orchestration Platform
https://www.reddit.com/r/programming/comments/1nccxwt/flowrun_system_design_building_an_llm/

Flow‑run: building a production‑ready LLM orchestration service I wrote a deep dive into the system design of flow‑run (open‑source). Highlights: • Tasks are atomic units (LLM calls, emails, etc.) and flows connect them as graphs; parallel execution via BFS. • Data model (accounts, providers, models, tasks, flows) → multi‑tenancy + reliable retries. • YAML DSL for providers/models/tasks/flows; /v1 API with client‑generated IDs for dedupe. • Scaling options: horizontal nodes, DB read replicas/clustering; how to choose multiple LLM providers vs multiple accounts. Feedback welcome from folks building orchestration layers or distributed systems: [https://vitaliihonchar.com/insights/flow-run-system-design]() (https://vitaliihonchar.com/insights/flow-run-system-design%5D())  submitted by /u/Historical_Wing_9573 (https://www.reddit.com/user/Historical_Wing_9573)
[link] (https://vitaliihonchar.com/insights/flow-run-system-design) [comments] (https://www.reddit.com/r/programming/comments/1nccxwt/flowrun_system_design_building_an_llm/)

1 view09:44

Reddit Programming

From Modular to Utility-First tailwind migration
https://www.reddit.com/r/programming/comments/1ncd7dh/from_modular_to_utilityfirst_tailwind_migration/

submitted by /u/FrequentBid2476 (https://www.reddit.com/user/FrequentBid2476)
[link] (https://auslake.vercel.app/blog/migration-tailwindcss) [comments] (https://www.reddit.com/r/programming/comments/1ncd7dh/from_modular_to_utilityfirst_tailwind_migration/)

1 view09:45

About

Blog

Apps

Platform