IPFS Project Roadmap
github.com
IPFS Project Roadmap
1–10 of 154 posts
Re: IPFS Project Roadmap
#2Would love to see Arch/Alpine Linux repo move to IPFS by default. Would also like to see better integration with Git, and an SCM platform comparable to GitHub (or GitLab). That could really get the developer community heavily involved in the project if it was sponsored by Protocol Labs.
Re: IPFS Project Roadmap
#3It's nice to see #2 for package managers, something I've been thinking about recently. I haven't look much into this yet, but I wonder if IPNS could provide a step forward in supply chain protection since package signing isn't available yet in certain managers/repos or not commonly utilized.
Re: IPFS Project Roadmap
#4The vision of a IPFS-powered web working is beautiful.
However I would love to see a reference implementation that works at minimum and not just drains out your computer up to latest resource it may have. If we're so near the "production-ready" status of the reference implementations then I think that goal will never be achieved.
Re: IPFS Project Roadmap
#5The vision of a IPFS-powered web working is beautiful. However I would love to see a reference implementation that works at minimum and not just drains out your computer up to latest resource it may have. If we're so near the "production-ready" status of the reference implementations then I think that goal will never be achieved.
That's what's got me excited - they've managed to articulate a vision for the future that I'm totally on board with: decentralized, privacy respecting, and user owned. I really want to see that vision become a reality.
Re: IPFS Project Roadmap
#6The vision of a IPFS-powered web working is beautiful. However I would love to see a reference implementation that works at minimum and not just drains out your computer up to latest resource it may have. If we're so near the "production-ready" status of the reference implementations then I think that goal will never be achieved.
I see this comment often when IPFS is discussed - but the devil is in the details when it comes to replacing the underlying tech of "the web" with something else.
How does an IPFS powered website do dynamic content? User sessions? Is all the client's session data encoded in the IPFS address itself?
Even if there's no user sessions, but the page content updates, how do you continuously point clients to fetch the right updated page (e.g. how would you implement a Hacker News style aggregator that updates every minute)?
IPFS does static content just fine - CAS-es are wonderful for that - but websites are much more than static content.
Re: IPFS Project Roadmap
#7The vision of a IPFS-powered web working is beautiful. However I would love to see a reference implementation that works at minimum and not just drains out your computer up to latest resource it may have. If we're so near the "production-ready" status of the reference implementations then I think that goal will never be achieved.
I see this comment often when IPFS is discussed - but the devil is in the details when it comes to replacing the underlying tech of "the web" with something else. How does an IPFS powered website do dynamic content? User sessions? Is all the client's session data encoded in the IPFS address itself? Even if there's no user sessions, but the page content updates, how do you continuously point clients to fetch the right…
Dynamic content is not the problem. I don't want dynamic content. I think HTTP and servers are the way to go on dynamic content. I just tried, for years, to use IPFS as a way to distribute static content (you know, stuff that will never ever change, even if that stuff is referenced from a dynamic location), and the problems I encountered were so many I finally gave up.
I would love to see all these problems solved and IPFS working very well in the next few years, but I'm afraid the IPFS people are very good in making press releases and presentations, but not in delivering really good software as they say they do.
Anyway, they have no obligation to deliver anything to anyone -- except maybe the people who entered the Filecoin ICO.
Re: IPFS Project Roadmap
#8This is exciting. I would love to make it to the 1st IPFS Camp in June.
Re: IPFS Project Roadmap
#9Earlier quoted context omitted.
I see this comment often when IPFS is discussed - but the devil is in the details when it comes to replacing the underlying tech of "the web" with something else. How does an IPFS powered website do dynamic content? User sessions? Is all the client's session data encoded in the IPFS address itself? Even if there's no user sessions, but the page content updates, how do you continuously point clients to fetch the right…
Dynamic content is not the problem. I don't want dynamic content. I think HTTP and servers are the way to go on dynamic content. I just tried, for years, to use IPFS as a way to distribute static content (you know, stuff that will never ever change, even if that stuff is referenced from a dynamic location), and the problems I encountered were so many I finally gave up. I would love to see all these problems solved an…
If you want IPFS to be a replacement technology for the web, you need dynamic content. Else, it's a useful static content distribution network, but it's not "the web", not even in the sense of what the web was in the 90s, or the "web" any more than Bittorrent is.
Now, obviously, they're under no obligation to deliver anything. But I'm trying to understand what you mean when you say:
The vision of a IPFS-powered web working is beautiful
Re: IPFS Project Roadmap
#10Earlier quoted context omitted.
Dynamic content is not the problem. I don't want dynamic content. I think HTTP and servers are the way to go on dynamic content. I just tried, for years, to use IPFS as a way to distribute static content (you know, stuff that will never ever change, even if that stuff is referenced from a dynamic location), and the problems I encountered were so many I finally gave up. I would love to see all these problems solved an…
If you want IPFS to be a replacement technology for the web, you need dynamic content. Else, it's a useful static content distribution network, but it's not "the web", not even in the sense of what the web was in the 90s, or the "web" any more than Bittorrent is. Now, obviously, they're under no obligation to deliver anything. But I'm trying to understand what you mean when you say: The vision of a IPFS-powered web w…
I'm under the impression that the original comment was referring to an IPFS-powered web, rather than the web being powered by IPFS. Good ol' HTTP servers will continue to form the web as we know it, and IPFS can provide a new web of static content.