Gabriele De Rosa

2.9K posts

Gabriele De Rosa banner
Gabriele De Rosa

Gabriele De Rosa

@derogab

focused builder @ https://t.co/0KsUfxswg3

Earth Katılım Mayıs 2011
1.6K Takip Edilen656 Takipçiler
OpenCode
OpenCode@opencode·
DeepSeek V4 Pro and Flash now available in Go We rushed to get this released, still working out the capacity and usage limits Thanks to the @deepseek_ai team for the PRs and fixes
English
98
110
2.5K
225.1K
Polymarket
Polymarket@Polymarket·
JUST IN: OpenAI is reportedly developing a smartphone designed to "make apps obsolete" by replacing them with AI agents.
English
578
495
4.8K
861.4K
Lovable
Lovable@Lovable·
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
153
87
989
380.7K
Vjekoslav Krajačić
Vjekoslav Krajačić@vkrajacic·
So prompt engineers learned English is imprecise for coding and started using stricter syntax. I wonder how long it will take before they come full circle and land back at programming languages again.
Sukh Sroay@sukh_saroy

Prompt engineering is dead. Nobody is writing english to chatbots anymore. The best outputs are coming from people who write prompts like code. It's called json prompting. and once you see it, you can't go back:

English
181
1.6K
18.8K
800.6K
Gabriele De Rosa
Gabriele De Rosa@derogab·
@Polymarket No issue: the average Lovable user had already exposed all their credentials themselves months ago.
English
1
0
2
1K
Polymarket
Polymarket@Polymarket·
BREAKING: Vibe-coding platform Lovable reportedly suffered a breach that exposed users’ AI chat histories, source code, & database credentials.
English
577
920
8.4K
2M
Tyler
Tyler@rezoundous·
Opus 4.7 is insane guys. It one shotted my session usage limit.
English
603
1.3K
31.5K
1.1M
Gabriele De Rosa
Gabriele De Rosa@derogab·
Everyone is 18+ in the EU 🇪🇺
Paul Moore - Security Consultant @Paul_Reviews

Bypassing #EU #AgeVerification using their own infrastructure. I've ported the Android app logic to a Chrome extension - stripping out the pesky step of handing over biometric data which they can leak... and pass verification instantly. Step 1: Install the extension Step 2: Register an identity (just once) Step 3: Continue using the web as normal The extension detects the QR code, generates a cryptographically identical payload and tells the verifier I'm over 18, which it "fully trusts". This isn't a bug... it's a fundamental design flaw they can't solve without irrevocably tying a key to you personally; which then allows tracking/monitoring. Of course, I could skip the enrolment process entirely and hard-code the credentials into the extension... and the verifier would never know.

English
0
0
0
51
Remarks
Remarks@remarks·
JUST IN: 🇺🇸 President Trump posts image portraying himself as Jesus Christ.
Remarks tweet media
English
6.5K
3.9K
21.5K
18M
Gabriele De Rosa retweetledi
calle
calle@callebtc·
UPDATE: EU CHAT CONTROL WAS REJECTED. AGAIN. UNTIL THEY TRY AGAIN NEXT WEEK.
calle tweet media
English
129
1.4K
19.5K
1.4M
Gabriele De Rosa retweetledi
antirez
antirez@antirez·
Please write to your MEPs to oppose untargeted mass scanning of private communications (Chat Control). On March 11 Parliament voted 458-103 to limit scanning. Today they vote again (!!!) and those protections could be watered down. Act now: fightchatcontrol.eu
English
4
19
128
6.4K
Gabriele De Rosa retweetledi
@levelsio
@levelsio@levelsio·
And after voting that out too... 🇪🇺 ChatControl is back with a vengeance The Conservatives (EPP) are attempting to force a new vote TODAY (March 26) seeking to reverse the European Parliament's NO on indiscriminate scanning of ALL your private messages, emails and photos This is a direct attack on democracy and blatant disregard for your right to privacy If you're European contact your representatives now, with this handy form: #contact-tool" target="_blank" rel="nofollow noopener">fightchatcontrol.eu/?foo=bar#conta… If not, please share this tweet so more people see it and we can block the vote It's crazy they keep just bringing back whatever they want until it's passed! Obviously now we see the European Commission is controlled by powerful evil lobbying groups 👺
@levelsio tweet media
@levelsio@levelsio

Just a month later and... 🇪🇺 ChatControl is back! Now they're trying to pass an even more far reaching ChatControl law through the back door, in a form even more intrusive than the originally rejected plan, without needing any of the EU countries votes The new proposal: - total mandatory surveillance of ALL text chats, emails and social media in the EU - obligatory registration of your ID/passport to your chat, email or social media account - minimum age requirement for chat, email and social media apps of 16 (!) The only way to stop this law is if EU countries veto it Read more here by @echo_pbreyer: patrick-breyer.de/en/chat-contro…

English
163
1.3K
4.9K
490.5K
Gabriele De Rosa retweetledi