4 ms·

There is no single company driving the PR and marketing for Web3, so the term is whatever somebody wants it to be. But the vague way to describe it is an approa

There is no single company driving the PR and marketing for Web3, so the term is whatever somebody wants it to be. But the vague way to describe it is an approach to building web apps with decentralized public blockchains and smart contracts, like DeFi or ENS.

andsoitis 4y ago
Enabling what? Use cases > technology shiny objects.
- threeseed 4y ago
  Money laundering, gambling and stock trading for kids of all ages. Also the whole rug-pulling game has been an impressive transfer of wealth from VCs -> influencers.
  - joeax 4y ago
    Sounds more like the early days of web 1.0
    - threeseed 4y ago
      I was on the internet in the early days of Web 1.0 None of those things were happening.
- zeroclip 4y ago
  It's a distributed ledger, that you can deploy a computer program to. Use cases extend outward from there.
  - andsoitis 4y ago
    Can you articulate one end user benefit / use case that’s not possible today or that would be better than today?
    - zeroclip 4y ago
      “Better” is relative, depends on your frame of reference. Anything crypto will be better in some ways, and worse in others. Like self custody: the idea of owning a valuable and transferable asset by only holding a private key was not possible prior to Bitcoin. The closest comparison might be a domain name: people feel like they own those, but they are just renting them from a registrar who leases you the account and ability to edit your domain records. This applies all over Ethereum, DeFi, ENS, NFTs. Look at Aave, that allows lending and borrowing without a custodial service provider.
- derefr 4y ago
  For one small example: enabling this https://docs.ipfs.tech/ https://docs.ipfs.tech/ website, to be delivered to your browser care of a (replaceable commodity) gateway node that fetches assets by URL-embedded content-hash from an open-membership DHT. (If you're wondering how this website appears on its own domain rather than you needing to directly visit the domain of the gateway node, that's because of https://docs.ipfs.tech/concepts/dnslink/ https://docs.ipfs.tech/concepts/dnslink/).
  - andsoitis 4y ago
    Can you reframe that in terms of end user benefit?
    - derefr 4y ago
      Site will never go down; data backing the site will never be lost; content-addressability of data means data is guaranteed to be the same data that was intended to be published, with no ability for e.g. a state-actor to tell Amazon to modify what's in the S3 bucket. In other words: if someone could figure out how to host ThePirateBay on IPFS, then governments wouldn't be able to take them down any more. They'd only be able to take down arbitrary IPFS gateway nodes; and if they did that enough to be a problem, anyone who cared could work around that by just running their own IPFS node. (Or using a browser like Brave which runs its own IPFS node internally.) Content will be fetched from by DNSLink-aware browsers in preference to hitting the gateway specified in the DNSLink record, so as soon as you used such a browser, all the taken-down domains would just magically work again for you.
      - n3t 4y ago
        > data backing the site will never be lost Data can be lost. I put a few files on IPFS some time ago. That files are no longer accessible because I stopped hosting them. > Site will never go down As long as there is a node hosting the data you're looking for. So it can go down.
        derefr 4y ago

andsoitis 4y ago

Enabling what? Use cases > technology shiny objects.

threeseed 4y ago
Money laundering, gambling and stock trading for kids of all ages. Also the whole rug-pulling game has been an impressive transfer of wealth from VCs -> influencers.
- joeax 4y ago
  Sounds more like the early days of web 1.0
  - threeseed 4y ago
    I was on the internet in the early days of Web 1.0 None of those things were happening.
zeroclip 4y ago
It's a distributed ledger, that you can deploy a computer program to. Use cases extend outward from there.
- andsoitis 4y ago
  Can you articulate one end user benefit / use case that’s not possible today or that would be better than today?
  - zeroclip 4y ago
    “Better” is relative, depends on your frame of reference. Anything crypto will be better in some ways, and worse in others. Like self custody: the idea of owning a valuable and transferable asset by only holding a private key was not possible prior to Bitcoin. The closest comparison might be a domain name: people feel like they own those, but they are just renting them from a registrar who leases you the account and ability to edit your domain records. This applies all over Ethereum, DeFi, ENS, NFTs. Look at Aave, that allows lending and borrowing without a custodial service provider.
derefr 4y ago
For one small example: enabling this https://docs.ipfs.tech/ https://docs.ipfs.tech/ website, to be delivered to your browser care of a (replaceable commodity) gateway node that fetches assets by URL-embedded content-hash from an open-membership DHT. (If you're wondering how this website appears on its own domain rather than you needing to directly visit the domain of the gateway node, that's because of https://docs.ipfs.tech/concepts/dnslink/ https://docs.ipfs.tech/concepts/dnslink/).
- andsoitis 4y ago
  Can you reframe that in terms of end user benefit?
  - derefr 4y ago
    Site will never go down; data backing the site will never be lost; content-addressability of data means data is guaranteed to be the same data that was intended to be published, with no ability for e.g. a state-actor to tell Amazon to modify what's in the S3 bucket. In other words: if someone could figure out how to host ThePirateBay on IPFS, then governments wouldn't be able to take them down any more. They'd only be able to take down arbitrary IPFS gateway nodes; and if they did that enough to be a problem, anyone who cared could work around that by just running their own IPFS node. (Or using a browser like Brave which runs its own IPFS node internally.) Content will be fetched from by DNSLink-aware browsers in preference to hitting the gateway specified in the DNSLink record, so as soon as you used such a browser, all the taken-down domains would just magically work again for you.
    - n3t 4y ago
      > data backing the site will never be lost Data can be lost. I put a few files on IPFS some time ago. That files are no longer accessible because I stopped hosting them. > Site will never go down As long as there is a node hosting the data you're looking for. So it can go down.
      - derefr 4y ago