Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Guido van Rossum: Let Web3 die in a flaming ball of fire

twitter.com

Post reply on HN
Print view View original

171–180 of 316 posts

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#171

Post by nomel »

smt88 wrote: post #78
influx wrote: post #69

Earlier quoted context omitted.

You don't think there's any value in an open source system that proves scarcity in a digital universe?

Why would I want artificial scarcity in any situation? Scarcity is bad.

> Scarcity is bad.

We could just print money and all be rich? If you value money, and you think that compensation for work can be paid with money, then compensating the work that went into creating digital goods seems appropriate. Should compensation for digital goods be through donations?

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#172

Post by maupin »

izolate wrote: post #163
howmayiannoyyou wrote: post #98

Earlier quoted context omitted.

I just created the world's most redundant and incorruptible database. People will have to pay many dollars to specialists called "miners" to add rows. For integrity reasons, no one can delete anything from it. It might change parts of the world where redundancy and integrity are threats to very powerful people who want to control transactions and corresponding data. -- Fixed it for you

> For integrity reasons, no one can delete anything from it. Except if they're the central authority, in which case they can unilaterally rollback the blockchain, rewrite history and fork? Totally makes sense.

Well, they're not "web3" then. No central authorities allowed.

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#174

Post by vmception »

HideousKojima wrote: post #143
vmception wrote: post #85

Earlier quoted context omitted.

Thanks for coming to this thread, I'm curious what the other person meant though. Yes, there is a stack and heap limiting the amount of resources that a command can use. So what? Design your application with that limitation in mind. Focus on what you can control, its a one-step one-click funnel that is inherently a payment and insatiable demand right now from the users. A Web 2.0 dream, I've sat through so many usele…

>Focus on what you can control, its a one-step one-click funnel that is inherently a payment and insatiable demand right now from the users right now is the really, really big issue here. We're talking about pay once read forever, not pay once read right now, or pay once and read while there's still interest or demand in running nodes.

Can you elaborate on what your concern/criticism/cynicism is?

What use case are you trying to imagine?

I think its been very easy and very competitive to design applications around using these redundant blockchain nodes as event-driven compute nodes, when compared to AWS Lambda or even addons to a paid Vercel plan or hosting my own microservice somewhere. The uptime has been on-par and the system design gives some assurances of the ability to maintain the uptime where it could theoretically be a concern.

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#175

Post by overkalix »

howmayiannoyyou wrote: post #98
labrador wrote: post #60

I just created the worlds slowest database. People will have to pay many dollars to specialists called "miners" to update it. For design reasons, no one can delete anything from it. It's going to change the world.

I just created the world's most redundant and incorruptible database. People will have to pay many dollars to specialists called "miners" to add rows. For integrity reasons, no one can delete anything from it. It might change parts of the world where redundancy and integrity are threats to very powerful people who want to control transactions and corresponding data. -- Fixed it for you

> It might change parts of the world where redundancy and integrity are threats to very powerful people who want to control transactions and corresponding data.

And how is this change supposed to work?

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#176

Post by croes »

howmayiannoyyou wrote: post #98
labrador wrote: post #60

I just created the worlds slowest database. People will have to pay many dollars to specialists called "miners" to update it. For design reasons, no one can delete anything from it. It's going to change the world.

I just created the world's most redundant and incorruptible database. People will have to pay many dollars to specialists called "miners" to add rows. For integrity reasons, no one can delete anything from it. It might change parts of the world where redundancy and integrity are threats to very powerful people who want to control transactions and corresponding data. -- Fixed it for you

If you need many dollars to add rows only the powerful could add lines.

Sounds like bringing back aristocracy.

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#177

Post by maupin »

RedShift1 wrote: post #170
ceejayoz wrote: post #149

Earlier quoted context omitted.

The bug part comes in when someone stuffs a few child porn images into the chain, making mere possession of a full node carry jail time in the US. Even better, due to strict liability, "I didn't know" or "It's not mine" aren't valid defenses. I wouldn't want to have to tell a judge "I can't remove it" in a libel proceeding, either.

Hmm, now I'm wondering why this hasn't happened yet? Is there be a way to encode arbitrary data inside a transaction?

As far as I know it has happened. It's been in Bitcoin and probably many other blockchains for years.

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#179

Post by vmception »

kovek wrote: post #119
vmception wrote: post #85

Earlier quoted context omitted.

Thanks for coming to this thread, I'm curious what the other person meant though. Yes, there is a stack and heap limiting the amount of resources that a command can use. So what? Design your application with that limitation in mind. Focus on what you can control, its a one-step one-click funnel that is inherently a payment and insatiable demand right now from the users. A Web 2.0 dream, I've sat through so many usele…

I didn’t understand you. But, imagine a DDOS attack on the nodes serving the blockchain. I don’t see why “pay once read forever” works financially.

> But, imagine a DDOS attack on the nodes serving the blockchain.

Okay.

> I don’t see why “pay once read forever” works financially.

A separate issue thats not really your problem. Its the node operators problem. When your use case expands to that being a viable problem for you, then you'll need to become a node operator or at least keep a copy of the state yourself. You can design applications around that. Or maybe you can't. Just rule those out or keep using AWS or some other company for those applications?

Re: Guido van Rossum: Let Web3 die in a flaming ball of fire

#180

Post by tquinn35 »

gtirloni wrote: post #159
tquinn35 wrote: post #109

Earlier quoted context omitted.

I disagree with this. I work at a large US bank and from the conversations I have been apart all the big banks are moving into crypto. So much float is moving out of the banks that they are scramble to catch up to try and control the damage. They are all planning to become crypto banks in a custodial sense to maintain float. Lots of people want to hate the new trendy thing but once this gets mainstream banking suppor…

Could you give us a ballpark number of how much is moving out of banks compared to the reaming that is not? Is it 10, 50 or 90% of the current economy?

The number that was quoted was "in the ballpark of 30%"
Post reply on HN