No but it should be a…
No but it should be a no brainer. I would go for a #nostr / #nosdav backed at:
### 1. Prerequisite Knowledge and Setup:
- Familiarize yourself with the rclone backend development documentation.
- Set up a development environment that allows you to build and test rclone with new changes.
### 2. Create a New Backend:
- Start by creating a new backend for NosDAV in rclone's backend directory.
### 3. Implement Identity Handling:
- Implement code to handle Nostr-IDs (both single-user and multi-user modes). This involves ensuring that the proper directory structures are maintained based on the Nostr-Id.
### 4. HTTP Request Handling:
- Implement the HTTP verbs: GET and PUT, as described in the NosDAV spec. Ensure correct URI formats and response handling.
- Handle file retrieval and storage based on Nostr-Id and file-path.
### 5. Authentication:
- Implement the authentication header mechanism. This includes:
- Generating the required nostr event.
- Signing the event with the required public key.
- Attaching the signed event to the Authorization header in the required format.
- Implementing the Schnorr signature scheme.
### 6. Access Control:
- Make sure GET requests are accessible to anyone.
- Implement required authentication checks for PUT requests, based on the provided authentication mechanism.
### 7. Implement CORS Handling:
- Add CORS headers to the NosDAV backend responses as per the spec.
### 8. Content Type Handling:
- Implement logic to determine file type based on extension and set the appropriate Content-Type header in responses.
### 9. Discovery:
- Implement the application-specific discovery mechanism as described, including the use of kind=30078 and storage tags.
### 10. Testing:
- Thoroughly test the new NosDAV backend with various scenarios to ensure all functionalities work correctly.
- Test edge cases, such as invalid Nostr-Ids, invalid file-paths, and unauthorized PUT requests.
### 11. Documentation:
- Write documentation for the new NosDAV backend in rclone, explaining its features, setup, and usage instructions.
### 12. Submit for Review:
- Push the changes to your rclone fork on GitHub.
- Open a pull request to the main rclone repository for review.
### 13. Feedback Loop:
- Address any feedback received from the rclone maintainers and community. Iterate on the implementation based on feedback until it's accepted.
### 14. Finalize:
- Once accepted, your NosDAV backend will be part of rclone, and users can utilize it for their Nostr-based file storage and retrieval.