Engineer on @googlechrome. Involved in CSS and W3C standards. Previously @mozilla, @w3ctag. Mastodon: @dbaron@w3c.social
Rockville, Maryland, USA
Joined March 2008
- Tweets 7,521
- Following 1,244
- Followers 4,296
- Likes 18,519
And don't forget that people who have their own businesses aren't eligible, so the numbers are really worse than that.
1
L. David Baron @dbaron@w3c.social retweeted
The New York Times worked with a doctor to film 72 hours at Elmhurst, the hospital that's been hardest hit by the coronavirus outbreak in NY. The result is an extraordinary piece of video journalism
Everybody should watch this: nytimes.com/video/nyregion/1… (by @robinnyc7/@rarecanary)
320
8,792
869
12,931
So the inclusion of "push" in that list, rather than being in a separate field, mean I can't filter on the reason I'm getting notifications for that PR (i.e., which of the others in the list it actually is).
And to follow up a little bit more, I'd note that all the Cc/X-GitHub-Reason types listed in help.github.com/en/github/re… except for "push" and "your_activity" are about answering "why am I getting email for this PR". But those two (especially the first) are orthogonal to it.
1
1
Yeah, I'm already filtering based on both List-ID and X-GitHub-Reason -- it's just that it doesn't do what I want because "push" is a broken X-GitHub-Reason.
1
1
I'm already doing my filtering based on X-GitHub-Reason.
My problem is that "push" is an X-GitHub-Reason when it's really the type of notification, not the reason you're getting it. So I can't distinguish the reason I'm getting the notification when it's about pushes.
1
In my github email notifications I'm never the "To:" (which is the repository) and *always* the "Cc:", so I don't see how this would help.
Maybe you have earlier filters for mentioned or created? But if so, I think they'll *miss* emails about pushes on issues you created.
1
In an effort to keep the noise down, I've decided to treat "push" like "subscribe" and put it in the bulk-email folder. So if I interact with a PR in csswg-drafts or some other standards repository that I watch, I simply won't see the notifications about followup commits.
1
My latest problem is notifications of type "push", for which it doesn't appear possible to distinguish between PRs that I've interacted with versus ones where I'm just watching the entire repo. I think it's the only one listed in help.github.com/en/github/re… where I can't tell.
1
1
I keep thinking I have this set up right, and then realizing I don't. Realizing I don't usually involves trying to keep up with my github email and realizing it's still filtered wrong (which may be part of why I tend to ignore it in the first place).
1
To put it another way, for *some* repositories, I want my github email notifications to go to a separate (higher-volume) mailbox if it's an issue that I haven't actually interacted with.
1
I want to filter @github email notifications based on two things:
1. whether it's an issue I've interacted with or I'm getting the email just because I'm subscribed to notifications for the repository
2. what repository it is.
2
1
5
Today's bread pictured.
I did settle for non-organic Gold Medal Bread Flour (from 99 Ranch in Mountain View) on our grocery run last week, although still probably 6 cups away from having to open it.
I also have decent stocks of Rye and Spelt flour that I use quite slowly.
1
1
L. David Baron @dbaron@w3c.social retweeted
Right now the smartest people I talk to want us to push R0 to zero, and be able to contract trace, install thermal indicators, reliable anti-body testing, and out fever tents in the right place.
Armchair experts and economic hacks feel different.27/
27
499
24
2,102
That's all the same loaf, just at different times.
(Tried a different technique today, which let me make one larger loaf rather than two smaller ones. I'll see how it turns out...)
Service reliability seems likely to be dependent on location. For example, in a city center, this seems less likely to be necessary. (Lines on telephone poles versus buried lines make a big difference, I think. But buried lines are prohibitively expensive where less dense.)
1