---
# System prepended metadata

title: Distributed Press / Sutty Communication Plan

---


# Distributed Press / Sutty Communication Drafts

## Fediforum Participation Announcement

### Title: Distributed Press is at Fediforum this week!

### Social Posts

* Tag Mauve, Akhi, fauno, Sutty, Fediforum, Fedi hashtags
* 

### Content

We're thrilled to be at Fediforum this week to present our latest tools! For the past year, we've been working on bringing distributed hosting to the Fediverse, to create better, more customizable social interactions built atop ActivityPub.

Come check out our talk on [DATE / TIME] here: [LINK TO SESSION]

Here's a sneak peek of our presentation:
* **No-code publishing to the distributed web:** Sutty CMS is a graphical, user-friendly interface for static Jekyll-based websites. With a click on a toggle, you can publish your websites to IPFS, Hypercore, and of course, HTTP. 
* **Social Inbox:** Publish a profile and post your website's contents directly to the Fediverse. Other accounts can follow your websites, and replies to your Fedi posts can be moderated and published on your for sites through a back-end moderation panel on the Sutty CMS. It also allows instance-level allowlists and blocklists. We've automated announcements so others can easily subscribe and follow your website posts on the Fediverse.
* **Social Reader:** A new ActivityPub client that supports natively loading published data over p2p protocols, skipping the need for always-online HTTP servers for accessing content. It also gives you more precise controls over the content that you interact with. 

### We'd love to connect with you! 

Especially if you're building or strategizing around:
* Payments and sustainable funding on the Fediverse
* Peer-to-peer and distributed publishing 
* Fediverse adoption by medium to large organizations

Hope to meet some of you there!

~ The Distributed Press Team









## PAST 

Distributed Press 

Building Decentralized Tools for Publishing and Hosting 

Distributed Press creates beginner-friendly, open source publishing tools that offer creators an alternative to centralized publishing platforms. With FFDW’s support, Distributed Press has built out a user-friendly, DWeb-native, no-code publishing platform that is both scalable and easy to adopt. The project automates the publishing and hosting of content using decentralized protocols like IPFS and Hyper through the Sutty static website platform. Their Social Inbox feature integrates a website’s comment section with federated social media platforms like Mastodon, allowing sites to engage with readers directly on the Fediverse through the ActivityPub protocol.

Distributed Press has also developed a digital publication called COMPOST, a magazine about the digital commons. COMPOST is designed to live test Distributed Press and research distributed publishing features directly with communities of artists, journalists, and more. All of these features are integrated into the Sutty CMS to facilitate adoption for non-technical users, including a magazine template created for new COMPOST editions and other DWeb publications.

About: Distributed Press is a free and open-source tool for publishing text and other multimedia works to the DWeb. 



## Distributed Press Social Inbox Release Posts

Ruby development: fauno, jazzari
UXDI research team: elio, dilit, edu
Communications: ania, elio
Website and template integration: develover, elihu, elio
Testing: maki, dilit
Project management: ania, fauno, elio
Graphic design: develover
Translations: maki, elio
Fediverse inhabitants: maki, nula
Emotional support/facilitation: dilit, elio


### Social Media

We're thrilled to announce the release of the Social Inbox, a new feature of Distributed.Press that integrates a website's comment section with the Fediverse!

It allows readers to directly engage with your posts where they already are, and gives publishers the ability to incorporate public dialogue into their websites. 

Full announcement here: [DRIPLINE URL]

-

Distributed.Press incorporates existing dweb protocols to expand the possibilities of digital publishing. It became important to incorporate ActivityPub into Distributed.Press given its flexibility and now popular use as a social media protocol. 

Through our existing suite of tools, it's already possible to publish static Jekyll (https://jekyllrb.com/) websites to the dweb. The benefit of static websites is that they load faster, don't rely on plug-ins that require constant updates, and tend to be more secure overall. We realized that we could lean on these features, while incorporating social interactions into websites using ActivityPub. 

So over the course of this year, we built the **Social Inbox**, which allows people to integrate their website with the Fediverse and to engage with readers there. 

-

With the Distributed.Press Social Inbox enabled on your site, you can:

* **Post to the Fediverse**: New articles can be posted to the Fediverse where followers can read, re-post, favorite, and send replies.

* **Approve replies as comments**: When posts receive replies on the Fediverse, the website owner can approve them as reader comments that are then posted alongside the original article on the website.

* **Streamline moderation**: Approve messages and follow requests one-by-one, automate the process on your own, or subscribe to existing block lists. (For now, Distributed.Press subscribes to GardenFence (https://github.com/gardenfence/blocklist/tree/main) to automatically block servers that have shown to be sources of hateful rhetoric, harassment, and spam.) 

* **Download your follower list**: If you would rather move your account to a different server, you can switch your Social Inbox instance very easily without needing to change the domain name for your site.

-

We also have a new *COMPOST blog*, which has the Social Inbox enabled. We created a blog to post updates about dweb publishing, along with updates about COMPOST and our sister project, Distributed.Press.

You can follow along, read, and reply to our posts at @posts@news.compost.digital.

-

Want a step-by-step guide on how to implement the Social Inbox through @sutty@todon.nl's static website CMS? Check out our demo video: https://youtu.be/ntTdIuC0bbM

-



-

You can follow Hypha's Dripline blog, which has implemented the Social Inbox, at dripline@hypha.coop

-


### Emails

SUBJECT: Announcing Distributed.Press Social Inbox 1.0

Hi there,

Hypha Worker Co-op and Sutty are thrilled to announce the release of the Social Inbox, a new feature of Distributed.Press that integrates a website's comment section with the Fediverse!

With the Social Inbox enabled, websites get their own account on the Fediverse, allowing it to automatically send out new posts to followers at the time of publication. When other users reply to posts, you can approve them to be published to the site as comments. The Social Inbox allows readers to directly engage with your posts where they already are, and gives publishers the ability to incorporate public dialogue into their websites. 

Full announcement here: [DRIPLINE URL]

If you have any questions or comments about this new feature, send us an email at hello@distributed.press, or get in touch with us on the Fediverse at @compost@social.coop. 

We also have a new *COMPOST blog*, which has the Social Inbox enabled. We created a blog to post updates about dweb publishing, along with updates about COMPOST and our sister project, Distributed.Press.

You can follow along, read, and reply to our posts at @posts@news.compost.digital.

Thank you for your support!

warmly,
mai



- boris
- cab
- dweb
- kev
- ira
- 




## Distributed Press v1.0 Release Twitter/Fedi Thread

1 - 
🔊We’re thrilled to release Distributed Press v1.0! 🔊

This release introduces two major features that radically simplifies the process of publishing to the decentralized web (dweb) – for now, that means two prominent dweb protocols, @IPFS and @holepunch_to. 1/9

2 -
We integrated our API into two static website generators, so now you can either:
1 - Use @SuttyWeb's CMS to publish your site to the dweb as easily as using Wordpress, and
2 - Use Github Actions to publish your site by adding a single step to your actions workflow. 2/9

3 - 
With @SuttyWeb’s CMS platform, you can use a user-friendly graphical interface to author posts and customize your website, then go to the configuration panel to publish the site to IPFS and Holepunch, in addition to the HTTP version. 3/9

4 - 
If you want to try using @SuttyWeb’s CMS to publish a blog or simple website to the dweb, we have step-by-step guide on how to use Sutty’s publishing platform on our documentation site: https://docs.distributed.press/deployment/sutty 4/9

5 - 
Our second feature allows you to add Distributed Press to your existing GitHub Actions publishing flow and “DWeb-ify” your website. All you have to do is add an extra step to upload the static site folder over HTTPS.

Here's our step-by-step guide: https://docs.distributed.press/deployment/github-actions 5/9

6 - 
Our new documentation website is built with Next.js. https://docs.distributed.press
Everything there is to know about how Distributed.Press works, as well as steps to self-deploy your own instance and upload data to it can be found there in our Docs. 👆 6/9

7 - 
We're releasing Distributed Press v1.0 as the third issue of @COMPOSTMag is finalized.

We're working on a building out a new theme in @SuttyWeb’s CMS based directly on COMPOST’s layout, so that anyone can make their own magazine and publish it across new dweb protocols. 📰🕸️✨ 7/9

8 -
Please try out Distributed Press v1.0, and let us know how it can be improved by writing to us at hello (at) distributed (dot) press or DM’ing us. The only way we can improve our tools is with your feedback. 🙏 8/9


8 - 
Finally, all of this was made possible thanks to invaluable insight & support from @FFDWeb! If you want to support us directly, you can do so my becoming a monthly contributor or supporting us with a one-time gift on our Open Collective page: https://opencollective.com/distributed-press 

Onwards and upwards! 9/9


## v.1 Release Strategy - April 2023
[ ] Post tweets/posts
[ ] Send FFDW package
[ ] Send mailing list - cc sutty@riseup

### Social media
[ ] FFDW Matrix channel
[ ] COMPOST channels
[ ] DWeb accounts





* Communication strategy
    * Sutty
        * Twitter
        * Telegram
        * Instagram
        * Fediverse
MASTODON: @sutty@todon.nl
or 
https://todon.nl/@sutty
    * DP/COMPOST
        * COMPOST Twitter
        * COMPOST Instagram
        * COMPOST Fediverse
        * DP Twitter
        * >> Create DP Fediverse
    * Announcements/messages
        * Collaboration between Sutty, Hypha/DP/COMPOST  *1st, this is the WHAT*
        * Centralized vs decentralized solutions *2nd, this is the WHY*
            * >> Build out messaging around this
            * >> Dig into the "ecosystem" that's been creating solutions for authenticity, documentation, etc which are Starling, Proof, Witness...
        * FFDW partnership announcement
        * Sutty's story of partnerships with collectives
            * How they build out their templates based on need
        * DP Profile
            * X-post from Sutty and COMPOST
        * Messaging towards end-users/target audience
            * Journalists; environmental activists; artists; community networks
            * Those who've been censored; offline communities
            * Small messages for them: "Have you have issues with website takedowns?"
            * Raising awareness of distributed technologies
            * Engage them in discussions about these issues
            * Which experiences have you had with "the old web" and what do you expect from new developments?
        * Technology considerations 
            * How we decide which paths to go down
            * Ex. DIY >> Do It Together
            * What are other similar projects that are doing this work and what do their solutions look like?
        * Concepts:
            * decentralization does not mean isolation, we should be inter-dependent
    * Goals
        * Build awareness around distributed tech
        * Invite and engage people to shape and reflect on the tech
* Audiences
    * Sutty users
        * What is DWeb, what is distributed press, what are these protocols?
        * DWeb community not familiar with Sutty (level 3) to try it out, get their friends to try it out

## Meeting March 29, 2023

### Participants
Ania, Elio, Mai

### Agenda
* Updates
* Define dates
* What's next?

### Comms TO DOs
- Social media: April 5, 2023
    - Twitter/Mastodon thread - IG posts
- "Learn more" helper: TUES April 4, 2023
    - **WIP, very advanced.** Mauve, Fauno and Jacky invited to check for errors and fill out the protocol missing parts.
- Blog posts: TUES April 4, 2023
    - Mai and Mauve doing a post for people who are familiar with dweb, how to use it? DWeb, COMPOST, etc. >> https://hackmd.io/37pUvS3rSsG_yZpJyASX4w
    - Ania's text can be used for people who are unaware - Sutty users and "general audience"
    https://docs.google.com/document/d/1X0TkzfW9FFCK9mKfwgve-3Bhe4oyx9xOB0MIokmXmjk/edit?usp=sharing
- Emails: FRI April 7, 2023
    - Messaging for partners and FFDW
    - Newsletter announcement
    - >> Links to blog post and Learn More page
    - >> Shortened version of blog post?

### Notes
- FFDW will announce it that week
    - They asked to send them our tweet thread 



## Meeting March 22, 2023

### Participants
Ania, Elio, Mai

### Agenda
* 1 - Communications milestones
* 2 - What are we communicating?


#### 1 - Communications Milestones
* 1 - Learn More page
    * Draft: https://docs.google.com/document/d/1Jw7GtYEfp3UPLdQGoLTDn0Bmu2PpA_pE9ox7W7nPMRA/edit?usp=sharing 
* 2 - Blog posts
    * I. COMPOST/Hypha Blog
    * II. Sutty (in Spanish)
* 3 - Social media posts
    * Instagram
    * Twitter/Mastodon
    * Video walkthrough
    * Sutty
        * Beta release
        * New feature
* Press release - Very basic info with links
    * New feature + what it's about
    * First step in a bigger project, this is Beta
    * Please test it and feedback
* Feedback - How do we receive it?
    * Form? Email?

#### 2 - What are we communicating?
* "Sutty has a new feature!"


TO DOs
[ ] MAI - Finish rough draft of Learn More page
[ ] ANIA - Social media framing document - level 3 / 4
[ ] ELIO - Sutty feedback form questions
    
## Meeting March 2, 2023

### Participants: 
Mai, Ania

### "Learn More" Page

* Outline
    * Introduction to DWeb publishing
        * Problem with centralized publishing
            * From FFDW partnership announcement: 
                * We exist to ensure the power of humanity’s most important information is never compromised, abused, or ruled by any single entity.
                * Many people are familiar with centralized publishing platforms, like Medium, SquareSpace, or Wordpress. These platforms are convenient and easy-to-use. They come with a built-in audience and distribution channels. They also come with tradeoffs – from subscription fees and link rot, to questions of content ownership and data privacy.
        * Solution we identify:
            * Decentralized publishing is an alternative, where resilient, decentralized infrastructure enables individuals more control and ownership over content.
            * We want to see a CMS that allows people to create and publish their content to the distributed web without having to navigate deep layers of protocols/infrastructure
        * Limitations/considerations
            * All the content is immutable -- very difficult to delete once it's published >> You need to be cautious about what you publish if you might want to take it down later even if we provide the ability to push an "empty" version of the site, people can still copy it
            * Everything is new, we're still building it and we may have limitations in this way
            * This may not be an option for you if you need things to be deleted
            * This is still an EARLY release -- we are still ironing out issues. Don't put anything sensitive here, that may pose a threat to yourself or others
        * Feedback
            * Because this is still new, we really would love your feedback on this!!! 
        * Terms to use: resilient, censorship-resistant, local-first, p2p, 
    * Project description
        * Links
        * How we built this
            * Building cooperative, shared/free and open publishing infrastructure
        * Donate links: Sutty, COMPOST, Distributed Press
    * Definitions
        * IPFS
        * Hypercore/Holepunch
        * BitTorrent
        * Decentralized Web
            * Link to getdweb.org
        * Peer-to-peer
    * FAQ
        1. Will I be able to turn this option off once my site is published? In other words, will I be able to delete this later?
            * Possibility of deletion
                * Push a deleted version instead -- most clients will respect that delete, unless someone explicitly made a copy
                    * Copies are made of mutable versions
                    * Make it easy to respect deletes
                    * Toggling off will clear the data for the site and share that cleared version
                * We can clear it from DP's IPFS and Hypercore nodes but not yet
                * Anyone can take a screenshot or archive your site anyway
                * Sliding scale, not an on or off
        3. If I turn this option off, how do I know for sure if there are already copies of this data on the dweb?
        4. What are the benefits of publishing my content to de dweb?
        5. Is this Web3? 
            5. "Yes and...2 -- We share some aspects of web3 projects because we're decentralized, and there are not single points of failure. But we are NOT web3 given that we do not apply consensus mechanism, and you don't need to participate financially to publish and be part of it
* Draft for "Learn more" post in Sutty
    * Graphics
        * ???
        * ???

* Notes re: Learn More
    * Example: https://sutty.nl/en/hidden-sites-with-tor/
    * Contents: DP intro explainer, graphics, donate link, how we built this, what this project is about
    * TERMS/PHRASES
        7. "Building power by cooperating" and trust 
        8. Resilience
        9. Where people can view the resilient sites: Brave and Agregore
    
    
    
## Meeting Feb 28, 2023

### Participants: 
Mai, Ania

### Action Plan
* Launch date for Sutty x Distributed Press in March
* "Learn More" page from DP toggle in Sutty
    * FAQ, English/Spanish
* COMPOST / Distributed Press Newsletter
* Social media / comms strategy
    *  Objective
    *  Audiences: Technologists, journalists, artists?
    *  Ex. Coati - Live testing experience for us, COMPOST theme or other theme?
    *  >> Select projects/allies to use it and highlight them as case studies
        *  Ask them to trial it, give us feedback, and interview them
        *  Projects - Coati; Servelots; Portal Sem Porteiras; 
        *  People - Ngoc, Luandro, 
* Social media plan based on strategy
    * Graphics, visuals
    * >> Chat with Ivan re: social media graphics
    * Pinterest for visual inspiration
* Blog posts
    * Deadlines!!
    * List
        * "Learn More" page for DP Toggle - Ania, Mai
            * Definitions, FAQ, Take from FFDW blog post
        * Technical deep dive Distributed Press - Mauve
        * COMPOST piece about Distributed Press - Mai, Jacky, Ania, Mauve 
        * What does distributed web publishing mean? - Protocols, people and projects that would use it
        * 

### Notes
* COMPOST gives a good structure for Coati (for ex.) to present their work, make their sites look more institutional



## Meeting Feb 10, 2023

### Participants: 
Mai, Sofia

### Agenda 
Sorting out all the comms channels
* Platforms: Instagram, Twitter, Mastodon, Newsletter
* Organizational: Hypha and Sutty
* Projects: Sutty CMS, COMPOST, Distributed press
* Languages: Spanish and English

### Notes
What is the objective or goal of promotion is?
* Education? Brand awareness? Key message? Action item?
* One or two things that should be considered and is the aim
* What do we want to focus on the most?
* Which platforms we're utilizing for different purposes, and which audiences we're trying to get in front of?
* Throughline for what we're posting
* High-level objectives
* Having a specific account for DP makes sense

Twitter vs. Mastodon
* Can A/B test between the platforms
* Makes sense to cross post for now
* Long form version on Mastodon, vs shorter-form on Twitter

FF vs. FFDW
* Filecoin Foundation: Getting behind what the Filecoin network is doing
* FFDW: Project partners, funding, etc.

TO DO
[] Send Sofia where we're posting what
[] Add Hypha + Sutty on the DP profile as collaboration, and beta release announcement


    
## Meeting Feb 7, 2023

### Participants: 
Ania, Mai

### Agenda
* Toggle language review
* Review and finalize social media posts
* Distributed Press website text brainstorm
* Brainstorm distribut blog post

#### Toggle language review
* Sutty folks liked it
* It's a good start -- it can be polished later
* Work in the "Learn more" - we could link to FFDW blog announcement?

#### Review and finalize social media posts



## Meeting Feb 2, 2023

### Participants: Ania, Mai

### Agenda
* Review the wording for the toggle button ("Publish to the Distributed Web"? title and description)
* Reviewing draft social media posts

DRAFT TOGGLE DESCRIPTION
>> Lives in the Configuration under "Where do you want your site to be hosted?"
>> "distributed" seems to be much more widely used than "decentralized"

* Toggle text

((O-->) Publish to the distributed Web

Make your site available through peer-to-peer protocols, Inter-Planetary File System (IPFS), Hypercore, and via BitTorrent, so your site is more resilient and can be available offline, including in community mesh networks.

Important: Only use this option if you would like your data to be permanently available. If you decide to undo this selection, a cleared 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 indefinitely.

[LINK: Learn more]

* Main title
    * Publish to the decentralized Web (DWeb)
        * Jacky: Decentralized on what access? Just technical? Seems like its spread out, like a lone wolf feel
            * >> Interdependence
    * Publish to the distributed Web
        * Fauno: always used "distributed", more historically correct and values aligned
        * Mauve: p2p web, local-first web?, it's "Distributed Press", more positioned to be the dweb thing
        * Jacky: Always uses this term the most, feels the most correct
    * Publish to Web3
        * Mauve: term is overloaded, big competition for SEO
* Brief description
    * Publish your site to other web protocols like Inter-Planetary File System (IPFS), Hypercore, and as a Torrent
    * Publish your site to Inter-Planetary File System (IPFS), Hypercore, and as a Torrent 
    * Make your site available through peer-to-peer protocols, Inter-Planetary File System (IPFS), Hypercore, and as a torrent
        * Mauve: Likes this most; peer-to-peer protocol
    * Publish your contents through decentralized infrastructures built by Distributed Press
        * Notes
            * Fauno: Materials aren't available in Spanish so we would have to translate
            * Add mention to Distributed Press
            * Don't link to the protocols directly in the brief description
            * Mention the protocols so those who are interested in them will know what it is, 
    * Benefit?
        * So it's available even if the World Wide Web is inaccessible
        * So it's available offline and in autonomous community mesh networks
            * Fauno: This one might be best
        * This may enable your site to circumvent censorship and be available in offline contexts
        * ... and have greater control over your data?
            *  Fauno: Contradictory, not accurate to say greater control
        * So your site is more resilient, it can be available offline, and in mesh networks
            * >> WORKSHOP

    * ** Warning ** 
        * Important: This will mean your site will never be able to disappear completely
        * Important: Do not use this option for data that may need to be permanently deleted in the future. **While it's possible to un-do this action whenever you want**, that doesn't prevent nodes on the decentralized storage network from retaining copies of the data indefinitely.
            * Notes
                * You can toggle it off but it won't stop copies from being made
                * Too many negatives, make it positive
                * This tool will make it digitally permanent, 
                * "Be aware that even if you stop sharing your data, others might retain a copy of it" 
                * Push a deleted version instead -- most clients will respect that delete, unless someone explicitly made a copy
                    * Copies are made of mutable versions
                    * Make it easy to respect deletes
                    * Toggling off will clear the data for the site and share that cleared version
                * We can clear it from DP's IPFS and Hypercore nodes but not yet
                * Anyone can take a screenshot or archive your site anyway
                * Sliding scale, not an on or off
        * Important: Only use this option if you would like your data to be permanently available. If you decide to undo this selection, a cleared version of the site will be shared in its place. However, it is possible that nodes on the decentralized storage network may continue retaining copies of the data indefinitely.
* Link to external page or blog post with deeper explanation
    * Draft for "Learn more" post in Sutty
    * Example: https://sutty.nl/en/hidden-sites-with-tor/
    * Contents: DP intro explainer, graphics, donate link, how we built this, what this project is about, link to COMPOST
    * **FAQ** 
        1. Will I be able to turn this option off once my site is published?
        2. If I turn this option off, how do I know for sure if there are already copies of this data on the dweb?
        3. What are the benefits of publishing my content to de dweb?
        4. Is this Web3? 
            5. "Yes and...2 -- We share some aspects of web3 projects because we're decentralized, and there are not single points of failure. But we are NOT web3 given that we do not apply consensus mechanism, and you don't need to participate financially to publish and be part of it
        6. Explain each of the protocols
    * TERMS/PHRASES
        7. "Building power by cooperating" and trust 
        8. Resilience
        9. Where people can view the resilient sites: Brave and Agregore

![](https://i.imgur.com/pDx3HC9.png)

![](https://i.imgur.com/GevOJQu.png)



## Meeting Jan 31, 2023

### Participants
Ania, Mai

### Agenda
* FFDW Announcement blog post
* Review the wording for Compost theme (title, description)

* Announcements/messages
    * Problem: ?? *this is the WHY*
    * Collaboration between Sutty, Hypha/DP/COMPOST  *this is the WHAT*
    * Our solution: decentralized solutions that have this and that features and vision *this is the HOW*
    * Build out messaging around this
    * Dig into the "ecosystem" that's been creating solutions for authenticity, documentation, etc which are Starling, Proof, Witness...
    * NEXT
        * Beta version is available on Sutty!
        * How to collaborate, give us feedback
* COMPOST theme rename + description
    * Title ideas
        * Magazine
    * Description
        * Version 1: A theme based on COMPOST magazine to create a multimedia publication or journal
        * Version 2: A theme to create a multimedia publication or journal based on COMPOST magazine 
        * Notes
            * Instead of a blog with regular updates, it's designed to be edited and released as contained artifact/publication

## Meeting Nov 30, 2022

### Participants
Ania, Mai

### Communication Ideas
* Styles of communication
    * Video clips
    * IG (collab post), Twitter/Mastodon
* MAIN POINTS
    * Censorship: government, corporate
    * Concrete needs vs. overarching values
        *  Values: Agency; Sovereignty; Interdependent
*  To Dos
    *  MAI: Create DP account on IG
    *  MAI: Create DP account on Mastodon
    *  MAI: Review Social Media Messaging (below) - FRIDAY DEC 2

# To decide
* Instagram for Sutty is in Spanish, and speaks in name of "Sutty the coop"
* Should we have a new account that represents Sutty the CMS and has specific content about how to use it, how to post, why to choose it...? **We decided not to, yet**
* Suggestion: have a clear focus for different audiences, more technical details for Mastodon posts, more social / conversational things for IG/TW posts


## DRAFT WRITING - SOCIAL MEDIA POSTS

SLIDE 1 - What happens when you build a strong online profile and community on a platform... that suddenly changes their policy or pricing and you risk losing everything?
SLIDE 2 - What happens when you record footage of human rights violations directly to your social media account... and the material is taken down with no warning?
SLIDE 3 - What happens when your team manages to launch a brand new website... but constant technical problems require time, attention and resources that make it impossible to maintain?

SLIDE 4 - When these things happen, we lose the ability to connect with our communities in a reliable, safe, and autonomous way. 
For large, gate-keeping tech companies, these might seem like minor exceptions to the rule. But for artists, journalists, and activists who rely heavily on digital platforms, any downtime can be a major blow to their work and livelihoods.
 Those most under threat from corporate censorship need access to the safest, most efficient, most resilient, and light-weight tools. 

SLIDE 5 - This year, Hypha Co-op and Sutty have teamed up to bring distributed, peer-to-peer tools to everyone. It's called Distributed Press.
Sutty's free and resilient website builder will integrate the Distributed Press tool to support anyone who wants to publish magazines, blogs, or campaigns to the distributed Web (dWeb). 

SLIDE 6 - Help us build a resilient web based on autonomy, solidarity, and interdependence.
Sign up to the newsletter (in bio) to find out when the beta release is out!

### SCRATCH

3. What happens when you need to gather information from activists, but the platforms you use endanger their privacy and safety?
5. What happens when your Internet shuts off? Does your whole work disappear?
6. When you are able to choose a digital platform to work onto, how well does it embody the values you believe in?

Make your site available through peer-to-peer protocols, Inter-Planetary File System (IPFS), Hypercore, and via BitTorrent, so your site is more resilient and can be available offline, including in community mesh networks.

For a Web where everyone can participate, Free Software is the most coherent and accesible option.  And in terms of storage and distribution of the content, 

That's why we need platforms where THEY have control and agency. 

Is this the B side of living and working online? Are there no alternatives for this side of Internet?

Most of the privative software available "for free" generates a technical and economical dependency for users, with hidden mainteinance burden and security threats. 
 That is why we created the CMS Sutty, and **keep developing its themes driven by the needs of community-based projects.**

CONNECT WITH: 
* Centralization: censorship; erasure; lack of autonomy
* Decentralization: more resilience, safer, more autonomy >> building this INTO the technology

This year, thanks to a cooperation with FFDW, Hypha Coop and Compost, we are adding distributed technologies to our solution. This allows us to deepen the resilience of the sites, publications or campaigns you can create.

*How do we express the centralized versus distributed technologies?*

# Tech development driven by community-based collectives' needs

Story: independent *book publishers*
The template *“Independent Editorial”* was inspired by our friends at La Bastardilla, a community-based and independent feminist market. As a result of the quarantine, they began to need digital spaces to display their publications. We chatted with them about their needs: easily creating a website that displays as catalog, associating with payment links and online payment methods. They were also concerned by their web positioning. We focused on also getting these catalogs to appear first in web searches, choosing a metadata structure that concurs with the patterns that Google uses to recognize items as objects for sale. Thanks to this, when users search any of those books on the Internet, there will be a much better chance of reaching their website.
Some sites which have been created using our template:

• [[La Disgráfica](https://ladisgrafica.sutty.nl/)]

• [[Tierra del Sur](https://tierradelsur.sutty.nl/)]

• [[Kinky Vibe](https://kinkyvibe.sutty.nl/)]


Story: campaigns

Story: independent radios

