_prometheus

7 ms·

1.
by _prometheus 6y ago
awesome! :)
2.
Building Web3: Textile – dev tools that return data ownership to users(youtube.com)
2 points by _prometheus 6y ago|0 comments
3.
by _prometheus 6y ago
This is great! SOOO useful to be able to do mounts w/o fuse, w/o kernel extension, w/o root. This is a HUGE UX thing, specially for macs. Fuse is a really great idea & project, but sadly today impls require a lot of insta
4.
Opera Android adds IPFS, ENS, and .crypto support by default(blog.ipfs.io)
2 points by _prometheus 6y ago|0 comments
5.
by _prometheus 7y ago
Datasaur looks awesome! Can't wait to try it out. Congrats on the launch! Curious about data security and privacy? How do you guarantee privacy? Is there some cryptography or secure enclaves used? Some sets of documents (and email) are
6.
by _prometheus 7y ago
Hello! o/ We've responded to a number of points here. You can check out our roadmap > IPFS is unworkable... making it usable in the next few years Absolutely not. The OP brings up a lot of great, useful feedback for us, and we&
7.
by _prometheus 7y ago
Decentralizing how we link, address, and move content is the basis of IPFS and Filecoin both. Both are solving different parts of moving our digital infrastructure to infrastructure that we control, that we govern, and that we are not held
8.
by _prometheus 7y ago
Exactly. P2P systems historically have dealt with the problem altruistically, or with limited tit-for-tat, which both work in many cases, but have so far failed to work for large scale long-term resilient systems. This is where Bitcoin mana
9.
by _prometheus 7y ago
This is excellent feedback! Thanks! > We even created a plugin ( https://github.com/almonit/almonit-plugin - unreleased officially yet!) for websites that combine IPFS with ENS (a decentralized DNS). This is great!
10.
Timelapse of the Future: A Journey to the End of Time (Melodysheep)(youtube.com)
2 points by _prometheus 7y ago|0 comments
11.
Quantifying the value of excellent explainers(twitter.com)
1 points by _prometheus 9y ago|0 comments
12.
by _prometheus 9y ago
Hey HN, this is jbenet -- an author of Filecoin. We think it's great that people ask hard questions, and get involved. It's great to see others studying our work and we really appreciate the open discourse. There are a few things
13.
by _prometheus 9y ago
It's coming shortly (days), it's a WIP that needs significant polish, but the core result is there.
14.
by _prometheus 9y ago
Thanks Craig and YC. Ton of fun.
15.
by _prometheus 9y ago
That's precisely one of the innovations in the new Filecoin paper :) -- we call it Proof-of-Replication. Papers coming soon.
16.
Protocol Labs – Research, Development, and Deployment(protocol.ai)
4 points by _prometheus 9y ago|0 comments
17.
Protocol Labs – Creating New Networks(protocol.ai)
5 points by _prometheus 9y ago|0 comments
18.
by _prometheus 9y ago
There are people in turkey replicating this snapshot right now. people browsing locally get it there. Even if all connections to outside the country get shut down it can be distributed locally.
19.
by _prometheus 10y ago
the table is so small you don't actually need to decode varints. any serious application needing speed would build a lookup table for all the common values -- in fact we will. size does matter. speed does matter.
20.
by _prometheus 10y ago
sounds interesting. we're definitely interested in figuring out ways for these protocols and formats to be as useful to others as they can be
21.
by _prometheus 10y ago
Yeah you're right, we've been meaning to add MD5. Filed issue: https://github.com/multiformats/multihash/issues/71
22.
by _prometheus 10y ago
yep, exactly :)
23.
by _prometheus 10y ago
See https://news.ycombinator.com/item?id=13740369 -- does that make sense? the idea is to treat those parameters as "part of the hash digest value", and write wrappers for siphash and functions like it, s.t.:
24.
by _prometheus 10y ago
@hobofan Yeah, exactly. We've explored this by making the value of such hashes (when generated and checked with multihash libs) literally be the `<hash-rounds><hash-result>` pair. This avoids complicating the table or multi
25.
by _prometheus 10y ago
Yeah this is a good point, which we discussed somewhere (not finding the issue atm). The resolution was to treat those as different hash function codes, because the normal usage of truncating hashes by chopping off bits is extremely common.
26.
by _prometheus 10y ago
Truncations happen in many sizes. The combinations here are not helpful: N functions * M commonly chosen sizes. Simple assumptions: 20 functions * 10 sizes = 200 codes. already not good. You can print a human-readable version of multihash
27.
by _prometheus 10y ago
Codes reserved for app-specific things should satisfy your concerns. coming soon: https://github.com/multiformats/multicodec/issues/39 One thing you should consider about using full names (like "sha2-256
28.
by _prometheus 10y ago
Attackers can exploit that by cutting off a stream. it's best to be explicit.
29.
by _prometheus 10y ago
That's right. It's really important to make sure there is restrictions on what hashes to use if your system is receiving hashes and only checking them for self-consistency. Particularly relevant is "Crypto Extensibility"
30.
by _prometheus 10y ago
Hey everyone. The SHAttered break made us release a new website for Multiformats: http://multiformats.io which includes a page explaining Multihash -- http://multiformats.io/multihash -- The page goes through a

More ›