Skip to content
This repository was archived by the owner on Nov 25, 2023. It is now read-only.

Commit 464dc5f

Browse files
committed
fix upload video demo
1 parent a23fadd commit 464dc5f

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ Built on top of the [Hypercore protocol](https://hypercore-protocol.org/) with e
77

88
## Demos
99
<p align="center">
10-
<img alt="Uploading Files" src="assets/upload-demo.gif" width="45%">
11-
&nbsp; &nbsp; &nbsp; &nbsp;
12-
<img alt="Downloading Files" src="assets/download-demo.gif" width="45%">
10+
<img alt="Uploading Files" src="assets/upload-demo.gif" width="50%">
11+
&nbsp; &nbsp;
12+
<img alt="Downloading Files" src="assets/download-demo.gif" width="50%">
1313
</p>
1414

1515
## Installation
@@ -40,7 +40,9 @@ $ portal join [sessionID]
4040
Portal relies on a publish-subscribe event model to drive its render and update cycles. File tree structure and individual file statuses are stored in a trie structure known as the Registry. On the host side, there is a local Registry that listens to file changes on the host machine and broadcasts them to an append-only [Hypercore](https://hypercore-protocol.org/protocol/#hypercore) that is used as an event log. A drive syncing hook listens for changes in the local registry and streams file changes from disk to a [Hyperdrive](https://hypercore-protocol.org/protocol/#hyperdrive). On the client side, a remote Registry listens for changes in the event log and replicates changes locally. A drive download hook listens for changes in the remote registry and streams file changes from the Hyperdrive to the local disk.
4141

4242
### Connection
43-
Portals are identified by unique* (1/1.1579x10^77 chance of collision) 32-byte keys. When a client 'joins' a portal, `portal` looks up the session key using [Hyperswarm](https://hypercore-protocol.org/protocol/#hyperswarm) and establishes a connection to the host using UDP holepunching.
43+
Portals are identified by unique* 32-byte keys. When a client 'joins' a portal, `portal` looks up the session key using [Hyperswarm](https://hypercore-protocol.org/protocol/#hyperswarm) and establishes a connection to the host using UDP holepunching.
44+
45+
*8.63x10<sup>-78</sup> chance of collision
4446

4547
### How is this different from Dat?
4648
Might seem similar to another similar project built on top of the Hypercore protocol called [Dat](https://github.com/datproject/dat) but there are a few key differences.

assets/upload-demo.gif

-22.7 MB
Loading

0 commit comments

Comments
 (0)