Excerpt from the new README:

## timeline
2015: first bingo! [eli](https://twitter.com/veryeli) and i used the attendee
directory to generate a unique card for everyone (twitter login kept it private
🔒). squares on your card were other attendees - if you met someone on your
card you got to check it off. we made it cuz we’re shy. most of it is in the
`pre-2019` folder!

2016: we made the cards prettier by pulling in people’s twitter photos and
doing imgmagick to them 🔮

2017: no xoxo, no bingo… missed u all

2018: xoxo was in the midst of changing their infrastructure, so i lost access
to the attendee directory. [hannah](https://twitter.com/herlifeinpixels),
[jason](https://twitter.com/justsomeguy) and i met in a cafe before the kickoff
ceremony and designed a static version with input from the community. hannah
and jason made 25 icons in like two minutes, it was incredible!!!

2019: i've been too cheap to get https://xoxo.bingo in previous years, but
[andy](https://twitter.com/andymcmillan) noticed a thread on slack and hooked
us up! thx andy.

leading up to xoxo2018, i realized we wouldn't have access to the new
attendee registry. andy and i
discussed ad-hoc private access and other ways to make it work, but it
was too much. so hannah, jason and i made a static version with
"achievements" sourced from the slack community.

it was fun to get excited about things specific to that year, like the
podcast airstream and the blue ox. and it's gonna be that way from now
on! feel free to create an issue or msg on slack if you have ideas for
this year's bingo squares.

since it's staying a static site, i moved everything off of heroku.
all site content will live in 2019-and-on/.

I'm experimenting with auto-generating nodes for
https://rileyjshaw.com/lab from a variety of data sources. This
project may eventually replace https://rileyjshaw.com.

This is the initial commit, completed quickly as a proof of concept.
There's nothing much to show, but I want to deploy ASAP so I can test
the full pipeline.

So far, everything has worked! Data from a variety of sources is
already appearing on my local server. To reproduce:

• Run gatsby develop.
• Open http://localhost:8000/page-2 in a browser.

So far, I'm surfacing data from:

• A hand-curated JSON list of projects I use for
  https://rileyjshaw.com/lab.
• Dwitter's API.
• My commit--blog's Atom feed.

Setting this up was EASY, which makes me excited for the future of
this experiment :)

I started this repository in the spirit of OpenFrameworks and
TouchDesigner: I wanted all the libraries I might need close at hand,
with a simple, abstracted API for drawing to , SVG, etc. I
wanted a personal playpen / pigpen to test ideas in.

For that reason, I didn't need nice features like routing or pages.
:) if I wanted to see an old sketch, I'd change the root component
and re-render. It worked for me!

But I planned to eventually make an easier way to browse existing
experiments. It would benefit me a bit, and casual viewers a lot.

I haven't updated this repository in nearly two years, and I honestly
never expect to again. I'm doing less browser-based creative coding
these days, and trying to stretch my work in other directions.

About an hour ago, I decided to create an index page or dropdown
to close this project out and keep it accessible in perpetuity. When I
cloned the repo and started looking at the build pipeline, I almost
noped the whole idea. I built this with create-react-app, so even
adding new pages for each project the recommended way involves:

1. Installing some sort of React-compliant router.
2. Spending… hours? figuring out which version of which router
   works with the project's outdated dependencies, OR,
3. Upgrading the entire project, likely involving major upgrades to
   Webpack, Babel, etc.
4. Installing something called react-snapshot,
   which apparently builds static files for you? But there's still
   a pushState history API? The README listed some tutorials, so I
   opened them.
5. …once I'd reached this point, I realized I'd need another method if
   I wanted to be done within the hour.

At that point, I could have searched the web for "create-react-app
static routes 2017 easy" and gone down that rabbit hole before giving
up. OR, I could have given up immediately. Or I could do what I did,
which was a good idea:

I changed the root component 38 times by hand, typed "npm run build"
into my terminal by hand, and dragged the built files BY HAND into
unique directories that I created BY HAND.

Gasp!

I spent another minute in my editor surrounding the output of ls -d
with anchor tags for a root index. (yes, by hand)

The most time-intensive part of the process was writing this commit
message. I'm confident if I'd tried to automate the process or rebuilt
the project "the right way", I'd be at this for a few more hours.

The result is a little sketchy. Namely, I'm sure the total payload of
each page is a bit bigger, and caching takes a hit. But I think an
extra kilobyte will be tolerated by the 3 people who ever visit this
corner of my website.

And wow it was so easy. And if I ever decide to add a new sketch, I
can do the same simple steps by hand. No dependency mismatch with my
local versions. No reading old docs. Just build, drag, repeat,
forever.

I guess I'm writing this as a reminder to myself: it's usually
possible to break back out to 1995 in a pinch.

I love the tidal wave of projects on /lab,
and I want to emphasize that for v3.0 of the website. I update pages
across the web daily; Glitch, Codepen, gist.github.com, Dwitter,
Hackster, etc. Plus there's social media…

I'm okay with manual curation for the most part, but for websites like
Dwitter where contributions are inherently unpolished / untitled, it
doesn't make sense for me to hand-pick and manually update a giant
list.

Also: I'm not sure how long Dwitter will be around for. Periodically
saving the underlying code / images / etc. gives me more ownership
over the presentation and preservation of my data. It changes my
relationship with these sites from content hosts to publishing
platforms. That makes me feel more secure with my zillion links.

TODO(?): Automatically fetch new content during the publishing step?

I've decided to upgrade my website! The
blog and lab
are moving to the same page. I'm also going to add
more content types, like songs, galleries, and
videos. As I migrate things over, I'll be
backfilling my blog with content to test with.

The CA post is an example of filler content.

As mentioned in https://developer.mozilla.org/en-US/docs/Web/API/Performance/now:

Firefox started rounding to 1 millisecond in Firefox 60.

This commit updates the performance.now() compatibility table to match the rest of the article.

Well, it's time.

When I made this website, I decided against adding an /about page. The
site was a sandbox to dump anything I happened to build / write /
imagine while attending Hacker School, and an /about page seemed
limiting. As the site grew, it grew weirder. I decided that its lack
of context was an asset. I have some free usertesting.com recordings
from 2015 that prove the site made no sense. I loved them.

But the real reason I never had an /about page is that I didn't want
to talk about myself.

Exactly a year ago, I retired my portfolio page.
I've recently begun applying for grants, and having some context on
who is behind this site is important.

The real problem is that this site is old; an /about page is an easy
stopgap. This site does not represent me well anymore; I don't know
why I still have links to my blog, for example. I would like to strip
the site down, and think about the intended audience. But that sort of
thing takes time, and I'm making the conscious decision to not
prioritize my personal site for now.

There are many technical goals I would keep in mind if I were to
rebuild my website:

• Cut dependencies and bundle size to make things faster.
• Move off of Ruby, Jekyll, Bower, and Grunt.
• Do not center particular frameworks or technologies on the new site.
  • Reorganize the file structure to be more modular and declarative. _data/lab/* is a great example.
• Have it available over the dat:// protocol, and accessible offline.

And I'd like to keep it weird.

The previous version of this library assumed use on RGB native
platforms, eg. web browsers. This had some consequences for HSL/HSB
devices (eg. Philips Hue lightbulbs), where 100% lightness does not
necessarily imply white light.

v2 uses some trig functions that are slower than the v1 algorithm. For
super fast averaging, v1 is still your best bet.

...Including jQuery!? That was easier than expected.

Meta Key + click to create a new text box anywhere on the page, then
just start typing!

Guess I'm never going back to a terminal that doesn't support unicode…

1 ahead, 0 behind

5 ahead, 2 behind

I'm about to go through a series of refactors, and want a quick visual
indication of whether I'm adding or removing lines of code overall.
This change shows whether I'm red or green from the upstream branch
and from HEAD.

It's a bit slow. I'd like to speed it up if this works out.

URL encodings - they%27ll get ya.

Wow. This, big time:
http://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/

Test Plan:

• npm run lint
• npm run test

Tested on latest IE, Firefox, Chrome, Safari.

Screenshot:

It's responsive, too!

Initially, this extension grabbed the content of a CSS file with an XMLHttpRequest and injected it into the bottom of the page. This had a few advantages:

1. Text content could be easy processed and manipulated (admittedly, I wasn't using this for anything).
2. Toggling styles was as easy as adding and removing a element from <body>.</li> <li>In theory, this strategy would beat out almost every other style rule (some inline styles excepted). <a href="http://www.w3.org/TR/CSS2/cascade.html#cascading-order">User <code>!important</code> rules used to override author <code>!important</code> rules</a>, but Chrome <a href="https://src.chromium.org/viewvc/chrome?revision=234007&amp;view=revision">no-longer does user stylesheets</a>. I figured an aggressively <code>!important</code> author stylesheet added at the very bottom of the page was pretty solid.</li> </ol> <p>After some testing, I realized that <code>!important</code> styles from <code>content_scripts</code> injection (along with chrome.tabs.insertCSS) actually <em>do</em> take precedence over author stylesheets. Since 3) was the key consideration for my original decision, I re-wrote the extension to inject a stylesheet from <code>content_scripts</code>.</p> <p>This change in architecture had pros and cons.</p> <pre><code>+ Improved chance of dark theme winning out over author styles. + Allowed styles to be applied before any other DOM is constructed, substantially reducing time-to-darkness. + Simplified the callbacks between background.js and client.js, reduced code, and made the entire extension easier to reason about. - With 1) above, I could&#39;ve handled variant rules (eg. specificityHelper) with a few regular expressions. Locking into a static stylesheet added some huge copypastas, tripling the size of main.css. - Injected stylesheets aren&#39;t accessible once they&#39;ve been added. Rather than &quot;turning the styles off&quot; like in 2), the best option was to add a toggle class to &lt;body&gt;. - Rewrites take time. </code></pre> <p>This commit was essentially a full rewrite, so I changed some smaller things while I was at it:</p> <ul> <li>Styles now look for :not(.off) instead of .on. This makes the default dark and avoids a Blinding White Flash before the class changes.</li> <li>Added id specificity helpers; it&#39;s discussed further in client.js:24.</li> <li>Renamed some files for clarity.</li> </ul> <p>I came across some unfortunate Chromium bugs while working on this, which caused me to dive into that project. It&#39;s huge! Lots of fun to poke around :)</p>

1, 2, 3, and 4 are useful for app-specific bindings and should thus be reserved.