currently would need a scan but a peer disconnecting (e.g the Steamdeck hibernation does get caught by Node, probably a system signal) could
warn connected peers so that they can update their peerFounds list
provide cacheable metadata (see #10 ) or even in some context data (could be manageable via rsync but would have to estimate size and bandwidth first)
currently would need a scan but a peer disconnecting (e.g the Steamdeck hibernation does get caught by Node, probably a system signal) could
* warn connected peers so that they can update their `peerFounds` list
* provide cacheable metadata (see https://git.benetou.fr/utopiah/offline-octopus/issues/10 ) or even in some context data (could be manageable via rsync but would have to estimate size and bandwidth first)
On reMarkable can't catch `SIGSTOP` so see instead https://github.com/Eeems-Org/oxide/ and if toltc is available (which is not on Codex v3 for now) see https://github.com/toltec-dev/toltec/blob/stable/package/rm2-suspend-fix/rm2-suspend-fix.sh
currently would need a scan but a peer disconnecting (e.g the Steamdeck hibernation does get caught by Node, probably a system signal) could
peerFoundslistSee https://nodejs.org/api/process.html#process_signal_events but unsure for now which signal to intercept.
On reMarkable can't catch
SIGSTOPso see instead https://github.com/Eeems-Org/oxide/ and if toltc is available (which is not on Codex v3 for now) see https://github.com/toltec-dev/toltec/blob/stable/package/rm2-suspend-fix/rm2-suspend-fix.sh