HN user

rahulrav

175 karma

[ my public key: https://keybase.io/rahulrav; my proof: https://keybase.io/rahulrav/sigs/ETwNNdEyJh3KW-TWTePixrqcXhVWA_9FKFOcVqV0BqU ]

Posts9
Comments34
View on HN

I would have purchased your book ! I just wanted to say thank you for writing (your blog). It is a joy to read.

I agree. My goal here was to get something that look like bokeh if you squinted at it.

I just wanted to see how far I could take this idea.

Yes. That is correct. Just wanted to see if the idea in my head actually worked. I was surprised by how decent it turned out especially given that I did not do anything “clever”.

It’s a simple Gaussian kernel multiplied with a triangular mask.

You can do better by playing with intensities of pixel values as suggested in the article I linked.

This is a quick proof of concept of an idea. This won't work for every use-case but it worked surprisingly well for a use-case I had in mind. Happy to answer any questions.

The rules of the race are that you can't cut corners from inside the track. Going out of the track is a natural penalty, so it's allowed. The car actually slows down a bit.

The ML algorithm being used is called behavioral cloning (and it's cloning me). It's just that I am a pretty rusty RC car driver :)

The first time I was building Donkey for an entirely new (and previously unsupported) SBC - the Asus Tinkerboard S. I was also unfamiliar with how everything was put together.

The second time was a breeze. Jetson Nano runs Ubuntu so getting everything to work was relatively easy.

They already don’t show up if you use fragment URIs. The real issue I have is that the OAuth2 spec covers all this and we don’t have to rehash this every time a new IDP creates an Auth system.

No. The final post is not made by the client and a server has to handle the request. Webapps cannot handle POST requests from an Authorization server.

Unfortunately, Apple Sign In for the Web - insists on using HTTP POST's for the redirect_uri. This is a snippet from their official JavaScript library.

const t = { baseURI: "https://appleid.apple.com", path: "/auth/authorize", originURI: "", env: "prod", uxMode: "redirect", responseType: "code id_token", responseMode: "form_post", client: { clientId: "", scope: "", redirectURI: "", state: "" } };

Notice the responseMode which is set to form_post which I believe is the only supported mode.

This means you can no longer do things like localhost redirect_uri's for testing, or even use Apple Sign In on an internal web-app. Also, goes against OAuth2. :(

I submitted this feedback. Hopefully, someone takes a look.

“OAuth2 spec is long and complex”.

One of my 20% projects at Google was addressing this very problem. I built an OAuth2 and OpenID-Connect client library for the Web that is written in TypeScript. The library supports web apps, Node.js CLI & Electron based apps.

https://github.com/openid/AppAuth-JS

There are sister projects for Android and iOS as well. Hopefully, OAuth2 complexity will not prevent you from consuming a service going forward.

Uses SQL Cipher, which uses "Algorithms provided by the peer reviewed OpenSSL crypto library".

Given all the problems with OpenSSL, I really wished they used something like BoringSSL.