| @LeaVerou @svgeesus Awesome! Congrats, you two! (Twitter) | |
| @fantasai @TzviyaSiegman @robinberjon @svgeesus @w3c @dauwhe 🥰� (Twitter) | |
| @TzviyaSiegman @robinberjon @svgeesus @w3c @dauwhe When I first came to W3C, I had a beard. How times have changed! (Twitter) | |
| @svgeesus @dauwhe @jensimmons I confess, when the request for design review came in and before I clicked through to read it past the title, I assumed it was either a joke or someone testing the issue template changes we’ve made recently. (Twitter) | |
| @robinberjon @svgeesus Oh, that’s perfect. (Twitter) | |
| @svgeesus aka the best hour of television I’ve seen in years (Twitter) | |
| @svgeesus @glazou there is no possible world within which "fragmentainer" is acceptable. :) It's just unacceptable for a different reason. (Twitter) | |
| @heycam @svgeesus closest is U+FB00 U+0073, sadly. (Twitter) | |
| @glazou @svgeesus But can you ligaturize within a fragmentainer? (Twitter) | |
| RT @svgeesus: OH "a CSS line is 96 CSS characters" (Twitter) | |
| @svgeesus it was a sufficiently oblique reference that I suspect the speaker was earnest… (Twitter) | |
| @svgeesus I am *so* over gradient syntax. At this point, we could pick anything and authors will rejoice at their ability to ship N-1 rules. (Twitter) | |