Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How We Made IPFS Content Publishing 10x Faster

probelab.io

Post reply on HN
Print view View original

61–69 of 69 posts

Re: How We Made IPFS Content Publishing 10x Faster

#61

Post by RobotToaster »

msm_ wrote: post #49
RobotToaster wrote: post #34

Earlier quoted context omitted.

Suddenly it looks a lot less decentralised.

I don't know, it looks pretty decentralised to me? >The purpose of this list is to allow IPFS node operators (e.g. someone running a public IPFS gateway) to opt into not hosting previously flagged content. IPFS node operators, who are supposedly interested in hosting malicious content (and i2p-hosted phishings are a real problem) can OPT INTO using this list. In this case, I don't see how that's any problem for pirac…

The fact that it's entirely binary, and they don't separate someone copying books from malware isn't helping that argument.

Re: How We Made IPFS Content Publishing 10x Faster

#62

Post by anacrolix »

boramalper wrote: post #58
Gigachad wrote: post #44

Earlier quoted context omitted.

Couldn't you also just build a bittorrent client that hosts a local webserver to provide http access? I could never get what IPFS actually did that bittorrent didn't.

> Couldn't you also just build a bittorrent client that hosts a local webserver to provide http access? And this does exist! See confluence by anacrolix: https://github.com/anacrolix/confluence

And also https://github.com/anacrolix/btlink :)

Re: How We Made IPFS Content Publishing 10x Faster

#63

Post by Borg3 »

dannyobrien wrote: post #40
boramalper wrote: post #31

Earlier quoted context omitted.

I think the biggest sin of IPFS is not working natively in web browsers—instead, requiring the use of either HTTP gateways or native apps running outside the browser.

Actually, this works now! https://inbrowser.link/ https://github.com/ipfs/service-worker-gateway -- getting p2p working in browsers is still surprisingly hard: even the official routes like webrtc have lots of hard edge cases.

Comment there made me chuckle..: serving only small static HTML+JS files (sigh So entire IPFS + IPFS Gateway needs to be so huge? 10MB? My dot.exe (DVFS repo manager) is 150kB..

Re: How We Made IPFS Content Publishing 10x Faster

#64

Post by preisschild »

phae wrote: post #51
boramalper wrote: post #12

Is anyone still (or has anyone ever) used IPFS in production? I’m not talking about technology demos such as Wikipedia-on-IPFS (which indeed worked and was impressive) but where IPFS is actually being relied on for some functionality.

the thing that prevented me using ipfs in anger.. (granted i may not have looked hard enough) was that i couldn't have stuff in ipfs, and access it via posix filesystem at he same time. i'd have to store things twice. fine for publishing, but not for having a live data set that is both used and published at the same time, as you can do with torrent.

> was that i couldn't have stuff in ipfs, and access it via posix filesystem at he same time.

Maybe this is possible to implement using fuse/9p fs

Re: How We Made IPFS Content Publishing 10x Faster

#65

Post by frollogaston »

benatkin wrote: post #36
boramalper wrote: post #19

Earlier quoted context omitted.

I don’t think NFTs (should) count: My first impressions of web3 by Moxie Marlinspike https://moxie.org/2022/01/07/web3-first-impressions.html

Moxie doesn't trash NFTs or Web3 in that article. He just points out some limitations of the ecosystem. Also, ipfs directly fixes one of the bigger issues: > Instead of storing the data on-chain, NFTs instead contain a URL that points to the data. If it's ipfs, it points to the content. If it's ipns, it points to a changeable link to the content, but one that is made consistent through the network, preventing the tri…

I still don't count it because NFTs have seemingly died off in popularity. If there were tons of money staying in NFTs, regardless of how silly I think it is, I'd consider that an important use case of IPFS.

Re: How We Made IPFS Content Publishing 10x Faster

#66

Post by benatkin »

frollogaston wrote: post #65
benatkin wrote: post #36

Earlier quoted context omitted.

Moxie doesn't trash NFTs or Web3 in that article. He just points out some limitations of the ecosystem. Also, ipfs directly fixes one of the bigger issues: > Instead of storing the data on-chain, NFTs instead contain a URL that points to the data. If it's ipfs, it points to the content. If it's ipns, it points to a changeable link to the content, but one that is made consistent through the network, preventing the tri…

I still don't count it because NFTs have seemingly died off in popularity. If there were tons of money staying in NFTs, regardless of how silly I think it is, I'd consider that an important use case of IPFS.

I don't think it matters if it's silly. I think it's highly successful, and that the success is continued. CryptoPunks is a clear example of genuine use of NFTs that still is an elite thing today, but another example is needed. I'll use this: if you go to Bored Apes and sort by recently sold, and look through them, you can see that there would have to be a lot of manipulation to have them rated in quality like they are. It just isn't plausible to me that a huge amount of those are self-dealing. If people were self-dealing, there would be a bunch of less cool ones with high prices, in order to try and get people to pay more for them. https://opensea.io/collection/boredapeyachtclub?sortDirectio...

Re: How We Made IPFS Content Publishing 10x Faster

#67

Post by ydj »

boramalper wrote: post #32
ydj wrote: post #26

Earlier quoted context omitted.

At meta, there was a project for delivering binaries of internally built libraries / binaries to dev laptops using a private ipfs network. This was live for at least some period of time.

Very interesting! I wonder if it’s still live and there is any writing on it?

Not sure, there was a lot of complaints when it rolled out because it was actually peer to peer syncing to other laptops which was causing bandwidth issues for people working on vpn, from planes etc.

I’m not sure if it was actually a well thought out idea, since it’s not like fb has a lack of servers or bandwidth, but I didn’t work on it, so I don’t want to throw too much shade at it.

Re: How We Made IPFS Content Publishing 10x Faster

#69

Post by yangm97 »

hannesfur wrote: post #23

Having worked on libp2p‘s DHT (Double Hashing for rust-libp2p) for a bit two years ago, it’s really great to see that there are improvements. To get to CDN level speeds though on dense networks, I still see it as an architectural flaw to not somehow encode network topology into the PeerID / identity in the DHT. A start would be to use the five RIRs. If you want to be more sophisticated, and I spent a lot of time theo…

We shouldn’t expect bodies and companies that benefit from centralization to give us crumbs. Remember IPv6 global multicast? ISPs killed that on sight.

We need to get encrypted mesh networking (Yggdrasil, CJDNS, FIPS etc) out there before it’s too late.

Post reply on HN