[deleted]
My First Impressions of Web3
321–330 of 1001 posts
Re: My First Impressions of Web3
#322Earlier quoted context omitted.
Please don't degenerate into flamewar. https://news.ycombinator.com/newsguidelines.html
With the greatest respect, I disagree with this reading of the parent’s comment. It doesn’t seem particularly inflammatory to me? Or at least enough to warrant this call out… It’s expressing a strong view yes, not necessarily one I disagree or agree with (I don’t know enough on the topic yet to take a view), but this doesn’t seem to blatantly break the guidelines. If it wasn’t for the superb track record for what I v…
[deleted]
Re: My First Impressions of Web3
#323Earlier quoted context omitted.
MetaMask is a wallet, its not ingrained into any blockchain, your free to use alternatives, and many protocols don't support it. The centralized aspect of a chrome app and marketplace like opensea is very well know issue and talked about a lot in crypto, the problem of course comes down to lack of education, which is apparent in this very post.
Can you point me to where this insightful discussion happens? And where can I educate myself? 99,99% of content and forums I find online about crypto only care about promoting coins, nfts or services basing only on futuristic visionary promises, hyping up the users and attempts at FOMO. It's almost literal spam. This is the first time I read something that just explains how thing works from a technical standpoint and…
This is the best place for deep, technical discussions free of shilling: https://ethresear.ch/
Re: My First Impressions of Web3
#324> 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…
> Like this author says, most people don't want to run their own web server... I know I certainly don't. I want to write my software and I want to be able to deploy it somewhere and manage the things I may care about for that specific software. As much as possible I don't want to have to care about hardware, or routing, or server administration, or user permissions, etc. Learning it once? Sure. Dealing with it every…
Amen. I don't even get why most companies have Dev-ops. For the price of one Dev-ops you can get the most expensive plan on many providers. Running the most expensive Heroku plan (with a concierge service) is cheeper than an employee, and office space, and medical insurance, and ....
And that's just the one provider I know.
I want to type git push master, and that's the end of my involvement in standing things up.
Re: My First Impressions of Web3
#325Earlier quoted context omitted.
The fact that all the data is there is kind of irrelevant if you can't query it.
Why would you want to query it, though? A full node lets you fully verify the chain's historical states and it lets you interact with the current state. Unless you're running a service that exists solely to allow people to query historical states (like a block explorer service), I don't see why it would be useful to be able to query historical state.
You need an archival node to see a list of all transaction that transfer eth into an address.
A full node can only give you the current balance, and a list of all transactions that directly transfer eth to that address. Any transaction that transfers eth as the side effect of a smart contract is invisible.
I personally see it as a flaw in the design of eth. You shouldn't need the complete history of states just to find all relevant transactions, but you do.
Besides, the argument that regular users shouldn't need to query such information it doesn't change the fact that the information is unqueriable in a full node, short of spending 28 days transforming it into an archival node.
Re: My First Impressions of Web3
#326> 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…
I think this is an excellent point.
People will run all sorts of things they don't directly interface with if the setup and functionality is low friction. People run routers for example. If you had to SSH into your router and troubleshoot it just to figure out why you're not getting connectivity people wouldn't do it. Unplug it for 5 seconds and plug it back in? Still frustrating, but the UX has low friction.
If you can buy a little square box that you plug into the wall and it Just Works™ people would do it. People used to leave their home PCs running all day to allow them to perform server type functions.
When I build a home server, I generally shoot for low maintenance, but I do the setup myself. If I can do it once, I can do it once for a million people. Sane defaults, low friction UX, just the needed functionality, everything starts on boot and resets on reboot to a working state is all it really takes.
Re: My First Impressions of Web3
#327Earlier quoted context omitted.
It's refreshing to read an article that admits this: > > Even nerds do not want to run their own servers at this point. I actually enjoy build and running servers, but only for hobby purposes. When it comes down to anything business related or critical, I have zero desire to run and maintain it on my own. And I especially don't want to have to handle security for large amounts of money that could disappear in an inst…
For sure. I ran my own servers for many years. And I still enjoy playing with hardware at home. But a couple years back I shut down my last colocated physical server and I do not miss it. The background stress of knowing that at any point I might have to wake up, haul my ass down to a colo, and swap a motherboard just got to me. Now all my must-stay-up stuff is built via Terraform in a a public cloud. If there's a ha…
> The background stress of knowing that at any point I might have to wake up, haul my ass down to a colo, and swap a motherboard just got to me.
I would miss mine terribly. I couldn't afford colo and hosted on VPS for a while but just didn't cut it. The Cloud is the same. Kind of like having two monitors and downgrading to only one.
In all honesty how often does that requirement come about? Did you not have fail over? 2u is mandatory if you want to fully exercise colo, 4u is ideal.
> If there's a hardware failure, it's not my problem. It's such a relief!
Not for me, if AWS or Azure fall over I'm at the mercy of the engineers to fix which could take hours just due to the processes standing up the cloud. And when those occurrences happen its normally fatal. If the same happens in colo their are only three reasons.
Datacentre, Server or DDoS
Granted you can either live on the edge and having no spare hardware and hope they don't die. Or have kit ready to ship and rack. My colo servers are eight hours from me and always happy to jump down to my rack to fix whatever.
But I do respect your opinion because I don't know the variables you live in. Colo forever with me.
Re: My First Impressions of Web3
#328Earlier quoted context omitted.
Oh it’s totally doable to run your own node on your own server! And thanks to the protocols consensus rules your users can trust that for a transaction to go through your node and be accepted onto main net your node is a good actor. So one example I’d give - every team I’ve worked on has had to build a local development environment with several nodes to easily spin up with a clean slate for deterministic testing. Tea…
> And thanks to the protocols consensus rules your users can trust that for a transaction to go through your node and be accepted onto main net your node is a good actor. Usually, you still have the “server is selectively lying” problem; unless the users are talking to each other, how do the consensus rules help with this? (Related to the https://en.wikipedia.org/wiki/Byzantine_fault problem, though that's about form…
> Usually, you still have the “server is selectively lying” problem; unless the users are talking to each other, how do the consensus rules help with this?
If you're submitting txs to a node that doesn't communicate to the mainnet (they're isolated from it) then any txs that go to it would be void. You could just use that Eth on the proper mainnet as it wouldn't be on the chain. If the node decided to then come onto the mainnet it's chain would be vetoed by the other nodes states and would fork back onto the main chain. Ethereal has Byzantine-Fault Tolerance up to 50% and you don't gain anything by running an isolated node to try trick people.
Re: My First Impressions of Web3
#329Earlier quoted context omitted.
Fortnite made $50 million selling NFL skins alone: https://www.sportskeeda.com/amp/fortnite/the-fortnite-skin-g... And the total sales volume since release is in the billions. Maybe a generational thing?
Kids who get a hold of their parents credit cards or the new generation of people who will live off stocks their parents gave them. We’ll see how much they’ll be spending on skins when they grow up/can’t game all the time. However I think this new class of all day gamers isn’t going anywhere. It’s the perfect time sink for the new leisure class. Orgy porgy
[deleted]
Re: My First Impressions of Web3
#330>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…
As the article points out, many NFTs are implemented by storing a URL in the blockchain; the digital artwork sits on some server and is reachable by that link. Fine, you can prove that you own the URL. But what that URL points to can change out from under you, so there's no way to make that trustless. If you own the domain and the server that it points to, the registrar can take the domain away from you and give it t…
So, this has a really easy fix. The NFT points to a content hash, and the content is uploaded to the Internet Archive (and they're compensated for the storage) as part of the NFT minting process.
Your ownership is now on a distributed ledger, with a cryptographic hash of the content, paired with long term storage of said digital artwork. The Internet Archive's costs are ~$2/GB to store content in perpetuity, which seems insanely cheap to carve off as part of a transaction (Eth gas fees aside).