Excited to be speaking at SGLang summit!
I'll share how we use SGLang for production serving at Meta, tackling tough correctness and performance challenges at massive scale to serve billions of users across Muse and the Meta family of apps.
Come join me and an amazing lineup of speakers at
https://t.co/At1E1SIdS7 @sgl_project
@JnBigio@__drewface Nowadays I mash the keyboard until I get something slightly legible and the agents still know what to do.
These things are truly amazing.
Prop G to reopen the great highway to cars has to be some of the dumbest legislation.
We voted on this twice already, the great highway is a great park now that people use every day. Why do we have to pander to people who want to use their private vehicles on it.
muse case for today, I want to buy new sheets so I had muse research which sheets to buy, and then render all of the color combos I'm interested in to give me a sense of which each looks like.
@johnmyleswhite I feel like the barrier to entry for some pieces of tech, particularly the ones that live in our own are so accessible that itβs difficult to treat it like something like video games.
The slot machine is always available and itβs engineered to engage.
We're excited to bring 1Password directly into @Muse for the many people who already use it. It gives you another secure way to let Muse sign in and keep working: you approve each login and your passwords stay in your vault. Rolling out across all platforms over the coming days.
An update on @Muse shared artifacts.
Earlier this week, a security researcher published details of a design flaw in @Muse shared artifacts: some shared artifact URLs were discoverable via passive DNS. We disabled sharing immediately to prevent any unintended exposure, which is why shared artifacts were temporarily unavailable. Some articles we have seen in the press mentioned a flaw in chat sharing, and that is not the case - this issue was specifically about shared artifacts.
The underlying issue is now fixed, and sharing is back on.
If you shared an artifact before the fix: it now has a new URL. Anyone visiting the old link will see a note asking them to get the new one from you. We know that's a pain, and we're sorry for the disruption β but protecting user data has to come first.
We're grateful to the researchers who find and report issues like this. The Muse bug bounty program exists so these reports can reach us directly and responsibly, with awards of up to $300,000 for valid findings. Every report is reviewed. If you find something, please send it our way.
Alexandr Wang (@alexandr_wang) says he has more than 200 direct reports at Meta's superintelligence lab, and that it is by design:
"Yeah, I think more than 200."
"One of the design principles around this was making it very flat. Effectively, all the research that we hired into this group called TBD, they report directly to me."
"TBD is like literally anti-bureaucracy."
"So I don't need to be micromanaging you to do brilliant work. You're gonna be able to do that on your own."
"We have this kind of like pod structure where we have various pods and there's various technical leads of the pods who tie break on the technical decisions."
"From a quote unquote people management perspective or from a bureaucracy perspective, we're just anti-bureaucracy."
"I would be lying if I said I was the best manager to more than 200 people."
"They don't need managers. They need a great environment."
"They just need the room to cook."
- Alexandr Wang, Meta Chief AI Officer, in an interview with David Senra published October 11.
Meta used to sell "Portal," it was their own version of Apple's "HomeView" product. It wasn't just one product. They had a lineup of four products with similar functionality to Apple's HomeView. They also had great integration with Meta's products, such as Facebook and WhatsApp, and even supported YouTube and Zoom.
I had one, and it was quite useful at the time.
It failed.
Now tell me, why would Apple's HomeView do any better?