And Nostr will miss an amazing opportunity... again.
Login to reply
Replies (41)
I've gotten 12 signups in the last few days for my hosting service and traffic has doubled on Flotilla this week. Small numbers still, but I'm hoping to start doing some real marketing this week and next. Maybe I can catch the wave.
That was supposed to be @hodlbod's job.
In progress
People are migrating to 
. Sadly most nostr devs are indie, we cannot compete with coporate.
Root - Not Just Chat, Built for Action
Root is a next-generation social platform that combines communication tools with a customizable app framework, allowing communities to organize, co...
Do you have a word of mouth referral mechanism for the current customers?
Well I don't currently charge for my service, so no
Oh you're on it? Awesome 💪
Root looks very good
🫡 flotilla.social
Of course. I meant if you were going to catch the opportunity
Oh haha well we'll see. Flotilla is like 90% stable now, which is good enough to start catching early adopters, but I still need to build rbac, voice chat, relay admin dashboard, migration, etc etc etc.
Rooting for ya (not for Root)
The web app bugs out when you try to join a channel when browsing them. Mobile works fine
Try a hard refresh, I think I fixed this yesterday
"Failed to join space. Please try again"
Yes, but people don't realize it's still a corporate product. sooner or later, it will do the same thing as discord does.
This has been my annoyence with nostr devs. To insist on being a one-man foss team is to forgo building a great product
Not charging doesn’t preclude referrals. Let your customers who love flotilla do marketing for you!
what do I offer them in return?
A place for them to communicate with their people without discord-honeypot gulag.
You could do social badges of course - e.g. community creator, invited community creator, invited community member etc (see github examples).
If someone already found their way to flotilla, and they stick around it means they are receiving value from your product.
Find your super spreader customers, and just ask them/make it easy for them to spread the word.
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.
“reaching feature parity “ sounds nice on paper.
In reality the customers switching from discord have a strong enough reason to do this to take risk, endure the pain of a new app that doesn’t have standard pattern of email login, and has a bunch of other novelties that no one has heard of outside our bubble.
The core jobs to be done are find my people, associate with my people, talk with my people. From this lens, the difference between flotilla and discord is the gulag.
Everything outside the core JTBDs else is bells & whistles.
Badges are a good idea, although there's nowhere to really see them
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.
That's a good distinction, feature parity is madness, but top-line features define what the product is actually useful for
Customer -> problem/jobs-to-be-done -> flotilla benefits (vs status quo discord) -> features.
Deal breakers are a real thing - the saudi wave who joined and quit nostr on learning delete doesnt exist in 2023 nostr is a real world dealbreaker example.
Have you validated with target customers - lets call them Discord Dodgers - what dealbreakers are, if any (given flotilla’s no gulag positioning)?
Hello, Discord Dodger here, nice to meet you. 
🤝
We shall see - bitchat is proof of concept
I would say THEY miss an amazing opportunity... again
“Discord meets bitchat” could be a good marketing hook for Flotilla
:110percent:
Great benchmark, thanks!!
I wish it was different...
What have you been working on recently Niel? :)
zapstore.dev
bitchat is very different from discord from what I saw
If your life changed overnight, how would you begin again?
We are trying to answer that question every day.
We never imagined we would have to ask for help. But survival leaves no room for pride.
Even small support matters more than you know:
$10 is not just money — it becomes bread.
$50 is not just a donation — it becomes medicine and safety for a few more days.
For us, these amounts are not numbers. They are moments of relief in a life filled with uncertainty.
If you feel moved, please stand with us.
gofundme.com
Donate to Wesam Sharaf and his family in Gaza, organized by Saleh Shan
Before October 7th, we lived a peaceful life, filled with hope and dreams for the futur… Saleh Shan needs your support for Wesam Sharaf and his f...
Any error in the console? This is in a generic try/catch, could be something related to notification APIs not being available
Failed to join space: TypeError: can't access property "encrypt", i.nip44 is undefined
encrypt nip07.js:25
t nip07.js:12
promise callback*cv/< nip07.js:8
encrypt nip07.js:25
encrypt util.js:41
Ln session.js:95
encrypt util.js:41
zn commands.ts:354
ie commands.ts:361
pa commands.ts:386
k SpaceJoin.svelte:49
Rr event-modifiers.js:97
Q attributes.js:406
r events.js:61
dt shared.js:44
r events.js:60
Sounds like your browser signer doesn't support nip44?
I meant more in proof of user adoption