_prometheus

9 ms·

1. 61.▲
   by _prometheus 11y ago

   (IPFS dev here) +1 o/ NDN is awesome. If any NDN devs see this, please reach out. We'd love to work with NDN on things-- we think we can generate lots of demand for NDN
2. 62.▲
   by _prometheus 11y ago

   Thanks mark! gun is really cool! Would love to talk about it, actually. I'd love to make gun a transport for IPFS objects, and viceversa. send me an email! Also, IPFS works today too, https://ipfs.io is served directly via
3. 63.▲
   by _prometheus 11y ago

   (IPFS Dev) Thanks! :) Yeah, we want to help sites scale without needing massive infrastructure funding.
4. 64.▲
   by _prometheus 11y ago

   Thanks! and please do-- find us on github.com/ipfs/ and #ipfs on irc.freenode.org :)
5. 65.▲
   by _prometheus 11y ago

   (IPFS Dev here) Maybe. I want to live in a web where, (1) if a region's network uplink disconnected (like it was in Egypt) websites/webapps don't cease to work. People should be able to communicate + compute in these local ne
6. 66.▲
   by _prometheus 11y ago

   (IPFS Dev) Duly noted! will do! :)
7. 67.▲
   by _prometheus 11y ago

   (IPFS Dev here) Sort of, actually. The gist is that in general yes, the network is growing and getting better. But, there's actually a growing divide between the hyper-developed cities and ... the rest of the world. One example is this
8. 68.▲
   by _prometheus 11y ago

   (IPFS Dev) Sure! We divide naming in two parts: (1) Providing a long-term reliable mutable pointer. (no consensus needed) (2) Providing a long-term reliable short and human-readable identifier. (consensus needed) Where "long-term relia
9. 69.▲
   by _prometheus 11y ago

   (IPFS Dev) Yes yes yes yes! :) This is very much what we're going for. Glad you mention semantic web-- it tends to be a very tricky word with most hacker cultures, because everyone loves to hate on failed attempts :( :( -- but in fact
10. 70.▲
    by _prometheus 11y ago

    (IPFS Dev) Yeah, we have many similarities with Freenet, but we also have significant differences. You mention the lack of anonymity, and yep, that's definitely one -- to speak more about this: this parts from our content model. Among
11. 71.▲
    by _prometheus 11y ago

    (IPFS dev here) Hey! Yeah, we're focusing right now on "distributed static websites" because those are really easy to get right and make work all over the network. However, what's _really_ interesting about IPFS is makin
12. 72.▲
    by _prometheus 11y ago

    (IPFS dev) Yes! One of my explicit goals is to help get to Alan Kay's "one address for each object" goal.
13. 73.▲
    by _prometheus 11y ago

    (IPFS dev here) I think subresource integrity is an _awesome_ thing that needs to be implemented and spread all over asap. (Actually, if you work on this, please ping us! we'd love to help!) However, this is very far from "many of
14. 74.▲
    by _prometheus 11y ago

    (IPFS Dev here) hey again tptacek! o/ > I'm not clear on how IPFS protects applications from DDOS. Systems like IPFS spread the load of delivering content, but applications themselves are intrinsically centralized. Think about
15. 75.▲
    by _prometheus 11y ago

    (IPFS dev here) I think she does, but perhaps the discrepancy may be that she's got a different target audience: the established website owners? Also to be fair, there's not much space in these sorts of articles LOTS gets cut
16. 76.▲
    by _prometheus 11y ago

    (IPFS dev here) "questionable bile"? we'd love your technical feedback. We know we have a ton of things to do better -- but what sort of things are you thinking about? what can we improve on?
17. 77.▲
    by _prometheus 11y ago

    (IPFS author here) You're hitting on some really hard questions :) the gist is that you use a "record system" that has some transport guarantees, for example relying on a dht has certain kind of properties, as opposed to rely
18. 78.▲
    by _prometheus 11y ago

    Yes. (IPFS author here) 1. Add a TXT record to DNS <domain> with: dnslink="/ipns/QmWGb7PZmLb1TwsMkE1b8jVK4LGceMYMsWaSmviSucWPGG" 2. should be able to use https://ipfs.io/ipns/<domain
19. 79.▲
    by _prometheus 11y ago

    see also: https://github.com/cryptix/git-remote-ipfs
20. 80.▲
    by _prometheus 11y ago

    the caveat of course being that SHA256 may be _broken_. That's when we'd have to upgrade to another hash function. (We may improve how this upgrade will work down the road by allowing links to link with multiple hashes at the same
21. 81.▲
    by _prometheus 11y ago

    this is why we use multihash -- https://github.com/jbenet/multihash
22. 82.▲
    by _prometheus 11y ago

    Check out another protocol we (the IPFS creators) are working on: http://filecoin.io
23. 83.▲
    by _prometheus 11y ago

    Two pieces of (coming soon) good news: - very soon, you wont need to install anything to use IPFS. it will "just work" with js on today's browsers. - for best perf, yes, we need browser implementations. and... those have begu
24. 84.▲
    by _prometheus 11y ago

    Thanks for the kind words. :) Come join us! https://github.com/ipfs/
25. 85.▲
    by _prometheus 11y ago

    Thanks! Help us make it :) -- https://github.com/ipfs/ and, you'll love what we have coming. Soon, you won't need to install ipfs at all :D
26. 86.▲
    by _prometheus 11y ago

    IPFS is designed with mutability in mind-- think of it like git branches which advance to newer versions. (though you can indeed get rid of version history in that pointer if you want). So, the short answer is "yes, IPFS will work with
27. 87.▲
    by _prometheus 11y ago

    Yep! entirely agreed.
28. 88.▲
    by _prometheus 11y ago

    though it may sounds similar, it's very, very different. take a deeper look at the demo on http://ipfs.io
29. 89.▲
    by _prometheus 11y ago

    > I suspect that there's a way to identify the latest content built into IPFS Yeah-- the IPNS records have a notion of recency, as well as being able to write version history datastructures (e.g. git)
30. 90.▲
    by _prometheus 11y ago

    Thank you for taking the time to write this explanation :)