Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aeijdenberg
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
aeijdenberg
10y ago
Have you considered transferring to a different team with a different project in the same company? Generally this is much easier than moving to a new company, you get to keep any accrued benefits of tenure, and in a big tech company the cul
32.
▲
by
aeijdenberg
10y ago
I think the single best thing an API designer should do is write a getting started guide with working sample code for the API they are producing. On my last project I found myself revising the API surface twice as a result of doing so.
33.
▲
by
aeijdenberg
10y ago
If you accept that for many uses of publicly verifiable data structures that centralization is actually OK (and actually often a good thing, as it matches well how most democratic societies function), then there are other simpler alternativ
34.
▲
by
aeijdenberg
10y ago
I've been working on something pretty akin to what you describe, hosted verifiable data structures (logs and maps). Rather than Blockchain it uses the same data structures as Certificate Transparency to provide equivalent functionality
35.
▲
Show HN: Continusec Key Transparency Server
(github.com)
1 points
by
aeijdenberg
10y ago
|
0 comments
36.
▲
by
aeijdenberg
11y ago
YQ surcharges are just another element an airline can choose to muck with to bump up or down the ticket price. As an end user I wouldn't bother reading anything into it - the total price is the total price regardless of how the airline
37.
▲
by
aeijdenberg
11y ago
> nor should Google be being informed every time I obtain or renew a certificate. Let's Encrypt actually log all certificates they issue to a number of public logs, including those operated by Google. See the "Certificate Trans
38.
▲
by
aeijdenberg
11y ago
The article looks at common sense from the passenger point of view, but in fact if you look at it from an airline point of view you can sometimes see a very different picture. For example, take the following 2 principles, each of which make
39.
▲
by
aeijdenberg
11y ago
See also Certificate Transparency (RFC6962) which I haven't seen mentioned in this thread yet - the goals of which are to require all certificates be written to publicly auditable, tamper-proof logs in order to be considered secure by