Jony Ive: "I believe we sense when there's care taken with a product” In the clip below, Jony shares that one of the things he has come to feel really strongly is that customers can sense when care has been taken with a product: “I can’t articulate why, but I believe we sense when there’s been care taken with a product. Just in the same way we sense carelessness.” Jony believes that most of our manufactured environment today sadly testifies to a degree of carelessness: “It testifies to: get it built fast, make it cheap, make it look different. There’s just that sort of carelessness. And I just think it’s one of the things that we can strive to do for humanity, and it’s a way that we can serve: is to take care.” This philosophy may have been instilled by Steve Jobs. In Walter Isaacson’s biography of Jobs, there’s a story of the time Jobs insisted that every element of the Macintosh computer be beautiful—down to the circuit boards inside: “Look at the memory chips. That’s ugly. The lines are too close together.” When the computer was finally perfected, Jobs had the engineers’ names engraved inside each one. “Real artists sign their work,” he told them. Isaacson comments: “No one would ever see them, but the members of the team knew that their signatures were inside, just as they knew that the circuit board was laid out as elegantly as possible.” Source: @VanityFair (Oct 2014)

🚨🇮🇱🇵🇸 A Palestinian gunman killed an Israeli in the West Bank earlier today, at a natural spring near Ramallah. The gunman opened fire from inside his vehicle as Israelis gathered near the settlement of Neve Tzuf. When medics arrived, they found a man suffering from critical gunshot wounds; he was later pronounced dead. The gunman was found and apprehended at a hospital. In a separate incident, Israeli soldiers killed a Palestinian driver who they claim was attempting to run them over. On the eve of Yom Kippur, the two incidents COULD be connected... but that much remains unclear. Writer: Michael

Ferrari has just officially unveiled its first ever all-electric car, called the Ferrari Luce. • Starting price: $640,000 • Interior co-designed with Apple's former head of design, Jony Ive • Range: 280 miles (expected EPA) • Peak charging speed: 350kW • 122 kWh battery • 1,050 horsepower • 0-60mph: 2.4s • 800v • Four-door four-seater • Four electric motors • OLED screens • Weight: 4,982 lbs • Front motors spin to 30,000 rpm, rears hit 25,500 rpm • Car uses an accelerometer to capture real vibrations from the electric motors & rear chassis. An algorithm filters out unpleasant frequencies and amplifies only the more “musical” sounds. This can be heard inside and outside the car. • Paddle shifter on steering wheel changes how aggressively torque is delivered, with five different levels • The trunk has 21.1 cubic feet of space, the largest luggage capacity the company has ever offered • 197.6 inches long, about as long as a Tesla Model S U.S. deliveries start in Q2 2027. More photos in the thread below:

Hezbollah shouldn’t have gotten involved on October 8th. It was a valiant and heroic act by Nasrallah, but Palestinians have never been a true friend to Lebanese. PLO in Lebanese Civil War, Hamas-supported terrorists in Syria, Palestinian refugees causing issues in Lebanon. These are some reasons. That’s the opinion from those inside Lebanon I’ve spoken with.

Hi @RobertKennedyJr I'm a cardiologist. I've spent twenty years watching Medicare deny my patients things they actually need — while stories like this one go on for years. RFK Jr. says HHS loses $100 billion a year to theft. Then he described what they found in Los Angeles. Criminals were walking into poor neighborhoods and offering people a $375 flat-screen TV for their patient number. "You don't ever have to go. We're just going to enroll you." Then they billed Medicaid roughly $6,000 a month — forever. A hospice is where you go to die. The average stay is measured in days to weeks. They found people enrolled two and three years later. Still alive. Still billing. Of course they never died — they were never sick. They found a hotel where every single room was a registered hospice. Twenty-nine of them. Zero patients. Just addresses. They shut down 800 hospices. And here's the detail that tells you everything: not one congressman called. Not one owner complained that patients were on the street. Nobody protested, because they all knew exactly what they were running. Now let me tell you what this looks like from inside a practice. I fight for prior authorizations on medications that prevent heart attacks. I get denied for imaging that finds disease early. I have patients rationing insulin. Every dollar in that hotel room was a dollar that didn't go to a nurse, a scan, or a drug that keeps someone alive. Fraud isn't a budget line. It's care stolen from patients who needed it. Two things I'd say if I ever got the room: Use AI to find the outliers. This is not hard. Every claim is already digital. Flag every provider billing five or ten standard deviations above their peers for a service, then audit them. A pattern like 29 hospices at one address, or a "terminal" patient billing for 36 straight months, is something an algorithm catches in an afternoon. We are using AI to read ECGs better than cardiologists — we can absolutely use it to catch a hotel room billing Medicaid. Then talk to practicing doctors. Not consultants. Not administrators. Physicians running busy clinics, who know exactly which codes get abused and which patterns are impossible, because we live inside the billing system every day. We could point at it in an hour. Almost nobody asks us. Catching fraud isn't about cutting care. It's the only way to fund it. Every stolen dollar has a patient's name on it. We just never learn which one.

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.