Is there any reason why you're opting for a REST based API? For enamel, I've been pondering with Cap'n'proto. (It just recently (today!) gained support for the futures-preview api ).

Since REST is a bit 'all-or-noting' with respect to model fields, I'd argue that there may be options more suited to the task?
If we can come to an agreement here, we could at least join forces for the server. I'm not too fond of an electron UI, but since hypocloid is separate, that wouldn't even matter.

Hi! I'm working on a new UI for Hypocloid.

It's Vue based and I'm hoping to release a initial version soon!

I realize ragnarok isn't maintained but I thought I'd still try asking: I'm having issues with the fact that getting /threads/ with an empty query results in a 15MB response. It's too much to wait, and frankly the browser too doesn't like having tens of thousands of rows in the message list.

On notmuch cli I can use search --limit 20 --offset 100. I'm wondering if there's any similar functionality here? I wasn't sure if notmuch-rs supports it (I'm not much of a rust developer), and even if the original C implementation has it. If not, I'm wondering what was your plan about this issue :)

Thank you!