Also the same author:
Generally, I believe (Rabbit) R1 has the potential to change the world.
There is a pattern here.
HN user
[ my public key: https://keybase.io/rahulrav; my proof: https://keybase.io/rahulrav/sigs/ETwNNdEyJh3KW-TWTePixrqcXhVWA_9FKFOcVqV0BqU ]
Also the same author:
Generally, I believe (Rabbit) R1 has the potential to change the world.
There is a pattern here.
I would have purchased your book ! I just wanted to say thank you for writing (your blog). It is a joy to read.
Thanks for your kind words and the tip about using canonical names. Will take a look.
Based on my cursory look at `libremarkable`, the SDK looks a lot more capable. You will need to port the code from Python though :/
No, that is what looked okay to me. The font sizing on the Calendar is customizable.
You can also side load custom fonts. I am going to look into this, because the default fonts are a bit meh.
Thanks ! Happy to be able to nudge things along
I started to work on this, because this is something I hoped existed. If there is enough interest, I am open to commercializing it. Its super easy to setup, especially given all my code is already open source :)
Thanks for the feedback. Let me fix that.
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.
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.
Thanks so much !
Yes. Join the Slack channel. We can help you out if you have 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 :)
JetsonHacks is pretty great.
The ones I really enjoyed reading were:
https://www.pyimagesearch.com/deep-learning-computer-vision-...
https://www.machinelearningisfun.com/
and
https://www.amazon.com/Deep-Learning-Python-Francois-Chollet...
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.
My first car took about a week. The second one took a day. The total BOM was around 400$.
Note: I am not great with hardware.
Apologies. This is a new blog I am working on. Will fix it.
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.
The next time you need to do something like this, take a look at https://github.com/openid/AppAuth-JS.
Here is an example which uses Node, and obtains your access tokens. (https://github.com/openid/AppAuth-JS/blob/master/src/node_ap...)
Once you have that - you can make any API requests by using the correct Authorization headers.
I use the Tinkerboard S and I absolutely love it. It’s so much faster and the dedicated EMMC storage helps a lot. Try it. The ecosystem is much better than it used to be.
Thanks for the shoutout to AppAuth (https://appauth.io). It’s our 20% project at Google.
This is amazing.
“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.
You might want to look at https://github.com/google/physical-web.It's really great, and you could target SSDP as a starting point.
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.