New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-decentralizing the Web with a peer-to-peer browser #96

Open
mozfest-bot opened this Issue Jul 9, 2017 · 6 comments

Comments

@mozfest-bot
Collaborator

mozfest-bot commented Jul 9, 2017

[ UUID ] 6120ad9e-6b26-4b1f-b64d-badba26bda19

[ Submitter's Name ] Tara Vancil
[ Submitter's Affiliated Organisation ] Blue Link Labs
[ Submitter's Github ] @taravancil

[ Additional facilitators ] Paul Frazee,

What will happen in your session?

We’ll begin by discussing what it means to say the Web is centralized, talk about the consequences of the Web being centralized, and introduce the decentralized Web as an alternative to the Web’s current architecture.

Next we’ll introduce the Beaker browser and Hashbase, the technologies we’ve built in an effort to decentralize the Web and reclaim privacy and data ownership on the Web. We’ll also talk about how we use Dat inside of Beaker. Dat is a peer-to-peer file sharing protocol that makes it possible to host websites from your local device.

We’ll then guide attendees through the Beaker installation process and step through an interactive demo, which ends with users learning how to make and publish a peer-to-peer website.

What is the goal or outcome of your session?

Our goal is to clarify what threats are posed if the Web remains centralized. We hope to articulate what flaws must be addressed in the Web’s architecture in order for the Web to be robust, open, and free for all.

We expect participants will leave with a clear sense of how modern peer-to-peer file sharing protocols provide tools to make Web publishing simple and very cheap, and how Beaker is using the Dat protocol to enable decentralized Web publishing and to build applications where users retain authority over their data.

By the end of the session, attendees should feel confident using Beaker to publish and share files, and perhaps even to use Beaker’s DatArchive Web APIs to create peer-to-peer websites.

If your session requires additional materials or electronic equipment, please outline your needs.

We need a projector to display our demos and guide participants through the interactive tutorial.

Time needed

60 mins

@timcowlishaw

This comment has been minimized.

Show comment
Hide comment
@timcowlishaw

timcowlishaw Jul 17, 2017

Collaborator

Hi there @taravancil,

This sounds really great. Can you give us an idea of the level of skill / expertise participants will need to take part in the tutorial? Mostly for information, but it'd be great to make sure that it's as widely accessible as possible!

Thanks!

Tim

Collaborator

timcowlishaw commented Jul 17, 2017

Hi there @taravancil,

This sounds really great. Can you give us an idea of the level of skill / expertise participants will need to take part in the tutorial? Mostly for information, but it'd be great to make sure that it's as widely accessible as possible!

Thanks!

Tim

@taravancil

This comment has been minimized.

Show comment
Hide comment
@taravancil

taravancil Jul 18, 2017

Hi @timcowlishaw,

The tutorial will be accessible for anyone that feels comfortable using a WYSIWYG-style editor. Participants won't need to know how to write code, and it won't require a deep understanding of the Web platform.

We'd like to step through a few examples that use Beaker's p2p Web APIs, but we can do those examples at the end of the session, so that participants who aren't comfortable working with code can leave if they'd like, or alternatively follow along with someone else.

taravancil commented Jul 18, 2017

Hi @timcowlishaw,

The tutorial will be accessible for anyone that feels comfortable using a WYSIWYG-style editor. Participants won't need to know how to write code, and it won't require a deep understanding of the Web platform.

We'd like to step through a few examples that use Beaker's p2p Web APIs, but we can do those examples at the end of the session, so that participants who aren't comfortable working with code can leave if they'd like, or alternatively follow along with someone else.

@dvigneshwer

This comment has been minimized.

Show comment
Hide comment
@dvigneshwer

dvigneshwer Aug 14, 2017

Collaborator

Hi @taravancil,

Thanks for this interesting proposal. Beaker browser and the idea of p2p websites sound really cool and promising.

It will be great if you help me with the following questions:

  • Do you think a less technically skilled person will be able to publish a peer-to-peer website?
  • How much time does it take to create a basic p2p website?
  • Will it be possible for a less technically adept person to create a p2p website by only referring to documentation?
Collaborator

dvigneshwer commented Aug 14, 2017

Hi @taravancil,

Thanks for this interesting proposal. Beaker browser and the idea of p2p websites sound really cool and promising.

It will be great if you help me with the following questions:

  • Do you think a less technically skilled person will be able to publish a peer-to-peer website?
  • How much time does it take to create a basic p2p website?
  • Will it be possible for a less technically adept person to create a p2p website by only referring to documentation?
@taravancil

This comment has been minimized.

Show comment
Hide comment
@taravancil

taravancil Aug 14, 2017

Hi @vigneshwerd

Do you think a less technically skilled person will be able to publish a peer-to-peer website?

Yes. We have some templates available that a less technically adept person could work from, but someone like that would probably prefer to use Beaker's builtin forking feature, which allows you to fork any existing p2p website and mint a new p2p URL in seconds, and then you can customize it however you like.

How much time does it take to create a basic p2p website?

In terms of crafting the HTML, CSS, JS, etc., just like on the traditional Web, the answer varies wildly based on which tools you use and what functionality you require.

However, unlike the traditional Web, p2p websites can be published in seconds. So for example, a basic website with just a simple index.html can be published and share-able on the p2p Web in < 30 seconds.

Will it be possible for a less technically adept person to create a p2p website by only referring to documentation?

Probably not. We haven't built a WYSIWYG, but a less technical person could use any WYSIWYG editor that generates HTML and then publish those files using Beaker. Keep in mind that we haven't prioritized that use case, so we don't have any docs guiding users through that process at this moment.

taravancil commented Aug 14, 2017

Hi @vigneshwerd

Do you think a less technically skilled person will be able to publish a peer-to-peer website?

Yes. We have some templates available that a less technically adept person could work from, but someone like that would probably prefer to use Beaker's builtin forking feature, which allows you to fork any existing p2p website and mint a new p2p URL in seconds, and then you can customize it however you like.

How much time does it take to create a basic p2p website?

In terms of crafting the HTML, CSS, JS, etc., just like on the traditional Web, the answer varies wildly based on which tools you use and what functionality you require.

However, unlike the traditional Web, p2p websites can be published in seconds. So for example, a basic website with just a simple index.html can be published and share-able on the p2p Web in < 30 seconds.

Will it be possible for a less technically adept person to create a p2p website by only referring to documentation?

Probably not. We haven't built a WYSIWYG, but a less technical person could use any WYSIWYG editor that generates HTML and then publish those files using Beaker. Keep in mind that we haven't prioritized that use case, so we don't have any docs guiding users through that process at this moment.

@daniellecrobinson

This comment has been minimized.

Show comment
Hide comment
@daniellecrobinson

daniellecrobinson Sep 15, 2017

👍 so into this session

daniellecrobinson commented Sep 15, 2017

👍 so into this session

@cubicgarden cubicgarden self-assigned this Sep 30, 2017

@dvigneshwer dvigneshwer self-assigned this Oct 1, 2017

@dvigneshwer

This comment has been minimized.

Show comment
Hide comment
@dvigneshwer

dvigneshwer Oct 1, 2017

Collaborator

Hi @taravancil

As MozFest is approaching we require the following information from your end to better support your session in the Decentralization learning forum space. You can get back to us by replying to this issue or emailing us directly, whichever communication channel is convenient to you.

  1. Provide us a brief outline of your session topics and time estimates
  2. Does your session require any additional materials or electronic equipment other than a projector and general office stationery?
  3. Please let us know if you want to make any modification to your session proposal

Thank you! Please don't hesitate to contact us if you have any queries.

Collaborator

dvigneshwer commented Oct 1, 2017

Hi @taravancil

As MozFest is approaching we require the following information from your end to better support your session in the Decentralization learning forum space. You can get back to us by replying to this issue or emailing us directly, whichever communication channel is convenient to you.

  1. Provide us a brief outline of your session topics and time estimates
  2. Does your session require any additional materials or electronic equipment other than a projector and general office stationery?
  3. Please let us know if you want to make any modification to your session proposal

Thank you! Please don't hesitate to contact us if you have any queries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment