Sabitlenmiş Tweet
trae.com
2.4K posts
I finalyyy redesigned my portfolio as a Gameboy game! I had this idea a few months ago and cant believe how it came out :)
esmeraldanava.com
Huge shout out to @SnakeMGL for the animation, I had a ton of fun working with your creation. #threejs
English
The "Claude VS Codex" debate soon:
GIF
Unitree@UnitreeRobotics
Unitree Unveils: GD01, A Manned Transformable Mecha, from $650,000 👏 The world's first production-ready manned mecha. It can transform. It's a civilian vehicle. It weighs ~500kg with you inside. Please everyone be sure to use the robot in a Friendly and Safe manner.
English
only 300 views
but it showed up on Pieter's feed, wtf 😂
Vincent@VynseDev
ONE IMAGE → ONE PLAYABLE BIKE this is the simplest workflow: 1. generate image with GPT image 2 2. copy paste into @MeshyAI "image to 3d" → low-poly 3. add texture, using the same image 4. download GLB & play it ✅ 10+ bikes to unlock ✅ 5 tiers (250cc, 500cc...) ✅ showroom for bikes + avatar customisation (later) different visual styles, I'm thinking of keeping the first bikes a bit old-school, and the better they get, the better they look, what do you think? now adding speed effects, new bikes for bots, then work on physics (collisions, hitboxes, then combat) already hard to stick to one artistic direction, it's too fun to experiment 😂 appreciate any suggestions and RT for visibility 🙏🏼
English
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": "user@example.com", // string OR array of strings
"from": "no-reply@yourdomain.com", // string OR {"address":"x@y","name":"Display"}
"subject": "...",
"html": "` 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.
...
", // 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 dash.cloudflare.com/profile/api-to… → 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.@levelsio@levelsio
✉️ Trying @Cloudflare's new Email Sending feature today If you send 1,000,000 emails per month: - Postmark: $1,206/mo - Resend: $650/mo - SendGrid: $600/mo - Cloudflare: $354/mo - Amazon SES: $100/mo So Postmark is now by far the most expensive email provider And SES and Cloudflare are now the cheapest email providers I know my friend @marckohlbrugge is trying out SES now so I'll try Cloudflare and see how it is, SES is cheaper but Marc said it takes a bit more managing, and since I already use so much Cloudflare stuff it's nice to use them for email too With AI especially all of these are just as easy to use and setup in your app/site so economically it makes sense to go for the cheapest, because email is just email, it's all the same and deliverability is good with all of these I think TL;DR email sending has become a commodity!
English
@jameygannon @figma @floraai @ChatGPTapp @GoogleLabs @jittervideo @capcutapp @suno I didn't know gradients could be like that
English
Tools used:
graphics: @figma
imagery/video: @floraai – @ChatGPTapp @GoogleLabs
motion design: @jittervideo @capcutapp
music: @suno
techbimbo@jameygannon
new work for @getmilana done with @JCKHLRY project breakdown 👇
English
stoked to add this to my video workflow
Jeremy Yudkin@yudDIDit
Today, @editframe emerges from stealth. Agents need video. Editframe Agent Skills: npm create @editframe@latest Just prompt Claude Code, Cursor, or Codex and get a working video or a full interactive GUI. This video was created just by prompting 👇
English
A sneak peek on the multiplayer mode I'm adding to my game for @levelsio's 2026 #vibejam
I'm really happy with how this is turning out!
Big shoutout to @colyseus for such a nice framework.
I fetched the whole docs, created a colyseus-skill.md file and it's pretty much one shotting everything (still need some tweaks and testing, of course)
I'm just not very happy with the single character model, it looks weird on multiplayer.
I might add more if I get the time.
English
It's my birthday today and all I want is for you to come build a really fun platforming level in my video game.
It's like Mario Maker meets r/place and it's called
< We All Make A Platformer >
wamp.land
English
No titans today, instead for #vibejam day 6 it's rooftop parkour while being chased by some very janky enemies
Kieran Smith@imkieransmith
I can't stop running around in my titan! I spent day 5 of #vibejam refining the boarding sequence and cockpit HUD. Really pleased with how it's turned out.
English
A new class of founders is emerging. The team put together a fun mini site to help find what kind of founder you are.
Anton Osika@antonosika
Eighteen months ago, we launched Lovable. We had a theory about who would show up. We were wrong. A new class of founders is emerging. Founders like John, who turned a former church into a $30K/month arcade business in three months, building every digital system himself on Lovable. Or Will, a Grammy-nominated songwriter, who built Disco after realizing 73 million freelancers like him had no good solution for tax season. Every week, we see someone new: a nurse, a teacher, a marketer, a filmmaker, a 16-year-old. People closest to the problems are now building the solutions. Millions of founders are building on Lovable. And we know the build is just the start. We're focused on helping people create real businesses with customers, feedback loops, and growth. And as the technology keeps getting better, more people will succeed. Our focus stays the same: real founders, real businesses, and real solutions. Entrepreneurship is the fastest way to change the world. More builders means more problems get solved in the world. I can't wait to see what problems this generation solves.
English
