Live data from Hacker News

My First Impressions of Web3

moxie.org

291–300 of 1001 posts

Re: My First Impressions of Web3

#291

The first article on Web3 that I've read that drills into the details and was written by someone who's not only kicked the tires but taken the thing for a spin. And the conclusion: It's mostly the bad stuff of Web2 combined with the bad stuff of Crypto.

[deleted]

Re: My First Impressions of Web3

#292
post #118

> People don’t want to run their own servers, and never will. Not really much related to web3/crypto topics, but I think this is an indictment of servers, not people. If managing a server were easy and secure, lots of people would do it - for blogs, a minecraft server for the kids, to back up their pictures, and yes, to store their bitcoins or other digital secrets - they just don't want to manage a unix or windows s…

What is the benefit to the average user of running their own server? Most people (maybe even on HN) just want things to work. We buy connectivity services for our phones and our homes. I certainly don't want to run my own Wireless ISP to connect up my neighbourhood even if it was marginally cheaper (until I account for my time). We buy storage services (for lots of reasons) from Amazon, Google, , etc. I don't want to…

The value to the average user is the possibility of self-hosting under unusual circumstances. It's like insurance. In a walled garden, when you get canceled there's nothing you can do. In an open Internet when you get canceled you can self-host. 99% of people will never need it but the option is valuable.

Re: My First Impressions of Web3

#293
post #165

Earlier quoted context omitted.

Algorand is carbon-negative. The inventor is a Turing-award winning MIT professor.

Via carbon offsets, so they emit all the co2 up front and then hope the forests their partners plant are both real and will be properly managed for the next few decades.

They emit very little co2 up front. So little that they trivially reach carbon-negative with a small amount of carbon offsets.

Re: My First Impressions of Web3

#294
post #157

Earlier quoted context omitted.

I should have said archival nodes, the ones that keep state back to the genesis block. I don't know if that number is even tracked anywhere. I've read estimates ranging from 2 to 5. I'm trying to find where I read that, happy to be wrong - or right, if anyone has data. [edit] Here. [1] And here. [2] After examining every which way we could think of to add the Trie state to our Ethereum state, we asked Vitalik for ass…

everyone running erigon nodes (like myself) are running full archival nodes, currently there are ~300, https://www.ethernodes.org/ . Many geth nodes are archival, but we cant see which ones are.

Some Erigon nodes run with pruning enabled. You can't tell which ones those are, or how much pruning.

Technically you can tell which Geth nodes are archive nodes with a GetNodeData query over devp2p, although that call is deprecated and will eventually be removed. Its replacement, GetTrieNodes, cannot be used for this.

Re: My First Impressions of Web3

#295

The first article on Web3 that I've read that drills into the details and was written by someone who's not only kicked the tires but taken the thing for a spin. And the conclusion: It's mostly the bad stuff of Web2 combined with the bad stuff of Crypto.

This article helped me understand why OpenSea was able to raise money at a $13 billion valuation. They're even more centralized than I had assumed. VCs look at that and see an impressive moat.

Re: My First Impressions of Web3

#296

I always had trouble understanding what web3 was all about because I just couldn't figure out why anyone would be excited for it. I found this article to be excellent at explaining what the platform is but I still can't figure out why people keep bringing up this topic when it's clearly a classic example of a "Solution in Search of a Problem".

>but I still can't figure out why people keep bringing up this topic when it's clearly a classic example of a "Solution in Search of a Problem".

They hope they can make money.

Re: My First Impressions of Web3

#297
> Despite considering myself a cryptographer, I have not found myself particularly drawn to “crypto.”

I would give this intro more credence if it hadn't been posted literally a day after he put his MobileCoin shitcoin into Signal.

It's annoying, because the rest of the article is good and apposite - but then he did that.

Re: My First Impressions of Web3

#298

Earlier quoted context omitted.

I don't think this article "lampoons" web3 in any way. While the article is on the whole critical (but not completely), it did not do so using sarcasm, ridicule, or irony. lampoon: publicly criticize (someone or something) by using ridicule, irony, or sarcasm.

Hmm, you're quite right. Poor word choice. Perhaps 'skewers' would be more appropriate.

Eviscerates. This is a vivisection. We can see how it works, but this kills the frog.

Re: My First Impressions of Web3

#299

> People don’t want to run their own servers, and never will This kind of gets at the reason why I think a lot of tech articles/blogs about what the future will be like are just terrible. The wants of someone who is driven enough read and write about the bleeding edge of technology are very, very different from the general population. Like this author says, most people don't want to run their own web server, but I'd…

[deleted]

Re: My First Impressions of Web3

#300
post #72
post #29

>When you think about it, OpenSea would actually be much “better” in the immediate sense if all the web3 parts were gone. It would be faster, cheaper for everyone, and easier to use. That sums up the situation for me. Having a marketplace for purely digital goods might be a concept with a future. Having standard ways to interoperate between different platforms and query and update these goods might make sense (althou…

> Couldn't Rolex issue a PGP signed CSV of all valid Rolex serial numbers once a month on IPFS and you'd get the exact same security and trust profile without having to involve any "web3" feature? A serial number can be copied and engraved onto a forged watch, so not really. A more analogous scenario would be if Rolex embedded an NFC hardware chip with a private key inside the watch, such that anyone could wave their…

This is sort of true. In the case of the watch, if you read the blockchain for the serial-number on the Rolex, you could engrave that too? The storage medium of the data wouldn't make a difference. The same could be said for the NFC chip. Those are copied all the time. Just purchase a blank and overwrite it with an original.
Post reply on HN