Consider supporting names tiles

[FiloSottile]

If my read of the code is correct, Certstream doesn't verify cryptographic inclusion proofs, and is primarily interested in the names on certificates. In that case, it could use the names tiles to reduce bandwidth and processing costs on both sides.

https://github.com/FiloSottile/sunlight/blob/main/names-tiles.md

Names tiles are gzip'd JSON Lines tiles that correspond to the data/partial tiles, containing entries in a format like

{
    "Timestamp": 1753375092043,
    "Subject": {
        "CommonName": "example.com"
    },
    "DNS": [
        "example.com",
        "www.example.com"
    ]
}

Do you think they would work for Certstream?

[d-Rickyy-b]

is primarily interested in the names on certificates

Well yes and no. Certstream offers there endpoints clients can connect to. One of which only delivers the domain names. The other two deliver various information about the certificates (up to the whole certificate in DER encoding). While I do think that the names tiles are a truly helpful extension to the ct ecosystem, I don't think they are particularly useful for the certstream project since they would only provide the necessary data for one of three endpoints.

Maybe I could add a config option for any operator to decide if they want full certificates or domain names only. The latter would only work for static ct logs but hey, at least they'd save on bandwidth and compute.

I do appreciate the suggestion though. Reducing bandwidth and processing cost definitely is something I support. I'll leave the issue open for others to comment on the idea.

[uggyuggy]

I do use only "domain names".. so as far as I understand, a config option to "force" that, and save bandwidth and compute could be a nice feature.