This project is a tiny compiler for a very simple language consisting of boolean expression.
The language has two constants: 1 for true and 0 for false, and 4 logic gates:
! (not), & (and), | (or), and ^ (xor).
It can also use parentheses to manage priorities.
Here is its grammar in BNF format:
expr ::= "0" | "1"
| enum State { | |
| Idle, | |
| LoadingJwt, | |
| Success, | |
| Error, | |
| } | |
| type Data = { error?: string; jwt?: string }; | |
| function Comp() { |
| <html> | |
| <head> | |
| <title>Stripe Gradient</title> | |
| </head> | |
| <body> | |
| <canvas id="gradient-canvas" data-js-darken-top data-transition-in> | |
| <!-- | |
| Remove data-js-darken-top to keep the same brightness in the upper part of the canvas | |
| --> | |
| </canvas> |
I've spent the day trying to get this setup working with GitHub and given the number of gotcha's I encountered, it seemed like a good idea to document how I finally got this working with as few hacks as possible. There's a lot of documentation out there (some of it old and misleading) and committing here for posterity will help me remember this when I inevitably need to do this again.
Passwords are simply not enough these days. Regardless of the company, breaches (and the associated Personally Identifiable Information harvested) are a matter of not if, but when. There are a number of things you can do to protect yourself, but being on the tin-foil-hat side of paranoia, means there are a few Commandents that I adhere to (and recommend for other folks)[Insert link to Fight Club Rules for the Secure Internet].
That being said, if you use 2-factor authentication and have committed to using a hardware token such as the Yubikey, then you're already ahead of the curve. The problem is that wh
| @supports (padding-top: constant(safe-area-inset-top)) { | |
| body { | |
| padding: env(safe-area-inset-top) env(safe-area-inset-right) env(safe-area-inset-bottom) env(safe-area-inset-left); | |
| } | |
| } | |
| @media (display-mode: fullscreen) { | |
| body { | |
| padding: 0; | |
| } |
This is a simple Tailwind plugin to expose all of Tailwind's colors, including any custom ones, as custom css properties on the :root element.
There are a couple of main reasons this is helpful:
See the Tailwind Plugins for more info on plugins.
| const MY_DOMAIN = "agodrich.com" | |
| const START_PAGE = "https://www.notion.so/gatsby-starter-notion-2c5e3d685aa341088d4cd8daca52fcc2" | |
| const DISQUS_SHORTNAME = "agodrich" | |
| addEventListener('fetch', event => { | |
| event.respondWith(fetchAndApply(event.request)) | |
| }) | |
| const corsHeaders = { | |
| "Access-Control-Allow-Origin": "*", |
Modern OpenSSH has native support for FIDO Authentication. Its much simpler and should also be more stable with less moving parts. OpenSSH also now has support for signing arbitary files witch can be used as replacement of gnupg. Git also supports signing commits/tags with ssh keys.
ssh, ssh-add and ssh-keygen on most computers
I largely followed Florin's blog post, but have a few notes to add regarding issues I encountered:
gpg-agent only automatically starts when gpg is used; for ssh, you'll need to ensure it's running.list command inside gpg --edit-card, look for the Key attributes line to see what is currently selected. On my YubiKey 4, it defaulted to 2048 bits for all keys:Key attributes ...: rsa2048 rsa2048 rsa2048