Ok, that’s better. Not 💯 true (again subjective part) but nostr has still a lot to do to be very scalable, but definitely has architectural advantages to scale well. I am not going to go into technical details, but the main advantage I see is its simplicity. We haven’t invested much into proper scalability yet, but if there was a need, I see how to make it work with millions of active users.
And by the way, I do appreciate all the criticism that comes my way, it helps a lot with making a better product.
Media side is the main area I am focusing on, and can assure you that we can handle a large number of concurrent users even now. Thanks again, and I hope to hear more from you in the future 🐶🐾🫂🫡
Thanks for the reply. I left the fediverse for nostr full time. I want to see it thrive. Redis caching and postgres backends would help a lot. Hopefully we see s3 support soon for uploads so anyone can host a media server easily like witj minio.
It’s already kind of possible with nip96, but as you can guess s3 object storage is not a great solution to the problem. Postgres is also not the best choice for this, cost of scaling is too high even if caching is there. I think more solid approach would be a KV storage backend for events. 🐶🐾🫡🫂
Awesome. I cant wait to see what comes next. Postgres aint my favorite but it seems to be the standard now. It will be nice to see nostr do something better. Cant wait
Absolutely! A lot of ideas, not enough time to explore them all! A good problem to have I guess 🐶🐾🤣🤣🤣