Freakoverse on Nostr: I'm not a fan of Primal's lightning wallet kyc, and wooden recommend it to people ...
I'm not a fan of Primal's lightning wallet kyc, and wooden recommend it to people comma but in terms of how their handling performance as a Nostr client, I might be doing the same thing if I'm understanding them right.
On my end, everything so far is pretty much on Nostr, however, there will be a normal backend/database server running alongside it, not caching the nozzle event data itself but saving event addresses, for the purpose of quickly identifying and loading in people's posts and increase reliability overall. This would be running in parallel with what's currently there.
This side supporting a traditional server is not needed for the client to work, it only enhances it, and it'd lower in cost than if it was holding all the data.
I think this approach is the best way to go about it, where it would provide the best possible experience, all the while having it still function even if that developers of it aren't around anymore (building it with this in mind as well, where even if anyone tries to take the project down, be at a person or an entity of power, even if development stops right now, or even if the team developing it myself is gone from the face of this earth, everything would still be functional. As a result, and while not desired or pursued, it's being built with the chance of me not receiving anything in return, only having the satisfaction of seeing it still being used and being unstoppable).
On my end, everything so far is pretty much on Nostr, however, there will be a normal backend/database server running alongside it, not caching the nozzle event data itself but saving event addresses, for the purpose of quickly identifying and loading in people's posts and increase reliability overall. This would be running in parallel with what's currently there.
This side supporting a traditional server is not needed for the client to work, it only enhances it, and it'd lower in cost than if it was holding all the data.
I think this approach is the best way to go about it, where it would provide the best possible experience, all the while having it still function even if that developers of it aren't around anymore (building it with this in mind as well, where even if anyone tries to take the project down, be at a person or an entity of power, even if development stops right now, or even if the team developing it myself is gone from the face of this earth, everything would still be functional. As a result, and while not desired or pursued, it's being built with the chance of me not receiving anything in return, only having the satisfaction of seeing it still being used and being unstoppable).