I was very happy to take part in the future of the browser conference, along with my amazing colleague Jasmine. It was a different kind of conference and this was very clear from the introduction with Amber in the future! (amazing and well worth watching)
Each section started with a really different video from different artists. This was a great move with most conferences, generally starting with a keynote before the conference talks) This conference turned that on its head before jumping into number of deep dives around aspects of the future browser. All the videos are now up online, so go have a watch now.
There was quite a few new developments I hadn’t really seen before.
Project Fugu is an effort to close gaps in the web’s capabilities enabling new classes of applications to run on the web. In short things like controlling Zigbee, USB and Bluetooth devices. I heard about this a while ago and thought Living room of the Future controlled via a browser.
Handshake is a decentralized, permission-less naming protocol where every peer is validating and in charge of managing the root DNS naming zone with the goal of creating an alternative to existing Certificate Authorities and naming systems. Names on the internet (top level domains, social networking handles, etc.) ultimately rely upon centralized actors with full control over a system which are relied upon to be honest, as they are vulnerable to hacking, censorship, and corruption.
I think that says it all, something which many people have pointed out many times as a major problem with the DNS system.
Handshake is an experiment which seeks to explore those new ways in which the necessary tools to build a more decentralized internet. Services on the internet have become more centralized beginning in the 1990s, but do not fulfill the original decentralized vision of the internet. Email became Gmail, usenet became reddit, blog replies became facebook and Medium, pingbacks became twitter, squid became Cloudflare, even gnutella became The Pirate Bay. Centralization exists because there is a need to manage spam, griefing, and sockpuppet/sybil attacks.
As most of you know, I have webmontization enabled on this blog and also on my mixes site. But Unlock is aimed at subscriptions and memberships. This is great news, except its not a standard yet but looks promising.
I had heard Matt talk previously during May’s Manchester Futurists. There is a lot of unexplored areas in the http status codes including 402, which could be used to do new and interesting things like WebMon, which was also covered in Manchester Futurists and the future of the browser.
Saving the page has been a nightmare for a long while, and I found Webrecorder and ArchiveWeb.page quite interesting solutions. Its also interesting to think about the lengths we have gone through to stop people saving the page.