RE: https://mastodon.social/@jagsworkshop/116218870935109636

I was unable to attend (tickets sold out in fifteen minutes!), but I did watch the livestream. It’s now up on CHM’s YouTube channel. A must-watch for anyone interested in the history of Apple.

(I was especially thrilled to see @Cdespinosa up on stage.)

RE: https://mastodon.social/@jagsworkshop/116021142819968656

Daniel Fienberg, The Hollywood Reporter: “it proves conclusively that what worked in the ’70s and a bit in the ’90s can absolutely still work today.”

I hope it worked well enough for Disney, because we could all use some zany, madcap relief. To quote my friend @timtr: “Need this every week. Forever.”

RE: https://front-end.social/@jensimmons/115708071675176381

Safari 26.2 brings some long-awaited updates for Safari Web Extensions.

1. If you’re still shipping a Safari App Extension on Mac, during an update you can replace it with a Safari Web Extensions and KEEP the website access permissions that have already been granted. Updating to a Safari Web Extension is seamless for your users and opens up a ton of new APIs alongside the ability to ship one extension across macOS, iOS, iPadOS, and visionOS.

2. From the native app shipped with your extension, you can check if the extension has been turned on. This lets you conditionally change the contents or functionality of your app.

3. On iOS, iPadOS, and visionOS, you can now deep link your users to Safari Extension Settings. If you’re shipping one extension, you can deep link directly to it, if you ship multiple extensions, you can choose to highlight them all in Settings.

Read about all of these changes and more on WebKit.org and reach out with any feedback.