Sabitlenmiş Tweet
brian
4.1K posts
brian
@brian_from_1999
26 / cs @georgiatech / open source contributor
a better future Katılım Aralık 2016
317 Takip Edilen237 Takipçiler
Two Biggest Shortcomings of AI
This week , We are So Back
> Ai can't do maths ( solve erdos problem )
> Ai can't write good story ( won prize in story writing )
Reason by Anti Ai : ai can't feel so they can't write , ai can't think so they can't solve open problem
OpenAI@OpenAI
Today, we share a breakthrough on the planar unit distance problem, a famous open question first posed by Paul Erdős in 1946. For nearly 80 years, mathematicians believed the best possible solutions looked roughly like square grids. An OpenAI model has now disproved that belief, discovering an entirely new family of constructions that performs better. This marks the first time AI has autonomously solved a prominent open problem central to a field of mathematics.
English
English
We are making our discount permanent! 🎉
Enjoy building with DeepSeek-V4-Pro and bring your innovative ideas to life! 🚀
DeepSeek@deepseek_ai
The DeepSeek-V4-Pro discount has been extended until May 31, 2026, 15:59 UTC!
English
I regret to inform the community that all that the source code for Vector has been leaked.
This has been tough on the team, most likely, it's being auctioned on the dark web.
🧵 Whoever purchases it will regret it for the reasons in this thread.
GitHub@github
1/ We are sharing additional details regarding our investigation into unauthorized access to GitHub's internal repositories. Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.
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
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
@spectre0799 @Kurrco Ya I heard that shi right away, was wondering if anyone else noticed it
English
Dear all, apologies if my posts or brand comes across as biased at times. In all honestly, it’s not easy to counter a false narrative without sometimes being a bit extreme or careless with my words.
I am committed to post high quality content and maximizing towards truth. There’s a lot more value I am capable to contribute and I am working hard to showcase that. Thank you for understanding.
If you are able, please support my work by subscribing to my creator page:
x.com/ns123abc/creat…
English
Live now at: traveltsa.com - covering 27 major airports, with 18 publishing live TSA wait times right now, plus checkpoint-hours coverage for more and flight lookup tools to help you time your trip better.
Adding more and more support soon.
Hope you like it!
English
@derekmeegan @sawyerhood yes but it was glm, and its license allows that. While kimi is released with modified MIT, and the modification is that if they used this model they have to display it somewhere. They couldve just named it "Composer 2 (kimi k2.5)" and that would be fine.
English
guys they forked vscode. what did you expect?
fynn@fynnso
was messing with the OpenAI base URL in Cursor and caught this accounts/anysphere/models/kimi-k2p5-rl-0317-s515-fast so composer 2 is just Kimi K2.5 with RL at least rename the model ID
English
@mickeyxfriedman @tekbog I don't know if it's hating as much as it's possibly violating licensing agreements. It's an open source model under a modified MIT License that specifically addresses scenarios like this
A clause exists that explicitly applies to RL setups such as Composer 2
English
@tekbog everyone loves to hate the top startup
picking over everything they do. it’s sad.
English
bad response from cursor, optics tanked, gg
Lee Robinson@leerob
Yep, Composer 2 started from an open-source base! We will do full pretraining in the future. Only ~1/4 of the compute spent on the final model came from the base, the rest is from our training. This is why evals are very different. And yes, we are following the license through our inference partner terms.
English
Since people really want me to say this: "KIMI K2.5" ‼️
Yes, that is the base we started from. And we are following the license through inference partner terms (e.g. Fireworks)
I'm thankful for OSS models personally, good for the ecosystem.
English
Yep, Composer 2 started from an open-source base! We will do full pretraining in the future.
Only ~1/4 of the compute spent on the final model came from the base, the rest is from our training. This is why evals are very different.
And yes, we are following the license through our inference partner terms.
fynn@fynnso
was messing with the OpenAI base URL in Cursor and caught this accounts/anysphere/models/kimi-k2p5-rl-0317-s515-fast so composer 2 is just Kimi K2.5 with RL at least rename the model ID
English
English
We’re growing FAST here @orchard_robots and hiring across our engineering team:
– Robotics Software Engineer 🤖
– Perception & Localization 🗺️
– Machine Learning Engineer 🚜
... as we scale to serve many of America's leading farms, and build the future of farming! 🍎
English
prediction: @thsottiaux is going to be resetting limits again with the influx of users from Claude Code being down
English
Ding. Ooo a text my my gf!!!
Not “how’s your day?”
Not a meme.
Yeah… I think I’ve found the one
English
@thsottiaux curious whether increased /fast usage has broader effects on total compute capacity or mainly impacts the /fast pool itself ?
English
