Oddbean

No Cloudflare. No DDoS. It’s live! Our new website is a solution to Cloudflare. Let’s break it down: Problem: Cloudflare breaks SSL encryption and acts as a man-in-the-middle to see all passwords. And by seeing the bulk of all traffic, they are able to do mass surveillance. Issue: When you bring up getting off Cloudflare with website creators, they say “But what about DDoS?”. And then you’re just directing them to less centralized alternatives, which could become the “next CF” if they got popular. Solution: Arweave is on-chain data storage functioning similar to Bitcoin Ordinals (but it scales). There's a brand-new testnet of global gateways for Arweave, to serve this content: For example I’m “Privacy” So you just put the name “Privacy” then a dot, in front of the Gateways. Germany ISP: Skylink https://privacy.arweaveblock.com France ISP: OVH https://privacy.arnode.xyz New York, USA ISP: Nubes, LLC https://privacy.exodusdiablo.xyz Los Angelos, USA ISP: Internet Access Company https://privacy.ardevpark.com United Kingdom ISP: Contabo GmbH https://privacy.flexibleee.xyz Turkey, Istanbul ISP: Yunus Emre https://privacy.thecoldblooded.online Singapore ISP: Lucidacloud Limited https://privacy.araoai.com China, Hanoi ISP: VNPT https://privacy.adn79.pro Brazil ISP: Redemetro Teleaco https://privacy.arbr.pro India ISP: Logiclabs Tech https://privacy.satoshispalace.xyz Pick one close to you, and try it out!

What you are saying is not logical and disconnected from reality. Blockchain as a whole has thousands of different things. The bandwidth that can be gotten from Arweave gateways would be a reflection of how many gateways and how much use the network is getting. This is not something you or me know right now. The idea that promoting Cloudflare and Blockstream's Lightning on Google Cloud, as decentralized.. is ridiculous. You are essentially spewing low level dribble

the structure of a blockchain is precisely tightening the precision of data that is kept on record by multiple replicas... the less tight this consistency, the more data, but the higher chance that you can't retrieve data from any given point in the network (consistency, availability and partition resistance) most of the blockchain clients run on these cloud devices or are in a small set of data centre locations, because they have such high requirements... for example, the Internet Computer Protocol requires machines with 64+ cores, 256gb memory, and have a price tag in the tens of thousands of dollars bitcoin has a small state history because of the target minimum requirement, and this is a relationship you can determine precisely based on what you want to get with the CAP factors of the system replication and the properties of the consensus you use blockchain is not the higher category here either, it's distributed systems, which are mostly limited by things like lightnspeed and the target level of replicas, how fast you want the network state to converge, and how you prevent it from forking IPFS and bittorrent have different replication properties, as does the nostr network, nostr is more like bittorrent in that the replicas have a very low convergence and consistency is inherently low, but at the same time data tends to leak, which gives it censorship resistance "blockchain" is a buzzword that means very little... it is literally just a system of ensuring integrity of a chain of transactions by the use of hashes that refer to prior nodes on the chain

ok, I don't know enough about ICP to comment on the first part. Nostr is very different from Bittorrent, there is only the sharing of data on discovery. You're pulling the actual data from 1 relay from my understanding of gossip's model and notice you did not mention arweave's gateways, nor did you mention cloudflare or the centralized internet. So your answer is what? do nothing and more of the same? no thanks

arweave gateways, and these are now a part of ICP, i just got a heads up about this, they now have web proxies in development for ICP, are just proxy caches, nothing special about that, it's just increasing the read capacity of the system the only difference between nostr and bittorrent is the lack of a DHT for finding who has the events, it would be pretty easy to add such a feature

Are you sure you're not mixing up ICP and AO (arweave's "super computer")? As far as I understand, this is renting the nodes out to run code. The nodes are different then the gateways. https://ao.arweave.dev/ This should not change the speed of gateways, and if it did from extra traffic, then more gateways would come on with all the extra revenue the service is doing to the coin(s) value(s). Arweave uses modified BitTorrent as part of it's "Proof of Access" system to share among nodes. But the gateways serve it to the end-consumer using regular https in a regular web browser.

lol, you think i don't know about these things intimately, it's my work just got notified yesterday that ICP is now adding gateways, and there is a list of about 30 on the configuration being provided and i'm extremely skeptical about arweave and i am actually working with it... been designing data structures for a social network aggregator the gateways are just caching proxies, much like the edges of cloudflare's DDoS protection system, it's to shift work away from authoritative replicas and the reason why these "cryptos" need these things is that there is no incentive to run a non-authoritative replica, unlike with bitcoin, where the incentives are privacy and reliability for your payment infrastructure the fact that payment/transfer use case is so minimally useful and not valuable to these networks is the biggest red flag that they don't survive once the marketing engine slows down

you're correct that just pure AR has no incentive to run gateways. That's why ar.io is now doing a system to pay gateways to run them, coming from the profits of those who buy DNS and update it. It's unclear what your point is, that we should all just use cloudflare? There is no Bitcoin binding contract

This is not just "spam", we're talking about censorship, privacy, and centralization issues with a single provider seeing, controlling, and hosting like 90% of sites/data. This affects Nostr as well, as many of the relays are on Cloudflare. You would benefit from this article on the issue: https://simplifiedprivacy.com/cloudflare/index.html

It's amusing that you're trying the crypto volatility angle, as Bitcoin drops over 10% today. And Bitcoin does nothing but "store value", while Arweave has useful market purpose. Even if Arweave suffers heavy volatility, they collect for 100 years upfront at today's prices. Considering storage prices are dropping, there would have to be massive downside volatility to not have at least 10+ years... which is wayyyyy more than most blogs/websites need. A blog can update every day or week. So you've really failed to address the main issue of decentralized storage/CDN to avoid Cloudflare.

Thanks for your reply. a) The chart is spiking up and down, that's not a trend. Arweave has over a billion dollar market cap, and value is subjective in the eye of buyer. b) Bitcoin has no binding contract. Systems such as Arweave enable trustless systems. As opposed to a system where you pay for something and don't know if the counter-party will deliver. Instead of thinking of this as currency, it's more like a stock in a semi-decentralized company. c) Ok. But I think you should properly learn about it before dismissing it. d) True wealth is created by investing in businesses that produce valuable things. Equities have and will always outperform Gold in the long run, and Bitcoin is essentially just digital censorship-resistant gold now. Bitcoin is not cash, you’re not talking about getting off banks.