Podcasts about mozilla add

It's dangerous to go alone! Take this: Shownotes Sponsor • Tienda Nube Creá tu tienda online | ↗ Tiendanube ↪︎ Prueba gratuita por 30 días y 25% off en el primer pago. MetaPixel: The YouTube Dance of Madness Supported YouTube File Formats | ↗ YouTube Support Add video thumbnails | ↗ YouTube Support Don't “Accept” image/webp | ↗ Mozilla Add-ons Pocket Casts | ↗ Play Store • ↗ App Store Overcast | ↗ App Store Spoiler Warning → Para saltearse la discución con spoilers de No Time to Die, vayan a 33:55. No Time to Die No Time to Die | ↗ Sitio Oficial • ↗ IMDb • ↗ Wikipedia In Bruges | ↗ Wikipedia • ↗ IMDb The Grand Budapest Hotel | ↗ Wikipedia • ↗ IMDb The Night Manager | ↗ Wikipedia • ↗ IMDb El salto del Aston Martin DBS en Casino Royale | ↗ Esquire Hans Zimmer Takes Over as Composer on Bond Movie | ↗ Variety Pacto Ficcional | ↗ Wikipedia Recomendaciones N → Ginger Root | ↗ YouTube F → AppStories • Obsidian in Depth: The Basics | ↗ MacStories • ↗ Podlink Créditos Recuerden que pueden seguirnos en ↗ Instagram para enterarse de las últimas novedades antes que nadie. Además pueden encontrar al Sr.

In this Hasty Treat, Scott and Wes talk about favicons. Favicons are a bit of mystery and something people don't talk about that often. Sanity - Sponsor Sanity.io is a real-time headless CMS with a fully customizable Content Studio built in React. Get a Sanity powered site up and running in minutes at sanity.io/create. Get an awesome supercharged free developer plan on sanity.io/syntax. LogRocket - Sponsor LogRocket lets you replay what users do on your site, helping you reproduce bugs and fix issues faster. It's an exception tracker, a session re-player and a performance monitor. Get 14 days free at logrocket.com/syntax. Show Notes 03:48 - What are favicons? Requesting favicons by default /favicon.ico 07:38 - Sizing favicons 16x16 is OG - don't do that now You can specify multiple sizes 09:41 - File formats .ico files .png favicons 13:40 - Animated favicons Canvas Base64 11:36 - SVG favicons 17:19 - Dark mode favicons 18:55 - App Coloring Isn't there a new Safari version? Links https://en.wikipedia.org/wiki/Favicon https://caniuse.com/ https://keycode.info/ https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/icons https://fav.farm/ https://deno.land/ https://uses.tech/ Missive Tweet us your tasty treats! Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

Hakuro Matsuda さんをゲストに迎えて、WWDC, iOS 14, Apple Silicon, YouTube Music などについて話しました。 Show Notes WWDC20 App Clips - Apple Developer Google Play Instant Apple adds a dedicated biking feature to Maps in iOS 14 iOS 12 has a game-changing NFC feature that works even if your iPhone battery dies The Talk Show Remote From WWDC 2020 MKBHD: Apple Responds to Your Comments! AirPods updated with automatic switching and a new ‘Spatial Audio’ feature Foundation — Teaser | Apple TV+ ファウンデーション | アイザック アシモフ バーナード嬢曰く。: 5 YouTube for Android TV adopts AV1 video codec in certain devices macOS Big Sur Preview Neumorphism in user interfaces Browser Extensions Apple is bringing Face ID and Touch ID to the web with Safari 14 Why 9:41 AM is always the time displayed on iPhones and iPads Apple announces Mac transition to Apple silicon Explore the new system architecture of Apple Silicon Macs - WWDC 2020 Quality of service Amazon's Arm-based Graviton2 Against AMD and Intel Armベースのスパコン「富岳」TOP500で世界1位獲得 Rebuild: 108: John Bull's Instruction Set (hak) Veteran chip engineer Jim Keller leaves Intel after just two years With YouTube Music, Google is holding my speakers for ransom SRS-HG10 | ソニー AfterShokz Aeropex 骨伝導ワイヤレスヘッドホン 三体Ⅱ　黒暗森林（上）

Ross Kaffenberger is a software engineer at Stitch Fix and has been developing web applications for the past 12 years, mostly in Ruby and JavaScript. Today he and the panel are discussing how to survive Webpack. When many folks first encounter Webpack, they feel confused, overwhelmed, and don’t know how to get it to do what you want it to. In the latest version they tried to introduce some more sane default settings, but it is still a major change in technology.  Ross talks about how his company transitioned Rails 5 to Rails 6 with the new Webpacker. His company chose to take an iterative approach and slowly migrated to Webpacker. His app was very JS heavy with a large number of libraries, many of which were not very Webpack friendly. They chose to separate out the vendor libraries into a separate bundle, that way they could contain each deploy. They still had to add some configuration, especially to make things available on global scope.As they started moving jQuery plugins over, sometimes the functionality would disappear, and Ross talks about how they figured out their mistakes. It was difficult for them to get out of their Sprockets mindset and into the new mindset of Webpack, which requires different techniques. There are also things that Webpack can do to keep you out of that situation Ross gives some strategy advice for someone who is in a position to update from Sprockets to Webpack. It’s important to consider your app size, your comfort level with Webpack, your team dynamic, and your timeframe. Ross recommends the iterative approach that they took, which took longer, but allowed them to learn as they went.  Ross talks about the changes that happened in the switch from Webpack 3 to Webpack 4, and some of the contributions they made. He talks about some of his preferred Webpack configs and plugins. They discuss some of the drawbacks of Webpack, particularly the plethora of plugins that can make it seem daunting.  One of the big gotchas with Webpack is the location of your source code. When you install Webpack for the first time, create a JS folder under App, it will place a ‘application.js’ file in another file called ‘Packs”. The idea of that pack file (application.js file under Packs) is that it’s the entry point for all of the JS that you’re going to add to your Webpack build. But if you add additional files to that Pack folder, Webpacker will instruct Webpack to treat each of those files as a separate entry point in a dependency graph. Make sure that only files that are intended to be the entry points for your Webpack builds are in that packs folder.  It is also important to understand how you’re using global scope inside your JavaScript modules in your build. There’s a way to allow Webpack to inspect each of the files for a certain variable, such as a dollar sign. If he could go back and do it again, Ross would not split his code manually, but instead Embrace the notion that Webpack understands how to do code splitting for you, as long as instruct it to do it the right way. Ultimately, it took Ross’ company 3 rather tedious months to transition to Webpack. It could’ve gone faster if they’d known more about Webpack to begin with. The panel discusses whether it was worth it to switch to Webpack. Transitioning to Webpack has changed their team dynamic and their day to day coding and debugging. One nice feature of Webpack is the source maps that aid in debugging. There are still areas for improvement, but now that it’s set up most folks on the team don’t think about it. Overall, the development experience has improved, and he thinks it was worth it, but it’s not for everybody. Panelists Dave Kimura Andrew Mason Nate Hopkins Charles Max Wood With special guest: Ross Kaffenberger Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Views on Vue Links Webpack Webpacker Sprockets  Knockout.js CKEditor Chosen Webpack Bundle Analyzer Manifest.json Module shimming SplitChunksPlugin Vue Follow DevChatTV on Facebook and Twitter Picks Dave Kimura: Avengers Quinjet Lego set Portable air conditioner Nate Hopkins: MDN JavaScript Reference Brandon Sanderson’s Mistborn series  Charles Max Wood: Restream Twitch OBS Ross Kaffenberger:  Exploring ES6 1 Second Everyday One Sentence Journal Follow Ross on Twitter and Github, and on his blog

Ross Kaffenberger is a software engineer at Stitch Fix and has been developing web applications for the past 12 years, mostly in Ruby and JavaScript. Today he and the panel are discussing how to survive Webpack. When many folks first encounter Webpack, they feel confused, overwhelmed, and don’t know how to get it to do what you want it to. In the latest version they tried to introduce some more sane default settings, but it is still a major change in technology.  Ross talks about how his company transitioned Rails 5 to Rails 6 with the new Webpacker. His company chose to take an iterative approach and slowly migrated to Webpacker. His app was very JS heavy with a large number of libraries, many of which were not very Webpack friendly. They chose to separate out the vendor libraries into a separate bundle, that way they could contain each deploy. They still had to add some configuration, especially to make things available on global scope.As they started moving jQuery plugins over, sometimes the functionality would disappear, and Ross talks about how they figured out their mistakes. It was difficult for them to get out of their Sprockets mindset and into the new mindset of Webpack, which requires different techniques. There are also things that Webpack can do to keep you out of that situation Ross gives some strategy advice for someone who is in a position to update from Sprockets to Webpack. It’s important to consider your app size, your comfort level with Webpack, your team dynamic, and your timeframe. Ross recommends the iterative approach that they took, which took longer, but allowed them to learn as they went.  Ross talks about the changes that happened in the switch from Webpack 3 to Webpack 4, and some of the contributions they made. He talks about some of his preferred Webpack configs and plugins. They discuss some of the drawbacks of Webpack, particularly the plethora of plugins that can make it seem daunting.  One of the big gotchas with Webpack is the location of your source code. When you install Webpack for the first time, create a JS folder under App, it will place a ‘application.js’ file in another file called ‘Packs”. The idea of that pack file (application.js file under Packs) is that it’s the entry point for all of the JS that you’re going to add to your Webpack build. But if you add additional files to that Pack folder, Webpacker will instruct Webpack to treat each of those files as a separate entry point in a dependency graph. Make sure that only files that are intended to be the entry points for your Webpack builds are in that packs folder.  It is also important to understand how you’re using global scope inside your JavaScript modules in your build. There’s a way to allow Webpack to inspect each of the files for a certain variable, such as a dollar sign. If he could go back and do it again, Ross would not split his code manually, but instead Embrace the notion that Webpack understands how to do code splitting for you, as long as instruct it to do it the right way. Ultimately, it took Ross’ company 3 rather tedious months to transition to Webpack. It could’ve gone faster if they’d known more about Webpack to begin with. The panel discusses whether it was worth it to switch to Webpack. Transitioning to Webpack has changed their team dynamic and their day to day coding and debugging. One nice feature of Webpack is the source maps that aid in debugging. There are still areas for improvement, but now that it’s set up most folks on the team don’t think about it. Overall, the development experience has improved, and he thinks it was worth it, but it’s not for everybody. Panelists Dave Kimura Andrew Mason Nate Hopkins Charles Max Wood With special guest: Ross Kaffenberger Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Views on Vue Links Webpack Webpacker Sprockets  Knockout.js CKEditor Chosen Webpack Bundle Analyzer Manifest.json Module shimming SplitChunksPlugin Vue Follow DevChatTV on Facebook and Twitter Picks Dave Kimura: Avengers Quinjet Lego set Portable air conditioner Nate Hopkins: MDN JavaScript Reference Brandon Sanderson’s Mistborn series  Charles Max Wood: Restream Twitch OBS Ross Kaffenberger:  Exploring ES6 1 Second Everyday One Sentence Journal Follow Ross on Twitter and Github, and on his blog

Ross Kaffenberger is a software engineer at Stitch Fix and has been developing web applications for the past 12 years, mostly in Ruby and JavaScript. Today he and the panel are discussing how to survive Webpack. When many folks first encounter Webpack, they feel confused, overwhelmed, and don’t know how to get it to do what you want it to. In the latest version they tried to introduce some more sane default settings, but it is still a major change in technology.  Ross talks about how his company transitioned Rails 5 to Rails 6 with the new Webpacker. His company chose to take an iterative approach and slowly migrated to Webpacker. His app was very JS heavy with a large number of libraries, many of which were not very Webpack friendly. They chose to separate out the vendor libraries into a separate bundle, that way they could contain each deploy. They still had to add some configuration, especially to make things available on global scope.As they started moving jQuery plugins over, sometimes the functionality would disappear, and Ross talks about how they figured out their mistakes. It was difficult for them to get out of their Sprockets mindset and into the new mindset of Webpack, which requires different techniques. There are also things that Webpack can do to keep you out of that situation Ross gives some strategy advice for someone who is in a position to update from Sprockets to Webpack. It’s important to consider your app size, your comfort level with Webpack, your team dynamic, and your timeframe. Ross recommends the iterative approach that they took, which took longer, but allowed them to learn as they went.  Ross talks about the changes that happened in the switch from Webpack 3 to Webpack 4, and some of the contributions they made. He talks about some of his preferred Webpack configs and plugins. They discuss some of the drawbacks of Webpack, particularly the plethora of plugins that can make it seem daunting.  One of the big gotchas with Webpack is the location of your source code. When you install Webpack for the first time, create a JS folder under App, it will place a ‘application.js’ file in another file called ‘Packs”. The idea of that pack file (application.js file under Packs) is that it’s the entry point for all of the JS that you’re going to add to your Webpack build. But if you add additional files to that Pack folder, Webpacker will instruct Webpack to treat each of those files as a separate entry point in a dependency graph. Make sure that only files that are intended to be the entry points for your Webpack builds are in that packs folder.  It is also important to understand how you’re using global scope inside your JavaScript modules in your build. There’s a way to allow Webpack to inspect each of the files for a certain variable, such as a dollar sign. If he could go back and do it again, Ross would not split his code manually, but instead Embrace the notion that Webpack understands how to do code splitting for you, as long as instruct it to do it the right way. Ultimately, it took Ross’ company 3 rather tedious months to transition to Webpack. It could’ve gone faster if they’d known more about Webpack to begin with. The panel discusses whether it was worth it to switch to Webpack. Transitioning to Webpack has changed their team dynamic and their day to day coding and debugging. One nice feature of Webpack is the source maps that aid in debugging. There are still areas for improvement, but now that it’s set up most folks on the team don’t think about it. Overall, the development experience has improved, and he thinks it was worth it, but it’s not for everybody. Panelists Dave Kimura Andrew Mason Nate Hopkins Charles Max Wood With special guest: Ross Kaffenberger Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Views on Vue Links Webpack Webpacker Sprockets  Knockout.js CKEditor Chosen Webpack Bundle Analyzer Manifest.json Module shimming SplitChunksPlugin Vue Follow DevChatTV on Facebook and Twitter Picks Dave Kimura: Avengers Quinjet Lego set Portable air conditioner Nate Hopkins: MDN JavaScript Reference Brandon Sanderson’s Mistborn series  Charles Max Wood: Restream Twitch OBS Ross Kaffenberger:  Exploring ES6 1 Second Everyday One Sentence Journal Follow Ross on Twitter and Github, and on his blog

Firefox Bans Obfuscated Code, Mozilla Add-on Bug Disabling Add-ons for Millions of Users, DOE Confirms Cyber Event Disrupting Power Grids, Citrix Announces Data Breach between October 13 and March 8, German Police Seize Wall Street Market Servers, Hacker selling Windows Zero-days for 3 Years Today's Agenda is as follows: Firefox Bans Obfuscated Code Mozilla Add-on Bug Disabling Add-ons for Millions of Users DOE Confirms Cyber Event Disrupting Power Grids Citrix Announces Data Breach between October 13 and March 8, German Police Seize Wall Street Market Servers German Police Seize Wall Street Market Servers, Hacker selling Windows Zero-days for 3 Years If you would like to add the podcast to your Alexa flash briefings you can do so here.

For our next season of the United States of Anxiety, we’re focusing on power and gender, and we’ve partnered with ProPublica to look at how political advertising targets people of different genders differently on Facebook. Unlike broadcast television ads, which are heavily regulated, we have no idea how individual voters are micro-targeted on Facebook. It’s still the Wild West. Nor do we know about potentially unethical or misleading advertising that may be happening. We do know from the Cambridge Analytica scandal that much of the misinformation spread in 2016 targeted people based on their race and gender. And we know that this is an election in which gender is expected to be a decisive factor. What can you do? Download the ProPublica Ad Tracker Extension - You can download the Facebook Political Ad Collector from the Chrome Web Store or the Mozilla Add-ons Store. NOTE: ProPublica is NOT collecting any private information from you. The plugin simply copies the ads you are seeing in your unique feed. You can read more about how ProPublica is protecting your privacy here. See the ads that other people are seeing - take a look through ProPublica’s database of political ads Send us tips - Have you seen any political ads that appear to target you by your gender? Or target you by your race? Have you seen any political ads that appear to celebrate women? Or any ads that seem misogynistic? Take a screenshot and email us at narrative@wnyc.org to tell us what you’re seeing.  By doing this, you'll be part of groundbreaking research — remember this is the first election cycle since Facebook changed its policies. And you'll also be helping WNYC and ProPublica bring you reporting and analysis about these campaign ads. To get started, visit propublica.org/facebook.

A record number of women are running for office this primary season, which means there's a groundswell of energy around targeting female voters with campaign ads. For our next season of the United States of Anxiety, we’re focusing on power and gender, and we’ve partnered with ProPublica to look at how political advertising targets people of different genders differently on Facebook. Unlike broadcast television ads, which are heavily regulated, we have no idea how individual voters are micro-targeted on Facebook. It’s still the Wild West. Nor do we know about potentially unethical or misleading advertising that may be happening. We do know from the Cambridge Analytica scandal that much of the misinformation spread in 2016 targeted people based on their race and gender. And we know that this is an election in which gender is expected to be a decisive factor. What can you do? Download the ProPublica Ad Tracker Extension - You can download the Facebook Political Ad Collector from the Chrome Web Store or the Mozilla Add-ons Store. NOTE: ProPublica is NOT collecting any private information from you. The plugin simply copies the ads you are seeing in your unique feed. You can read more about how ProPublica is protecting your privacy here. See the ads that other people are seeing - take a look through ProPublica’s database of political ads Send us tips - Have you seen any political ads that appear to target you by your gender? Or target you by your race? Have you seen any political ads that appear to celebrate women? Or any ads that seem misogynistic? Take a screenshot and email us at narrative@wnyc.org to tell us what you’re seeing.  By doing this, you'll be part of groundbreaking research — remember this is the first election cycle since Facebook changed its policies. And you'll also be helping WNYC and ProPublica bring you reporting and analysis about these campaign ads. To get started, visit propublica.org/facebook.  

関連リンク React v15.5.0 - React Blog GitHub - reactjs/react-codemod: React codemod scripts GitHub - facebook/jscodeshift: A JavaScript codemod toolkit. ESLint v4.0.0 の変更点まとめ - Qiita How we built Twitter Lite | Twitter Blogs Twitter Lite and High Performance React Progressive Web Apps at Scale ng-conf 2017 1日目 Keynoteメモ | はじめに | Reset CSSフレンズ Scala入門としてCLIツールを作り、Scala.js, React, ScalaCSSでサイトを作った - マルシテイア Announcing Scala.js 0.6.15 - Scala.js WEBASSEMBLY USUI BOOK GitHub - photopea/UTIF.js: Fast and advanced TIFF decoder Add-on Compatibility for Firefox 54 | Mozilla Add-ons Blog Microsoft SVG Logo Introduction · react-indepth React VR | A framework for building VR apps using React