101–110 of 115 posts
does anyone know why libgen is still running over http? (But sincerely thanks for the site! it saved me on several occasions!)
One of the new IPFS-backed mirror sites ( https://libgen.fun/ ) is on HTTPS.
Earlier quoted context omitted.
One of the new IPFS-backed mirror sites ( https://libgen.fun/ ) is on HTTPS.
Great, however it currently doesnt have the sci-tech filter, and no comics filter too :-(
comics is not a public dataset -- it's privately run and managed, so there are no mirrors for it. I guess someone could scrape it.
does anyone know why libgen is still running over http? (But sincerely thanks for the site! it saved me on several occasions!)
It's hard to believe, but it's certainly happened/happening -- plenty of democratic countries are filtering the internet, like Turkey.
Is LibGen safe? I remember testing some of its mirror links on virustotal and saw some red flags, so I decided not to risk downloading.
VirusTotal includes some very poor quality Chinese AVs that produce positives for nearly every file. PDFs are pretty damn safe to access today -- the days of exploding macro exploits are about a decade behind us.
Earlier quoted context omitted.
IPFS gateways are similar to Tor exit relays, they just route the traffic to the public internet. Tor exit relays still exist, and haven't been DCMAed out of existence so far. One could also imagine IPFS over Tor.
Tor exit nodes are forward proxies, they are used by the client-side to initiate connections to the public Internet but do not accept connections from the public Internet. You cannot host an Internet-facing webserver on a Tor exit (Onion Service exists solely within the Tor network), DMCA is not an issue, they do not act as a point of content distribution, there is nothing to take down. The main issue is the abusive…
Well, then we might need something like IPFS-over-Tor, using Tors anonymity features to make it more safe for operators.
Earlier quoted context omitted.
Great, however it currently doesnt have the sci-tech filter, and no comics filter too :-(
scitech is there, it's relabeled "Educational." comics is not a public dataset -- it's privately run and managed, so there are no mirrors for it. I guess someone could scrape it.
Earlier quoted context omitted.
This has been the state of IPFS for years now. The protocol and client haven't been developed to where they can work reliably in a real P2P scenario. IPFS only appears to work because most requests go strait to one of the big gateways which already has the content cached. Development of IPFS slowed to a crawl when most of Protocol Labs switched to working on Filecoin. It remains to be seen if either Filecoin or IPFS…
I'm not sure you are right about this. The following link will stream big buck bunny directly from the network with full P2P support. It is not using a gateway node for the video content. https://bbb.fu.io/ You can run the following in the console to see all your peers for await (const peer of await node.swarm.peers()) { console.log(peer.addr.toString()) } The console currently get's spammed pretty hard because they…
Earlier quoted context omitted.
Protocols don't have attitudes, everything you're using IPFS for you could also use BitTorrent for (almost). The protocols don't really care about what data you send, and no one can stop you from using them, BT or IPFS. The CoC you've linked covers the IPFS Community and other Protocol Labs initiatives, it doesn't cover usage of IPFS itself. freeread.org is not bound by that CoC.
It's more that just the protocol though. TFA links directly to the IPFS Desktop Client, which certainly can have an attitude e.g. if a future update blocks this project. That risk doesn't really exist for any mainstream torrent client.
I guess TFA is Teach for America? Doesn't really matter, but anything that is linking to IPFS Desktop could easily link to their own distribution of the client as it's all open source.
And while IPFS Desktop could start blocking content, so could torrent clients, not sure what's different really. They both are just clients for a protocol anyone can write new clients for and both have the risk of adding blocklists and having people abandon the client, so the same risks exists for both of them.
I think such materials should better be placed to darknets protecting the privacy of users and seeders, e.g., to I2P.
If you take IPFS's model and add inherent anonymity, that's exactly what Freenet is. (To this day I'm confused about why IPFS is popular while Freenet isn't.)
I'm not sure why IPFS is more popular than Freenet, but the difference mentioned above certainly makes me more likely to run a IPFS node than Freenet.