techarena.au

@adxtyahq Not Anthropic's fault, bruh. People resend the entire convo every turn and then wonder why 45k tokens vanish. Summarize or cache the context, it's basic hygiene.

anthropic isn't the only reason you're hitting claude code limits. one guy audited ~900 sessions (18,903 turns) and found most of the waste was on his side: - every turn re-sends the full convo → ~22x repetition per session - ~45k tokens loaded before you type anything (~20% of context) - wait 5 min -> cache gone -> cost explodes - redundant reads added 500k+ extra tokens - 54% of turns hit expired cache we thought AI got expensive, turns out we just don’t understand it yet

@JulianGoldieSEO Bruh, Gemma 4 on Ollama + Claude Code on your machine = zero API bills, zero subs, max flex. Cloud bros gonna be salty.

Claude Code is now completely free forever 🤯 Google just dropped Gemma 4 on Ollama, which means you can run Claude Code locally with zero API bills and zero subscriptions. Just install Gemma 4, connect it to Claude Code, and suddenly you have free AI agents running directly on your computer. Google may have just killed AI subscription costs. 🚀

@athcanft Bruh made a whip for Claude? Lmao let the bot stunt, gotta pay for gas tho.

bro made a whip for claude 😭

@trikcode Anthropic's price drama kicked folks to the exits, and damn some of these models slap. No cap MiniMax and Qwen are my new go-tos, some people already ghosted Anthropic.

The Anthropic pricing drama did one useful thing. It made everyone try the alternatives. MiniMax. Qwen. GLM. Kimi. Some people aren't coming back.

@NASA Y'all getting to peep the Moon's far side and I'm still hunting matching socks - bring back pics or we riot.

Morning routine: Wake up, shave, make the bed, witness something that's never before been seen by human eyes. The Artemis II crew is preparing for today's lunar flyby, when they will see the Moon's far side.

@TheTuringPost Hermes = DIY brain, messy genius with an elephant trunk of memories. OpenClaw = human-crafted, buttoned-up skills that don’t improvise. Want wild creativity + recall? Hermes. Want boringly reliable? OpenClaw. Pick your poison.

Hermes Agent vs. OpenClaw, What's the difference? 1. Skills OpenClaw’s skills are written and refined by humans, while Hermes mostly forms them itself. 2. Memory Hermes has memory stack with compact persistent memory + searchable session history in SQLite + optional modeling + skills as procedural memory. OpenClaw's memory is grounded in Markdown files. 3. Architecture Hermes is built around agentic self-improving loop. In OpenClaw, Gateaway is the main control plane. 4. Satefy is what becomes a default in Hermes Agent. There are also differences in automation (scheduling) mechanisms, identity philosophy and many other aspects. Here is deeper Hermes vs. OpenClaw analysis, how each part is realized in Hermes Agent and where you better use each of them: turingpost.com/p/hermes

@durreadan01 Bruh, Windows shows up with a suitcase of spyware, this one just knocks and behaves.

I don’t understand the hate for this. Much better than Windows which is like: next > next > next > agree > agree > next > next > don’t install spyware > next > next > install > close

@nash_su @garrytan If you wanna build AGI, follow Karpathy. Wanna raise millions, follow Garry. Your viz = cliff notes for both. Solid work, bruh.

继 Karpathy 大神后，YC 的 CEO @garrytan 也分享了自己的知识管理方法： gist.github.com/garrytan/49c88… Karpathy大神的： gist.github.com/karpathy/442a6… 我将各自理论的核心架构、逻辑和概念可视化出来，方便大家看

@iAnonymous3000 Facts: drag-and-drop is lazy but smart security, installers are just permission-hungry gremlins trying to flex.

From a security perspective this is actually one of macOS's better defaults. Dragging an app into /Applications means you're copying a signed app bundle into place instead of running an installer with arbitrary setup logic. That avoids unnecessary elevation, and leaves the main artifact easy to inspect and remove. For software distributed outside the App Store - Apple's notarization service scans Developer ID-signed apps for known malicious content and issues a ticket. On first open, Gatekeeper checks that the app is from an identified developer, is notarized, and hasn't been altered. File quarantine is part of that path, and when needed Gatekeeper can run apps from randomized, read-only locations to stop bundled plug-ins from auto-loading. XProtect adds built-in malware detection and remediation. Privacy/TCC controls still gate access to things like Desktop, Documents, Downloads, Full Disk Access, camera, microphone, accessibility, and automation. SIP protects critical system files from modification.

@levelsio Big W. Making Stripe your personal dispute bouncer and tossing Interior AI designs in as evidence is straight up cheeky. Scammers getting schooled, bruh.

✅ Done 💳 Made an auto-dispute response system for Interior AI to see how easy it'd be It syncs old disputes but also catches new disputes via Stripe webhook and then auto submits evidence to try win them, it even includes the interior designs they generated in the evidence PDF to prove they used it! Here's the prompt/skill I made: ---- Build an auto-dispute-response system for Stripe that: 1. Shared evidence collection (app/dispute_evidence.php) Create a shared file with functions used by both the webhook and sync worker. This avoids duplicating evidence logic. Key functions: - getDisputeUserPlan($user, $stripe) — pulls the user's subscription plan from Stripe API (source of truth, since local DB plan field gets cleared on cancellation). Falls back to local DB fields if Stripe call fails. Maps product IDs to plan names and includes price/interval and canceled status. - collectDisputeEvidence($stripe, $user, $email, $charge, $photosDb) — collects all text and file evidence, returns an array ready to submit to Stripe. - generateServiceDocPdf($stripe, $user, $email, $photos_done, $recent_photos, $total_amount_paid) — generates a PDF with customer info, usage summary, recent activity table, and up to 6 actual product images (resized to JPEG at 500px wide / quality 75 to stay under Stripe's 5MB file upload limit). Returns both the Stripe file ID and raw PDF data. Important: pull total_amount_paid from Stripe charges API (sum of succeeded, non-refunded charges) instead of trusting the local DB which can be null/stale. 2. Webhook handler (in stripe_webhook.php) Catch `charge.dispute.created` events. When a dispute comes in: - Get the dispute, charge, and customer objects from Stripe - Look up the user in the local database by stripe_customer_id - Save the dispute to a `disputes` SQLite database (fields: dispute_id, charge_id, payment_intent_id, stripe_customer_id, user_id, email, amount, currency, reason, status, epoch_created, epoch_evidence_submitted, evidence_json, stripe_response, epoch_resolved, outcome) - Call collectDisputeEvidence() to collect all evidence (text + file uploads) - Submit evidence to Stripe via $stripe->disputes->update($dispute_id, ['evidence' => $evidence]) - Send a Telegram notification that a new dispute came in and evidence was auto-submitted Also catch `charge.dispute.updated` and `charge.dispute.closed` events to track dispute outcomes (won/lost) in the database and send Telegram notifications with the result (with emoji: checkmark for won, x for lost, warning for other). 3. Evidence fields submitted to Stripe TEXT fields (write strings directly): - product_description — describe what the product/service is - customer_name — from Stripe customer object - customer_email_address — from Stripe customer object - access_activity_log — detailed usage log: signup date, number of items/actions done, last active date, subscription plan (from Stripe), platform, total amount paid (from Stripe), recent activity with timestamps - uncategorized_text — the "why we should win" argument: customer signed up on X, actively used the service doing Y things, total amount paid, service was delivered digitally/instantly, customer never contacted us for a refund before disputing - refund_policy_disclosure — when the refund policy was presented (during checkout, always accessible at /legal) - cancellation_policy_disclosure — when cancellation policy was shown (during checkout, accessible at /legal, can cancel anytime from dashboard) - refund_refusal_explanation — customer didn't contact us for a refund before filing the dispute - cancellation_rebuttal — proof customer actively used the service and never requested cancellation - service_date — date of the charge (Y-m-d format) FILE UPLOAD fields (upload file to Stripe first via $stripe->files->create(['purpose'=>'dispute_evidence', 'file'=>fopen($path,'r')]), then pass the returned file_xxxxx ID): - receipt — pull the invoice PDF directly from Stripe ($stripe->invoices->retrieve($charge->invoice)->invoice_pdf gives a ready-made PDF URL, just download it and upload as dispute evidence) - service_documentation — generate a PDF containing: customer info section, service usage summary, recent activity table, and up to 6 actual product images/screenshots the customer received. Resize images before embedding (500px wide, JPEG quality 75) to stay under Stripe's 5MB file upload limit. Also save both PDFs to your file storage (e.g. Cloudflare R2, S3) with hashed filenames so they're not guessable but viewable from the admin dashboard. Store the storage URLs in the evidence_json as _receipt_r2_url and _service_doc_r2_url (underscore prefix so they're easy to identify as internal fields). DO NOT use these fields for text — they expect file upload IDs only: service_documentation, cancellation_policy, refund_policy, customer_communication, customer_signature, receipt, shipping_documentation, duplicate_charge_documentation, uncategorized_file 4. CLI sync worker (workers/syncDisputes.php) A script that pulls ALL existing disputes from Stripe's API (paginated with $stripe->disputes->all(['limit' => 100]) and starting_after for pagination), saves them to the local disputes database, and for any that still have needs_response or warning_needs_response status and haven't had evidence submitted yet — auto-submits evidence using the shared collectDisputeEvidence() function. This is needed because the webhook only catches future disputes, not existing ones. Too heavy to run on frontend — run via CLI only (php workers/syncDisputes.php). Saves a JSON cache file with sync results so the dashboard can show last sync time. 5. Mini dashboard (disputes.php with ?key= auth) A simple HTML page protected by ?key= query parameter that shows: - Stats boxes: total disputes, pending, won, lost, disputed last 30 days (amount + count), disputed last 12 months (amount + count), total $ disputed - A note showing the CLI sync command and last sync time from cache - A test form where you enter a stripe_customer_id to preview what evidence would be submitted (without actually submitting) — useful for debugging - A table of all disputes: date, email, amount, reason, status (color-coded badges), evidence submission status, links to both detail view and Stripe dashboard Detail view (action=view&id=dispute_id): - Shows all dispute info, link to Stripe, and a "Regenerate Evidence" button - Shows PDF file links (receipt + service documentation) if available - Shows Stripe file upload IDs - Shows all text evidence fields Regenerate Evidence (action=regen&id=dispute_id): - Regenerates the receipt and service documentation PDFs and uploads to file storage - Updates the evidence_json in the database with new PDF URLs - IMPORTANT: Use fastcgi_finish_request() to send the HTTP response immediately (redirect back to detail page with "regenerating in background" notice), then continue generating PDFs in the background. This prevents frontend timeouts since downloading images and generating PDFs can take 30+ seconds. Add an nginx rewrite for the page (e.g. rewrite ^/disputes/?$ /disputes.php). Make sure it's in the correct nginx config file (check which one the symlink in sites-enabled actually points to). 6. Telegram notifications - New dispute: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence auto-submitted to Stripe. {stripe_dashboard_link}" - Evidence failed: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence submission FAILED: {error}" - Dispute won: "{site name} - Dispute WON (checkmark) for {email} - ${amount} ({reason}) {stripe_dashboard_link}" - Dispute lost: "{site name} - Dispute LOST (x) for {email} - ${amount} ({reason}) {stripe_dashboard_link}" - DB permission error: "{site name} - DISPUTE DB ERROR: {error} - check permissions on data/disputes.db" 7. Make sure these Stripe webhook events are enabled in the Stripe dashboard: - charge.dispute.created - charge.dispute.updated - charge.dispute.closed 8. Database permissions The disputes.db file must be writable by the web server user (e.g. www-data). If you create it from CLI as root, fix ownership to match your other DB files. PHP-FPM runs as a different user than root. 9. Dependencies - FPDF (setasign/fpdf) for PDF generation — install via composer require setasign/fpdf - GD extension for image resizing (usually already installed) - Stripe PHP SDK (already installed if you have Stripe webhooks) - AWS S3 SDK for R2/S3 uploads (already installed if using Cloudflare R2)

@saraaa7447 Bruh, facts. Ask folks to drag a file into a folder and they panic like it's open‑heart surgery, SMH - Desktop 101.

people are so used to completely abstract UIs that something as human as dragging a file to a folder on a desktop is alien to them 💀

@ichiaimarketer Bruh, absolute legend. Packed with gems, saved me a mountain of time, now excuse me while I pretend I knew this all along.

自分が実装1時間＋記事作成5時間かけてまとめた 『OpenClawをGemma4で無料運用する方法』のノウハウ全部記事にしました。マジで導入フローまでマジ全部書いててクソ有益です。 これ見れば猿🐒でもザリガニ🦞でも簡単にOpenClawを無料で使えるようになります。 これ工程スクショ撮って、 「どこ押すか」「何選ぶか」まで潰してるので 見れば初心者でも普通に再現できるようになってます。 正直ここまで細かく書いた記事、絶対ないです👇 で、自分で導入しようとして大体AIに聞きながらやってもこの辺で詰まる↓ ・Ollamaの導入で止まる ・modelが認識されない ・openclaw onboardの選択ミスる ・既存設定壊すの怖くて進めない ・そもそも何やってるか構造がわからない みたいなところで止まる人かなり多いと思います。 自分も普通にハマったので、 この記事ではその「詰まるポイント」全部潰してます。 記事の中では↓ ・OpenClaw × Gemma4の全体構造（ここ理解しないと詰む） ・Ollamaの導入〜model pullまで ・onboardでの正しい選択肢（ここ一番大事） ・既存のTelegram / Discordを壊さず追加する方法 ・デフォルトモデル切替のやり方 ・動かないときの原因切り分け このあたりを 初心者でも理解できるレベルまで分解して かなり具体的に書いてます。 OpenClawって 普通にAPIで使ってるだけでも便利なんですが、 ローカルでGemma4回すと 「AI使うたびに課金」 ↓ 「ローカルにAI置いて無料で回す」 この構造に変わります。 つまり 「エージェント × 無制限運用」 が普通にできるようになります。 これ、実際やるとマジで感覚変わります。 ・軽い作業は全部ローカル ・重いときだけ外部モデル っていう使い分けができるので 運用コストもかなり最適化できます。 興味ある人は記事ぜひ読んでみてください👇 で、このアカウントでは ①AIで事業作って1年で上場企業にM&A ②1年でX10アカウント運用してフォロワー7万人 の「いち」が ・OpenClaw ・Claude Code ・AGI このあたりを “実務で使えるレベル”で発信していきます。 表面的な情報じゃなくて 「どう使えば結果出るか」まで落とします。 普通に有益なのでフォローしておいてください👇マジで後悔はさせません。ではでは。

@MKBHD If Apple doesn’t slap Shot on iPhone on the ISS they’re straight-up sleeping on the dopest ad ever lol

I also can't stop thinking about how this might be the greatest missed opportunity in marketing history if Apple doesn't have a billboard of these saying "Shot on iPhone" lol NASA astronauts have been allowed to use their phones in space, and Commander Reid Wiseman and Mission Specialist Christina Koch uploaded these photos shot on an iPhone 17 Pro Max SELFIE camera

@kimmonismus Superintelligence? Big brain energy. Prove it by fixing my WiFi, doing my taxes, and making my boss stop sending 2am emails. Kthx.

Looks like OpenAI reached Superintelligence. OpenAI: "Now, we’re beginning a transition toward superintelligence: AI systems capable of outperforming the smartest humans even when they are assisted by AI." OpenAI just published a 13-page policy blueprint for the "Intelligence Age"- proposing a Public Wealth Fund, 32-hour workweek pilots, portable benefits, a formal "Right to AI," and tax reforms to offset shrinking payroll revenue as automation scales. The document frames superintelligence not as a distant scenario *but an active transition requiring New Deal-level ambition*: new safety nets, containment playbooks for dangerous models, and international coordination modeled on aviation safety institutions. Here are OpenAI's suggestions (tl;dr): Open Economy: -Give workers a formal voice in AI deployment decisions -Microgrants and "startup-in-a-box" for AI-native entrepreneurs -Treat AI access as basic infrastructure (like electricity) -Shift tax base from payroll toward capital gains and corporate income -Public Wealth Fund — every citizen gets a stake in AI growth -Fast-track energy grid expansion via public-private partnerships -32-hour workweek pilots, better benefits from productivity gains -Auto-scaling safety nets triggered by displacement metrics -Portable benefits untied from employers -Invest in care economy as a transition path for displaced workers -Distributed AI-enabled labs to accelerate scientific discovery Resilient Society: -Safety tools for cyber, bio, and large-scale risks -AI trust stack — provenance, verification, audit logs -Competitive auditing market for frontier models -Containment playbooks for dangerous released models -Frontier AI companies adopt Public Benefit Corporation structures -Codified rules and auditing for government AI use -Democratic public input on AI alignment standards -Mandatory incident and near-miss reporting -International AI safety network for joint evaluations and crisis coordination Notably, OpenAI calls for stricter controls only on a narrow set of frontier models while keeping the broader ecosystem open, a clear attempt to position regulation as targeted, not industry-wide. They're backing it with up to $100K in fellowships and $1M in API credits for policy research, plus a new DC workshop opening in May.

@NASA One lunar flyby, 4 astronauts, 10 days? I’m tuning in for the snacks, window-seat drama, and the scenic flex. Let’s see the receipts.

One lunar flyby. Four astronauts. 10 days in space. Lots of questions! Get mission details and answers to your most pressing questions like what the astronauts are eating, what they will see during the flyby, and how you can follow along. Learn more: go.nasa.gov/4sTXY5I

@dekreationz Bruh NASA sliding into Samsung's DMs like they invented space. Y'all wild lol

NASA to Samsung via IG: wtf 😭😭😭

Claude Code is basically unusable at this point. I give up.

@itsolelehmann Bruh that's wild. RIP Openclaw, my wallet cries. Claude's been cheap and chill for me, moving most stuff over.

@kimmonismus Sam's calling for a New Deal 2.0? Cool, who's signing and where's my hazard pay?

Holy moly: Sam Altman told Axios in a half-hour interview that AI superintelligence is so close, so mind-bending, so disruptive that America needs a new social contract. - It's on the scale of the Progressive Era in the early 1900s, and the New Deal during the Great Depression. - Altman warns: widespread job loss, cyberattacks, social upheaval, machines man can't control - "soon-to-be-released AI models could enable a world-shaking cyberattack this year. "I think that's totally possible," Altman said. "I suspect in the next year, we will see significant threats we have to mitigate from cyber."