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
1. Bill Clinton
2. Al Gore
3. Nelson Mandela
4. Richard Nixon
5. Barack Obama
(I'm being a bit generous with "a few feet"; I'm including "in the same auditorium as" and "saw their motorcade go past from the sidewalk". But that makes it a little more interesting.)
List 5 famous people you've either met or have been within a few feet of, but ONE is a lie. Then let your friends guess which one they think is a lie.
1. Mickey Rourke
2. Al Pacino
3. Bobby Orr
4. James Earl Jones
5. Charlie Sheen
Who is my lie?
1
L. David Baron @dbaron@w3c.social retweeted
He killed George Floyd over a $20 counterfeit bill while he underreported $464,433 in joint income and owes $21,853 in taxes.
My god.
Fired Minneapolis officer Derek Chauvin and his wife are charged with tax crimes allegedly dating back to 2014. strib.mn/3fMC6nn
809
129,150
1,361
349,204
L. David Baron @dbaron@w3c.social retweeted
Obama didn’t brag half as much about winning a Nobel Peace Prize as Trump is about passing a dementia test.
2,621
54,975
2,701
287,605
Sounds a lot like what happened to the Russian consulates in San Francisco (nytimes.com/2017/08/31/us/po…) and Seattle (nytimes.com/2018/03/29/world…) a few years ago.
1
2
L. David Baron @dbaron@w3c.social retweeted
There is a #tsunami #warning for South #Alaska and the Alaska Peninsula for a 7.4 magnitude #earthquake. No warning yet for anywhere else. #PTWC #NTWC.
tsunami.gov/events/PAAQ/2020…
24
538
93
769
Also, I'd note that for Web NFC in Chrome, I don't think the permissions are scoped to devices. I think it's just permission to use NFC or not.
1
I agree executables are often dangerous.
However, as long as the Web is a multi-vendor multi-OS platform, there will be things you can do in native apps on at least some platforms that the Web can't do. So some level of unusual or new things will always need native code/apps.
2
Yubikeys happen to be well-known devices; given that there are lots of less-well-known devices out there, it seems likely they're not the only ones with that sort of problem.
(I think that issue was first raised in github.com/mozilla/standards… and led to devices being blocklisted.)
1
One concern from Mozilla folks is that it exposes to the Web things that weren't designed with the knowledge that they'd be exposed to arbitrary Web content. (There should be straightforward ways to address this.)
This isn't theoretical; see blocklisting of Yubikeys in WebNFC.
2
4
Seems pretty easy in Firefox, where the default for camera/mic permissions is not to remember the permission (though it's easy if you want to).
1
8
L. David Baron @dbaron@w3c.social retweeted
Philly @DA_LarryKrasner is threatening to criminally charge federal agents if they are sent to Philadelphia and "assault" or "kidnap" people.
42
721
116
2,100
L. David Baron @dbaron@w3c.social retweeted
"In 2017, the idea of unidentified agents in camouflage snatching leftists off the streets without warrants might have seemed like a febrile Resistance fantasy. Now it’s happening," writes @michelleinbklyn. nyti.ms/3eUa6Nz
75
375
39
635
L. David Baron @dbaron@w3c.social retweeted
I should be more specific. What are Democrats going to do given that the House is voting on a DHS appropriations bill next week?
Unidentified stormtroopers. Unmarked cars. Kidnapping protesters and causing severe injuries in response to graffiti.
These are not the actions of a democratic republic.
@DHSgov’s actions in Portland undermine its mission.
Trump & his stormtroopers must be stopped.
110
1,125
98
3,913
Old code (before tokio/futures update):
github.com/dbaron/wgmeeting-…
Old code (after tokio/futures update):
github.com/dbaron/wgmeeting-…
New code:
github.com/dbaron/wgmeeting-…
Much nicer.
(I admit I don't write a whole lot of rust, so I'm sure my code is non-idiomatic in various ways.)
5/5
3
That said, I'd note that there was also one unfair advantage with the new way, which is that one of my dependent libraries, crates.io/crates/irc , has restructured to get along a better with the new tokio/futures infrastructure than it did with the old.
4/5
1
It feels like a big improvement -- and probably a bigger difference than the introduction of async/await in Javascript.
3/5
1
1
Using futures and streams with chained callback functions (the old way) instead of async/await (the new way) led to lots of struggling over ownership and lifetimes (and fighting with the borrow checker). In the same code restructured to use async/await, it's much easier.
2/5
1
1
The past two days I've had a chance to use async/await in Rust for the first time. It was a useful comparison against the old way since I was refactoring existing code to use it.
It made things *much* easier and simpler.
1/5
1
6
L. David Baron @dbaron@w3c.social retweeted
Do not get lost in a sea of despair. Be hopeful, be optimistic. Our struggle is not the struggle of a day, a week, a month, or a year, it is the struggle of a lifetime. Never, ever be afraid to make some noise and get in good trouble, necessary trouble. #goodtrouble
4,026
94,067
10,271
202,701