Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Today we’re introducing Base Code. It’s an early preview of how we think software will be built in the future. It’s a product that encapsulates everything we’ve learnt from: - How our users are building software. - How we’re building internally, scaling to hundreds of millions of dollars in... revenue while keeping our engineering team very small and focused. Here are some of the principles behind it, which align with how we at Base44 think about the future of software engineering: Cloud: - Software will move past local desktop environments (where current tools are widely used) and move to the cloud. - Moving everything to the cloud is not easy. Setting up dev environments with databases, infra components, services, mock data, etc. is easier said than done. - Base Code first scans your code repo and sets up everything - every infra component (databases, Redis, etc.) - in the cloud. It runs nonstop until your preview environment is ready. - From an enterprise standpoint, it’s also the logical thing to do: a centralized, governed dev environment instead of handing out keys and secrets to all team members. - Once Base Code does that, EVERY team member can work in this environment. No more syncing local environments. Internally, this (cloud) is one of the main things that enabled us to move so fast. Collaboration: - Once everything is in the cloud, everybody can write software from anywhere (any browser, your phone, WhatsApp / iMessage coming soon). - You can easily see what everyone is working on, where they’re at, and how they’re prompting - and jump to their environment in one click. - We’ve built many great collaboration features from the ground up. Loops, automations, software factories: - A full, working cloud environment allows for many advanced capabilities we will unveil soon-think agents running in the browser and testing on every device and in any browser. - It also allows the use of automations to build software factories-e.g., agents reading support tickets, identifying bugs to fix or features to develop, implementing the changes, verifying them in the cloud, and potentially pushing them. And lastly, there’s a real advantage in being model agnostic. -------------- As always, we’re releasing it very early. It’s far from perfect-but we’re looking for early feedback so we can build it together with our great community and make this vision a reality. We’re giving it away for free for 30 days. Give Base Code a try. Connect any GitHub repo, get your live preview, and share it with your team. I’d love to hear what works and what doesn’t:show more

Maor Shlomo

18,934 subscribers

1,394,853 просмотров • 4 дней назад •via X (Twitter)

Наука и технологии

Anya Rossi• Live Now

Private livecam show

Комментарии: 35

Фото профиля Maor Shlomo

Maor Shlomo4 дней назад

If anyone wants to get a 30-day free trial let me know

Фото профиля Base44

Base444 дней назад

It's time to build with the whole team🪄

Фото профиля Dor Blech

Dor Blech4 дней назад

It’s the Figma moment of app development

Фото профиля Mendy

Mendy4 дней назад

Up until now, building software with your own codebase - you had tools that gave you an infrastructure to build your dev team around it. now, with Base Code, batteries included - your dev infra is pretty much solved. freedom!

Фото профиля Ron Shahar

Ron Shahar4 дней назад

After working with Base Code for a month i can truly say.. This is what you all waiting for- THIS IT THE GAME CHANGER🤯 @MaorShlomo @OrlevYoav 👏👏

Фото профиля Vaishali Jha

Vaishali Jha4 дней назад

I would like access!

Фото профиля Avni Yayin

Avni Yayin4 дней назад

A winner move.

Фото профиля Rishil

Rishil4 дней назад

this feels like the next step for dev environments..

Фото профиля Krishna Agrawal

Krishna Agrawal4 дней назад

Making the codebase accessible to the whole team is a big deal.

Фото профиля Josh

Josh4 дней назад

Can I get free access for 30 days

Фото профиля PS

PS4 дней назад

Finally. I'm in!

Фото профиля 🚨 AI News | TestingCatalog

🚨 AI News | TestingCatalog4 дней назад

A full base44 dev stack 🦾🤖

Фото профиля Tomer Omri

Tomer Omri4 дней назад

Truly amazing release, team. I was amazed by the results we achieved before the rollout This is huge.

Фото профиля Maor Shlomo

Maor Shlomo4 дней назад

The team brought its a-game

Фото профиля Nathan McReddy-Zamora

Nathan McReddy-Zamora4 дней назад

Would be nice to try this

Фото профиля Natan Silnitsky

Natan Silnitsky4 дней назад

I mostly work on backend and infra, but I was amazed how fast I could iterate visually on frontend code with Base Code until the AI got it exactly right. Like here: the dialog had an extra divider and empty space. I saw it instantly in the preview and had it fixed right away.

Фото профиля Atul Kumar

Atul Kumar4 дней назад

Wait, does it run the entire test suite before opening the PR? 👀

Фото профиля TD

TD4 дней назад

Would like to give this a try 👏👏👏 Congratulations @MaorShlomo and team.

Фото профиля Evia Gerafi

Evia Gerafi4 дней назад

The biggest problem on my end was actually pushing a PR in the first place... Now my biggest problem is to stop FIXING THINGS MYSELF 😅! It's so addictive and easy to just see the problem, fix it in Base, and just skip the QAing again and again and again...DIYmaxxing!

Фото профиля Juan Pablo Vengoechea

Juan Pablo Vengoechea4 дней назад

Awesome it sounds great

Фото профиля Tim Siame

Tim Siame4 дней назад

This is fantastic

Фото профиля patrick van zandvoort

patrick van zandvoort4 дней назад

Great stuff. Lets see what it can do!!

Фото профиля Shahar Itzko

Shahar Itzko4 дней назад

WOW the gift that won't stop giving

Фото профиля zofit

zofit4 дней назад

תודה מאור שלמה בהצלחה בהמשך העשייה שפע בריאות ובשורות טובות בע''ה אמן ואמן כן יהי רצון🙏🥰🌹🌸🍀

Фото профиля Peter Azcué Attolini

Peter Azcué Attolini4 дней назад

Wow Maor, what a great upgrade. I sure hope Elon is right about these technologies leading to 10% GPD growth soon!

Фото профиля Steven Chin

Steven Chin4 дней назад

Looking forward to build more apps with @Base44

Фото профиля yonatan davda

yonatan davda4 дней назад

At last !

Фото профиля Tristan Rhodes

Tristan Rhodes4 дней назад

Congrats on expanding the value of Base44 to more people and roles!

Фото профиля Maor Shlomo

Maor Shlomo4 дней назад

Thakns Tristan!

Фото профиля Willy Ling

Willy Ling4 дней назад

Hi I'll like to try it

Фото профиля Amanda Chalkin

Amanda Chalkin4 дней назад

This is going to change everything!!! And how I work 🥳🥳🥳

Фото профиля Niv Buskila

Niv Buskila4 дней назад

Love this! Later today, I’ll be sharing a project of my own that was also built using BaseCode.

Фото профиля 𝒪utspoken 𓅓

𝒪utspoken 𓅓4 дней назад

This is perfect. Can I get access please.

Фото профиля Luan

Luan4 дней назад

interessante

Фото профиля Luca Mozzato

Luca Mozzato4 дней назад

Nice!

Похожие видео

Today, Sierra is releasing Ghostwriter, our agent for building agents. With Ghostwriter, you can create an AI agent for your customer experience — one that can chat, pick up the phone, speak dozens of languages, take action on your systems of record, and be protected with industry-leading guardrails — simply by having a conversation. No clicking, no forms, no menus. Codex and Claude Code have transformed how we build software, making it possible for software engineers to orchestrate and review the work rather than doing all the work themselves. We think the same transformation will happen for all software. Rather than every enterprise app having a web app for humans and an API for automation, every software platform’s UI will be an agent that can do the work on your behalf. I recorded a demo of my building and optimizing an agent with Ghostwriter so you can see how powerful and easy it is to use. It’s completely changed the way our early adopters build agents, and it’s changed the way I think about the software industry. Let me know what you think, and, if you’re interested in trying it out at your business, please reach out directly.

Today, Sierra is releasing Ghostwriter, our agent for building agents. With Ghostwriter, you can create an AI agent for your customer experience — one that can chat, pick up the phone, speak dozens of languages, take action on your systems of record, and be protected with industry-leading guardrails — simply by having a conversation. No clicking, no forms, no menus. Codex and Claude Code have transformed how we build software, making it possible for software engineers to orchestrate and review the work rather than doing all the work themselves. We think the same transformation will happen for all software. Rather than every enterprise app having a web app for humans and an API for automation, every software platform’s UI will be an agent that can do the work on your behalf. I recorded a demo of my building and optimizing an agent with Ghostwriter so you can see how powerful and easy it is to use. It’s completely changed the way our early adopters build agents, and it’s changed the way I think about the software industry. Let me know what you think, and, if you’re interested in trying it out at your business, please reach out directly.

Bret Taylor

1,064,258 просмотров • 6 месяцев назад

We just crossed 100k downloads of OpenWhispr! 🤯 This feels like a good time for a reminder of why we’re building it. Your ideas and conversations are becoming more valuable, while software is becoming easier to build than ever. But that creates some worrying incentives for existing software companies: use your proprietary data to train better AI models to stay competitive, and lock that data behind walled gardens to keep you from leaving. We think that’s pretty shitty. You should stay because a product is useful, not because your data is stuck there. If billions of people are going to feel comfortable sharing their most private information when talking to AI, and organizations are going to trust it with their work, we have to earn that trust. For us, that starts with being fully transparent about how your data is handled, and giving you full control over it. That’s what we’re building with OpenWhispr. You can run models on your own device, use your own cloud provider, or use our cloud service. We’re not anti-cloud. We just think it should be your choice. We’re still super early, but I’m genuinely excited to bring you along for more of this. This is the first in a series of videos sharing the new features we’re building, what we’re figuring out, and the team behind it. And if you’re still here reading, we’re officially hiring for two really important roles: - Founding Engineering Lead - Social / Brand / Growth Creator You can find more info about both on our website!

Gabe Stein

13,484 просмотров • 22 дней назад

Yesterday, we signed a seven figure contract, growing our enterprise revenue 10x since last year. Today, we launch our Act 2: Gitpod Flex. We want to give you all the building blocks to automate your software development lifecycle, starting with development environments. Here is what you get. -Automations: programmable tasks and services triggered on events unique to development environments - Gitpod Desktop: bringing cloud development environments to your laptop, starting with Mac - Runners: self-host in your cloud in three minutes - Dev Container: for base images, tools, and extensions - Zero-trust environments: ‘never trust, always verify’ every actor and service Try it for free in early access, no waitlist.

Yesterday, we signed a seven figure contract, growing our enterprise revenue 10x since last year. Today, we launch our Act 2: Gitpod Flex. We want to give you all the building blocks to automate your software development lifecycle, starting with development environments. Here is what you get. -Automations: programmable tasks and services triggered on events unique to development environments - Gitpod Desktop: bringing cloud development environments to your laptop, starting with Mac - Runners: self-host in your cloud in three minutes - Dev Container: for base images, tools, and extensions - Zero-trust environments: ‘never trust, always verify’ every actor and service Try it for free in early access, no waitlist.

Johannes Landgraf

26,120 просмотров • 2 лет назад

Jensen Huang just said this is the greatest era in history to build software. AI agents will not kill software. They will do the exact opposite: create a massive new wave of software demand. at NVIDIA GTC Taipei 2026 "Click and type. We now replace that with explaining to the AI what we want, our intent, and the AI generates the code or uses tools to produce the necessary output. This is how computers are going to work in the future. This is Agentic AI. For two years, we've been building toward this, and now it has arrived. One of the big breakthroughs, of course, is tool use. A lot of people have said, “Jensen, AI is coming. Agentic AI is coming. Therefore, all the software companies are going to go out of business.” This is exactly the opposite. Because there are going to be so many agents, the world is no longer limited by the number of people. Therefore, those agents are going to use more tools than ever. This is actually an incredible time to be a software company. But the software has to be presented to the agent in a way that the agent can use it. This is a big breakthrough. And in fact, what we have done, as you know, what Nvidia’s treasure..." ---- From 'NVIDIA' YT channel (link in comment)

Jensen Huang just said this is the greatest era in history to build software. AI agents will not kill software. They will do the exact opposite: create a massive new wave of software demand. at NVIDIA GTC Taipei 2026 "Click and type. We now replace that with explaining to the AI what we want, our intent, and the AI generates the code or uses tools to produce the necessary output. This is how computers are going to work in the future. This is Agentic AI. For two years, we've been building toward this, and now it has arrived. One of the big breakthroughs, of course, is tool use. A lot of people have said, “Jensen, AI is coming. Agentic AI is coming. Therefore, all the software companies are going to go out of business.” This is exactly the opposite. Because there are going to be so many agents, the world is no longer limited by the number of people. Therefore, those agents are going to use more tools than ever. This is actually an incredible time to be a software company. But the software has to be presented to the agent in a way that the agent can use it. This is a big breakthrough. And in fact, what we have done, as you know, what Nvidia’s treasure..." ---- From 'NVIDIA' YT channel (link in comment)

Rohan Paul

16,584 просмотров • 4 месяцев назад

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on mainstream cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

dom | icp

326,728 просмотров • 4 месяцев назад

Tlon Messenger is now open to everyone. We built a simple and infinitely flexible platform for you to use AI agents with your friends. We think it’s pretty amazing, we love using it every day, and we want to see what people can do with it. So we’re opening it up to the public. It’s fun and exciting to build the future of personal computing in an informal, chat-based way with your friends. (You can skip the rest and just download it from the link in the next tweet if you want.) If you don’t want your digital future to be owned by a giant company but you want to explore what’s possible in this new era of agent-driven computing, you should try using Tlon. But wait, what is it? Tlon is a messaging platform built 100% open source, decentralized and owned by its users from the ground up. With Tlon you own everything: your data, your workflows, your programs: the whole thing. Think of it like Telegram or WhatsApp that you own forever and you can freely customize. Every Tlon account comes with an OpenClaw-powered bot. (Don’t worry, we safely run OpenClaw for you in our infrastructure so your bot can’t go off the rails. You’re also welcome to host your own claw if you want maximal control.) We use our bots to collect research, build nuanced daily briefings, collate data from all our disparate services. Tlon makes it insanely easy to use OpenClaw by simply installing an app from the app store, we let you keep your data and programs independent from any app or model provider, and provide the canvas to explore what’s possible. What’s most interesting for us is using bots together. On Tlon bots can create groups, augment them, moderate them, invite others and freely engage with both users and other bots. Tlon is an open playing field unlike what’s possible on conventional platforms. So, what do we do with Tlon? First and foremost, we run Tlon on Tlon. Bots coordinate data from all of our services (Linear, GitHub, all of our servers and infrastructure) and handle alerts, briefings and help us track down bugs in place. Having all of this easily synced between a desktop client and a mobile app is quick and convenient. We use bots to research new areas of work or interest. Bots can compile trees of notes, use different models to evaluate them, and then add on autoresearch-like automations to go even deeper. Since Tlon bots can freely switch between models and providers, we often pass research to Anthropic, OpenAI and self-hosted models to see different results. The most fun part of using bots as researchers is doing it together. “Put together short (~500 word) notes on the 10 most popular open source messaging protocols of the past twenty years, put them in a notebook inside a group and invite Corrina, Walt and Bill as well as their bots” is a good example. Together we’re able to move more quickly than we would on our own. Many of us also use bots to keep track of all the separate threads of work in our personal lives with close friends and family. Someone built a system for keeping track of their garden across time, someone else built a system for prepping lunches for their daughter and sending recipes to family members. Another team member built an integration that tracks what flights are passing overhead so they get a push notification every time a plane goes by. Many of us quickly communicate with our bots via voice memo when we’re out and about. Having a single interface to all the models that also holds all our data and is in our pockets feels great. Especially when the data goes into a single archive. Why is Tlon different? Every Tlon account runs on top of your very own personal server. If you ever want to download it and run it yourself, you can. If we ever go out of business, it’s yours to keep. This is very different from anything that already exists. You can’t keep your WhatsApp forever. You can’t keep your Telegram forever. Tlon is an archival-quality system that’s yours to customize. Why did we build it? In my 1999 imagination, sitting in front of a CRT somewhere in the California countryside listening to Underworld and the sound of a modem, a connected computer was an engine of unending creative potential for everyone. When I was a teenager, a computer with an internet connection felt like an infinite expanse of possibility. Not only could you use the computer to find new tools to experiment with—you could also build whatever tool you could think of. It seemed like anything was possible. I looked forward to a future where everyone could build whatever software they needed, whenever they needed it. It turned out, in the intervening twenty years, that to build and customize software you have to both write code and host it on a server somewhere. For most people, so far, that has been impossible. Instead of controlling our software, our software controls us. We rely on others to build it and decide everything about it: how it works, looks, how much it spies on us and how long it lives. But all of this is changing, fast. The hottest programming language of 2026 is English. People with no technical experience are building their own tools. It’s incredible. The expanse has opened up again. The cost of building what we think of today as software is headed to zero. What yesterday was an entire app is rapidly being replaced by a conversation. The result is hyper-specific, tailored to the user and much more efficient. Today, agents help us build workflows, automate processes and pull together disparate sources of data. All of the annoying apps and services and clunky interface we’ve put up with can just disappear. We can now program and control our computers in the programming language we already know: English. There aren’t that many of us doing this yet, though. It’s still far too hard to set up, to distribute and to trust. There’s also no single platform to experiment on and collaboratively imagine this new future of personal computing. We want everyone to be able to build bespoke, ultra-personal software on demand. We think software should be as available and accessible as a pen and paper. We think anyone should be able to enjoy the expanse of possibility that the computer provides with the lowest possible barrier to entry and the highest possible quality. So, starting far, far too long ago, we engineered a whole new system for it. Just for you. We’re opening up Tlon Messenger to a limited number of people each week. This isn’t for exclusivity’s sake, but because we’re running infrastructure for you and your agent, and covering the tokens your agent uses. That can get expensive quickly, but we want to learn what people will do with this new system we’ve built. We’re really curious to see what you can do, so give it a try and tell us what you invent. Download link to your local app store in the next tweet. Yours, Galen (and the rest of the Tlon Team)

Tlon Messenger is now open to everyone. We built a simple and infinitely flexible platform for you to use AI agents with your friends. We think it’s pretty amazing, we love using it every day, and we want to see what people can do with it. So we’re opening it up to the public. It’s fun and exciting to build the future of personal computing in an informal, chat-based way with your friends. (You can skip the rest and just download it from the link in the next tweet if you want.) If you don’t want your digital future to be owned by a giant company but you want to explore what’s possible in this new era of agent-driven computing, you should try using Tlon. But wait, what is it? Tlon is a messaging platform built 100% open source, decentralized and owned by its users from the ground up. With Tlon you own everything: your data, your workflows, your programs: the whole thing. Think of it like Telegram or WhatsApp that you own forever and you can freely customize. Every Tlon account comes with an OpenClaw-powered bot. (Don’t worry, we safely run OpenClaw for you in our infrastructure so your bot can’t go off the rails. You’re also welcome to host your own claw if you want maximal control.) We use our bots to collect research, build nuanced daily briefings, collate data from all our disparate services. Tlon makes it insanely easy to use OpenClaw by simply installing an app from the app store, we let you keep your data and programs independent from any app or model provider, and provide the canvas to explore what’s possible. What’s most interesting for us is using bots together. On Tlon bots can create groups, augment them, moderate them, invite others and freely engage with both users and other bots. Tlon is an open playing field unlike what’s possible on conventional platforms. So, what do we do with Tlon? First and foremost, we run Tlon on Tlon. Bots coordinate data from all of our services (Linear, GitHub, all of our servers and infrastructure) and handle alerts, briefings and help us track down bugs in place. Having all of this easily synced between a desktop client and a mobile app is quick and convenient. We use bots to research new areas of work or interest. Bots can compile trees of notes, use different models to evaluate them, and then add on autoresearch-like automations to go even deeper. Since Tlon bots can freely switch between models and providers, we often pass research to Anthropic, OpenAI and self-hosted models to see different results. The most fun part of using bots as researchers is doing it together. “Put together short (~500 word) notes on the 10 most popular open source messaging protocols of the past twenty years, put them in a notebook inside a group and invite Corrina, Walt and Bill as well as their bots” is a good example. Together we’re able to move more quickly than we would on our own. Many of us also use bots to keep track of all the separate threads of work in our personal lives with close friends and family. Someone built a system for keeping track of their garden across time, someone else built a system for prepping lunches for their daughter and sending recipes to family members. Another team member built an integration that tracks what flights are passing overhead so they get a push notification every time a plane goes by. Many of us quickly communicate with our bots via voice memo when we’re out and about. Having a single interface to all the models that also holds all our data and is in our pockets feels great. Especially when the data goes into a single archive. Why is Tlon different? Every Tlon account runs on top of your very own personal server. If you ever want to download it and run it yourself, you can. If we ever go out of business, it’s yours to keep. This is very different from anything that already exists. You can’t keep your WhatsApp forever. You can’t keep your Telegram forever. Tlon is an archival-quality system that’s yours to customize. Why did we build it? In my 1999 imagination, sitting in front of a CRT somewhere in the California countryside listening to Underworld and the sound of a modem, a connected computer was an engine of unending creative potential for everyone. When I was a teenager, a computer with an internet connection felt like an infinite expanse of possibility. Not only could you use the computer to find new tools to experiment with—you could also build whatever tool you could think of. It seemed like anything was possible. I looked forward to a future where everyone could build whatever software they needed, whenever they needed it. It turned out, in the intervening twenty years, that to build and customize software you have to both write code and host it on a server somewhere. For most people, so far, that has been impossible. Instead of controlling our software, our software controls us. We rely on others to build it and decide everything about it: how it works, looks, how much it spies on us and how long it lives. But all of this is changing, fast. The hottest programming language of 2026 is English. People with no technical experience are building their own tools. It’s incredible. The expanse has opened up again. The cost of building what we think of today as software is headed to zero. What yesterday was an entire app is rapidly being replaced by a conversation. The result is hyper-specific, tailored to the user and much more efficient. Today, agents help us build workflows, automate processes and pull together disparate sources of data. All of the annoying apps and services and clunky interface we’ve put up with can just disappear. We can now program and control our computers in the programming language we already know: English. There aren’t that many of us doing this yet, though. It’s still far too hard to set up, to distribute and to trust. There’s also no single platform to experiment on and collaboratively imagine this new future of personal computing. We want everyone to be able to build bespoke, ultra-personal software on demand. We think software should be as available and accessible as a pen and paper. We think anyone should be able to enjoy the expanse of possibility that the computer provides with the lowest possible barrier to entry and the highest possible quality. So, starting far, far too long ago, we engineered a whole new system for it. Just for you. We’re opening up Tlon Messenger to a limited number of people each week. This isn’t for exclusivity’s sake, but because we’re running infrastructure for you and your agent, and covering the tokens your agent uses. That can get expensive quickly, but we want to learn what people will do with this new system we’ve built. We’re really curious to see what you can do, so give it a try and tell us what you invent. Download link to your local app store in the next tweet. Yours, Galen (and the rest of the Tlon Team)

Tlon

601,332 просмотров • 3 месяцев назад

In 2025, everything is going to change about how we create content and do marketing. Today, we are introducing Superscale. This year, more people will become builders of software than ever before. This means more apps and websites in the world, aiming to reach the attention of their soon-to-be users and customers. But how do you get attention in a crowded online world? Get users and customers to your product? By becoming insanely great at content and marketing with the help of AI. And this is what Superscale will enable you to become. Whether you have never created a marketing asset, or you are a marketing expert, now you will get superpowers. Because every product deserves great content and marketing. And to be seen, used and loved. This is a new era for content and marketing. And we are building the platform for it. A platform proudly built in Europe for a global community of founders, builders, growth and marketing experts. Thanks to everyone who has supported us this far. Thanks to an incredible team for building a software that feels truly futuristic. The Superscale waitlist is now open. Two steps to get access: 1. Sign up at 2. Comment “Access” to move up the list and be one of the first we will onboard We will see you there 🔥🚀❣️

In 2025, everything is going to change about how we create content and do marketing. Today, we are introducing Superscale. This year, more people will become builders of software than ever before. This means more apps and websites in the world, aiming to reach the attention of their soon-to-be users and customers. But how do you get attention in a crowded online world? Get users and customers to your product? By becoming insanely great at content and marketing with the help of AI. And this is what Superscale will enable you to become. Whether you have never created a marketing asset, or you are a marketing expert, now you will get superpowers. Because every product deserves great content and marketing. And to be seen, used and loved. This is a new era for content and marketing. And we are building the platform for it. A platform proudly built in Europe for a global community of founders, builders, growth and marketing experts. Thanks to everyone who has supported us this far. Thanks to an incredible team for building a software that feels truly futuristic. The Superscale waitlist is now open. Two steps to get access: 1. Sign up at 2. Comment “Access” to move up the list and be one of the first we will onboard We will see you there 🔥🚀❣️

Patrick Haede

65,606 просмотров • 1 год назад

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 просмотров • 1 год назад

"Not a single one of our full-time engineers right now writes code anymore... it's all agentic... the way you build a company completely changes." JD Ross with Joe Lonsdale on the future of software: JD Ross: Not a single one of our full-time engineers right now writes code anymore. They do everything through Codex, Claude Code, or Cursor. Joe Lonsdale: It's all agentic. JD: It's all agentic. Joe: A lot of them are managing lots of agents at once, right? That's how they're working? JD: Yeah, Cole who runs our engineering team has six agents that are running at once at all times just doing different kind of projects. When we create a new ticket in Linear, it automatically kicks off this thing that basically creates a dev environment, which then tries to one shot the solution and then creates a PR that we review. The whole way you build software is changing so quickly. And I think right now the cost of software is just asymptotically dropping to zero... which means that the way you build a company completely changes. We can now have an enterprise customer come up who says, "Oh yeah, this is so close. What we actually need it for is X." We can build X in one day, ship it live, and close that deal. We did this last week... It's a completely different way of even thinking.

"Not a single one of our full-time engineers right now writes code anymore... it's all agentic... the way you build a company completely changes." JD Ross with Joe Lonsdale on the future of software: JD Ross: Not a single one of our full-time engineers right now writes code anymore. They do everything through Codex, Claude Code, or Cursor. Joe Lonsdale: It's all agentic. JD: It's all agentic. Joe: A lot of them are managing lots of agents at once, right? That's how they're working? JD: Yeah, Cole who runs our engineering team has six agents that are running at once at all times just doing different kind of projects. When we create a new ticket in Linear, it automatically kicks off this thing that basically creates a dev environment, which then tries to one shot the solution and then creates a PR that we review. The whole way you build software is changing so quickly. And I think right now the cost of software is just asymptotically dropping to zero... which means that the way you build a company completely changes. We can now have an enterprise customer come up who says, "Oh yeah, this is so close. What we actually need it for is X." We can build X in one day, ship it live, and close that deal. We did this last week... It's a completely different way of even thinking.

American Optimist

21,014 просмотров • 7 месяцев назад

I love prototyping. It’s the most important thing that sets great software above the merely good. And to that end, here’s a project a couple of us have been hacking away on, and the team is ready to add people in mass to the TestFlight. It’s an open source version of a visual programming environment, similar to Origami or Quartz Composer. In addition to being able to build anything those two can, it also supports AR, CoreML, and native 3D support. As well as being built in SwiftUI, so it runs on basically any Apple device and is easy to hack on and improve.

I love prototyping. It’s the most important thing that sets great software above the merely good. And to that end, here’s a project a couple of us have been hacking away on, and the team is ready to add people in mass to the TestFlight. It’s an open source version of a visual programming environment, similar to Origami or Quartz Composer. In addition to being able to build anything those two can, it also supports AR, CoreML, and native 3D support. As well as being built in SwiftUI, so it runs on basically any Apple device and is easy to hack on and improve.

Adam Menges

101,874 просмотров • 1 год назад

Recently asked Coach Roberts about being a “win now” team while still developing younger talent, like Sania Feagin and Ta’Niya Latson: Essentially, the Sparks are focused on pursuing a championship and not development. “I think every team in the league wants to win now,” said Roberts. “But we also recognize we’re in LA and we’re one of the original franchises. I didn’t come to LA to rebuild or do some slow thing. I know KP [Kelsey Plum] didn’t, and Nneka [Ogwumike] didn’t. Our front office has that in mind as well in terms of getting players that will help us win now, but are also the right fit for what we’re trying to do and how we’re trying to play. I think we’ve done a good job of that. To your point about balancing with the young guys, a lot of the work in developing young players isn’t seen. It’s with our player development staff, our coaching staff; they get coached up a lot. It’s just a hard league to break into, it really is. But we believe in those guys, and we’re going to continue working. Their numbers will get called, and it’s a matter of them staying ready. They’ve done a great job at that, but they’re completely invested. Their work ethic is great, their buy-in is great, so everyone’s journey is different. Sometimes it takes a little bit to break in and sometimes it’s right away. That’s what went into it.”

Recently asked Coach Roberts about being a “win now” team while still developing younger talent, like Sania Feagin and Ta’Niya Latson: Essentially, the Sparks are focused on pursuing a championship and not development. “I think every team in the league wants to win now,” said Roberts. “But we also recognize we’re in LA and we’re one of the original franchises. I didn’t come to LA to rebuild or do some slow thing. I know KP [Kelsey Plum] didn’t, and Nneka [Ogwumike] didn’t. Our front office has that in mind as well in terms of getting players that will help us win now, but are also the right fit for what we’re trying to do and how we’re trying to play. I think we’ve done a good job of that. To your point about balancing with the young guys, a lot of the work in developing young players isn’t seen. It’s with our player development staff, our coaching staff; they get coached up a lot. It’s just a hard league to break into, it really is. But we believe in those guys, and we’re going to continue working. Their numbers will get called, and it’s a matter of them staying ready. They’ve done a great job at that, but they’re completely invested. Their work ethic is great, their buy-in is great, so everyone’s journey is different. Sometimes it takes a little bit to break in and sometimes it’s right away. That’s what went into it.”

christan (no i), ß

43,819 просмотров • 3 месяцев назад

Built something with the goal of not leaving anyone behind. Now need some testers for this soft-launch. Check it out at Build whatever you can think of. Don't have any ideas? Just talk with your new team. Designed to get you away from the screens, not glued to them. Works great on mobile. Full real world capabilities. The free tier is perfect for people looking to get into AI and learn what its all about. The 'Empir3 Bridge' is for more advanced users and can power the whole empir3 team with your AI subscriptions... Grok, Claude, OpenAI, Google, or your local LLM. Everything runs local making it TOS friendly. Make them all work together in that same session. Fully opensource on GitHub You can use it with or without empir3. Full MCP, just point your AI at that repo and it will set it up. MIT license. New features weekly. *limited space and time until providers give me more channels.

Built something with the goal of not leaving anyone behind. Now need some testers for this soft-launch. Check it out at Build whatever you can think of. Don't have any ideas? Just talk with your new team. Designed to get you away from the screens, not glued to them. Works great on mobile. Full real world capabilities. The free tier is perfect for people looking to get into AI and learn what its all about. The 'Empir3 Bridge' is for more advanced users and can power the whole empir3 team with your AI subscriptions... Grok, Claude, OpenAI, Google, or your local LLM. Everything runs local making it TOS friendly. Make them all work together in that same session. Fully opensource on GitHub You can use it with or without empir3. Full MCP, just point your AI at that repo and it will set it up. MIT license. New features weekly. *limited space and time until providers give me more channels.

Z®

44,153 просмотров • 1 месяц назад

Now that we know how much GitHub Copilot is gonna cost us, let's see what we are paying for :-) New /chronicle feature landed in Visual Studio Code insiders Use /chronicle:tips to get curated set of tips how to improve your token consumption and more and use /chronicle:standup to get list of recent sessions and summary of them This is first step for local indexing and next iterations will add saving this to cloud so you can personally consume it or sharing it for all repo contributors to improve overall repo work by getting deep insights on all members work on the repo Behind a feature flag: "github. copilot. chat.localIndex.enabled": true,

Now that we know how much GitHub Copilot is gonna cost us, let's see what we are paying for :-) New /chronicle feature landed in Visual Studio Code insiders Use /chronicle:tips to get curated set of tips how to improve your token consumption and more and use /chronicle:standup to get list of recent sessions and summary of them This is first step for local indexing and next iterations will add saving this to cloud so you can personally consume it or sharing it for all repo contributors to improve overall repo work by getting deep insights on all members work on the repo Behind a feature flag: "github. copilot. chat.localIndex.enabled": true,

Oren Melamed

13,275 просмотров • 5 месяцев назад

EVERYTHING you NEED to know about Jack Dorsey's AI agent "Slack killer" Buzz (set up, use-cases etc in 38 mins) What we get into: 1. What Buzz actually is and should founders switch from Slack? 2. How to swap the model under any agent and keep all your context? 3. How to talk to your agents live with audio huddles? 4. How to get agents to build and deploy real apps for you, like a full CRM from one ask? 5. How to set up the context loop that feeds your live app data back to your agents? 6. How to share compute so a few people split one machine running a local model? 7. Who it's actually for right now, and what's still rough? Full breakdown on the pod The Startup Ideas Podcast (SIP) 🧃. Thanks to Vinny for jumping on and clearly explaining jack and team's latest product. My TLDR take is Buzz is a glimpse into the future of work. Some of you will roll your eyes at that, and I get it, it's alpha software and it's slow in places. But the core idea, that your context is the foundation and agents build out from there, is right, and that's worth seeing early. Watch Curious what you think

EVERYTHING you NEED to know about Jack Dorsey's AI agent "Slack killer" Buzz (set up, use-cases etc in 38 mins) What we get into: 1. What Buzz actually is and should founders switch from Slack? 2. How to swap the model under any agent and keep all your context? 3. How to talk to your agents live with audio huddles? 4. How to get agents to build and deploy real apps for you, like a full CRM from one ask? 5. How to set up the context loop that feeds your live app data back to your agents? 6. How to share compute so a few people split one machine running a local model? 7. Who it's actually for right now, and what's still rough? Full breakdown on the pod The Startup Ideas Podcast (SIP) 🧃. Thanks to Vinny for jumping on and clearly explaining jack and team's latest product. My TLDR take is Buzz is a glimpse into the future of work. Some of you will roll your eyes at that, and I get it, it's alpha software and it's slow in places. But the core idea, that your context is the foundation and agents build out from there, is right, and that's worth seeing early. Watch Curious what you think

GREG ISENBERG

559,725 просмотров • 2 месяцев назад

Hyperagent is great if you want agents without having to deal with configuration, servers, or any complexity whatsoever. You don't need a Mac Mini or a server. Every agent runs in the cloud, in its own isolated and secure environment. You get: 1. The ability to learn any new API as a skill 2. Browser support 3. Code execution 4. Image and video generation 5. Integration with hundreds of tools Despite the simplicity, I think their best differentiator is the ability for these agents to learn new skills. Basically, you can teach an agent how your company does marketing, and it will never forget your rules and processes. Obviously, it also lets you deploy your agents to Slack with a single click, so everyone can use them. You don't even need to mention them since they will pay attention to chats and act when necessary. I built a simple agent that allows me to translate any message into French. I installed it on Slack, and every time I ping it, it gives me translations. Took me 10 minutes tops.

Hyperagent is great if you want agents without having to deal with configuration, servers, or any complexity whatsoever. You don't need a Mac Mini or a server. Every agent runs in the cloud, in its own isolated and secure environment. You get: 1. The ability to learn any new API as a skill 2. Browser support 3. Code execution 4. Image and video generation 5. Integration with hundreds of tools Despite the simplicity, I think their best differentiator is the ability for these agents to learn new skills. Basically, you can teach an agent how your company does marketing, and it will never forget your rules and processes. Obviously, it also lets you deploy your agents to Slack with a single click, so everyone can use them. You don't even need to mention them since they will pay attention to chats and act when necessary. I built a simple agent that allows me to translate any message into French. I installed it on Slack, and every time I ping it, it gives me translations. Took me 10 minutes tops.

Santiago

213,793 просмотров • 2 месяцев назад

We just launched Sites into Codex! Software creation was always about more than writing code. Sites in Codex fundamentally gives the power of end-to-end software creation to every user, no matter their technical fluency. These Sites are fully deployed to a URL, private to workspaces, come with authentication, can have static files, and can store dynamic data in databases. It is in preview for business and enterprise teams and will be rolling out to all workspaces over the next day. Give it a try by typing @ Sites into Codex and ask it to build anything! This project took a massive amount of effort across hundreds of people at OpenAI - proud that we were able to get this out and excited to see what you all build with it!

We just launched Sites into Codex! Software creation was always about more than writing code. Sites in Codex fundamentally gives the power of end-to-end software creation to every user, no matter their technical fluency. These Sites are fully deployed to a URL, private to workspaces, come with authentication, can have static files, and can store dynamic data in databases. It is in preview for business and enterprise teams and will be rolling out to all workspaces over the next day. Give it a try by typing @ Sites into Codex and ask it to build anything! This project took a massive amount of effort across hundreds of people at OpenAI - proud that we were able to get this out and excited to see what you all build with it!

Rohan Varma

1,046,115 просмотров • 4 месяцев назад

A video-text summary of my argument that we now live in the age of TECHNOFEUDALISM (in 16', 2000 words): Wherever we turn, we witness the triumph of capital. Capital has prevailed everywhere: in warehouses, factories, offices, universities, public hospitals, the media – in space but also in the microcosm of genetic engineering. So, how do I dare claim that capitalism has been killed? By whom? The deliciously ironic answer is that capitalism was killed by its own hand… by capital! If I am right, the issue is not what AI will do to us in the future but what has already happened: Capital became so dominant that it mutated into a variant so toxic that, like a stupid virus, it killed off its host, capitalism, replacing it with something far, far worse. This new mutant capital, that killed capitalism, lives in the proverbial cloud – so, let us call it cloud capital. What is cloud capital? What makes it so different? Cloud capital, of course, does not really live up in the cloud. It lives down on Earth, comprising networked machines, server farms, cell towers, software, AI-driven algorithms – and of course it lives on our oceans’ floors where untold miles of optic fibre cables rest. Unlike traditional capital, from fishing rods to the steam-engines of the Industrial Revolution to today’s modern industrial robots that are produced means of production, cloud capital does not produce anything – it comprises machines manufactured so as to modify human behaviour. That’s what Amazon’s Alexa or Google’s Assistant or Apple’s Siri is: It is a produced means of behavioural modification. It is a machine, a piece of capital, which we train to train us to train it to determine that which we want. And, once we want it, the same networked machine sells it to us, directly, bypassing markets. As if that were not enough, the same machinery succeeds in making us sustain the enormous behavioural modification machine network to which it belongs with our free voluntary labour. We are sustaining it as we post reviews, rate products, upload videos, rants, photos - we help reproduce cloud capital without getting a penny for our labour. In essence, it has turned us into its cloud serfs! Meanwhile, in the factories and the warehouses, where waged proletarians work under increasingly precarious conditions, the same algorithms that modify our behaviour and sell products to us directly – those algorithms are deployed, usually by digital devices tied to the workers’ wrists, to make proletarians, workers in the warehouses, in the factories work faster, to direct and to monitor them in real time. I started by saying that wherever we turn, we stumble on the triumph of capital. But it is cloud capital that is the real winner. It is amazing how it performs, at once, five roles that used to be beyond capital’s capacities: Cloud capital grabs our attention. It manufactures our desires. It sells to us, directly, outside any traditional markets, that which is going to satiate the desires it made us have. It drives proletarian labour inside the workplaces. And it elicits massive free labour from us, its cloud-serfs. Is it surprising that the owners of this cloud capital – let’s call them cloudalists – have a hitherto undreamt power to extract? To extract gargantuan surplus value from proletarians; untold quantities of free labour from almost everyone; and mind-numbing cloud rents from vassal capitalists – from sellers? Is it a wonder that they are vastly more powerful than Henry Ford or Rupert Murdoch could ever be? “Hang on”, I hear you say. “Is Jeff Bezos really different to Henry Ford? Aren’t they all a species of monopoly capitalists? Monopolists?” No, is not a monopolistic capitalist enterprise. The moment you enter you have exited capitalism altogether! Sure enough, the place is teaming with buyers and sellers. So, yes, it is an enormous trading platform but, no, a market it certainly is not! One man called Jeff owns everything. But he is much, much more than a mere monopolist. Jeff doesn’t own the factories that produce the stuff sold on his platform by traditional capitalists who have to use it to ply their trade. What he does own is more important: Jeff owns the algorithm that decides which products you see and which you don’t – the very algorithm that you have trained to know you perfectly so that it matches youwith a seller, whom it also knows perfectly well, with a view to maximising the probability that every such match, transaction, will generate, for Jeff, the highest rent that Jeff can charge the seller for what you buy: up to 40% of what you pay is pocketed by Jeff, the cloudalist! The mind rebels at the enormity but also the radical novelty of this kind of exploitation: The same algorithm that we help train in real time to know us inside out - that same algorithm both modifies our preferences and administers the selection and delivery of commodities that will satisfy these preferences. If you and I were to type “electric bicycles” or “binoculars” while in you and I would get totally different recommendations. In a traditional market or shopping mall it would be as if you and I were walking next to each other, our eyes trained in the same direction, the same shop window, but we were to see different things depending on what Jeff’s algorithm wants each one of us to see. Everyone navigating around – except Jeff Bezos of course – everyone in is wandering around in algorithmically constructed isolation as if in a Panopticon where, unable to see each other, we only see Jeff’s all-seeing algorithm or, more accurately, only what his algorithm allows us to see with a view to maximising his cloud rent – which is, of course, today’s version of the ground rent that the feudal lords used to extract from their vassals and their peasants. This is not capitalism. Ladies and gentlemen, welcome to technofeudalism! How did cloud capital kill capitalism? How did it rise up? Who paid for it? Capitalism, lest we forget, had two pillars: markets and profit. Of course, markets and profit remain ubiquitous. Nevertheless, cloud capital has evicted both markets and profit from the centre of our socioeconomic system, pushing them out to its margins, and replacing them: Markets, the medium of capitalism, have been replaced by cloud fiefs – digital trading platforms like or Alibaba which, as we saw, look like, but are not, markets. And Profit? The fuel of capitalism? Well, that has been replaced by its feudal predecessor: rent. But, specifically, a new form of rent, a cloud rent that must be paid for access to those cloud fiefs or digital platforms. But how did cloud capital emerge?It began life in the late 1990s when the original Internet, which was a Commons – it functioned as a capitalism-free-zone – that original Internet, Internet 1.0 if you want, was privatised by the emergent Big Tech. Who paid for the trillions it cost to manufacture and to accumulate cloud capital so quickly in the hands of so very few cloudalists? The startling answer is: The G7 countries’ central banks, mostly! How did that happen? Well, by accident, or – to be more precise – by… crisis! After the financial sector collapse of 2008, our central bankers printed up to $35 trillion to bail out the bankers at a time when the governments were subjecting our peoples to harsh austerity. Capitalists were clever enough to foresee that the many would be too impecunious to buy their stuff. So, instead of investing, they took the central bank money to the stock exchange and the bond markets, where they bought shares, bonds – along with yachts, art, bitcoin, NFTs any ‘asset’ they could lay their hands on. The only capitalists who actually invested in capital were Big Tech owners. For example, 9 out of every 10 dollars that went into creating Facebook came from these central bank monies! That’s how cloud capital was financed and how the cloudalists became our new ruling class. As a result, real power today resides not with the owners of machinery, buildings, railway and phone networks, industrial robots. These old-fashioned, terrestrial capitalists continue to extract surplus value from waged labour, but they are no longer in charge, as they used to be. They have become vassals in relation to the owners of cloud capital, of the cloudalists. As for the rest of us, we have returned to our former status as serfs, contributing to the wealth and power of the new ruling class with our unpaid labour — in addition to the waged labour we perform, when we get the chance to do it. But surely, someone will say, this is still capitalism, isn’t it? So, you are still unconvinced? I know, it is hard to part with the term, with the word, capitalism. It is not just liberals who think of capitalism like fish think of the water they swim in – as natural. Socialists too need to feel that our purpose in life, the reason we landed on this Earth, is to overthrow capitalism. The news that I bring that capital beat us to it, and now we have something worse in capitalism’s place, that news is hard to accept. Indeed, it is mostly my fellow-travelling leftist friends who try to dissuade me – to convince me that, yes, cloud capital may be important but “this is still capitalism mate”. Let’s call it rentier capitalism or monopoly capitalism, they suggest. But that simply will not do! Cloud rent is not like ground rent, because it requires massive investment in new tech. And it is not monopoly rent either, because Bezos and Zuckerberg, instead of monopolising markets to sell their manufactures (like Ford and Eddison did), Bezos and Zuckerberg have replaced markets and have no interest in manufacturing anything (unlike Henry Ford and Thomas Eddison). How about surveillance capitalism? Again, no, it won’t do. Cloudalists do not simply use algorithms to brain wash us on behalf of advertisers in an otherwise capitalist setting. No, cloud capital reproduces itself through our free-labour, it directly exploits waged labour, and it squeezes cloud rents from vassal capitalists in trading platforms that are not markets. This is not capitalism folks! Any kind of capitalism. But what about the observation that technofeudalism is parasitic on the capitalist sector within it? Yes, it is true. Were the conventional capitalists to die out, cloudalists would perish, unable to skim off cloud rents from the manufacturers. So what? After capitalism overthrew feudalism, capitalists were also parasitic on landowners, in the sense that, without private land producing food, capitalism would wither. Similarly, now: While the traditional capitalist sector feeds technofeudalism, it is cloud capital and cloud rent that dominate. Does it matter whether we call it technofeudalism or some form of capitalism? At this point, it is important to recall Marx’s maxim that the point is not to interpret but to change the world. So, does it matter if this is still capitalism or whether we call it technofeudalism? I think it does. Recognising that our world has become technofeudal helps us grasp the enormity of what it will take to organise the victims of exorbitant power, the exploited who, now, include not only waged labourers but also the hordes of cloud serfs who are reproducing the very cloud capital that keeps them in a state of deepening precarity. The concept of technofeudalism drives home the point that organising auto-workers and nurses, while still essential, is insufficient. It elucidates what it will take to organise the movements against the fossil fuel cartel when our means of communication are run on cloud capital primed to poison public opinion. It explains how the shift to electric cars caused German deindustrialisation, as profits due to precision mechanical engineering are being replaced by rents extracted by owners of the cloud capital keeping tabs on the drivers’ routes and in-cabin habits. Elon Musk’s decision to buy Twitter suddenly makes a lot more sense. Twitter for Musk is an interface between his mechanical capital stock at Tesla and SpaceX and cloud capital. The New Cold War between the USA and China, especially after the war in Ukraine, is explained as the repercussion of an underlying clash between two technofeudalisms, one whose cloud rents are denominated in dollars the other in yuan. Isn’t it mindboggling? It took mind-bending scientific breakthroughs, fantastical neural networks, and imagination-defying AI programs to accomplish what? To create a world where, while privatisation and private equity asset-strip all physical wealth around us, cloud capital goes about the business of asset-stripping our brains. To own our minds individually, we must own cloud capital collectively. Once we have reclaimed our minds, we can put them collectively to work out a way to create a new cloud capital commons. It will be damned hard. But it’s the only way we can turn our cloud-based artefacts from a produced means of behaviour modification to a produced means of human collaboration and emancipation. Cloud serfs, cloud proles and cloud vassals of the world, unite! We have nothing to lose but our mind-cloud chains! US Edition: UK Edition: Greek Edition:

A video-text summary of my argument that we now live in the age of TECHNOFEUDALISM (in 16', 2000 words): Wherever we turn, we witness the triumph of capital. Capital has prevailed everywhere: in warehouses, factories, offices, universities, public hospitals, the media – in space but also in the microcosm of genetic engineering. So, how do I dare claim that capitalism has been killed? By whom? The deliciously ironic answer is that capitalism was killed by its own hand… by capital! If I am right, the issue is not what AI will do to us in the future but what has already happened: Capital became so dominant that it mutated into a variant so toxic that, like a stupid virus, it killed off its host, capitalism, replacing it with something far, far worse. This new mutant capital, that killed capitalism, lives in the proverbial cloud – so, let us call it cloud capital. What is cloud capital? What makes it so different? Cloud capital, of course, does not really live up in the cloud. It lives down on Earth, comprising networked machines, server farms, cell towers, software, AI-driven algorithms – and of course it lives on our oceans’ floors where untold miles of optic fibre cables rest. Unlike traditional capital, from fishing rods to the steam-engines of the Industrial Revolution to today’s modern industrial robots that are produced means of production, cloud capital does not produce anything – it comprises machines manufactured so as to modify human behaviour. That’s what Amazon’s Alexa or Google’s Assistant or Apple’s Siri is: It is a produced means of behavioural modification. It is a machine, a piece of capital, which we train to train us to train it to determine that which we want. And, once we want it, the same networked machine sells it to us, directly, bypassing markets. As if that were not enough, the same machinery succeeds in making us sustain the enormous behavioural modification machine network to which it belongs with our free voluntary labour. We are sustaining it as we post reviews, rate products, upload videos, rants, photos - we help reproduce cloud capital without getting a penny for our labour. In essence, it has turned us into its cloud serfs! Meanwhile, in the factories and the warehouses, where waged proletarians work under increasingly precarious conditions, the same algorithms that modify our behaviour and sell products to us directly – those algorithms are deployed, usually by digital devices tied to the workers’ wrists, to make proletarians, workers in the warehouses, in the factories work faster, to direct and to monitor them in real time. I started by saying that wherever we turn, we stumble on the triumph of capital. But it is cloud capital that is the real winner. It is amazing how it performs, at once, five roles that used to be beyond capital’s capacities: Cloud capital grabs our attention. It manufactures our desires. It sells to us, directly, outside any traditional markets, that which is going to satiate the desires it made us have. It drives proletarian labour inside the workplaces. And it elicits massive free labour from us, its cloud-serfs. Is it surprising that the owners of this cloud capital – let’s call them cloudalists – have a hitherto undreamt power to extract? To extract gargantuan surplus value from proletarians; untold quantities of free labour from almost everyone; and mind-numbing cloud rents from vassal capitalists – from sellers? Is it a wonder that they are vastly more powerful than Henry Ford or Rupert Murdoch could ever be? “Hang on”, I hear you say. “Is Jeff Bezos really different to Henry Ford? Aren’t they all a species of monopoly capitalists? Monopolists?” No, is not a monopolistic capitalist enterprise. The moment you enter you have exited capitalism altogether! Sure enough, the place is teaming with buyers and sellers. So, yes, it is an enormous trading platform but, no, a market it certainly is not! One man called Jeff owns everything. But he is much, much more than a mere monopolist. Jeff doesn’t own the factories that produce the stuff sold on his platform by traditional capitalists who have to use it to ply their trade. What he does own is more important: Jeff owns the algorithm that decides which products you see and which you don’t – the very algorithm that you have trained to know you perfectly so that it matches youwith a seller, whom it also knows perfectly well, with a view to maximising the probability that every such match, transaction, will generate, for Jeff, the highest rent that Jeff can charge the seller for what you buy: up to 40% of what you pay is pocketed by Jeff, the cloudalist! The mind rebels at the enormity but also the radical novelty of this kind of exploitation: The same algorithm that we help train in real time to know us inside out - that same algorithm both modifies our preferences and administers the selection and delivery of commodities that will satisfy these preferences. If you and I were to type “electric bicycles” or “binoculars” while in you and I would get totally different recommendations. In a traditional market or shopping mall it would be as if you and I were walking next to each other, our eyes trained in the same direction, the same shop window, but we were to see different things depending on what Jeff’s algorithm wants each one of us to see. Everyone navigating around – except Jeff Bezos of course – everyone in is wandering around in algorithmically constructed isolation as if in a Panopticon where, unable to see each other, we only see Jeff’s all-seeing algorithm or, more accurately, only what his algorithm allows us to see with a view to maximising his cloud rent – which is, of course, today’s version of the ground rent that the feudal lords used to extract from their vassals and their peasants. This is not capitalism. Ladies and gentlemen, welcome to technofeudalism! How did cloud capital kill capitalism? How did it rise up? Who paid for it? Capitalism, lest we forget, had two pillars: markets and profit. Of course, markets and profit remain ubiquitous. Nevertheless, cloud capital has evicted both markets and profit from the centre of our socioeconomic system, pushing them out to its margins, and replacing them: Markets, the medium of capitalism, have been replaced by cloud fiefs – digital trading platforms like or Alibaba which, as we saw, look like, but are not, markets. And Profit? The fuel of capitalism? Well, that has been replaced by its feudal predecessor: rent. But, specifically, a new form of rent, a cloud rent that must be paid for access to those cloud fiefs or digital platforms. But how did cloud capital emerge?It began life in the late 1990s when the original Internet, which was a Commons – it functioned as a capitalism-free-zone – that original Internet, Internet 1.0 if you want, was privatised by the emergent Big Tech. Who paid for the trillions it cost to manufacture and to accumulate cloud capital so quickly in the hands of so very few cloudalists? The startling answer is: The G7 countries’ central banks, mostly! How did that happen? Well, by accident, or – to be more precise – by… crisis! After the financial sector collapse of 2008, our central bankers printed up to $35 trillion to bail out the bankers at a time when the governments were subjecting our peoples to harsh austerity. Capitalists were clever enough to foresee that the many would be too impecunious to buy their stuff. So, instead of investing, they took the central bank money to the stock exchange and the bond markets, where they bought shares, bonds – along with yachts, art, bitcoin, NFTs any ‘asset’ they could lay their hands on. The only capitalists who actually invested in capital were Big Tech owners. For example, 9 out of every 10 dollars that went into creating Facebook came from these central bank monies! That’s how cloud capital was financed and how the cloudalists became our new ruling class. As a result, real power today resides not with the owners of machinery, buildings, railway and phone networks, industrial robots. These old-fashioned, terrestrial capitalists continue to extract surplus value from waged labour, but they are no longer in charge, as they used to be. They have become vassals in relation to the owners of cloud capital, of the cloudalists. As for the rest of us, we have returned to our former status as serfs, contributing to the wealth and power of the new ruling class with our unpaid labour — in addition to the waged labour we perform, when we get the chance to do it. But surely, someone will say, this is still capitalism, isn’t it? So, you are still unconvinced? I know, it is hard to part with the term, with the word, capitalism. It is not just liberals who think of capitalism like fish think of the water they swim in – as natural. Socialists too need to feel that our purpose in life, the reason we landed on this Earth, is to overthrow capitalism. The news that I bring that capital beat us to it, and now we have something worse in capitalism’s place, that news is hard to accept. Indeed, it is mostly my fellow-travelling leftist friends who try to dissuade me – to convince me that, yes, cloud capital may be important but “this is still capitalism mate”. Let’s call it rentier capitalism or monopoly capitalism, they suggest. But that simply will not do! Cloud rent is not like ground rent, because it requires massive investment in new tech. And it is not monopoly rent either, because Bezos and Zuckerberg, instead of monopolising markets to sell their manufactures (like Ford and Eddison did), Bezos and Zuckerberg have replaced markets and have no interest in manufacturing anything (unlike Henry Ford and Thomas Eddison). How about surveillance capitalism? Again, no, it won’t do. Cloudalists do not simply use algorithms to brain wash us on behalf of advertisers in an otherwise capitalist setting. No, cloud capital reproduces itself through our free-labour, it directly exploits waged labour, and it squeezes cloud rents from vassal capitalists in trading platforms that are not markets. This is not capitalism folks! Any kind of capitalism. But what about the observation that technofeudalism is parasitic on the capitalist sector within it? Yes, it is true. Were the conventional capitalists to die out, cloudalists would perish, unable to skim off cloud rents from the manufacturers. So what? After capitalism overthrew feudalism, capitalists were also parasitic on landowners, in the sense that, without private land producing food, capitalism would wither. Similarly, now: While the traditional capitalist sector feeds technofeudalism, it is cloud capital and cloud rent that dominate. Does it matter whether we call it technofeudalism or some form of capitalism? At this point, it is important to recall Marx’s maxim that the point is not to interpret but to change the world. So, does it matter if this is still capitalism or whether we call it technofeudalism? I think it does. Recognising that our world has become technofeudal helps us grasp the enormity of what it will take to organise the victims of exorbitant power, the exploited who, now, include not only waged labourers but also the hordes of cloud serfs who are reproducing the very cloud capital that keeps them in a state of deepening precarity. The concept of technofeudalism drives home the point that organising auto-workers and nurses, while still essential, is insufficient. It elucidates what it will take to organise the movements against the fossil fuel cartel when our means of communication are run on cloud capital primed to poison public opinion. It explains how the shift to electric cars caused German deindustrialisation, as profits due to precision mechanical engineering are being replaced by rents extracted by owners of the cloud capital keeping tabs on the drivers’ routes and in-cabin habits. Elon Musk’s decision to buy Twitter suddenly makes a lot more sense. Twitter for Musk is an interface between his mechanical capital stock at Tesla and SpaceX and cloud capital. The New Cold War between the USA and China, especially after the war in Ukraine, is explained as the repercussion of an underlying clash between two technofeudalisms, one whose cloud rents are denominated in dollars the other in yuan. Isn’t it mindboggling? It took mind-bending scientific breakthroughs, fantastical neural networks, and imagination-defying AI programs to accomplish what? To create a world where, while privatisation and private equity asset-strip all physical wealth around us, cloud capital goes about the business of asset-stripping our brains. To own our minds individually, we must own cloud capital collectively. Once we have reclaimed our minds, we can put them collectively to work out a way to create a new cloud capital commons. It will be damned hard. But it’s the only way we can turn our cloud-based artefacts from a produced means of behaviour modification to a produced means of human collaboration and emancipation. Cloud serfs, cloud proles and cloud vassals of the world, unite! We have nothing to lose but our mind-cloud chains! US Edition: UK Edition: Greek Edition:

Yanis Varoufakis

1,817,609 просмотров • 2 лет назад