19, building video, ex @Lovable @ensdomains
stockholm, sf
Joined April 2021
- Tweets7.1K
- Following665
- Followers8.2K
- Likes11.1K
Elliot Lindberg retweeted
there are a lot of founders who wants to come to Japan like @robiot
he speaks Japanese
Japanese First Residency - AG1.
10 weeks in Tokyo for free with founders from across the world.
005: w/ Asu Capital Partners (@HideoNw, @lukeli_asu)
Elliot Lindberg retweeted
Hot take: You should learn the basics of video editing...
AI is about to get really good at Davinci, Premiere, After Effects, and more.
If you have no experience in the timeline, that will be equivalent to vibe coding with no coding experience. The timeline is the codebase.
And... with AI, you can learn these platforms so quickly. When you get stuck just ask AI what to do.
And you only need to know the basics.
I'd start here w/ davinci or premiere
- How the timeline works
- Sequences and nested sequences
- How audio tracks and mixing works
- How keyframes and animations work
- How to cut, trim, and pace your videos
- How to color grade videos
- How to layer B-roll, text, and graphics
- How effects, transitions, and masks work
- How to frame, crop, and guide the viewer’s attention
Elliot Lindberg retweeted
Today, we’re releasing screen-aware one-click writing to everyone.
The natural next step after voice dictation.
Press Option in any text field. Goldfish predicts what you want to write from the real context of your work.
Already used 250,000+ times.
Free for a little longer: goldfish.sh
Elliot Lindberg retweeted
welcoming Lovable bros (@robiot & @isaaksundeman) to Singapore with some durian
Elliot Lindberg retweeted
Last week our AI opened a store in SF, this week AI is opening a cafe in Sweden.
Meet Mona, our AI tasked with selling coffee and managing European bureaucracy.
Visit Andon Cafe at Norrbackagatan 48 in Stockholm.
Elliot Lindberg retweeted
We’re sorry our initial statement didn't properly address our mistake. Here's what a public project on Lovable means, and how we got to where we are today:
In the early days, people didn't know what Lovable was capable of. So we wanted to make it easy to explore what others were building, as a way to spark ideas and lower the barrier to getting started. Like scrolling GitHub or Dribbble: you browse projects to see what's possible, then go build your own.
When you create a project on GitHub, you can make it private or public. Lovable worked the same. Users had a "Public" or "Private" option right in the chatbox. A public project meant the entire project was public, both chat and code. “Just like a public project on GitHub," we thought.
Over time, we realized this was confusing. Many users thought "public" just meant others could see their published app, not the chat of an unpublished project. That's reasonable.
On the free tier, users originally couldn't create private projects. They had to upgrade to a paid plan to do so. In May 2025, we changed this: users on the free tier could choose to make their projects private. For enterprise customers, the public visibility setting was disabled altogether. And in December 2025, we switched to private by default across all tiers.
We also retroactively patched our API so public project chats couldn't be accessed, no matter what. Unfortunately, in February, while unifying permissions in our backend, we accidentally re-enabled access to chats on public projects.
This was reported through our vulnerability disclosure program (via HackerOne). Unfortunately, the reports were closed without escalation because our HackerOne partners thought that seeing public projects’ chats was the intended behaviour.
Upon learning this, we immediately reverted the change to make all public projects’ chats private again. We appreciate the researchers who uncovered this.
We understand that pointing to documentation issues alone was not enough here. We’ll do better.
We were made aware of concerns regarding the visibility of chat messages and code on Lovable projects with public visibility settings.
To be clear: We did not suffer a data breach.
Our documentation of what “public” implies was unclear, and that’s a failure on us.
Specifically for public projects, chat messages used to be visible — this is now no longer possible.
When it comes to code of public projects: That is intentional behavior. We have experimented with different UX for how the build history is surfaced on public projects, but the core behavior has been consistent and by design.
Importantly, for enterprise customers, being able to set visibility to public for new projects has been disabled since May 25, 2025.
Readers added context they thought people might want to know
Lovable admitted in a follow-up that access to chat messages on public projects was accidentally re-enabled in February 2026 during backend changes and fixed after vulnerability reports were dismissed as intended. x.com/Lovable/status… docs.lovable.dev/features/proje…
Elliot Lindberg retweeted
in shenzhen most business people respond to you within 3 minutes on a sunday. even if you have no prior connection. it’s surreal
Elliot Lindberg retweeted
All I can say is go star our GitHub repo :D
Delve knows no shame.
They allegedly sold another YC company’s (@simdotai) open source tool as a standalone product to companies like Notion and Brex without attribution, violating the Apache license, and then lied about it to the founders of Sim.
The founders of Sim (@emkara) are left with nothing while Delve walks away with the money.
Elliot Lindberg retweeted
5 days left to Takeoff Tokyo 2026.
Why are we doing this?
Our passion and vision is in one video.