bastiat

Public Key

npub10g8tpefz2fhrqtwa60fmh5tv7l4fl5wm7na6qwsagnstk4rltrkq4v50ha

Profile Code

nprofile1qqs85r4su539ym3s9hwa85am69k0065l68dlf7aq8gw5fc9m23l43mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsme5z2v

Publishing to

relay.primal.net

relay.damus.io

nos.lol

Author Public Key

npub10g8tpefz2fhrqtwa60fmh5tv7l4fl5wm7na6qwsagnstk4rltrkq4v50ha

Show more details

Last Notes

2026-02-16 23:25:33 UTC

- reply

Nostr stands for “Notes and Other Stuff Transmitted by Relays.”, and currently all the NIPs go through relays, but in principle there is nothing stopping out-of-band also being used in the future, there is also some suggestions already around mesh, bluetooth, gossip, etc.

2026-02-15 22:23:10 UTC

- reply

The starting experience with Nostr is, lets be honest, rough.
You learn about the protocol, then you go to nostrapps.com and look through to see if you can find some apps you want to try out, you go to sign up, and it tells you that best practice is to set up a remote signer. Ok, fine, which one to trust? You are making an irrevocable decision about what software you are going to trust your master key to, a wrong decision is catastrophic, lose the key and your identity is gone, if the key is compromised there is no way to regain control, the identity is permanently ruined.
Ok, whatever, you choose eg. to try out NOS2X, and you get an extension that while it works, the UX is frankly garbage tier. Then you finally get to sign up for the thing you wanted to try out to begin with, and then every time you do a new action you have to choose whether you give permanent authorization for 10 different actions one by one, with an explanation that quite frankly doesn't really make it clear what it is, or you can give temporary authorization and it will keep asking you every fucking time you do the thing.
This is one of the reasons I wrote a post about a DID based system, where the UX by comparison to what I just laid out would be:
1. You go to the app you want to try out, it could list a few options for you for identity wallets available on the platform you are currently on.
2. You download the identity wallet, and save your master key somewhere safe, ideally in cold storage, but it could also be inside of Bitwarden or similar password manager. An update key is set up as well and stored in the identity wallet app.
3. You click sign in in the app you want to sign into, and it sends you to something that looks very much like an OAuth authorization page, listing out all the permissions the application is asking for, and if you click "Authorize", a verification key is generated and sent to the app (probably stored in local storage, this key can be revoked at any time to disable the permissions granted to the app). The identity wallet handles all the broadcasting of DID documents etc. automatically.
#nevent1q…g7sw

2026-02-15 20:56:14 UTC

I wish Nostr used DIDs, specifically a new DID spec that functions something like this:
Each DID document includes:
- A version number, which the owner increments each time a new version of the DID document is created.
- A master key, where the pubkey acts as the identity. The master private key is intended to live in cold storage, think of it as an "in emergency break glass" key.
- One or more update key(s), that can be rotated by creating a new DID document and signing it with the master key. Update keys have authority to sign new versions of the DID document, changing the list of update keys or verification keys + permission strings. Update private keys are intended to live in an identity wallet on a users device.
- One or more verification key(s), with a string of permissions granted to the key(s). These are intended to be used to grant permissions to applications.
- A version history that lists revoked update keys and verification keys.
- A list of relays the DID document owner uses.
This would grant a bunch of nice properties, such as:
- Ability to revoke update and verification keys in case of compromises.
- Key rotation would not lead to your pubkey/identity changing, which would break eg. mentions in Nostr.
- No need for complex key share handling where you must dispose of shares when rotating keys, and having to have multiple devices on at all times to be able to use Nostr, like would be the case with Frostr which uses a threshold based signature scheme.
- No longer needing to use remote signers as a best practice in all cases, if a verification key is compromised it is a limited amount of damage it can do since permissions are limited to only what you want to give the application ability to do.
- Because the DID documents have to be signed either with a master key or an update key, they can't be changed without invalidating the signature, which makes it easily cryptographically verifiable that a DID document has in fact been signed by the owner.
(Not an exhaustive list, just some highlights).
DID documents would be distributed to DID Directory Relays. The relays would not have any authority over the documents, just like in Nostr today, if a relay blocks you, users can simply find your DID document on a different relay. The DID document can also be sent directly to a user or service without going through a relay. This is fundamentally different than eg. AT Protocol that relies on the centralized PLC Directory for distribution of DID documents.

2026-02-14 03:52:31 UTC

- reply

This is a good suggestion.

2026-02-14 00:41:52 UTC

- reply

You should check out what @nprofile…cr3y is doing with Flotilla, pretty cool ngl.

2026-02-13 13:20:38 UTC

- reply

Very true. @nprofile…cr3y is doing good work with Flotilla in that regard, preparing for the disgruntled Discord users looking to migrate.

2026-02-12 06:03:10 UTC

- reply

Matrix/Element has a Discordification issue with a TODO list in that they have been "working on" for more than 8 years. They still haven't gotten around to doing a single fucking thing pretty much.

2026-02-12 04:29:12 UTC

- reply

The eternal purity spiral on what decentralization means.
Flotilla can't ban a user from connecting to communities/servers, unlike Discord, Flotilla can't control the rules communities/servers have to follow, unlike Discord, Flotilla can't force users to have to share their identity documents to not be treated like a teenager, unlike Discord, Flotilla can't delete your identity, unlike Discord.
Could go on. Its not overselling it at all to call Flotilla decentralized Discord once the most important features people use Discord for are supported.

2026-02-12 02:51:15 UTC

- reply

Here is a second option too, also with logo and text fixed.
https://blossom.primal.net/4f9b99bb1c0bbb46dec566396e24f543a0748ee08f509fb070618552452cebaa.png

2026-02-12 02:50:04 UTC

- reply

After prompting it a bit more i got it to add the flotilla logo to the sail and fix the text :D
https://blossom.primal.net/9eab2af990551435a218ca83b45d9800a1b7001a8a482c6637f12a37fc81a7f4.png

2026-02-12 02:41:30 UTC

- reply

Tried to have ChatGippity make an image of the above idea :D
https://blossom.primal.net/878ffd4bd3b99be799690dcb6b486d4a66bd207fa7f7b588650d8b468513eb3f.png

2026-02-12 02:34:26 UTC

- reply

To capture Discord users you aren't trying to win over the users that search for "Discord Alternative" on google, what you are really trying to do is to convince community owners to move to Flotilla, the community members will move where the community goes. Throwing money at google ads won't accomplish that. Its all about winning over the owners.

2026-02-12 02:15:42 UTC

- reply

You could also do some play on word stuff with the "Flotilla" name by the way. Communities/servers being ships in a flotilla setting off from the prison island that is Discord.

2026-02-12 02:13:44 UTC

- reply

Try to emphasize the ways in which Flotilla is similar to Discord. For instance, you join a server through an invite link, and that servers on flotilla has channels like on discord, and you can even list the features that arent yet there but are planned and simply put a link to the roadmap next to unfinished features with an "In Progress" badge above the title. For instance role based access control with role names and colors, voice channels with push to talk, DMs, custom emojis, and whatever else.

2026-02-12 01:53:06 UTC

- reply

The most important thing to prepare is your website and documentation IMO. On the flotilla website you put heavy emphasis on "Book a Demo", and it makes it come across as if you can't just go and try it right now. I think its fine to have a book a demo button further down maybe, but front and center on your website should be "Try it now", and "Get started", and "Developer Documentation", and "Host it yourself" type language.
As far as catching the discord alternative wave, please also consider adding language to that effect on the flotilla homepage, and streamline the process of setting up your own relay. Also, remember that the people you are courting here are not bitcoiners, they want to be able to pay using normal money, so get a payment gateway that can receive card payments set up.

2026-02-12 01:45:45 UTC

- reply

Probably not honestly. I think you are better off optimizing the text on your website to be the sort of things people search for, eg. "Discord Alternative", and getting traction on product hunt, alternative to type websites, etc. And potentially getting some "self hosting" type youtubers to try it out once you are happy with the feature set.

2026-02-12 01:39:01 UTC

- reply

Hello, Discord Dodger here, nice to meet you. https://blossom.primal.net/ff66dec64fe88033766383b6a64f62165b7834cc92fa3ab5bcf4e96a24d3da2e.png

2026-02-12 01:25:09 UTC

- reply

For each type of community there are certain features that are deal breakers not to have.
For instance:
- Not having the "delete all messages" function when banning a user is a non-starter for any discord community with public access, not having that would make managing spam impossible.
- Not having role based access control makes managing communities with more than a hundred users painful instead of fun.
- Not having message retention systems makes use of Flotilla by companies impossible.
- Not having voice channels with push to talk means gaming communities can't use Flotilla.
Just some examples. I am not asking for complete feature parity, I am talking the features that make Flotilla a non-starter. It isn't actually that many features that are necessary to make it good enough.

2026-02-12 01:10:30 UTC

- reply

A promise of Flotilla actually reaching feature parity where important with Discord is more than enough.
Let early adopters feel involved by taking feature suggestions and make it easy to see progress being made towards the goal (could eg. be a Github issue called "Discordification with a list of features being checkmarked as they are completed, so people can go there to see the current status).
Also, if you can push things faster forward by hiring or giving grants to devs in the community, letting the early adopters give you money that specifically will go towards discordification or specific features in that roadmap would be wise.