Right now I'm mostly just solving problems that require aggregation, and are hard to do on the client. Search and discovery are big parts of that. That includes APIs for other apps.

For the APIs my vision is to make them generic and eventually standardized, so that apps could allow users to switch btw different aggregation layer providers. That way we could have at least some push back against centralization, which aggregation inevitably creates.

I'm still figuring out the path for the nostr.band user-facing side. It will have search & discovery components of course, but I like the micro-app ethos that fiatjaf stands for and I don't want it to do 'everything'. I'm thinking on focusing on the reader experience, and leave posting and participation in conversations to other apps.

What's your opinion or advice?