The Internet as we know it has existed unchanged (more or less) for the last 50 years. People across the globe use their devices to retrieve data from huge servers dotted around the world.
A group of dedicated technologists wants to change that to make the internet a place where people can connect and share information directly instead of relying on a central server (decentralization).
There are a bunch of such decentralized services that we have already covered on It’s FOSS. LBRY as YouTube alternative, Mastodon as Twitter alternative are just a couple of such examples.
And today I am going to cover another such product called Beaker Browser which is essentially for browsing the peer to peer web.
What is the ‘peer-to-peer Web’?
According to one of the devs behind the Beaker browser, “The P2P Web is an experimental set of technologies…to give users more control over the Web.”
Further, they say that the peer-to-peer Web has three main principles: anybody can be a server; multiple computers can serve the same site; there is no back end.
As you can see from those principles. the idea of the peer-to-peer Web is very similar to BitTorrent where files are seeded by multiple peers and those peers share the bandwidth load. This reduces the overall bandwidth that a person needs to provide for their site.
The other major part of the peer-to-peer Web is creator control of their ideas. In this day and age, platforms being controlled by large corporations, who try to use your data for their benefit. Beaker returns control to the content creators.
Browsing the decentralized web with Beaker
The Beaker Browser first came into existence in 2016. The project (and the technology that surrounds it) is created by a team of three at Blue Link Labs. The Beaker Browser uses the Dat protocol to share data between computers. All websites that use the Dat protocol start with dat:// instead of http://.
The strengths of the Dat protocol are:
- Fast – Archives sync from multiple sources at once.
- Secure – All updates are signed and integrity-checked.
- Resilient – Archives can change hosts without changing their URLs.
- Versioned – Changes are written to an append-only version log.
- Decentralized – Any device can host any archive.
The Beaker Browser is essentially a cut down version of Chromium with built-in support for dat://addresses. It can still visit regular http:// sites.
Each time you visit a dat site, the content for that site is downloaded to your computer as you request it. For example, a picture of Linux Torvalds on the about page of a site is not downloaded until you navigate to that page.
Also, once you visit a dat website, “you temporarily re-upload or seed whichever files you’ve downloaded from the website.” You can also choose to seed the website to help its creator.
Since the whole idea of Beaker is to create a more open web, you can easily view the source of any website. Unlike most browsers where you just see the source code the current page, you are viewing, Beaker shows you the entire structure of the site in a GitHub-like view. You can even fork the site and host your version of it.
Besides visiting dat-based websites, you can also create your own site. In the Beaker Browser menu, there is an option to create a new website or an empty project. If you select the option to create a new website, Beaker will build a little demo site that you can edit with the browser’s built-in editor.
However, if you are like me and prefer to use Markdown, you can choose to create an empty project. Beaker will create the structure of a site and assign it a dat://address. Create an index.md file and you are good to go. There is a short tutorial with more info. You can also use the create empty project option to build a web app.
Since Beaker acts as a web server and site seeder, any time you close it or turn off your computer your site will become unavailable. Thankfully, you don’t have to run your computer or the browser constantly. You can also use a seeding service named Hashbase or you can set up a homebase seeding server.
Though Beaker is available for Linux, Windows, and macOS. If you do start playing around Beaker, be sure to take a quick look at their guides.
Beaker Browser is not for everyone but it has a purpose
When I first got this assignment, I had high hopes for the Beaker Browser. As it stands now, it’s still very experimental. A number of the dat sites that I tried to visit were unavailable because the user was not seeding their site. Beaker does have an option to notify you when that site is back online.
Another problem is that Beaker is a really stripped down version of Chromium. There is no option to install extensions or themes. Instead, you are stuck with a white theme and a very limited toolset. I would not use this as my main browser and having access to the world of dat websites is not enough of a reason to keep it installed on my system.
I looked to see if there is an extension for Firefox that would add support for the dat:// protocol. I did find such an extension, but it also required the installation of a couple of other pieces of software. It’s just easier to install Beaker.
As it stands now, Beaker is not for me. Maybe in the future, more people will start using Beaker or the dat protocol will gain support by other browsers. Then it might be interesting. Right now, it’s kinda empty.
As part of my time with Beaker, I created a website using the built-in tools. Don’t worry, I made sure that it’s seeded.
What are your thoughts on the Beaker Brower? What are your thoughts on the peer-to-peer web? Please let us know in the comments below.
If you found this article interesting, please take a minute to share it on social media, Hacker News, or Reddit.
from It's FOSS https://ift.tt/2VXL0ac
via IFTTT
Tidak ada komentar:
Posting Komentar