The user interface needs to be #bitchat ..
Why ?
1) it is light weight
2) best design
3) going to be lot more popular than #nostr . Even if not , it captures a different cohort of users .
Opportunity for nostr
1) stream the channels live .. imagine a conference of 5000 people chatting on bitchat but one of them is streaming live .. it is like live news from battlefield :-)
2) allow users to login with nostr npub ..optional for users.... but the benefit carrot is obvious , it lets me use different devices .. backs up my communication on relays if I want
3) why should nostr do it .. 1) new user cohort to capture 2) ride the bitchat wave 3) alignment of ethos .. freedom , anti deplatfom etc
4) new client interface . Lay the ground work for other platforms to adopt nostr as a protocol
What nostr should NOT do
1) create another app - cuz it is unnecessary
2) confuse users - three layer architecture
3) double the attack surface
Login to reply
Replies (2)
I'm totally against that approach, sorry. The idea is that somebody familiar with #amethyst (or any other client) should just continue using it seamlessly.
I didn't move to nostr to be captured by apps instead of platforms.
Don't get me wrong. I perfectly understand it's a paid point for users, but luckily I don't have any VP over my head, so I can stick attached to what I believe is better.
That said, as far it doesn't break that rule, I'm 100% open to improve the user experience and welcome any used feedback.
The user interface needs to be #bitchat ..
Why ?
1) it is light weight
2) best design
3) going to be lot more popular than #nostr . Even if not , it captures a different cohort of users .
Opportunity for nostr
1) stream the channels live .. imagine a conference of 5000 people chatting on bitchat but one of them is streaming live .. it is like live news from battlefield :-)
2) allow users to login with nostr npub ..optional for users.... but the benefit carrot is obvious , it lets me use different devices .. backs up my communication on relays if I want
3) why should nostr do it .. 1) new user cohort to capture 2) ride the bitchat wave 3) alignment of ethos .. freedom , anti deplatfom etc
4) new client interface . Lay the ground work for other platforms to adopt nostr as a protocol
What nostr should NOT do
1) create another app - cuz it is unnecessary
2) confuse users - three layer architecture
3) double the attack surface
View quoted note →
Nostr Devs - Don't create new clients unless a really l new use case .. Instead add nostr to all the open source apps .. #bitchat #mdbook #audacity #sox #ffmpeg #vim ..
The user interface needs to be #bitchat ..
Why ?
1) it is light weight
2) best design
3) going to be lot more popular than #nostr . Even if not , it captures a different cohort of users .
Opportunity for nostr
1) stream the channels live .. imagine a conference of 5000 people chatting on bitchat but one of them is streaming live .. it is like live news from battlefield :-)
2) allow users to login with nostr npub ..optional for users.... but the benefit carrot is obvious , it lets me use different devices .. backs up my communication on relays if I want
3) why should nostr do it .. 1) new user cohort to capture 2) ride the bitchat wave 3) alignment of ethos .. freedom , anti deplatfom etc
4) new client interface . Lay the ground work for other platforms to adopt nostr as a protocol
What nostr should NOT do
1) create another app - cuz it is unnecessary
2) confuse users - three layer architecture
3) double the attack surface
View quoted note →