Freakoverse on Nostr: There's local caching on my end, but the user deletes it of course, and ya as you ...
There's local caching on my end, but the user deletes it of course, and ya as you said it's not a good idea to burden the user handle such a thing to have a proper site/app experience.
I'll be doing remote caching, but doing it in a way that it's only to run it in parallel to what's already there, where if my server goes poof, the site/app still functions, just not optimally.
And now after a discussion, it'd evolve into giving the user the ability to changing to different caching servers/services too, or turn it off completely if they want. Here's the previous talk about it:
and
I'll be doing remote caching, but doing it in a way that it's only to run it in parallel to what's already there, where if my server goes poof, the site/app still functions, just not optimally.
And now after a discussion, it'd evolve into giving the user the ability to changing to different caching servers/services too, or turn it off completely if they want. Here's the previous talk about it:
quoting nevent1q…q7d4I'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).
and
quoting nevent1q…c7y5That's why it's not reliant on it. If it gets attacked then that's that, the site is still running, just not in pristine condition. That's about it.
And yeah that can work too, in the app/setting page there'd be:
Title: Caching Server [button: add]:
Subtitle: Official servers:
cahcing.degmods.com [button: unset]
Subtitle: Recommended servers:
caching.example1.com [button: set]
caching.example2.com [button: set]
caching.example3.com [button: set]
Subtitle: Custom/user servers:
input-field [button: add]
caching.exampleCustom.com [button: set]
This can be a nip too, now that I think about it.