PhistucK comments

Results 43 comments of


                                            PhistucK

Track open source contributions made with Janitor

(And a .stopnagging file that can stop those messages)

Track open source contributions made with Janitor

I plan to add this comment to my (hopefully) [next Chromium change list](https://chromium-review.googlesource.com/c/chromium/src/+/1154225) - ``` This commit was made possible by Janitor - https://janitor.technology ```

Add fields for identifying the security protocol, cipher, signature and so on

At the least, it is good for statistics and for potentially phasing out security protocols (and the rest of the details) for a given website. Analytics services can provide those...

Add fields for identifying the security protocol, cipher, signature and so on

Well, those fields only expose technical details about the connection and encryption, so nothing identifying.

Add fields for identifying the security protocol, cipher, signature and so on

@sleevi (in reply to https://github.com/w3c/resource-timing/issues/74#issuecomment-260548565) - I meant "ciphersuite data" of the used certificate, if that were not clear. I think the server knows about that, too.

Add fields for identifying the security protocol, cipher, signature and so on

I am not sure what the privacy concerns are here, especially if the server knows all of those already. Nothing I mentioned includes any identifying name or identifying detail -...

Add fields for identifying the security protocol, cipher, signature and so on

@sleevi - sorry for the short answer, but... For statistics and analytics, just like `nextHopProtocol`.

Add fields for identifying the security protocol, cipher, signature and so on

@sleevi - then why is it being added to Chrome?

Add fields for identifying the security protocol, cipher, signature and so on

@sleevi - was it a private argument? The thread does not seem to have any post by you. https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/Hs5-wPpCPZc/NOkvTgqQAQAJ

Limit the parallelism of user Chromium builds to 8 using an alias

If I understand the concept correctly, I feel like host-level affinity limits would be too limiting for the situations where someone needs a bit more power for a short while...