CanBeSolved

Developers stare at screens for 8-12 hours a day. Yet, we pick our IDE themes based purely on "vibes." Today is Day 1 of building the Endgame: an code, term and text-editor color theme engineered entirely based on eye biomechanics, science-baked data and other key factors.

@FFmpeg @X @OBSProject Thank you for your hard work and contributions.

FFmpeg's native AAC encoder has just been rewritten, and now beats both fdkaac and qAAC according to current metrics and listening tests. This is not a small change. @X and @OBSProject use it, as well as many others. It's been a critical piece of the internet, and is now the best

@sysxplore GNU/Linux for sure

Name a better OS than Linux. I'll wait.

@Itsfoss It's just not released yet

Name a better office suite than ONLYOFFICE. I'll wait.

@Etched 🎂Awesome. Will wait for thermal tests and benchmarks.

We're coming out of stealth. We've built our first racks after a successful A0 tapeout, $1B+ in customer contracts, and $800m raised. Early customer tests show us achieving SOTA throughput, latency, and power efficiency on inference workloads. Our first racks ship this summer.

Day 10. An interesting result. I need to make some adjustments in tones, but we are already seeing positive outcomes

🦾Project Endgame. Day 10. The first prototype is ready, and we are starting real-world testing in different tasks.

✅Project Endgame. Day 9. After multiple rounds of testing and calculations, the halation and chromatic aberration issues have been successfully resolved.

@phoronix Very interesting.

Infinity Scheduler Aims To Be A Better Linux Scheduler phoronix.com/news/Infinity-…

✅Project Endgame. Day 8. Pursuing perfection. The first prototype is coming together. Today I'm focused on reducing halation/glow and chromatic aberration - small details that make a big difference in long-term readability and visual comfort.

@code Very relevant information. Thank you for your work.

🤖 Ready to get started with Agentic Development in @code? We've put together 3 free courses covering everything from building your first AI agent to customizing and extending agent workflows. A quick breakdown 🧵👇

@alexxubyte Thank you for sharing

API Security Best Practices Most API breaches happen because of broken authorization, leaked secrets, or missing rate limits. Let's look at some of the basics. - Use Modern OAuth/OIDC + MFA: PKCE for public clients, short-lived tokens, and step-up MFA for anything sensitive. Implicit and password grants should be dead by now. - Enforce Fine-Grained Authorization: Check object, function, and field-level permissions on every request. BOLA is still the top API vulnerability. - Minimize Scopes and Data: Give each client the smallest token scope and the least data it needs. Only return the fields the caller actually needs. - Encrypt Every Hop: TLS for external traffic and mTLS between services. If it crosses a network boundary, encrypt it. - Protect Secrets and Keys: Store signing keys in HSM-backed vaults. Rotate them. - Validate Requests with Schemas: Reject unknown fields, oversized payloads, and suspicious URLs at the gateway. Don't let bad input reach your business logic. - Rate Limit and Cap Resources: Quotas per user, payload size caps, and execution timeouts. Without these, one misbehaving client takes down your entire system. - Defend Sensitive Business Flows: Protect login, checkout, and OTP with anti-bot, idempotency keys, and step-up auth. - Control Outbound and Third-Party Calls: Allowlist where your API can call out to and block internal metadata endpoints. Your security is only as strong as your weakest integration. - Harden Config and Error Handling: Deny by default on CORS, methods, and debug endpoints. Return generic errors, never stack traces. - Inventory APIs and Versions: Track every endpoint, version, and shadow API. You can't secure what you don't know exists. - Log, Detect, and Respond: Push auth decisions and anomalies to a SIEM. Alert on 401 spikes before they become incidents. Over to you: Which of these best practices is the hardest to enforce across your services?

✅ Project Endgame. Day 7. Tools ready, criteria defined. Time to make first prototype.

@IBMNews Increadible. Sincerest congratulations!

The world’s first sub‑1 nanometer node chip is here. Delivering 70% greater energy efficiency, this breakthrough powers a new era of computing that’s more capable while using less energy. Dig into this next-gen tech: ibm.co/6016EOHpM

✅ Updated diagram to v3. Added semantics: - color related (red - alert, yellow - warning, green - good) - human-language related (letters, numbers, symbols) - software related (IDE, text editor) (comment, function, variable, condition)

Endgame/Day6: ✅ Updated diagram to v2. Added visual effects factors: - Chromatic aberration - Halation

🤔Did you know that most IDE themes use blue tones, even though the cones in the human eye responsible for detecting blue light make up only about 7% of the total? I am developing an innovative color theme based on eye biomechanics and scientific data. Which color palette or theme do you prefer?

Endgame/Day5: On the path to innovation. The diagram is ready. I am presenting the list of factors and criteria that influence perception and must be taken into account when creating a color theme. What else is missing in your opinion?

Next, I’m adding CIEDE2000 as a reference metric — alongside APCA for actual text readability. The goal: calibrate a color system with perceptual data, not guesswork.

I'm currently developing a diagram of influencing factors. At the same time, I'm working on a tool that ensures perfect contrast compliance and calibration using WCAG/APCA standards and OKLCH for color correctness.

@RajputNikh13836 Stay calm

what is the biggest challenge 0f tech person in todays market ?