jameshfisher/jameshfisher.com

jameshfisher.com

npm install
npm run build  # or npm run dev

jameshfisher.com's Issues

Backend Auth Issues with 2017-08-05-sign-in-with-google.md

Hi James,

I appreciate your article for doing Google SSO via a Golang app (2017-08-05-sign-in-with-google.md). I'm noticing that the frontend client works as expected, but the backend parsing doesn't seem to work anymore. Perhaps it's the change in the keys at https://www.googleapis.com/oauth2/v3/certs. There are now two, and they're no longer in PEM format. Just wanted to give a heads up, as your post shows in Google search results on this topic.

Licence?

Hello.

I quite like how your personal website is laid out. The simplicity of it appeals to me greatly. I was hoping to rip it off and use it for my own nefarious purposes. Would you consider adding a licence to this repo to aid me in my blatant derivative endeavours?

PS I also hate telephones

Reporting errors after standard error was closed

Regarding https://jameshfisher.com/2017/02/17/how-do-i-call-a-program-in-c-with-pipes.html:

In the version at the end with error handling, you may call perror() after standard error has already been closed. The underlying problem should maybe at least mentioned.

And the the file closing with error checking should better be renamed to something like do_close() so that it doesn't clash with the close() that it is calling in the function body.

CORS vs. "I can see your local web servers"

Regarding, http://http.jameshfisher.com/2019/05/26/i-can-see-your-local-web-servers:

When I open up a server on my local network and try out your page, the JS console log gives me:

Access to fetch at 'http://192.168.0.1/' from origin 'http://http.jameshfisher.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

It seems to me that in all cases the requests you're talking about should be blocked from getting any data (beyond information that the port is open) by CORS, as per the same origin policy unless the server you're talking to explicitly authorizes such requests from web pages served from other hosts. What am I missing here?

getaddrinfo: loading order question

Hi Jim, thank you for your articles, I've been learning tons recently.

I'm currently trying to reproduce the steps you have done on What does getaddrinfo do? and when running strace, I see the following:

openat(AT_FDCWD, "/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 5
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=304, ...}) = 0
openat(AT_FDCWD, "/etc/host.conf", O_RDONLY|O_CLOEXEC) = 5
openat(AT_FDCWD, "/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 5
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = 5
openat(AT_FDCWD, "/etc/hosts", O_RDONLY|O_CLOEXEC) = 5
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_dns.so.2", O_RDONLY|O_CLOEXEC) = 5
openat(AT_FDCWD, "/etc/gai.conf", O_RDONLY|O_CLOEXEC) = 5

But, in your article, you state that:

The file [...] /etc/resolv.conf is known by /lib/x86_64-linux-gnu/libnss_dns.so.2

How can ping load /etc/resolv.conf before loading libnss_dns.so if the path is only known by libnss_dns.so?
I am thinking it might have something to do with /etc/host.conf but even when commenting that file it still loads resolv.conf.

EDIT: after some deeper look it seems that resolv.conf is known by libresolv.so, which is loaded very early.

Blog post obsolete

https://jameshfisher.com/2017/08/30/how-do-i-make-a-full-width-iframe/
This blog post's examples don't work as intended on the latest Chrome.

The blog uses too much css!

https://jameshfisher.com/2016/11/15/no-css/ says that 128 bytes of CSS is enough, but I count 1504 bytes! Naughty naughty...

The dots do matter - email-domains too!

Hey James,
maybe you already know, but the same "trick" works with using an old "@googlemail.com" instead of "@gmail.com"...
I tried contacting netflix about this, but they just delete the "new" account.