HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ssbc
patchwork
JavaScript2016–2024
ssbc / patchwork · Archived

patchwork

A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB).

32Distinct people
35Mentions
0Explicit recommenders
3.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB).

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year35 dated mentions

Observed mentions: 2016-02-22 05:40:15 UTC to 2024-07-27 02:23:46 UTC.

051015202016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 18 mentions; 1 submissions, 17 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC615
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC18117
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
⚠️ Patchwork v3.18.1 was the last release! ⚠️ This release is meant to tide us over so that other clients can take it from here. Thank you to everyone who contributed to this release and all the ones preceding it! Paul, Matt McKegg, and Christian Bundy first and foremost, but by now the contributors page shows 94 contributors! 💓 Where do we go from here? Do I have to change client now? For the time being (the next couple of months) you should be fine to just keep Patchwork running. However, as time progresses and security of the underlying components "degrades" (read: already existing issues are discovered) it will become a bad idea to keep running Patchwork. By that time, you should pick a different ssb client. Why retire Patchwork? Can I keep it alive? Of course Patchwork is, as always, released under the AGPL license. So if you really wanted to, you could fork it and keep it alive. However, let me (Daan) explain why this is a bad idea: All the devs say "Don't do it!" Everyone who has spent significant time in the codebase agrees that it is time to retire Patchwork. Over the years, it has seen multiple iterations of developers coming in, trying to change things in a structural way, then burning out on it. It's a pattern, so be warned. This is due to the fact that Patchwork makes some architectural decisions that make it hard to maintain, and even harder for new developers to get into the codebase: depject is a bespoke dependency injection system, which breaks any kind of navigation and tool support for debugging. mutant is another bespoke implementation of observables. It is also used for generating HTML, which makes a transition to component-based UI toolkits very hard. custom sbot: Patchwork doesn't really work except with its own, bundled ssb-server. This is considered bad form for ssb applications. ssb-db, the bespoke database of the original ssb stack, is deeply baked into patchwork. Migrating to the new #ssb-db2 would be a long and painful process. This is compounded by the fact that patchwork bundles a few custom plugins for ssb-db. I want to be clear that none of the above are impossible to solve; in fact, they all have straight-forward but labour-intensive solutions. I also want to be clear that these technological choices were all made for good reasons at the time, and I am sure you're as greatful to the developers who made them as I am, for putting their (overwhelmingly volunteered!) time into the project, and for making Patchwork the application that it is. In combination however, the above issues mean that new developers are faced with a very, very steep leaning curve before they're able to even make small changes. Given all of the above, it makes more sense to deprecate Patchwork and focus our efforts on projects like #oasis or #manyverse which are nearing feature parity with Patchwork. If you want to get involved with ssb development, both are great projects for that; they are much more hackable than Patchwork, and follow standard techniques & workflows, so you'll feel right at home. If you do, against all advice, want to continue developing Patchwork then we kindly request you rename it to reflect the change in leadership. Original Readme A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB). Features Connect with friends without depending on any central servers. Don't worry about spam, you only get messages from people you follow. Use Patchwork online or offline, the data you need is stored on your device. Sync messages with friends when you're on the same Wi-Fi network. Keep secrets with private messages, which are always end-to-end encrypted. Change and improve Patchwork however you'd like, it's free and open source. Usage New to Scuttlebutt? Join the network by connecting to a pub. Choose a pub from the pub list and copy an invite code. Open Patchwork and select Join Pub. Paste the invite code and select Redeem Invite. You're done! Check out #new-people to see who else has recently joined. Installation Most people should download Patchwork for Windows, macOS, or Linux. Alternatively, you can install Patchwork with your favorite package manager. npm: npm install --global ssb-patchwork yarn: yarn global add ssb-patchwork brew: brew cask install patchwork yay: yay -S ssb-patchwork Building from source? Check out INSTALL.md for more information. Contributing Create a new issue to report problems or request features. See CONTRIBUTING.md for more information on how to get involved. You can also support the project via donations. Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Also patchbay ssb-server manyverse License AGPL-3.0
Read the full README on GitHub

What Hacker News says

35 sources
You're effectively describing Scuttlebutt in a nutshell. Small communities that are formed ad-hoc by peering with each other. "Follow" mean you'll help replicate their content for others who follow them + you. Scuttlebutt is already successful even though it's very small so far. Tags and other things can be used to explore content on the network, as long as you've found an entry-point. I'm a bit split about spreading the word about Scuttlebutt, I don't want to ruin it since it's already so great. But felt it was very related to what you were writing, so here goes nothing :) In case you wanna join: https://scuttlebutt.nz/ The client I'm using is https://github.com/ssbc/patchwork
In Social Networks: It's worse than you think (2020)
Fediverse is such a poor design. It's utterly futile. The ID is tied to a host, so every time you lose your host, there's a lot of work to do, because you don't own your account - your host do. You basically have to start from scratch every time, so what's the point? Better to use Twitter, at least there's some chance they will not dissapear out of the blue. Identities should be self-generated, and independent of any hosting. Fediverse hosting should just facilitate passing stuff when peers are offline. Then it wouldn't matter if you're on one server or other, because it wouldn't be even visible in the UI. https://github.com/ssbc/patchwork had some more interesting ideas, but AFAIK execution was rather poor.
In Centralisation and Mastodon
This technology exists, it just needs to be more widespread. Scuttlebutt[1] is a system for building peer to peer applications. It's main use currently is social networking[2] but someone has already implemented a git store /GitHub alternative on top of it[3]. Nobody controls the network so it can't be censored. If we can get more developers building on top of it we could have a much more decentralized internet. [1] https://scuttlebutt.nz [2]https://github.com/ssbc/patchwork [3]https://github.com/noffle/git-ssb-intro
In Tell HN: GitHub deleted anti-censorship activist repositories
Pub servers are very much considered a temporary workaround in the Scuttleverse, and there is a lot of ongoing work to make onboarding both more directly user-friendly, and also less dependent on "having an anarchist sysadmin in your friend group". Right now, without pub servers you can: 1. find friends in your immediate vicinity over WiFi/Bluetooth/etc.-type nearby protocols. 2. if you have a friend (see #1), you can connect to friends-of-friends (#1 may seem extremely limiting at first, but it's actually only limiting for a technology which is not popular in your local area—network effect problems—so "in theory" it's not really so bad when you think about it. I've probably added a good portion of my FB friends in their presence) However, one of the main alternatives being actively worked on is DHT invites. This is basically the "torrent
Read the rest
magnet link" equivalent for SSB. See various links to work on this below: [0] https://gitlab.com/staltz/ssb-dht-invite [1] https://gitlab.com/staltz/manyverse/issues/186 [2] https://github.com/ssbc/patchwork/pull/862 [3] %r6dTZ4WG7kuLFfGlUR1DAhyat7YEuX682mGI9UJXlc4=.sha256
In Three protocols and a future of the decentralized internet
The examples you listed gained many users because they were (and are) sharing content that they do not own. Imagine peer to peer sharing of personal photos and videos by the users that own the copyright. The difference in outcome may be due to less economic incentive. It's easy to share photos on instagram and it's much more difficult to, say, download 20 academic papers without emptying one's bank account. There is a cost to the user to sharing photos with instagram. The cost hasn't been realized by the average user. https://github.com/ssbc/patchwork/
In Centralized Wins. Decentralized Loses
I'm not a user, but I have been watching it (and its related projects on github). I believe Patchwork[0] is the social network you joined, and it is based on scuttlebutt[1]. It seems like very early times for most people even considering the downsides of centralized 'social media,' and it will take time and hand-holding to demonstrate the alternative possibilities. A great client app that could unify the user experience, but offer power-user features could go a long way. Most people that I know (older) are not overtly interested in participating in any public social network (i.e. Twitter). I wonder if one could build a more closed, private, white-list-default (triple opt-in!) type of social network on top of SSB with the right client software? [0] "A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)." https:
Read the rest
//github.com/ssbc/patchwork [1] "A database of unforgeable append-only feeds, optimized for efficient replication for peer to peer protocols" https://github.com/ssbc/secure-scuttlebutt
In Mastodon Is Better Than Twitter: Elevator Pitch

Showing the 15 most recent of 35 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.