Podcasts about Bluetooth Low Energy

This week on the Mr. Beacon Podcast, Thomas Roedding, CEO of Narravero, unpacks the rise of Digital Product Passports (DPPs). We explore how DPPs drive compliance, sustainability, and customer engagement under EU regulations. Roedding shares Narravero's hands-on work with over 200 clients and explains why DPPs are more than a legal necessity—they're a powerful business tool. Learn how to let your products “talk” in a smarter, connected future.Thomas' Top 3 Favorite Songs:“The River” by Bruce Springsteen: https://www.youtube.com/watch?v=y7BUXRsTbvI “Bochum” by Herbert Grönemeyer: https://www.youtube.com/watch?v=OvauzdH0fHY “River Flows In You” by YIRUMA: https://www.youtube.com/watch?v=92IlKBhKbWM Mister Beacon is hosted by Steve Statler, CEO of AmbAI Inc. — creators of AmbAI, the AI agent that connects people to products and the brands behind them. AmbAI also advises leading brands on Ambient Intelligence strategy.Our sponsor is Identiv https://www.identiv.com, who's IoT solutions create digital identities for physical objects, enhancing global connectivity for businesses, people, and the planet. We are also sponsored by Blecon http://www.blecon.net. Blecon enables physical products to communicate with cloud applications using Bluetooth Low Energy. Hosted on Acast. See acast.com/privacy for more information.

C'est un petit pas pour Apple, mais un grand bond pour l'interopérabilité. Avec iOS 26, la firme de Cupertino amorce un virage discret mais symbolique : le protocole AirDrop, jusqu'ici jalousement gardé dans l'écosystème Apple, s'ouvre enfin à des applications tierces. En clair, les développeurs auront bientôt accès au même canal de communication sans fil qu'AirDrop, via une nouvelle interface de programmation baptisée NearbyFileShare. Le principe est simple : grâce au Wi-Fi Direct et au Bluetooth Low Energy, les applis tierces pourront détecter des appareils à proximité, s'annoncer et transférer des fichiers — le tout chiffré, de manière native, sans bidouille ni QR code. On imagine déjà des applis de messagerie ou de cloud proposer un bouton « Partager à proximité » directement intégré à l'interface iOS.Mais Apple ne lâche pas tout. L'entreprise impose un cadre strict : transferts limités à 10 mètres, respect de la sandbox, chiffrement de bout en bout… et surtout, droit de retrait pour les applications qui détourneraient l'outil à des fins de diffusion massive. Côté utilisateur, AirDrop restera activé par défaut, mais un menu permettra de choisir son service préféré, comme on le fait déjà avec le navigateur ou le client mail. Pourquoi ce geste d'ouverture maintenant ? Il faut chercher la réponse à Bruxelles. Le Digital Markets Act pousse les géants du numérique à ouvrir leurs services clés, et le partage local faisait partie des derniers bastions verrouillés d'iOS. Plutôt que d'attendre une sanction, Apple devance l'injonction, comme elle l'a fait en autorisant les boutiques alternatives ou en abaissant ses commissions sur les paiements in-app.Alors, peut-on imaginer bientôt un partage de fichiers fluide entre iPhone, Android et Windows ? Pas si vite. Pour l'instant, rien n'indique que NearbyFileShare sera compatible hors de l'écosystème Apple. Mais en laissant des éditeurs comme Google ou Microsoft s'y frotter, la firme garde la main tout en contournant les accusations d'entrave à la concurrence. Un numéro d'équilibriste bien maîtrisé : Apple cède un peu de terrain sans abandonner ses règles. Et si l'Europe veut aller plus loin, il faudra sortir les grands moyens. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

In this episode of the Mr. Beacon Podcast, Kirsten Newquist, CEO of Identiv, shares her journey from Avery Dennison to leading one of the most innovative companies in IoT. Kirsten discusses Identiv's unique engineering, new growth strategy, and their impact on healthcare and smart device solutions. She also highlights her values-driven leadership approach and offers personal insights on building resilient, purpose-led teams in a fast-evolving, connected world.Kirsten's Top 3 Favorite Songs:“Don't Worry Be Happy” by Bobby McFerrin: https://www.youtube.com/watch?v=d-diB65scQU“Lean On Me” by Bill Withers: https://www.youtube.com/watch?v=fOZ-MySzAac“Rise Up” by Andra Day: https://www.youtube.com/watch?v=LDffmI0ncfoMister Beacon is hosted by Steve Statler, CEO of AmbAI Inc. — creators of AmbAI, the AI agent that connects people to products and the brands behind them. AmbAI also advises leading brands on Ambient Intelligence strategy.Our sponsor is Blecon http://www.blecon.net. Blecon enables physical products to communicate with cloud applications using Bluetooth Low Energy. Hosted on Acast. See acast.com/privacy for more information.

Connor Rigby joins the Elixir Wizards to talk about Blue Heron BLE (Bluetooth Low Energy) support for Elixir apps. Blue Heron implements the BLE specs in pure Elixir, leveraging binary pattern matching and concurrent message processing to handle Bluetooth protocols. Unlike most solutions that require C ports or NIFs, Blue Heron runs entirely in user space, so it works seamlessly in both Nerves-based embedded projects and (eventually) desktop Elixir applications. We discuss how Nerves development differs from building Phoenix apps. Connor shares challenges he's experienced with hardware compatibility, where some chips only partially implement the spec, and he discusses the surprisingly deep (but sometimes incomplete) world of BLE device profiles. His tip for anyone entering the BLE space: read the official spec instead of trusting secondhand blog posts. Tools like Nerves LiveBook give you hands-on examples, so you can get a BLE prototype running on a Raspberry Pi and your phone in no time. Key topics discussed in this episode: Blue Heron origins and “bird” naming convention BLE vs. Bluetooth Classic: core differences Pure Elixir implementation—no C dependencies Binary pattern matching for packet parsing Hardware transport options: UART, SPI, USB, SDIO GenServer patterns in Nerves vs. Phoenix Linux requirement and power-consumption trade-offs GATT (Generic Attribute Table) implementation patterns SQLite integration for Nerves apps Hardware chip quirks and spec compliance Manufacturer-specific commands and workarounds BLE device profiles and spec gaps Security Management Profile (SMP) for encryption Device connection and pairing workflows Web vs. embedded development differences Where to get started: hardware recommendations and docs Links mentioned: https://github.com/ConnorRigby/ https://github.com/blue-heron/ https://nerves-project.org/ BLE (Bluetooth Low Energy) https://en.wikipedia.org/wiki/BluetoothLowEnergy https://developer.apple.com/ibeacon/ https://learnyousomeerlang.com/building-otp-applications Linux https://www.linux.org/ HCI (Host Controller Interface) https://en.wikipedia.org/wiki/Hostcontrollerinterface Circuits UART Library https://hexdocs.pm/circuitsuart/readme.html SPI (Serial Peripheral Interface) https://github.com/elixir-circuits/circuitsspi SDIO (Secure Digital Input Output https://en.wikipedia.org/wiki/SDIO Raspberry Pi https://www.raspberrypi.com/ Coral SoM Dev Board https://coral.ai/products/dev-board/ BeagleBone Single-Board Linux Computer https://www.beagleboard.org/boards/beaglebone-black https://www.bluetooth.com/bluetooth-resources/intro-to-bluetooth-gap-gatt/ Genservers https://hexdocs.pm/elixir/1.12/GenServer.html https://hexdocs.pm/ecto/Ecto.html https://github.com/elixir-sqlite/ectosqlite3 https://github.com/nerves-livebook/nerveslivebook Special Guest: Connor Rigby.

The Storm Skiing Journal and Podcast is a reader-supported publication (and my full-time job). To receive new posts and to support independent ski journalism, please consider becoming a free or paid subscriber.WhoJoe Hession, CEO of Snow Partners, which owns Mountain Creek, Big Snow American Dream, SnowCloud, and Terrain Based LearningRecorded onMay 2, 2025About Snow PartnersSnow Partners owns and operates Mountain Creek, New Jersey and Big Snow American Dream, the nation's only indoor ski center. The company also developed SnowCloud resort management software and has rolled out its Terrain Based Learning system at more than 80 ski areas worldwide. They do some other things that I don't really understand (there's a reason that I write about skiing and not particle physics), that you can read about on their website.About Mountain CreekLocated in: Vernon Township, New JerseyClosest neighboring public ski areas: Mount Peter (:24); Big Snow American Dream (:50); Campgaw (:51) Pass affiliations: Snow Triple Play, up to two anytime daysBase elevation: 440 feetSummit elevation: 1,480 feetVertical drop: 1,040 feetSkiable Acres: 167Average annual snowfall: 65 inchesTrail count: 46Lift count: 9 (1 Cabriolet, 2 high-speed quads, 2 fixed-grip quads, 1 triple, 1 double, 2 carpets – view Lift Blog's inventory of Mountain Creek's lift fleet)About Big Snow American DreamLocated in: East Rutherford, New JerseyClosest neighboring public ski areas: Campgaw (:35); Mountain Creek (:50); Mount Peter (:50)Pass affiliations: Snow Triple Play, up to two anytime daysVertical drop: 160 feet Skiable Acres: 4Trail count: 4 (2 green, 1 blue, 1 black)Lift count: 4 (1 quad, 1 poma, 2 carpets - view Lift Blog's of inventory of Big Snow American Dream's lift fleet)Why I interviewed himI read this earlier today:The internet is full of smart people writing beautiful prose about how bad everything is, how it all sucks, how it's embarrassing to like anything, how anything that appears good is, in fact, secretly bad. I find this confusing and tragic, like watching Olympic high-jumpers catapult themselves into a pit of tarantulas.That blurb was one of 28 “slightly rude notes on writing” offered in Adam Mastroianni's Experimental History newsletter. And I thought, “Man this dude must follow #SkiTwitter.” Or Instabook. Of Flexpost. Or whatever. Because online ski content, both short- and long-form, is, while occasionally joyous and evocative, disproportionately geared toward the skiing-is-fucked-and-this-is-why worldview. The passes suck. The traffic sucks. The skiers suck. The prices suck. The parking sucks. The Duopoly sucks. Everyone's a Jerry, chewing up my pow line with their GoPro selfie sticks hoisted high and their Ikon Passes dangling from their zippers. Skiing is corporate and soulless and tourist obsessed and doomed anyway because of climate change. Don't tell me you're having a good time doing this very fun thing. People like you are the reason skiing's soul now shops at Wal-Mart. Go back to Texas and drink a big jug of oil, you Jerry!It's all so… f*****g dumb. U.S. skiing just wrapped its second-best season of attendance. The big passes, while imperfect, are mostly a force for good, supercharging on-hill infrastructure investment, spreading skiers across geographies, stabilizing a once-storm-dependent industry, and lowering the per-day price of skiing for the most avid among us to 1940s levels. Snowmaking has proven an effective bulwark against shifting weather patterns. Lift-served skiing is not a dying pastime, financially or spiritually or ecologically. Yes, modern skiing has problems: expensive food (pack a lunch); mountain-town housing shortages (stop NIMBY-ing everything); traffic (yay car culture); peak-day crowds (don't go then); exploding insurance, labor, utilities, and infrastructure costs (I have no answers). But in most respects, this is a healthy, thriving, constantly evolving industry, and a more competitive one than the Duopoly Bros would admit.Snow Partners proves this. Because what the hell is Snow Partners? It's some company sewn together by a dude who used to park cars at Mountain Creek. Ten years ago this wasn't a thing, and now it's this wacky little conglomerate that owns a bespoke resort tech platform and North America's only snowdome and the impossible, ridiculous Mountain Creek. And they're going to build a bunch more snowdomes that stamp new skiers out by the millions and maybe – I don't know but maybe – become the most important company in the history of lift-served skiing in the process.Could such an outfit possibly have materialized were the industry so corrupted as the Brobot Pundit Bros declare it? Vail is big. Alterra is big. But the two companies combined control just 53 of America's 501 active ski areas. Big ski areas, yes. Big shadows. But neither created: Indy Pass, Power Pass, Woodward Parks, Terrain Based Learning, Mountain Collective, RFID, free skiing for kids, California Mountain Resort Company, or $99 season passes. Neither saved Holiday Mountain or Hatley Pointe or Norway Mountain or Timberline West Virigina from the scrapheap, or transformed a failing Black Mountain into a co-op. Neither has proven they can successfully run a ski area in Indiana (sorry Vail #SickBurn #SellPaoliPeaks #Please).Skiing, at this moment, is a glorious mix of ideas and energy. I realize it makes me uncool to think so, but I signed off on those aspirations the moment I drove the minivan off the Chrysler lot (topped it off with a roofbox, too, Pimp). Anyhow, the entire point of this newsletter is to track down the people propelling change in a sport that most likely predates the written word and ask them why they're doing these novel things to make an already cool and awesome thing even more cool and awesome. And no one, right now, is doing more cool and awesome things in skiing than Snow Partners.**That's not exactly true. Mountain Capital Partners, Alterra, Ikon Pass, Deer Valley, Entabeni Systems, Jon Schaefer, the Perfect Clan, Boyne Resorts, Big Sky, Mt. Bohemia, Powdr, Vail Resorts, Midwest Family Ski Resorts, and a whole bunch more entities/individuals/coalitions are also contributing massively to skiing's rapid-fire rewiring in the maw of the robot takeover digital industrial revolution. But, hey, when you're in the midst of transforming an entire snow-based industry from a headquarters in freaking New Jersey, you get a hyperbolic bump in the file card description.What we talked aboutThe Snow Triple Play; potential partners; “there's this massive piece of the market that's like ‘I don't even understand what you're talking about'” with big day ticket prices and low-priced season passes; why Mountain Creek sells its Triple Play all season long and why the Snow Triple Play won't work that way (at least at first); M.A.X. Pass and why Mountain Creek declined to join successor passes; an argument for Vail, Alterra and other large ski companies to participate on the Snow Triple Play; comparing skiing to hotels, airlines, and Disney World; “the next five years are going to be the most interesting and disruptive time in the ski industry because of technology”; “we don't compete with anybody”; Liftopia's potential, errors, failure, and legacy; skiing on Groupon; considering Breckenridge as an independent ski area; what a “premium” ski area on the Snow Triple Play would be; why megapasses are “selling people a product that will never be used the way it's sold to them”; why people in NYC feel like going to Mountain Creek, an hour over the George Washington Bridge, is “going to Alaska”; why Snow Triple Play will “never” add a fourth day; sticker shock for Big Snow newbs who emerge from the Dome wanting more; SnowCloud and the tech and the guest journey from parking lot to lifts; why Mountain Creek stopped mailing season passes; Bluetooth Low Energy “is certainly the future of passes”; “100 percent we're getting more Big Snows” – but let's justify the $175 million investment first; Big Snow has a “terrible” design; “I don't see why every city shouldn't have a Big Snow” and which markets Snow Partners is talking to; why Mountain Creek didn't get the mega-lift Hession teased on this pod three years ago and when we could see one; “I really believe that the Vernon base of Mountain Creek needs an updated chair”; the impact of automated snowmaking at Mountain Creek; and a huge residential project incoming at Mountain Creek.What I got wrong* I said that Hession wasn't involved in Mountain Creek in the M.A.X. Pass era, but he was an Intrawest employee at the time, and was Mountain Creek's GM until 2012.* I hedged on whether Boyne's Explorer multi-day pass started at two or three days. Skiers can purchase the pass in three- to six-day increments.Why now was a good time for this interviewOkay, so I'll admit that when Snow Partners summarized the Snow Triple Play for me, I wasn't like “Holy crap, three days (total) at up to three different ski areas on a single ski pass? Do you think they have room for another head on Mount Rushmore?” This multi-day pass is a straightforward product that builds off a smart idea (the Mountain Creek Triple Play), that has been a smash hit at the Jersey Snow Jungle since at least 2008. But Snow Triple Play doesn't rank alongside Epic, Ikon, Indy, or Mountain Collective as a seasonlong basher. This is another frequency product in a market already flush with them.So why did I dedicate an entire podcast and two articles (so far) to dissecting this product, which Hession makes pretty clear has no ambitions to grow into some Indy/Ikon/Epic competitor? Because it is the first product to tie Big Snow to the wider ski world. And Big Snow only works if it is step one and there is an obvious step two. Right now, that step two is hard, even in a region ripe with ski areas. The logistics are confounding, the one-off cost hard to justify. Lift tickets, gear rentals, getting your ass to the bump and back, food, maybe a lesson. The Snow Triple Play doesn't solve all of these problems, but it does narrow an impossible choice down to a manageable one by presenting skiers with a go-here-next menu. If Snow Partners can build a compelling (or at least logical) Northeast network and then scale it across the country as the company opens more Big Snows in more cities, then this simple pass could evolve into an effective toolkit for building new skiers.OK, so why not just join Indy or Mountain Collective, or forge some sort of newb-to-novice agreement with Epic or Ikon? That would give Snow Partners the stepladder, without the administrative hassle of owning a ski pass. But that brings us to another roadblock in Ski Revolution 2025: no one wants to share partners. So Hession is trying to flip the narrative. Rather than locking Big Snow into one confederacy or the other, he wants the warring armies to lash their fleets along Snow Partners Pier. Big Snow is just the bullet factory, or the gas station, or the cornfield – the thing that all the armies need but can't supply themselves. You want new skiers? We got ‘em. They're ready. They just need a map to your doorstep. And we're happy to draw you one.Podcast NotesOn the Snow Triple PlayThe basics: three total days, max of two used at any one partner ski area, no blackouts at Big Snow or Mountain Creek, possible blackouts at partner resorts, which are TBD.The pass, which won't be on sale until Labor Day, is fully summarized here:And I speculate on potential partners here:On the M.A.X. PassFor its short, barely noted existence, the M.A.X. Pass was kind of an amazing hack, granting skiers five days each at an impressive blend of regional and destination ski areas:Much of this roster migrated over to Ikon, but in taking their pass' name too literally, the Alterra folks left off some really compelling regional ski areas that could have established a hub-and-spoke network out of the gate. Lutsen and Granite Peak owner Charles Skinner told me on the podcast a few years back that Ikon never offered his ski areas membership (they joined Indy in 2020), cutting out two of the Midwest's best mountains. The omissions of Mountain Creek, Wachusett, and the New York trio of Belleayre, Whiteface, and Gore ceded huge swaths of the dense and monied Northeast to competitors who saw value in smaller, high-end operations that are day-trip magnets for city folks who also want that week at Deer Valley (no other pass signed any of these mountains, but Vail and Indy both assembled better networks of day-drivers and destinations).On my 2022 interview with HessionOn LiftopiaLiftopia's website is still live, but I'm not sure how many ski areas participate in this Expedia-for-lift-tickets. Six years ago, I thought Liftopia was the next bargain evolution of lift-served skiing. I even hosted founder Evan Reece on one of my first 10 podcasts. The whole thing fell apart when Covid hit. An overview here:On various other day-pass productsI covered this in my initial article, but here's how the Snow Triple Play stacks up against other three-day multi-resort products:On Mountain Creek not mailing passesI don't know anything about tech, but I know, from a skier's point of view, when something works well and when it doesn't. Snow Cloud's tech is incredible in at least one customer-facing respect: when you show up at a ski area, a rep standing in a conspicuous place is waiting with an iPhone, with which they scan a QR code on your phone, and presto-magico: they hand you your ski pass. No lines or waiting. One sentimental casualty of this on-site efficiency was the mailed ski pass, an autumn token of coming winter to be plucked gingerly from the mailbox. And this is fine and makes sense, in the same way that tearing down chairlifts constructed of brontosaurus bones and mastodon hides makes sense, but I must admit that I miss these annual mailings in the same way that I miss paper event tickets and ski magazines. My favorite ski mailing ever, in fact, was not Ikon's glossy fold-out complete with a 1,000-piece 3D jigsaw puzzle of the Wild Blue Gondola and name-a-snowflake-after-your-dog kit, but this simple pamphlet dropped into the envelope with my 2018-19 Mountain Creek season pass:Just f*****g beautiful, Man. That hung on my office wall for years. On the CabrioletThis is just such a wackadoodle ski lift:Onetime Mountain Creek owner Intrawest built similar lifts at Winter Park and Tremblant, but as transit lifts from the parking lot. This one at Mountain Creek is the only one that I'm aware of that's used as an open-air gondola. Get full access to The Storm Skiing Journal and Podcast at www.stormskiing.com/subscribe

What does it really take to go from writing code to running a company in the fast-moving world of IoT? What happens when a seasoned embedded engineer decides to build a company from scratch? In this episode of The IoT Podcast Show, host Tom White sits down with Bartek Kling, CEO and founder of NeedCode, a company specialising in embedded software services for connected devices. Bartek shares his journey from being a hands-on embedded engineer in the automotive sector to launching and scaling his own successful tech startup. He opens up about the reality of stepping into a leadership role, the unexpected importance of sales and marketing, the art of building long-term client relationships and how NeedCode has carved out a space in a competitive market by focusing on Bluetooth Low Energy and full-cycle product development. Whether you're building the next big IoT product or just want a behind-the-scenes look at what it takes to lead in this space, this episode delivers real insights, lessons learned, and a forward-looking view of the industry. Chapters... 00:00 Introduction to Bartek Kling and needCode 03:43 Bartek's Journey from Engineer to CEO 09:19 Transitioning from Freelancing to Founding NeedCode 12:24 Challenges of Being a Founder and CEO 14:39 Differentiating NeedCode in the Market 16:36 Plans for Scaling NeedCode 19:09 Capabilities and Offerings of NeedCode 23:35 Common Customer Pain Points 26:44 Building a Talent Network for Growth 30:03 Future Trends in IoT 34:24 Security and Privacy in IoT Devices 37:09 Conclusion and Where to Find NeedCode The episode is live on all major listening platforms now! Listen here: https://linktr.ee/theiotpodcast Connect with our guest… https://www.linkedin.com/in/bartek-kling/ About needCode needCode is a European IoT development company that specialises in creating smart product solutions, embedded software, and AI-powered IoT systems. They help businesses design, secure, and optimise connected products while offering strategic support and staff augmentation to bring innovative ideas to market. Find out more: https://needcode.io/ SUBSCRIBE TO THE IOT PODCAST ON YOUR FAVOURITE LISTENING PLATFORM: https://linktr.ee/theiotpodcast Sign Up for exclusive email updates: https://theiotpodcast.com/get-exclusive-access/ Contact us to become a guest/partner: https://theiotpodcast.com/contact/ Connect with host Tom White: / tom5values

In the first Control Amplified podcast of 2025, wireless technology expert Ian Verhappen joins Len Vermillion for a discussion on the past, present and future of wireless technology for industrial operations. Among their topics are the fast advances and usage of wireless in industrial plants, why Wi-Fi advancement enables more efficient operations, the growing influence of Bluetooth Low Energy on the plant floor, and the need for cybersecurity to advance in lock step with these technologies. In addition, they look at the process for adopting new technologies in industry and why software will be the focus of development over the next decade.

This week's EYE ON NPI is another great step forward in Bluetooth Low Energy development, it's Nordic's new nRF54 series (https://www.digikey.com/en/product-highlight/n/nordic-semi/nrf54l15-multiprotocol-soc) and nRF54L15 Wireless SoC Development Kit (https://www.digikey.com/en/product-highlight/n/nordic-semi/nrf54l15-wireless-soc-development-kit). This is the heir-apparent to the popular nRF52840 (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF52840-CKAA-R/15929796) series chip which we know and love so much. The nRF54 series comes in L and H variants, for 'low' and 'high' power, but even the L series is a step up, with Cortex M33 running at 128MHz, and up to 1.5MB ReRAM (https://en.wikipedia.org/wiki/Resistive_random-access_memory) / 256KB SRAM. The H series is a whole new ball-game with dual M33 running at 320MHz, 2MB of ReRAM and 1MB of SRAM plus upgraded peripherals. Wow, the nRF series has come such a long way from the baby-steps of the SPI-peripheral nRF8001 (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF8001-R2Q32-T/4626390) to the early ARM Cortex M0 plus BLE combo chip, the nRF51 (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF51822-QFAB-R7/4626396). We still use that nRF51 in many of our Bluetooth LE boards like the Feather 32u4 and M0 (https://www.digikey.com/en/products/detail/adafruit-industries-llc/2995/5823444), also as a SPI-peripheral-to-BLE converter. The next big upgrade was the nRF52832 (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF52832-QFAB-R/6051565) which bumped the processor from an M0 to an M4, but didn't do a huge bump to the Flash or SRAM compared the nRF51. The big leap after that was the nRF52840 which is still an amazing chip: USB peripheral means you can use this chip as the main processor, and it can do all your processing, user interface, sensor reading and wireless communication with only a few passives to support it. There was an nRF5340 released about two years ago (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF5340-CLAA-R/14323741) but much like Windows releases, we tend to skip every other chip. We happened to check digikey.com/new yesterday and saw the nRF54L (https://www.digikey.com/short/zf8pz0cr) series pop up, which is exciting as it was pre-announced about a year ago (https://www.youtube.com/watch?v=XG8bRNaNHrg) and is now shipping to customers! The nRF54L (https://www.digikey.com/short/zf8pz0cr) comes in three variants, which is not surprising because we've seen earlier chips come in 'lite' versions that cut pricing by having less flash or RAM. All variants have a 128MHz Cortex M33 with a RISC-V co-processor, and a BLE stack. One interesting thing we noted, is that instead of flash memory, which is big and expensive and hard to do with modern fab processes, the nRF54 uses ReRAM (https://en.wikipedia.org/wiki/Resistive_random-access_memory) which is non-volatile and uses memristor technology, which is pretty cool! The nRF54 series supports BLE 6, one new capability is channel sounding (https://en.wikipedia.org/wiki/Channel_sounding) which will improve the ability of phones to locate 'find my' tags that have become such a popular usage for the nRF chipset. Traditionally, the nRF52 chips in these tags use RSSI to measure approximate distance. There's been some improvements on the technology such as Angle-of-Attack that was introduced in BLE 5.1 (https://www.youtube.com/watch?v=EosGQtGioiY) but now with a broad-sprectrum burst it's looking like some of the lessons from UWB (https://blog.adafruit.com/2024/03/15/sera-nx040-ultra-wide-band-and-bluetooth-combo-module-eyeonnpi-digikey-digikey-lairdconnect-adafruit/) are being integrated to the BLE specification to improve item location. The nRF54L series is launching with the L15 variant (https://www.digikey.com/short/rd9fr19f), that's the one with the most memory, so it's a good start: once you have your design settled you can transition to the smallest chip you can get away with. They're coming into stock shortly so sign up at DigiKey to get notified when the package you're looking for arrives. While you wait, you can order up one of the nRF54L15-DK (https://www.digikey.com/short/qvhqv85q) dev kits, which are only $39 and in stock right now for immediate shipment. Order today and you'll get everything you need to start developing the nRF54 (https://www.nordicsemi.com/Products/Development-hardware/nRF54L15-DK) - a built in debugger, power management chip, broken out GPIO, user buttons and LEDs. While you wait for your dev kit to arrive, you can start thinking about the nRF54H series (https://www.nordicsemi.com/Products/nRF54H20) which is the high-end chip with dual M33 running at 320 MHz, 1 MB of SRAM, 2MB of ReRAM , high speed USB and I3C support (https://www.youtube.com/watch?v=hC4zkvdVag4)!

Recorded October 11, 2024 (Yes, I let AI write all this stuff - cjd) We dive into the world of assistive technologies, AI-generated transcripts, and the quirks of Bluetooth systems. Today's discussion zeroes in on the upcoming digital accessibility deadlines, the challenges of compliance, and the importance of starting somewhere, even when the task seems daunting. We also explore the exciting potential of Bluetooth Low Energy audio systems and how they can revolutionize assistive listening in educational environments. Finally, we discuss the peculiarities of AI transcription services. Are they ready for prime time? Spoiler alert: not quite yet. News article: https://www.edsurge.com/news/2024-07-19-are-schools-and-edtech-companies-ready-for-the-digital-accessibility-deadline   Connect with Mikey Shaffer: https://www.linkedin.com/in/mikeyshaffer/ Bluetooth SIG Auracast: https://www.bluetooth.com/auracast/ Ampetronic Auracast: https://www.ampetronic.com/auracast-broadcast-overview/ Listen Technologies monthly webinar on ADA: https://www.listentech.com/training/ Listen Technologies Auri product line: https://www.listentech.com/auri/   AI-suggested alternate show titles: Bluetooth Bonanza The Accessibility Adventure AI Transcription Terrors Assistive Listening Revolution Digital Deadline Drama The Future is Bluetooth Transcription Trials and Tribulations The Great Accessibility Debate Tech Tangles and Triumphs AV Adventures in Accessibility   Better alternative show titles: The Dante for ALS Talk like someone from Kentucky I love not taking notes A bunch of Furbies hanging out   We stream live every Friday, and you can listen to everything we record over at AVSuperFriends.com   ▀▄▀▄▀ CONTACT LINKS ▀▄▀▄▀ ► Website: https://www.avsuperfriends.com ► Twitter: https://twitter.com/avsuperfriends ► LinkedIn: https://www.linkedin.com/company/avsuperfriends ► YouTube: https://www.youtube.com/@avsuperfriends ► Email: mailbag@avsuperfriends.com ► RSS: https://avsuperfriends.libsyn.com/rss   Individual Twitter links: ► Chris Dechter: @cdechter ► Jamie Rinehart: @avsfjamie ► Marc Cholewczynski: @avdiplomat ► Larry Darling: @lsdarling1 ► Justin Rexing: @justinrexing   Donate to AVSF: https://www.avsuperfriends.com/support

In this episode of the IoT For All Podcast, Simon Ford, CEO of Blecon, joins Ryan Chacon to discuss using Bluetooth Low Energy for IoT connectivity. The conversation covers the advantages and challenges of Bluetooth Low Energy, the role of BLE in edge AI, energy scavenging, and other IoT trends, the pragmatic deployment of IoT solutions, and insights into the future of BLE and how it aligns with enterprise requirements. Simon Ford is the founder and CEO of Blecon, a company enabling low-cost cloud connectivity for engineering diagnostics, product analytics, and sensor data using Bluetooth Low Energy. Simon has over 20 years of industry experience in microelectronics, mobile, and IoT, with a strong focus on providing technology to developers. He founded ARM's embed OS to help launch ARM Cortex-M to market alongside other developer technologies such as CMSIS-DAP, DAPLink, and pyOCD, and was technical lead for the ARMv7/NEON architecture used to launch the smartphone revolution. Blecon enables physical products to communicate with cloud applications using Bluetooth Low Energy. Founded in 2021 and headquartered in the UK, Blecon combines the inherent benefits of BLE with the deployment model of WiFi and the network model of cellular to achieve low-cost and low-power IoT connectivity. With its flexible architecture and ease of integration, Blecon democratizes access to Bluetooth Low Energy IoT connectivity. Discover more about Bluetooth and IoT at https://www.iotforall.com More about Blecon: https://www.blecon.net Connect with Simon: https://www.linkedin.com/in/simonford/ (00:00) Intro (00:10) Simon Ford and Blecon (00:33) What is Bluetooth Low Energy? (03:19) Bluetooth Low Energy use cases (07:37) Challenges of Bluetooth Low Energy (10:33) How does BLE relate to other IoT trends? (13:58) Future developments in Bluetooth and IoT (16:33) Learn more and follow up Subscribe on YouTube: https://bit.ly/2NlcEwm​ Join Our Newsletter: https://www.iotforall.com/iot-newsletter Follow Us on Social: https://linktr.ee/iot4all Check out the IoT For All Media Network: https://www.iotforall.com/podcast-overview

This week's EYE ON NPI is teamwork makin' the dream work - a collaboration between our favorite module makers Raytac (https://www.digikey.com/en/supplier-centers/raytac) and our favorite Bluetooth Low Energy designers, Nordic Semiconductor (https://www.digikey.com/en/supplier-centers/nordic-semiconductor). Together they've created what we think is the best nRF52840 module, the Raytac MDBT50Q-1MV2 (https://www.digikey.com/short/t8hvw1bt). Historically you've had to pick this up direct from Raytac, but now it's stocked by DigiKey which is excellent news for anyone who wants to integrate the powerful nRF52840 with little fuss. The Nordic Semiconductor nRF52840 (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF52840-QIAA-R/7725407) is not a new chip, we've been selling the Feather nRF52840 (https://www.digikey.com/en/products/detail/adafruit-industries-llc/4062/9843410) since 2019 and the chip itself was announced in mid 2017 (https://www.nordicsemi.com/Nordic-news/2017/05/Nordic-Semiconductor-introduces-latest-nRF52-Series-SoC). It builds on the popular nRF52832 (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF52832-QFAB-R/6051565), a chip with an Arm Cortex M4-F / 512K Flash / 64K SRAM, but with a ton more memory: the '840 has 1MB Flash and 256K SRAM. It also comes with native USB device support, which is new to the nRF series but makes product design easier because DFU and computer-interfacing doesn't require a second chip. The only challenge is that the nRF52840 itself is in a funky QFN package with pads underneath, and multiple rows, which requires either very fine traces, 4-layer boards, plugged vias, or a combination, in order to get to the 'inner' traces. Also, you have to get your antenna tuning right - even though the nRF is very forgiving, it's still extra effort! That's why at Adafruit we have been using Raytac's MDBT50Q-1MV2 Module (https://www.digikey.com/short/t8hvw1bt) for years, in our Feather nRF52840 (https://www.digikey.com/en/products/detail/adafruit-industries-llc/4062/9843410), ItsyBitsy nRF52840 (https://www.digikey.com/en/products/detail/adafruit-industries-llc/4481/11497502) and CLUE board (https://www.digikey.com/en/products/detail/adafruit-industries-llc/4500/11594501). We like that it pick-and-places cleanly and easily on 2-layer PCBs with 8/8 rule DRC, comes with certifications, and has a couple different built-in antenna options, all tuned and ready. In particular, if you want a larger and/or external antenna check out the MDBT50Q-U1MV2 (https://www.digikey.com/en/products/detail/raytac/MDBT50Q-U1MV2/13968055) but we like the chip-antenna version the most. Either way, the module footprint is much easier to work with - you still have pads underneath but they're large, and you can easily fit vias in the unused spots. Just make sure you keep ground clearance around the antenna if you're using an on-module version. If you need tips on schematic and layout, just use our open source hardware design files to guide you - or check Nordic's devZone (https://devzone.nordicsemi.com/). If you've wanted to use the Nordic Semiconductor nRF52840 chip (https://www.digikey.com/en/products/detail/nordic-semiconductor-asa/NRF52840-QIAA-R/7725407) for your ultra low-power Bluetooth LE products, but have hesitated due to the effort of integrating the QFN chip, we can't recommend the Raytac MDBT50Q-1MV2 module (https://www.digikey.com/short/t8hvw1bt) enough! And now that it's for sale through DigiKey, you can pick up some at a great price. Order today and you can BLE-ify your next design by tomorrow afternoon.

Join Scott as he starts working on ESP BLE pairing and bonding (aka initiating encrypted connections), demonstrates building CircuitPython with asyncio python scripts and answers questions. https://github.com/tannewt/circuitpython/tree/embedded-build https://github.com/tannewt/embedded Thanks to dcd for timecodes: 0:00 Getting Started 1:56 Hello - welcome to Deep Dive w/Scott 3:00 Adafruit Feather nRF25840 bluefruit feather example 3:09 We will talk about Bluetooth Low Energy today 4:47 Join #live-broadcast-chat on Discord at http://adafrui.it/discord 5:15 BLE vs Bluetooth "Classic" (older devices) 6:06 ESP32-S2-DevKitC-1 V1.o S2 SOLO N4R2 (bad example, no BLE support :-) ) 6:16 ESPS3 BLE + WiFi 7:43 LED Glasses nRF52840 8:42 Creating Servers and Dynamic Services - from two weeks ago 10:00 Pull Request to add ability to create services (e.g. HID services ) 10:45 Pairing & Bonding / services / characteristics (create a keyboard) 12:20 esp-matter protocol - hamslabs 13:35 PR: Add ESP BLE GATT server support #9222 13:46 also issue Add ESP BLE GATT server support #5926 14:41 Code review process inner workings 15:29 ESP32-H4 and ESP32-P4 annonuncement on espressif.com (not available yet) - but see ESP-IDF SDK 16:14 also added C2 support to circuitpython ( but it ran out of memory ) maybe only one of WiFi or BLE at a time 17:08 and C6 - no RMT neopixel support, but it does have BLE 19:45 using TinyUSB on devices with SPI but no USB 21:03 BLE_EXT_ADV ( extended advertising feature of BLE 5) 24:39 yesterdays ESP32 issue - better debugging by enabling better debug logging 25:40 pondering interrupt handlers and weak functions 26:27 Review files changed in PR9222 26:35 Trade-off OTA for BLE on new 4MB boards 28:00 adding -u to LDFLAGS to deal with weak symbols 29:18 Pairing and Bonding not supported yet 29:50 then maybe look at building CP with new build systems 31:29 Pairing and Bonding ... 33:35 ESP IDF stores bonding information in NVS partion 34:03 look on github circuitpython/tests/circuitpyton-manual for example code (but no BLE code) 34:14 adafruit/Adafruit_CircuitPython_BLE/examples/ble_hid_central.py ( all commented out) 36:13 adafruit/Adafruit_CircuitPython_BLE/examples/ble_current_time_service.py 36:37 iPhone pairing can deliver time 37:08 github espressif/esp-idf/examples/bluetooth/nimble blecent and bleprph 38:38 bleprph/tutorial bleprph_walkthrough.md 41:35 watch running CP and BLE and updating time 43:38 view example for bleprph/main/main.c code 44:14 CP repo ports/espressif/common-hal/_bleio/PacketBuffer.c 44:26 and ports/espressif/common-hal/_bleio/Connection. ( TODO:Implement this ) 46:58 using copilot to make printf debugging faster! 50:54 also Adapter.c 53:39 refer to online CP docs for _bleio 56:20 git switch ble_bonding 58:03 clangd feature for genertated tags in editor ( mentioned a few weeks ago )o 59:54 S3 WROOM-2 N32R8V 1:01:02 set up window for serial output capture and CP serial REPL 1:06:21 update code.py - start test / paired - decode connections 1:09:20 CP doesn't have audio over BLE 1:17:36 use chatgpt to convert C #defines to switch statement function 1:25:54 save the work in process and switch to embedded-build git repo 1:27;20 fetch and pip install the build tool 1:31:28 review the build code in build_circuitpython.py 1:34:44 build tool uses python asyncio to get parallelism 1:35:38 return to the perfetto.dev chart of the threads to see basic trace information 1:43:02 when you call an async function, it doen't even begin to execute it - it just wraps it so you can run it later1:44:20 discussion of zig build system 1:45:30 rerun the build - this time with some more parallel tasks 2:01:43 TODO: add memoization to the build system in the future 2:04:01 push the code tannewt embedded build and wrap up 2:11:10 have a great weekend Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

In this exclusive interview from the NGA show, Michael Wang, CEO, and Vaughn Roller, Chief Business Officer at SIRL, reveal how their cutting-edge retail technology is transforming the way retailers track shopping journeys and optimize store operations. SIRL's real-time location system leverages low-cost tracking tags and wireless infrastructure to achieve an unprecedented 3-foot accuracy and 1-second latency, effectively creating a "physical search engine" for retail. Discover how SIRL's solution empowers retailers to enhance shopper privacy while tapping into the potential of retail media networks and in-store advertising. Learn about the significant ROI and revenue opportunities generated by this technology, as well as its ability to streamline merchandising optimization and shopper behavior clustering. With its easy deployment and reliance on Bluetooth Low Energy, SIRL is poised to revolutionize the retail landscape. And thank you to the VusionGroup for making our coverage of NGA possible! #SIRL #retailtechnology #indoorpositioning #realtimeloca ionsystem #shoppingjourneytracking #lowcosttrackingtags #wirelessinfrastructure #3footaccuracy #1secondlatency #physicalsearchengine #shopperprivacy #retailmedianetworks #instoreadvertising #improvedstoreoperations #ROI #revenueopportunities #easydeployment #merchandisingoptimization #shopperbehaviorclustering #BluetoothLowEnergy

Soy Rafa, tu anfitrión en este viaje semanal por el fascinante mundo de la tecnología. Cada miércoles, exploramos juntos las últimas innovaciones, trucos y consejos que hacen la vida digital más fácil y comprensible para todos.

Delincuentes pro-rusos consiguen detener múltiples trenes en Polonia con un ataque de lo menos sofisticado Fallos de privacidad en el diseño de Bluetooth Low Energy en dispositivos Apple siguen dando la tabarra: o cómo un investigador de seguridad causó pánico entre los asistentes de la DEF CON 31. Notas y referencias en https://www.tierradehackers.com/episodio-105 👁️ YouTube: https://www.youtube.com/tierradehackers 👀 Twitch: https://www.twitch.tv/tierradehackers ➡️ Twitter: https://www.twitter.com/tierradehackers ➡️ LinkedIn: https://www.linkedin.com/company/tierradehackers ➡️ Instagram: https://www.instagram.com/tierradehackers ➡️ Facebook: https://www.facebook.com/tierradehackers ➡️ TikTok: https://www.tiktok.com/@tierradehackers No olvides unirte a nuestra comunidad de Discord: 👾 https://www.tierradehackers.com/discord Si te gusta lo que hacemos, considera apoyarnos en Patreon para que podamos seguir creciendo y crear aun más contenido 🫶 https://www.patreon.com/tierradehackers/ Gracias también a los patrocinadores de este episodio: 👉 Monad (https://www.monad.com) Si quieres venirte a la conferencia organizada por EUROPOL en conjunto con fuerzas y cuerpos de seguridad de España, puedes unirte a la red EDEN en este enlace, y tendrás un descuento en la entrada 👉 https://www.europol.europa.eu/europol-data-protection-experts-network-eden 👉 https://www.europol.europa.eu/publications-events/events/11th-eden-event-whisperers-of-contrast-madrid-spain

Join us for a MASTERCLASS in Bluetooth with amazing guest Mohammad Afaneh! Watch this on YouTube: https://youtu.be/jHEfLGRoxb4 Want to learn more? Check out our training program! https://bit.ly/45ncO8R  Check out the article on our website: https://bit.ly/43X8dsU __________ Novel Bits: https://novelbits.io Bluetooth Developer Academy: https://novelbits.io/academy Intro to Bluetooth Low Energy e-book (v1.0, FREE download): https://novelbits.io/introduction-to-bluetooth-low-energy-book/ Intro to Bluetooth Low Energy e-book (v1.0, Kindle, Paperback): https://a.co/d/hzWyHNM Intro to Bluetooth Low Energy e-book (v2.0): https://novelbits.io/intro-bluetooth-low-energy-version-2/ LinkedIn (if people would like to connect with me): https://www.linkedin.com/in/mafaneh/ https://www.youtube.com/playlist?list=PLYj4Cw17Aw7ypuXt7mDFWAyy6P661TD48 https://novelbits.io/academy/

This week's EYE ON NPI is enjoying the beautiful weather with you, whether sitting in the sun or lounging in the shade - all's good because we've got Nexperia's NEH2000BY Energy Harvesting Power Management IC with embedded solar MPPT capability! (https://www.digikey.com/en/product-highlight/n/nexperia/neh2000by-energy-harvesting-power-management-ic) This tiny, low-cost chip is a one-stop solution for extending the life of your product by making it powered by small solar cells. This chip is perfect for wearables or miniature sensor nodes, maybe with a LoRa radio, WiFi or Bluetooth Low Energy where space and pricing is important. For example, an asset tracker, traffic monitor, activity watch, or agricultural sensor network: stuff that is outside anyways so it'll be designed for outdoor use and have lots of sun exposure. We've covered other MPPT tracking solar harvesting chips (https://blog.adafruit.com/2021/04/23/eye-on-npi-max20361-tiny-single-multi-cell-solar-harvester-maximintegrated/), and the NEH2000BY has some advantages in size, cost and simplicity. Either use it to increase the time between charges, or use it to have your product be fully encased with no need for charging at all, thanks to the power of the SUN (https://solarsystem.nasa.gov/solar-system/sun/galleries/?page=0&per_page=25&order=created_at+desc&search=&href_query_params=category%3Dsolar-system_sun&button_class=big_more_button&tags=sun&condition_1=1%3Ais_in_resource_list&category=51) The Nexperia NEH2000BY energy harvester (https://www.digikey.com/short/hpnfttw3) is designed specifically for use with solar cells because cells collapse under high current draw - which is what batteries want when they are charging up so that they can be ready to go ASAP! When drawing current from a solar cell, at the very beginning the voltage is very high, then is slowly drops down as more is drawn until the input voltage collapses completely. So you have to be very careful when drawing current - too little and you lose out on efficiency, too much and your power goes away completely. There's a 'sweet spot' right in the middle, where you can get the most power output, which is called the Max Power Point. (https://en.wikipedia.org/wiki/Maximum_power_point_tracking) And this point varies with how much sunlight you get - so it isn't something you can pre-program in with a comparator or anything. Instead, the energy harvester has to wiggle the power draw forward and back to find the maximum point. For large-scale solar installations, you'd have a microcontroller do the math for you, and adjust throughout the day - it isn't hard to do MPPT it just takes measurement and computation. But in small and low-current situations, you can't spend all your power budget on a microcontroller to manage your battery charger. First up, almost no extra components are needed: just a stabilization capacitor plus a capacitor for the switched-cap boosting doubler. Note that there's no inductor because it seems to use a switched-cap boosting method for approximately 2x voltage output - so you will need to spec a panel that, when the MPPT voltage is approximately doubled, you'll have about 0.3V above the battery voltage. There's some math in the datasheet to work this out but basically in the end, use a panel with an open-circuit voltage - Voc - that is about 0.7 times the battery voltage. So, e.g. if you're using a Lipoly (https://www.digikey.com/short/h02tmj1q), with a VBat of 4.2V, use a 3V solar panel - which is very common and inexpensive. For NiMH cells, add up the total series voltage before multiplying by 0.7 for the Voc desired. To keep your battery from over-charging, either use a separate battery charger chip that will do the constant-current to voltage-limited charging, or use a low cost over-voltage protection (OVP) chip as recommended in the datasheet. If you'd like to integrate the Nexperia NEH2000BY Energy Harvesting Power Management IC (https://www.digikey.com/short/hpnfttw3) into your next solar-powered product, thank your lucky stars because DigiKey has the NEH2000BY in stock right now at a great price for immediate shipment. With the long summer days ahead, you can order today and be max-power-point'ing before the sun sets tomorrow.

Peggy Smedley and Scott Schober, president & CEO, Berkeley Varitronics Systems, talk about a new Kickstarter campaign for BlueSleuth-Lite. He says the product focuses in on Bluetooth Low Energy and scans all around looking for devices using it. The technology helps to determine if someone is being tracked or followed using tags.  They also discuss: What he is hoping to accomplish with this Kickstarter campaign. The difference between GPS trackers and tags. What the consumer wants from technology such as this. bvsystems.com  (2/14/23 - 809) IoT, Internet of Things, Peggy Smedley, artificial intelligence, machine learning, big data, digital transformation, cybersecurity, blockchain, 5G, cloud, sustainability, future of work, podcast, Scott Schober, Berkeley Varitronics Systems, Kickstarter, BlueSleuth-Lite This episode is available on all major streaming platforms. If you enjoyed this segment, please consider leaving a review on Apple Podcasts.

Peggy Smedley and Scott Schober, president & CEO, Berkeley Varitronics Systems, talk about a new Kickstarter campaign for BlueSleuth-Lite. He says the product focuses in on Bluetooth Low Energy and scans all around looking for devices using it. The technology helps to determine if someone is being tracked or followed using tags.  They also discuss: What he is hoping to accomplish with this Kickstarter campaign. The difference between GPS trackers and tags. What the consumer wants from technology such as this. bvsystems.com  (2/14/23 - 809) IoT, Internet of Things, Peggy Smedley, artificial intelligence, machine learning, big data, digital transformation, cybersecurity, blockchain, 5G, cloud, sustainability, future of work, podcast, Scott Schober, Berkeley Varitronics Systems, Kickstarter, BlueSleuth-Lite This episode is available on all major streaming platforms. If you enjoyed this segment, please consider leaving a review on Apple Podcasts.

This week's EYE ON NPI won't have you singin' the blues about Bluetooth stack development. It's InPlay IN100 NanoBeacon™ Bluetooth® Low Energy Beacon SoC (https://www.digikey.com/en/product-highlight/i/inplay/in100-nanobeacon-soc), an ultra-low cost way to make sensor beacons for data collection, with no coding required! These flash-less chips are packed with peripherals that can be configured with a desktop tool and then burned into OTP EEPROM memory. That makes them both reliable and very inexpensive, so they're great for distributed sensors that may end up getting damaged or lost. They're also great for when you want to get something into production super fast and don't want to spend time learning Bluetooth SDKs or wireless stacks. Bluetooth LE is a low-power 2.4GHz protocol that has some nice 'connection-less' capabilities. Unlike WiFi and cellular, BLE has the ability to act like a 'beacon' (https://learn.adafruit.com/introduction-to-bluetooth-low-energy) where data is blipped out for anyone to listen to. (https://learn.adafruit.com/alltheiot-transports/bluetooth-btle) Note that in beacon mode, there's no wireless reception happening - and because there's no need to listen for packets, the beacon can go into very, very low power usage because it just has to wake up, send the beacon out, and go back to deep sleep. Receiving requires a lot more power because you have to be listening at all times. Beacons are what are used in "lost and found" tags, for asset or people tracking, as well as distributing URLs.(https://en.wikipedia.org/wiki/Bluetooth_Low_Energy_beacon) Normally, folks would use a common BLE chipset such as nRF, Dialog, or TI - often these come with a ARM Cortex chip inside that can run a BLE stack. The stack can either be the in-house brand such as the nRF SDK (https://www.nordicsemi.com/Products/Development-software/nrf5-sdk) or a third-party like Zephyr (https://docs.zephyrproject.org/3.1.0/connectivity/bluetooth/api/index.html) but either way you have to write some code and burn it into the chip. You also have to learn how to manage the low power modes and debug your code. For many basic beacon projects, such as measuring a digital, analog, or I2C sensor - the IN100 is pretty amazing: all the low power and SDK stuff is done - you just have to configure each board and burn in the settings. The good news is that you can deploy your beacons or sensor nodes super fast, and because the core is designed to only do this one thing, the chips are really really cheap. Like 40 cents per piece cheap! (https://www.digikey.com/en/products/filter/rf-transceiver-ics/879?s=N4IgTCBcDaIJYDsCMAGFIC6BfIA) Your entire BOM for a beacon product could easily be under $1 including the coin battery. They're available in 10-DFN IN100-D1 (https://www.digikey.com/short/3jmnp8r3) and 18-QFN IN100-Q1 (https://www.digikey.com/short/mtp92d50) depending on how many GPIO you need. Since the trade-off for the ultra-simple design and low BOM cost is OTP memory, we recommend getting the IN100 evaluation kit (https://www.digikey.com/short/0q0jwwqq) which comes with a programming dongle and three beacon boards fitted with the QFN version of the IN100. Then download the cross-platform configuration tool (https://inplay-tech.com/nanobeacon-config-tool) and follow the YouTube video tutorials they've filmed to learn how to configure the beacons for different advertising modes. (https://www.youtube.com/watch?v=dJfQ059KzRg) Don't worry about making mistakes: you can always run from RAM to iterate the design before finally burning it into the OTP! And even if there are errors, the InPlay IN100 NanoBeacon Eval Kits are inexpensive (https://www.digikey.com/short/5z920hrj). Once you're ready to go into production, the individual chips are plentiful and low cost (https://www.digikey.com/short/97773wh3) so you can get into production almost immediately. The InPlay IN100 NanoBeacon Eval Kits (https://www.digikey.com/short/5z920hrj), IN100-D1 (https://www.digikey.com/short/3jmnp8r3) and IN100-Q1 (https://www.digikey.com/short/mtp92d50) are all in stock right now for immediate shipment from Digi-Key - available nowhere else! If you're curious to try this no-code BLE beacon chipset, order today and you can be Bluetooth Beacon'ing by tomorrow afternoon!

That's why SwaraLink Technologies created the Bluetooth Low Energy Developer's Checklist. In this podcast, the CEO and Co-Founder of SwaraLink Technologies, Sandeep Kamath, breaks down BLE and the checklist they've created, including various topics, from optimizing throughput and power consumption to ensuring secure connections and supporting over-the-air firmware updates. These aren't necessarily must-dos, but they're essential considerations to keep in mind as you design, develop, and test your product.Sandeep was initially a self-taught programmer, playing around with QBASIC and Visual C++ in high school, but then shifted his interest from software to hardware while at the university level. He received his Bachelor's and Master's degrees in Electrical Engineering from the University of California, San Diego, focusing on Analog and RF Integrated Circuit Design. His educational background in hardware and RF systems and personal interest in software eventually led him to the world of embedded wireless systems. After graduating, Sandeep spent over a decade in the semiconductor industry, including eight years working for Texas Instruments Wireless Connectivity group. During his career at TI, Sandeep worked in various technical, management, and business roles, all related to TI's Bluetooth Low Energy product line. In 2017 Sandeep took his knowledge of Bluetooth Low Energy from both a technology and market standpoint and founded SwaraLink Technologies to help companies build high-quality products with great user experiences.SwaraLink Technologies is a services and solutions company focused on Bluetooth Low Energy (BLE) systems and software. Their flagship product, the SwaraLink Bluetooth Low Energy Platform, is a cross-platform middleware solution that reduces the cost of developing high-quality products that use Bluetooth Low Energy technology. SwaraLink was founded and incorporated in the State of California in 2017, with headquarters in San Diego. Since its founding, SwaraLink has helped numerous customers with various services, including architecture, development, testing, and debugging complex hardware and software systems that use Bluetooth and Bluetooth Low Energy Technology.

The Six Five On The Road at #SnapdragonSummit 2022. Hosts Patrick Moorhead and Daniel Newman sit down with Sarah McMurray, Sr. Manager, Product Marketing for Voice & Music at Qualcomm, for one of many conversations at this year's #SnapdragonSummit. Their discussion covers: The launch of S5 & S3 Gen 2 Sound Platforms Technical improvements with S5/S3 Snapdragon Sound Platform in the commercial market Importance of spatial audio and Bluetooth Low Energy

#circuitpythonparsec Give your Bluetooth Low Energy object descriptive advertised name in CircuitPython. To learn about CircuitPython: https://circuitpython.org Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Adafruit on Instagram: https://www.instagram.com/adafruit Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

Archer Aviation planning full transition flights of their Maker aircraft, drone shuts down Ronald Reagan Washington National Airport, protecting sporting events with drones, using lasers for drone communications, RQ-4 Global Hawk end-of-life, alligator attacks drone, a Remote ID device from Aerobits, and the Zephyr UAS flies for 26 days. Archer Aviation Maker eVTOL. UAV News Archer Flight Testing Gains Momentum, On Pace to Achieve Transition Flight By Year End Archer Aviation Inc. announced it is confident it will achieve its goal of flying full transition flights with its Maker aircraft by year-end. Flight tests of the full-scale 12-motor eVTOL demonstrator aircraft with a Tilt Propeller System (TPS) have been successful. Maker successfully completed its first hover test flight in December 2021 and since then the engineering team has focused on the development and testing of the systems needed for a full transition to horizontal flight. Errant drone briefly shuts down D.C. airport Air traffic was shut down at Ronald Reagan Washington National Airport for 45 minutes. There is no information about who was operating the drone, if it was taken down, or if it was retrieved.  The DHS told Congress that TSA has reported nearly 2,000 drone sightings near U.S. airports since 2021. Pilots had to take “65 evasive actions” after drones came too close or disturbed aircraft. World Cup to use drones to help protect stadiums Utah-based Fortem Technologies has reached an agreement with Qatar's interior ministry to provide the interceptor drones at this winter's Fifa World Cup in Qatar. Fortem's “DroneHunters” that shoot nets will be able to bring down small rogue drones. These are autonomous, radar-guided drones. Laser-Controlled Drones Can Evade Signal-Jamming Countermeasures The counter-drone technology that physically attacks rogue drones with a net or a projectile requires that you track the drone's movement. On the other hand, signal jamming doesn't require such precise tracking. But now British company QinetiQ has a way to remotely operate drones without the communication signals that can be jammed. The new system uses lasers or Free-Space Optical Communications (FSO, or FSOC) signals. Air Force's RQ-4 Global Hawk drones headed for retirement in FY27 The US Air Force plans to phase out all remaining RQ-4 Global Hawk reconnaissance drones by fiscal 2027. Northrop Grumman was informed they should expect that the fleet will reach its end of life by that date. In a statement, an Air Force spokeswoman said, “Our ability to win future high-end conflicts requires accelerating investment in connected, survivable platforms and accepting short-term risks by divesting legacy ISR assets that offer limited capability against peer and near-peer threats.” What a snap! Moment alligator leaps out of Brazilian river and devours nosy fisherman's drone in mid-flight A Brazilian man was testing his new drone and had seen some alligators, so he flew back to the spot. The drone hovered over one of the alligators who eyed the drone for a few seconds. The gator then lept out of the water, grabbed the drone, and swam away. Video: Alligator leaps out of Brazilian river and snatches drone in mid flight https://youtu.be/rXeU7_l-PEo The most advanced Remote ID with WI-FI and BLE technology Aerobits has launched an advanced version of the idME PRO device that can broadcast on Wi-Fi and Bluetooth. It provides enhanced identification and tracking for UAS and works with MAVLINK devices. The Wi-Fi can connect to the Pixhawk drone controller via a JST connector. The Bluetooth Low Energy (or BLE) provides surveillance and drone operator identification capability via smartphones or tablets.  US Army conducts high-altitude experiments with Zephyr UAS The U.S. Army wants to implement ultra-long endurance stratospheric UAS capabilities. During a June 2022 test flight,

This week we try to determine whether Netflix has jumped the shark and what they can do save the company. We also take a look at a new smart home protocol from Broadlink called Fastcon. It's highly reliable and very affordable. We also read your emails and discuss the week's news. News: LG 'Objet' OLED Evo TVs prioritise both style and substance Android TV reaches 10K streaming apps There's a new OLED TV panel manufacturer on the block Cox explores a smart TV strategy Other: doitforme.solutions Sonos Voice Assistant - what is it, how does it work, how does it compare? Apple Inks 10 Year Global Deal for Major League Soccer Has Netflix jumped the shark? - Listener email and discussion Just been thinking about Netflix and wanted to share my thoughts  The old saying from Happy days when the Fonz jumped a shark tank on water skis and Happy Days was never the same. Innovation & Interface No one can say that Netflix was not an innovator in the DVD delivery and then streaming service.  They showed everyone what could be done and pioneered the streaming services.  A wise person in the software business who I work with to create our company's digital platform told me this that our product was visionary and ahead of anything currently on the market.  He then said let's make sure that we keep pushing forward because the competition is coming and this is their starting point.  Netflix in my opinion is no longer the innovator they once were and have fallen behind the crowd.  I believe the lack of integrating into a box or TV streaming OS really hurts them.  This is my main way to find new stuff to watch and the what's next makes decisions easier.  Their interface I believe is one of the worst of the main stream services.  They have gone to allowing algorithms show you movies/shows that it thinks you would want to watch.  I have a soft side I don't always need to see thing blow up in what I watch.  Trying to find the vast majority of their library is difficult.  The other streaming service allow you to see everything they have very easily again in my opinion. Cost of main stream streamers & Business Model Netflix 4k streaming at $19.99 Disney Bundle – No ads 4k streaming - $19.99 Netflix - 1080P only - @ $15.49 HBO Max - 4k streaming @ $14.99 Disney Bundle adds - $13.99 All others are under $10 a month I believe    They raised their prices at the wrong time as inflation was starting to it creep up they raised the prices and in reality or the #1 & 2 highest priced streaming services as the Disney bundle is 3 separate services.  Also, it was kick in the face to be charging $15.49 for 1080P streaming – this is when I said goodbye.  I have kept my Paramount, Discovery, Apple TV+, subscription because their prices is low and upgraded to Peacock without commercials because the per month price is under $10.  I do get the Disney bundle and HBO Max free and if I had to pay for them I would pay from HBO Max & Disney Plus – wait for the $1 deal from hulu to sign back up. Their business model of binging is great for consumers but not the corporations.  Once Netflix jumped the shark with their prices I decided I could just wait till the late summer and re-activate for a month or two to see all their good content and then put the service back on pause.  Disney & HBO have the weekly release that to me makes more invested in their services and they have good content.   Future Does NetFlix go the way of Blackberry, MySpace or can they reinvent themselves?  This is the questions each stockholder is asking right now.  If I were in charge first thing I would do is realize that I'm no longer the only big dog and be honest about my place in the streaming world.  I would integrate with the Box and TV OS's integrated search.  I would redesign my interface.  I would change my $15.49 price to allow for 4K streaming.   I would not buy Roku as that does not help you but spend money.  If your plan is to make it the only way to get Netflix then you really don't know your place in the streaming war.  If you want to buy something look for a content provider with a big catalog if there is one left.  I hope Reid can see beyond his ego and reshape Netflix to be competitive and still deliver great content and reasonable price.  Roku Staffers Swirl in Netflix Acquisition Rumors  Roku stock was up nearly 10% Wednesday morning as internal discussions focus on the possibility of a tie-up with a streaming giant that suddenly needs help with advanced advertising Full article here… Ad supported streaming? - With Roku Netflix would not have to share revenue with other hardware makers.  Broadlink FastCon Smart Home Protocol We have spoken a lot about Matter this year as a way to unify the Smart Home market. Well there is another protocol that has recently been released that has some pretty cool features. We're talking about the Broadlink FastCon Smart Home Protocol. FastCon BLE is a patented communication technology based on Bluetooth Low Energy developed by BroadLink, boasting many advantages over their previous Wi-Fi based smart products. Benefits include: Zero Setup: Power up > Device Appears Batch Installation: Add up to 90 devices in one second Super Mesh Network: Extends signal range up to 500m covering all your house even in commercial buildings. Max 250 devices require only one gateway - saves your cost and time implementing and won't crash your router anymore No Internet Required: The fastest control experience is direct local access Almost all controls especially for lighting are operated locally (except voice control) Bluetooth connection enables you to control devices via App or switch at home No Account Required: Boot up, open the app and add your devices Guaranteed Success Rate: 99.99% device discovery and control rate. Enhanced mesh repeating mechanism guaranteed the delivery of control commands but avoiding duplicated signals Low Cost: Very cost-effective FastCon BLE Chipset, which lowers device cost What devices are on the market? Broadlink has a lot of devices and from what we can tell you can do your entire home with their devices and here is the kicker, their products are inexpensive. They even have an IR remote that allows you to integrate your smart home with your home theater. The best way to get started is with a starter kit that consists of 3 A19 Bluetooth Color Changing Light Bulbs with Music Sync, 1 Wireless Scene Switch and a Hub. While the Hub is not required for local control, it does allow remote access of your home as well as voice control via Alexa or Google Home. All of this for the whopping price of $34.99! There are Smart Touch Wall Light Switches available for $24.99 for the 1 Gang model that requires a hub but not included. The version that comes with a hub is only two dollars more ($26.99). Someone is taking a loss on the hub! There is a model that allows you to control three light lights for $30.99.  There are also two types of wall plugs, and the cheapest one available is $5.99 and is a simple on and off switch. The second version has a dimmable night light that sells for $11.99 You can use the $24.99 Smart Button (includes a hub) to kick off scenes and automations as well as control lights and turn on your home entertainment system. To control your home entertainment system you will need the Mini IR Universal Remote Control which runs $25,99.  They support almost all TVs and entertainment systems on the market today. But with this remote you are not limited to TVs. You can control AC Units, blinds, and pretty much anything that takes an IR command.  This system looks similar to Insteon in the sense that it is proprietary. We didn't find a Thermostat that works with it so keep that in mind. It is also unlikely that Broadlink will support Matter anytime soon. If you go this route you may be on an island. Albeit a nice tropical island.  

Podcast: Control Loop: The OT Cybersecurity PodcastEpisode: Welcome to Control Loop: Giving back to the OT community.Pub date: 2022-06-01Every two weeks, get the latest in OT news in Control Loop News Brief, an interview featuring a thought leader in the OT space sharing current industry trends, and the Control Loop Learning Lab's educational segment. A companion monthly newsletter is available through free subscription and on the CyberWire's website.Headlines include: Russia's hybrid war against Ukraine. Russian threat actors against industrial control systems. Exploits for Bluetooth Low Energy. Hacktivists claim attacks against Russian ground surveillance robots. New wiper loader. Turla threat actor reconnaissance in Estonian and Austrian networks. Robert M. Lee, CEO of Dragos, talks giving back to the OT community and shares insights on Pipedream malware. Learning Lab has Dragos' Mark Urban and Jackson Evans-Davies talking about the fundamentals of OT cybersecurity.Control Loop News Brief.Continuing expectations of escalation in cyberspace.Microsoft President: Cyber Space Has Become the New Domain of Warfare - Infosecurity MagazineCyber Attacks on Ukraine: Not What You Think | PCMag Warning: threat actor targets industrial systems.US warns energy firms of a rapidly advancing hacking threat - E&E NewsPIPEDREAM: CHERNOVITE's Emerging Malware Targeting Industrial Environments | DragosPipedream Malware: Feds Uncover 'Swiss Army Knife' for Industrial System Hacking | WIREDIndestroyer2 and Ukraine's power grid. Twitter: @ESETresearchIndustroyer2: Industroyer reloaded | WeLiveSecurityRussian hackers tried to bring down Ukraine's power grid to help the invasion | MIT Technology ReviewBluetooth vulnerabilities demonstrated in proof-of-concept.NCC Group uncovers Bluetooth Low Energy (BLE) vulnerability that puts millions of cars, mobile devices and locking systems at riskTesla Hacker Proves a Way of Unlocking Doors, Starting Engine - BloombergCISA and its international partners urge following best practices to prevent threat actors from gaining initial access.Weak Security Controls and Practices Routinely Exploited for Initial Access | CISAHacktivists claim to have compromised Russian-manufactured ground surveillance robots.Did hackers commandeer surveillance robots at a Russian airport?Twitter: @caucasnetPolitically motivated DDoS attack on Port of London Authority website.Twitter: @LondonPortAuthPro-Iran Group ALtahrea Hits Port of London Website by DDoS Attack New loader identified in wiper campaigns.Sandworm uses a new version of ArguePatch to attack targets in Ukraine | WeLiveSecurity Turla reconnaissance detected in Austrian and Estonian networks.Russian hackers perform reconnaissance against Austria, Estonia TURLA's new phishing-based reconnaissance campaign in Eastern Europe SANS ICS Summit is coming to Florida, June 1-9.ICS Security Summit & Training 2022Colonial Pipeline's ransomware attack, one year later.How the Colonial Pipeline attack instilled urgency in cybersecurityOT vulnerabilities as credit risk.Operational Technology Cyberattacks Are a Credit Risk for UtilitiesA Cyber Resilience Pledge. Global CEOs Commit to Collective Action on Cyber Resilience Recent threat intelligence findings from Dragos.Dragos ICS/OT Ransomware Analysis: Q1 2022Control Loop Interview.Robert M. Lee, CEO of Dragos, on giving back to the OT cybersecurity community, the idea behind the Control Loop podcast and newsletter, and his candid thoughts on the Pipedream malware and its creators.Follow Rob on LinkedIn and Twitter.Control Loop Learning Lab.Dragos' Mark Urban and Jackson Evans-Davies on the fundamentals of OT cybersecurity and network architecture.Dragos 2021 ICS Cybersecurity Year in ReviewHow to Build a Roadmap for ICS/OT Cybersecurity: 3 Steps to a Sustainable ProgramManaging External Connections to Your Operational Technology EnvironmentImproving ICS/OT Security Perimeters with Network SegmentationThe podcast and artwork embedded on this page are from CyberWire Inc., which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

Every two weeks, get the latest in OT news in Control Loop News Brief, an interview featuring a thought leader in the OT space sharing current industry trends, and the Control Loop Learning Lab's educational segment. A companion monthly newsletter is available through free subscription and on the CyberWire's website. Headlines include: Russia's hybrid war against Ukraine. Russian threat actors against industrial control systems. Exploits for Bluetooth Low Energy. Hacktivists claim attacks against Russian ground surveillance robots. New wiper loader. Turla threat actor reconnaissance in Estonian and Austrian networks. Robert M. Lee, CEO of Dragos, talks giving back to the OT community and shares insights on Pipedream malware. Learning Lab has Dragos' Mark Urban and Jackson Evans-Davies talking about the fundamentals of OT cybersecurity. Control Loop News Brief. Continuing expectations of escalation in cyberspace. Microsoft President: Cyber Space Has Become the New Domain of Warfare - Infosecurity Magazine Cyber Attacks on Ukraine: Not What You Think | PCMag  Warning: threat actor targets industrial systems. US warns energy firms of a rapidly advancing hacking threat - E&E News PIPEDREAM: CHERNOVITE's Emerging Malware Targeting Industrial Environments | Dragos Pipedream Malware: Feds Uncover 'Swiss Army Knife' for Industrial System Hacking | WIRED Indestroyer2 and Ukraine's power grid.  Twitter: @ESETresearch Industroyer2: Industroyer reloaded | WeLiveSecurity Russian hackers tried to bring down Ukraine's power grid to help the invasion | MIT Technology Review Bluetooth vulnerabilities demonstrated in proof-of-concept. NCC Group uncovers Bluetooth Low Energy (BLE) vulnerability that puts millions of cars, mobile devices and locking systems at risk Tesla Hacker Proves a Way of Unlocking Doors, Starting Engine - Bloomberg CISA and its international partners urge following best practices to prevent threat actors from gaining initial access. Weak Security Controls and Practices Routinely Exploited for Initial Access | CISA Hacktivists claim to have compromised Russian-manufactured ground surveillance robots. Did hackers commandeer surveillance robots at a Russian airport? Twitter: @caucasnet Politically motivated DDoS attack on Port of London Authority website. Twitter: @LondonPortAuth Pro-Iran Group ALtahrea Hits Port of London Website by DDoS Attack  New loader identified in wiper campaigns. Sandworm uses a new version of ArguePatch to attack targets in Ukraine | WeLiveSecurity  Turla reconnaissance detected in Austrian and Estonian networks. Russian hackers perform reconnaissance against Austria, Estonia  TURLA's new phishing-based reconnaissance campaign in Eastern Europe  SANS ICS Summit is coming to Florida, June 1-9. ICS Security Summit & Training 2022 Colonial Pipeline's ransomware attack, one year later. How the Colonial Pipeline attack instilled urgency in cybersecurity OT vulnerabilities as credit risk. Operational Technology Cyberattacks Are a Credit Risk for Utilities A Cyber Resilience Pledge.  Global CEOs Commit to Collective Action on Cyber Resilience  Recent threat intelligence findings from Dragos. Dragos ICS/OT Ransomware Analysis: Q1 2022 Control Loop Interview. Robert M. Lee, CEO of Dragos, on giving back to the OT cybersecurity community, the idea behind the Control Loop podcast and newsletter, and his candid thoughts on the Pipedream malware and its creators. Follow Rob on LinkedIn and Twitter. Control Loop Learning Lab. Dragos' Mark Urban and Jackson Evans-Davies on the fundamentals of OT cybersecurity and network architecture. Dragos 2021 ICS Cybersecurity Year in Review How to Build a Roadmap for ICS/OT Cybersecurity: 3 Steps to a Sustainable Program Managing External Connections to Your Operational Technology Environment Improving ICS/OT Security Perimeters with Network Segmentation

This week's EYE ON NPI is chillin' and listening to some vibin' beats - we're featuring Nordic's jam-packed nRF5340 Audio Development Kit (https://www.digikey.com/en/product-highlight/n/nordic-semi/nrf5340-audio-development-kit) that will get you going fast with Bluetooth Low Energy audio development with a lovely kit that has everything you need to build both basic and advanced BTLE audio demos that exercise all the new capabilities of BT 4.x and 5.x's native audio streaming technology Audio was one of the first killer app's for Bluetooth adoption. Who doesn't remember when ubiquitous 'hands-free' headsets (https://en.wikipedia.org/wiki/Headset_(audio)#Bluetooth_wireless_headsets) started popping up in every business guy's ear. For mobile devices, these headsets turned out be quick to pair, and allowed people to talk, or listen to music, while driving or working without wires. Bluetooth classic audio is still incredibly popular today: not just used in headsets but also in Bluetooth speakers (https://www.digikey.com/en/products/detail/klein-tools-inc/AEPJS2/11570486), hearing aids, wireless mics, home voice agents, and more! When the audio profile was first invented, there were a few, totally reasonable restrictions placed on how it was used. First, it's a point-to-point connection - also called source-sink connection. There's a supplier source of audio - say the MP3 player - and a destination sink like a speaker. Second, the compression codec had to match the processor and battery capabilities of late 90's technology. The first classic codec was called SBC, although recently there are newer codecs that can do a better job with reducing lossyness and, of course, can take advantage of the Moore's-law improvements in memory and processor capabilities. Unfortunately, as one can expect in such a technology space, many of the codecs are patented, licensed, and require per-device fees. Also, unless you know what to look for, it's harder to compare two headsets with different codecs, as another variable that affects audio quality and delay. While many non-audio/non-keyboard devices have thankfully moved from BT classic to BTLE, mostly in order to avoid Apple's MFI program, there's been a bit of a lag in getting audio devices to switch over from classic to LE due to the high inertia of technological laziness. However, in the last few years, a Really Good Reason to move over has been invented: AirPods! (https://www.apple.com/shop/product/MME73AM/A/airpods-3rd-generation) Yep, when Apple came out with their new wireless Bluetooth earbuds, they had to come up with a custom BTLE protocol - because there's two sinks and one source, and even if you created two connections (one for left and one for right) the source would have to work hard to synchronize audio. Sure Apple can put the time and money into that kind of development, but what about everyone else who wanted to make similar products? That's why when BTLE audio came 'free' with multi-point transmission and synchronization and an improved free codec, folks' ears started perking up. With Nordic's new nRF5340 ADK (https://www.digikey.com/short/vm7q7fwz), creating advanced BTLE Audio applications is super fast. The nRF5340 is a dual core ARM processor, which means it's easy to have one core dedicated to codec management and DMA audio streaming, and the other core for interfacing and control. The free software examples (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/nrf5340_audio/README.html) come with two main demos right now: a synchronous example for making wireless earbuds, and a broadcast example for sending audio to multiple sinks. Note that for these examples you'll often want two ADKs so you can stream audio to both ADKs as a way to mimic earbuds, for example. And, have you heard the good news? Digi-key has a TON of the nRF5340 Audio Development Kit (https://www.digikey.com/short/vm7q7fwz) in stock right now for immediate shipment. Each ADK has all the accessory hardware needed to immediately bootstrap your BTLE example project. (Hint, it's also a great dev board for general nRF5340 development, with SD card, built in debugger, power management, Arduino-esque headers, RGB LEDs, and user interface buttons. Pick up two of these dev kits today and you can be jammin' and boppin' by tomorrow afternoon!

This episode reports on credit card web scraping with PHP, Conti ransomware gang threatens overthrow of Costa Rica, a warning to users of Bluetooth Low Energy smart locks patches from Nvidia

A daily look at the relevant information security news from overnight.Episode 238 - 17 May 2022Apple attack - https://www.bleepingcomputer.com/news/security/apple-emergency-update-fixes-zero-day-used-to-hack-macs-watches/Conti hits Parker - https://www.infosecurity-magazine.com/news/parker-conti-ransomware/Tesla BLE - https://www.bleepingcomputer.com/news/security/hackers-can-steal-your-tesla-model-3-y-using-new-bluetooth-attack/Card skimming - https://www.zdnet.com/article/fbi-hackers-used-malicious-php-code-to-grab-credit-card-data/iPhone vulv- https://threatpost.com/iphones-attack-turned-off/179641/Hi, I'm Paul Torgersen. It's Tuesday May 17th, 2022, and this is a look at the information security news from overnight. From BleepingComputer.com:Apple has released security updates to address a zero-day vulnerability that threat actors can exploit in attacks targeting Macs and Apple Watches. The flaw is an out-of-bounds write issue in the AppleAVD, the kernel extension for audio and video decoding. Apple says it is likely this has already been exploited in the wild. From Infosecurity-magazine.com:US manufacturer Parker-Hannifin has announced a data breach exposing employees' PII after being the target of a Conti ransomware attack. The company said that an unauthorized third party gained access to its IT systems between 11 and 14 of March this year. On the plus side, if you‘re information was involved, you just got two free years of identity theft monitoring. From BleepingComputer.com:Security researchers at the NCC Group have developed a tool to carry out a Bluetooth Low Energy relay attack that bypasses all existing protections to authenticate on target devices. What target devices, you ask? Teslas. Details in the article. From ZDNet.com:The FBI put out a warning that someone is scraping credit card data from the checkout pages of US businesses' websites. The bad actor is injecting malicious PHP Hypertext Preprocessor code into the business' online checkout page and sending the scraped data to a server that spoofed a legitimate card processing server. They also left a backdoor into the victims system. And last today, from ThreatPost.comBecause of how Apple implements standalone wireless features such as Bluetooth, Near Field Communication and Ultra-wideband technologies, researchers have found that iPhones are vulnerable to malware loading attacks even when the device is turned off. The root cause of the issue is how iPhones implement low power mode for wireless chips. No comment yet from Apple, but there is a link to the research report in the article. That's all for me today. Remember to LIKE and SUBSCRIBE. And as always, until next time, be safe out there.

This is the Learning by Proxy podcast for Edition 94. If you do not enjoy reading long-form, get the gist of it in about 10 minutes (or that was the hope). This time in the podcast - Mesh Networks have been around and have been used in WiFi applications for years now. They are being increasingly used with Bluetooth Low Energy devices to ostensibly track missing items. But the work and time that it has taken to build these networks make me think there is a much larger plan in the works here.You can find the whole blog at this link.Music Courtesy Pixabay This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.learningbyproxy.com

In S2 episode 10 and part two of our two-part special with Nordic Semiconductor, we are joined by Svein-Egil Nielsen - CTO and Paal Kastnes to unwrap the transformations happening in short-range IoT!⌚️

Supply Chain visibility and sustainability are two of the most important topics in supply chain today. So when I came across Sony Visilion's Head of IoT Tracking Erik Lund I knew I had to get him on the podcast. Fortunately he was delighted to join and we had a great discussion about IoT tracking and the visibility implications of that, and we also talked about the sustainability implications of seeing the data associated with your shipments.As usual, I learned loads, and I hope you do too...Oh, and this is one of the first podcast episodes that I have created chapters for. If you find them useful, do let me know (tom.raftery@sap.com) and I'll make the effort to do it more often!If you have any comments/suggestions or questions for the podcast - feel free to leave me a voice message over on my SpeakPipe page or just send it to me as a direct message on Twitter/LinkedIn. Audio messages will get played (unless you specifically ask me not to).If you want to learn more about how to juggle sustainability and efficiency mandates while recovering from pandemic-induced disruptions, meeting growth targets, and preparing for an uncertain future, check out our Oxford Economics research report here.And don't forget to check out the 2021 MPI research on Industry 4.0 to find out how to increase productivity, revenues, and profitability for your operations. This global study examines the extent to which manufacturers deploy Industry 4.0 in their business and the benefits it brings.And if you liked this show, please don't forget to rate and/or review it. It makes a big difference to help new people discover it. Thanks.And remember, stay healthy, stay safe, stay sane! 

Miguel Reyes nos da una catedra sobre que se necesita para empezar a hacer productos un poco mas profesionales que utilicen bluetooth low Energy. Hay funciones de seguridad que protegen tu aplicación pero eso ocasiona que se necesiten mas herramientas para poder diseñar de forma mas sencilla y evitarse problemas. Esperemos que lo disfruten

On today's show we discuss watching Dune from our home theaters, Seven Alexa commands you are probably not using, and why we think Matter really matters. Plus we have two weeks of emails and news. Dune - Our thoughts 7 Alexa commands you're probably not using (but should be) With Alexa and the range of Echo devices, -- including smart displays and smart speakers -- Amazon has built a robust service that can deliver seemingly endless information and control your home. But, are you actually taking full advantage of all it can do? Full article here… Samsung promises Matter support for SmartThings hubs, Galaxy devices, TVs, and fridges The Matter smart home train is picking up steam. Following Google's commitment to the new standard at its developer conference last week and Apple's addition of Matter support in iOS 15 at WWDC, Samsung is now following suit. The company announced a complete adoption of Matter across ​Samsung's Galaxy devices, televisions, Family Hub appliances, and SmartThings hubs at SDC21, its virtual developer conference being held this week. Full article here… Matter is the foundation for connected things. This industry–unifying standard is a promise of reliable, secure connectivity—a seal of approval that devices will work seamlessly together, today and tomorrow. Matter is creating more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers. This collaborative breakthrough is built on proven technologies and guided by the Connectivity Standards Alliance (formerly Zigbee Alliance), whose members come together from across industries to transform the future of connectivity. Companies from across the industry are contributing market-proven technologies and best practices. Matter is built around a shared belief that smart home devices should be secure, reliable, and seamless to use. By building upon Internet Protocol (IP), Matter will enable communication across smart home devices, mobile app and cloud services, and to define a specific set of IP-based networking technologies for device certification. Foundation for connected things: Simplicity - Easy to purchase and use Interoperability - Devices from multiple brands work natively together Reliability - Consistent and responsive local connectivity Security - Robust and streamlined for developers and users An open-source approach Members of the Alliance have taken an open-source approach to the development and implementation of this new, unified connectivity protocol. We are using best-in-class contributions from market-tested smart home technologies, such as those from Amazon, Apple, Google, the Connectivity Standards Alliance (formerly the Zigbee Alliance), and others. By leveraging these technologies' contributions, we have been able to accelerate the development of the protocol and deliver benefits to manufacturers and consumers faster. IP-Based Matter makes it easier for device manufacturers to build devices that are compatible with smart home and voice services such as Amazon's Alexa, Apple's Siri, Google's Assistant, and others. The first specification release of the Matter protocol will run on Wi-Fi and Thread network layers and will use Bluetooth Low Energy for commissioning.

Bluetooth ha crecido muchísimo en los últimos años. Parecía que cada protocolo de comunicación iba a tener nichos de uso y que las personas tendríamos que tener gateways con múltiples radios para comunicar cosas entre cosas y al internet. Hoy día Bluetooth tiene una proyección muy amplia donde poco a poco se esta comiendo muchos mercados conforme la especificación va creciendo y la capa física va mutando poco a poco. Hablamos con Miguel Reyes ingeniero de aplicaciones enfocado a comunicaciones inalámbricas y que tiene 10 años utilizando bluetooth y soportando grandes clientes que utilizan el bluetooth de maneras estándar, pero también muy locas. En este episodio Miguel nos platica un poco de la historia de bluetooth y Bluetooth Low energy. Y sirve de preámbulo para una serie de episodios relacionados con bluetooth y bluetooth low energy. Esperemos que lo disfruten Bluetooth por años ha ido ganando terreno en cuanto a los protocolos de comunicación más conocidos y utilizados por las personas. El celular sirvió como detonante para que bluetooth se comiera muchas otras aplicaciones y mas de 10 años después sigue creciendo y expandiéndose hasta llegar a localizar físicamente cosas. Miguel Reyes           Twitter          @reyesjr88

On this episode of Connect, learn about the new SimpleLink CC2652RSIP wireless system-in-package (SIP) module, a fully certified small form-factor module with integrated DC/DC components, balun and crystal oscillators. The new CC2652RSIP supports Bluetooth Low Energy, Zigbee and Thread wireless protocols to help save time, money & system designs in all applications.

In this episode of the IoT For All Podcast, Navigine CEO Alexey Panyov and CMO Elvina Sharafutdinova join us to talk all-things indoor positioning with IoT. Alexey and Elvina share their experience building an indoor positioning solution, some of the use cases they've tackled, and where the technology is going in the near future, and what use cases we can expect that will unlock.Alexey Panyov has a PhD in Physics and Math at Moscow State University and has over 15 scientific articles and more than 10 years of experience in software development. In Lomonosov Moscow State University, Alexey was engaged in various navigation projects in the defense area including the development of navigation systems for aircraft, underwater, underground moving objects, and vehicles.Elvina Sharafutdinova serves as CMO of Navigine and possesses a master's degree in economics. She's the former chairwoman of Unilever millennials board and is highly experienced in sales and project management, as well as the building and managing of sales departments.Interested in connecting with Alexey and Elvina? Reach out to Alexey on Linkedin here or Elvina here.About Navigine: Navigine is a global provider of integrated positioning technologies that enable advanced wayfinding and tracking solutions, with over 500 implementations worldwide.Key Questions and Topics from this Episode:(01:28) Introduction to Alexey Panyov and Elvina Sharafutdinova(02:29) Introduction to Navigine(03:12) Navigine Use Cases(05:08) How do the different kinds of indoor location applications differ?(06:57) What sets Navigine apart from other indoor tracking solutions?(10:56) In terms of marketing and go-to-market strategy, what did Navigine do to set itself apart in the market?(12:23) What's the current state of the indoor tracking/navigation market?(14:55) What technologies are playing the largest role in the indoor positioning space? (20:07) How do you see indoor navigation and positioning playing a role in the healthcare and logistics spaces?(23:53) What advice do you have for companies in the space and companies looking to implement indoor positioning?

Welcome to Bits, your daily tech news bulletin, for Wednesday, May 12, I'm Seamus Byrne.The federal budget happened last night, and over the past week the government pre-announced many aspects that are important to technology and digital culture industries, including the tax offset scheme for videogames and the new AI centre at the CSIRO. Unfortunately the university sector continues to be treated with disdain by the government, with almost 10% of further cuts that will see yet more jobs lost in the sector. And never forget the government's continued negligence on climate change.https://www.innovationaus.com/local-tech-gets-overlooked-by-govt-again/Intel has unveiled its 11th-generation H-Series Core processors for high-end mobile performance overnight. Codenamed Tiger Lake, the new hardware is aimed at people who want to take serious gaming or graphics processing on the go. Alongside the news, NVIDIA also unveiled its mobile edition RTX 30 Series GPUs alongside Intel's announcements, with Dell, HP, Lenovo, Gigabyte, MSI and Razer all having new high-end laptops ready to roll based on the new hardware combination.https://www.anandtech.com/show/16668/intel-launches-11th-generation-core-tiger-lakeh-eight-core-10nm-mobile-processorshttps://blogs.nvidia.com/blog/2021/05/11/geforce-rtx-studio-laptops-3050-ti/To go with your shiny new gaming laptop why not grab a shiny new VR headset? HTC is holding its ViveCon virtual event this week and revealed the new Vive Pro 2 and Vive Focus 3 headsets. The Vive Pro 2 is a big upgrade over the previous generation, with a 120-degree field of view, 120Hz refresh rate and 2448x2448 pixel resolution for each eye. The Focus 3 features similar specs but is a wireless all-in-one VR system that requires no PC and no sensors and is targeted toward business users.https://uploadvr.com/vive-pro-2-vive-focus-3/Good news for smart home technology today, with a leading interconnectivity standard getting a brand overhaul ahead of full rollout to the market. The tech is now called Matter, with a logo that will appear on supporting hardware. Matter is being supported by Apple HomeKit, Amazon Alexa, and Google Assistant standards and can run over Ethernet, Wi-Fi, Bluetooth Low Energy, or Thread networking technologies.Matter is run by an industry alliance, formerly known as Zigbee and now the Connectivity Standards Alliance, that is sponsored by Apple, Google and Amazon, the project is open source and royalty free, and market leaders like Philips are saying they can send software updates to existing products to support Matter.https://www.cnet.com/home/smart-home/amazon-google-apple-back-alliance-to-certify-smart-home-devices-that-work-together/Ebay has announced it will allow the sale of NFTs on its platform, adding yet more legitimacy to selling all manner of digital things as collectible tokens on blockchains. NFTs are typically bought and sold using cryptocurrencies, but that doesn't have to be the case, so eBay may lead to a mainstreaming of the concept. eBay has also recently said it is looking at the possibility of accepting cryptocurrencies as a payment in future.https://www.reuters.com/business/retail-consumer/ebay-taps-into-nft-frenzy-allows-sale-platform-2021-05-11/The little space probe that could, Voyager 1, keeps on delivering fascinating new insights into the great beyond, with a new report in Nature Astronomy looking at how its instruments are now detecting the constant drone of interstellar plasma waves. This is valuable insight into the nature of particles and plasma in the very-nearly-full-vacuum beyond our solar system. Launched in 1977, it is now over 22 billion kms from home and sends data back at a rate of 160-bits-per-second from its 70 kilobytes of memory.https://phys.org/news/2021-05-space-voyager-plasma.htmlIn games news, for those lucky enough to have gotten their hands on a PlayStation 5... See acast.com/privacy for privacy and opt-out information.

In episode 29, we plunge into the IoT Connected Health and Wearables universe with Adrie van Meijeren – Product Marketing Manager at Dialog Semiconductor, to examine the technology and applications sculpting the Medical and Healthcare industries!

Más de lo que nunca quisiste aprender sobre JIT, guardas y especialización https://podcast.jcea.es/python/11 En lo que sigue, cuando se habla de CPython, se refiere al intérprete de referencia de Python, que está escrito en lenguaje C: https://www.python.org/downloads/. Participantes: Eduardo Castro, email: info@ecdesign.es. Conectando desde A Guarda. Jesús Cea, email: jcea@jcea.es, twitter: @jcea, https://blog.jcea.es/, https://www.jcea.es/. Conectando desde Madrid. Javier, conectando desde Madrid. Víctor Ramírez, twitter: @virako, programador python y amante de vim, conectando desde Huelva. Miguel Sánchez, email: msanchez@uninet.edu, conectando desde Canarias. Audio editado por Pablo Gómez, twitter: @julebek. La música de la entrada y la salida es "Lightning Bugs", de Jason Shaw. Publicada en https://audionautix.com/ con licencia - Creative Commons Attribution 4.0 International License. [00:52] Aviso de que se está grabando. Temas legales. [01:52] Valor de publicar estos audios y las dificultades para hacerlo. [02:42] Métodos mágicos: __set_name__(). PEP 487: https://www.python.org/dev/peps/pep-0487/. [04:12] Problemas con PIP 20.3.2: https://github.com/pypa/pip/issues/9284. [05:52] ¿Actualizar a la última versión o esperar? Poder "echar atrás" fácil. Acumular cambios pendientes es deuda técnica. [10:42] Google caído https://www.theguardian.com/technology/2020/dec/14/google-suffers-worldwide-outage-with-gmail-youtube-and-other-services-down. [11:02] Generación de wheels en varios sistemas: https://pythonwheels.com/. auditwheel: https://pypi.org/project/auditwheel/. ¿Generación de Wheels en Microsoft Windows? [13:12] Caché local de PIP https://pip.pypa.io/en/stable/. [14:17] Event Sourcing https://dev.to/barryosull/event-sourcing-what-it-is-and-why-its-awesome. Módulo eventsourcing: https://pypi.org/project/eventsourcing/. [14:42] De momento se puede usar el viejo "resolver" de dependencias de PIP. Se puede usar la opción -use-deprecated=legacy-resolver. Esa opción se puede meter también en el fichero de configuración, para no tener que escribirlo en cada invocación. Jesús Cea comete el pecado de meter paquetes Python en el sistema operativo. [17:02] Batallitas de Jesús Cea. Jesús lleva dos años dándole vueltas a esto: bpo35930: "Raising an exception raised in a "future" instance will create reference cycles": https://bugs.python.org/issue35930. Explicación detallada del asunto. Brainstorming. [21:22] Visión a alto nivel del recolector de basuras de Python (cpython) Contador de referencias. Inmediato, pero no recoge ciclos. Si se crean instancias y no se destruyen, se llama a un recolector "pesado" que también recoge ciclos. Esto puede ser problemático al arrancar el programa, antes de que la creación/destrucción de objetos se "estabilice". gc.disable(): https://docs.python.org/3/library/gc.html#gc.disable. Jesús Cea "abusa" de los destructores y de que se ejecuten cuando él quiere. Lo práctico contra lo puro. Jesús ofrece cervezas. gc.collect(): https://docs.python.org/3/library/gc.html#gc.collect. Esto sirve tanto para recoger los ciclos como para comprobar si tu programa tiene ciclos de memoria o no. Futures: https://docs.python.org/3/library/concurrent.futures.html. [35:29] Módulo Manhole https://pypi.org/project/manhole/. Explorar un programa en producción. Tracemalloc: https://docs.python.org/3/library/tracemalloc.html. DTrace: http://dtrace.org/blogs/about/. py-spy: https://pypi.org/project/py-spy/. Pérdidas de memoria: Recordar lo hablado ya en tertulias anteriores. jemalloc: http://jemalloc.net/. MALLOC_PERTURB_: https://debarshiray.wordpress.com/2016/04/09/malloc_perturb_/. zswap: https://en.wikipedia.org/wiki/Zswap. [42:52] Micropython: https://micropython.org/. ESP8266: https://en.wikipedia.org/wiki/ESP8266. ESP32: https://en.wikipedia.org/wiki/ESP32. Bluetooth Low Energy: https://en.wikipedia.org/wiki/Bluetooth_Low_Energy. ¿Qué ventajas aporta usar Micropython? Velocidad de desarrollo y depuración. [52:42] ¿El futuro será mejor? O no. Desperdicio de recursos materiales porque realmente sobran. Python es mucho más lento que C y no digamos ensamblador. [57:17] Cambiar Python por un lenguaje más rápido. Go: https://en.wikipedia.org/wiki/Go_(programming_language). Rust: https://en.wikipedia.org/wiki/Rust_(programming_language). C++: https://en.wikipedia.org/wiki/C%2B%2B. [01:00:20] Python no pinta nada en móviles. Kivy: https://kivy.org/. [01:02:07] Acelerar Python. Subinterpreters: PEP 554: https://www.python.org/dev/peps/pep-0554/. Si los subintérpretes no compartiesen NADA, se podrían lanzar simultaneamente en varios núcleos de la CPU sin competir por un GIL https://en.wikipedia.org/wiki/Global_interpreter_lock único. JIT: https://es.wikipedia.org/wiki/Compilaci%C3%B3n_en_tiempo_de_ejecuci%C3%B3n. PYPY: https://www.pypy.org/. RPython: https://rpython.readthedocs.io/en/latest/. Numba: https://numba.pydata.org/. Cython: https://cython.org/. Python es "potencialmente" muy dinámico, pero en la práctica los programas no lo son. Jesús pone varios ejemplos. Conversación densa entre Jesús y Javier. Guardas para comprobar que la especialización sigue siendo correcta. Por ejemplo, para los diccionarios: PEP 509 Add a private version to dict: https://www.python.org/dev/peps/pep-0509/ "Tipado" más estricto. MYPY: http://mypy-lang.org/. Pydantic: https://pydantic-docs.helpmanual.io/. Comprobación de tipos en tiempo de ejecución. Descubrimiento de tipos en tiempo de ejecución, proporcionando "especialización". psyco: https://en.wikipedia.org/wiki/Psyco. Eduardo Castro entra y simplifica la discusión. Jesús explica qué hace "a+b" internamente. [01:29:22] PyParallel http://pyparallel.org/ Memoria transaccional: https://es.wikipedia.org/wiki/Memoria_transaccional. (nota de Jesús Cea): Los sistemas de persistencia Python descritos en tertulias anteriores pueden considerarse casos de memoria transaccional... si somos flexibles. "Colorear" objetos y que dos hilos no puedan acceder a objetos del mismo color simultaneamente o en transacciones concurrentes. [01:30:42] PYPY https://www.pypy.org/ es tan sofisticado que no lo entiende ni dios. Jesús Cea lo ha intentado y se ha rendido. psyco: https://en.wikipedia.org/wiki/Psyco. CFFI: https://cffi.readthedocs.io/en/latest/. [01:35:22] Compilar CPython a WebAssembly https://en.wikipedia.org/wiki/WebAssembly va más rápido que en C nativo. [01:36:02] Simplemente compilar código python con Cython https://cython.org/ sin declaración de tipos dobla la velocidad de ejecución. ¡CPython lo puede hacer mejor! [01:36:57] Subinterpreters: PEP 554: https://www.python.org/dev/peps/pep-0554/. Poder usar todos los núcleos de la CPU. [01:38:07] Seguimos hablando del asunto. [01:39:07] Un problema es que Python tiene la vocación de funcionar en todas partes, así que hay resistencia para implementar mejoras solo en ciertas plataformas. [01:40:17] Cierre. Dadle una pesada al bug bpo35930: "Raising an exception raised in a "future" instance will create reference cycles": https://bugs.python.org/issue35930. [01:41:13] Final.

Neil & Matthew play with P2P Matrix BLE

James chats with Michael Nitschinger of Couchbase to discuss Coffee Machines, PID control loops, Bluetooth Low Energy, and Databases.

James has finally discovered the magic of Bluetooth and is on an adventure of building his own app. On top of that he is investigating the wonderful world of IoT and Bluetooth combined! Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Merge Conflict: Twitter, Facebook, Website, Chat on Discord Music : Amethyst Seer - Citrine by Adventureface ⭐⭐ Review Us (https://itunes.apple.com/us/podcast/merge-conflict/id1133064277?mt=2&ls=1) ⭐⭐ Machine transcription available on http://mergeconflict.fm

James has finally discovered the magic of Bluetooth and is on an adventure of building his own app. On top of that he is investigating the wonderful world of IoT and Bluetooth combined! Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Merge Conflict: Twitter, Facebook, Website, Chat on Discord Music : Amethyst Seer - Citrine by Adventureface ⭐⭐ Review Us (https://itunes.apple.com/us/podcast/merge-conflict/id1133064277?mt=2&ls=1) ⭐⭐ Machine transcription available on http://mergeconflict.fm

Nodle, which is competing in the TechCrunch Disrupt Berlin Startup Battlefield this week, is based on a simple premise: What if you could crowdsource the connectivity of smart sensors by offloading it to smartphones? For most sensors, built-in cell connectivity is simply not a realistic option, given how much power it would take. A few years of battery life is quite realistic for a sensor that uses Bluetooth Low Energy.

Welcome to the History of Computing Podcast, where we explore the history of information technology. Because by understanding the past, we're able to be prepared for the innovations of the future! Today we're going to look at the emergence of Google's Android operating system. Before we look at Android, let's look at what led to it. Frank Canova who built a device he showed off as “Angler” at COMDEX in 1992. This would be released as the Simon Personal Communicator by BellSouth and manufactured as the IBM Simon by Mitsubishi. The Palm, Newton, Symbian, and Pocket PC, or Windows CE would come out shortly thereafter and rise in popularity over the next few years. CDMA would slowly come down in cost over the next decade. Now let's jump to 2003. At the time, you had Microsoft Windows CE, the Palm Treo was maturing and supported dual-band GSM, Handspring merged into the Palm hardware division, Symbian could be licensed but I never met a phone of theirs I liked. Like the Nokia phones looked about the same as many printer menu screens. One other device that is more relevant because of the humans behind it was the T-Mobile sidekick, which actually had a cool flippy motion to open the keyboard! Keep that Sidekick in mind for a moment. Oh and let's not forget a fantastic name. The mobile operating systems were limited. Each was proprietary. Most were menu driven and reminded us more of an iPod, released in 2001. I was a consultant at the time and remember thinking it was insane that people would pay hundreds of dollars for a phone. At the time, flip phones were all the rage. A cottage industry of applications sprung up, like Notify, that made use of app frameworks on these devices to connect my customers to their Exchange accounts so their calendars could sync wirelessly. The browsing experience wasn't great. The messaging experience wasn't great. The phones were big and clunky. And while you could write apps for the Symbian in Qt Creator or Flash Lite or Python for S60, few bothered. That's when Andy Rubin left Danger, the company the cofounded that made the Sidekick and joined up with Rich Miner, Nick Sears, and Chris White in 2003 to found a little company called Android Inc. They wanted to make better mobile devices than were currently on the market. They founded Android Inc and set out to write an operating system based on Linux that could rival anything on the market. Rubin was no noob when cofounding Danger. He had been a robotics engineer in the 80s, a manufacturing engineer at Apple for a few years and then got on his first mobility engineering gig when he bounced to General Magic to work on Magic Cap, a spinoff from Apple FROM 92 TO 95. He then helped build WebTV from 95-99. Many in business academia have noted that Android existed before Google and that's why it's as successful as it is today. But Google bought Android in 2005, years before the actual release of Android. Apple had long been rumor milling a phone, which would mean a mobile operating system as well. Android was sprinting towards a release that was somewhat Blackberry-like, focused on competing with similar devices on the market at the time, like the Blackberries that were all the rage. Obama and Hillary Clinton was all about theirs. As a consultant, I was stoked to become a Blackberry Enterprise Server reseller and used that to deploy all the things. The first iPhone was released in 2007. I think we sometimes think that along came the iPhone and Blackberries started to disappear. It took years. But the fall was fast. While the iPhone was also impactful, the Android-based devices were probably more-so. That release of the iPhone kicked Andy Rubin in the keister and he pivoted over from the Blackberry-styled keyboard to a touch screen, which changed… everything. Suddenly this weird innovation wasn't yet another frivolous expensive Apple extravagance. The logo helped grow the popularity as well, I think. Internally at Google Dan Morrill started creating what were known as Dandroids. But the bugdroid as it's known was designed by Irina Blok on the Android launch team. It was eventually licensed under Creative Commons, which resulted in lots of different variations of the logo; a sharp contrast to the control Apple puts around the usage of their own logo. The first version of the shipping Android code came along in 2008 and the first phone that really shipped with it wasn't until the HTC Dream in 2009. This device had a keyboard you could press but also had a touch screen, although we hadn't gotten a virtual keyboard yet. It shipped with an ARM11, 192MB of RAM, and 256MB of storage. But you could expand it up to 16 gigs with a microSD card. Oh, and it had a trackball. It bad 802.11b and g, Bluetooth, and shipped with Android 1.0. But it could be upgraded up to 1.6, Donut. The hacker in me just… couldn't help but mod the thing much as I couldn't help but jailbreak the iPhone back before I got too lazy not to. Of course, the Dev Phone 1 shipped soon after that didn't require you to hack it, something Apple waited until 2019 to copy. The screen was smaller than that of an iPhone. The keyboard felt kinda' junky. The app catalog was lacking. It didn't really work well in an office setting. But it was open source. It was a solid operating system and it showed promise as to the future of not-Apple in a post-Blackberry world. Note: Any time a politician uses a technology it's about 5 minutes past being dead tech. Of Blackberry, iOS, and Android, Android was last in devices sold using those platforms in 2009, although the G1 as the Dream was also known as, took 9% market share quickly. But then came Eclair. Unlike sophomore efforts from bands, there's something about a 2.0 release of software. By the end of 2010 there were more Androids than iOS devices. 2011 showed the peak year of Blackberry sales, with over 50 million being sold, but those were the lagerts spinning out of the buying tornado and buying the pivot the R&D for the fruitless next few Blackberry releases. Blackberry marketshare would zero out in just 6 short years. iPhone continued a nice climb over the past 8 years. But Android sales are now in the billions per year. Ultimately the blackberry, to quote Time a “failure to keep up with Apple and Google was a consequence of errors in its strategy and vision.” If you had to net-net that, touch vs menus was a substantial part of that. By 2017 the Android and iOS marketshare was a combined 99.6%. In 2013, now Google CEO, Sundar Pichai took on Android when Andy Rubin was embroiled in sexual harassment charges and now acts as CEO of Playground Global, an incubator for hardware startups. The open source nature of Android and it being ready to fit into a device from manufacturers like HTC led to advancements that inspired and were inspired by the iPhone leading us to the state we're in today. Let's look at the released per year and per innovation: * 1.0, API 1, 2008: Include early Google apps like Gmail, Maps, Calendar, of course a web browser, a media player, and YouTube * 1.1 came in February the next year and was code named Petit Four * 1.5 Cupcake, 2009: Gave us on an-screen keyboard and third-party widgets then apps on the Android Market, now known as the Google Play Store. Thus came the HTC Dream. Open source everything. * 1.6 Donut, 2009: Customizeable screen sizes and resolution, CDMA support. And the short-lived Dell Streak! Because of this resolution we got the joy of learning all about the tablet. Oh, and Universal Search and more emphasis on battery usage! * 2.0 Eclair, 2009: The advent of the Motorola Droid, turn by turn navigation, real time traffic, live wallpapers, speech to text. But the pinch to zoom from iOS sparked a war with Apple.We also got the ability to limit accounts. Oh, new camera modes that would have impressed even George Eastman, and Bluetooth 2.1 support. * 2.2 Froyo, four months later in 2010 came Froyo, with under-the-hood tuning, voice actions, Flash support, something Apple has never had. And here came the HTC Incredible S as well as one of the most mobile devices ever built: The Samsung Galaxy S2. This was also the first hotspot option and we got 3G and better LCDs. That whole tethering, it took a year for iPhone to copy that. * 2.3 Gingerbread: With 2010 came Gingerbread. The green from the robot came into the Gingerbread with the black and green motif moving front and center. More sensors, NFC, a new download manager, copy and paste got better, * 3.0 Honeycomb, 2011. The most important thing was when Matias Duarte showed up and reinvented the Android UI. The holographic design traded out the green and blue and gave you more screen space. This kicked off a permanet overhaul and brought a card-UI for recent apps. Enter the Galaxy S9 and the Huawei Mate 2. * 4.0 Ice Cream Sandwich, later in 2011 - Duarte's designs started really taking hold. For starters, let's get rid of buttons. THat's important and has been a critical change for other devices as well. We Reunited tablets and phones with a single vision. On screen buttons, brought the card-like appearance into app switching. Smarter swiping, added swiping to dismiss, which changed everything for how we handle email and texts with gestures. You can thank this design for Tinder. * 4.1 to 4.3 Jelly Bean, 2012: Added some sweet sweet fine tuning to the foundational elements from Ice Cream Sandwich. Google Now that was supposed to give us predictive intelligence, interactive notifications, expanded voice search, advanced search, sill with the card-based everything now for results. We also got multiuser support for tablets. And the Android Quick Settings pane. We also got widgets on the lock screen - but those are a privacy nightmare and didn't last for long. Automatic widget resizing, wireless display projection support, restrict profiles on multiple user accounts, making it a great parent device. Enter the Nexus 10. AND TWO FINGER DOWN SWIPES. * 4.4 KitKat, in 2013 ended the era of a dark screen, lighter screens and neutral highlights moved in. I mean, Matrix was way before that after all. OK, Google showed up. Furthering the competition with Apple and Siri. Hands-free activation. A panel on the home screen, and a stand-alone launcher. AND EMOJIS ON THE KEYBOARD. Increased NFC security. * 5. Lollipop came in 2014 bringing 64 bit, Bluetooth Low Energy, flatter interface, But more importantly, we got annual releases like iOS. * 6: Marshmallow, 2015 gave us doze mode, sticking it to iPhone by even more battery saving features. App security and prompts to grant apps access to resources like the camera and phone were . The Nexus 5x and 6P ports brought fingerprint scanners and USB-C. * 7: Nougat in 2016 gave us quick app switching, a different lock screen and home screen wallpaper, split-screen multitasking, and gender/race-centric emojis. * 8: Oreo in 2017 gave us floating video windows, which got kinda' cool once app makers started adding support in their apps for it. We also got a new file browser, which came to iOS in 2019. And more battery enhancements with prettied up battery menus. Oh, and notification dots on app icons, borrowed from Apple. * 9: Pie in 2018 brought notch support, navigations that were similar to those from the iPhone X adopting to a soon-to-be bezel-free world. And of course, the battery continues to improve. This brings us into the world of the Pixel 3. * 10, Likely some timed in 2019 While the initial release of Android shipped with the Linux 2.1 kernel, that has been updated as appropriate over the years with, 3 in Ice Cream Sandwich, and version 4 in Nougat. Every release of android tends to have an increment in the Linux kernel. Now, Android is open source. So how does Google make money? Let's start with what Google does best. Advertising. Google makes a few cents every time you click on an ad in an advertisement in messages or web pages or any other little spot they've managed to drop an ad in there. Then there's the Google Play Store. Apple makes 70% more revenue from apps than Android, despite the fact that Android apps have twice the number of installs. The old adage is if you don't pay for a product, you are the product. I don't tend to think Google goes overboard with all that, though. And Google is probably keeping Caterpillar in business just to buy big enough equipment to move their gold bars from one building to the next on campus. Any time someone's making money, lots of other people wanna taste. Like Oracle, who owns a lot of open source components used in Android. And the competition between iOS and Android makes both products better for consumers! Now look out for Android Auto, Android Things, Android TV, Chrome OS, the Google Assistant and others - given that other types of vendors can make use of Google's open source offerings to cut R&D costs and get to market faster! But more importantly, Android has contributed substantially to the rise of ubiquitious computing despite how much money you have. I like to think the long-term impact of such a democratization of Mobility and the Internet will make the world a little less idiocracy and a little more wikipedia. Thank you so very much for tuning into another episode of the History of Computing Podcast. We're lucky to have you. Have a great day!

As part of its expanded anti-phishing and account security measures, Google offers extensive support for physical authentication tokens. In a surprising setback, though, the company announced today that it has discovered a vulnerability in the Bluetooth version of its own Titan Security Key—which pairs to devices through the wireless Bluetooth Low Energy protocol, rather than through NFC or physical insertion into a port.

Tracy Lee: @ladyleet | ladyleet.com Ben Lesh: @benlesh | medium.com/@benlesh Show Notes: 00:50 - What is This Dot? 03:26 - The RxJS 5.5.4 Release and Characterizing RxJS 05:14 - Observable 07:06 - Operators 09:52 - Learning RxJS 11:10 - Making RxJS Functional Programming Friendly 12:52 - Lettable Operators 15:14 - Pipeline Operators 21:33 - The Concept of Mappable 23:58 - Struggles While Learning RxJS 33:09 - Documentation 36:52 - Surprising Uses of Observables 40:27 - Weird Uses of RxJS 45:25 - Announcements: WHATWG to Include Observables and RxJS 6 Resources: this.media RxJS RX Workshop Ben Lesh: Hot vs Cold Observables learnrxjs.io RxMarbles Jewelbots Transcript: CHARLES: Hello everybody and welcome to The Frontside Podcast, Episode 91. My name is Charles Lowell, a developer here at The Frontside and your podcast host-in-training. Joining me today on the podcast is Elrick Ryan. Hello, Elrick. ELRICK: Hey, what's up? CHARLES: Not much. How are you doing? ELRICK: I'm great. Very excited to have these two folks on the podcast today. I feel like I know them… CHARLES: [Laughs] ELRICK: Very well, from Twitter. CHARLES: I feel like I know them well from Twitter, too. ELRICK: [Laughs] CHARLES: But I also feel like this is a fantastic company that is doing a lot of great stuff. ELRICK: Yup. CHARLES: Also not in Twitter. It should be pointed out. We have with us Tracy Lee and Ben Lesh from This Dot company. TRACY: Hey. CHARLES: So first of all, why don't we start, for those who don't know, what exactly is This Dot? What is it that you all do and what are you hoping to accomplish? TRACY: This Dot was created about a year ago. And it was founded by myself and Taras who work on it full-time. And we have amazing people like Ben, who's also one of our co-founders, and really amazing mentors. A lot of our friends, when they refer to what we actually do, they like to call it celebrity consulting. [Laughter] TRACY: Which I think is hilarious. But it's basically core contributors of different frameworks and libraries who work with us and lend their time to mentor and consult with different companies. So, I think the beautiful part about what we're trying to do is bring together the web. And we sort of do that as well not only through consulting and trying to help people succeed, but also through This Dot Media where it's basically a big playground of JavaScripting all the things. Ben and I do Modern Web podcast together. We do RX Workshop which is RxJS training together. And Ben also has a full-time job at Google. CHARLES: What do they got you doing over there at Google? BEN: Well, I work on a project called Alkali which is an internal platform as a service built on top of Angular. That's my day job. CHARLES: So, you've been actually involved in all the major front-end frameworks, right, at some point? BEN: Yeah, yes. I got my start with Angular 1 or AngularJS now, when I was working as a web developer in Pittsburgh, Pennsylvania at a company called Aesynt which was formerly McKesson Automation. And then I was noticed by Netflix who was starting to do some Angular 1 work and they hired me to come help them. And then they decided to do Ember which is fine. And I worked on a large Ember app there. Then I worked on a couple of large React apps at Netflix. And now I'm at Google building Angular apps. CHARLES: Alright. BEN: Which is Angular 5 now, I believe. CHARLES: So, you've come the full circle. BEN: Yeah. Yeah, definitely. CHARLES: [Chuckles] I have to imagine Angular's changed a lot since you were working on it the first time. BEN: Yeah. It was completely rewritten. TRACY: I feel like Angular's the new Ember. CHARLES: Angular is the new Ember? TRACY: [Laughs] BEN: You think? TRACY: Angular is the new Ember and Vue is the new AngularJS, is basically. [Laughs] CHARLES: Okay. [Laughter] CHARLES: What's the new React then? BEN: Preact would be the React. CHARLES: Preact? Okay, or is Glimmer… BEN: [Laughs] I'm just… CHARLES: Is Glimmer the new React? BEN: Oh, sure. [Laughs] CHARLES: It's important to keep these things straight in your head. BEN: Yeah, yeah. CHARLES: Saves on confusion. TRACY: Which came first? [Chuckles] BEN: Too late. I'm already confused. CHARLES: So now, before the show you were saying that you had just, literally just released RxJS, was it 5.5.4? BEN: That's right. That's right. The patch release, yeah. CHARLES: Okay. Am I also correct in understanding that RxJS has kind of come to very front and center position in Angular? Like they've built large portions of framework around it? BEN: Yeah, it's the only dependency for Angular. It is being used in a lot of official space for Angular. For example, Angular Material's Data Table uses observables which are coming from RxJS. They've got reactive forms. The router makes use of Observable. So, the integration started kind of small which HTTPClient being written around Observable. And it's grown from there as people seem to be grabbing on and enjoying more the React programming side of things. So, it's definitely the one framework that's really embraced reactive programming outside of say, Cycle.js or something like that. CHARLES: Mmhmm. So, just to give a general background, how would you characterize RxJS? BEN: It's a library built around Observable. And Observable is a push-based primitive that gives you sets of events, really. CHARLES: Mmhmm. BEN: So, that's like Lodash for events would be a good way to put it. You can take anything that you can get pushed at you, which is pretty much value type you can imagine, and wrap it in an observable and have it pushed out of the observable. And from there, you have a set of things that you can combine. And you can concatenate them, you can filter them, you can transform them, you can combine them with other sets, and so on. So, you've got this ability to query and manipulate in a declarative way, events. CHARLES: Now, Observable is also… So, when Jay was on the podcast we were talking about Redux observable. But there was outside of the context of RxJS, it was just observables were this standalone entity. But I understand that they actually came from the RxJS project. That was the progenitor of observables even though there's talk of maybe making them part of the JavaScript spec. BEN: Yeah, that's right. That's right. So, RxJS as it stands is a reference implementation for what could land in JavaScript or what could even land in the DOM as far as an observable type. Observable itself is very primitive but RxJS has a lot of operators and optimizations and things written around Observable. That's the entire purpose of the library. CHARLES: Mmhmm. So, what kind of value-adds does it provide on top of Observable? If Observable was the primitive, what are the combinators, so to speak? BEN: Oh, right. So, similar to what Lodash would add on top of say, an iterable or arrays, you would have the same sorts of things and more inside of RxJS. So, you've got zip which you would maybe have seen in Lodash or different means of combines. Of course, map and ‘merge map' which is like a flattening sort of operation. You can concatenate them together. But you also have these time-based things. You can do debouncing or throttling of events as they're coming over in observable and you create a new observable of that. So, the value-add is the ability to compose these primitive actions. You can take on an observable and make a new observable. We call it operators. And you can use those operators to build pretty much anything you can imagine as far as an app would go. CHARLES: So, do you find that most of the time all of the operators are contained right there inside RxJS? Or if you're going to be doing reactive programming, one of your tasks is going to be defining your own operators? BEN: No, pretty much everything you'd need will be defined within RxJS. There's 60 operators or so. CHARLES: Whoa, that's a lot. BEN: It's unlikely that someone's going to come up with one. And in fact, I would say the majority of those, probably 75% of those, you can create from the other 25%. So, some of the much more primitive operators could be used… TRACY: Which is sort of what Ben did in this last release, RxJS 5…. I don't know remember when you introduced the lettable operators but you… BEN: Yeah, 5.5. TRACY: Implemented [inaudible] operators. BEN: Yeah, so a good portion of them I started implementing in terms of other operators. CHARLES: Right. So, what was that? I didn't quite catch that, Tracy. You said that, what was the operator that was introduced? TRACY: So, in one of the latest releases of RxJS, one of the more significant releases where pipeable operators were introduced, what Ben did was he went ahead and implemented a lot of operators that were currently in the library in terms of other operators, which was able to give way to reduce the size of the library from, I think it was what, 30KB bundled, gzipped, and minified, to about 30KB, which was about 60 to 70% of the operators. Right, Ben? BEN: Yeah. So, the size reduction was in part that there's a lot of factors that went into the size reduction. It would be kind of hard to pin it down to a specific operator. But I know that some of the operators like the individual operators themselves, by reimplementing reduce which is the same as doing as scan and then take last, implementing it in terms of that is going to reduce the size of it probably 90% of that one particular file. So, there's a variety of things like that that have already started and that we're going to continue to do. We didn't do it with every operator that we could have. Some operators are very, very common and consequently we want them to be as optimized as possible. For example, map. You can implement map in terms of ‘merge map' but it would be very slow to do so. It might be smaller but it would be slower. We don't want that. So, there are certain areas we're always going to try to keep fairly a hot path to optimize them as much as possible. But in other spots like reduce which is less common and isn't usually considered to be a performance bottleneck, we can cut some corners. Or ‘to array' or other things like that. CHARLES: Mmhmm. TRACY: And I think another really interesting thing is a lot of people when learning RxJS, they… it's funny because we just gave an RX Workshop course this past weekend and the people that were there just were like, “Oh, we've heard of RxJS. We think it's a cool new thing. We have no plans to implement it in real life but let's just play around with it and let me learn it.” I think as people are starting to learn RxJS, one of the things that gets them really overwhelmed is this whole idea that they're having to learn a completely new language on top of JavaScript or what operators to use. And one of our friends, Brian Troncone who is on the Learning Team, the RxJS Learning Team, he pulled up the top 15 operators that were most commonly searched on his site. And some of them were ‘switch map', ‘merge map', ‘fork join', merge, et cetera. So, you can sort of tell that even though the library has quite a few… it's funny because Ben, I think the last RX Workshop you were using pairs and you had never used it before. BEN: Yeah. TRACY: So, it's always amusing for me how many people can be on the core team but have never implemented RxJS… CHARLES: [Laughs] TRACY: A certain way. BEN: Right. Right, right, right. CHARLES: You had said one of the recent releases was about making it more friendly for functional programming. Is that a subject that we can explore? Because using observables is already pretty FP-like. BEN: What it was before is we had dot chaining. So, you would do ‘dot map' and then call a method and then you get an observable back. And then you'd say ‘dot merge' and then you'd call a method on that, and so on and so forth. Now what you have is kind of a Ramda JS style pipe function that just takes a comma-separated list of other functions that are going to act upon the observable. So, it reads pretty much the same with a little more ceremony around it I guess. But the upside is that you can develop your operators as just higher-order functions. CHARLES: Right. And you don't have to do any monkey-patching of prototypes. BEN: Exactly, exactly. CHARLES: Because actually, okay, I see. This is actually pretty exciting, I think. Because we actually ran into this problem when we were using Redux Observable where we wanted to use some operators that were used by some library but we had to basically make a pull request upstream, or fork the upstream library to include the operators so that we could use them in our application. It was really weird. BEN: Yeah. CHARLES: The reason was because it was extending the observable prototype. BEN: Yeah. And there's so many… and that's one way to add that, is you extend the observable prototype and then you override lift so you return the same type of observable everywhere. And there are so many things that lettable operators solved for us. For example… CHARLES: So, lettable operators. So, that's the word that Tracy used and you just used it. What are lettable operators? BEN: Well, I've been trying to say pipeable and get that going instead of lettable. But basically there's an operator on RxJS that's been there forever called let. And let is an operator and what you do is you give it a function. And the function gives you the source observable and you're expected to return a new observable. And the idea is that you can then write a function elsewhere that you can then compose in as though it were an operator, anywhere you want, along with your other dot-chained operators. And the realization I had a few months ago was, “Well, why don't we just make all operators like this?” And then we can use functional programming to compose them with like a reduce or whatever. And that's exactly what the lettable operators are. And that's why I started calling them lettable operators. And I kind of regret it now, because so many people are saying it and it confuses new people. Because what in the world does lettable even mean? CHARLES: Right. [Laughs] BEN: So, they are pipeable operators or functional operators. But the point is that you have a higher-order function that returns a function of a specific shape. And that function shape is, it's a function that receives an observable and returns an observable, and that's it. So, basically it's a function that transforms an observable into a new observable. That's all an operator. That's all an operator's ever been. It's just this is in a different flavor. CHARLES: Now, I'm curious. Why does it do an observable into an observable and not a stream item into an observable? Because when you're actually chaining these things together, like with a map or with a ‘flat map' or all these things, you're actually getting an individual item and then returning an observable. Well, I guess in this case of a map you're getting an item and returning an item. But like… BEN: Right, but that's not what the entire operation is. So, you've got an operation you're performing whenever you say, if you're to just even dot-chain it, you'd say ‘observable dot map'. And when you say ‘dot map', it returns a new observable. And then you say ‘dot filter' and it returns another new observable. CHARLES: Oh, gotcha, gotcha, gotcha. Okay, yeah, yeah, yeah. Yeah, yeah. BEN: So, this function just embodies that step. CHARLES: I see, I see. And isn't there some special… I feel like there's some proposal for some special JavaScript syntax to make this type of chaining? BEN: Yeah, yeah, the pipeline operator. CHARLES: Okay. BEN: I don't know. I think that's still at stage one. I don't know that it's got a lot of headway. My sources and friends that are in the TC39 seem to think that it doesn't have a lot of headway. But I really think it's important. Because if you look at… the problem is we're using a language where the most common use case is you have to build it, get the size as small as possible because you need to send it over the wire to the browser. And understandably, browsers don't want to implement every possible method they could on say, Array, right? CHARLES: Mmhmm, right. BEN: There's a proposal in for ‘flat map'. They could add zip to Array. They could add all sorts of interesting things to Array just by itself. And that's why Lodash exists, right? CHARLES: Right. BEN: Is because not everything is on Array. And then so, the onus is then put on the community to come up with these solutions and the community has to build libraries that have these constraints in size. And what stinks about that is then you have say, an older version of Lodash where you'd be like, “Okay, well it has 36 different functions in it and I'm only using 3 of them. And I have to ship them all to the browser.” CHARLES: Mmhmm. BEN: And that's not what you want. So, then we have these other solutions around tree-shaking and this and that. And the real thing is what you want is you want to be able to compose things left to right and you want to be able to have these functions that you can use on a particular type in an ad hoc way. And there's been two proposals to try to address this. One was the ‘function bind' operator, CHARLES: Mmhmm. BEN: Which is colon colon. And what that did is it said, “You can use this function as a method, as though it were a method on an object. And we'll make sure that the ‘this' inside that function comes from the instance that's on the left-hand side of colon colon.” CHARLES: Right. BEN: That had a bunch of other problems. Like there's some real debate I guess on how they would tie that down to a specific type. So, that kind of fell dead in the water even though it had made some traction. And then the pipeline operator is different. And then what it says is, “Okay, whatever is on the…” And what it looks like is a pipe and a greater than right next to each other. And whatever's on the left-hand side of that operand gets passed as the first argument to the function on the right-hand side of that operand. CHARLES: Mmhmm. BEN: And so, what that means is for the pipeable operators, instead of having to use a pipe method on observable, you can just say, “instance of observable, pipeline operator and an operator, and then pipeline operator, and then the Rx operator, and then pipeline operator and the Rx operator, and so on.” And it would just be built-in. And the reason I think that JavaScript really needs it is that means that libraries like Lodash can be written in terms of simple functions and shipped piece-meal to the browser exactly as you need them. And people would just use the pipeline operator to use them, instead of having to wrap something in a big object so you can dot-chain things together or come up with your own functional pipe thing like RxJS had to. CHARLES: Right. Because it seems it happens again and again, right? Lodash, RxJS, jQuery. You just see this pattern of chaining, which is, you know… BEN: Yeah, yeah. People want chaining. People want left to right composition. CHARLES: Mmhmm. BEN: And it's problematic in a world where you want to shake off as much unused garbage as possible. And the only way to get dot chaining is by augmenting a prototype. There's all sorts of weird problems that can come with that. And so, the functional programming approach is one method. But then people look at it and they say, “Ooh, yuck. I've got to wrap things in a function named pipe. Wouldn't it be nicer if there was just some syntax to do this?” And yeah, it would be nicer. But I have less control over that. CHARLES: Right. But the other alternative is to have right to left function composition. BEN: Right, yeah. CHARLES: But there's not any special syntax for that, either. BEN: Not very readable. CHARLES: Yeah. BEN: So, you just wrap everything. And the innermost call is the first one and then you wrap it in another function and you wrap that in another function, and so on. Yeah, that's not [inaudible]. But I will say that the pipe function itself is pretty simple. It's basically a function that takes a rest of arguments that are all functions. CHARLES: Mmhmm. BEN: And so, you have this array of functions and you just reduce over it and call them. Well, you return a function. So, it's a higher function. You return a function that takes an argument then you reduce over the functions that came in as arguments and you call each one of them with whatever result was from the previous. CHARLES: Right. Like Tracy mentioned in the pre-show, I'm an aspiring student of functional programming. So, would this be kind of like a monoid here where you're mashing all these functions together? Is your empty value? I'm just going to throw it out there. I don't know if it's true or not, but that's my conjecture. BEN: Yes. Technically, it's a monoid because it wouldn't work unless it was a monoid. Because monoids, I believe the category theory I think for monoid is that monoids can be concatenated because they definitely have an end. CHARLES: Right. BEN: So, you would not be able to reduce over all those functions and build something with that, like that, unless it was a monoid. So yeah, the fact that there's reduction involved is a cue that it's a monoid. CHARLES: Woohoo! Alright. [Laughter] CHARLES: Have you found yourself wanting to apply some of these more “rigorous” formalisms that you find out there in the development of RxJS or is that just really a secondary concern? BEN: It's a secondary concern. It's not something that I like. It's something I think about from time to time, when really, debating any kind of heavy issue, sometimes it's helpful. But when it comes to teaching anybody anything, honestly the Haskell-isms and category theory names, all they do is just confuse people. And if you tell somebody something is a functor, they're like, “What?” And if you just say it's mappable, they're like, “Oh, okay. I can map that.” CHARLES: [Laughs] Right, right. BEN: And then the purists would be like, “But they're not the same thing.” And I would be like, “But the world doesn't care. I'm sorry.” CHARLES: Yeah, yeah. I'm kind of experiencing this debate myself. I'm not quite sure which side I fall on, because on the one hand it is arbitrary. Functor is a weird name. But I wish the concept of mappable existed. It does, but I feel like it would be handy if people… because there's literally five things that are super handy, right? Like mappable, if we could have a name for monoid. But it's like, really, you just need to think in terms of these five constructs for 99% of the stuff that you do. And so, I always wonder, where does that line lie? And how… mappable, is that really more accessible than functor? Or is that only because I was exposed to the concept of mapping for 10 years before I ever heard the F word. BEN: Yes, and yes. I mean, that's… CHARLES: [Laughs] BEN: Things that are more accessible are usually more accessible because of some pre-given knowledge, right? What works in JavaScript probably isn't going to work in Haskell or Scala or something, right? CHARLES: Mmhmm. BEN: If someone's a Java developer, certain idioms might not make sense to them that come from the JavaScript world. CHARLES: Right. But if I was learning like a student, I would think mappable, I'd be thinking like, I would literally be thinking like Google Maps or something like that. I don't know. BEN: Right, right. I mean, look at C#. C#, a mapping function is always going to be called select, right, because that's C#. That's their idiom for the same thing. CHARLES: Select? BEN: Yeah. CHARLES: Really? BEN: Yeah, select. So, they'll… CHARLES: Which in Ruby is like find. BEN: Yeah. there's select and then, what's the other one, ‘select many' or something like that. [Chuckles] BEN: So, that's C#. CHARLES: Oh, like it's select from SQL. Okay. BEN: Yeah, I think that's kind of where it came from because people had link and then they had link to SQL and then they're like, well I want to do this with regular code, with just using some more… less nuanced expressions. So, I want to be able to do method calls and chain those together. And so, you end up with select functions. And I think that that exists even in Rx.NET, although I haven't used Rx.NET. CHARLES: Hmm, okay. ELRICK: So, I know you do a lot of training with Rx. What are some of the concepts that people struggle with initially? TRACY: I think when we're teaching RX Workshop, a lot of the people sort of… I'll even see senior level people struggle with explaining it, is the difference between observables and observers and then wrapping their head around the idea that, “Hey, observables are just functions in JavaScript.” So, they're always thinking observables are going to do something for you. Actually, it's not just in Angular but also in React, but whenever someone's having issues with their Rx applications, it's usually something that they're like nesting observables or they're not subscribing to something or they've sort of hot-messed themselves into a tangle. And I'm sure you've debugged a bunch of this stuff before. The first thing I always ask people is, “Have you subscribed?” Or maybe they're using an Angular… they're using pipes async but they're also calling ‘dot subscribe' on their observable. BEN: Yeah. So, like in Angular they'll do both. Yeah. There's that. I think that, yeah, that relates to the problem of people not understanding that observables are really just functions. I keep saying that over and over again and people really don't seem to take it to heart for whatever reason. [Chuckles] BEN: But you get an observable and when you're chaining all those operators together, you're making another observable or whatever, observables don't do anything until you subscribe to them. They do nothing. CHARLES: Shouldn't they be called like subscribable? BEN: Yes. [Chuckles] BEN: They probably should. But we do hand them an observer. So, you are observing something. But the point being is that they don't do anything at all until you subscribe to them. And in that regard, they're like functions, where functions don't do anything unless you call them. So, what ends up happening with an observable is you subscribe to it. You give it an observer, three callbacks which are then coerced into an observer. And it takes that observer and it hands it to the body of this observable definition and literally has an observer inside of there. And then you basically execute that function synchronously and do things, whatever those things are, to set up some sort of observation. Maybe you spin up a WebSocket and tie into some events on it and call next on the observer to get values out of your observable. The point being that if you subscribe to an observable twice, it's the same thing as calling a function twice. And for some reason, people have a hard time with that. They think, if I subscribe to the observable twice, I've only called the function once. CHARLES: I experienced this confusion. And I remember the first time that that… like, I was playing with observables and the first time I actually discovered that, that it was actually calling my… now what do you call the function that you pass to the constructor that actually does, that calls next or that gets passed the observer? TRACY: [Inaudible] BEN: I like to call it an initialization function or something. But the official name from the TC39 proposal is subscriber function. CHARLES: Subscriber function. So, like… BEN: Yeah. CHARLES: I definitely remember it was one of those [makes explosion sound] mind-blowing moments when I realized when I call my subscribe method, the entire observable got run from the very beginning. But my intuition was that this is an object. It's got some shared state, like it's this quasar that I'm now observing and I'm seeing the flashes of light coming off of it. But it's still the same object. You think of it as having yeah, not as a function. Okay. No one ever described it to me as just a function. But I think I can see it now. ELRICK: Yeah, me neither. CHARLES: But yeah, you think of it in the same way that most people think of objects, as like, “I have this object. I have a reference to it.” Let observable equal new observable. It's a single thing. It's a single identity. And so, that's the thing that I'm observing. It's not that I'm invoking this observable to observe things. And I think that's, yeah, that's a subtle nuance there. I wish I had taken y'all's course, I guess is what I'm saying. ELRICK: Yeah. BEN: Yeah. Well, I've done a few talks on it. CHARLES: [Laughs] BEN: I always try to tell people, “It's just a function. It's just a function.” I think what happens to a lot of people too is there's the fact that it's an object. But I think what it is, is people's familiarity with promises does this. Because promises are always multicast. They are always “hot”. And the reason for this is because they're eager. So, by the time you have a promise, whatever is producing value to the promise has already started. And that means that they're inherently a multicast. CHARLES: Right. BEN: So, people are used to that behavior of, I can ‘then' off of this promise and it always means one thing. And it's like, yeah, because the one thing has nothing to do with the promise. It wasn't [Chuckles] CHARLES: Right. BEN: This promise is just an interface for you to view something that happened in the past, where an observable is more low-level than that and more simple than that. It just states, “I'm a function that you call. I'm going to be able to do anything a function can do. And by the way, you're giving me an observer and I'm going to do some stuff with that too and notify you via this observer that you handed me.” Because of that you could take an observable and close over something that had already started. Say you had a WebSocket that was already running. You could create a new observable and just like any function, close over that, externally create a WebSocket. And then everyone that subscribes to that observable is tying an observer to that same WebSocket. Then you're multicast. Then you're “hot”. ELRICK: [Inaudible] CHARLES: Right. So, I was going to say that's the distinction that Jay was talking about. He was talking about we're going to just talk about… he said at the very beginning, “We're just going to talk about hot observable.” ELRICK: Yup. CHARLES: But even a hot observable is still theoretically evaluating every single time you subscribe. You're getting a new observable. You're evaluating that observable afresh each time. It just so happens that in the lexical scope of that observable subscriber function, there is this WebSocket? BEN: Yeah. So, it's the same thing. Imagine you wrote a function that when you called it created a new WebSocket and then… say, you wrote a new function that you gave an observer object to, right? An observer object has next, error, and complete. And in that function, when you called it, it created a new WebSocket and then it tied the ‘on message' and ‘on close' and whatever to your observer's next method and your observer's error message and so on. When you call that function, you would expect a new WebSocket to be created every single time. Now, let's just say alternately you create a WebSocket and then you write a new function that that function closes over that WebSocket. So, you reference the WebSocket that you externally created inside of your function. When you call that function, it's not going to create a new WebSocket every time. It's just closing over it, right? So, even though they both are basically doing the same thing, now the latter one of those two things is basically a hot observable and the former is a cold observable. Because one is multicast which is, “I'm sharing this one WebSocket with everybody,” and the other one is unicast which is, “I am going to create a new WebSocket for each person that calls me.” And that's the [inaudible] people have a hard time with. CHARLES: Right. But really, it's just a matter of scope. BEN: Yeah. The thing people have a hard time with, with observables, is not realizing that they're actually just functions. CHARLES: Yeah. I just think that maybe… see, when I hear things like multicast and unicast, that makes me think of shared state, whereas when you say it's just a matter of scope, well then I'm thinking more in terms of it being just a function. It just happens that this WebSocket was already [scoped]. BEN: Well, shared state is a matter of scope, right? CHARLES: Yes, it is. It is. Oh, sorry. Shared state associated with some object identity, right? BEN: Right. CHARLES: But again, again, it's just preconceptions, really. It's just me thinking that I've had to manage lists of listeners and have multicast observers and single-cast observers and having to manage those lists and call notify on all of them. And that's really not what's happening at all. BEN: Yeah. Well, I guess the real point is observables can have shared state or they could not have shared state. I think the most common version and the most composable version of them, they do not have any shared state. It's just one of those things where just like a function can have shared state or it could be pure, right? There's nothing wrong with either one of those two uses of a function. And there's nothing wrong with either one of those two uses of Observable. So, honest to god, that is the biggest stumbling block I think that I see people have. That and if I had to characterize it I would say fear and loathing over the number of operators. People are like… CHARLES: [Chuckles] BEN: And they really think because everyone's used to dealing with these frameworks where there's an idiomatic way to do everything, they think there's going to be an RxJS idiomatic way to do things. And that's just patently false. That's like saying there's an idiomatic way to use functions. There's not. Use it however it works. The end. It's not… CHARLES: Mmhmm, mmhmm. BEN: You don't have to use every operator in a specific way. You can use it however works for you and it's fine. ELRICK: I see that you guys are doing some fantastic work with your documentation. Was that part of RxJS 2.0 docs? TRACY: I was trying to inspire people to take on the docs initiative because I think when I was starting to learn RxJS I would get really frustrated with the docs. BEN: Yeah. TRACY: I think the docs are greatly documented but at the same time if you're not a senior developer who understands Rx already, then it's not really helpful. Because it provides more of a reference point that the guys can go back and look at, or girls. So anyways, after many attempts of trying to get somebody to lead the project I just decided to lead the project myself. [Laughter] TRACY: And try to get… the community is interesting because I think because the docs can be sometimes confusing… Brian Troncone created LearnRxJS.io. There's these other visualization projects like RxMarbles, RxViz, et cetera. And we just needed to stick everybody together. So, it's been a project that I think has been going on for the past two months or so. We have… it's just an Angular app so it's probably one of the most easiest projects to contribute to. I remember the first time I tried to contribute to the Ember docs. It literally took me an hour to sit there with a learning team, Ember Learning Team member and… actually, maybe it was two hours, just to figure out how the heck… like all the things I had to download to get my environment set up so that I could actually even contribute to the darn documentation. But with the Rx, the current RxJS docs right now is just an Angular app. You can pull it down. It's really easy. We even have people who are just working on accessibility, which is super cool, right? So, it's a very friendly place for beginners. BEN: I'm super pleased with all the people that have been working on that. Brian and everybody, especially on the accessibility front. Jen Luker [inaudible] came in and voluntarily… she's like the stopgap for all accessibility to make sure everything is accessible before we release. So, that's pretty exciting. TRACY: Yeah. ELRICK: Mmhmm. TRACY: So funny because when me and Jen started talking, she was talking about something and then I was like, “Oh my god, I'm so excited about the docs.” She's like, “I'm so excited, too! But I don't really know why I'm excited. But you're excited, so I'm excited. Why are you excited?” [Laughter] TRACY: I was like, “I don't know. But I'm excited, too!” [Chuckles] TRACY: And then all of a sudden we have accessibility. [Laughs] ELRICK: Mmhmm. Yeah, I saw some amazing screenshots. Has the new docs, have they been pushed up to the URL yet? TRACY: Nah, they are about to. We were… we want to do one more accessibility run-through before we publish it. And then we're going to document. We want to document the top 15 most viewed operators. But we should probably see that in the next two weeks or so, that the new docs will be… I mean, it'll say “Beta, beta, beta” all over everything. But actually also, some of our friends, [Dmitri] from [Valas] Software, he is working on the translation portion to make it really easy for people to translate the docs. CHARLES: Ah. TRACY: So, a lot of that came from the inspiration from the Vue.js docs. we're taking the versioning examples that Ember has done with their docs as inspiration to make sure that our versioning is really great. So, it's great that we can lend upon all the other amazing ideas in the industry. ELRICK: Oh, yeah. CHARLES: Yeah, it's fantastic. I can't wait to see them. ELRICK: Yeah, me neither. The screenshots look amazing. I was like, “Wow. These are some fabulous documentation that's going to be coming out.” I can't wait. TRACY: Yeah. Thank you. CHARLES: Setting the bar. ELRICK: Really high. [Laughter] CHARLES: Actually, I'm curious. Because observables are so low-level, is there some use of them that… what's the use of them that you found most surprising? Or, “Whoa, this was a crazy hack.” BEN: The weirdest use of observables, there's been quite a few odd ones. One of the ones that I did one time that is maybe in RxJS's wheelhouse, it was just that RxJS already existed. So, I didn't want to pull in another transducer library, was using RxJS as a transducer. Basically… in Netflix we had a situation where we had these huge, huge arrays of very large objects. And if you try to take something like that and then map it and then filter it and then map it and then filter it, we're using Array map and filter, what ends up happening is you create all sorts of intermediary arrays in-memory. And then garbage collection has to come through and clean that up. And that locks your thread. And over time, we were experiencing slowness with this app. And it would just build up until eventually it ground to a halt. And I used RxJS because it was an available tool there to wrap these arrays in an observable and then perform operations on them step-by-step, the same map, filter, and so on. But when you do that, it doesn't create intermediary arrays because it passes each value along step to step instead of producing an entire array and then doing another step and producing an entire array, and so on. So… CHARLES: So, will you just… BEN: It saved garbage collection and it increased the performance of the app. But that's just in an extreme case. I would never do that with just regular arrays. If anything, it was because it was huge, huge arrays of very large objects. CHARLES: So, you would create an observable our of the array and then just feed each element into the observable one at a time? BEN: Well, no. If you say ‘observable from' and you give it an array, that's basically what it does. CHARLES: Okay. BEN: It loops over the array and nexts those values out of the array synchronously. CHARLES: I see, I see. BEN: So, it's like having a for loop and then inside of that for loop saying, “Apply the map. Apply the filter,” whatever, to each value as they're going through. But when you look at it, if you had array map, filter, reduce, it's literally just taking the first step and saying ‘observable from' and wrapping that array and then the rest of it's still the same. CHARLES: Right. Yeah. No, that's really cool. BEN: That was a weirder use of it. I've heard tell of other things where people used observables to do audio synchronization, which is pretty interesting. Because you have to be very precise with audio synchronization. So, hooking into some of the Web Audio APIs and that sort of thing. That's pretty interesting. The WebSocket multiplexing is something I did at Netflix that's a little bit avant-garde for observable use because you essentially have an observable that is your WebSocket. And then you create another observable that closes over that observable and sends messages over the WebSocket for what you're subscribed to and not subscribed to. And it enables you to very easily retry connections and these sorts of things. I did a whole talk on that. That one's pretty weird. CHARLES: Yeah. Man, I [inaudible] to see that. BEN: But in the general use case, you click a button, you make an AJAX request, and then you get that back and maybe you make another AJAX request. Or like drag and drop and these sorts of things where you're coordinating multiple events together, is the general use case. The non-weird use case for RxJS. Tracy does weird stuff with RxJS though. [Laughter] CHARLES: Yeah, what's some weird uses of RxJS? TRACY: I think my favorite thing to do right now is to figure out how many different IoT-related things I can make work with RxJS. So, how many random things can I connect to an application using that? BEN: Tracy's projects are the best. They're so good. [Laughter] TRACY: Well, Ben and I created an application where you can take pictures of things using the Google Image API and it'll spit back a set of puns for you. So, you take a picture of a banana, it'll give you banana puns. Or you can talk to it using the speech recognition API. My latest thing is I really want to figure out how to… I haven't figured out if Bluetooth Low Energy is actually enabled on Google Home Minis. But I want to get my Google Home Mini to say ‘booty'. [Inaudible] [Laughter] CHARLES: RxJS to the rescue. [Laughter] BEN: Oh, there was, you remember Ng-Cruise. We did Ng-Cruise and on there, Alex Castillo brought… TRACY: Oh, that was so cool. BEN: All sorts of interesting… you could read your brain waves. Or there was another one that was, what is it, the Microsoft, that band put around your wrist that would sense what direction your arm was in and whether or not your hand was flexed. And people… TRACY: Yeah, so you could flip through things. BEN: Yeah. And people were using reactive programming with that to do things like grab a ball on the screen. Or you could concentrate on an image and see if it went blurry or not. ELRICK: Well, for like, Minority Report. BEN: Oh, yeah, yeah. Literally, watching a machine read your mind with observables. That was pretty cool. That's got to be the weirdest. TRACY: Yeah, or we had somebody play the piano while they were wearing one of the brainwave… it's called the OpenBCI project is what it is. And what you can do is you can actually get the instructions to 3D print out your own headset and then buy the technology that allows you to read brain waves. And so with that, it's like… I mean, it was really awesome to watch her play the piano and just see how her brain waves were going super crazy. But there's also these really cool… I don't know if you guys have heard of Jewelbots, but they're these programmable friendship bracelets that are just little Arduino devices that light up. I have two of them. I haven't even opened them. CHARLES: [Laughs] TRACY: I've been waiting to play with them with you. I don't know what we're going to do, but I just want to send you lights. Flashing lights. [Laughter] TRACY: Morse code ask you questions about RxJS while you're working. [Laughter] CHARLES: Yeah. Critical bug. Toot-toot-toot-too-too-too-too-toot-toot. [Laughter] CHARLES: RxJS Justice League. TRACY: That would actually be really fun. [Laughter] TRACY: That would be really fun. I actually really want to do that. But… CHARLES: I'm sure the next time we talk, you will have. TRACY: [Laughs] Yes. Yes, yes, yes, I know. I know. we'll do it soon. We just need to find some time while we're not going crazy with conferences and stuff like that. CHARLES: So, before we head out, is there any upcoming events, talks, releases, anything that we ought to be, we or the listeners, ought to be aware of? TRACY: Yeah, so one of the things is that Ben and I this weekend actually just recorded the latest version of RX Workshop. So, if you want to learn all about the latest, latest, newest new, you can go ahead and take that course. We go through a lot of different things like multiplex WebSockets, building an application. Everywhere from the fundamentals to the more real world implementations of RxJS. BEN: Yeah. Even in the fundamentals area, we've had friends of ours that are definitely seasoned Rx veterans come to the workshop. And most of them ask the most questions while talking about the fundamentals. Because I tend to dig into, either deep into the internals or into the why's and how's thing. Why and how things work. Even when it comes to how to subscribe to an observable. Deep detailed information about what happens if you don't provide an error handler and certain cases and how that's going to change in upcoming versions, and why that's changing in upcoming versions, and what the TC39's thoughts are on that, and so on and so forth. So, I try to get into some deeper stuff and we have a lot of fun. And we tend to be a little goofier at the workshops from time to time than we were in this podcast. Tracy and I get silly when we're together. TRACY: It's very true. [Laughter] TRACY: But I think also, soon I think there are people that are going to be championing an Observable proposal on what [inaudible]. So, aside from the TC39 Observable proposal that's currently still at stage one, I don't know Ben if you want to talk a little bit about that. BEN: Oh, yeah. So, I've been involved in conversations with folks from Netflix and Google as well, Chrome team and TC39 members, about getting the WHATWG, the ‘what wig', they're a standards body similar to W3C, to include observables as part of the DOM. The post has not been made yet. But the post is going to be made soon as long as everybody's okay with it. And what it boils down to is the idea of using observables as part of event targets. An event target is the API we're all familiar with for ‘add event listener', ‘remove event listener'. So, pretty much anywhere you'd see those methods, there might also someday be an on method that would return an observable of events. So, it's really, really interesting thing because it would bring at least the primitives of reactive programming to the browser. And at the very least it would provide maybe a nicer API for people to subscribe to events coming from different DOM elements. Because ‘add event listener' and ‘remove event listener' are a little unergonomic at times, right? CHARLES: Yeah. They're the worst. BEN: Yeah. CHARLES: That's a very polite way of putting it. BEN: [Chuckles] So, that's one thing that's coming down the pipe. Other things, RxJS 6 is in the works. We recently tied off 5.5 in a stable branch. And master is now our alpha that we're working on. So, there's going to be a lot of refactoring and changes there, trying to make the library smaller and smaller. And trying to eliminate some of the footprints that maybe people had in previous versions. So, moving things around so people aren't importing stuff that were meant to be implementation details, reducing the size of the library, trying to eliminate some bloat, that sort of thing. I'm pretty excited about that. But that's going to be in alpha ongoing for a while. And then hopefully we'll be able to move into beta mid first quarter next year. And then when that'll be out of beta, who knows? It all depends on how well people like the beta and the alpha, right? CHARLES: Alright. Well, so if folks do want to follow up with y'all either in regards to the course or to upcoming releases or any of the other great stuff that's coming along, how would they get in touch with y'all? TRACY: You can find me on Twitter @ladyleet. But Ben is @BenLesh. RX Workshop is RXWorkshop.com. I think in January we're going to be doing state of JavaScript under This Dot Media again. So, that's where all the core contributors of different frameworks and libraries come together. So, we'll definitely be giving a state of RxJS at that time. And next year also Contributor Days will be happening. So, if you go to ContributorDays.com you can see the previous RxJS Contributor Days and figure out how to get involved. So, we're always open and happy and willing to teach everybody. And again, if you want to get involved it doesn't matter whether you have little experience or lots of experience. We are always willing to show you how you can play. BEN: Yeah. You can always find us on Twitter. And don't forget that if you don't find Tracy or I on Twitter, you can always message Jay Phelps on Twitter. That's important. @_JayPhelps. Really. TRACY: Yeah. [Laughter] BEN: You'll find us. CHARLES: [Chuckles] Look for Jay in the show notes. [Laughter] CHARLES: Alright. Well, thank you so much for all the stuff that y'all do, code and otherwise. And thank you so much Ben, thank you so much Tracy, for coming on the show. BEN: Thank you. CHARLES: Bye Elrick and bye everybody. If you want to reach out to us, you can always get in touch with us at @TheFrontside or send us an email at contact@frontside.io. Alright everybody, we'll see you next week.