An add-on to bridge Web Browsers and the Decentralized Web
Become a contributor
Top financial contributors
€70 EUR since Jun 2019
€61 EUR since Aug 2019
€50 EUR since Oct 2019
€50 EUR since Oct 2019
€25 EUR since Apr 2020
€18 EUR since Jul 2019
€18 EUR since Oct 2019
Anders Rune Jensen
€15 EUR since Jun 2019
€10 EUR since Jun 2019
€5 EUR since Aug 2020
What's new with Patchfox
Stay up to dates with our latest activities and progress.
Patchfox 2019.11.1 released
See how money openly circulates through Patchfox. All contributions and all expenses are published in our transparent public ledger. Learn who is donating, how much, where is that money going, submit expenses, get reimbursed and more!
~ €398.03 EUR
Patchfox is all of us
Our contributors 15
Everyone who has supported Patchfox. Individuals and organizations that believe in –and take ownership of– our purpose.
You are awesome! Keep going...great things will come to you in time <3
Where money will be spent?
- Development time from contractors and core contributors.
- Potential infrastructure.
- Outreach towards other dweb communities, web developers and events.
- Producing content to help onboard new users and developers.
- Add support for:
- Private messages
- Start testing under Opera Browser and Brave Browser
- Improve pull-stream handling for posts/avatars/names/votes
Motivation behind the project
At the moment, there are two main ways of interacting with scuttlebutt: running an electron based app or running some form of server and opening a local webapp. In the first case, your scuttlebutt experience is decoupled from your web experience which is at the same time good and bad. In the second case, even if you’re using scuttlebutt from a tab in your browser of choice, it doesn’t interact with the remaining web experience you have while using the browser. Patchfox make possible new experiences and features that are not easily done with the above mentioned ways of running Secure Scuttlebutt. I’d like to summarize some reasons why I believe this is a good idea:
Richer interaction with the browser
Using an add-on allows us to tap into APIs that are not available to normal webapps. It opens possibilities for contextual menus, browser buttons, sidebars, and other UX experiences. For example, a compose message window on a sidebar allows you to change your active tab while still composing the message, thus making it a lot easier to compose entries that carry content from multiple sources and to fact-check stuff while you’re posting.
Allows us to run one less web engine
There are too many electron based apps in our daily usage. Many of us (me included) are running an editor such as Visual Studio Code or Atom, Slack, Spotify, Patchwork, Trello app, and each of those apps is one more chrome-based engine running. Chrome is not known for being a diet browser, if we could run one less instance of chrome, that would help our machine.
Find new usage patterns
As this deeper integration opens up new possibilities of usage (mostly by reducing friction), new forms of interaction between the current web and the decentralized web will surface. Having decentralized technology inside a major browser will probably lead to new usage patterns beyond what we have seen so far.
Pave the way for more decentralized features inside major web browsers
Once completed and working, the method of adding ssb features to Firefox will make it easier to add features from other dweb solutions such as dat and ipfs, which could lead to larger and more frictionless adoption of those technologies as well.
WebExtensions work in many browsers
The new add-on API called WebExtensions is basically an standard. The API is shared between Firefox, Chrome, Opera and even Edge and Vivaldi. Each browser has some APIs that are not present in the others but it is a lot easier to port between browsers than it was when each used their own API. This work could later be used in porting the add-ons to other browsers.