Avatar
Water Blower
6b9da920c4b6ecbf2c12018a7a2d143b4dfdf9878c3beac69e39bb597841cc6e
Creator of Blowater & I self identify as a Pro Sleeper

It is indeed hard. Because Nostr is a rare opportunity for developers to work on their own. Many developers are simply here to hack and have fun. A few are working on it with an entrepreneur ambition and efficient execution.

But still, the current capittal utilization of Nostr, or simply OpenSats, is much higher than any VC. The 5M is not fully spent yet. No VC can support such a wide range of projects with just 5M.

Nostr is not a single app where as Bluesky, as a single app, raised 8M in its seed.

Therefore, it's not an apples to apples comparison. Most Nostr projects, be it a client or server, receives less than 0.05M funding. 160X less money!

As far as I know, the whole Nostr ecosystem only has 6M so far, that is 1M to primal and 5M to OpenSats for 20+ projects.

Most OpenSats grants are to solo developers. But I feel it's time for some projects to have 2-3 full-time developers to work on it or at least that's my goal. Even though there are 3 developers working on Blowater, I am still the only full-time person doing 80%+ of the total work. Therefore, I believe that OpenSats can't be the only source of funding for Nostr. Different projects, be it client or not, have to find their funding independently. OpenSats is just a good starting point.

Having 50 projects going on is fun, similar to genetic selection, but the late game needs to be 5-10 really good projects that cover 95% of the known use cases.

Of course, we will always find new use cases and new projects will be born.

I don't think the problem is lack of UX research. At least not from my perspective. Taking Blowater as an example, my biggest problem is that there are always performance problems before the UX problem. For example, I know the onboard is bad, but to fix onboard, I need to fix some other things first. I simply don't have enough manpower to work on top level UX and bottom level infrastructure at the same time. Adding UX research or designing only extends the todo list. But my problem is about checking off todo items. One UI/UX designer can produce 10 weeks of work for a developer in a week.

There are many issues to work on

I need a good frontend engineer to work on Blowater to hard

What do you plan to do when the relay doesn’t support negentropy? nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s will that break your Nostr DB architecture?

I believe they all use nostr-tools and I need to submit a PR to make nostr-tools fast.

I might just have to implement a NIP07 extension to just get fast decryption. Blowater’s built-in decryption is 3X faster than Alby or nos2x but the user has to put their trust to us to nsec. When decrypting 1000+ DMs, performance matters.

Fat level Asian isn’t even fat. Fat level American is a violation to human rights and should be illegal.

Extension is really just another web page with more system privileges than normal web pages. It can communicate with servers and peek your current webpage’s data without your permission. From this perspective it’s less secure than a normal webpage.

The narrative on Nostr is if you centralize your private key risk to a single extension that you trust, then you don’t have to trust individual Nostr clients. Meaning you still need to pick one extension that you trust. Extensions are not intrinsically safer.

The question comes down to: web extensions are just another web page so that the security level is the same. It comes down to whether you trust the app or not.

The problem on mobile is that there is no extension.

https://github.com/BlowaterNostr/blowater/milestone/2 we are 40% done with our September plan, right on track