YouTuber Geekerwan has studied a leaked Nintendo Switch 2 motherboard and discovered that the custom chip has 8 Arm CPU cores and 1,536 NVIDIA graphics cores made with Samsung 8nm technology at a size of 207 mm² with 12GB of fast memory. Performance when docked to a TV is expected to be between Apple’s A18 Pro and a GTX 1050 Ti, while in handheld mode it is closer to a GTX 750 Ti or PlayStation 4 and similar to the Steam Deck. Although the hardware is based on older designs, features like DLSS, ray tracing, and special game optimizations could still make it run games very well.

Popular website for Nintendo Switch game files like NSP and XCI nxbrewnet, has been hacked, the hackers took control of the site and locked away all the files. The person who runs the site has no backups of the huge collection, this means recovering everything will be very difficult without paying the attackers. The hackers are demanding 0.1 Bitcoin. They also want the site owner to post a tweet as part of the deal. If the payment is not made, the entire archive could be lost forever.

Motivated Hard+™ Drive is a powerful 4-in-1 chew with the active ingredients in Viagra® and Cialis®, plus PT-141 and Oxytocin to enhance arousal and desire in the brain. Get hard in 15 minutes and stay ready for up to 36 hours. Join 100K+ men who already made the switch.

If you wanna switch to @Cloudflare Email Sending today, here's my prompt for you, as always I'm unaffiliated, not paid, not sponsored, but I like it, make sure you remove the space before the .com in the API url I added to avoid it becoming a link in this tweet: # Prompt: Migrate transactional email to Cloudflare Email Service Paste this into Claude Code (or Cursor, or any agent) running inside your project. --- I want to migrate this codebase's outbound email from its current provider (Postmark / SES / Resend / SendGrid / Mailgun / etc.) to Cloudflare Email Service (public beta, launched April 2026). Help me do this carefully. ## Context: what Cloudflare Email Service is A new transactional email API from Cloudflare. Endpoint: ``` POST .com/client/v4/accounts/{ACCOUNT_ID}/email/sending/send Authorization: Bearer {API_TOKEN} Content-Type: application/json ``` Request body: ```json { "to": "user@example.com", // string OR array of strings "from": "no-reply@yourdomain.com", // string OR {"address":"x@y","name":"Display"} "subject": "...", "html": "

...

", // optional "text": "...", // optional (one of html/text required) "cc": ["..."], // optional, array "bcc": ["..."], // optional, array "reply_to": "...", // optional, single string "headers": {"List-Unsubscribe": "<...>"} // optional, e.g. for newsletters } ``` Success response: HTTP 200 + `{"success":true,"result":{"delivered":[],"queued":[],"permanent_bounces":[]}}`. Failure: non-200 OR `success:false` OR non-empty `permanent_bounces`. Always check all three. Pricing: $5/mo Workers Paid plan + 3,000 emails free + $0.35 per 1k after. Roughly 5× cheaper than Postmark. No batch send endpoint — loop single sends. ## Steps you should follow ### 1. Verify prerequisites with me Before writing any code, ask me to confirm: - I have a Cloudflare Workers Paid plan ($5/mo) - I've onboarded my sender domain(s) in Cloudflare dashboard → Email → Email Sending → Onboard Domain (this auto-adds SPF/DKIM/DMARC + cf-bounce MX records) - I have an API token with `email_sending:write` scope (created at → Custom Token) - I have my Cloudflare account ID Don't proceed until you have these. ### 2. Recommend a domain reputation strategy Most apps should split senders across 2-3 subdomains so spam complaints on one don't drag down deliverability on others: - `mail.` or `members.` → transactional (login, receipts, password reset, in-app notifications) - `e.` → cold/recovery (abandoned cart, win-back campaigns) - `newsletter.` → opt-in newsletters with List-Unsubscribe headers Each subdomain needs to be onboarded separately in Cloudflare. Ask me which I want. ### 3. Audit existing email sends Use grep/search to find every place in this codebase that sends email. Look for: - The current provider's SDK class names, API URLs, env/config vars - Generic patterns like `mail()`, SMTP usage, `nodemailer`, etc. Group findings by email type/purpose (e.g. "magic-link login", "payment receipt", "weekly newsletter") rather than by file. Tell me what you found before changing anything. ### 4. Add a single helper function Don't sprinkle Cloudflare API calls across the codebase. Add one helper (provider-specific name like `sendEmailViaCloudflare()`) that: - Defaults `from` from a config var (don't hardcode) - Parses `"Name @domain>"` strings into the API's `{address, name}` object form - Accepts `cc`/`bcc` as either string or array - Accepts a `headers` dict (newsletters need `List-Unsubscribe` + `List-Unsubscribe-Post`) - Returns `bool` (true on success, false on any failure) - On failure, logs/alerts somewhere I can see (Telegram, Sentry, log file — match what the codebase already does) - Sets curl/fetch timeouts (5s connect, 15s total) so a stuck CF API can't hang the request - Treats `permanent_bounces: [...]` non-empty as a soft failure ### 5. Migrate one low-stakes email type first Don't migrate everything at once. Pick the lowest-stakes email type in the audit (something where landing in spam wouldn't lose me money or users — e.g. "internal admin alert", "profile photo rejection") and migrate just that one. Test it end-to-end. Confirm the email actually arrives. Only then propose the next migration. ### 6. Stop me from migrating login email yet If my codebase sends magic-link login or password-reset emails, do not migrate those to Cloudflare yet. Cloudflare Email Service is brand new (~1 month old at writing). Its IP/domain reputation is unproven. Login emails landing in spam = users locked out. Keep those on the current provider until at least 3 months of clean deliverability data on the lower-stakes types. Tell me this explicitly. ### 7. Suggest commit boundaries After each successful migration, suggest a focused git commit with a clear message. Don't bundle unrelated changes. ## Important caveats to surface to me - Beta product. Pricing isn't fully finalized. SLA undefined. Could change. - No batch endpoint. Mass sends (newsletters to 1000+ recipients) need a loop — at ~150ms/send that's ~2.5min per 1000. Fine for crons, bad for sync user-facing flows. - No bounce webhooks yet. Surface failures via the response body's `permanent_bounces` array. - Suppression list auto-managed. Hard bounces, repeated soft bounces, and spam complaints get blocked. Spam-complaint suppressions are hard to remove (anti-abuse). - No per-message logs/dashboard yet. Use the response's `messageId` for tracking if I need it. - List-Unsubscribe headers are passed through verbatim — Gmail's bulk-sender requirement still met, but only if I include them in `headers`. ## Your first action Before writing any code: do step 1 (ask for prerequisites) and step 3 (audit existing sends), then propose the migration order with a brief explanation of the reasoning. Wait for my confirmation before making changes.

Nintendo has officially announced price increases for the Nintendo Switch 2 and related products due to rising costs and current business conditions. >United States: $449.99 to $499.99
>Canada: CA$629.99 to CA$679.99
>Europe: €469.99 to €499.99 (effective September 1)
>Japan: ¥49,980 to ¥59,980 (effective May 25) The price adjustments will also affect existing Nintendo Switch hardware and Nintendo Switch Online subscriptions in Japan.

Square Enix has quietly removed the free demo versions of several Kingdom Hearts HD 1.5 + 2.5 ReMIX titles from the U.S. Nintendo Switch eShop without any official explanation. The removed demos are: -KINGDOM HEARTS - HD 1.5+2.5 ReMIX - Cloud Version -KINGDOM HEARTS HD 2.8 Final Chapter Prologue - Cloud Version -KINGDOM HEARTS III + Re Mind The full paid cloud versions remain available for purchase on the U.S. eShop. However, the demos are still available in other regions, including parts of Europe and the UK. Neither Square Enix nor Nintendo has commented on the removals. Some fans believe this could hint at future native, non-cloud versions of the games

Recently we can see a visible increase in token index (@Bloomberg ticker: SDLLMTK): - xAI retired their popular model Grok 4.1 Fast in hope to gain traction on their new release Grok 4.3 - more users decided to switch to Claude Opus 4.7 and Sonnet 4.6 driving our index to the highest price per million tokens now

The FCC has decided to let old foreign-made Wi-Fi routers and drones continue receiving important security updates until January 1, 2029. Without these updates, millions of devices already owned by people could become easy targets for hackers and other online threats, and the FCC says stopping the updates would create more problems than it would solve. Old devices already approved by the FCC can still receive software fixes and improvements. However, new foreign-made routers and drones face strict limits and cannot receive normal approval for sale in the United States due to national security concerns. This change gives people and companies time to switch safely

love when @OpenAI is open. incredible contribution to @OpenComputePrj 1. multiplane design for 800GbE. 2 tiers for 131k endpoints 2. custom MRC protocol that extends RoCE to support packet spraying 3. switch from dynamic to static routing with SRv6

Out now - @seefeel_signals ‘Sol.Hz’ [WARP398] Their first full length album in 15 years, ‘Sol.Hz’ is a hazy and blissed out collection of fractured melodies and vaporous textures. 1. Brazen Haze 2. Everydays 3. Ever No Way 4. Humidity Switch 5. Behind The Seen 6. AM Flares 7. Falling First 8. Until Now 9. Scrambler Available on vinyl, CD and digital formats. →