Integrate nostr as backend

[rikmeijer]

Opening up to nostr can bring endless possibilities to your product. There are specs for calendars and storage.

How can I help realizing this?

[devvv4ever]

Hello,

as long as nostr does not provide a CalDAV gateway/mapping it will never work :-/ For file access we use WebDAV. Nothing else is in the scope of DAVx5. Sorry!

[chGoodchild]

@devvv4ever and @rikmeijer have you considered dropping caldav files on blossom servers to replace caldav servers like radicale?

[rikmeijer]

You mean extending blossom servers with dav functionality, @chGoodchild ?

[chGoodchild]

That could be useful too, but I was thinking of a smart client + dumb server. What if there was a calendar frontend that places its CalDav files on blossom servers without requiring that the blossom server knows what CalDav is?

[rikmeijer]

Hmm, you might as well directly build a nostr client than. I am looking for a way to quickly open up the nostr network to existing software. You would need to extensively alter davx to cater your solution. Or am I missing something?

[devvv4ever]

That could be useful too, but I was thinking of a smart client + dumb server. What if there was a calendar frontend that places its CalDav files on blossom servers without requiring that the blossom server knows what CalDav is?

That sounds hardly possible to do easily, since CalDAV servers must always (also contextually) understand the request by a client and then offer the appropriate answer to it. It can't be just files that are synced (that would more or less be "simple" WebDAV, but CalDAV extends on WebDAV).