Igor ➔ extcontabilidade.com.br

Building @extcontabilidad #buildinpublic #indiehacker Tweets in 🇺🇸 & 🇧🇷

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

@lincolixavier @oprimodev Entao, arrumamos, agr mandamos com dias de antecedência pra n esquecer de pagar kkk

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

Coupon com 50% OFF pra você não se preocupar com oq o sushi disse
https://t.co/6hccYZFoni

[sushi com abacate @sushicomabacate]

Sempre procurem um contador pra virar PJ

Ele vai explicar que vcs nao devem abrir uma empresa de "desenvolvimento de software” mas sim uma de
- manutenção de CRUD/legados/servidores onpremise
- treinamento de deploy às sextas-feiras

Caindo direto no Anexo III sem Fator R

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

@thayto_dev @dev_VictorRb O tenho o msm problema com o meu hd
Comprei o clean my app e ajuda bastante, mas tou vendo de atualizar o mac

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

PRAZO DO IR da PF É AMANHÃ!

Migrando a contabilidade da sua empresa pra Ext tu ganha o IRPF de graça
https://t.co/sXc6eToUna

[Garry Tan @garrytan]

Founders must stop trying to building 2010-era businesses with 2026-era technology.

Don't try to rebuild Foursquare or Yelp.

Don't try to recreate Basecamp by 37 Signals with $10/mo SaaS pricing.

Don't underprice! If it works it's worth a lot more.

Don't be tempted to become "Tech enabled PE" with revenue tricks.

The rules of tech changed with AI. Play the new game.

[Sibelius Seraphini @sseraphini]

Existe algo pior que o CLT do Brasil?

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

@onicolasrivera @osouzajefferson

[Cafe ➔ zumypay.com.br @maiscafepf]

Vou iniciar a migração da zumy para a ext contabilidade do @igorhalfeld
Foi um dos melhores atendimentos a apoio que encontrei, parabéns Igor.

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

@maiscafepf Bora q bora

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

@lucasmoraisdev @Mirandaverso É osso

[antonio realoficial.com.br | viral.day @acgfbr]

saimos da faria lima e agora estamos em ourinhos

somos ext contabilidade, tamo junto @igorhalfeld ajudou demais nessa migraçao fiscal

com preço em real e nota fiscal, só o real oficial
https://t.co/DRHmjmDAcW

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

👀

[ChatGPT @ChatGPTapp]

A preview for Pro users: a new personal finance experience in ChatGPT.

Pro users in the U.S. can securely connect financial accounts, see where their money is going, and ask questions based on the information they choose to connect.

Your full financial picture, now in ChatGPT.

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

Toda semana um bo novo de sec

Os caras tão usando IA errado 👍

Tem que lembrar de colocar no prompt:
Make no mistakes AND a security review

[Socket @SocketSecurity]

Update: Socket has found 121 more compromised npm package artifacts across 84 package names, including 64 UiPath artifacts.

Combined w/ TanStack, the current known total is 205 affected npm package artifacts across enterprise automation, AI/MCP, auth, workflow, and dev tooling.

[@levelsio @levelsio]

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 https://api.cloudflare .com/client/v4/accounts/{ACCOUNT_ID}/email/sending/send
Authorization: Bearer {API_TOKEN}
Content-Type: application/json
```

Request body:

```json
{
"to": "[email protected]", // string OR array of strings
"from": "[email protected]", // string OR {"address":"x@y","name":"Display"}
"subject": "...",
"html": "<p>...</p>", // 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 https://t.co/s5aigJ6CKV → 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.<domain>` or `members.<domain>` → transactional (login, receipts, password reset, in-app notifications)
- `e.<domain>` → cold/recovery (abandoned cart, win-back campaigns)
- `newsletter.<domain>` → 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 <email@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.

[Igor ➔ extcontabilidade.com.br @igorhalfeld]

@pvbinatto @dlemesdev me chama discord? tu me encontra lá pelo mesmo @

[Kaio Caldeira @KaioCaldeira]

@dlemesdev A @extcontabilidad do @igorhalfeld

[Caio @caiolombello]

@dlemesdev curto mt a @extcontabilidad do @igorhalfeld

[Claude @claudeai]

We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity.

This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.