mleku on Nostr: not so excited to write #progressreport #realy posts at the moment but i've just made ...
not so excited to write #progressreport #realy posts at the moment
but i've just made a small improvement that uses standard XDG style directories for things
there is now separation between config, data and state...
on linux, config goes in ~/.config/realy the data goes in ~/.local/share/realy and the state data goes in ~/.local/state/realy - this essentially implements the proper way it should be done
but having said that, i don't think this handles android/ios correctly, which i probably want to switch up the code later when i do the nostr relay chat app, to also handle android and iOS properly by using their respective config/state/data settings...
there isn't really anything in the relay that needs "cache" - cache essentially means data that doesn't break the config or state, but speeds things up, this isn't part of what the relay does, but again, when there is NRC the need for this kind of stuff, things like caches of event history that probably should really be living on a relay
i'm very inclined to lean towards just using a relay and making a small GUI to run realy in a similar capacity as citrine, but that's a whole load of work as well, however, if i'm finally getting funding to build NRC then ok, it's part of the agenda, the relay will have a mobile release, at least on android, i'll not touch the crapple shit unless someone wants to volunteer to maintain that shit, i would feel like i just stepped in a shit if i bought even an old second hand but current enough iPwn
but i've just made a small improvement that uses standard XDG style directories for things
there is now separation between config, data and state...
on linux, config goes in ~/.config/realy the data goes in ~/.local/share/realy and the state data goes in ~/.local/state/realy - this essentially implements the proper way it should be done
but having said that, i don't think this handles android/ios correctly, which i probably want to switch up the code later when i do the nostr relay chat app, to also handle android and iOS properly by using their respective config/state/data settings...
there isn't really anything in the relay that needs "cache" - cache essentially means data that doesn't break the config or state, but speeds things up, this isn't part of what the relay does, but again, when there is NRC the need for this kind of stuff, things like caches of event history that probably should really be living on a relay
i'm very inclined to lean towards just using a relay and making a small GUI to run realy in a similar capacity as citrine, but that's a whole load of work as well, however, if i'm finally getting funding to build NRC then ok, it's part of the agenda, the relay will have a mobile release, at least on android, i'll not touch the crapple shit unless someone wants to volunteer to maintain that shit, i would feel like i just stepped in a shit if i bought even an old second hand but current enough iPwn