K on Nostr: i think about nostr adoption sometimes. how do we reach a true adoption? last time i ...
i think about nostr adoption sometimes. how do we reach a true adoption?
last time i remembered a quote from someone from whom i learned software development, i learned more than software development; i learned how to think from him.
once we were talking about one of our projects and its code base compared to another project, and he told me the point about our project is that it doesn't get more, but it gets better.
i think this will be the same for nostr. we need to get better at what features we have. make them work as smoothly as possible.
but this is only true when we talk about adoption. one of nostr powers is that it can have infinite features with a simple protocol flow. we can make anything out of it. so another path that devs can follow is to make features that look like they came from future and let cool guys enjoy them.
i love both of them and follow both paths.
last time i remembered a quote from someone from whom i learned software development, i learned more than software development; i learned how to think from him.
once we were talking about one of our projects and its code base compared to another project, and he told me the point about our project is that it doesn't get more, but it gets better.
i think this will be the same for nostr. we need to get better at what features we have. make them work as smoothly as possible.
but this is only true when we talk about adoption. one of nostr powers is that it can have infinite features with a simple protocol flow. we can make anything out of it. so another path that devs can follow is to make features that look like they came from future and let cool guys enjoy them.
i love both of them and follow both paths.