Just a quick update on the Nostr Backup Service (NBS) project:
The Backup, Broadcast & Restore backend is almost done! I'm currently working on the frontend and trying to determine the best way to deliver the service. The plan is to launch an all-in-one dashboard site that's easy to use, and I'll be using the #[0] handle for quick accessibility. If you have any suggestions, I'd love to hear them.
Context: @note1t2cd3f74dkp5eupv2gcsfexyftuef7al6sducu248caett4arnuq4e4qeg
🤙🏾💜
is this a paid relay itself?
following nostr.wine model:
subscribe to wss://service/pubkey
your service backs up on behalf of this user, rebroadcasts, and persists for point in time recovery in which they can download/rebroadcast manually from their dashboard?
Users only need to submit their public key once, and our platform will automatically broadcast their events to all the major relays. Additionally, we'll create a backup file that can be restored to any desirable relay. Users can also manually broadcast, backup, and restore events through the dashboard. We plan to offer all these services for free and sustain the platform through donations. let's see 😅
actually yeah, and i realize it's probably significantly more annoying to do so:
-pull media and archive it along with a users profile. (only because most people are terrible at keeping track of what they shoot/link/post, and some even are more terrible and use social media to offload files when running out of phone/disk space....! ) Rest assured I'm not in any of these camps, but a great many are. You can likely charge these specific use cases a small fee to go towards running the server.
If I think of any other suggestions, I'll shoot them in your general direction.
Is the project on phabricator, or github?
