dendrite
nostr
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dendrite
- The Tailscale Universal Docker Mod
- Conduit: Simple, fast and reliable chat server powered by matrix
-
Databag – tiny self-hosted federated messenger for the decentralized web
Matrix already has key-based identity in the works at https://github.com/matrix-org/matrix-spec-proposals/blob/keg... (and implemented in Dendrite at https://github.com/matrix-org/dendrite/pulls?q=is%3Apr+is%3A...). Matrix is set up to let folks go wild and change fundamentals like this; basically every Matrix Spec Change (MSC) is a small fork, which then gets merged into the main spec if it can be proven to work well in the wild.
-
What's the easiest way to use Matrix and add matrix-bridges for Messenger, Instagram, and Telegram etc.
I really hope that Dendrite is getting more traction and maybe there's an OIDC solution for Matrix one day.
-
Can Dendrite run on Kubernetes?
Yes there is an official helm chart. https://github.com/matrix-org/dendrite/releases/tag/helm-dendrite-0.11.2
- suggestions on a self-hosted messaging server with end-to-end encryption for a small family
-
Have any of you used a decentralized messenger before?
This is what the Matrix team is developing Dendrite for. To have a feature-complete yet small server software. But it's still in beta.
-
Matrix 2.0 — Matthew Hodgson talks about Rust in Element client, Rust SDK, IETF MLS, MIMI and more
Pinecone, which is an experimental overlay routing protocol used by P2P Matrix. It and Dendrite are extremely important to P2P Matrix.
-
How to generate keys for program like Dendrite
So I want to setup an instance of Dendrite, a matrix home server. I have a docker-compose set, the yaml file in the correct directory, but I do not understand how to generate the key files. the dockerhub states that I should use this:
-
How should I set up a private chat server/client for my family ?
Dendrite, meanwhile, can be found here. They say it's in beta. I think it's a late Alpha. Dendrite's primary mode is "Monolith"; this will have many of the same scalability/balancing options that Synapse does. However the true benefit to Dendrite as I see it is the "polylith" mode where workers can swap around which worker is the master without any interruption of service. I do not think that Dendrite polylith works yet, but I might be wrong. I'll be looking at running it on a test server in January to see if it's time to upgrade from Synapse (and time to invest in 4-6 SBCs to keep three here and send 3 to 3 of my buddies to make my Matrix even more reliable).
nostr
-
Probably a bad idea to use Reddit to talk about privacy.
Some resources if you're interested in learning more: https://nostr.com/ https://ron.stoner.com/nostr_Security_and_Privacy https://github.com/nostr-protocol/nostr/ https://nostorg.github.io/clients/
-
Ask HN: What is the next great online community?
I think your best bet here is Nostr (Notes and Other Stuff Transmitted by Relays): https://nostr.com https://github.com/nostr-protocol/nostr
Nostr isn't a federated platform like Mastodon or Lemmy, it's more similar to the AT protocol created by Bluesky, whilst being far simpler to understand and write apps using it. The nostr protocol is defined by a series of NIPs (Nostr implementation possibilites https://github.com/nostr-protocol/nips), the most basic of which can be implemented in a client or a relay in 50-100 lines of code in any modern programming language.
Each user runs a client, anyone can write a relay or run any of hundreds of existing implementations, both clients and relays can choose to support a number of NIPs. Users have a public-private keypair, and distribute notes to relays signed with their private key, which are verified by relays. Clients subscribe via websockets to any number of relays (I usually have 20-30), and receive notes from all users on those relays' databases, or filtered by the public keys of the users you're following. Relays for the most part don't communicate with each other. If you're ever blocked or banned from a relay, you'll still be able to have your notes seen as long as you have at least one relay in common with anyone who wants to see them. I run my own as well for extra resiliency.
At the moment there's ~50 standardised NIPs, which add features like likes, zaps (bitcoin tips for notes), user status, post expiration, mentions, search, DMs, and public chats. Nearly all of these are supported by popular clients and relays. While nostr is primarily used for social media at the moment, it's already possible to build upon as a protocol for pretty much any online service.
The total active user count on most public relays I'd estimate is somewhere around 500k to a million, though the nature of the protocol makes it impossible to estimate its true size. The perceived community on most relays before following anyone frankly can get pretty cancerous, mainly due to a lot of clients sorting notes by new by default, so I can only hope to high heaven it'll improve as it grows.
Though like any new non-centralised platform, it's more difficult to get started on for most non-technical users as they have to pick one of hundreds of clients to install, and requires caution to never leak your private key and be very wary of which clients you trust it with.
-
🤡
I hope this was not too technical and all over the place. If you are interested in knowing more please ask me or check out https://github.com/nostr-protocol/nostr or https://nostr.com/get-started
- r/nostr stands with Reddit users and support continued use of 3rd party apps. However, during the blackout on 6/12, we welcome you to come to us and ask questions about our open-source, decentralized and censorship-proof social media protocol known as nostr.
-
The Stack Overflow Data Dump has been turned off
Without movement on this [1] I can't see adoption.
[1] https://github.com/nostr-protocol/nostr/issues/97
-
A Social Media site where “No Humans” are allowed and AI Bots run the show
I think the next stage is decentralized social media. Something like nostr (1) where there’s no centralized entity determining the algorithm to boost. It’s up to the individual to follow users.
Perhaps the next challenge would be human verification, even with this protocol we’d need something to index public people by to handle discovery.
Even before LLM’s became as mainstream as they are, most social media platforms were riddled with spam: affiliate marketing, drop shipping crap, and people who are running some sort of con.
1 - https://github.com/nostr-protocol/nostr already has 8k stars on github
- Vart tar man vägen när Reddit går åt helvete?
-
It's time to go NOSTR
Considering that Reddit might not be able to negotiate better pricing for API usage, it's worth considering a different approach. The future of social media seems to be moving towards protocols rather than specific platforms. This means that instead of relying on a single platform like Reddit, Apollo should focus on using a protocol called NOSTR (you can find more information at https://github.com/nostr-protocol/nostr).
- Now that Reddit are killing 3rd party apps on July 1st what are great alternatives to Reddit?
-
Twitter's Algorithm: Amplifying Anger, Animosity, and Affective Polarization
Holding me back from posting updates of what I had for breakfast is the problem of private key sharing with services that I can use in order to post updates of what I had for breakfast.
A client or service will inevitably be compromised. And with it, the private keys of all using it whether stored by the service or logged on entry by a compromised system.
Private keys should be chained, master->subkey, with subkey the public key of the service __or a solution like that or that ends in the same result. When (not if) a service or key is compromised, the key can be blacklisted and/or any key co-signed by a compromised service blacklisted.
I'm confused by the oversight. It's also been raised here https://github.com/nostr-protocol/nostr/issues/97
Until then, I'll have to keep my updates of what I had for breakfast to myself.
What are some alternatives?
Synapse - Synapse: Matrix homeserver written in Python/Twisted.
Mastodon - Your self-hosted, globally interconnected microblogging community
synapse-admin - Admin console for synapse Matrix homeserver
ipfs - Peer-to-peer hypermedia protocol
conduit
simplex-chat - SimpleX - the first messaging network operating without user identifiers of any kind - 100% private by design! iOS, Android and desktop apps 📱!
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
Signal-Server - Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS
Telegram-FOSS - Unofficial, FOSS-friendly fork of the original Telegram client for Android
awesome-nostr - nostr.net - awesome-nostr is a collection of projects and resources built on nostr to help developers and users find new things
Ligase - Ligase is a Golang-based implementation of Matrix homeserver, powered by finogeeks https://www.finogeeks.com/Finchat
matrix-spec - The Matrix protocol specification