A good idea in theory. When I was at uni, i designed a protocol for that, with the vision of having individual stores, "commerce article aggregators", and user apps that can query either stores directly or aggregators, all using the same interface, same user preferences and filters.
The base premise is the same: SQL is not a proper programming language and everyone knows it only because they have to. And I feel like everyone who knows SQL enough admits that, but still none of the 20+ attempts of a better language stuck on.
Because we already have databases we have to query and they speak only a dialect of SQL. If there were a lower-level machine-friendly instruction set for databases, it should target that.
For the last year, I've been working on a query language that aims to replace SQL and data frame libraries. It's continuation of my work on PRQL and EdgeQL.
Now I need feedback on usability, ergonomics and overall design. Read trough the examples, check out the CLI & tell me what could be better.
I use vyos instead of OpenWRT, but I'd presume OpenWRT can mirror a port? It'd be better to do it on your switch of course. But you could mirror your traffic going across the LAN-WAN barrier and direct it to a security onion install, it's an opensource IDS. It has pretty heavy demands, but traffic analysis is not an easy, computationally cheap task.
It's definitely not malicious intent. It's an inlined version of our new search engine that we'll release in early 2026, but already wanted to ship with Zensical. However, you're right that this might raise some eyebrows – we'll fix it with the next release.
reply