与「Becauseどっちつかず」相关的搜索结果

#無意識の色# リリースイベントでした✨とっても楽しかった〜💗 #コサンガー7# #Becauseどっちつかず# 披露したよ！この曲とっても好き💗劇場盤のみの収録もったいない😡ダンス頑張ったよ💨衣装も可愛いの☺そう！ちかこ！ネクポジもラブクレも両立頑張ってね〜😙（笑）MCも楽しかったなぁ〜♪

Very welcome recent news from Signal: they are working on letting you register an account without a phone number. That said, an important counterpoint about what this would and would not accomplish. The good #1#: reducing dependence on phone numbers. Even aside from privacy benefits, reducing dependency on a highly oligopolistic system of chokepoints is good in itself. The good #2#: phone numbers are for many people not a good "root" of identity from an access control perspective. Phone numbers get sim swapped all the time. The good #3#: allowing phone-number-free accounts will make it harder for them in the future to discriminate against people by country - and so make it harder for governments to pressure them to block their own citizens. Now, on privacy. Significantly better than status quo, so yes it is good #4#, but... In practice, in 2026, I believe that pseudonymity (a long-term persistent account that is not tied to your primary identity) is a dead concept. There are just too many channels by which we accidentally slowly leak data about who we are - timing of messages, the pattern of who we send messages to with what frequency, size, etc. And too many highly effective AI-based means (both using LLMs per-user, and LLMs helping every person and agency under the sun use math that we had all along) to uncover and piece together those hints. As a trivial example, whatever server you interact with learns your IP address, but even if you hide *that* with a VPN or Tor, there are many other identity leakage vectors. And so the only defensible form of privacy is *message-by-message unlinkability* - no one except sender and receiver knows the (sender, receiver) pair, ideally even not knowing who the sender or the receiver are. A natural taxonomy of privacy is the following 2x2: * Sitting duck: adversary knows "X did Y" * Confidentiality: adversary knows "X did ???" [E2E encryption provides this] * Anonymity: adversary knows "??? did Y" [aka message-by-message unlinkability] * Ideal: adversary knows "??? did ???" Signal has already had confidentiality for a long time. (Note: in other contexts, "confidentiality" sometimes means "someone knows X did Y, and we trust that someone to not reveal it", ie. not true privacy. Here, by confidentiality we mean hiding contents from third parties) This adds pseudonymity: in the above schema, adversary knows "0x8b512c... did Y", where they don't initially know who 0x8b512c... is, but may figure that out over time. The ideal is getting to message-by-message unlinkability. Actually accomplishing that gets into territory that is currently being explored by mixnet projects as well as newer messengers, eg. @session_app and @SimpleXChat. Once we get deeper into this territory, I suspect the primary frontier will be spam and DoS protection. Right now, much of the internet blocks all Tor exit nodes - not because they personally hate privacy, but because that's where DoS attacks come from. So we need ways for people to prove their non-spammer status while maintaining message-by-message unlinkability. See here for one direction (which complements nicely). So I hope that we appreciate the victory that is mainstreaming of end-to-end encryption, that we actually get Signal accounts without phone number dependency (it's a great thing even if it had zero privacy consequences), and then that we keep moving forward and pushing the frontier of data leakage minimization.

The "Web app" standard for the Agentic Web/OS has arrived. It is essentially the open standardization of the third-party app/plugin ecosystem found in ChatGPT. It consists of Skills and MCP, with MCP covering standards such as MCP Apps and MCP-UI, which allow third-party apps to embed GenUI-based interactive interfaces directly into the main Agentic Web/OS interface. WebMCP is about "embedding Tools within UI," while Agent Plugins / MCP Apps are about "optionally embedding UI within Tools." The core of this kind of "app" ecosystem are Tools, rather than any specific UI representation, such as cards, icon + Activity, or windows. AppFunctions / AppIntents / AppActions on Android, iOS, and Windows, like WebMCP, also belong to the "embedding Tools within UI" model. The current CLI ecosystems around Coding Agents such as Codex and Claude Code are effectively local "native app" ecosystems: apps have to be pre-packaged, downloaded, and installed, and users cannot realistically install too many of them. By contrast, Agent Plugins / MCP Apps can be regarded as a kind of "Web app" ecosystem, because their core functionality is retrieved from the Web on demand. Skills, like manifest-style files such as mcp.json, are lightweight distributions of code with declared metadata, somewhat like HTML: they can be discovered, loaded, activated, and used on demand, in a process analogous to HTML rendering but much more intelligent. This creates an opportunity to extend existing Web standards, which are centered around the distribution of UI resources. Instead of RESTful HTTP exposing only a limited set of actions over resources, the Web could expose a vast long tail of Tools that AI can discover and understand, and that can optionally embed UI. A general-purpose Agent capable of discovering, loading, and running Agent Plugins / MCP Apps on demand would be equivalent to "the browser + Google" of the desktop Internet era. If such an Agent becomes a super app, it could easily abstract away the operating system and become the single dominant super app for most user scenarios, much like the desktop Internet era, rather than the mobile Internet era with many parallel super apps. So such an Agent will naturally tend to integrate into the entire OS and even the hardware itself, much like IE vs. Netscape. That is also why Google, OpenAI, and even ByteDance are determined to build consumer electronics hardware products.

Standing in front of the Burj Khalifa again. Goosebumps. Around three years ago I was here talking to a crypto bro based in the UAE. He told me most of his friends use @TrustWallet. I said that was impossible. It lacked this feature, that chain, that polish. He just smiled and said, “That’s what I see people using.” Coming back to the same place, I can only laugh at my own naivety. Trust Wallet is more performant now. The UX is better. We support more chains and features than ever. But that’s not why people stay. They stay because they trust. They trust the brand. They trust self-custody. They trust that the team will do right by them. Features can be copied. Performance can be improved. Trust takes years to build. We’re nine years in. Still early. Still entrusted by millions. What we carry forward isn’t just a product. It’s the trust of the people who chose us. It’s always Day 1. Thank you for your trust.

on the upcoming deepseek price increase we've been able to reproduce their current prices even on rented GPUs so this likely isn't because they're "losing money" it's traffic shaping because they are overloaded

Milton Friedman said we can't have free immigration and a welfare state He was wrong Turns out that if you create pathways for illegal immigrants to vote, then actually, 100% of the time you INEVITABLY end up with both a welfare state and free immigration Because incentives determine actions Whichever politicians realize they can essentially use taxpayer dollars to fund welfare to import voters will exploit this hack ruthlessly 1. Offer welfare 2. Allow illegal immigration 3. Let illegal immigrants vote (they will 100% of the time vote for more welfare) 4. Win office 5. Raise taxes, offer more welfare, repeat It's a self-reinforcing feedback loop Allowing illegal immigrants to count in the census and vote cements this loop Literally only 12 states require proof of citizenship to register to vote. Look it up. It's horrifying. That is why 15m illegal immigrants came across the border in 4 yrs. It is game theory the only smart thing to do This ends in disaster

Tomorrow will be my last day at Google after 27 years, and watching it grow from 25 people to 190,000+ has been an amazing journey. Below is a note I shared with many people internally at Google today. An excerpt is: It has been an absolute pleasure to work with you and to help build some of the most widely used and impactful products of all time. As a kid, I dreamed of helping build software that would be used by many people, and Google now has thirteen products used by more than a billion people (amazing!). Our work has had a tremendous impact in the world, and I have been lucky enough to collaborate and form friendships with many colleagues that I deeply admire, respect, and enjoy. It still brings me joy every time I see people out in the world using our products to find information, handle email, translate documents, watch videos, learn new things, navigate and understand the physical world, browse the web, use their phone, run large-scale computations on our infrastructure, ride in an autonomous vehicle, or perform complex tasks with the help of our AI systems. I hope you all share this sense of joy, because it is a shared accomplishment! Thank you to all of my colleagues at Google over many years! Now I'm excited to go start @DiscoLoopAI with my longtime friends and colleagues @Sanjay_Ghemawat, @OriolVinyalsML, and @quocleix. (Updated post: slightly redacted to not have some personal info)

Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deeply leveraging AI. This is more or less the culmination of my secret 10-year master plan. This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug. We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night. How is that possible? It's the Sandstorm security model, revisited. A "Gadget" is the same thing as a Sandstorm "Grain": a fine-grained app instance. For example, if you have a document editor app, each document runs as a separate instance of the app, in a separate sandbox (one "Gadget"). This means two things, both of which I think are Big Deals: 1. The platform can manage all access control, by controlling who can access the Gadget at all. There is no way the Gadget can accidentally leak itself to an attacker -- even an attacker who has access to other Gadgets based on the same app. 2. Since everyone is running their own copy of the code, everyone can freely *modify* their copy of the code. Think about #2# a bit more. What if, when you wanted a new feature in the software you are using, you could just prompt your agent to add it? This doesn't work in the cloud Software-as-a-Service model, because you are not running your own copy of the app. Sandstorm tried to change that 10 years ago, but the world wasn't ready, because not enough people had the skills or patience to actually modify their software. AI has changed that. Now you just ask the agent -- the same agent that you are using to help you interact with the Gadget can also modify the code of the Gadget. And it is so fun.

Hot take… isn’t it kinda crazy that nobody is really using AI Agents? I don’t mean software engineers or AI early adopters. I mean “college friends talking about it in group chat,” the feeling you got when everyone started using Instagram or TikTok. These frontier AI models are *insane* (as are the harnesses & tool calls & the like). And every large tech co has an AI agents platform, not to mention all the YC startups doing vertical agents. Yet all of your friends and family outside of tech — who spend all day staring at their iPhones and get paid to work in browser tabs — don’t really care or find themselves using any AI agents yet. Yes ChatGPT, Claude, etc. are extremely popular… but if you look at the engagement data the vast majority of people are still using these aI chat tools like a glorified Google + Grammarly. That’s why the AGI labs are all pushing desktop apps for Codex, Cowork, etc. so hard to non-technical ppl. And yes exceptions for lawyers and customer service but even those have some asterisks and exceptions to rule. Look I’m not saying the ChatGPT moment for AI Agents is not coming… it most definitely is! Remember we pivoted from Arc to Dia precisely because we believe computing is going to be radically reimagined around these AI primitives. No doubt. But that’s my point: it’s just so surprising it hasn’t happened yet because all of the tech you’d need is there. Again if you stop for a second and think about it… for all the press and money and hype and models and crazy ARR numbers… this “AI Agent” moment does not *feel* like the other breakthrough tech moments we’ve lived through (e.g. think the shift to Stories via Snapchat & Instagram, or shift to on-demand via Uber/Airbnb/Doordash). Which is a long way of saying: if you can figure out the answer to “why” most people don’t care about AI agents yet (and have no enduring interest in using them) — especially since the models and harnesses are here and ready — the answer to that question will allow you to capture a lot of marketshare and make a lot of money in 2027. Theoretically, the tech is ready for AI Agents to totally transform how we work and live our lives… but alas the general public dgaf… that’s the generational puzzle to solve for the next 12 months for anyone not working on the models themselves.