theWeb3CloudGuy.icp ∞

303 posts

theWeb3CloudGuy.icp ∞ banner
theWeb3CloudGuy.icp ∞

theWeb3CloudGuy.icp ∞

@theweb3cloudguy

🌐 Cloud Engineer (7+ yrs) | Web2 → Web3 | Exploring ICP, ETH, BTC, HBAR | Tech believer & enthusiast 🚀

Berlin, Germany Se unió Ağustos 2025
254 Siguiendo32 Seguidores
Tweet fijado
theWeb3CloudGuy.icp ∞
theWeb3CloudGuy.icp ∞@theweb3cloudguy·
The cloud is changing 🌐 After years in AWS, GCP & Azure, I’m diving into @dfinity’s #ICP — a blockchain that reimagines the cloud by running compute & storage directly on-chain.
English
4
2
28
892
Fabio
Fabio@Zero2HeroZombie·
Tick tock ⏲️ Governments & Large Institutions are the new target audience for internet-computer:native
Fabio tweet media
English
3
26
121
1.8K
Fabio
Fabio@Zero2HeroZombie·
Wait what? Is this a glitch on the internet-computer:native ??? 13.9 Trillion cycles/s is insanely high.
Fabio tweet media
English
27
33
240
14.1K
theWeb3CloudGuy.icp ∞ retuiteado
ChrisYost.icp ∞
ChrisYost.icp ∞@ChrisYost_·
Cloud Records now supports video playback entirely on chain 🎥📺⛓️ No AWS. No S3. No CloudFront. No IPFS gateway. No YouTube embed. Just a canister on @dfinity — the smart contract is the host. Link in reply ⬇️ A Cloud Foundation Production ♾☁️🎧 $ICP
English
30
47
195
5.9K
theWeb3CloudGuy.icp ∞ retuiteado
theWeb3CloudGuy.icp ∞ retuiteado
dom | icp
dom | icp@dominic_w·
Internet Computer's 5th birthday on May 10th, 2026. To celebrate, DFINITY will demo "cloud engines," including agentic builds, AI nodes, and more. This is a very big deal for ICP, cloud and agentic R&D. Engines will be the 1st frontier cloud/compute technology the wild⏱️
English
94
290
1.1K
45.1K
theWeb3CloudGuy.icp ∞ retuiteado
dom | icp
dom | icp@dominic_w·
Someone got Wordpress running 100% from the Internet Computer! Not as easy as it sounds, as it's designed to run on traditional tech, not frontier serverless cloud, so big shout out to ICP community member @miadey 🔥 forum.dfinity.org/t/wordpress-ru…
English
60
222
920
33.6K
theWeb3CloudGuy.icp ∞ retuiteado
Chainspect
Chainspect@chainspect_app·
.@dfinity just crossed 280 BILLION transactions That's 280B+ transactions powering an agents-first cloud network for building performant apps and services 📊 chainspect.app/chain/icp
Chainspect tweet media
English
14
63
291
10K
theWeb3CloudGuy.icp ∞ retuiteado
dom | icp
dom | icp@dominic_w·
For more than 10 yrs, I've worked on "frontier compute." I've worked on this since the "world computer" vision was first mooted. Nowadays, the terms "crypto," "web3" and "blockchain" are inextricably linked to speculative assets. But this is 1 niche application of the tech. 🧵
English
80
213
837
33.2K
Pierre
Pierre@PierreSamaties·
Oh my… @Bankless writing a whole thread on “Solving Crypto’s Frontend Problem” without once acknowledging that full‑stack, tamper‑proof internet services (frontend, backend, and data) have been running on decentralized cloud networks for years is actually insane. Crypto doesn’t only have a frontend problem, it has a glaring journalism credibility problem. Who, in 2026, still talks about “frontend hosting” like it’s unsolved while ignoring architectures where the application runs end‑to‑end on a decentralized compute network and is served directly over HTTP, with no Web2 servers and no reliance on traditional DNS as a security choke point? Human‑error attack surfaces get radically smaller when there’s no web2 backend to phish or socially engineer. Y’all hyping tiny bytecode tweaks on legacy L1s like they’re groundbreaking while the real full‑stack, decentralized cloud solution has been live since 2021. The blind spot is embarrassing. Or is it intentional?
Bankless@Bankless

DNS hijacks are spiking in crypto. CoW Swap and eth (dot) limo were both hit. You visit a frontend, everything looks normal, you sign a transaction and funds go to an attacker's wallet. The defense isn't better detection. It's frontends that STRUCTURALLY can't be cracked. Two approaches already exist: > IPFS + ENS: Your frontend lives on a distributed file network instead of a server. Point your web3 domain (ENS) at that file. No DNS, no central server to compromise > Fully onchain (ERC-4804): The app itself lives inside smart contracts. The frontend is served directly from Ethereum Sadly though, regular browsers can't load either. That’s why we have web3 browsers like: > Freedom Browser: open-source browser that loads ENS domains and IPFS sites natively, the same way Chrome loads (dot) com addresses > EVM Browser: built around the web3:// protocol, loads apps served directly from smart contracts on Ethereum or any EVM chain The proof of concept is already live. @z0r0zzz built zSwap is a DEX frontend deployed ENTIRELY into Ethereum contract bytecode for under $5. Anyone can load it through EVM Browser. In other words: No servers, No DNS, Nothing to hack. Every DeFi project should ship a permanent onchain frontend as a fallback. Best security is just to go straight to the contract. The tools exist. Build toward it.

English
51
117
437
22.2K
theWeb3CloudGuy.icp ∞ retuiteado
dom | icp
dom | icp@dominic_w·
People asking what ICP "cloud engines" – the Internet Computer as frontier onchain cloud for agents building apps, services and systems - actually looks like. Here's approximately what's coming:
dom | icp tweet media
English
89
277
968
65.2K
theWeb3CloudGuy.icp ∞ retuiteado
DFINITY Foundation
DFINITY Foundation@dfinity·
The 1990s gave us the Internet Service Provider model. Cloud Engines are bringing it to compute.
DFINITY Foundation tweet media
English
19
90
338
14.2K
caffeine
caffeine@caffeineai·
Your app lives in Caffeine. Now your code can too - on your terms. A lot of you have been asking for this. You want to open your codebase in your own editor, version it properly, work with your existing tools, and bring it back into Caffeine when you're done. That's exactly what GitHub import lets you do. Export to GitHub, tweak it however you want, and pull it straight back in. Your workflow, your tools.
caffeine tweet media
English
19
75
257
13.3K
theWeb3CloudGuy.icp ∞
theWeb3CloudGuy.icp ∞@theweb3cloudguy·
@kristoferlund In simpler terms, when we get vulnerable npm packages, and my app uses them, I should also be worried like the rest of web2 apps? How does running on $icp save me from those vulnerabilities?
English
0
0
0
11
Kristofer
Kristofer@kristoferlund·
NPM hosts 3.1 million packages. Now, ALL those packages are available to your Caffeine app! 🤯 In this vid I replace the default text editor with the super nice Editor.js package.
English
10
34
138
9.9K
mert
mert@mert·
decentralization is coordination without central authority a thought experiment: assume the most decentralized blockchain in existence. hundreds of thousands of nodes, run at home, with distributed mining power and coin supply. now assume, hypothetically, that if North Korea is able to move funds from Wallet A to Wallet B on this chain in a time period T, then it's tied to an automatic switch such that NK is able to detonate nuclear weapons in a majority of countries in the world simultaneously (remember, it's a thought experiment) finally, assume that the blockchain was able to fork such that Wallet A funds were frozen and billions didn't die now: was that blockchain decentralized or not? well, given that the incentive of humans is to not die, they were able to coordinate under a shared incentive to prevent this so while the chain itself is decentralized, that does not imply that the chain is disorganized put differently: decentralization actually means coordination without central authority if the cost of coordination is functionally zero, then it's centralized however, if the cost is infinite, then technically speaking, it is still not decentralized because you can not even apply that terminology to a non functional system (i.e you can't even process state transitions if the nodes don't coordinate to make blocks)
mert@mert

reminder

English
66
23
256
39.4K