@ryancarson Everything is now a race towards better design and real moats.
English
RCK
58 posts
RCK
@version_7_0
CTO / AI Product Strategy / Building software that helps us live and work in harmony 🧘🏽♂️📈 #ai #focus #harmony
New York, NY Katılım Mayıs 2025
37 Takip Edilen6 Takipçiler
Just shipped a major new feature.
Had the idea on Monday, shipped it today.
4.5 days from idea to prod.
This easily would've been at least two 2-week sprints at my last startup - with a whole team (pm, designer, 2 devs).
Still wild to experience it.
English
@version_7_0 All C++: bgfx, GLM, open dynamics engine, miniaudio, steam-audio so far. When I get the AI subsystem up and running I might try to use a small LLM to manage the AI state, but that's probably really hard to get working well in real time
English
Wild to see some of my favourite games of all time, Dishonored, Prey, and Thief, all getting so much spontaneous love on here when I've been building a hackable, modernized version of the Dark Engine for Thief as a vibe coding challenge these past few months
MakutaArty1987@ArtemYakov19657
Dishonored is rightfully getting a lot of praise, and Prey is getting it by proxy of also being made by Arkane. Can Thief get some glaze too by being the primary inspiration for Dishonored? And also by being good
English
@IamJoshJackson @pitnikola I see a lot of folks referencing “slack connect” as the reason people will not switch. Can’t one simply create a Slack integration so that “legacy” slack teams can seamlessly talk to the company on the new platform?
English
@pitnikola Yep - the amount of money, hiring and growth needed is more than people realise.
Then you realise no one will move because slack connect.
English
I've seen 4-5 startups trying to build a Slack competitor in the last 5 years, and all of them gave up. It will take a massive effort to move any large business off Slack, and Slack isn't even winning the market. Teams is winning.
Ben Lang@benln
Imagine Slack, but built from scratch in 2026
English
@charles_maddock I think we have to rewrite project collaborations suites from scratch. Nothing has fundamentally changed in this space for over 20 years, yet the rest of the world is completely different.
English
Linear:
We need to move beyond the generic chat format
Also Linear:
English
@Lovable Honest mistake. Thanks for the transparency. You are providing great value to non-technical folks and are helping them achieve things they never knew possible. Do get a fully dedicated, super paranoid senior info-tech person onboard. Don't outsource security.
English
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.
Lovable@Lovable
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.
English
@DanielBlancoSWE Técnicamente los credenciales fueron expuestos porque se mencionaron en el chat. No se sabe si fue error de usuario o falla de diseño del sistema. Aún así, hacer público la conversación con el bot + el código en el modo "Public" no fue muy buena/clara.
Español
Se vienen meses / años interesantes en el panorama tecnológico.
Aquí os dejo un tweet que lo explica más a fondo si os interesa el tema
x.com/weezerOSINT/st…
impulsive@weezerOSINT
Lovable has a mass data breach affecting every project created before november 2025. I made a lovable account today and was able to access another users source code, database credentials, AI chat histories, and customer data are all readable by any free account. nvidia, microsoft, uber, and spotify employees all have accounts. the bug was reported 48 days ago. its not fixed. They marked it as duplicate and left it open.
Español
Se ve que los proyectos públicos en Lovable exponen los chats, el código e incluso credentials a internet.
Y lo peor de todo es que esta era la opción por defecto al crear un proyecto hasta Noviembre de 2025.
Lovable@Lovable
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.
Español
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.
English
@IsakPar021 @weezerOSINT I suspect all Delve customers are a crazy target right now.
English
@weezerOSINT This is bad, very bad BUT at least they are SOC II compliant thanks Delve….
English
Lovable has a mass data breach affecting every project created before november 2025.
I made a lovable account today and was able to access another users source code, database credentials, AI chat histories, and customer data are all readable by any free account.
nvidia, microsoft, uber, and spotify employees all have accounts. the bug was reported 48 days ago. its not fixed. They marked it as duplicate and left it open.
English
El caballero tiene una molestia válida pero está reaccionando mal. Aún así, él tiene mucho más derecho de vivir en una comunidad limpia que el perro recibir comida de extraños. La organización debe respetar las comunidades donde operan. Busquen una finca con fondos del municipio y trasladen los perros operados ahí. No hay ningún vecino que aplauda perros/gatos salvajes en la calle. Están haciendo mas mal neto que bien si operan sin aprobación de la comunidad.
Español
𝐌𝐚𝐥𝐭𝐫𝐚𝐭𝐨 𝐚𝐧𝐢𝐦𝐚𝐥 𝐝𝐞𝐧𝐮𝐧𝐜𝐢𝐚𝐝𝐨 𝐞𝐧 𝐏𝐨𝐧𝐜𝐞: 𝐨𝐫𝐠𝐚𝐧𝐢𝐳𝐚𝐜𝐢𝐨́𝐧 𝐬𝐞𝐧̃𝐚𝐥𝐚 𝐚𝐜𝐭𝐨𝐬 𝐜𝐨𝐧𝐭𝐫𝐚 𝐩𝐞𝐫𝐫𝐨𝐬 𝐫𝐞𝐚𝐥𝐞𝐧𝐠𝐨𝐬
Ponce, 17 de abril de 2026- La organización Huellitas de la Montaña denunció públicamente un presunto caso de maltrato animal ocurrido en áreas de Ponce, donde, según alegan, un individuo lanzó dispositivos pirotécnicos de bajo impacto —conocidos como “snappers” o “pop-its”— directamente hacia perros realengos, provocándoles miedo, estrés y riesgo de daño.
De acuerdo con la denuncia, el incidente se produjo en un área donde voluntarias de la organización realizan labores de alimentación y programas de captura, esterilización y retorno (TNR, por sus siglas en inglés). Además, señalaron que el individuo presuntamente arrolló con su vehículo la comida destinada a los animales, afectando directamente a perros que dependen de esta ayuda para sobrevivir en la calle.
La entidad recalcó que este tipo de acciones no solo impacta a los animales, considerados vulnerables, sino que también interfiere con esfuerzos comunitarios organizados para el control poblacional y el bienestar animal en la ciudad. Según indicaron, estas prácticas buscan reducir el abandono y evitar la proliferación descontrolada de camadas en las comunidades.
Huellitas de la Montaña sostuvo que los hechos descritos podrían constituir violaciones a la Ley 154 de Puerto Rico sobre maltrato de animales. Asimismo, denunciaron que al intentar radicar una querella ante la Policía de Puerto Rico el mismo día de los hechos, esta no fue recibida, situación que, según expresaron, contraviene los protocolos establecidos que garantizan el derecho de cualquier ciudadano a reportar este tipo de incidentes.
La organización hizo un llamado a que estos casos no sean minimizados ni ignorados, destacando la importancia de la intervención ciudadana y de las autoridades para atender la problemática del maltrato animal. Reiteraron que continuarán alzando la voz en defensa de los animales, quienes no pueden expresarse por sí mismos, e insistieron en la necesidad de acción, responsabilidad y consecuencias ante este tipo de conducta.
Español
@StartupMary @antonosika @Lovable Big Lovable fan here. Could you share what your experience has been with other tools? Why didn't you build with Claude Code?
English
@antonosika I lauched on @Lovable and it's been a wonderful experience.
English
We officially opened Lovable’s first US office in Boston.
Boston felt like the right place for us to open an office because Massachusetts has a practical view of AI. It’s about using AI to solve real problems rather than just building the technology, which is something Gov. Maura Healey has spoken about clearly.
That’s why we started Lovable, to help more people turn ideas into software, products, companies, and real economic value.
PS, check out Gov. Healey rocking our Lovable socks.
English
@byronrode @kirstycarrot @anothercohen I don't know much about Discord. My team vibe coded an internal tool to replace Slack+Notion+Project Management and so far its working out well.
English
I'm tempted to finally churn off Slack.
We're paying ~$6k/year for 40 people and they just quoted me $21k/year for the business version that includes a BAA (and all the shitty AI features).
Incredibly overrated software
English
@kirstycarrot @anothercohen Hey Kirsty, what features did Discord lack that made you switch back?
English
@anothercohen The problem is there isn’t much else that does the same thing - we tried discord and telegram but ended up back in slack 🙈
English
Announcing Amazon S3 Files.
The first and only cloud object store with fully-featured, high-performance file system access.
Learn more here. go.aws/4tw17Zg
English
But I'm sure my vibe coded thing will fail, so please advise me of any good agentic customer support software :D
English
the state of b2b saas in 2026: it's faster to vibe code your own tool than to onboard onto one that already exists
today i tried to set up a customer support saas for my startup — we're at the point where we need to reply to 100+ of client messages a day. the onboarding was so insufferable (3 hours of manual integration or hop on a demo call) that it was easier to just vibe code the whole thing than actually use their product
English