The next set of hardware purchases will cost more than their last set of hardware purchases, and that's going to outweigh any labour economies of scale given just how many hardware components are in shortage this year.
If their growth had been in their projections in say 2024, they might have just been able to skip a round of hardware purchases, but the combination of growth meaning they must expand their hardware and hardware costs made this inevitable.
Google made the first move with their initial plan to lock it down, so the onus is on Google to calm the fears they caused if they don't want people to distrust them.
But they did. That was the announcement that they would still allow sideloading. If you are still afraid then that's kind of on you. Seems silly to expect Google to put out info about enabling sideloading for a system they haven't even released yet. It could very well be in there day 1. Nobody knows.
It's deliberately written to be vague and not say anything, and given the original intention, it's hard to believe that means it should be interpreted generously.
I'm not sure non-technical people have a good understanding of or experience with password less email login either. While doing tech support I've seen people get very confused at the need to open another app to login in or the fact that they're now logged in in the webview of their email app and not logged in in the app or browser they had been using (especially if the first thing that web view does is pop up a giant "try the app" modal)
Thanks for your insight. Outside of being a consumer, and as a security engineer one who appreciates things like passwordless, my experience comes from my employers passwordless rollout. The sentiment is broadly positive, but we would veer to a technical user base, and sentiment misses the nuance you brought up.
Isn’t it microtransactions? Which kind of hints at the difference, since it’s all the ceremony of a two party transaction, while micropayments proposals usually have some focus on being automatic or frictionless
> Agentic workflows are a VERY small percentage of all LLM usage at the moment. As that market becomes more important, Google will pour more resources into it.
I do wonder what percentage of revenue they are. I expect it's very outsized relative to usage (e.g. approximately nobody who is receiving them is paying for those summaries at the top of search results)
> Most agent actions on our public API are low-risk and reversible. Software engineering accounted for nearly 50% of agentic activity, but we saw emerging usage in healthcare, finance, and cybersecurity.
this doesn’t answer your question, but maybe Google is comfortable with driving traffic and dependency through their platform until they can do something like this
They have a ML model based on shrug emoji that decides if you’re in the automatically approved bucket, the face verification bucket or the ID verification bucket. If face verification fails or you’re in the high risk bucket you’ll need to send them ID to access adult content, i.e. any channels manually set to nsfw, anything their classifier deems nsfw and anything in servers deemed nsfw. Discord would like to imply that most users are in the automatically verified bucket and only like porn is flagged nsfw, but it’s entirely in their control to tighten these screws when they reckon that the controversy is over (and they’ve already been trialling more mandatory ID verification on UK users, before starting the global rollout)
You could still run the sofa customers list against a list of known offenders but is there a federal list? Maybe the number of states where the sofa was sold was to large and getting the full list not feasible?
If their growth had been in their projections in say 2024, they might have just been able to skip a round of hardware purchases, but the combination of growth meaning they must expand their hardware and hardware costs made this inevitable.
reply