标签：#c

عندما توقف Claude Fable 5 عن العمل في 12 يونيو 2026 بموجب ضوابط التصدير الأمريكية، فعل فريقك ما فعلته أغلب الفرق: أعاد توجيه الإنتاج إلى Claude Opus 4.8 أو Sonnet 4.6، أصلح الأوامر المعطلة، وتجاوز الانقطاع. رُفعت الضوابط في 30 يونيو، وعاد Fable 5 للعمل اعتبارًا من 1 يوليو عبر Claude.ai ، وواجهة برمجة التطبيقات API، وClaude Code، وCowork. أكدت Anthropic إعادة النشر الكامل في إعلانها الرسمي . جرّب Apidog اليوم الخطوة السهلة هي التراجع عن آخر تغيير في التكوين واعتبار المشكلة منتهية. لا تفعل ذلك. الخدمة التي تعود إليها ليست بالضرورة مطابقة سلوكيًا لما استخدمته قبل الانقطاع: أُعيد تدريب طبقة الأمان، وقد تختلف جاهزية المنصات السحابية حسب المنطقة، وأصبح Opus 4.8 الذي استخدمته لثلاثة أسابيع خط الأساس العملي للمقارنة. تعامل مع العودة إلى Fable 5 كترحيل إنتاجي: تحقق، اختبر، قارن، ثم اطرح تدريجيًا. جرد ما تغير أثناء غيابك بين 12 يونيو و1 يوليو، تغيرت ثلاثة أشياء. وشيء واحد بقي كما هو. 1. أُعيد تدريب مصنف الأمان يأتي Fable 5 المعاد نشره مع مصنف أمان أُعيد تدريبه لاستهداف تقنية كسر حماية أُبلغ عنها أثناء الانقطاع. تقول Anthropic إنه يحظر أكثر من 99% من محاولات استخدام هذه التقنية. النقطة المهمة للتطبيقات الإنتاجية: الطلبات المصنفة لا تفشل بالضرورة. تُعاد توجيهها تلقائيًا إلى Claude Opus 4.8. الرد يحمل إشعارًا بذلك. أكثر من 95% من الجلسات لا ترى أي تراجع. هذا يعني أن أوامرك تعمل الآن أمام طبقة أمان مختلفة قليلًا. لا تفترض أن نتائج أوائل يونيو ما زالت صالحة؛ أعد الاختبار. 2. تحقق من حالة المنصة السحابية أعاد Amazon Bedrock دعم Fable 5 في 1 يوليو، في نفس يوم واجهة برمجة التطبيقات الأساسية، لكن ملفات تعريف الاستنتاج الإقليمية قد تُطرح بشكل غير متساوٍ. قد يكون Google Vertex AI وMicrosoft Foundry ما زالا في مرحلة اللحاق. توجيه Anthropic للمنصات المعلقة هو "بأسرع وقت ممكن"، بدون تاريخ محدد. إذا كنت تستخدم موفرًا سحابيًا، لا تغيّر الإنتاج قبل التحقق من: توفر Fable 5 على المنصة. توفره في المنطقة التي تستخدمها. توافق اسم النموذج أو ملف تعريف الاستنتاج مع تكوينك الحالي. 3. خطط الاشتراك لها تاريخ يجب مراقبته إذا كان أعضاء الفريق يستخدمون Claude عبر خطط الاشتراك بدلًا من مفاتيح API، فهناك تغ

Your portfolio is often the first impression a recruiter, client, or fellow developer gets of you. If it loads slowly, ranks nowhere on Google, or is a pain to update, it's working against you instead of for you. Here's how I approached optimizing mine — covering performance, SEO, and everyday usability. 1. Start With a Lightweight Foundation The biggest performance wins come before you write a single line of custom code. Pick a lean stack. Static site generators (Astro, Next.js with static export, Hugo, or even plain HTML/CSS/JS) ship far less JavaScript than a full SPA framework for a mostly-static portfolio. Avoid unnecessary UI libraries. A heavy component library for a five-page site adds kilobytes you don't need. Hand-roll simple components instead. Use system fonts or self-host web fonts. Pulling fonts from a third-party CDN adds an extra DNS lookup and render-blocking request. Self-hosting with font-display: swap avoids layout shift and speeds up first paint. 2. Optimize Images (This Is Usually the Biggest Win) Images are almost always the heaviest assets on a portfolio site. Convert images to WebP or AVIF — typically 30–50% smaller than JPEG/PNG at the same visual quality. Resize before upload. Don't serve a 4000px-wide photo in a 600px container. Use loading="lazy" on below-the-fold images so the browser doesn't fetch them until needed. Add explicit width and height attributes to prevent layout shift (this also helps your Cumulative Layout Shift score). <img src= "/project-thumb.webp" alt= "Project screenshot" width= "600" height= "400" loading= "lazy" /> 3. Minimize and Defer JavaScript Ship only the JS a page actually needs — code-split per route if your framework supports it. Defer non-critical scripts (analytics, chat widgets) with defer or load them after the page is interactive. Audit your bundle with a tool like source-map-explorer or your framework's built-in bundle analyzer to catch unexpectedly large dependencies. 4. Nail the SEO Basics Good perf

Yes, I said final. Fight me in the comments. But seriously: there are basically exactly 3 serious JS runtimes in the world. (Now 4... or 1, idk). Why? Because the modern JS ecosystem is a fragmented, bloated nightmare. Node, pnpm, tsc, eslint, prettier, vite. Each spins up its own V8 instance, parses your codebase from scratch, and leaves a graveyard of .json configs in your root directory. meow squishes it all into one cute 82MB binary. It’s a drop-in Node replacement, ultra-fast package manage

Please post your personal projects, startups, product placements, collaboration needs, blogs etc. Please mention the payment and pricing requirements for products and services. Please do not post link shorteners, link aggregator websites , or auto-subscribe links. -- Any abuse of trust will lead to bans. Encourage others who create new posts for questions to post here instead! Thread will stay alive until next one so keep posting after the date in the title. -- Meta: This is an experiment. If the community doesnt like this, we will cancel it. This is to encourage those in the community to promote their work by not spamming the main threads. submitted by /u/AutoModerator [link] [留言]

AI is changing how we build software, but I think a lot of developer tools are solving yesterday's...

Shared mailboxes for teams and AI agents Discussion | Link

https://www.gnosyslabs.com/case-studies/safety-classifier-sparse-labels Gnosys is an autonomous model engineer: it improves prompts and classifiers when ground truth is too sparse for conventional optimization. On ToxicChat, a public safety benchmark, under realistic label scarcity, it improved a classifier past both the team's starting point and GEPA (a standard prompt optimizer), across two runs of our current method. This note describes what we did, what we found, and where the method underperformed. Results We report harm caught : the share of harmful messages flagged, holding the false positive rate fixed at 5% (one in twenty) for every method, so a difference reflects additional harm caught at the same cost rather than a change of threshold. Both runs below are scored on a held-out set the system never saw. Headline run (3,000) Prior run (1,000) Gnosys 0.777 0.909 Starting classifier 0.731 0.788 GEPA 0.702 0.848 In both runs, Gnosys improved on both the starting classifier and GEPA. In the headline run GEPA not only trailed Gnosys but fell below the starting classifier (0.731 to 0.702); in the prior run it improved on the starting point. This inconsistency is the central difficulty under sparse labels: optimization sometimes helps and sometimes harms, and without trustworthy measurement there is no way to tell which has happened. The comparison is intentionally conservative: both approaches use the same underlying optimizer. The only difference is that Gnosys engineers the objective the optimizer works against. The problem Teams running high-stakes AI classifiers, in content moderation, fraud, claims review, and risk scoring, share one constraint: the ground truth they need is a human judgment that is expensive, slow, and sometimes never arrives. They can verify only a small set of examples while decisions accumulate on everything else. Tuning the model against the few labels on hand is where the difficulty concentrates. Here "few" is literal: about 200 verifi

Every developer has that one project. The passion build that sits in the back of your mind for months—or even years—before you finally sit down, crack your knuckles, and make it a reality. For me, that project was building a modern, open-access bilingual digital lexicon bridging English and Assamese: AssameseDictionary.org . While it started as a personal milestone dream, it quickly turned into a massive data engineering and architecture challenge. Here is how I tackled parsing a massive vocabulary database and serving it globally with near-zero latency. 🏗️ The Core Challenge: Scale vs. Speed A dictionary isn't like a standard SaaS app or landing page. It lives and dies by its database depth. To make this a truly definitive tool, I compiled, cleaned, and programmatically validated an extensive vocabulary index mapping over 293,000 words . The dataset doesn't just hold simple translations; it maps complex bidirectional lookups, phonetic transliterations, advanced English definitions, context usage examples, and cross-linked synonym tokens. If I threw this massive dataset into a traditional relational database hooked up to a standard server setup, I ran into immediate roadblocks: Latency: Heavy search queries on a dataset this size can cause noticeable lag. Cost/Overhead: Maintaining and scaling database servers for unpredictable public traffic gets expensive fast. I wanted the search utility to snap back instantly. To achieve that, I had to ditch traditional server paradigms entirely. ⚡ The Architecture: Serverless Edge Caching To keep things ultra-lightweight, highly cost-effective, and blazing fast, I built the platform around an edge-computing topology: The Runtime: I offloaded the backend logic entirely to Cloudflare Workers . Instead of routing traffic to a centralized origin server, queries are intercepted and executed at serverless edge locations physically closest to the user. The Data Layer: Instead of an active SQL database bottleneck, I mapped the data mat

Introduction: Unveiling the Critical Vulnerability The recently identified CVE-2026-8037 vulnerability in Progress Kemp LoadMaster represents a critical threat to enterprise infrastructure. This remote code execution (RCE) flaw, stemming from an uninitialized heap issue , enables pre-authentication exploitation, allowing attackers to bypass initial security barriers without valid credentials. The root cause lies in the failure to initialize dynamically allocated memory regions, creating an exploitable condition where untrusted input can corrupt critical data structures. Attackers leverage this memory corruption to redirect program execution to malicious payloads, achieving full system compromise—from data exfiltration to operational disruption. Technically, the vulnerability arises during the software’s handling of untrusted input. When memory chunks in the heap are allocated but not properly initialized, they retain residual data or undefined states. Attackers exploit this oversight by crafting inputs that overwrite function pointers or control-flow structures, hijacking the program’s execution path. The causal sequence is precise: uninitialized heap → memory corruption → arbitrary code execution → system compromise. The pre-authentication nature of the exploit exacerbates the risk, as attackers require no prior access to execute their payload, rendering perimeter defenses ineffective. The implications are severe for enterprises relying on Kemp LoadMaster for load balancing and application delivery. Unpatched systems are exposed to infiltration, data theft, and ransomware deployment. Beyond the technical failure, CVE-2026-8037 exposes systemic deficiencies: insufficient input validation in software design and inadequate security testing during development. Organizations further amplify risk through delayed patch management , creating a critical window of opportunity for attackers. Immediate remediation is imperative to prevent catastrophic breaches that could under