Sounds like I2P without the privacy.
post
no source code
no paper
no open protocol definition
full of emojis
LMAO
I am sorry but this is so clearly vibe coded and lazily, i would not trust the security of that thing one second...
A question: can you modify the site (edit its content etc.) once it's published?
Because the uses for a never-changing site are quite limited.
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...?
Server side rendering includes showing a list of 10 elements in a catalog of 10K elements. Do you really want to transfer all the catalog to each client every time?
Who says I'm a "web guy". It's only that a server has its uses and a client has its uses. Sending all the DB to the client is as bad as streaming an FPS from a server.
It shows deleted
How it that different from IPFS? ipfs.tech
Or even better Veilid?
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.
all 26 comments