Looks useful, but it depends on PipelineDB, a PostgreSQL extension for streaming data. Unfortunately PipelineDB hasn't been updated since May 2019 [0] when they were acquired by Confluent [1]. The former PipelineDB team appears to be focused on Confluent's KSQL product [2]. There's an open source "ksqlDB" but it appears to depend on Kafka, so it's not a 1:1 replacement for PipelineDB[3].

[0] https://github.com/pipelinedb/pipelinedb

[1] https://www.confluent.io/blog/pipelinedb-team-joins-confluen...

[2] https://www.confluent.io/blog/confluent-cloud-ksql-as-a-serv...

[3] https://ksqldb.io/quickstart.html

Yes, I'm relying on the "continuous views" feature of PipelineDB which is like autorefreshing materialized views. I'm planning to swap PipelineDB with TimescaleDB in near future

Most of the heavy lifting is done by Postgres/PipelineDB with Node.js as a simple wrapper so it's both performant and consumes less resources.

http://docs.pipelinedb.com/continuous-views.html

https://docs.timescale.com/latest/using-timescaledb/continuo...

I really like the look of this. And I really like the response here regarding "blockers" [0].

Is there any documented way to let users opt-out sans ublock:o (or other)? Or configure it to respect "Do Not Track"?

[0] https://github.com/sheshbabu/freshlytics/issues/12

Thanks!

> Is there any documented way to let users opt-out sans ublock:o (or other)? Or configure it to respect "Do Not Track"?

I initially wanted to implement DNT but there's a lot of confusion about whether it's useful or not. I'm not sure if there's a standardized way for users to opt-out.

How does it track individual users without cookies?

Yes, it doesn't actually track individual visitors as we can't use cookies or any fingerprinting methods.