The package sets up a local server and a Cloudflare tunnel to let custom GPTs run almost all Shortcuts actions supported by macOS and read iMessages. Everything stays private between you and your ChatGPT. Here’s setting it up to help me coordinate my schedule with friends:

We built a lil toy to give GPTs access to your Mac: https://t.co/KUZWnjAUof Me: complain to my landlord for me and my roommates pls 🥺 GPT: (reads iMessage chat with roomies, summarizes complaints, finds our landlord’s email, pulls up a drafted email)

sRGB has ~899,155 distinct colors, Display P3 has ~1,354,483 distinct colors (~50% more) to the average human eyes (ΔE³ estimates from Monte Carlo simulations with ICCView by Tobias Huneke and argyllcms by Graeme Gill)

Perceptual color distance can be measured with euclidean distance in L*a*b* space (ΔE), hence the # of perceptually distinct colors is the volume of the gamut. Plugging the tristimulus coordinates (XYZ) of each primary of the two profiles, we can see from ΔE³ that... 11/

...and hence were not representable in sRGB (ignoring quantization) 8,139,790 brand new colors / 2^24 colors in sRGB is ~49%! Note that not all these colors are distinguishable to the human eye, but % of new perceptually distinct colors is in that ballpack too. 10/

Wait but ... where did the 49% number come from? Both sRGB and Display P3 colors in @figma are 24-bit depth (8-bit per channel; excl. alpha) 8,139,790 of the 2^24 = 16,777,216 values introduced in Display P3 were outside the sRGB gamut... 9/

🥁... What's new: Starting today, you'll see an option to set the color profile of your file to Display P3, and (if your monitor supports it!) you'll be able to see 49% more colors in your designs. Hope you enjoy it! 8/

So, we developed polyfills for each. Our CSS polyfill uses a 1px PNG template, modifies bits in the color palette chunk, and regenerates the checksum to create a color solid paint 🟥 The team then ran dark tests to QA the experience 🧪🕵️‍♂️ 7/

BUT, Display P3 was still not supported for 2D canvases & web components styled with CSS. We also had to figure out how to bring Display P3 to every color picker surface (there are A LOT of them in Figma) 6/

...so if the monitor is using P3, our desktop app will also render in P3. In August 2022, @ChromiumDev shipped Display P3 support for WebGL canvases, which made it possible for us to show the editor canvas in P3 on Chrome & Edge browsers, as well as our desktop app 🎉 5/

We started receiving features requests for designing with Display P3 colors in 2017, before any browser supported the standard. As a workaround, our team maintained a @electronjs flag to pass through colors directly to the monitor without color management by Chromium... 4/

Display P3 was tricky to integrate into Figma for a few reasons. Support for color profiles varies by browser and OS. While it's an imperfection for most web apps, for a professional design tool like Figma, this means serious production issues for our customers 🧐 3/

@figma now supports Display P3, a wide-gamut color profile developed by @Apple  Display P3 offers more vibrant colors with richer saturations on modern digital displays. You'll have to take my word for it, since @Twitter  doesn't support P3 yet 2/

Today marks an exciting day in @figma history: we brought 49% more colors to the canvas (!!) 🎨🌈 Sounds intriguing? Let's unravel the engineering magic behind this... 🧵🪡" 1/

We know it’s been too long — emojis have been updated in @figma (~1000 added)! While we were at it, we also improved the rendering, quality, and ease of future updates. Emoji on 🙌

Join @claraujiie, @adispezio, Amanda Yeh and me for office hours next Tuesday @ 9am PT. We'll be talking about some under-the-hood editor magic that made variable fonts happen at @figma and how you can take advantage of them.

Congrats to @mwichary @LinzhiQ & team for shipping VFs 👏 lots of great work & bad puns went into this

above all, proud to have triggered a small transfer of VC 💸 to a non-profit 😌

The provider donated $10K to @EFF in place of a bounty at my request. Customer source code and production secrets from build processes were vulnerable, but no abuse was found after a third-party forensics. https://t.co/xRk1jSTFPn

18 miles but didn’t quite escape from the city