arthurfranca

> Thanks @kwhitley for your library! > There is work going on at this [fork](https://github.com/arthurfranca/apicache-plus), maybe the two projects can merge? > cc @arthurfranca > > I'm willing to help...

I've just faced the same problem. The prefix option maybe isnt a good idea because the redis client instantiation can already define a prefix. So maybe just a mandatory prefix...

i think it could be done if adding an early toggle option (toggle fn wouldn't have access to e.g. response headers, but would already have access to things like req.path,...

There is no problem using node 13 with json.sortify. Recommended npm version is wrongly limited. Please +1 this [https://github.com/ThomasR/JSON.sortify/pull/12](https://github.com/ThomasR/JSON.sortify/pull/12)

The code seems ok but the problem is that regular users will also be able to use `x-api-cache-force-fetch`. Maybe you could add an `isRefreshable` option (default false) so that server...

> Unlike normal Markdown links `[]()` that link to webpages, wikilinks `[[]]` link to other articles in the wiki. Maybe this could be a NIP-19 `nwiki` similar to naddr but...

@erskingardner the nwiki would reference not a single event, but a group of events. ~I change my suggestion to something more generic that could also reference [NIP-61 - Unbounded Lists](https://github.com/nostr-protocol/nips/pull/784):...

If I got it right, the problem you want to solve is that a media url on a note may have been uploaded by someone else other than the note...

> it paves the way for nostr clients to allow to migrate data from one server to another (NIP 96 forces to have an endpoint to delete), imagine a button...

> Before, when a file was uploaded by a pubkey that did not have an account on the server (in my case they are free, but in the case of...