Core contributors often achieve consensus by banning people who disagree. Use these if you ever get banned:
1. Mailing list alternative: https://groups.google.com/g/bitcoin-dev-moderation
2. Delving alternative: Nostr
3. BIP repo alternative: Own repo
4. Core alternative: Knots
Login to reply
Replies (14)
Nostr forum is still badly needed
Isnt @hodlbod 's #Flotilla a solution that is intended for communities? Or is it only for "invite only" forums/chats?
Not really, it’s a single server group chat
The layering of decentralized infrastructure mirrors the inherent redundancy built into Bitcoin’s block propagation; a fascinating strategy for circumventing centralized control.
There are already multiple daily-driver clients that use the forum kind 11 and even a few stand-alone clients.


aitherboard
aitherboard - Decentralized Forum on Nostr
A decentralized forum built on the Nostr protocol. Create threads, comment, and react in a censorship-resistant environment.
what are the other ones?
Imwald, relay.tools, I think mycelium, and some newer ones. I just see them posting in the threads.
Yes mycelium supports kind-11 but I am moving toward API and away from websocket. So you know like a regular forum *but it's nostr events.
Based mercury relay.
Communities should work now riiiiight 😮💨
Give me a week or whatever. 🐇
Knots is not a serious alternative to Core
Do you know of a better alternative that is a fork of the core codebase and has some users?
Just announced:
Announcing #Squalk
Personally, I’m not a fan of real-time communication at all costs; I believe that an asynchronous approach based on more in-depth content is often more effective and healthy. So why not breathe new life into good old-fashioned forums? They seem like the perfect solution and I really don’t understand why something like this didn’t already exist on Nostr, so I created it!
The basic idea behind Squalk is to offer a tool through which anyone can build their own community, where the main focus is on thoughtful discussion.
Each forum includes a chat feature in the right-hand sidebar, which is useful for quickly interacting with other users in spontaneous and temporary discussions, thus combining the best of both worlds.
Squalk supports both single-room and multi-room setups.
It’s also possible to add resources in the form of articles and customize specific pages (homepage, contact page) to offer a unique and distinctive experience to your users.
You can format and tag your posts, and there’s full support for quoting.
Squalk is based on NIP-29 and NIP-7D, with some minor implementations that are fully backward-compatible. I’m also exploring how to extend NIP-29 for better permission management, so that various types of groups can be created.
After refining these parts, I will add an admin interface for the admins.
You can play it here: https://squalk-test.dtonon.com
Source code and setup details are available at https://github.com/dtonon/squalk
Have fun and let me know what you think! :)
View quoted note →
The basic idea behind Squalk is to offer a tool through which anyone can build their own community, where the main focus is on thoughtful discussion.
Each forum includes a chat feature in the right-hand sidebar, which is useful for quickly interacting with other users in spontaneous and temporary discussions, thus combining the best of both worlds.
Squalk supports both single-room and multi-room setups.
It’s also possible to add resources in the form of articles and customize specific pages (homepage, contact page) to offer a unique and distinctive experience to your users.
You can format and tag your posts, and there’s full support for quoting.

looks great 👀
No, why does it have to be a fork of the Core codebase?
Because it's easier to work on a codebase that you are already familiar with.