auxten

Anyone tried ClickHouse on CSV?

chDB author here, You are right, we have not made a static libchDB. BTW, I guess you are a golang developer?

Data operations are increasingly happening near the GPU side to boost efficiency—especially for compute-heavy workflows. Talking about Arrow file processing and zero-copy queries on DataFrames, which are becoming crucial for modern data pipelines. I think another option worth considering is chdb, which supports these features and fits well with this shift. (author of chdb here)

I think Human Layer is a great idea. Recently, my baby turned one year old, which made me reflect on many issues. We train AI with a lot of data but overlook the impact that decades of seemingly useless data from human growth experiences have on our brain development. As a result, humans still have an incomparable advantage over LLMs in terms of the so-called "big picture." For example, a recent experience I had was when I asked Claude 3.5-sonnet to write a bash script; it inadvertently modified the PATH variable, costing me a lot of time to fix it. Such attention to detail in work is difficult to avoid through vector db recall or manual context completion. But I believe that a true bash expert would not make such mistakes.

Yes, if not put it there. Everyone want to have a try need to register a Google Clould account

Interesting project. With chDB, the in-process ClickHouse engine you can make HTTP API a ClickHouse table. Here is a ClickHouse on Google Calendar example: https://github.com/auxten/SQL-On-Everything/tree/main/google... Btw, I'm the author of chDB.

Author of chDB here. For those who are interested, there is a blog post that explains how we created chDB. https://clickhouse.com/blog/chdb-embedded-clickhouse-rocket-....

Golang's forward compatibility and static compilation allow developers to quickly download and use the latest Golang release without the pain of upgrading like interpreted languages or VM-dependent languages.

Noted, thanks.

How does it compare to Apache Superset?

With JFS we can use S3 as a cheap backend of HDFS.

"Boutique Consultancy" is quite recapitulative for most AI companies for now. But this may be the only way to empower their clients. One of these startups will find the path to scale up eventually.

To be honest, I think most developers or App owner are not clear of that.

Maybe, we can just follow facebook.com: "Use with Consent"

Cookie description data is crawled from https://cookiepedia.co.uk/

And I put it into CQL Database for easier usage.

I really don't know the "PRO" label implies.

Technically, yes. I will have a try.

Any work you did on GitHub?

User private OAuth token is stored in the cookie. Forum clients can share the same token and also use their own token. Same DSN(database serial num) indicates the same forum.

Yes, SQL on blockchain is append-only. The SQLChain blocks can only be accessed with a granted private key. I think all public chains are facing the abuse problem.

First, it's open source. so it's free technically. And, as all the database miner node is distributed globally(not enought for now). By running a client you can visit the forum even from localhost, it's relatively hard to block the forum. But using database hosted by miners need to pay PTC. You can get PTC by replying to the [topic](https://demo.covenantsql.io/forum/#/t/2) with your wallet address.

CovenantForum stores data in CovenantSQL Miners which are selected and organized by the algorithm running by CovenantSQL BlockProducer. For more details, you can refer to: https://github.com/CovenantSQL/CovenantSQL#one-line-makes-da...

and https://github.com/CovenantSQL/CovenantForum#arch

CovenantSQL uses a CA less protocol to distribute log.

To implement a decentralized system, I wrote a TLS like P2P net stack. The main idea is removing CA Cert from the whole system by using a DHT for Naming and Key Exchange. I am not a crypto expert, so if there's any flaw please point it out for me here or Github I use an Elliptic Curve for asymmetric encryption

DH-RPC NodeID is generated by hash of Node PublicKey and an Uint256 Nonce:

    NodeID := sha256(blake2b-512(NodePublicKey + Uint256Nonce))

I refer to S/Kad idea to define the number of consecutive 0s in front of the NodeID as difficulty and to impose a minimum limit on the difficulty of the NodeID allowed to be stored on the DHT. DHT is used to hold the NodeID:PublicKey NodeID:Addr map. NodeID and Nonce are sent to do ECDH getting shared secret after TCP connection established. GenECDHSharedSecret(APub, BPriv) == GenECDHSharedSecret(BPub, APriv) The main procedure is described as sequence chart: https://github.com/CovenantSQL/CovenantSQL/blob/develop/logo... Because in the decentralized system NodeID is the URI, not "Bob/Alice.com". So anyone tries to fake NodeB by overwriting the address or public key on DHT without the private key of NodeB will be failed to get the correct shared secret.

Github: https://github.com/CovenantSQL/CovenantSQL/tree/develop/rpc

Yes, you are right. But I really can not find a proper word to describe this project. CovenantForum just stores all the data in CovenantSQL which is a database use blockchain to sync "binlog". CovenantForum also stores the pictures in database as blob.

The Demo is here: https://demo.covenantsql.io/forum/ All messages can be found on blockchain like this: https://github.com/CovenantSQL/CovenantForum#comments-on-blo...

Not in China where we work 12+ hours per day, 6+ days a week.

HSP is a simple solution: 1. No schema needed 2. No much pain to have a try

First, we have SQL support, Bigchaindb is MongoDB. CovenantSQL is written in Golang and C. Bigchaindb is written in Python. For more, you can refer our README

The website is fancy, but I believe https://github.com/CovenantSQL/CovenantSQL/tree/develop/rpc is way better “distributed private networking”

I refer to S/Kademlia's idea to define the number of consecutive 0s in front of the NodeID as difficulty and to impose a minimum limit on the difficulty of the NodeID allowed to be stored on the DHT. As the S/Kademlia paper said, they just use the PoW NodeID way to obviate Eclipse Attack(Make Kademlia Network Fork), Sybil Attack(Fake Nodes), Churn Attack(Frequently Join & Leave), Adversarial Routing(Spread Bad Route).

Adversarial Routing is a bit related to DOS Attack you described. As the DHT is a gossip protocol organized network, maybe some Peer Rating stuff with PoW NodeId will work out an intergalactic-internet scale DHT. Just a well behaved proper difficulty NodeID will be trusted to spread more NodeID routing info.