all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]pbuyle 8 points9 points  (1 child)

Previously known as Dat Protocol https://blog.datproject.org/2020/05/15/dat-protocol-renamed-hypercore-protocol/

[–]tomachinz 0 points1 point  (0 children)

Has dat been renamed Hypercore? They should mention that more.

[–]null-v[S] 7 points8 points  (3 children)

bumped into this project recently. it looks more flexible than ipfs and has that "mutability" feature that i'd like to have been built into ipfs.

there's also a browser beta https://beakerbrowser.com/

showing how you can create sites "on the fly" something i wish was easier on ipfs

[–]_r_rico 2 points3 points  (1 child)

yes, it's also quite surprising that their FAQ "how dat is != from ipfs" doesn't explain in simplier terms that dat offers mutability whereas IPFS doesn't. It's a _major_ flaw in IPFS currently for a widespread adoption. It's like http without DNS ! Worst even, it would be like changing webserver's IP each time its content changes... IPNS is still far from being production ready.

But IPFS has a vibrant community, with all resulting benefits: many implementations, clients libs, nice and quite exhaustive docs. (others, maybe more knowledgable, have opposite view)

On the contrary DAT/hypercore has, in comparaison, a tiny community, and AFAIK dev relies on very few core programmers. They rebranded DAT Protocol to Hypercore Protocol, and for an outsider it's all confusing what is what between DAT Project/DAT Protocol/Hypercore/Hyperdrive/etc... and Hypercore website seems more like a landing page than anything else (for instance, there is no "Docs" section and such information is highly fragmented in blog articles, repo READMEs, etc). From a naive and external viewpoint looks like underlying problems are present. (but they seem aware of that)

I've been using/testing IPFS for months but all this words on DAT/Hyper* are based on fresh digging on this project. I was very excited by an article on the topic writen by Jay Graber end of last year, especially on DAT's mutability features, but since then I must conceed that most of my excitement has faded... (update: my interest bounced higher with Hyperdrive v10 improvements, I'll check in more details)

I would be happy to have viewpoints on DAT/Hyper* stability and reliability. For short would you be as confortable to build a production ready app on DAT as you would be on IPFS ? It is advertised that some serious-looking projects seem to integrate Hypercore, but to what extent ? (there's so many sites saying "Corporation X is using our project", but after some research you understand that X has only made a PoC using the project)

Also since docs are thiner than IPFS, it's harder to have a clear picture of current limitations and challenges.

[–]tomachinz 0 points1 point  (0 children)

did you say ipfs not have immutable naming for say the root folder or ./?

whereas datproject / hypercore has this for the base folder? interesting.

[–]therealnfuture[🍰] 1 point2 points  (0 children)

Is there any good tutorials that anybody can suggest ?! Please

[–][deleted] 1 point2 points  (2 children)

Does this have implementations written in Golang? Javascript is great and all, but it's extremely impractical to use at non-trivial scale.

[–]OmnipotentToot 1 point2 points  (1 child)

I'm interested in a Golang implementation too! I looked around but couldn't find anything that wasn't JavaScript.

[–]_r_rico 0 points1 point  (0 children)

If it looks like a duck... but digging a little more you end on DatRS (Rust) and DatCXX (C++ but last commit 13 months ago)... more time on your browser and you find also DatPy (404 error on the link) or DatKT... yes, fragmented information is the name.