profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/hypercore-protocol/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Hypercore Protocol hypercore-protocol Decentralised Internet https://hypercore-protocol.org A fast, scalable, and secure peer-to-peer protocol for everyone

hypercore-protocol/hypercore 1953

Hypercore is a secure, distributed append-only log.

hypercore-protocol/hyperdrive 1621

Hyperdrive is a secure, real time distributed file system

hypercore-protocol/hypertrie 296

Distributed single writer key/value store

hypercore-protocol/cli 151

A CLI for peer-to-peer file sharing using the Hypercore Protocol.

hypercore-protocol/hyperbee 151

An append-only Btree running on a Hypercore

hypercore-protocol/hyperdrive-daemon 149

Hyperdrive, batteries included.

hypercore-protocol/hyperspace 140

Hypercores, batteries included.

hypercore-protocol/hypercore-protocol 100

Stream that implements the hypercore protocol

hypercore-protocol/p2p-indexing-and-search 64

Getting started with P2P indexing and search using the Hypercore Protocol

hypercore-protocol/corestore 45

A simple corestore that wraps a random-access-storage module

startedhypercore-protocol/hypercore

started time in an hour

issue commenthypercore-protocol/cli

keep getting "the daemon is not active" even after running hyp daemon start

Encountering the same issue on two machines. Debian Buster and Windows 10 both running Node.js 16.9.1. I am not encountering this on a third Debian Buster instance running Node 16.9.1, where the daemon starts and is seeding.

PS C:\Users\metanomial> hyp daemon start
Hyperspace daemon started
Mirroring daemon started
Daemon is running.
PS C:\Users\metanomial> hyp daemon status
Daemon not active
resession

comment created time in 13 hours

issue commenthypercore-protocol/hyperdrive

State of multiwriter?

@RangerMauve your worry of not using sparse data structures so as my history gets longer it will get way slower, especially if new users join in, is the performance degradation over time issue described in the pushpin app which uses hypermerge ?

https://github.com/automerge/pushpin/blob/master/WARNINGS.md#performance-may-degrade-over-time

According to you which CRDT's implementation uses sparse data structures, and therefore could mitigate this problem? https://crdt.tech/implementations

aral

comment created time in 14 hours

startedhypercore-protocol/cli

started time in 18 hours

issue commenthypercore-protocol/hyperdrive

State of multiwriter?

@ralphtheninja Depends on what your data model is like. You might want to look into other things like y.js . Else you can update something like hypermerge which uses CRDTs to represent data.

One worry I have is that a lot of the stuff building on top of hypercore for collaborative editing doesn't use sparse data structures so as your history gets longer it'll get way slower, especially if new users join in. 🤷

aral

comment created time in a day

issue commenthypercore-protocol/hyperdrive

State of multiwriter?

@RangerMauve What do you suggest among the available hyper modules to use for a multi-user collaborative editing?

aral

comment created time in 2 days

fork jeraldrich/hypercore

Hypercore is a secure, distributed append-only log.

fork in 3 days

startedhypercore-protocol/hypercore

started time in 4 days

issue commenthypercore-protocol/hyperdrive

Hyperdrive is not a constructor

Hi @andrewosh !

This is the content of my package.json file :

{
  "dependencies": {
    "hyperdrive": "^10.21.0",
    "hyperspace": "^3.19.0"
  }
}
raphael10-collab

comment created time in 5 days

issue commenthypercore-protocol/hyperdrive

Hyperdrive is not a constructor

Hi @raphael10-collab, I just re-ran the example in a freshly initialized module (in a temporary directory), and it gave the correct expected output:

Hyperspace daemon connected, status:
{
  apiVersion: '1.15.1',
  holepunchable: false,
  remoteAddress: '',
  version: '3.19.0'
}
New drive created, key:
   a9f9ac5c18cc1527741f677ba89f5095cf98ded36b60ba2dea1d68de2b1b24e4
readdir(/)
   [ 'stuff', 'file1.txt' ]
readFile(/file1.txt, utf8)
   Hello world!
readFile(/stuff/file2.bin, hex)
   00010204
Shutting down Hyperspace, this may take a few seconds...

Are you sure you're not importing an old version of Hyperdrive?

raphael10-collab

comment created time in 5 days

issue openedhypercore-protocol/hyperdrive

Hyperdrive is not a constructor

Trying to execute this demo app: https://hypercore-protocol.org/guides/examples/hyperdrive-app/

(base) raphy@pc:~/hypercore/hyperdrive/hyperdrive-app$ node hyperdrive_app.js
Hyperspace daemon connected, status:
{
  apiVersion: '1.15.1',
  holepunchable: false,
  remoteAddress: '',
  version: '3.19.0'
}
(node:132481) UnhandledPromiseRejectionWarning: TypeError: Hyperdrive is not a constructor
    at main (/home/raphy/hypercore/hyperdrive/hyperdrive-app/hyperdrive_app.js:16:15)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:132481) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:132481) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

How to solve the problem?

created time in 5 days

startedhypercore-protocol/hyperbee

started time in 6 days

startedhypercore-protocol/hypercore

started time in 6 days

pull request commenthypercore-protocol/hypertrie

Patch wrong `this` usage

5.1.2

rzadp

comment created time in 6 days

created taghypercore-protocol/hypertrie

tagv5.1.2

Distributed single writer key/value store

created time in 6 days

push eventhypercore-protocol/hypertrie

Mathias Buus

commit sha 374a4fe21e35e48317cac898a742d6a9b40e8032

5.1.2

view details

push time in 6 days

pull request commenthypercore-protocol/hypertrie

Patch wrong `this` usage

Great catch, thank you.

rzadp

comment created time in 6 days

push eventhypercore-protocol/hypertrie

Przemyslaw Rzad

commit sha 9938f16f911ad69b5f45ea4893ea07c9d29db8c2

Patch wrong 'this' usage (#45)

view details

push time in 6 days

PR opened hypercore-protocol/hypertrie

Patch wrong 'this' usage
+1 -1

0 comment

1 changed file

pr created time in 6 days

fork dxos/hypertrie

Distributed single writer key/value store

fork in 6 days

fork Anyass3/hyperdrive

Hyperdrive is a secure, real time distributed file system

fork in 6 days

startedhypercore-protocol/cli

started time in 7 days

startedhypercore-protocol/hyperbee

started time in 7 days

startedhypercore-protocol/hyperdrive

started time in 7 days

startedhypercore-protocol/hypercore

started time in 7 days

startedhypercore-protocol/hypercore

started time in 7 days

startedhypercore-protocol/hypercore

started time in 7 days

fork summercms/hypercore-proposals

Hypercore Proposals. RFCs specifying the Hypercore Protocol behaviors.

fork in 8 days

startedhypercore-protocol/hypercore-protocol

started time in 9 days