Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pfraze
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
63 ms
·
781.
▲
by
pfraze
9y ago
In the Dat world, we have https://hashbase.io , a self-deployable service for rehosting archives
782.
▲
by
pfraze
9y ago
We're not reproducing the Web, we're improving it. The Web is well-known by devs and users, has lots of tooling, and has all the features I'd want from a p2p applications platform. It just needs the p2p. The question to ask i
783.
▲
by
pfraze
9y ago
Just replace HTTP with the peer-to-peer network. You don't need to lose the whole platform.
784.
▲
The web is dying, but mesh networks could save it
(thenextweb.com)
15 points
by
pfraze
9y ago
|
6 comments
785.
▲
by
pfraze
9y ago
2. See my reply to 1! 3. I'm not personally familiar with OpenMined but decentralization is a pretty active space. SSB and Dat/Beaker have a few things in common: overlap in the communities, a focus on p2p hypermedia protocols, an
786.
▲
by
pfraze
9y ago
1. Yes. Economic models are challenging, especially if ads don't work well anymore. (One thing I'd point out is that most ad revenue is sucked up by Google and Facebook, and they're the entities most ripe for disruption.) A
787.
▲
by
pfraze
9y ago
Another interesting element about the local index is that it might be usable for discovery. Essentially there's a local cache of the Web in the user's browser. Much of that local cache has semi-structured data thanks to JSON, and
788.
▲
by
pfraze
9y ago
macawfish is suggested distributed search indexes, which is a neat idea that YaCy [1] explores. We're looking at adding a private search index in the browser itself. This index would be constructed by adding dat sites to your 'lib
789.
▲
by
pfraze
9y ago
I worked on Secure Scuttlebutt and then founded Beaker. Happy to answer questions.
790.
▲
WebDB – A database that reads and writes records on dat:// websites
(github.com)
2 points
by
pfraze
9y ago
|
0 comments
791.
▲
Why is this company tracking where you are on Thanksgiving?
(theoutline.com)
2 points
by
pfraze
9y ago
|
0 comments
792.
▲
by
pfraze
9y ago
I think you're right that handling catastrophic failure is the key question for a hosted ledger. You have to find a way for the network to agree on who will rehydrate the balances, so to speak, into a replacement host, and you need to
793.
▲
by
pfraze
9y ago
Hey Brock. My argument is that decentralized consensus is actually a political solution. It has technical merits -- it makes it easier to deal with a host that breaks the contract, because there are lots of nodes, so you just 'route ar
794.
▲
by
pfraze
9y ago
Choosing another node won't involve consensus in the way that consensus is described in distributed networks. You'd handle that ideally by a prior agreement -- eg, "if this node corrupts, it's going to go into arbitratio
795.
▲
by
pfraze
9y ago
Actually I appreciate the defense, but that's not what I'm claiming. I'm claiming that decentralized consensus gives only a minor gain over a single node maintaining a well-monitored blockchain. Single nodes don't have t
796.
▲
by
pfraze
9y ago
> Paul's system has no way of addressing this other than "trust the central authority to process transactions in the order they receive them". Thanks, pal, that's called e-cash, and was invented by David Chaum in 1983
797.
▲
by
pfraze
9y ago
Well, no, I'm not describing Linked Timestamping (hereafter LT), because LT is a system for creating trustable timestamps, and I'm talking about a system for auditing the state and operation of a service. Hash/block chains ar
798.
▲
by
pfraze
9y ago
I absolutely do respond to alternatives to proof of work in my post, thank you very much! And I agree that they may be valuable, but I'm skeptical, and you can reread my post to see why. And, by the by, the DDOS argument is a straw
799.
▲
by
pfraze
9y ago
There's aaalways a catch. See my response to hagreet. Neither of those problems are unfixable.
800.
▲
by
pfraze
9y ago
Semi-trusted. You have total transparency into whether the node is following the rules of the code contract. The node could not, for instance, change values in the DB without doing so via the contract, and that would be logged for all to se
801.
▲
by
pfraze
9y ago
You don't use decentralized consensus in this model. It's a single node that's maintaining the blockchain state. Monitors actively watch the blockchain to make sure the node doesn't deviate from the code contract. If the
802.
▲
by
pfraze
9y ago
Yeah, though we don't use Git to monitor active systems.
803.
▲
by
pfraze
9y ago
You can have blockchains without decentralized consensus. It's how Certificate Transparency works. You have the contract host record all operations and output on a ledger, and then ship that ledger/log out to monitors. This impro
804.
▲
A smart-contract server built on Dat
(nodevms.com)
3 points
by
pfraze
9y ago
|
0 comments
805.
▲
by
pfraze
9y ago
I gave a talk about a P2P Web at PDX node just a bit ago https://www.youtube.com/watch?v=-ep0ZIe6i10
806.
▲
by
pfraze
9y ago
You can't just wish that people would build apps a different way though, right? You have to change the system somehow. So, this is how we're doing it. No legacy support, but it does have interesting new use-cases that can disrupt
807.
▲
by
pfraze
9y ago
This was fun, second podcast I've done. (Learning process for sure.) We talked about a lot of different technical details, which should be interesting but it's pretty dense. I pulled out a clip that gives a high level overview if
808.
▲
by
pfraze
9y ago
You're ignoring the data silo problem. Of course the Web is decentralized in terms of accessing web pages, but-- the majority of data is not composed of pages, and the majority of actions on the Web are not composed of hyperlink traver
809.
▲
by
pfraze
9y ago
letlambda's explanation for IPFS is right. In Dat, that method is used to produce an append only log out of a merkle tree. Each time you add an entry, a leaf is added to the tree, and the new head is signed. I wrote about it here [1] a
810.
▲
by
pfraze
9y ago
Beaker and Dat are actually two different groups that work together. We discuss things all the time but decide on things separately. Beaker uses Electron. We chose that because we're from the nodejs world and it allows us to move reall
More ›