121–130 of 154 posts
Earlier quoted context omitted.
We conducted initial experiments with moving nix package manager to ipfs, but also ran into too many issues.
Are these issues documented somewhere, would love to learn more. At first glance nix and ipfs seem like a perfect match
"2019 Goal: The most used code and binary Package Managers are powered by IPFS." That's kind of stupid-ambitious for 2019 when another 2019 goal is "a production-ready implementation" and IPFS has been around for 3 years already. This isn't a roadmap, it's a wishlist. And I'm someone who wants to see IPFS succeed.
I would love to see IPFS used in projects like Nix, but in the current state it's downright impossibile. I have seen IPNS taking between 5-10 minutes to solve a single address and go-ipfs with a few pinned files taking more that 5GB of memory after running for a day.
Yeah, I don't understand the hype around IPFS when it performs so badly. After reporting the issue and having a conversation with the devs I had an impression that they are just dilettantes.
Earlier quoted context omitted.
One practical difference is that all the parts of a "collection" are individually addressable in IPFS. For example, unlike torrents, you can seed a collection like "My Web Show (All Seasons)" and add new files as new episodes become available. With torrents, you have to repackage them as new torrent files. IPFS also then encourages file canonicalization instead of everyone seeding their own copy of a file.
This is a over simplification I think. In IPFS to add a file to a folder, you need to rebuild that folder which changes the address. You still need to get people to access the new address to see any updates. IPNS makes that fairly easy, but a similar technology could be made for bittorrent. I think what makes IPFS interesting is that all files are like torrents and all folders all like torrents of torrents. And since…
This is not a roadmap, but rather a wishlist. There is a fundamental problem that IPFS needs to solve first. This problem is called an efficient WebRTC-based DHT. In order to change the web, IPFS needs to become usable in the browsers. Since the backbone of IPFS is DHT, there need to be an efficient UDP-based solution for "DHT in the web". Right now this isn't possible and reasons are not just technical, but politica…
I actually wrote a DHT that operated over WebRTC itself with in-band signalling for my undergrad thesis, in the application/js layer. Total PITA, but a ... "good?" learning experience.
Earlier quoted context omitted.
For dynamic data, you need to use a CRDT system like GUN ( https://github.com/amark/gun ). For instance, see P2P Reddit ( http://notabug.io ) which: - Running in production with GUN. - Handling about 42,000 monthly visitors. ( https://www.similarweb.com/website/notabug.io ) - Has done ~1TB in 1 day of decentralized traffic. You can then configure GUN to save to IPFS as the blob/storage engine (or we have filesystem,…
It's a shame that so many P2P advocates - or at least the ones using the stuff built with P2P tech - are very loud alt-right types. I popped on notabug.io just now, and the chat is full of swastikas, racial slurs, and the most up-voted posts are primarily anti-gay misinformation. I see you wrote GUN, which I'm sure was no small feat, and it looks like an impressive piece of technology. How do you feel about your tech…
The guy actually built a P2P moderation tool (anyone has their own "glasses" that filters based on your policy).
notabug.io is suppose to be running a curated homepage (nab.cx not curated) but I think he said it broke a week ago when he was modularizing his code.
NAB usually isn't this bad, lot of the people on it are anti-altright, but altrighters certainly can drown them out.
But it does look like NAB has become more toxic over time. :(
Previously, I was pretty neutral "do what you want with it".
Now, I shifted to be more opinionated about what I want to see built on top.
Primarily, apps that spread Open Source economics through art (music, etc.), to draw a crowd of lovers/creators not haters/destroyers.
Earlier quoted context omitted.
it is already here! If you use a mix of SSB, GUN, DAT, IPFS, & WebTorrent. SSB = Social-like P2P data. GUN = Firebase-like P2P data. SEA = End-to-end encryption. ( https://gun.eco/docs/SEA ) DAT = GIT-like P2P data. IPFS = Images/assets. WebTorrent = Video-like P2P data.
Are there example applications with some complexity on GUN?
Only saw your comment now, will reply on Twitter too - long time no see since #hashtheplanet !
Earlier quoted context omitted.
I actually wrote a DHT that operated over WebRTC itself with in-band signalling for my undergrad thesis, in the application/js layer. Total PITA, but a ... "good?" learning experience.
any links, please?
Earlier quoted context omitted.
Are there example applications with some complexity on GUN?
Yes, D.Tube, The Internet Archive, Notabug.io (warning: its getting spammed by altrighters currently), etc. Only saw your comment now, will reply on Twitter too - long time no see since #hashtheplanet !
Earlier quoted context omitted.
Yes, D.Tube, The Internet Archive, Notabug.io (warning: its getting spammed by altrighters currently), etc. Only saw your comment now, will reply on Twitter too - long time no see since #hashtheplanet !
It would be great to get case studies with some information on how they use the platform into the docs. GUN sounds reasonable from the description but it is really difficult to visualize using it in a larger app.
Notabug basically does everything Reddit does + more. Would that qualify as a larger app?
What in particular, what do you think would be difficult?
This is not a roadmap, but rather a wishlist. There is a fundamental problem that IPFS needs to solve first. This problem is called an efficient WebRTC-based DHT. In order to change the web, IPFS needs to become usable in the browsers. Since the backbone of IPFS is DHT, there need to be an efficient UDP-based solution for "DHT in the web". Right now this isn't possible and reasons are not just technical, but politica…