tgasson

Joined 14 years ago

Karma
51
Submissions
31
Member since
May 1
tom<at>gasson<dot>com<dot>au
View on Hacker News

Recent submissions

Comment · 1 year ago
Comment · 8 years ago
They'll struggle to get anywhere asking for cash. Australians generally carry little to no cash around
Comment · 9 years ago
Comment · 9 years ago
chrome://flags/#show-cert-link
Comment · 9 years ago
No, not part of graphql. Apollo Optics (no relation) is an option, or you can instrument the fields yourself just like you would implement any other instrumentation.
Comment · 9 years ago
> with GraphQL there are relations that get used through each other which is less straightforward to determine when pruning or updating your API

That can be easier since you can add metrics to each individual field rather than url, allowing you to deprecate rarely used fields knowing what you'll break and alert only those who are using it of the change

Comment · 9 years ago
Do you have any links to how the errors are passed through to the client? Do you mean that they imitate the incoming certificate exactly or send the information by some other method?
Comment · 9 years ago
You want to do that both on your intercepted LAN and with a direct connection and compare the results. If they both give the same results you can be happy your MitM proxy is at least treating insecure sites equivalently. You still lose the advantage that you browser will tell you why the site is insecure
Comment · 10 years ago
Comment · 11 years ago
Comment · 12 years ago
It's 4. The columns are the digits 1, 2, 3, 4, 5, 6, 7, 8, 9, 0 And the rows are the character used for that digit at that point in time.

At some point later 5 mutated from looking like 4 to as it is now.

Comment · 12 years ago
Comment · 13 years ago
Yes I have run into this issue myself. It is a public resource, if you're not logged in at all its fine or if you're recently logged in its fine.

It's the same reauth you sometimes get when visiting a public blogger site. It is an edge case, but quite unpredictable and hard to track down from client reports.

Comment · 13 years ago
This is great for prototypes but there's an edge case that breaks it's usefulness in live sites.

Sometimes google will make already logged in users reauthenticate. It will redirect to the authentication page and you'll get a bunch of HTML rather than json returned, and the user won't know why it's not working.

Comment · 13 years ago
No, because it needs to be checked out (that's the deployment). As a usual git server, yes --bare is the way to go. In this case you could alternatively use --bare in a ~/repos/example.com dir and set the $GIT_WORKING_DIR environment variable to ~/www/example.com for checkout.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton