IPFS and Beaker

[Trevor Oakley]

I am trying to browse IPFS but when I use ipfs:/ipfs/QmeAfcM5esSxEU3PDdzS3MZXbvPWYdCCy546Typk95is9b it keeps defaulting to duckduckgo. I am using Ubuntu.

Is there any solution to this?

[Mario Pietsch]

Hi Trevor,

I'm not sure, if it ever worked, but with beaker V0.7.0 it's mentioned in the "Deprecations:" section. see:https://github.com/beakerbrowser/beaker/releases

-mario

[Trevor Oakley]

Thanks. Yes I saw it says they want to support dat files now. 

I am working with IPFS in the context of blockchains (address of the file is a hash on the blockchain). I was wondering if anyone has worked with dat and blockchains or even if that is possible. 

They say here - https://exclusive-index.glitch.me/docs/inside-beaker/other-technologies.html#why-not-a-blockchain - blockchains are ignored but their text is dated. Blockchains are moving to Proof of Stake and a lot of variants are appearing onto the market. 

[Paul Frazee]

The text on blockchains is up to date. Proof-of-Stake is still new and unproven, and other UX problems exist for blockchains, including large downloads and up-front fees for every transaction.

Dat works extremely well without blockchains. Each Dat is addressed by a private-key, and is backed by a signed merkle-tree log which I happen to be writing about right now.

--
You received this message because you are subscribed to the Google Groups "Beaker Browser" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beaker-browser+unsubscribe@googlegroups.com.
To post to this group, send email to beaker-browser@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beaker-browser/af658fa3-3086-4a52-9926-b936ef1cafb3%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Trevor Oakley]

No one in the blockchain sector thinks PoM has any future. There are a lot of scalability issues with blockchains and these are being worked on. The blockchain sector is very fast moving. 

On Sunday, June 18, 2017 at 5:28:35 PM UTC+1, Paul Frazee wrote:

The text on blockchains is up to date. Proof-of-Stake is still new and unproven, and other UX problems exist for blockchains, including large downloads and up-front fees for every transaction.

Dat works extremely well without blockchains. Each Dat is addressed by a private-key, and is backed by a signed merkle-tree log which I happen to be writing about right now.

On Sun, Jun 18, 2017 at 8:40 AM, Trevor Oakley <trevoro...@gmail.com> wrote:

Thanks. Yes I saw it says they want to support dat files now. 

I am working with IPFS in the context of blockchains (address of the file is a hash on the blockchain). I was wondering if anyone has worked with dat and blockchains or even if that is possible. 

They say here - https://exclusive-index.glitch.me/docs/inside-beaker/other-technologies.html#why-not-a-blockchain - blockchains are ignored but their text is dated. Blockchains are moving to Proof of Stake and a lot of variants are appearing onto the market. 

On Sunday, June 18, 2017 at 12:05:43 PM UTC+1, Mario Pietsch wrote:

Hi Trevor,

I'm not sure, if it ever worked, but with beaker V0.7.0 it's mentioned in the "Deprecations:" section. see:https://github.com/beakerbrowser/beaker/releases

-mario

--
You received this message because you are subscribed to the Google Groups "Beaker Browser" group.

To unsubscribe from this group and stop receiving emails from it, send an email to beaker-browse...@googlegroups.com.
To post to this group, send email to beaker-...@googlegroups.com.

[Trevor Oakley]

PoW I meant. 

[Tara Vancil]

Hi Trevor,

We know folks are working hard to address the scale issues of blockchains, but at this point, using a blockchain isn't necessary to achieve our goals.

Of course we'll keep an eye on developments in the space, but right now we're happy with how our architecture is serving our needs.

To view this discussion on the web visit https://groups.google.com/d/msgid/beaker-browser/6d434a74-5cb8-4876-a8da-cd438947778b%40googlegroups.com.

[Mario Pietsch]

Probably a bit OT. ... bare with me ;)

On Sunday, June 18, 2017 at 8:45:16 PM UTC+2, Tara Vancil wrote:

Hi Trevor,

We know folks are working hard to address the scale issues of blockchains, but at this point, using a blockchain isn't necessary to achieve our goals.

For me the "... achieve our goals" is the important part here. ... Users want to "get work done". Most of them really don't care about the underlaying technology. ... They know files, they know e-mail and some of them know dropbox. That's it.

Many users go a really long way to keep their data "file based", but still need / want a platform to share it with their community, in a relatively easy way and "privately" if needed.

IMO this behavior isn't economically useful, but that doesn't matter. ... It's the status quo and changing it is really hard. ...

I do like this dat-intro by Karissa McKelvey very much. It sums up the reasons, why the dat-protocol was developed in the first place. (It's from October 2016. So I hope the goals are still the same.)

dat, imo has a slightly different characteristic than IPFS. While IPFS wants to change "the web" as a whole, dat uses a more conservative approach.

There is still the problem, to create an "incentive" for "players", that is good enough, to host user data. IPFS seems to bet on "filecoins", based on "eutherium". Which seems to be a possible business model. How it works out, will need to be seen. ...

For the dat-protocol I don't see many incentives at the moment. Except as "just an other file hosting service". Which isn't unique at all.

The beaker browser is a "different" beast. ... Is it the "killer app" that can push itself and the underlaying tech to get a critical mass? We'll see. .

Just some thoughts.

have fun!
mario

[Paul Frazee]

Well said, Mario. It's really a difference of bets on tech that each group is making. We think we benefit from a lot less complexity overall by removing blockchains from the stack. We think users don't need it, and the product will be faster and simpler without it.

--
You received this message because you are subscribed to the Google Groups "Beaker Browser" group.

To unsubscribe from this group and stop receiving emails from it, send an email to beaker-browser+unsubscribe@googlegroups.com.
To post to this group, send email to beaker-browser@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beaker-browser/2195f8db-eba0-4a7e-8d54-6c0183277e38%40googlegroups.com.