@bramus So happy for you to join us! Congratulations and welcome to the team! 🎈
This is what evil looks like: https://t.co/knFrRV6spj (Russian original, English translation: https://t.co/sOFlWi3kPw). Professor of History at Yale University @TimothyDSnyder called the article a “genocide handbook” in https://t.co/F66RwLHU2P.
#StopPutin
@dluzar Happy the mystery got solved. Another idea would be to simply add a timestamp to the data and check if the stored data is more current than the to-be-stored data.
An @excalidraw data loss mystery solved: Always be careful with automatic reloading, service workers, and storing data just before unloading a page! (The quoted tweet is from the middle of a thread.) https://t.co/39E5U0KYmm
@Lance_I_ @ericwbailey I came here to say this. It should just be a built-in accessibility feature. Or actually, not even be tied to accessibility: Ever tried using a phone in a bike mount? I get it needs “wobble†room, so probably makes most sense on
@alexanderdanilo @mozhacks @webkit @behdadesfahbod Interesting background. @abrax5 probably can add more from his view. COLRv1 also seems to be somewhat dependent on (the way) Skia (does things).
I can’t judge the technical accuracy of the claims, but it’s interesting to read the two assessments:
@mozhacks: “more compact and lightweight than OT-SVG†https://t.co/uRh0tq4NAg
@webkit: “we’re not confident that it can be implemented intero
The struggle of using native emoji on the web, by N. Lawson. I wrote in a comment that COLRv1 might be an answer: The format got positive feedback from â¦@ChromiumDevâ© (implementer) and â¦@mozhacksâ© (worth prototyping)—just â¦@webkitâ©â€™s meh.