Interesting.. and likely unsustainable 😉
I’d guess re-hydration may need to rate limit itself broadcasting out to relays - or results will be some events worked and some didn’t.
And not all events should be re-hydrated, like old meta or contact list events. No need for the network to see them. You may only care if you’re doing analytics or delta tracking on them.
Yes it should be gentle at the uploading phase.
Need some check maybe, Cc #[6]
I just launched this project yesterday, but it's still in early beta. In the coming days, I plan to optimize it as much as possible.
One change I will make is to give users the option to choose specific relays when performing manual backups, instead of broadcasting to all of them.
Users will also be able to select the types of events they want to broadcast.
As for auto backups, starting today they will only create and store backups in the cloud, without broadcasting them.
This should make the process more efficient and less of a burden on the relays, which is important for sustainability.
If anyone has additional suggestions, I would be grateful to hear them.
#[2]
