|
Michael Kleber
@
Log3overLog2
Boston, MA
|
|
Mathematician, at Google, keeping the web working. He/Him.
|
|
|
219
Tweetovi
|
109
Pratim
|
283
Osobe koje vas prate
|
| Tweetovi |
| Michael Kleber proslijedio/la je tweet | ||
|
إليزابيث 🇻🇦
@enchanteeq
|
2. velj |
|
the bishop of orlando is also the bishop of the moon, due to a canon law that says "any newly discovered territory would fall under the bishopric from whence the discovering expedition departed". his is therefore the largest catholic diocese, at over 14,000,000 square miles
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
1. velj |
|
Quite right. @Paul_Kinlan It would be great if chromestatus feature pages made it easy to see which will be fully enabled in a new milestone vs. be carefully ramped up over time.
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
1. velj |
|
It does not.
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
1. velj |
|
I don't know of any previous time when we've said an exact date. Note that even now we've only said "the week of Feb 17" and it's being re-broadcast as an exact date again :-/
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
1. velj |
|
The "Feb 4" date is when M80 goes stable, though even that takes some time to roll out to all users. Once that's done, we will ramp up this behavior change, with appropriate caution. I apologize again to people who thought they knew exactly when things were at risk of breaking.
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
1. velj |
|
FYI @stshank this is the normal way Chrome rolls out potentially breaking changes. See e.g. this old blog post on the subject: textslashplain.com/2017/10/18/chr…
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
1. velj |
|
I apologize if we made you think stuff was going to break on the wrong day.
Here's @ericlaw's explanation from 2018 of how Chrome rolls out dangerous things: textslashplain.com/2017/10/18/chr…
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
1. velj |
|
You should tweet a correction or apology, John; you're just wrong. Many roll-outs, and all dangerous ones, are controlled by an experiment fraction that we change over time. This is happening during Feb, after M80 rolls to stable on Feb 4, entirely as planned.
|
||
|
|
||
| Michael Kleber proslijedio/la je tweet | ||
|
Chrome Developers
@ChromiumDev
|
30. sij |
|
Need to dissect your cookies 🔪🍪 in preparation for Chrome's #samesite updates? Check out our new, in-depth guide to testing and debugging cookies with 🧰 DevTools and more!
chromium.org/updates/same-s… pic.twitter.com/SoWWElS63m
|
||
|
|
||
| Michael Kleber proslijedio/la je tweet | ||
|
Coffee, HIIT, and then Science
@CoffeeScience3
|
28. sij |
|
If He had given us vegetable shortening
If He had given us dairy-free creamer
If He had given us Rich’s non-dairy creamer
If He had given us Smart Balance margarine twitter.com/merriamwebster…
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
29. sij |
|
I'm proud of you. pic.twitter.com/kZr7zO9mOJ
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
25. sij |
|
Definitely a worry. Make 3p scripts less powerful than 1p, and you'll get 1p's re-hosting those scripts — which makes updating much harder, and so weakens the web's security stance.
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
24. sij |
|
Yup, I have. And I agree that now is not the time for more detailed public comment.
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
24. sij |
|
Um no. It would be more honest to say that the researchers only released POC code for versions of the attack that you patched.
twitter.com/justinschuh/st…
|
||
|
|
||
| Michael Kleber proslijedio/la je tweet | ||
|
Justin Schuh 🤬
@justinschuh
|
22. sij |
|
No, I can assure you that they still haven't fixed these issues, which is what made that blog post last year so weird. Apple didn't disclose the vulnerabilities or appropriately credit the researchers, but put out a post implying they fixed "something".
|
||
|
|
||
| Michael Kleber proslijedio/la je tweet | ||
|
Artur Janc
@arturjanc
|
22. sij |
|
Earlier today we published the details of a set of vulnerabilities in Safari's Intelligent Tracking Prevention privacy mechanism: arxiv.org/abs/2001.07421. They are... interesting. [1/9]
@kkotowicz @empijei @we1x
|
||
|
|
||
| Michael Kleber proslijedio/la je tweet | ||
|
Lukasz Olejnik
@lukOlejnik
|
22. sij |
|
Apple/Safari Intelligent Tracking Prevention is a mechanism intended to improve privacy. It was found to have privacy vulnerabilities allowing sites to track the user (and fingerprint), and to stealing web browser history of a user. Incredible find. arxiv.org/pdf/2001.07421… pic.twitter.com/HR48ulUoHK
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
21. sij |
|
Please join the discussion! We (incl. @harrison_char) are designing APIs, but that's always better when their users are in the conversation.
|
||
|
|
||
|
Michael Kleber
@Log3overLog2
|
20. sij |
|
Reading this was even better than watching the movie again. twitter.com/uzbadyubi/stat…
|
||
|
|
||
| Michael Kleber proslijedio/la je tweet | ||
|
Antoine Chambert-Loir
@achambertloir
|
19. sij |
|
At the recent Lean conference, Kevin Buzzard @XenaProject made a talk where he explains lucidly — but I feel bitterly — some aspects of the present development of mathematical proofs in the standard mathematical litterature.
This is worth meditating.
andrew.cmu.edu/user/avigad/me…
|
||
|
|
||