Yuval Kogman

for bip (3)21 URIs to convey bip 77 *only* and not bip 78 is supported, my preferred approach is to add a new key like `&pjv2=` instead of `&pj=` that...

I'm personally very much in favor of `tracing`-maxxing, not just for downstream users but al unpopular opinion: i don't think structured logging is complex at all, rather it's simpler than...

I don't think this can be considered closed yet, we have plenty of log events that currently just format strings but which could use structured logging instead

Cache control header on RFC 9540 responses

see also: - https://www.ietf.org/rfc/rfc9458.html#name-signaling-key-configuration - https://www.ietf.org/rfc/rfc9458.html#section-7-3 for our use case, since the payloads are uniform there's not much that can be learned from partitioned key configs, short IDs still link...

> Receiver side already enforced the size limit iiuc? that limit is only enforced after the request data was buffered in memory, the resource exhaustion concern is with payjoin-cli itself...

this issue was primarily about the payjoin-cli behavior both the payjoin and the payjoin-cli crates implements both the sender and receiver roles. in the payjoin crate, the receiver had limits,...

I would prefer to just switch to `tracing` in the payjoin crate, which is why I never took this out of draft (that's what I do in my local trees...

> I suppose GET range headers and padding could even be added to pjv2 after #364 is merged by making a default behavior to return a pre-defined number of bytes....

One of the papers I was alluding to is https://people.cs.umass.edu/~gbiss/mixing.pdf but I still can't remember what the other one is