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
The Gregorian calendar has a 400 year pattern of leap years. It turns out that that 400 year pattern happens to have a number of days that's a multiple of 7. This means date on day-of-week is not evenly distributed, but is a function of the pattern in that 400 year cycle.
Sometimes bash is the right tool:
$ for ((YEAR=2000; $YEAR < 2400; YEAR=$YEAR + 1)); do date --date="$YEAR-12-25 12:00" +"%w %a"; done | sort | uniq -c
58 0 Sun
56 1 Mon
58 2 Tue
57 3 Wed
57 4 Thu
58 5 Fri
56 6 Sat
1
I'd add that while there was a time when only Chrome supported the older FIDO U2F API, there wasn't a time when only Chrome supported WebAuthN, since Firefox shipped WebAuthN support before Chrome did (though only by a few weeks based on the versions in developer.mozilla.org/en-US/… ).
1
We should build the new housing in dense patterns that allow us to build good transit systems and environments where people can walk.
2
So I think 5% thresholds work reasonably well and 3.25% ones don't. Given that you could argue that lower thresholds produce a more representative/democratic result, I guess you could frame those as two points along your continuum, though. I'm a fan of the ~5% one...
I think different sorts of proportional systems have different problems, though. Set the threshold too low, and it's too easy for small parties to get in the legislature, which makes it hard to form coalitions (e.g., Israel uses 3.25%, compared to 5% in Germany & NZ).
1
... but those are the changes since you last opened it, not since you last actually reviewed it.
And once you've looked at that view of changes since you last opened the document, and closed it, you can't get it back.
So you're just supposed to review all 20 pages again?
2/2
Google Docs is such a pain sometimes...
If you don't have "Edit" access (i.e., only comment access) to a document you can't see its revision history.
Though when you first open the document, it offers to show you the changes since you last opened the document...
1/2
1
nope, as Cliff said, it's San Mateo County. I think it's just outside of Menlo Park city limits, in unincorporated SMC, but I'm not sure how much I trust OpenStreetMap's city boundaries...
1
2
goo.gl/maps/QDtN3gpFpFXdmE32…
Note that the photo is clearly westbound Sand Hill Road.
1
1
Whereas engines/browers with smaller shares can *sometimes* get real wins for their users, at least for a decent length of time, by blocking just the current technique rather than the entire underlying problem. 4/4
1
2
This means that larger-share engines need more thorough modelling of privacy like a security attack surface for privacy (or similar) mitigations to be equally effective (share of sites, time decay of effectiveness). 3/4
1
1
For example, a browser with larger market share that makes cross-site tracking ineffective will make a lot more sites move to fingerprinting than one with smaller market share. 2/N
1
A complicating factor here, in terms of the benefit for users, is that how much sites will work around these things varies depending on the market share of the browser. They'll do things for a browser with 30% share but might let the users of a 3% share browser go untracked. 1/N
1
One thing Palo Alto has over Mountain View: a greater share of the restaurants and shops are in multi-story buildings that have something else in them (on higher floors). (A pattern that could eventually become urban...)
I could go either way on the ground floor food/retail...
1
2
