• 2 months

    no source code

    no paper

    no open protocol definition

    full of emojis

    LMAO

    • So it makes a swarm and distributes pieces of the site all over the internet. Theoretically, the original peer can go down and the site keeps running.

      Thats not how i2p works. I2p works in a different way and solves a different problem.

      However, i2p CAN torrent so technically you could stack this technology in top of it.

    • 2 months

      Perhaps that is the point: peer auditing instead of blind forwarding

  • 2 months

    I am sorry but this is so clearly vibe coded and lazily, i would not trust the security of that thing one second…

  • 2 months

    A question: can you modify the site once it’s published?

    Because the uses for a never-changing site are quite limited.

    • 2 months

      Also, the content is statically-generated only, I guess? No server-side rendering? No POSTing, etc? Or…is this creating some cache based on a real server it contacts…?

    • Not too different vs IPFS, essentially the IPFS network if it was using WebTorrent. Both rely on swarms of p2p users/servers to seed/pin data to keep it online.

      I’m not too familiar with Veilid but that does seem different since it’s built for privacy so I doubt all the peers are public in that scenario. There is nothing private about IPFS or WebTorrent, all peer IP addresses are public in their respective swarms.

  • Might be because I’m on Ironfox maybe but it just stays on connecting to peers for me with nothing else happening. So yeah not one for me.

    • Not really. Decentralized does not mean anonymous… and I doubt people sharing that type of content are doing it publicly with their public IP addresses.

      Looks like PeerWeb uses WebTorrent - so that means every single IP address serving the website is easily found in the peer list of the torrent swarm. Nothing anonymous about this.