4 ms·

An example of such a thing is the Libgen search interface hosted on IPFS (both data as well as webapp). If you have a means to directly navigate IPFS (that is,

An example of such a thing is the Libgen search interface hosted on IPFS (both data as well as webapp). If you have a means to directly navigate IPFS (that is, without using a proxy) it can be found here: ipns://libgen.crypto/ If you do not yet have this set up the same thing can be reached through a proxy, e.g.: https://libgen-crypto.ipns.dweb.link/ https://libgen-crypto.ipns.dweb.link/ The former (pure IPFS/IPNS) link is resistant to censorship as long as access to IPFS is available. The latter can of course be censored but once IPFS becomes mainstream the need for such proxies will disappear. More on this project can be found here: https://libgen.fun/dweb.html https://libgen.fun/dweb.html

BrianOnHN 5y ago
> If you have a means to directly navigate IPFS (that is, without using a proxy) What's the requirement for this? Like, is this a me (local config) or them (ISP connection) issue?
- hagbard_c 5y ago
  You need access to the internet, that's about it. IPFS can use any transport protocol (see section 3.2 in the whitepaper [1]), it uses a distributed hash table for routing purposes, content addressing to represent objects - these are immutable, once published they're available as long as there is a peer which has the object in cache or 'pinned' (permanently cached). Read the whitepaper and install [2] a node of your own to get a feel of the thing, you'll soon find out it is an amalgamation of earlier peer to peer systems. The go-ipfs daemon tends to be quite busy, it averages somewhere around 30% CPU, 500MB memory, 0.1Mb/s in, 0.04Mb/s out when hosting ~3GB of (self-generated, niche-interest, database-related) files. This busyness is acknowledged by the developers and should be addressed somewhere down the line. [1] https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-p2p-file-system.pdf https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-... [2] https://dist.ipfs.io/ https://dist.ipfs.io/ (get go-ipfs)
  - capableweb 5y ago
    > IPFS can use any transport protocol (see section 3.2 in the whitepaper [1]), In theory. In practice, the network (I checked my local node with ~2500 nodes connected to it) is mostly using quic over tcp/udp, more or less 50%/50% split between tcp/udp. > This busyness is acknowledged by the developers and should be addressed somewhere down the line. IPFS has been killing routers[https://github.com/ipfs/go-ipfs/issues/3320 https://github.com/ipfs/go-ipfs/issues/3320] and sending/receiving lots of network traffic[https://github.com/ipfs/go-ipfs/issues/2917 https://github.com/ipfs/go-ipfs/issues/2917] since 2016 and there hasn't been any notable improvements on that front yet. When is "down the line" in reality?
    - hagbard_c 5y ago
      The "router kill" problem is a problem with those routers, not with IPFS, or any other chatty program for that matter. That said, IPFS is chatty and as such not something you'd run on a dial-up line. ADSL 4/1 or higher would be fine though, as long as you get a router which can take the load - just find something that can run OpenWRT and has enough memory and you're set. Of course you don't need to run IPFS to get at IPFS-hosted content, there are plenty of gateways out there (one of them hosted by Cloudflare). Run your own node if you want to have full control over the path between IPFS and your instances, if you want to contribute to the decentralisation of the 'net or if you just like to tinker.
      - capableweb 5y ago
        > The "router kill" problem is a problem with those routers, not with IPFS, or any other chatty program for that matter. It's really hard to be convinced by that argument when go-ipfs is the only software that manages to kill peoples router until people reboot the router, when literally every other piece of software they use work perfectly, even when using bittorrent and other data-heavy protocols.
        e12e 5y ago
        Kill routers quickly. I've had to reboot various routers over the years when the buffers tracking states grow full (typically sharing a flat with friends where everyone runs torrent, direct connect or similar).
Scoundreller 5y ago
> ipns Please tell me this is a (Freudian?) typo.
- capableweb 5y ago
  IPNS - InterPlanetary Name System
- hagbard_c 5y ago
  InterPlanetary Name System (IPNS) IPFS uses content-based addressing; it creates an address of a file based on data contained within the file. If you were to share an IPFS address such as /ipfs/QmbezGequPwcsWo8UL4wDF6a8hYwM1hmbzYv2mnKkEWaUp with someone, you would need to give the person a new link every time you update the content. The InterPlanetary Name System (IPNS) solves this issue by creating an address that can be updated. https://docs.ipfs.io/concepts/ipns/ https://docs.ipfs.io/concepts/ipns/
- musicale 5y ago
  IPNS, not to be confused with NIPS or PNAS. https://nips.cc/ https://nips.cc/ https://www.pnas.org/ https://www.pnas.org/

BrianOnHN 5y ago

> If you have a means to directly navigate IPFS (that is, without using a proxy) What's the requirement for this? Like, is this a me (local config) or them (ISP connection) issue?

hagbard_c 5y ago
You need access to the internet, that's about it. IPFS can use any transport protocol (see section 3.2 in the whitepaper [1]), it uses a distributed hash table for routing purposes, content addressing to represent objects - these are immutable, once published they're available as long as there is a peer which has the object in cache or 'pinned' (permanently cached). Read the whitepaper and install [2] a node of your own to get a feel of the thing, you'll soon find out it is an amalgamation of earlier peer to peer systems. The go-ipfs daemon tends to be quite busy, it averages somewhere around 30% CPU, 500MB memory, 0.1Mb/s in, 0.04Mb/s out when hosting ~3GB of (self-generated, niche-interest, database-related) files. This busyness is acknowledged by the developers and should be addressed somewhere down the line. [1] https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-p2p-file-system.pdf https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-... [2] https://dist.ipfs.io/ https://dist.ipfs.io/ (get go-ipfs)
- capableweb 5y ago
  > IPFS can use any transport protocol (see section 3.2 in the whitepaper [1]), In theory. In practice, the network (I checked my local node with ~2500 nodes connected to it) is mostly using quic over tcp/udp, more or less 50%/50% split between tcp/udp. > This busyness is acknowledged by the developers and should be addressed somewhere down the line. IPFS has been killing routers[https://github.com/ipfs/go-ipfs/issues/3320 https://github.com/ipfs/go-ipfs/issues/3320] and sending/receiving lots of network traffic[https://github.com/ipfs/go-ipfs/issues/2917 https://github.com/ipfs/go-ipfs/issues/2917] since 2016 and there hasn't been any notable improvements on that front yet. When is "down the line" in reality?
  - hagbard_c 5y ago
    The "router kill" problem is a problem with those routers, not with IPFS, or any other chatty program for that matter. That said, IPFS is chatty and as such not something you'd run on a dial-up line. ADSL 4/1 or higher would be fine though, as long as you get a router which can take the load - just find something that can run OpenWRT and has enough memory and you're set. Of course you don't need to run IPFS to get at IPFS-hosted content, there are plenty of gateways out there (one of them hosted by Cloudflare). Run your own node if you want to have full control over the path between IPFS and your instances, if you want to contribute to the decentralisation of the 'net or if you just like to tinker.
    - capableweb 5y ago
      > The "router kill" problem is a problem with those routers, not with IPFS, or any other chatty program for that matter. It's really hard to be convinced by that argument when go-ipfs is the only software that manages to kill peoples router until people reboot the router, when literally every other piece of software they use work perfectly, even when using bittorrent and other data-heavy protocols.
      - e12e 5y ago
        Kill routers quickly. I've had to reboot various routers over the years when the buffers tracking states grow full (typically sharing a flat with friends where everyone runs torrent, direct connect or similar).

Scoundreller 5y ago

> ipns Please tell me this is a (Freudian?) typo.

capableweb 5y ago
IPNS - InterPlanetary Name System
hagbard_c 5y ago
InterPlanetary Name System (IPNS) IPFS uses content-based addressing; it creates an address of a file based on data contained within the file. If you were to share an IPFS address such as /ipfs/QmbezGequPwcsWo8UL4wDF6a8hYwM1hmbzYv2mnKkEWaUp with someone, you would need to give the person a new link every time you update the content. The InterPlanetary Name System (IPNS) solves this issue by creating an address that can be updated. https://docs.ipfs.io/concepts/ipns/ https://docs.ipfs.io/concepts/ipns/
musicale 5y ago
IPNS, not to be confused with NIPS or PNAS. https://nips.cc/ https://nips.cc/ https://www.pnas.org/ https://www.pnas.org/