Nostr Web Client

I understand why everyone focuses on clones, though, as that's the easiest way to be successful, since everyone understands what it does and how it works. If you hear "the new Twitter" or "the new Instagram" or "the new Facebook", everyone can picture something concrete.

If you build something novel, everyone is just like, LOL Wut? It's a double-high hurdle, as Nostriches came here for the social media clones and you're communicating to a feed completely dominated by social media clone producers, so you're trying to redirect a tiny subset of a tiny market, while holding the world's smallest microphone.

You really have to focus to being useful to people who aren't already on Nostr. You have to solve some _other, additional_ problem. People have to come to your app, for the app's own sake. Which means your app needs to be really, really, good.

Garbage nsec 1y ago

Yeah, right on🫡. I think you can make two lists for every Nostr use case.

List one: Things we’re going to be asking users to kindly live without (vis a vis their experience with wherever they’re coming from).

List two: Things that'll hopefully elicit a: "wow, that's new", or "wow, that's better" response.

For some use cases List One is pretty long (kindly live without the ability to confidently delete your posts, to know exactly how many followers you have, to be able to reset things if your account is compromised...) while List Two doesn't do enough to offset these (if indeed they can be offset, given that for many users a long List One is an instant game over).

But for other use cases List One is actually pretty short, with Nostr's potential downsides just not relevant in that context (like how in the 90s Linux's potential downside of crap graphics and clunky UX turned out to be more or less irrelevant in the server context) while List Two is like bada-bada-bling-bling!

Reply to this note

Please Login to reply.

Discussion

No replies yet.