# orderedItems[].object.content
@agwa I added a brief related work section now that references your authorize API docs and the thread where we were initially talking in. I also highlighted the points where the silentct design is different on a high-level based on the thread. See:

https://git.glasklar.is/rgdd/silentct/-/commit/2dd7cdc11d4e40fbcec19514ea79af639d0730e3

I'm more than happy to make tweaks if anything stands out from your perspective!

# orderedItems[].object.contentMap.en
@agwa I added a brief related work section now that references your authorize API docs and the thread where we were initially talking in. I also highlighted the points where the silentct design is different on a high-level based on the thread. See:

https://git.glasklar.is/rgdd/silentct/-/commit/2dd7cdc11d4e40fbcec19514ea79af639d0730e3

I'm more than happy to make tweaks if anything stands out from your perspective!

# orderedItems[].object.content
Is CT finally being added in Firefox and I somehow missed that?

https://bugzilla.mozilla.org/show_bug. cgi?id=1921525

If anyone is aware of more links/documentation related to this please share!

# orderedItems[].object.contentMap.en
Is CT finally being added in Firefox and I somehow missed that?

https://bugzilla.mozilla.org/show_bug. cgi?id=1921525

If anyone is aware of more links/documentation related to this please share!

# orderedItems[].object.content
@agwa @filippo Yep, exactly like that!

# orderedItems[].object.contentMap.en
@agwa @filippo Yep, exactly like that!

# orderedItems[].object.content
@agwa @filippo That leaves us at signed-note with hmac(s) where the body is a list of certs in PEM format. Getting cleaner for each toot! I'll try to write up something short soon so we can either iterate more on it or agree it seems reasonable. Sounds good?

How about we initiate the process of getting a c2sp spec namespace for the three of us to maintain -- name silentct?

# orderedItems[].object.contentMap.en
@agwa @filippo That leaves us at signed-note with hmac(s) where the body is a list of certs in PEM format. Getting cleaner for each toot! I'll try to write up something short soon so we can either iterate more on it or agree it seems reasonable. Sounds good?

How about we initiate the process of getting a c2sp spec namespace for the three of us to maintain -- name silentct?

# orderedItems[].object.content
@agwa @filippo You're right, good catch! I had the reason for using a chain mixed up with something unrelated (looking at the prototype it only makes decisions based on the end-entity certificates; so the chains are kind of just hanging around).

# orderedItems[].object.contentMap.en
@agwa @filippo You're right, good catch! I had the reason for using a chain mixed up with something unrelated (looking at the prototype it only makes decisions based on the end-entity certificates; so the chains are kind of just hanging around).

# orderedItems[].object.content
@filippo list of chains, each chain separated by something. Still important to agree on, and maybe a spec is good for branding/framing silent ct monitors. But don’t know, let’s think some more about it!

# orderedItems[].object.contentMap.en
@filippo list of chains, each chain separated by something. Still important to agree on, and maybe a spec is good for branding/framing silent ct monitors. But don’t know, let’s think some more about it!

# orderedItems[].object.content
@filippo I think I wasn't sure about the scoping of signed-note, and mostly thought of it as a format for asymmetric signatures. I don't see why we couldn't just add a signed-note type for this use though. WDYT?

# orderedItems[].object.contentMap.en
@filippo I think I wasn't sure about the scoping of signed-note, and mostly thought of it as a format for asymmetric signatures. I don't see why we couldn't just add a signed-note type for this use though. WDYT?

# orderedItems[].object.content
@agwa @filippo On the topic of trying to standardize something in c2sp or similar: I think that could be kept quite minimal. Basically: here's how we do msg+mac, monitors are expected to pull msg+mac (e.g., URL); and to verify msg+mac with a shared secret. Framing "this is an allowlist/bless method to build interoperable silent monitors".

Quick sketch of the current prototype format here: https://git.glasklar.is/rgdd/silentct/-/blob/main/docs/feedback.md?ref_type=heads

The name is terrible so please ignore that :).

# orderedItems[].object.contentMap.en
@agwa @filippo On the topic of trying to standardize something in c2sp or similar: I think that could be kept quite minimal. Basically: here's how we do msg+mac, monitors are expected to pull msg+mac (e.g., URL); and to verify msg+mac with a shared secret. Framing "this is an allowlist/bless method to build interoperable silent monitors".

Quick sketch of the current prototype format here: https://git.glasklar.is/rgdd/silentct/-/blob/main/docs/feedback.md?ref_type=heads

The name is terrible so please ignore that :).

# orderedItems[].object.content
@agwa @filippo Do you see any obvious issues with the above crude sketch? Otherwise I'm happy to just give it a go at some point and maybe fail miserably hehe :).

# orderedItems[].object.contentMap.en
@agwa @filippo Do you see any obvious issues with the above crude sketch? Otherwise I'm happy to just give it a go at some point and maybe fail miserably hehe :).

# orderedItems[].object.content
@agwa @filippo If it makes implementation easier I'm more than fine to have a reporting delay in the order of minutes to hours (but at least less than a working day or so).

# orderedItems[].object.contentMap.en
@agwa @filippo If it makes implementation easier I'm more than fine to have a reporting delay in the order of minutes to hours (but at least less than a working day or so).

# orderedItems[].object.content
@agwa @filippo My crude sketch is that I just want to run the monitor as if it was a daemon; but force it into a schedule that fits e.g. a CI pipeline. So more or less something like: start running every T time units, stop and restart (or similar) if it doesn't finish on time, and of course stop if the monitor managed to catch up with all logs. While the monitor is still catching up with a slow log, just continue running for the other logs.

# orderedItems[].object.contentMap.en
@agwa @filippo My crude sketch is that I just want to run the monitor as if it was a daemon; but force it into a schedule that fits e.g. a CI pipeline. So more or less something like: start running every T time units, stop and restart (or similar) if it doesn't finish on time, and of course stop if the monitor managed to catch up with all logs. While the monitor is still catching up with a slow log, just continue running for the other logs.

# orderedItems[].object.content
@agwa @filippo Thanks for the link -- I don't think I see these problems as major blockers, but they certainly need to be accounted for so many thanks for pointing them out!

# orderedItems[].object.contentMap.en
@agwa @filippo Thanks for the link -- I don't think I see these problems as major blockers, but they certainly need to be accounted for so many thanks for pointing them out!

# orderedItems[].object.content
Send me a DM somewhere if this sounds useful to you!

# orderedItems[].object.contentMap.en
Send me a DM somewhere if this sounds useful to you!

# orderedItems[].object.content
My RIPE Atlas probe is approaching 6 years with all-time 99.3% uptime. If anyone needs RIPE Atlas credits for network measurements and research purposes I'm more than happy to share mine.

# orderedItems[].object.contentMap.en
My RIPE Atlas probe is approaching 6 years with all-time 99.3% uptime. If anyone needs RIPE Atlas credits for network measurements and research purposes I'm more than happy to share mine.

# orderedItems[].object.content
@mc same here, really good advice and encouragement!

# orderedItems[].object.contentMap.en
@mc same here, really good advice and encouragement!

# orderedItems[].object.content
@filippo @agwa and I of course misread s/needed/need. But yes, agree it didn’t fly as well without witnessing. It’s part of why I liked pursuing the direction we’re on!

# orderedItems[].object.contentMap.en
@filippo @agwa and I of course misread s/needed/need. But yes, agree it didn’t fly as well without witnessing. It’s part of why I liked pursuing the direction we’re on!

# orderedItems[].object.content
Are you’re one of those people that don’t like speaking at conferences and get spooked the moment you’re wired up to a microphone?

I’ll share some wisdom from Al Cutter this week: no one wants you to fail. Everyone wants you to succeed. Think about that positive perspective next time you’re on the stage delivering an accepted talk!

# orderedItems[].object.contentMap.en
Are you’re one of those people that don’t like speaking at conferences and get spooked the moment you’re wired up to a microphone?

I’ll share some wisdom from Al Cutter this week: no one wants you to fail. Everyone wants you to succeed. Think about that positive perspective next time you’re on the stage delivering an accepted talk!

# orderedItems[].object.content
@filippo @agwa At the very least it wouldn’t be a terrible idea to write down something coherent. I.e., to share what we already know and still think about for the end-to-end story!

# orderedItems[].object.contentMap.en
@filippo @agwa At the very least it wouldn’t be a terrible idea to write down something coherent. I.e., to share what we already know and still think about for the end-to-end story!

# orderedItems[].object.content
@filippo @agwa Yeah, I was looking for some note about maybe pinning the certspot HTTPS key or similar. As the command-line tools which do submission probably don't enforce CT.

# orderedItems[].object.contentMap.en
@filippo @agwa Yeah, I was looking for some note about maybe pinning the certspot HTTPS key or similar. As the command-line tools which do submission probably don't enforce CT.

# orderedItems[].object.content
@filippo @agwa What I've had in mind for the "map" part is a data structure that provides (non-)membership proofs for wildcard queries. How I initially thought of it is described here:

https://arxiv.org/abs/1711.03952

Not 100% sure if the many small batches part is essential or not, but (non-)membership proofs for wildcard queries seems better than exact-matching as in a typical map?

What makes the approach more practical since the paper was written: witnessing to solve split-views.

# orderedItems[].object.contentMap.en
@filippo @agwa What I've had in mind for the "map" part is a data structure that provides (non-)membership proofs for wildcard queries. How I initially thought of it is described here:

https://arxiv.org/abs/1711.03952

Not 100% sure if the many small batches part is essential or not, but (non-)membership proofs for wildcard queries seems better than exact-matching as in a typical map?

What makes the approach more practical since the paper was written: witnessing to solve split-views.