When turning the “Publish to Distributed Web” toggle on, you will make your site's contents available through the following peer-to-peer protocols: InterPlanetary File System (IPFS) and Holepunch (formerly known as Hypercore). These are just two of many distributed web (DWeb) protocols that exist today. By publishing through Sutty, you are also making your web page available on the World Wide Web (WWW) using Hypertext Transfer Protocol (HTTP), the web protocol that is most widely known and used.
Each of these protocols have their benefits and drawbacks, but we believe that using multiple means to publish and access content on the web is crucial, in order to make websites more accessible, resilient, and censorship-resistant.
We want to make sure you fully understand what it means to publish on the DWeb…!
*** Please do not publish sensitive materials that may pose a threat to yourself or others. Only use this option if you would like your data to be publicly available permanently. ***
If you decide to undo this selection, an empty version of the site will be shared in its place. However, it is possible that nodes on the distributed storage network may continue retaining copies of the data you originally shared indefinitely.
This is not so different from the traditional web. There, people can also take screenshots or archive your site. It is nearly impossible to know if someone may have a copy or photo of sites, even if it has been taken down from its host server. However, the censorship-resistance of DWeb protocols depends on multiple copies of your data being made across the network, and so it is harder to remove this data once it is distributed.
Please read the Frequently Asked Questions below for a more detailed explanation.
This toggle feature in the Sutty web page editor is still in Beta – that means this is a new feature we are releasing into the world for people to try out, and it likely has bugs or useability issues. As we continue to polish this feature, we value hearing from you about how this tool is working or not working as you hope or expect.
Thank you so much for helping us make DWeb publishing better for everyone!
This is a free and open source project led by two non-for-profit worker co-operatives, Sutty and Hypha Worker Co-operative. If you’re a fan of this mission and would like to see Distributed Press continue to be maintained and expanded, please support us in the following ways.
Frequently Asked Questions
What does it mean to publish to the distributed Web (DWeb)?
If you decide to turn the “Publish to Distributed Web” toggle on, your site will become available through the following peer-to-peer protocols: InterPlanetary File System (IPFS) and Holepunch (formerly known as Hypercore) – these are just two of many distributed (DWeb) protocols that exist today. By publishing through Sutty, you are also making your web page available on the World Wide Web (WWW) using Hypertext Transfer Protocol (HTTP), the web protocol that is most widely known and used:
For example, if your site is https://ilovecapybaras.com on the World Wide Web, your site will also be available at
or served via our dedicated gateways on
Depending on the protocol, your website will be published, stored, and accessible through different technical means.
How can someone access my site through the DWeb?
You can use the following browsers to access content on the DWeb:
Agregore – IPFS, Holepunch
Brave – IPFS
Opera – IPFS
What are the benefits of publishing my content to the DWeb?
Creating multiple ways for people to publish and access content on the web helps make websites more accessible, resilient, and censorship-resistant. It means that your content is not dependent on a single web server. It allows readers to access your text from machines closer and faster to them. It lets supporters of your site create copies of the site that others can use, sharing the burden of hosting and making distribution an act of mutual support. Each protocol has its benefits and challenges. These DWeb protocols are younger and less well-adopted than the traditional web, but they have great potential as tools to make digital knowledge less dependent on centralized services. Part of the goal of Distributed Press is to have more people publish to the DWeb to expand the realm of possibility and be able to compare and contrast best use cases for each protocol.
By publishing your web content on the DWeb, you will be on the bleeding edge of digital publishing. This means the risks and benefits are subtly different from the web you may be used to.Roughly speaking, data can be harder to delete on the DWeb, and while it can protect the privacy of publishers better, it can make readers more visible to third parties. While the pros and cons are complex and may require additional thought for your project. publishing to the decentralized web means you get to shape the future of a web that we believe could be more equitable and empowering.
By using this tool and giving us your valuable feedback, you can help us make distributed publishing better for everyone. We can’t do it without you!
What is the story behind this and what are the motivations behind this feature?
This feature reflects the mutual cooperation between Sutty and Hypha Worker Co-operative, by integrating tools developed by their respective projects, Distributed Press and the Sutty CMS. It is a free and open source implementation that enables people to publish digital works (blogs, magazines, resource guides, and more) to the distributed Web (DWeb) without having to navigate deep layers of protocols and infrastructure.
Sutty is a platform created in 2017 for publishing static web sites built for and with activists and social organizations, working for the democratization of a set of tools that, in the context of a technical resiliency and human rights strategy, results in a platform to make our voices heard.
Distributed Press originally emerged out of discussions between Mai Ishikawa Sutton, Benedict Lau, and Udit Vira, of Hypha Worker Co-operative in 2019 following DWeb Camp. They wanted to develop a suite of tools that would enable people to publish web content to the DWeb, because they saw how problematic centralized publishing had become.
This tool aims to protect people’s publications from the whims of big gatekeepers. Mainstream corporate platforms centralize web content both technologically and organizationally, enabling them to censor websites, control how people use their services, and undermine their ability to receive fair compensation for their creative labor.
When both projects met in 2021, we found our goals and perspectives aligned, so we partnered to bring this feature to reality.
What are your goals?
Our shared goals are to improve content discoverability and archiving, fight political censorship and misinformation, while supporting offline distribution, new monetization channels, and fair compensation for those who publish their works to the web. We aim to do this by building publishing tools that put control over the means of publication in the hands of organizers, artists, journalists, and those in offline communities.
Ultimately, this project exists to ensure the power of humanity’s most important information is never compromised, abused, or ruled by any single entity. We believe that a more interoperable, distributed web is only possible if it’s built through cooperation and collaboration among those who are building the tools and those who have the most to gain from more democratic and inclusive digital networks.
Will I be able to turn this option OFF once my site is published? In other words, can I delete my site from the DWeb if I change my mind later?
For the most part, yes. If you turn off the “Publish to DWeb” toggle in the Sutty CMS, we will push cleared (empty) versions of the site for the DWeb protocols. Most clients (aka browsers) will respect that delete, unless someone explicitly made a copy and they are viewing the site locally, from their own computer or a local server.
Please note that even on the World Wide Web, people can also take screenshots or archive your site. So even with HTTP versions of web pages (the primary means of publishing and accessing websites), it is nearly impossible to know if someone may have a copy or photo of sites, even if it has been taken down from its host server.
The best way to think about it is that even though the toggle is ON/OFF, it is more like a sliding scale of availability. By publishing to the DWeb, you are making your website even more available to people than if it is only published on the World Wide Web. When you turn it off, it will no longer be served to people who visit your site through IPFS and Holepunch, but that does not mean it is deleted from the entire web.
If I turn this option off, is there a way to know if there are already copies of my web page and its contents on the DWeb?
It is technically possible to see how many “peers” there are for your site before you delete it (this is a feature we are hoping to develop in the future). However, it will not tell you how many devices have downloaded it in the past and whether their clients will attempt to load the “cleared” version of your site when they come online. It is most likely that any peers that have actively loaded your site will be following changes and will load the cleared version, but it is not an absolute guarantee.
What are the differences between IPFS, Holepunch, and BitTorrent?
The main difference between DWeb and World Wide Web is how and where someone publishes and stores web content, and how someone else retrieves and views that content.
Hypertext Transfer Protocol (HTTP) – This protocol is what most websites use today. It works by having a central server which clients will request data from based on a hyperlink. The server can also accept new data and update its private copy. In general, a server can serve _anything_ for a given link to any particular user and a user has no guarantee that they aren’t getting content that’s different from what others are seeing. Part of the reason it is this way is that a link can contain any arbitrary text:it’s up to the HTTP server to make sense of what data that relates to.
InterPlanetary File System (IPFS) – IPFS is a peer-to-peer protocol that uses a method called “Content Addressing” where the link for referencing some data is based on the content of the data itself. Specifically, the link is a Content ID (CID) which is the result of passing the data through a hash function. This makes it possible to fetch data from any source and verify that it has not been tampered with. This is how IPFS can be used with peer-to-peer protocols to load parts of a website from anyone that has a copy instead of a single server. IPFS finds peers not just for the website, but for individual files within a website, so if several sites depend on the same video for example, they will share peers to help load the file to newcomers. Learn more: Official IPFS Documentation.
Holepunch (formerly Hypercore) – Holepunch uses content addressing under the hood for data integrity, but on top of that it builds efficient “append-only logs” – data structures which makes it fast to exchange several chunks of data at once. It also links to data based on a “public key” which enables verification of data that changes over time. Holepunch has built-in versioning so older versions of a site can be persisted and accessed at a later time. Learn more: Official Holepunch Documentation.
BitTorrent (coming soon) – BitTorrent is one of the early success stories of peer-to-peer file transfer protocols. Like IPFS it uses content addressing, however, instead of using content addressing on individual files, it generates a single “infohash” which is used to track the dataset as a whole and does not attempt to reuse peers between sites. The main advantage of BitTorrent is that there are already many clients out there for it and it is a stable and proven technology. Learn more: Official BitTorrent Help Center.
Is Distributed Press considered a “Web3” project?
We share some aspects of Web3 projects – we're decentralized and are building our tools to have no single points of failure. But we are not Web3 given that we do not utilize blockchain technologies or a consensus mechanism, and people do not need to participate financially to publish or access works through Distributed Press!
Who is behind this project?
Members and contributors to Hypha Worker Co-operative, based in Toronto, Canada, and Sutty, based in Buenos Aires, Argentina, are building and maintaining this project.
We believe that building free and open network technologies through shared principles must be grounded in a culture and practice of solidarity, cooperation, and trust. As worker-owned cooperatives, we work closely together and with our partners across international borders to build publishing tools that people want and need.
Can I know more about the Sutty CMS and why it decided to make its sites available on the DWeb?
Sutty started in 2018 to build a CMS for resilient sites based on Jekyll technologies, along with new features we developed and contributed to that community.
We wanted to make website development very accessible for activists in our South American context (namely social activists, independent journalists, trans and LGBTQIA+ communities, among others). The project aimed to not only build a platform for creating “better websites”, but also to develop a set of tools to increase the self-defense of marginalized and targeted groups against persecution and censorship. We do this to support the right to free expression (Derecho a la Comunicación) as a Human Right.
That is why we also believe in a sustainable, resilient internet made with a plurality of voices and protocols! We tried to participate and make contact with several communities working on DWeb tools. That is how we fortunately found Hypha Worker Co-operative, COMPOST, and Distributed Press – they were already working on decentralized publishing. We are excited and honored to work with them on this project!