Bitdb dedicated topic. More info: https://bitdb.network

The way bitdb is ordering transactions is not good sometimes, here is an example : https://memo.cash/topic/IRC

Bitdb request : { "v": 3, "q": { "find": { "out.h1": "6d0c", "out.s2" : "IRC" }, "project": { "out.$": 1 } }, "r": { "f": "[ .[] | {msg: .out[0].s3} ]" } }

Real order is the one from memo for this topic. https://memo.cash/topic/Capitalism has the same problem

bitdb.network was fine yesterday. today i'm consistently getting this message "request timed out. try to construct a more efficient query" Is it just me?