标签：#Meta

Pocket is listed in app stores but seemingly unavailable in the US.

Mozilla shut down the well-loved read-it-later Pocket app last year, and now Meta is launching an app called Pocket with an entirely different, AI-focused pitch: this new app lets you make and share little interactive "gizmos" built from an AI prompt, as reported by Business Insider. Meta CEO Mark Zuckerberg is all in on AI […]

Meta has quietly launched Pocket, an experimental AI app that lets users generate and share interactive mini games using text prompts.

Doctors find grey fluid and dead, metallic flesh inside poisoned woman's hip.

Fake Mr Beast "promotions" are ubiquitous on Threads - they're also part of massive crypto scam network.

You bought the hardware. Now you’ll need to subscribe for “expanded access” to the most advanced features.

Meta says usernames improve privacy, but critics question whether its safeguards can prevent impersonation.

Selling server infrastructure would put Meta in competition with Amazon and Google.

Meta is developing plans for a cloud infrastructure business, selling access to AI compute power and models. The move would pit it against the big cloud providers like Amazon Web Services, Google Cloud, and Microsoft Azure.

Would you pay $20 a month for access to AI hardware you already own? That appears to be one of Meta's next bets. This week, it quietly announced that your glasses' Conversation Focus feature will soon be limited to three hours of use per month, unless you pay for a $19.99 Meta One Premium subscription. […]

The app's arrival follows an announcement at last year's Meta Connect conference.

The updates include translations, new tools for hosts, and more.

Hundreds of contractors working on a project for Meta pretended to be kids—and then prompted rival chatbots like Gemini and ChatGPT to discuss high-risk subjects.

Even if you only use WhatsApp sometimes, you might want to snag your username now to stop giving out your phone number.

WhatsApp username can be between 3 to 35 characters.

WhatsApp username can be between 3 to 40 characters length

WhatsApp is introducing a new way to add and chat with contacts, without having to share your phone number. Usernames will be launching "later this year," in a move to make the communications platform "even more private," allowing you to keep your phone number concealed from people who aren't already in your contacts. Usernames are […]

Instagram users could soon see more ways to tune their content.

Three bugs this month. All three looked fixed before they broke. The date was quoted in 51 out of 52 posts. The model was pinned to a specific version. The upload feature had been working in production for weeks. Each one passed the obvious checks and failed somewhere else. That's the theme for this Friday Fixes: the fix that wasn't. Not bugs that went unnoticed, but bugs where a defense existed and the failure found its way around it. 1. The Unquoted Date, Part Two If this one sounds familiar, it should. I wrote an entire Friday Fixes post about this exact bug class five weeks ago. An unquoted YAML date. gray-matter parsing it as a Date object instead of a string. A crash downstream. Last time it took down /admin/drafts . The fix hardened formatDate() to coerce Date objects before calling .includes() . I verified it. I shipped it. I wrote 2,000 words about it. I moved on. This time it took down the homepage. The symptom: vibescoder.dev loaded for a split second, then flashed to Chrome's "This page couldn't load" screen. Every browser, every profile, every device. The site was completely dead to visitors. The twist: curl returned HTTP 200 with ~900KB of fully rendered HTML. The server was fine. The crash was happening during React hydration in the browser, invisible to any server-side test. The cause: A new post had date: 2026-06-19 in its frontmatter. No quotes. gray-matter parsed it as a Date object. In posts.ts , the code does const meta = data as PostMeta and then spreads ...meta into the return value. The as PostMeta cast told TypeScript the date was a string . At runtime, it was a Date . That Date object flowed through the server component, through the RSC serialization boundary, and into PostListWithFilters , a "use client" component. React couldn't hydrate it. No global-error.tsx existed to catch the crash. Dead page. Why the May fix didn't prevent this: Because the May fix was in the wrong layer. It hardened formatDate() , the function that happened to cras

Meta is, by and large, a company built on other companies' ideas. It has almost perfected the strategy: wait for a new platform or social mechanic to take off, then either buy or clone it, put it next to Meta's unmatched user base and advertising engine, and watch the money pile up. Well, the next […]