Viktor

@PrimalNick let me import existing floor plans pls

Every home is now editable

@adamguild Sick -- when are you launching for hotels?

Introducing Grader: the world's first AI CMO for restaurants. It’s helped us drive over $1 BILLION in sales for our customers. Grader outperforms human marketing teams. See how:

@Bootsblac @opengeometry @threejs @GoogleAI Badly need this, hit me up with an invite pls 🙏

Geometry changes everything. Geometry was the missing layer in AI. We believe if you don’t own the geometry, you don’t own the outcome. Now it’s obvious. Text → Floorplans → CAD → Render Made with @opengeometry, @threejs @GoogleAI #aec #bim #cad #architecture #building

📢 Brand designers: what I want to buy from u is not a static brand book but a series of @floraai techniques that you maintain for me. Help me help my marketing team put the brand to use and I'd happily pay you per generation so that it's passive income for you.

@luusssso How ya like our master bedroom tub?

Something about moody red bathroom tile that just does it for me

@TannerBuilds Dumb and ugly

Honest thoughts on a double island?

@AirbnbHelp I did 24hrs ago, but haven't heard back!

@engborg We'd like to have a look at the situation for you. Can you kindly DM us the email address registered on Airbnb? twitter.com/messages/compo…

Hey @Airbnb — you just cancelled our highest-revenue booking of the year with zero notice and zero explanation. No call, no message, nothing. We found out on our own. The guest was a verified Superhost since 2013 with 21 five-star reviews, but you called it a "Security risk." 🧵

cc @bchesky @AirbnbHelp #Airbnb #AirbnbHost #AirbnbSuperhost #ShortTermRental #STR #HostLife

We need: (1) A real explanation, (2) Full payout for the cancelled reservation — this was outside our cancellation window, and (3) A senior case manager, not a script reader. Reservation HM9SWTD4KD. DMs open.

If the guest was actually a risk, why has he been hosting and traveling on your platform for 13 years? And if there's a legitimate reason, why can't you tell us anything? "We can't disclose" isn't a policy — it's a cop-out.

This is a $4,000 booking at a property with hundreds of 5-star reviews. We're professional hosts running a hospitality business. You gave us no opportunity to review, no appeal, no recourse — just a cancelled reservation and a vague excuse.

@Hartdrawss Adding to #20: TypeScript helps, but the bigger win is making AI explain its assumptions before you accept the code.\n\nAlso: #7 and #17 feel like table stakes most vibe coders skip. What's the one you see most often?

20 things that make your VIBE CODED app a SINKING SHIP : 1/ no rate limiting on API routes > anyone can spam your backend into a $500 bill overnight 2/ auth tokens stored in localStorage > one XSS attack = every single user account compromised 3/ no input sanitisation on forms > SQL injection still works in 2026. your AI didnt tell you that. 4/ hardcoded API keys in the frontend > someone WILL find them within 48 hours of launch 5/ stripe webhooks with no signature verification > anyone can fake a successful payment event 6/ no database indexing on queried fields > works fine at 100 users. completely dies at 1,000. 7/ no error boundaries in the UI > one crash = white screen = user never comes back 8/ sessions that never expire > stolen token = permanent access to that account. forever. 9/ no pagination on database queries > one fetch loads your entire database into memory 10/ password reset links that dont expire > old email in someones inbox = instant account takeover 11/ no environment variable validation at startup > app silently breaks in production with zero error message 12/ images uploaded directly to your server > no CDN = 8 second load times + massive hosting bill 13/ no CORS policy > any website on the internet can make requests to your API 14/ emails sent synchronously in request handlers > one slow SMTP server = your entire app hangs 15/ no database connection pooling > first traffic spike = database crashes 16/ admin routes with no role checks > any logged in user can access your admin panel 17/ no health check endpoint > your app goes down silently. you find out from a client. 18/ no logging in production > when something breaks you have zero idea where or why 19/ no backup strategy on your database > one bad migration = all your user data. gone. 20/ no TypeScript on AI generated code > AI writes confident, wrong, untyped code and you ship it anyway

@emmettshine Smart framing. The 'voice in the room' positioning is where health-tech needs to go — make environmental risks actionable through conversation, not another dashboard. Full-gen AI workflows show the new dev model works.

Incredibly interesting video since it highlights the differences for different roles and areas of expertise in tech, and how they view and feel about AI. If this is how engineers feel — I am and feel the complete opposite as a designer. I can now ship for the first time ever, and I’m also having more fun than ever. I don’t know what this means for how roles shift in the near future, but I’m excited.

@varunram Agreed. Haven’t used since they fumbled the the GPT5 launch — useless model.

I still think o3 was the best OAI model out there, really had the "oh wow this is great" feeling that's been hard to find with models after that GPT 5 felt rushed, no feedback on 5.1 and 5.2. Codex models are good but super duper slow. But o3? o3 was perfect, was ahead of everything. Only model I can definitively sense better than o3 is Opus 4.6 Fwiw I think some of it has to do with aggressive benchmark optimization

Denied twice. 3rd submission in review. Let's go!

@elie2222 It takes 2 min to answer "hello" 🤣 But yeah it's the future

HOLY MOLY I just tested Qwen 3.5 9b and it's the future 8GB of RAM. Less than Chrome

Who is “US government” in this aspect? Just the White House? They can do this without congress intervention in any capacity whatsoever? Wild times.

@LandseerEnga ✅

@engborg follow me back so I can DM you!

Agents can one shot mobile apps, but testing is still the bottleneck. So we built a CLI that gives Claude Code the one thing it was missing - eyes and hands The best part? t's fully vision-based: - No scripts, no selectors, no element IDs - It interacts with the app exactly like a human would Claude now writes code → tests it on the app → sees what broke → fixes it Spawn a cloud agent, go to sleep, and wake up knowing it actually worked.