Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pfraze
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
97 ms
·
661.
▲
by
pfraze
6y ago
The Beaker team works on Hyperdrive (the Hypercore Protocol) but we maintain a separate org at https://github.com/hypercore-protocol
662.
▲
by
pfraze
6y ago
Currently Beaker only has Web APIs for Hyperdrive, but we're going to add Hypercore APIs Hypercore is lower-level - it's basically an append-only log. There have been some projects that use it directly such as Kappa-core [1]. You
663.
▲
by
pfraze
6y ago
Personally I think it's the hackability. Data is disconnected from apps (in your personal drives) and shared between applications. Hyperdrives are also forkable. Beaker currently pushes people to create personal sites and build social
664.
▲
by
pfraze
6y ago
Yeah so Beaker uses a peer-to-peer filesystem called Hyperdrive to share websites. It works a lot like BitTorrent in that it shares bandwidth. Every drive has a public key and the data is signed in a log. Since the Hyperdrive FS is read
665.
▲
by
pfraze
6y ago
I think dat has always been node/js
666.
▲
by
pfraze
6y ago
Thanks! Let us know how it goes
667.
▲
by
pfraze
6y ago
This new version of Beaker took over a year to get done and is basically a ground-up rewrite. Team is here to answer any questions.
668.
▲
Beaker 1.0 Beta – a peer-to-peer Web browser
(beakerbrowser.com)
23 points
by
pfraze
6y ago
|
14 comments
669.
▲
by
pfraze
6y ago
Thanks! - "Hyperdrive" was formerly the internal data-structure name of Dat archives. With this release, the team decided to rename the protocol from Dat to Hypercore Protocol. Subsequently, "Dat Archives" are now "
670.
▲
by
pfraze
6y ago
That's odd, what browser?
671.
▲
by
pfraze
6y ago
I'm not deeply familiar with Syncthing but here are some differences based on what I do know: - Hyperdrive includes mass-publishing as a usecase, so it uses public-key URLs and a bandwidth-sharing mechanism among its active peers (like
672.
▲
by
pfraze
6y ago
Hyperdrive is part of the peer-to-peer networking stack that Beaker Browser uses for websites. Today is release day and this tech update is the first announcement.
673.
▲
Hyperdrive v10 – a peer-to-peer filesystem
(blog.hypercore-protocol.org)
387 points
by
pfraze
6y ago
|
117 comments
674.
▲
by
pfraze
6y ago
I do agree that the US is rigid in its thinking. We accumulated a lot of wealth in the mid-20th century and a lot of national policy debates are around how that wealth is distributed rather than about undertaking new national ventures to br
675.
▲
by
pfraze
6y ago
Beaker's going to finally release a new version in ~2 weeks. No solution to the mobile browser yet, but I hope somebody will pick up the mantle from Cliqz and Busnen.
676.
▲
by
pfraze
7y ago
I think that's exactly what Pebble' problem was, unfortunately. It wasn't fashionable.
677.
▲
by
pfraze
7y ago
You have the details right. I think it's fair to say that the protocol is very leaky with its metadata right now. In a local network, it would be wise to only exchange announcements with trusted devices. In the global network, it would
678.
▲
by
pfraze
7y ago
> Does the newest version of dat handle large files well (10gb)? Large files work fine but currently any change to a file rewrites it in its entirety. That will mean history will be large until the GC kicks in, and any file that's m
679.
▲
by
pfraze
7y ago
Yeah I do know there's a Rust impl that people are working on
680.
▲
by
pfraze
7y ago
We decided to take a year to go heads down and rework a lot of stuff, so we did get publicly stagnant but we're fulltime on the next version and should release a public beta soon. I tweet a lot about our progress if you can sort throug
681.
▲
by
pfraze
7y ago
Unfortunately that demo was built on a protocol prototype which was deprecated. Multiwriter is still being worked on, but it's not in the current release schedule. The upcoming release focuses on performance, scaling, reliability, and
682.
▲
by
pfraze
7y ago
Generally speaking, this is the right call - though you don't necessarily need to rebase the whole log. The hypercore logs that Cabal uses can partially sync. You can choose not to sync certain chunks without losing verifiability; all
683.
▲
by
pfraze
7y ago
If we assume that corporate value is relatively unchanged from 2014 and then assume that the government bails out the companies by paying off the debt, then the stock market's growth from 2014 would be a form of inflation, wouldn'
684.
▲
by
pfraze
7y ago
Wasm comes to mind for a new browser arch because in theory it could be a userland replacement for traditional platform features like the UI. You could have a wasm module for HTML, for instance, which could be chosen for legacy sites, but r
685.
▲
by
pfraze
7y ago
There may be a market for a "microkernel" redesign of browsers in the next 5 years. OP's point is right that the current design is impossible for new entrants to implement. That alone probably won't create a market for s
686.
▲
by
pfraze
7y ago
Okay thanks for the insights. Learning curve may reduce the available engineers (at least for a bit) but my concern is about whether the PL's premises are holding up in real world usage, which it sounds like (for you and other commente
687.
▲
by
pfraze
7y ago
Thanks for the insight!
688.
▲
by
pfraze
7y ago
We'll s/biased/credible/ on this one. Can you think of any cases where he might be right? How often do you hit, for instance, "This code cleanly fit its original construction, but now I have to add some complexity f
689.
▲
by
pfraze
7y ago
I'm interested in Rust's future, but not a Rust developer myself. The author's argument is pretty straight-forward: Rust's borrow-checker makes for complex code, so you should think carefully whether your application is
690.
▲
by
pfraze
7y ago
It might be simpler to view these languages from the perspective of "general purpose" or "specialized." General purpose languages rely on social compatibility because they're meant to handle a wide range of common d
More ›