Container for a set of identifiers
POPULARITY
15 episodes with Namespace
4 episodes with Namespace
2 episodes with Namespace
2 episodes with Namespace
2 episodes with Namespace
2 episodes with Namespace
2 episodes with Namespace
2 episodes with Namespace
2 episodes with Namespace
Welcome to Manufacturing Hub, where we dive deep into the world of industrial automation, software, and digital transformation. In this episode, hosts Dave and Vlad are joined by Zach Scriven, an industrial automation expert, digital transformation evangelist, and a key player in the development of Prove It, a groundbreaking industry conference.This conversation explores a range of topics, from Zach's personal journey in industrial automation and SCADA integration to his pioneering work in digital transformation education. We discuss Unified Namespace (UNS)—a powerful framework for structuring and scaling industrial data—and its role in breaking down silos and creating scalable, interoperable architectures.Key Topics Discussed:✅ Zach Scriven's Background: His journey from SCADA integration in the water industry to co-founding 4.0 Solutions and IoT University.✅ Unified Namespace (UNS): What it is, why it matters, and how it enables scalable industrial data architectures.✅ Digital Transformation in Manufacturing: The need for a clear strategy, the challenges of data silos, and the shift toward IT-OT convergence.✅ Edge Computing & Industrial Data Platforms: How Ignition, MQTT, Litmus Edge, HighByte, and HiveMQ are changing the landscape of industrial automation.✅ Challenges in Legacy Industrial Systems: How companies with aging infrastructure can begin their digital transformation journey.✅ The Future of Industrial Conferences – Prove It: Why traditional conferences fail to deliver value and how Prove It is disrupting the model by requiring vendors to "prove" their solutions in a real-world simulated environment.References & Companies Mentioned:
In this episode of Control Intelligence, written by contributing editor Tobey Strauch, editor in chief Mike Bacidore explains what unified namespace is and why it's beneficial.
On this episode of the IoT For All Podcast, Dominik Obermaier, Co-Founder and CTO of HiveMQ, joins Ryan Chacon to discuss unified namespace (UNS). The conversation covers how UNS eases new data architecture adoption, how UNS is changing how enterprises think about data, what makes UNS different from other data architectures, IT/OT convergence, MQTT, trends in industrial data management, advice for transitioning to unified namespace, and unified namespace use cases. Dominik Obermaier is the Co-Founder and CTO of HiveMQ. He is a member of the OASIS Technical Committee and is part of the standardization committee for MQTT 3.1.1 and MQTT 5. He is the co-author of the book "The Technical Foundations of IoT" and a frequent speaker on IoT, MQTT, and messaging. HiveMQ empowers businesses to transform with the most trusted MQTT platform. Designed to connect, communicate, and control IoT data under real-world stress, the HiveMQ MQTT Platform is the proven enterprise standard and powers use cases in automotive, energy, logistics, smart manufacturing, transportation, and more. Leading brands like Audi, BMW, Liberty Global, Mercedes-Benz, Siemens, and ZF choose HiveMQ to build smarter IoT projects, modernize factories, and create better customer experiences. Discover more about IoT at https://www.iotforall.com Find IoT solutions: https://marketplace.iotforall.com More about HiveMQ: https://www.hivemq.com Connect with Dominik: https://www.linkedin.com/in/dobermai/ (00:00) Intro (00:12) Dominik Obermaier and HiveMQ (00:54) What is unified namespace? (04:46) How does UNS ease new data architecture adoption? (07:20) How is UNS changing how enterprises think about data? (10:00) What makes UNS different and IT/OT convergence (12:50) What to look for in an MQTT platform when using UNS (15:21) Trends in industrial data management (17:08) Advice for transitioning to unified namespace (18:28) Unified namespace use cases (20:15) Learn more and follow up Subscribe on YouTube: https://bit.ly/2NlcEwm Join Our Newsletter: https://newsletter.iotforall.com Follow Us on Social: https://linktr.ee/iot4all
In this episode of Crazy Wisdom, Stewart Alsop hosts ~littel-wolfur to explore spaced repetition, the dynamics of learning algorithms, and the philosophy behind Urbit. They break down Urbit's promise as a peer-to-peer platform with roots in a deep, almost otherworldly commitment to resilience and a long time horizon. Alongside ~littel-wolfur's take on memory as the strange balance of laziness and persistence, they dig into shrubbery, Urbit's latest namespace innovation, and the challenge of creating tools that last. From generational shifts to the philosophy of technology, Stewart and ~littel-wolfur contemplate whether Urbit's rebellious craftsmanship might be the foundation for a more enduring internet. You can connect with ~littel-wolfur on Twitter.Check out this GPT we trained on the conversation!Timestamps00:00 Introduction to the Crazy Wisdom Podcast00:22 Understanding Spaced Repetition01:39 Personal Experiences with Spaced Repetition04:08 Challenges in Spaced Repetition Software06:45 Building a Flashcard App on Urbit09:03 Introduction to Shrubbery on Urbit13:26 The State of Urbit and Its Future22:01 The Long-Term Vision of Urbit and Bitcoin28:37 Balancing Internet Time with Parenthood29:37 Challenges of Urbit's Ease of Use30:22 New Blood in the Urbit Community31:15 Building Communities on Urbit32:38 Twitter's Complexities and Elon Musk's Influence41:02 AI's Role in Software Development49:52 Transhumanism and AI Art54:50 The Future of Craftsmanship in Programming55:45 Conclusion and Contact InformationKey InsightsThe Power and Paradox of Spaced Repetition: Stewart and ~littel-wolfur discuss spaced repetition as an ingenious blend of laziness and persistence. By setting reminders to review information just before it's forgotten, spaced repetition acts as an effortless yet powerful memory tool. Although the practice demands daily discipline, it becomes an invaluable mechanism for retaining knowledge across vast timescales.SuperMemo and Incremental Reading: ~littel-wolfur shares his experience with SuperMemo, the original spaced repetition software that takes the method even further. SuperMemo's “incremental reading” allows users to gradually extract information from lengthy texts, breaking down complex learning into manageable, spaced chunks. For ~littel-wolfur, this approach goes beyond mere memorization; it turns learning into an immersive, long-term commitment.The Urbit Experiment: Urbit, a decentralized peer-to-peer network and OS, represents a radical rethinking of the internet. Stewart and ~littel-wolfur examine Urbit's potential as a platform where users truly own and control their data, echoing ideals of early Web 1.0. As the “long-haul project” of the tech world, Urbit cultivates an almost timeless ethos, making it as much a social experiment as a computing system.Shrubbery and Namespace Innovation: A core element of Urbit, “shrubbery” introduces a namespace that enables users to organize, connect, and retrieve information from across their digital universe. ~littel-wolfur explains how shrubbery allows users to link pieces of data like conversation notes, wikis, and documents, making it a versatile learning platform on Urbit. The elegance of this integration hints at a future internet where information can be personalized and seamlessly connected.Craftsmanship and Digital Resilience: ~littel-wolfur and Stewart touch on the fading art of craftsmanship in tech, which often gets lost in the layers of abstractions that modern software relies on. For ~littel-wolfur, coding on Urbit feels like working in a digital woodshop, where the focus is on intentionality and precision rather than flashy or disposable tech. This philosophy of craftsmanship offers a refreshing take on the art of creation in software, hinting at the durability and authenticity Urbit hopes to embody.AI's Limitations and Overconfidence Trap: The episode also highlights the limitations of AI, especially when it encourages laziness or over-reliance. While AI can help automate routine tasks, ~littel-wolfur warns of its tendency to produce fragile, overly complex solutions that unravel under scrutiny. They caution that true understanding comes not from shortcuts, but from engaging deeply with the work—a point that resonates with their belief in disciplined learning practices like spaced repetition.The Value of Optimism and Long Time Horizons: Amid a society obsessed with quick wins and rapid monetization, Stewart and ~littel-wolfur see Urbit's culture as a refreshing outlier, filled with builders who value curiosity and long-term thinking. This “thousand-year mindset” stands in contrast to much of the tech industry, where projects are often driven by immediate financial returns. By embracing a philosophy that resists the pressure for instant success, Urbit aligns itself with a vision of digital infrastructure that, rather than fueling transient trends, aims to be a lasting foundation for generations to come.
For episode 423, Co-founder Benjamin Brandall explains what Decent Land is and they are building tools to unify and liberate your on-chain data. Decent Land believes in radical composability for web3. The future is multichain but a multitude of walled gardens is no improvement to the web2 models we're trying to escape. The ultimate outcome for the new age of the web is a pool of easily accessible, sampleable and remixable data that can power permanent applications without sacrificing UX. Some existing Decent Protocols that we discuss in the episode include WeaveVM, Molecular Execution Machine, Namespace and Ark Protocol. ⏳ Timestamps: 0:00 | Introduction 0:56 | Who is Benjamin Brandall? 8:40 | What is Decent Land? 9:53 | WeaveVM and Molecular Execution Machine 12:10 | Consequences of inadequate blockchain storage 14:00 | Can all blockchain data truly be decentralized? 18:15 | Which blockchain handles on-chain storage the best? 20:03 | Decent Land roadmap 21:57 | Decent Land Website & Social Media
話したこと RubyKaigi 2024 - RubyKaigi 2024 Namespace, What and Why - RubyKaigi 2024 【タイミー】スキマ時間にすぐ働ける！700万人が利用している単発バイトアプリ yuru28 と yarukinaifm Events - RubyKaigi 2024 AI Travel：出張の手間とコストを削減 県民の定番「締めのステーキ」とは？ 人気を呼ぶ千円ステーキ 「やっぱりステーキ」県外進出 Yarukinai.fmをサポートする 話してる人 マーク(tetuo41) 39歳男性。既婚。二児の父です。 須貝(sugaishun) 会社員
This week's guest is Vatsal Shah (https://www.linkedin.com/in/vatsal12/), Founder and CEO of Litmus (https://www.linkedin.com/company/litmus-automation/). Vatsal discusses his journey from an automation engineer at Rockwell, to building a new industrial data platform from the ground up after becoming frustrated with the limitations of the offerings from established vendors. He discusses manufacturers' exodus from on-prem to cloud systems, the pros and cons of data protocols like MQTT and Sparkplug B, and why the Unified Namespace architecture is getting so much attention. Plus, he shares his vision for the future of edge computing and how an open ecosystem of interoperable tools is transforming the industry. Augmented Ops is a podcast for industrial leaders, shop floor operators, citizen developers, and anyone else that cares about what the future of frontline operations will look like across industries. This show is presented by Tulip (https://tulip.co/), the Frontline Operations Platform. You can find more from us at Tulip.co/podcast (https://tulip.co/podcast) or by following the show on LinkedIn (https://www.linkedin.com/company/augmentedpod/). Litmus is a Tulip Technology Ecosystem (https://tulip.co/partners/technology-ecosystem-partners/) Partner. Special Guest: Vatsal Shah.
#OpenSource #Architektur #Datahub #Communitywww.iotusecase.comFrank Thelen, der Unternehmer, Bestsellerautor, Investor, bekannt aus “Die Höhle der Löwen”, ist mit seinem neuesten IIoT-Investment United Manufacturing Hub (UMH) in der 122. Folge des IoT Use Case Podcast bei Madeleine Mickeleit zu Gast! Gemeinsam mit Alexander Krüger (CEO und Co-Founder bei UMH) diskutieren sie Themen wie den Einsatz von Open Source Software, die Wichtigkeit von Datenstandardisierung oder die Rolle von Community-driven Entwicklungen.Zusammenfassung der PodcastfolgeDas Kölner Startup United Manufacturing Hub hat sich zum Ziel gesetzt, einen neuen Datenstandard in der Industrie zu etablieren. Unterstützt wird es dabei von Frank Thelens Venture-Capital-Fonds Freigeist und dem Bestandsinvestor DnA Ventures. Die von ihnen entwickelte Open-Source-Plattform ermöglicht es Ingenieuren, alle Datenquellen in der Fabrik nahtlos zu integrieren, um eine datengetriebene, effizientere und nachhaltigere Produktion zu fördern. Der Unified Namespace spielt eine zentrale Rolle im Konzept von United Manufacturing Hub. Er wird beschrieben als eine Art zentraler Datenkrake oder Message Broker, durch den alle Arbeitsaufträge, Datenpunkte und Temperaturen innerhalb einer Fabrik geleitet werden. Diese Architektur ermöglicht den einheitlichen Zugriff auf Daten aus verschiedenen Quellen, was die Basis für die standardisierte Datenkommunikation bildet. Der Unified Namespace ermöglicht die Trennung und das gezielte Routing von Daten, was ihn zu einem wichtigen Werkzeug für die Integration und Analyse von Produktionsdaten macht. United Manufacturing Hub nutzt diesen Ansatz, um eine effiziente und übergreifende Datennutzung in Produktionsumgebungen zu ermöglichen, wodurch die Basis für datengetriebene Entscheidungen und Prozessoptimierungen geschaffen wirdUnited Manufacturing Hub wurde 2021 von Jeremy Theocharis, Alexander Krüger und Christian Proch gegründet. Das Team hat sich zum Ziel gesetzt, die besten IT- und OT-Tools für Ingenieure zugänglich zu machen und eine Grundlage für den Austausch von Wissen und Erfahrungen zu bieten. Bis heute hat das Unternehmen an über 50 Kundenstandorten gearbeitet und ist auf sechs Kontinenten aktiv.Mit der Seed-Finanzierung durch Freigeist und der Unterstützung von DnA Ventures plant das Unternehmen, sein Produkt- und Engineering-Team weiter auszubauen, um den wachsenden Anforderungen großer Unternehmen gerecht zu werden. Darüber hinaus wird in die schnell wachsende Community rund um das United Manufacturing Hub investiert, die bereits mehr als 2.000 Entwickler und Ingenieure umfasst.---Relevante Folgenlinks:Alex (https://www.linkedin.com/in/alexander-krueger/)Madeleine (https://www.linkedin.com/in/madeleine-mickeleit/)https://learn.umh.app/Community-Einladung: https://discord.com/invite/2B6tF6mF4ZJetzt IoT Use Case auf LinkedIn folgen
United Manufacturing Hub aus Köln hat eine Software-Plattform entwickelt, die es Industrieunternehmen ermöglicht, alle Daten ihrer Produktion auf einem zentralen Daten-Bus zu verarbeiten. Damit wollen sie zum Datenstandard in der Industrie werden und so die Basis für KI-gestützte, effiziente und nachhaltige Produktionen liefern. Das Konzept ist in der Industrie als Unified Namespace bekannt. Gründer Alexander Krüger erzählt im Podcast mit Frank Thelen und Freigeist Principal Alex Pass, wie es zu der Entstehung der Open-Source Softwareplattform kam und wie namhafte Kunden wie E.ON sie bereits einsetzen, um ihre Prozesse effizienter zu gestalten. Mehr Informationen auf https://www.umh.app/
The TWiET crew delves into botnets, securing hybrid work environments, the future of DNS architecture, and more. News Blips: Researchers uncover sophisticated IoT botnet named "K- Botnet" targeting US entities; linked to Chinese state-aligned hackers AI startup Vanta (a TWiT.tv Sponsor) launches AI suite to automate repetitive security and compliance tasks DARPA funds revolutionary laser-based aerial energy delivery system for military operations Networking company Cradlepoint acquires SASE vendor ERA to provide a potential combined 5G and zero-trust networking solution DNS Deep Drive Part 3 with DNS Expert Josh Kuo and Principal Solutions Architect of Infoblox Ross Gibson Internal vs external DNS; differences in intended audience and integration Decoupling DNS services from domain controllers for stability Namespace planning tips; use owned domains, avoid random internal TLDs Encrypted DNS tradeoffs; privacy vs. visibility for security teams DNS security options like RPZ for control over internal resolution Future DNS role predictions like firewall integration and threat intel protections The episode concludes with the announcement that the long-running show will be coming to an end after 12 years of enterprise content. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guests: Josh Kuo, Ross Gibson, and Leo Laporte Help support TWiT by joining Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT vanta.com/ENTERPRISE Miro.com/podcast
The TWiET crew delves into botnets, securing hybrid work environments, the future of DNS architecture, and more. News Blips: Researchers uncover sophisticated IoT botnet named "K- Botnet" targeting US entities; linked to Chinese state-aligned hackers AI startup Vanta (a TWiT.tv Sponsor) launches AI suite to automate repetitive security and compliance tasks DARPA funds revolutionary laser-based aerial energy delivery system for military operations Networking company Cradlepoint acquires SASE vendor ERA to provide a potential combined 5G and zero-trust networking solution DNS Deep Drive Part 3 with DNS Expert Josh Kuo and Principal Solutions Architect of Infoblox Ross Gibson Internal vs external DNS; differences in intended audience and integration Decoupling DNS services from domain controllers for stability Namespace planning tips; use owned domains, avoid random internal TLDs Encrypted DNS tradeoffs; privacy vs. visibility for security teams DNS security options like RPZ for control over internal resolution Future DNS role predictions like firewall integration and threat intel protections The episode concludes with the announcement that the long-running show will be coming to an end after 12 years of enterprise content. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guests: Josh Kuo, Ross Gibson, and Leo Laporte Help support TWiT by joining Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT vanta.com/ENTERPRISE Miro.com/podcast
The TWiET crew delves into botnets, securing hybrid work environments, the future of DNS architecture, and more. News Blips: Researchers uncover sophisticated IoT botnet named "K- Botnet" targeting US entities; linked to Chinese state-aligned hackers AI startup Vanta (a TWiT.tv Sponsor) launches AI suite to automate repetitive security and compliance tasks DARPA funds revolutionary laser-based aerial energy delivery system for military operations Networking company Cradlepoint acquires SASE vendor ERA to provide a potential combined 5G and zero-trust networking solution DNS Deep Drive Part 3 with DNS Expert Josh Kuo and Principal Solutions Architect of Infoblox Ross Gibson Internal vs external DNS; differences in intended audience and integration Decoupling DNS services from domain controllers for stability Namespace planning tips; use owned domains, avoid random internal TLDs Encrypted DNS tradeoffs; privacy vs. visibility for security teams DNS security options like RPZ for control over internal resolution Future DNS role predictions like firewall integration and threat intel protections The episode concludes with the announcement that the long-running show will be coming to an end after 12 years of enterprise content. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guests: Josh Kuo, Ross Gibson, and Leo Laporte Help support TWiT by joining Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT vanta.com/ENTERPRISE Miro.com/podcast
The TWiET crew delves into botnets, securing hybrid work environments, the future of DNS architecture, and more. News Blips: Researchers uncover sophisticated IoT botnet named "K- Botnet" targeting US entities; linked to Chinese state-aligned hackers AI startup Vanta (a TWiT.tv Sponsor) launches AI suite to automate repetitive security and compliance tasks DARPA funds revolutionary laser-based aerial energy delivery system for military operations Networking company Cradlepoint acquires SASE vendor ERA to provide a potential combined 5G and zero-trust networking solution DNS Deep Drive Part 3 with DNS Expert Josh Kuo and Principal Solutions Architect of Infoblox Ross Gibson Internal vs external DNS; differences in intended audience and integration Decoupling DNS services from domain controllers for stability Namespace planning tips; use owned domains, avoid random internal TLDs Encrypted DNS tradeoffs; privacy vs. visibility for security teams DNS security options like RPZ for control over internal resolution Future DNS role predictions like firewall integration and threat intel protections The episode concludes with the announcement that the long-running show will be coming to an end after 12 years of enterprise content. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guests: Josh Kuo, Ross Gibson, and Leo Laporte Help support TWiT by joining Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT vanta.com/ENTERPRISE Miro.com/podcast
The TWiET crew delves into botnets, securing hybrid work environments, the future of DNS architecture, and more. News Blips: Researchers uncover sophisticated IoT botnet named "K- Botnet" targeting US entities; linked to Chinese state-aligned hackers AI startup Vanta (a TWiT.tv Sponsor) launches AI suite to automate repetitive security and compliance tasks DARPA funds revolutionary laser-based aerial energy delivery system for military operations Networking company Cradlepoint acquires SASE vendor ERA to provide a potential combined 5G and zero-trust networking solution DNS Deep Drive Part 3 with DNS Expert Josh Kuo and Principal Solutions Architect of Infoblox Ross Gibson Internal vs external DNS; differences in intended audience and integration Decoupling DNS services from domain controllers for stability Namespace planning tips; use owned domains, avoid random internal TLDs Encrypted DNS tradeoffs; privacy vs. visibility for security teams DNS security options like RPZ for control over internal resolution Future DNS role predictions like firewall integration and threat intel protections The episode concludes with the announcement that the long-running show will be coming to an end after 12 years of enterprise content. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guests: Josh Kuo, Ross Gibson, and Leo Laporte Help support TWiT by joining Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT vanta.com/ENTERPRISE Miro.com/podcast
The TWiET crew delves into botnets, securing hybrid work environments, the future of DNS architecture, and more. News Blips: Researchers uncover sophisticated IoT botnet named "K- Botnet" targeting US entities; linked to Chinese state-aligned hackers AI startup Vanta (a TWiT.tv Sponsor) launches AI suite to automate repetitive security and compliance tasks DARPA funds revolutionary laser-based aerial energy delivery system for military operations Networking company Cradlepoint acquires SASE vendor ERA to provide a potential combined 5G and zero-trust networking solution DNS Deep Drive Part 3 with DNS Expert Josh Kuo and Principal Solutions Architect of Infoblox Ross Gibson Internal vs external DNS; differences in intended audience and integration Decoupling DNS services from domain controllers for stability Namespace planning tips; use owned domains, avoid random internal TLDs Encrypted DNS tradeoffs; privacy vs. visibility for security teams DNS security options like RPZ for control over internal resolution Future DNS role predictions like firewall integration and threat intel protections The episode concludes with the announcement that the long-running show will be coming to an end after 12 years of enterprise content. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guests: Josh Kuo, Ross Gibson, and Leo Laporte Help support TWiT by joining Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT vanta.com/ENTERPRISE Miro.com/podcast
Show Notes The M365 Admin app is used to administer M365 tenants on the go. It's a complex app written in Xamarin.Forms ... or it was. Find out how the team behind the M365 admin app migration from Xamarin.Forms to .NET MAUI. .NET MAUI API Browser (https://learn.microsoft.com/en-us/dotnet/api/?view=net-maui-7.0) Reuse Effects in .NET MAUI (https://learn.microsoft.com/en-us/dotnet/maui/migration/effects?view=net-maui-7.0) Upgrade a Xamarin.Forms app to a .NET MAUI app with the .NET Upgrade Assistant (https://learn.microsoft.com/en-us/dotnet/maui/migration/upgrade-assistant?tabs=vswin) Migrate a Xamarin.Forms custom renderer to a .NET MAUI handler (https://learn.microsoft.com/en-us/dotnet/maui/migration/renderer-to-handler) Namespace changes (https://learn.microsoft.com/dotnet/maui/migration/multi-project-to-multi-project?view=net-maui-8.0#namespace-changes) API changes (https://learn.microsoft.com/dotnet/maui/migration/multi-project-to-multi-project?view=net-maui-8.0#api-changes) Update app dependencies (https://learn.microsoft.com/dotnet/maui/migration/multi-project-to-multi-project?view=net-maui-8.0#update-app-dependencies) Migration troubleshooting tips (https://learn.microsoft.com/dotnet/maui/migration/multi-project-to-multi-project?view=net-maui-8.0#compile-and-troubleshoot) Upgrade from .NET 7 to .NET 8 (https://learn.microsoft.com/en-us/dotnet/maui/whats-new/dotnet-8?view=net-maui-8.0#upgrade-from-net-7-to-net-8) What's new in .NET MAUI for .NET 8 (https://learn.microsoft.com/dotnet/maui/whats-new/dotnet-8?view=net-maui-8.0) Cross-platform resource files with single project (https://learn.microsoft.com/dotnet/maui/fundamentals/single-project?view=net-maui-8.0#resource-files) Build accessible apps with semantic properties (https://learn.microsoft.com/dotnet/maui/fundamentals/accessibility?view=net-maui-8.0) Mono interpreter on iOS and Mac Catalyst (https://learn.microsoft.com/dotnet/maui/macios/interpreter?view=net-maui-8.0) Microsoft Intune App SDK for .NET MAUI (Android | iOS) (https://github.com/msintuneappsdk) Add authentication to your .NET MAUI app using MSAL.NET (https://learn.microsoft.com/azure/developer/mobile-apps/azure-mobile-apps/quickstarts/maui/authentication?pivots=vs2022-mac) A .NET MAUI sample using MSAL.NET to authenticate users with Azure AD (https://learn.microsoft.com/samples/azure-samples/ms-identity-ciam-dotnet-tutorial/ms-identity-ciam-dotnet-tutorial-2-sign-in-maui/) Follow Us: * James: Twitter (https://twitter.com/jamesmontemagno), Blog (https://montemagno.com), GitHub (http://github.com/jamesmontemagno), Merge Conflict Podcast (http://mergeconflict.fm) * Matt: Twitter (https://twitter.com/codemillmatt), Blog (https://codemilltech.com), GitHub (https://github.com/codemillmatt) * David: Twitter (https://twitter.com/davidortinau), Github (https://github.com/davidortinau)
节目概要：为什么团队要做Space ID？与其他域名服务的区分点数字身份的意义就在于能在各个场景里使用，甚至能在用户使用一个app时通过获得另一个app上这个用户身份背后的某些行为数据从而更好的服务这个用户。Space ID在这块的思考和计划？长期来看数字身份肯定不会只是用文字来表现，那么域名的意义？未来数字身份的形态？Space ID 未来会支持的链智能合约钱包的支持和其他与身份相关的协议打造爆款与降低准入门槛：鸡和蛋的问题为什么要有这个ID token？用户可以拿它来做什么？ Twitter：@SpaceIDProtocolWebsite: https://space.id/ 如果喜欢本作品，欢迎打赏ETH/SOL/BTC：ETH: 0x83Fe9765a57C9bA36700b983Af33FD3c9920Ef20SOL: AaCeeEX5xBH6QchuRaUj3CEHED8vv5bUizxUpMsr1KytBTC: 3ACPRhHVbh3cu8zqtqSPpzNnNULbZwaNqG 重要声明：Mable Jiang或嘉宾在播客中的观点仅代表他们的个人看法。此播客仅用于提供信息，不作为投资参考。Mable Jiang有时可能会在此节目中讨论的某项目中持有头寸。 Important Disclaimers: All opinions expressed by Mable Jiang, or other podcast guests, are solely their opinion. This podcast is for informational purposes only and should not be construed as investment advice. Mable Jiang may hold positions in some of the projects discussed on this show.
A meditation on the power of metaphors and mental models which shape our understanding of cyberspace. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/generativity/message
Im Tec-Podcast für Sie nachgefragt: Das Storage Consortium im Expertengespräch mit HPE und CANCOM zu CTERA Global File Services, 'Warm Data' und Object Storage Gesprächspartner dieser Episode unter Einbeziehung von Lösungen der Anbieter Scality (Object Storage) und CTERA (File Services) sind Dirk Hannemann, HPE Principal Solution Architect und Christian Hansmann, Solution Sales Architect bei CANCOM. Die Fragen stellt Norbert Deuschle vom Storage Consortium. Um was geht es? Nachdem in einer der vorangegangenen Podcast-Episode geklärt wurde, ob und in wieweit die Objektdaten-Speicherung nur für große unstrukturierte Datenmengen sowie überwiegend inaktive (kalte) Daten geeignet ist, liegt der inhaltliche Fokus dieses Fachbeitrags bei der Speicherung-/Verwaltung von sog. 'warmen' Daten mit Hilfe globale File Services sowie cloud-native Objektspeicher-Technologien; dies aber im Zusammenhang mit NAS-Migrationen (File-Daten) und der Cloud. Im Detail werden neben kundenseitigen Anforderungen auch die Lösungen auf Basis Scality Ring bzw. Artesca (Objektspeicher) in Verbindung mit CTERA (Global File Services) vorgestellt. Hier einige Punkte, die in dieser Episode detaillierter behandelt werden (Hörzeit 27:02 min): Gewährleistung von Sicherheit, Datensouveränität und Datenschutz (EU-DSGVO...) Steigendes Risiko von Cyber-/Ransomware-Angriffen Kosten für die Migration in die Cloud; Kosten für den Zugriff auf Daten in der Cloud ?? Bereitstellung einer sicheren kosteneffizienten Plattform für Unternehmens-Dateidienste, um NAS-Migrationen in die Cloud zu vereinfachen. Traditionelle Speicher- und Sicherungssysteme mit herkömmliche dateisystembasierte Anwendungen und Arbeitslasten durch ein Cloud-Dateisystem ergänzen bzw. ersetzen, das auf softwaredefinierten File Services über Objektspeicher basiert und ohne Einschränkungen mit Object Storage funktioniert. File services mit Hilfe von CTERA's File Server Technologie. Globaler, optimierter Zugriff auf File-Daten Edge-to-core, der nativ objektbasiert ist. Vorteile gegenüber lokalen File-Diensten (klassischer Filer ohne global Namespace). Beispiele CTERA File Server Konsolidierung etc. Das globale Dateisystem ermöglicht die Speicherung einer "goldenen Kopie" aller Unternehmensdaten auf kostengünstigem und skalierbarem Cloud-Objektspeicher. Unternehmen erhalten eine unbegrenzte Dateikapazität am Edge, ohne dass zusätzlicher Speicherplatz für wachsende Datenmengen erforderlich ist. Workloads: Collaboration, PACS, Content, Video, Fotos, File-Storage etc. Geringere Speicherkosten: Edge-Caching sowie Deduplizierung und Komprimierung von Dateien vor der Speicherung tragen zur Senkung der Egress-Gebühren und des Objektspeichervolumens bei. Speicherkosten senken, indem alte Dateiserver durch kostengünstigen Objektspeicher ersetzt werden. Skalierbarkeit: Zwischenspeicherung und Speicherung von Hot-Files am Edge, während Cold-Files in den Cloud Object Storage ausgelagert werden. Anwendungen müssen nicht umgeschrieben werden... Benutzer arbeiten weiterhin mit einer hierarchischen Dateistruktur und Microsoft-kompatiblen NT ACL-Berechtigungen. Der Edge Filer speichert die Dateien für einen schnellen Benutzerzugriff lokal im Cache und synchronisiert die Dateien über mehrere Standorte hinweg, während der Großteil der Daten in einem kostengünstigen Objektspeicher vor Ort oder in der Cloud gespeichert wird. Georedundanz (kein B/R) Multi-Cloud-Datenreplikation stellt die Geschäftskontinuität sicher, wenn Unternehmen Daten und Anwendungen außerhalb des Unternehmens verlagern und ein neues externes Sicherungsziel benötigen. Einsatzvorteile mit MS 365 usw.
Sponsors:Buzzsprout Ads can now Monetize Your Back Catalog, by finding insertion points in your entire back catalogue automatically. SquadCast invites you to join their new Slack channel, DM @SquadCastFM if you want to join.Notes & Links: Spotify has launched audiobooks (in the US only). Audiobooks are an extra cost and you'll be taken to a website to purchase them.Spotify has signed a deal with Wattpad to bring Indonesian and Filipino webnovel authors to podcasting.Spotify's video podcasting service is apparently being used to pirate moviesSpotify's Chartable, an analytics and attribution service, is to lower its prices by 50%Acast is to lay off around 70 people (15% of its staff)The Open Podcast Prefix Project has been launched by John Spurlock. INTERVIEW: JOHN SPURLOCK NEXT WEEKTransistor now supports the Open Podcast Prefix project Apple Podcasts wants a website link for your podcastPodimo, the European subscription podcast service, has raised €58.6m ($58.5m) in funding. It had previously raised more than $116m.INTERVIEW: MORTEN CEO PODIMO NEXT WEEKIvy.fm now supports transcripts, soundbites, and location from the Podcast Index namespace!Captivate has just announced v2 of their dynamic content and monetisation engine AMIERSS Blue has added support for Alby and Fountain digital walletsBitcoin magazine carries a long piece about Podcasting 2.0's “value for value” fundingGoogle search is vulThe Greg Krino ShowVeteran, pilot, and attorney - Greg Krino - takes you on a deep-dive with experts to...Listen on: Apple Podcasts Spotify
Molly Presley, SVP of Marketing at Hammerspace discusses some challenges of protecting NAS devices, the importance of a global file system to leverage your metadata, and why the Developer is king.
Array Cast - March 5, 2022 Show NotesMany thanks to Adám Brudzewsky for collecting these links.[1] 00:01:23 APL Seeds '22 conference: https://www.dyalog.com/apl-seeds-user-meetings/aplseeds22.htm [2] 00:02:00 APL Quest chat event: https://apl.wiki/APL_Quest [3] 00:02:05 APL Orchard: https://apl.wiki/APL_Orchard [4] 00:02:55 APL Seeds '21 https://www.dyalog.com/apl-seeds-user-meetings/aplseeds21.htm [5] 00:03:38 APL Seeds '22 registration https://us02web.zoom.us/webinar/register/WN_yZb-ha8sRLCJ1DbjAq8nzA [6] 00:04:15 APL Farm: https://apl.wiki/APL_Farm [7] 00:04:20 BQNPad https://bqnpad.mechanize.systems/ [8] 00:06:02 Carlisle Group: https://www.carlislegroup.com/ [9] 00:07:55 APL '99: https://aplwiki.com/wiki/APL_conference#1999[10] 00:10:54 Josh wins second prize: https://www.dyalog.com/news/102/420/2015-APL-Programming-Contest-Winners.htm[11] 00:10:57 And grand prize: https://www.dyalog.com/news/112/420/2016-APL-Programming-Contest-Winners.htm[12] 00:11:04 Winner's presentation: https://dyalog.tv/Dyalog16/?v=afB2IXCBJJ8[13] 00:13:18 Dado Wiki coding practices: https://github.com/the-carlisle-group/Dado/wiki/How-Not-To-Code-In-Dyalog-APL[14] 00:17:23 Paul Mansour's blog: https://www.toolofthought.com[15] 00:18:00 Practical Introduction to APL https://github.com/the-carlisle-group/PracticalAPL[16] 00:18:32 Cas https://github.com/the-carlisle-group/cas-samples[17] 00:18:55 FlipDB https://github.com/the-carlisle-group/FlipDBDoc[18] 00:20:12 Carlisle Group on GitHub: https://github.com/the-carlisle-group[19] 00:23:34 Advent of Code in APL: https://apl.wiki/Advent_of_Code[20] 00:26:25 Outer Product: https://apl.wiki/Outer_Product[21] 00:27:01 ADSP #1 https://adspthepodcast.com/2020/11/20/Episode-0.html[22] 00:29:01 Marshall Lochbaum's intro do APL based on the Outer Product: https://www.youtube.com/watch?v=WlUHw4hC4OY[23] 00:29:23 Inner Product: https://apl.wiki/Inner_Product[24] 00:29:50 Iverson's generalisation of Outer Product: https://www.jsoftware.com/papers/APLDictionary1.htm#dot[25] 00:34:23 Summary of Paul Mansour "Why my mother-in-law has special serving dishes for corn on the cob and I don't" talk: https://www.dyalog.com/user-meetings/dyalog09.htm#24[26] 00:36:03 The Abacus project: https://github.com/the-carlisle-group/Abacus/[27] 00:38:37 Roger's "50" paper: https://www.jsoftware.com/papers/50/[28] 00:39:15 Parenthesis nesting: https://www.jsoftware.com/papers/50/50_05.htm[29] 00:41:25 Finnish book of APL idioms https://www.aplwiki.com/wiki/FinnAPL_idiom_library[30] 00:42:10 APL Quest on "Keeping Things In Balance": https://chat.stackexchange.com/transcript/52405?m=60517971#60517971[31] 00:42:58 Adám's Companion video: https://www.youtube.com/watch?v=El0_RB4TTPA&list=PLYKQVqyrAEj9wDIUyLDGtDAFTKY38BUMN&index=4[32] 00:43:10 Operators Ken Iverson paper https://dl.acm.org/doi/pdf/10.1145/357073.357074[33] 00:45:42 Aaron Hsu's talk "Does APL Need a Type System?": https://www.youtube.com/watch?v=z8MVKianh54[34] 00:48:47 Is-Prefix-Of ⊃⍷ : https://tryapl.org/?clear&q=IsPrefixOf%E2%86%90%E2%8A%83%E2%8D%B7%20%E2%8B%84%20%27ABC%27%20IsPrefixOf%20%27ABCDEF%27%20%E2%8B%84%20%27XYZ%27%20IsPrefixOf%20%27ABCD%27%20%E2%8B%84%20%27ABCD%27%20IsPrefixOf%20%27ABC%27&run[35] 00:49:40 "Default value": https://aplwiki.com/wiki/Fill_element[36] 00:51:02 Average +⌿÷≢ : https://tryapl.org/?clear&q=Average%E2%86%90%2B%E2%8C%BF%C3%B7%E2%89%A2%20%E2%8B%84%20Average%203%201%204%201%205&run[37] 00:51:15 Split ≠⊆⊢ : https://tryapl.org/?clear&q=Split%E2%86%90%E2%89%A0%E2%8A%86%E2%8A%A2%20%E2%8B%84%20%27%2F%27Split%27now%2Fis%2Fthe%2Ftime%27&run[38] 00:51:30 tacit: https://apl.wiki/Tacit_programming[39] 00:52:03 APLcart: https://apl.wiki/APLcart[40] 00:53:30 Dfn: https://apl.wiki/Dfn[41] 00:54:00 Traditional "procedural" functions: https://apl.wiki/Defined_function_(traditional)[42] 00:55:56 Power operator: https://help.dyalog.com/latest/#Language/Primitive%20Operators/Power%20Operator.htm[43] 01:01:30 Big O notation https://en.wikipedia.org/wiki/Big_O_notation[44] 01:02:20 Josh's email: josh {at} dyalog.com[45] 01:02:52 Namespaces: https://apl.wiki/Namespace[46] 01:09:21 Jobs: https://apl.wiki/Jobs[47] 01:10:52 contact at arraycast dot com
Join us every week where we answer your questions on Industry 4.0, IIoT, and digital transformation. Thanks for watching! Join our community Discord Server
Welcome to the 4.0 Solutions Weekly Live Q&A. Join us every week where we talk about Industry 4.0, IIoT, and Digital Transformation. Today we are answering the question: How do I document the progress/status of our Unified Namespace as we are in the process of a transformation? Join the Industry 4.0 Mentorship Program!https://www.iiot.university/mentorship-program Join the Digital Factory Mastermindhttps://www.iiot.university/digital-mastermind Thanks for watching! Subscribe!
All the deets of the New Libsyn release, including, dark mode, text snippets and OMGosh social media publishing, where did the Apple summary tag go? Video gear updates, Podcash, how to get the best audience stats, geographic and user agent stats! Sign up for our New Libsyn Webinar! Audience feedback drives the show. We'd love for you to contact us and keep the conversation going! Email thefeed@libsyn.com, call 412–573–1934 or leave us a message on Speakpipe! We'd love to hear from you! SIGN UP FOR OUR NEWSLETTER HERE! Quick Episode Summary :13 Intro 2:54 PROMO 1: Use of Force 3:23 Rob and Elsie conversation The snow came! And did all kinds of things! 7:03 The New Libsyn! What we released! No new user name or password need and there are no additional fees If you need to go back, you can by logging in to Libsyn 4 Dark mode! Canva integration! Text snippets! Fancy stats! The player! 18:46 the new social media publishing 26:28 Supporting the Podcast 2.0 Namespace through the locked tag Permalink, and podcast page updates 32:05 sign up page updates! No. More. Slugs. 34:44 The Apple Summary field was removed and why More advertising tools added to Libsyn 5 37:14 Elsie's turning 50 and she's buying video gear to celebrate Talking about Podcash and what do folks have to do when they win? 45:34 Promo 2: The Strokecast 46:19 Where can one get the best listener downloads? Breaking down server side and client side stats 49:06 Where can we find the Instagram Reels webinar (and all the other ones?) Best practices for adding meta data for guests on your podcast Looking back to stats, and why there aren't IAB stats before July 2019? 55:32 Promo 3: Educational Duct Tape Podcast 56:05 Stats: Geographic and user agent Facebook responds to pre-loading and IAB stats Where have we been and where are we going? Featured Podcast Promo + Audio PROMO 1: Use of Force PROMO 2: Strokecast PROMO 3: Educational Duct Tape Podcast Thank you to Nick from MicMe for our awesome intro! Podcasting Articles and Links mentioned by Rob and Elsie Leave us voice feedback! Welcome To The New Libsyn If you want Libsyn 4, go here and bookmark! Four.libsyn.com Sony Alpha ZV-E10 eCamm Live TMP100 Podcash [The Reels Webinar]((https://www.youtube.com/watch?v=YiDtRPnpHJA&t=1s) Follow Libsyn on Crowdcast for all upcoming webinars The Libsyn YouTube Channel - subscribe! TikTok and growing your podcast webinar Welcome to the New Libsyn Webinar HELP US SPREAD THE WORD! We'd love it if you could please share The Feed with your Twitter followers. Click here to post a tweet! If you dug this episode, head over to Podchaser and kindly leave us a review and follow the show! Follow The Feed wherever you listen to audio! → Follow via Apple Podcasts → Follow via Google Podcasts → Follow via Spotify → Here's our RSS feed! FEEDBACK AND PROMOTION ON THE SHOW You can ask your questions, make comments and create a segment about podcasting for podcasters! Let your voice be heard. Download The Feed App for iOS and Android Call 412–573–1934 Email thefeed@libsyn.com Use our Speakpipe Page
All the deets of the New Libsyn release, including, dark mode, text snippets and OMGosh social media publishing, where did the Apple summary tag go? Video gear updates, Podcash, how to get the best audience stats, geographic and user agent stats! Sign up for our New Libsyn Webinar! Audience feedback drives the show. We'd love for you to contact us and keep the conversation going! Email thefeed@libsyn.com, call 412–573–1934 or leave us a message on Speakpipe! We'd love to hear from you! SIGN UP FOR OUR NEWSLETTER HERE! Quick Episode Summary :13 Intro 2:54 PROMO 1: Use of Force 3:23 Rob and Elsie conversation The snow came! And did all kinds of things! 7:03 The New Libsyn! What we released! No new user name or password need and there are no additional fees If you need to go back, you can by logging in to Libsyn 4 Dark mode! Canva integration! Text snippets! Fancy stats! The player! 18:46 the new social media publishing 26:28 Supporting the Podcast 2.0 Namespace through the locked tag Permalink, and podcast page updates 32:05 sign up page updates! No. More. Slugs. 34:44 The Apple Summary field was removed and why More advertising tools added to Libsyn 5 37:14 Elsie's turning 50 and she's buying video gear to celebrate Talking about Podcash and what do folks have to do when they win? 45:34 Promo 2: The Strokecast 46:19 Where can one get the best listener downloads? Breaking down server side and client side stats 49:06 Where can we find the Instagram Reels webinar (and all the other ones?) Best practices for adding meta data for guests on your podcast Looking back to stats, and why there aren't IAB stats before July 2019? 55:32 Promo 3: Educational Duct Tape Podcast 56:05 Stats: Geographic and user agent Facebook responds to pre-loading and IAB stats Where have we been and where are we going? Featured Podcast Promo + Audio PROMO 1: Use of Force PROMO 2: Strokecast PROMO 3: Educational Duct Tape Podcast Thank you to Nick from MicMe for our awesome intro! Podcasting Articles and Links mentioned by Rob and Elsie Leave us voice feedback! Welcome To The New Libsyn If you want Libsyn 4, go here and bookmark! Four.libsyn.com Sony Alpha ZV-E10 eCamm Live TMP100 Podcash [The Reels Webinar]((https://www.youtube.com/watch?v=YiDtRPnpHJA&t=1s) Follow Libsyn on Crowdcast for all upcoming webinars The Libsyn YouTube Channel - subscribe! TikTok and growing your podcast webinar Welcome to the New Libsyn Webinar HELP US SPREAD THE WORD! We'd love it if you could please share The Feed with your Twitter followers. Click here to post a tweet! If you dug this episode, head over to Podchaser and kindly leave us a review and follow the show! Follow The Feed wherever you listen to audio! → Follow via Apple Podcasts → Follow via Google Podcasts → Follow via Spotify → Here's our RSS feed! FEEDBACK AND PROMOTION ON THE SHOW You can ask your questions, make comments and create a segment about podcasting for podcasters! Let your voice be heard. Download The Feed App for iOS and Android Call 412–573–1934 Email thefeed@libsyn.com Use our Speakpipe Page
A new initiative uses open source to keep podcasting decentralized and add new features. We chatted with Dave Jones behind the Podcast Index. Special Guest: Dave Jones.
Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio.Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: Literature Review For Academic Outsiders: What, How, and Why , published by namespace on LessWrong. This is a linkpost for A few years ago I wrote a comment on LessWrong about how most authors on the site probably don't know how to do a literature review: On the one hand, I too resent that LW is basically an insight porn factory near completely devoid of scholarship. On the other hand, this is not a useful comment. I can think of at least two things you could have done to make this a useful comment: Specified even a general direction of where you feel the body of economic literature could have been engaged. I know you might resent doing someone elses research for them if you're not already familiar with said body, but frankly the norm right now is to post webs spun from the fibrous extrusions of peoples musing thoughts. The system equilibrium isn't going to change unless some effort is invested into moving it. Notice you could write your comment on most posts while only changing a few words. Provide advice on how one might go about engaging with ‘the body of economic literature'. Many people are intelligent and reasonably well informed, but not academics. Taking this as an excuse to mark them swamp creatures beyond assistance is both lazy and makes the world worse. You could even link to reasonably well written guides from someone else if you don't want to invest the effort (entirely understandable). I also linked a guide from Harvard's library (Garson & Lillvick, 2012) on how to do a literature review. But this guide makes extensive use of flash video, which makes it increasingly hard to access the content. Even if flash was alive and well, video is not necessarily the most comfortable format. Worse still, I remember feeling there was a great deal of tacit knowledge excluded from the guide which wouldn't be apparent to someone that isn't already familiar with academic culture. Even if the guide was a perfect representation of how to do an academic literature review, the priorities and types of work put together by LessWrong authors are more outsider science (Dance, 2008) than they are Harvard. For this reason I've had writing a guide to literature review aimed towards academic outsiders on my to-do list for a while. At the same time I'm not interested in reinventing the wheel. This guide is going to focus specifically on filling in the knowledge gaps I would expect from someone who has never stepped foot inside a college campus. The other aspects have been discussed in detail, and where they come up I'll link to external guides. What is a literature review? 'Literature review' the process is a way to become familiar with what work has already been done in a particular field or subject by searching for and studying previous work. A 'literature review' is a document (often a small portion of a larger work) which summarizes and analyzes the body of previous work that was encountered during literature review, often in the context of some new work that you're doing. Why do literature review? Literature reviews tend to come up in two major contexts: As a preliminary study to help contextualize a novel work, or as a work itself to summarize the state of a field or synthesize concepts to create new ideas. Most of my research falls into the latter category, I'm a big fan of putting together existing evidence and ideas to synthesize models (namespace, 2020). Gwern also tends to do work in this style (Branwen, 2020). I suspect that a lot of authors on LessWrong are attempting to do this, but fail to really say anything useful because they haven't figured out how to incorporate thorough evidence into their argument. When I did a r...
Thank you HiveMQ for sponsoring this live Stream. Check out their MQTT Broker at https://www.hivemq.com Watch the HiveMQ & HighByte Webinar
Listen to James Cridland and Sam Sethi GUESTS: Bailey Drake - Back Stage by HeadlinerBenjamin Bellamy - CEO Ad AuresNEWS: Spotify released its Q3/21 results. It has 3.2m podcasts on its platform (subtext: beating Apple). Earnings were buoyed by growth in podcast advertisingSpotify is to add video podcasts, but probably not as you know them. You can only upload them via Anchor - there's a waitlist to join - and you can only watch the videos on SpotifyFacebook's Chelsea White and Irena Lam appeared on The New Media Show. Now everyone can get their podcast into FacebookShadow is a new podcast app for iOS which includes SharePlay, so you can listen to a podcast with friends. Here are some promo codes for a free year of Shadow+LJP74J6NR6YJ3LHW3LKTHJ6XYKRWRFPNJTHE3K3M3JY4MXAXWFW34X34FJHRLINKS: Tom Webster has shared a video of his keynote at Podcast Movement; and focused on what Facebook might mean for podcasters Nick Hilton - wrote a blog called It's Time to End Podcast Self-Promo on Twitter Matt Deegan wrote Getting to know your listeners and the audio market. What is more interesting is the report on how listener behaviour has changed during Covid Adam Bowie does a great in-depth analysisHeather Osgood's “Podcast Advertising Playbook” this week with Bryan Barletta talking about YouTube podcasting
Leading the Bleeding: The Intersection of Podcasting and Bitcoin
On September 2nd, 2021 about 15-20 podcasters got together to talk about the value for value model where podcasters can receive bitcoin from their audience using apps from newpodcastapps.com At this point, it is very VERY early in the process, and there are some speed bumps along the way. TUTORIALS ON USING SATOSHIS.STREAM Video - Dave Jackson https://youtu.be/tpY1UD6a3gQ Written - James Cridland How to do value4value and earn Bitcoin from your podcast CHECK OUT OUR RESOURCES leadingthebleeding.com/resources TOPICS 00:35 CryptoCurrency 01:07 But What About Bitcoin Alternatives? 02:46 Namespace is??? 03:20 The Openness of the Namespace 04:10 Three Options to Set Up Your Podcast 05:55 Boostagram 06:46 The Advantage of Hosting Your Own Node? 08:27 Wallets 16:20 Adding Your Show to Podcastindex.org 18:24 Setting Up a Listener 25:45 Evaluating Income 26:24 The Telegram Apps 28:14 How Do I Know This is Working? 28:47 Show Only V4V Shows MENTIONED IN THIS EPISODE Podcast Index http://www.podcastindex.org Podcasterwallet.com Used to submit your show to podcastindex.org or to claim a show that is already there. Telegram App https://telegram.org/ Used by Satosshis.stream to allow you to track your progress. School of Podcasting https://www.schoolofpodcasting.com Libsyn.com Podcast Media Hosting https://www.libsyn.com Use the coupon code sopfree to get a full free month. Zapp App https://zaphq.io/ Podcast Index Social https://podcastindex.social/ Video For US Listeners https://youtu.be/Wo8YyHd_9xc Find Value in this Episode? Buy Me a Coffee https://www.buymeacoffee.com/davejackson PARTICIPANTS Daniel J Lewis www.theaudacitytopodcast.com James Cridland www.podnews.net Evo Tera podcastpontifications.com/ Anu Bhardwaj www.sheqonomi.com Paul Colligan paulcolligan.com Rick www.drinkwithrick.com Six of Swords www.occultfan.com Gary Arndt Everything Everywhere Daily Jennifer Navarrete www.cryptocontentcreators.com GET THE LATEST UPDATES VIA THE NEWSLETTER https://www.leadingthebleeding.com/p/newsletter/
This week's Pipeliners Podcast episode features first-time guest Aron Semle of HighByte discussing the application of IIoT, MQTT, Sparkplug B, and the Universal Namespace to the pipeline industry. In this episode, you will learn about the latest IIoT technology available for use in pipeline industry, how IIoT technology is cutting days/weeks/months of effort down to minutes, the capabilities to structure data all the way to remote devices, the importance of the universal namespace to unify real-time data, and many more exciting technological developments that can simplify complex tasks for pipeliners. - Access the show notes and full episode transcript at PipelinersPodcast.com.
Scaling of Industrial IoT solutions requires a Unified Namespace, which acts as a centralized repository of data, information, and context where any application or device can consume or publish data needed for a specific action. A place where everything is a node within an ecosystem Best described as “What one node knows, all nodes know” If a Unified Namespace is so important, why do most of us not know what the heck it is and how to achieve it? In this week's episode, we talk about the concept of a Unified Namespace strategy early in our Digital Transformation journey to ensure the full potential of your investment and that it can scale. I am pleased to welcome David Shultz of G5 Consulting to discuss architecting a digital transformation solution. Connect with our Guest Here: David Schultz - https://www.linkedin.com/in/thedavidschultz/ If your company sells products or services to engaged maintenance & reliability professionals, tell your marketing manager about Maintenance Disrupted. If you'd like to discuss advertising, please email us at maintenancedisrupted@gmail.com Check out our website at www.maintenancedisrupted.com and sign up for the weekly disruption newsletter with bonus content. If you like the show, please tell your colleagues about it and follow maintenance disrupted on LinkedIn and YouTube. Follow Maintenance Disrupted on LinkedIn https://www.linkedin.com/company/maintenancedisrupted Music: The Descent by Kevin MacLeod Link: https://incompetech.filmmusic.io/song/4490-the-descent License: http://creativecommons.org/licenses/by/4.0/
I love it when people correct me! Andy Lehman tells me all about what I didn't get quite right about the Podcast Namespace.
Podcast etiquette, the power of clean HTML, Hopin acquisition of Streamyard, podcasters with COVID, Apple Spotlight and subscription speculation, clarifications, updated ad insertion tools, the power of Destinations, square vs wide format podcast art, geographic and user agent stats and oh, so much more
I conclude my thoughts, that I started right before I got sick about the new tags in the podcast 2.0 namespace. This time I share how I see these being used to improve the experience for all podcast listeners. If you want to know more you can find the tags… I conclude my thoughts, that I started right before I got sick about the new tags in the podcast 2.0 namespace. This time I share how I see these being used to improve the experience for all podcast listeners. If you want to know more you can find the tags…
Podcast etiquette, the power of clean HTML, Hopin acquisition of Streamyard, podcasters with COVID, Apple Spotlight and subscription speculation, clarifications, updated ad insertion tools, the power of Destinations, square vs wide format podcast art, geographic and user agent stats and oh, so much more
This is the Industry 4.0 Live Q&A from 1/19/21 edited and reuploaded. Here are the question topics are broken down with timestamps for quickly finding the question you want to be answered! 0:00 Intro 0:50 Community Updates 7:08 Community Shout-Outs 11:00 Are there any CMMS or MES on the market which are ISA-95 compliant? 12:54 FrameworX University Launch Event Agenda 16:36 Where does the Historian fit in the IIoT Unified Namespace? 20:00 Enterprise-Wide Unified Namespace Example 37:17 How to qualify software vendors as open architecture? 40:35 Should I use a shop floor DMZ for an Industry 4.0 Solution? 44:20 How to normalize analog and discrete variables over time? 50:25 Will MES 4.0 be available for Ignition and FrameworX? 50:45 Can Cybus.io serve as the Unified Namespace? Thanks for watching! Subscribe!
This is the Industry 4.0 Live Q&A from 1/19/21 edited and reuploaded. Here are the question topics are broken down with timestamps for quickly finding the question you want to be answered! 0:00 Intro 0:50 Community Updates 7:08 Community Shout-Outs 11:00 Are there any CMMS or MES on the market which are ISA-95 compliant? 12:54 FrameworX University Launch Event Agenda 16:36 Where does the Historian fit in the IIoT Unified Namespace? 20:00 Enterprise-Wide Unified Namespace Example 37:17 How to qualify software vendors as open architecture? 40:35 Should I use a shop floor DMZ for an Industry 4.0 Solution? 44:20 How to normalize analog and discrete variables over time? 50:25 Will MES 4.0 be available for Ignition and FrameworX? 50:45 Can Cybus.io serve as the Unified Namespace? Thanks for watching! Subscribe!
En @NotiPodHoy ✅ Las nuevas reglas de privacidad de WhatsApp provocan un éxodo y ejecutivos de FB e Instagram tratan de aclarar la información. ✅ 5 cosas que debes saber sobre la audiencia de podcasts. ✅ 8 métricas de datos de podcasts que pueden generar conocimiento sin comprometer la privacidad del oyente. ➽ Los alojadores de pódcast Buzzsprout y Blubrry anuncian nuevas funciones. ➽ Descript, recibe US$30 millones de inversionistas. ➽ Un análisis en Bloomberg dice que el objetivo de Spotify es conseguir más Joe Rogan para hacer crecer su negocio. ➽ Podcast Index & Podcast 2.0 Namespace: ¿qué es? ➽ El equipo de Breaker se une a Twitter pero la aplicación no desaparece.
In this video, Walker Reynolds answers several questions in detail that came up here on YouTube and in the Industry 4.0 Community Discord Server. We wanted to share these answers here on YouTube because they get asked often and we think it will help answer some of your questions on the details of the Unified Namespace and how it works. Thanks for watching! Subscribe!
In this video, Walker Reynolds answers several questions in detail that came up here on YouTube and in the Industry 4.0 Community Discord Server. We wanted to share these answers here on YouTube because they get asked often and we think it will help answer some of your questions on the details of the Unified Namespace and how it works. Thanks for watching! Subscribe!
Shownotes Podcasting 2.0 for January 1st 2021 Episode 18: Taking a Tenet The guy who put the D-J in Top40 Radio, a renaissance man of the 21st century - I give you Mr. Dave Jones Crank those value sliders up everyone! Download the mp3 Check out the podcasting 2.0 apps and services newpodcastapps.com Support us with your Time Talent and Treasure Check out all the 2.0 apps and hosting companies: newpodcastapps.com Shownotes Adam & Dave discuss the week's developments on podcastindex.org Dan Benjamin Founder of Fireside.FM Stacking Sats Namespace -> Castopod IPFS IPNS Lightining Sphinx Breeze Strike Voltage Keywords
Shownotes Podcasting 2.0 for December 4th 2020 Episode 14: Stats and Facts Crank those value sliders up everyone! Download the mp3 Support us with your Time Talent and Treasure Shownotes Adam & Dave discuss the week's developments on podcastindex.org Dave's Podcast Interview Community Chapters Namespace Value running through sphinx Keywords
Shownotes Podcasting 2.0 for November 20th 2020 Episode 12: Breaking Code And now, the man who did a decade's work in 3 months - Dave "The Namespace Slayer" Jones! Crank those value sliders up everyone! Download the mp3 Support us with your Time Talent and Treasure Shownotes Adam & Dave discuss the week's developments on podcastindex.org Captions Bug Android Namespace lockdown Lock Chapter Transcript/Captions Funding Soundbite Phase 2 tags Person Season Location Value Hosters update Austin Bitcoin meetup Tribes rockin' Breeze reference app Keywords
Show Notes Podcasting 2.0 for October 23d 2020 Episode 8: Or is it Chapter 8? Download the mp3 Support us with your Time Talent and Treasure Shownotes Adam & Dave discuss the week's developments on podcastindex.org The man who parses XML faster than JSON, The Dev From The Deep South - Dave Jones Technology History lessons in Schools Chapters and interactivity Locktag Funding Tag Transcript tag The Namespace timing, phases and process Digital money and podcasting Keywords
PHP Internals News: Episode 66: Namespace Token, and Parsing PHP London, UK Thursday, August 13th 2020, 09:29 BST In this episode of "PHP Internals News" I chat with Nikita Popov (Twitter, GitHub, Website) about his Namespaced Names as a Single Token, and Parsing PHP. The RSS feed for this podcast is https://derickrethans.nl/feed-phpinternalsnews.xml, you can download this episode's MP3 file, and it's available on Spotify and iTunes. There is a dedicated website: https://phpinternals.news Transcript Derick Rethans 0:16 Hi, I'm Derick, and this is PHP internals news, a weekly podcast dedicated to demystifying the development of the PHP language. This is Episode 66. Today I'm talking with Nikita Popov about an RFC that he's made, called namespace names as token. Hello Nikita, how are you this morning? Nikita 0:35 I'm fine Derick, how are you? Derick Rethans 0:38 I'm good as well, it's really warm here two moments and only getting hotter and so. Nikita 0:44 Same here. Same here. Derick Rethans 0:46 Yeah, all over Europe, I suppose. Anyway, let's get chatting about the RFC otherwise we end up chatting about the weather for the whole 20 minutes. What is the problem that is RFC is trying to solve? Nikita 0:58 So this RFC tries to solve two problems. One is the original one, and the other one turned up a bit later. So I'll start with the original one. The problem is that PHP has a fairly large number of different reserved keyword, things like class, like function, like const, and these reserved keywords, cannot be used as identifiers, so you cannot have a class that has the name list. Because list is also a keyword that's used for array destructuring. We have some relaxed rules in some places, which were introduced in PHP 7.0 I think. For example, you can have a method name, that's a reserved keyword, so you can have a method called list. Because we can always disambiguate, this versus the like real list keyword. But there are places where you cannot use keywords and one of those is inside namespace names. So to give a specific example of code that broke, and that was my, my own code. So, I think with PHP 7.4, we introduced the arrow functions with the fn keyword to work around various parsing issues. And I have a library called Iter, which provides various generator based iteration functions. And this library has a namespace Iterfn. So Iter backslash fn. Because it has this fn keyword as part of the name, this library breaks in PHP 7.4. But the thing is that this is not truly unnecessary breakage. Because if we just write Iter backslash fn, there is no real ambiguity there. The only thing this can be is a namespace name, and similarly if you import this namespace then the way you actually call the functions is using something like fn backslash operator. Now once again you have fn directly before a backslash so there is once again no real ambiguity. Where the actual ambiguity comes from is that we don't treat namespace names as a single unit. Instead, we really do treat them as the separate parts. First one identifier than the backslash, then other identifier, then the backslash, and so on. And this means that our reserved keyword restrictions apply to each individual part. So the whole thing. The original idea behind this proposal was actually to go quite a bit further. The proposal is that instead of treating all of these segments of the name separately, we treat it as a single unit, as a single token. And that also means that it's okay to use reserved keywords inside it. As long as like the whole name, taken together is not a reserved keyword. The idea of the RFC was to, like, reduce the impact of additional reserved keywords, introduced in the future so in PHP eight we added the match keyword, which can cause similar issues, and in PHP 8.1 maybe we're going to add an enum keyword, and so on. Each time we add a keyword we're breaking code. The idea of this RFC was to reduce the breakage, and the original proposal, not just allowed these reserved keywords inside namespace names, but also removed the restrictions we have on class names and function names and so on. So you would actually be able to do something like class Match. Then, if you wanted to use the class, you would have to properly disambiguate it. For example, by using a fully qualified name, starting with a backslash or by well or using any other kind of qualified name. So you wouldn't be able to use an isolated match, but you could use backslash match, or some kind of things they just named backslash match. However, in the end, I dropped support for this part of the RFC, because there were some concerns that would be confusing. For example if you write something like isset x, that would call the isset on built in language construct. And if you wrote backslash isset x, that would call a user defined, isset function, because we no longer have this reserved keyword restriction. While this is like an ambiguous from a language perspective, the programmer might get somewhat confused. So if we want to go in this direction we probably want to add more validation about which reserved keywords are allowed in certain positions and I didn't want to deal with that at this point. Derick Rethans 5:33 Also by removing it, you make the RFC smaller which gives usually a better chance for getting them accepted anyway. Nikita 5:40 Yes. Derick Rethans 5:41 You mentioned in the introduction that originally you tried to solve the problem of not being able to use reserved keywords in namespace names. It ended up solving another problem that at the moment you wrote this, you wasn't quite aware of. What is this other problem? Nikita 5:57 The other problem is the famous or infamous issue of the attributes syntax, which we are having a hard time solving. The backstory there is that originally the attributes introduced the PHP eight use double angle brackets, or shift operators as delimiters. Derick Rethans 6:18 I've been calling it the pointy one. Nikita 6:20 Okay, the pointy one. And then there was a proposal accepted to instead change this to double at operator at the start, because that's kind of more similar to what other languages do; they use one @, we will use two @s on to avoid the ambiguity with the error suppression operator. Unfortunately, it turned out that as initially proposed the syntax is ambiguous. All because of quite an edge case, I would say. So attributes in PHP are going to be allowed on parameters, and then parameters can have a type. You can have a sequence where you have @@, then the attribute name, then the type name, then the parameter name. And the problem is that because we treat each part of the name separately, between the backslashes, there can also be whitespace in between. So you can have something like a, whitespace, backslash, whitespace, b. Now the question is, in this case does the ab belong to the attribute so is it an attribute name, or is only the a an attribute name, and b is the type name of the parameter. Yeah that's ambiguous and we can't really resolve it unless we have some kind of arbitrary rule, and while the original proposal did introduce an arbitrary rule that the attribute name cannot contain whitespace, it will be interpreted in a particular way. And what this proposal, effectively does is to instead say that names, generally cannot contain whitespace. Derick Rethans 8:01 Your namespace names as token RFC basically disallows spaces for namespace names which you currently can have? Nikita 8:10 Right. So I don't think anyone intentionally uses whitespace inside namespace names. Or actually, you could even have comments inside them. But it is currently technically allowed, and one might introduce it as a typo. That means that this change is a backwards compatibility break. Because you can have currently whitespace in names, but based on static analysis of open source projects, we found that this is pretty rare. So I think we found something like five occurrences inside the top thousand packages. There is one other backwards compatibility break that is in practice I think much more serious. And that's the fact that it changes our token representation. So instead of representing just names as a string separates a string. We now have three different tokens, which is the one for qualified names, one for fully qualified names. So with everything backslash and one for namespace relative names, which is if you have namespace backslash at the start, and namespace I mean, here literally. So this is a very rarely used on PHP feature. Derick Rethans 9:26 I did not know it existed. Nikita 9:28 I also actually did some analysis for that I found very few uses in the wild. I think mostly people writing the static analysis tools know about that, no one else. But the other problem is that this breaks static analysis tools because they now have to deal with a new token representation. Derick Rethans 9:47 We have been talking about these tokens. What are tokens on like the smallest level. Nikita 9:51 PHP has, what's a three phase compilation process where first we convert the raw source code, which is just a sequence of characters into tokens, which are slightly larger semantic units. So instead of having only characters we recognize reserved keywords and recognize identifiers and operators, and so on. Then on the second phase, we have the parser which converts these individual tokens into larger semantic structures like addition expression, or an assignment expression or class expression and so on. Finally we convert the result of that which is a parse tree or an abstract syntax tree into our actual virtual machine instructions, our bytecode representation. Derick Rethans 10:41 And then PHP eight down to machine code, if the JIT kicks in. I remember from a long time ago when I was in uni, is that there are different kinds of parsers and from what I understand PHP's parser is a context free parser. What is is a context free parser? Nikita 10:57 Well a context free in particular is a term from the CompSci theory, where we separate parsers into four languages, into four levels, though I think this is not a super useful distinction, when it comes to language parsing. Because general context free parser has complexity of O(n^3). Like if you have a very large file, it will take very long to parse it could be with the general context free parser. So what we'll be do in practice are more like deterministic context free languages, which is a smaller set. The formal definition there are a set that can be parsed by deterministic push down automaton but I don't think you want to go there. Derick Rethans 11:41 No, not today. Nikita 11:44 Because in practice actually what we do in PHP is even more limited than that. So the parser we use in PHP is called LA/LR1 parser. So that's a look ahead, left to right, right most derivation parser Derick Rethans 11:59 Also mouthful, but it's simpler to explain. Nikita 12:02 I think really the most relevant parts of this algorithm to us is the "1". What the one means is that we can only use a single look ahead token. When we recognize some kind of structure, we have to be able to recognize it by looking at the current token, and that the next token. At each parsing step, those two things have to be sufficient to recognize and to disambiguate syntax. Actually even more restrictive than that but I think that's a good mental model. This is really, I think the core problem we often have when introducing new syntax, so this is the problem we had with the short arrow syntax, short closure syntax. There we would need not one token of look ahead but an infinite potentially in finite number of look ahead. Derick Rethans 12:55 In case the function keyword is still being used. Nikita 12:59 Yes, that's why we added the fn keyword to what the problem because with the fn keyword we can immediately say at the start of the start of the arrow function that this is an arrow function. And we will have similar problems if we introduce generics in the future, at which point we might actually just give up and switch to a more powerful parser. The parser generator we use, which is bison, has two modes. One is the LA/LR mode. And the other one is the GLR mode. They both use the same base parsing algorithm at first, but the GLR mode allows forking it. So if it encounters an ambiguity, it will actually like try to pursue both possibilities, which is of course a lot less efficient, but it allows us to parse more ambiguous structures. Derick Rethans 13:50 Wouldn't that not cause a problem that has some cases because every token will be ambiguous, it will explode in like an exponential way? Nikita 13:57 Yes, I mean it's worst case exponential. But if you like have a careful choice of where you are ambiguous, then you can see that okay with this particular ambiguity, you can actually get worse still linear for valid code. Derick Rethans 14:14 That makes a decision between two possibilities pretty much at that stage. Nikita 14:18 But I think the danger there is that one might not notice when one introduces ambiguities, or maybe not real syntax ambiguities, you do tend to notice those. But ambiguities on the parser level where the parser cannot distinguish possibilities based on the single token for get. Derick Rethans 14:41 Was there in the past being ambiguities introducing a PHP language, that we fail to see? Nikita 14:46 I don't think so. I mean, because we use this parser generator. It tells us if we have ambiguities, so either in the form of shift/reduce or reduce/reduce conflicts. So we cannot really introduce ambiguities. We can it's possible to suppress them, and we actually did have a couple of suppressed conflicts in the past, this was for one particular very well known ambiguity, which is the dangling elseif/else. Basically that the else part of an ifelse. So if you have a nested if without braces. Then there is an else afterwards, the else could ever belong to the inner if or to the outer if, but this is like a standard ambiguity in all C like languages that allow omitting two braces. Derick Rethans 15:35 That's why coding standard say: Always use braces. The patch belonging to this RFC has been merged. So it means that in PHP eight we'll have the longer or the new token names. Do you think that in the future we'll have to make similar choices or similar adjustments to be able to add more syntax? Nikita 15:56 Yes. As I was already saying before, I think these syntax conflicts, they crop up pretty often. This is like very much not an isolated occurrence. If it's really fundamental. If there are any fundamental problems in the PHP syntax where we made bad choices. I think it's pretty normal that you do run into conflicts at some point. So, especially when it comes to generics using angle brackets, in pretty much all languages I deal with my major parsing issues when it comes to that. For example Rust has the famous turbo fish operator, where you have to like write something like colon colon angle brackets to disambiguate things in this specific situation. Derick Rethans 16:49 I just listened to a podcast on the Go language where they're also talking about adding generics, and they had the exact same issue with parsing it. I think they ended up going for the square bracket syntax instead of the angle brackets, or the pointies, as I mentioned. Nikita 17:04 Everyone uses the pointy brackets syntax, despite all those parsing issues because everyone else use it. For PHP for example, we wouldn't be able to use square brackets, because those are used for array access, and that would be completely ambiguous, but we could use curly braces. Well, people have told me that they would not appreciate that. Let's say it like this. Derick Rethans 17:31 Is it's finally time to start using the Unicode characters for syntax? No! Nikita 17:38 Although I did see that, apparently, some people use non breaking spaces inside their test names, because it looks nice and is pretty crazy. Derick Rethans 17:49 I like using it in my class names as well instead of using study caps. Nikita 17:52 I hope that's a joke, you can ever tell. Derick Rethans 17:54 I like using emojis instead. That's also a joke, but I do use it in my presentations and my slides just to jazz them up a little bit. Nikita 18:01 This is an advantage of PHP, because our Unicode support in identifiers works because the files are in UTF-8. That means that all the non ASCII characters have the top bit set, and we just allow all characters with a top bit set as identifiers. And that means that there is no validation at all that identifiers used contain only like identifier or letter characters, so you can use all of the emojis and whitespace characters and so on, you won't have any restrictions. Derick Rethans 18:36 And that was possible for as long as PHP 3 as far as I know. It's a curious thing because this is something that popped up quite a lot when we're discussing, or arguing, about Unicode. You shouldn't allow Unicode because then you can have funny characters in your function names like accented characters and stuff like that, and then also always fun to point out that yeah you could have done that since 1997. Anyhow, would you have anything else to add? Nikita 19:01 I don't think so. Derick Rethans 19:02 Well thank you very much for having a chat with me this morning. And I'm sure we'll see each other at some other point in the future. Nikita 19:09 Thanks for having me once again Derick. Derick Rethans 19:12 Thanks for listening to this instalment of PHP internals news, the weekly podcast dedicated to demystifying the development of the PHP language. I maintain a Patreon account for supporters of this podcast, as well as the Xdebug debugging tool, you can sign up for Patreon at https://drck.me/patreon. If you have comments or suggestions, feel free to email them to derick@phpinternals.news. Thank you for listening, and I'll see you next week. Show Notes RFC: Treat namespaced names as single token GLR Parser LALR(1) Parser Iter Library RFC: Match expression Credits Music: Chipper Doodle v2 — Kevin MacLeod (incompetech.com) — Creative Commons: By Attribution 3.0
Once people understand the concept of IIoT and understand the value of the Unified Namespace, the most common question we get is: What software can be used as the IIoT Unified Namespace? Or can I use Kepware or software-x as my Unified Namespace? In this video, Walker Reynolds answers that question! Thanks for listening! Subscribe!
Once people understand the concept of IIoT and understand the value of the Unified Namespace, the most common question we get is: What software can be used as the IIoT Unified Namespace? Or can I use Kepware or software-x as my Unified Namespace? In this video, Walker Reynolds answers that question! Thanks for listening! Subscribe!
- O que é um Namespace - Nome único da organização - Só necessário para ORGs que de Pacotes (AppExchange) - Similaridade com outros namespace (Android, iOS, c#, Java) - Como configurar? - Uma vez configurado não pode ser removido - Não pode ser alterado - Qual os impactos de ativar o namespace - Problemas que você pode ter durante o desenvolvimento - DescribeObject.getName() e getLocalName() Acompanhe as live de segunda a sexta às 21:41, saiba mais em https://souforce.cloud/lives Siga-nos no Instagram @iFernandoSousa & @Anellinv & @souforce Blog: https://souforce.cloud YouTube: https://youtube.com/souforce Telegram: https://t.me/souforce
#160 - O que é um Manage Package - Transmitido ao vivo em 21/02/2020 1) O que é Manage Package 2) Ponto positivo de usar Manage Package 3) Nível de segurança critico para Manage Package Validados 4) Namespace único 5) Trabalhar com todos os cenários sempre 6) Impossível de testar (Log invisível na org do cliente) 7) Beta vs Release Version 8) Description of the Package Acompanhe as live de segunda a sexta às 21:41, saiba mais em https://souforce.cloud/lives Siga-nos no Instagram @iFernandoSousa & @Anellinv Blog: https://souforce.cloud Cursos: https://cursos.souforce.cloud Youtube: https://youtube.com/souforce
Walker Reynolds and Zack Scriven have an in-depth Q&A style discussion about the Unified Namespace that we talk about on our channel and some of the characteristics you need to be thinking about as you build out your Industry 4.0 and IIoT architecture. As always please leave your questions in the comments for us to get to in future videos. Thanks for watching! Subscribe!
Walker Reynolds and Zack Scriven have an in-depth Q&A style discussion about the Unified Namespace that we talk about on our channel and some of the characteristics you need to be thinking about as you build out your Industry 4.0 and IIoT architecture. As always please leave your questions in the comments for us to get to in future videos. Thanks for watching! Subscribe!
成し遂げたいこと Atelierを大きくする 現在の会社で開発チームを作る SHOWNOTE アトリエ ゲストTwitterID ・ YOU : ＠i_namespace TwitterID ・なべくら : @nabe__kurage ・KANE : @higuyume 音楽 ・魔王魂 収録場所 ・ラボ 詳細 : note.mu/oyakata2438/n/n61dfd82ab189
Steam gets support for Linux namespaces, some distributions are struggling with the shift from Python 2, Arch Linux supports reproducible builds, and GNOME has a new app in beta.
Topics:Infosec Campout report Jay Beale (co-lead for audit) *Bust-a-Kube* Aaron Small (product mgr at GKE/Google) Atreides Partners Trail of Bits What was the Audit? How did it come about? Who were the players? Kubernetes Working Group Aaron, Craig, Jay, Joel Outside vendors: Atredis: Josh, Nathan Keltner Trail of Bits: Stefan Edwards, Bobby Tonic , Dominik Kubernetes Project Leads/Devs Interviewed devs -- this was much of the info that went into the threat model Rapid Risk Assessments - let’s put the GitHub repository in the show notes What did it produce? Vuln Report Threat Model - https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Threat%20Model.pdf White Papers https://github.com/kubernetes/community/tree/master/wg-security-audit/findings Discuss the results: Threat model findings Controls silently fail, leading to a false sense of security Pod Security Policies, Egress Network Rules Audit model isn’t strong enough for non-repudiation By default, API server doesn’t log user movements through system TLS Encryption weaknesses Most components accept cleartext HTTP Boot strapping to add Kubelets is particularly weak Multiple components do not check certificates and/or use self-signed certs HTTPS isn’t enforced Certificates are long-lived, with no revocation capability Etcd doesn’t authenticate connections by default Controllers all Bundled together Confused Deputy: b/c lower priv controllers bundled in same binary as higher Secrets not encrypted at rest by default Etcd doesn’t have signatures on its write-ahead log DoS attack: you can set anti-affinity on your pods to get nothing else scheduled on their nodes Port 10255 has an unauthenticated HTTP server for status and health checking Vulns / Findings (not complete list, but interesting) Hostpath pod security policy bypass via persistent volumes TOCTOU when moving PID to manager’s group Improperly patched directory traversal in kubectl cp Bearer tokens revealed in logs Lots of MitM risk: SSH not checking fingerprints: InsecureIgnoreHostKey gRPC transport seems all set to WithInsecure() HTTPS connections not checking certs Some HTTPS connections are unauthenticated Output encoding on JSON construction This might lead to further work, as JSON can get written to logs that may be consumed elsewhere. Non-constant time check on passwords Lack of re-use / library-ification of code Who will use these findings and how? Devs, google, bad guys? Any new audit tools created from this? Brad geesaman “Hacking and Hardening Kubernetes Clusters by Example [I] - Brad Geesaman, Symantec https://www.youtube.com/watch?v=vTgQLzeBfRU Aaron Small: https://cloud.google.com/blog/products/gcp/precious-cargo-securing-containers-with-kubernetes-engine-18 https://cloud.google.com/blog/products/gcp/exploring-container-security-running-a-tight-ship-with-kubernetes-engine-1-10 https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster CNCF: https://www.youtube.com/watch?v=90kZRyPcRZw Findings: Scope for testing: Source code review (what languages did they have to review?) Golang, shell, ... Networking (discuss the networking *internal* *external* Cryptography (TLS, data stores) AuthN/AuthZ RBAC (which roles were tested? Just admin/non-admin *best practice is no admin/least priv*) Secrets Namespace traversals Namespace claims Methodology: Setup a bunch of environments? Primarily set up a single environment IIRC Combination of code audit and active ?fuzzing? What does one fuzz on a K8s environment? Tested with latest alpha or production versions? Version 1.13 or 1.14 - version locked at whatever was current - K8S releases a new version every 3 months, so this is a challenge and means we have to keep auditing. Tested mulitple different types of k8s implementations? Tested primarily against kubespray (https://github.com/kubernetes-sigs/kubespray) Bug Bounty program: https://github.com/kubernetes/community/blob/master/contributors/guide/bug-bounty.md Check out our Store on Teepub! https://brakesec.com/store Join us on our #Slack Channel! Send a request to @brakesec on Twitter or email bds.podcast@gmail.com #Brakesec Store!:https://www.teepublic.com/user/bdspodcast #Spotify: https://brakesec.com/spotifyBDS #RSS: https://brakesec.com/BrakesecRSS #Youtube Channel: http://www.youtube.com/c/BDSPodcast #iTunes Store Link: https://brakesec.com/BDSiTunes #Google Play Store: https://brakesec.com/BDS-GooglePlay Our main site: https://brakesec.com/bdswebsite #iHeartRadio App: https://brakesec.com/iHeartBrakesec #SoundCloud: https://brakesec.com/SoundcloudBrakesec Comments, Questions, Feedback: bds.podcast@gmail.com Support Brakeing Down Security Podcast by using our #Paypal: https://brakesec.com/PaypalBDS OR our #Patreon https://brakesec.com/BDSPatreon #Twitter: @brakesec @boettcherpwned @bryanbrake @infosystir #Player.FM : https://brakesec.com/BDS-PlayerFM #Stitcher Network: https://brakesec.com/BrakeSecStitcher #TuneIn Radio App: https://brakesec.com/TuneInBrakesec
Topics:Infosec Campout report Derbycon Pizza Party (with podcast show!) https://www.eventbrite.com/e/brakesec-pizza-party-at-the-derbycon-mental-health-village-tickets-69219271705 Mental health village at Derbycon Jay Beale (co-lead for audit) *Bust-a-Kube* Aaron Small (product mgr at GKE/Google) Atreides Partners Trail of Bits What was the Audit? How did it come about? Who were the players? Kubernetes Working Group Aaron, Craig, Jay, Joel Outside vendors: Atredis: Josh, Nathan Keltner Trail of Bits: Stefan Edwards, Bobby Tonic , Dominik Kubernetes Project Leads/Devs Interviewed devs -- this was much of the info that went into the threat model Rapid Risk Assessments - let’s put the GitHub repository in the show notes What did it produce? Vuln Report Threat Model - https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Threat%20Model.pdf White Papers https://github.com/kubernetes/community/tree/master/wg-security-audit/findings Discuss the results: Threat model findings Controls silently fail, leading to a false sense of security Pod Security Policies, Egress Network Rules Audit model isn’t strong enough for non-repudiation By default, API server doesn’t log user movements through system TLS Encryption weaknesses Most components accept cleartext HTTP Boot strapping to add Kubelets is particularly weak Multiple components do not check certificates and/or use self-signed certs HTTPS isn’t enforced Certificates are long-lived, with no revocation capability Etcd doesn’t authenticate connections by default Controllers all Bundled together Confused Deputy: b/c lower priv controllers bundled in same binary as higher Secrets not encrypted at rest by default Etcd doesn’t have signatures on its write-ahead log DoS attack: you can set anti-affinity on your pods to get nothing else scheduled on their nodes Port 10255 has an unauthenticated HTTP server for status and health checking Vulns / Findings (not complete list, but interesting) Hostpath pod security policy bypass via persistent volumes TOCTOU when moving PID to manager’s group Improperly patched directory traversal in kubectl cp Bearer tokens revealed in logs Lots of MitM risk: SSH not checking fingerprints: InsecureIgnoreHostKey gRPC transport seems all set to WithInsecure() HTTPS connections not checking certs Some HTTPS connections are unauthenticated Output encoding on JSON construction This might lead to further work, as JSON can get written to logs that may be consumed elsewhere. Non-constant time check on passwords Lack of re-use / library-ification of code Who will use these findings and how? Devs, google, bad guys? Any new audit tools created from this? Brad geesaman “Hacking and Hardening Kubernetes Clusters by Example [I] - Brad Geesaman, Symantec https://www.youtube.com/watch?v=vTgQLzeBfRU Aaron Small: https://cloud.google.com/blog/products/gcp/precious-cargo-securing-containers-with-kubernetes-engine-18 https://cloud.google.com/blog/products/gcp/exploring-container-security-running-a-tight-ship-with-kubernetes-engine-1-10 https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster CNCF: https://www.youtube.com/watch?v=90kZRyPcRZw Findings: Scope for testing: Source code review (what languages did they have to review?) Golang, shell, ... Networking (discuss the networking *internal* *external* Cryptography (TLS, data stores) AuthN/AuthZ RBAC (which roles were tested? Just admin/non-admin *best practice is no admin/least priv*) Secrets Namespace traversals Namespace claims Methodology: Setup a bunch of environments? Primarily set up a single environment IIRC Combination of code audit and active ?fuzzing? What does one fuzz on a K8s environment? Tested with latest alpha or production versions? Version 1.13 or 1.14 - version locked at whatever was current - K8S releases a new version every 3 months, so this is a challenge and means we have to keep auditing. Tested mulitple different types of k8s implementations? Tested primarily against kubespray (https://github.com/kubernetes-sigs/kubespray) Bug Bounty program: https://github.com/kubernetes/community/blob/master/contributors/guide/bug-bounty.md Check out our Store on Teepub! https://brakesec.com/store Join us on our #Slack Channel! Send a request to @brakesec on Twitter or email bds.podcast@gmail.com #Brakesec Store!:https://www.teepublic.com/user/bdspodcast #Spotify: https://brakesec.com/spotifyBDS #RSS: https://brakesec.com/BrakesecRSS #Youtube Channel: http://www.youtube.com/c/BDSPodcast #iTunes Store Link: https://brakesec.com/BDSiTunes #Google Play Store: https://brakesec.com/BDS-GooglePlay Our main site: https://brakesec.com/bdswebsite #iHeartRadio App: https://brakesec.com/iHeartBrakesec #SoundCloud: https://brakesec.com/SoundcloudBrakesec Comments, Questions, Feedback: bds.podcast@gmail.com Support Brakeing Down Security Podcast by using our #Paypal: https://brakesec.com/PaypalBDS OR our #Patreon https://brakesec.com/BDSPatreon #Twitter: @brakesec @boettcherpwned @bryanbrake @infosystir #Player.FM : https://brakesec.com/BDS-PlayerFM #Stitcher Network: https://brakesec.com/BrakeSecStitcher #TuneIn Radio App: https://brakesec.com/TuneInBrakesec
We try out Debian 10 Buster and cover what's new. There is a fresh Linux distro for Chromebooks that is very appealing, and the ISPA calls Mozilla a villain. Plus why Fucshia OS might be the most significant future threat to Linux.
We try out Debian 10 Buster and cover what's new. There is a fresh Linux distro for Chromebooks that is very appealing, and the ISPA calls Mozilla a villain. Plus why Fucshia OS might be the most significant future threat to Linux.
We try out Debian 10 Buster and cover what's new. There is a fresh Linux distro for Chromebooks that is very appealing, and the ISPA calls Mozilla a villain. Plus why Fucshia OS might be the most significant future threat to Linux.
Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Redisgreen Panel Charles Max Wood Dave Kimura Special Guest: Jason Swett Episode Summary Jason Swett is a former host on Ruby Rogues. Now he has his own show, Ruby Testing Podcast and runs the site codewithjason.com where he teaches Rails testing. Today, Jason discusses turning fat models into skinny POROs (Plain Old Ruby Objects). He once read an article that said you don’t have to put all your code into active record models, that you can create plain ruby objects. These can go into active models if you want, but you’re not limited to active record models, you can make your own classes. This realazition greatly impacted the way he structures his code. The panelists talk about the individual ways the structure their code. Jason discusses other structuring methods he has tried and gives some examples of using skinny POROs in the apps he works on. They discuss the pros and cons of using skinny POROs instead of active models, pros being it cleans up the model and makes testing easier, and the cons being it adds to a bit of overhead to the application, as somebody unfamiliar with the application might recreate parts if you don’t have an index. The panel discusses how to decide when you want to create a new PORO. They talk about each of their methods and discuss the the usefulness of token generators. They conclude that in order for skinny POROs to be effective in code, they must be well factored and organized, and that unfortunately some complexity in code is unavoidable. Links POROs- Plain Old Ruby Objects Model Active record models Namespace Service objects Value objects CSS Form object Tokens Initializer Singleton object Picks Dave Kimura: Reek Kubernetes Charles Max Wood: Cloud66 Podwrench Podcasting booth New podcasts coming to DevChat-- if you want to revive a podcast that has stopped airing, contact Charles Max Wood Programming Podcasters Slack chat Jason Swett: Practical Object Oriented Design in Ruby Ruby Testing Podcast Codewithjason.com
Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Redisgreen Panel Charles Max Wood Dave Kimura Special Guest: Jason Swett Episode Summary Jason Swett is a former host on Ruby Rogues. Now he has his own show, Ruby Testing Podcast and runs the site codewithjason.com where he teaches Rails testing. Today, Jason discusses turning fat models into skinny POROs (Plain Old Ruby Objects). He once read an article that said you don’t have to put all your code into active record models, that you can create plain ruby objects. These can go into active models if you want, but you’re not limited to active record models, you can make your own classes. This realazition greatly impacted the way he structures his code. The panelists talk about the individual ways the structure their code. Jason discusses other structuring methods he has tried and gives some examples of using skinny POROs in the apps he works on. They discuss the pros and cons of using skinny POROs instead of active models, pros being it cleans up the model and makes testing easier, and the cons being it adds to a bit of overhead to the application, as somebody unfamiliar with the application might recreate parts if you don’t have an index. The panel discusses how to decide when you want to create a new PORO. They talk about each of their methods and discuss the the usefulness of token generators. They conclude that in order for skinny POROs to be effective in code, they must be well factored and organized, and that unfortunately some complexity in code is unavoidable. Links POROs- Plain Old Ruby Objects Model Active record models Namespace Service objects Value objects CSS Form object Tokens Initializer Singleton object Picks Dave Kimura: Reek Kubernetes Charles Max Wood: Cloud66 Podwrench Podcasting booth New podcasts coming to DevChat-- if you want to revive a podcast that has stopped airing, contact Charles Max Wood Programming Podcasters Slack chat Jason Swett: Practical Object Oriented Design in Ruby Ruby Testing Podcast Codewithjason.com
Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Redisgreen Panel Charles Max Wood Dave Kimura Special Guest: Jason Swett Episode Summary Jason Swett is a former host on Ruby Rogues. Now he has his own show, Ruby Testing Podcast and runs the site codewithjason.com where he teaches Rails testing. Today, Jason discusses turning fat models into skinny POROs (Plain Old Ruby Objects). He once read an article that said you don’t have to put all your code into active record models, that you can create plain ruby objects. These can go into active models if you want, but you’re not limited to active record models, you can make your own classes. This realazition greatly impacted the way he structures his code. The panelists talk about the individual ways the structure their code. Jason discusses other structuring methods he has tried and gives some examples of using skinny POROs in the apps he works on. They discuss the pros and cons of using skinny POROs instead of active models, pros being it cleans up the model and makes testing easier, and the cons being it adds to a bit of overhead to the application, as somebody unfamiliar with the application might recreate parts if you don’t have an index. The panel discusses how to decide when you want to create a new PORO. They talk about each of their methods and discuss the the usefulness of token generators. They conclude that in order for skinny POROs to be effective in code, they must be well factored and organized, and that unfortunately some complexity in code is unavoidable. Links POROs- Plain Old Ruby Objects Model Active record models Namespace Service objects Value objects CSS Form object Tokens Initializer Singleton object Picks Dave Kimura: Reek Kubernetes Charles Max Wood: Cloud66 Podwrench Podcasting booth New podcasts coming to DevChat-- if you want to revive a podcast that has stopped airing, contact Charles Max Wood Programming Podcasters Slack chat Jason Swett: Practical Object Oriented Design in Ruby Ruby Testing Podcast Codewithjason.com
DF#60#P2 @ Helgi Доброго дня и добро пожаловать. Пятница, вечер, бар "ГАРАЖ" и Deep House музыка. Новая подборка серии Deep Friday. Первая часть лайв микса, House импровизация выходного дня. Немного легкого Deep и напористого Tech House звучания, с элементами эмбиента и этническими вставками. Устраиваемся поудобнее. Слушаем и наслаждаемся. Хорошая музыка для хорошего отдыха. 00:00 01 N'Pot & Nahue Juarez - Endless Summer (Modulo & Monotribe Remix) 07:29 02 Hobo - Daydream (Original Mix) 14:27 03 Guy J - Lamur (Sebastian Leger Mix Low Bpm) 20:39 04 Namespace feat. Amber Long - Turning Back (Original) 26:55 05 Rodrigo Mateo - Carbon Monoxide (Santiago Garcia Remix) 33:37 06 Stan Kolev - Panevritmia 39:33 07 Barja feat. Dazzo - Have Fun (Alok and Gabe Remix) 46:20 08 The Cheapers - Hey Victor (Original Mix) 51:45 09 Kamilo Sanclemente & Juan Pablo Torrez - Anxiety (Original Mix)
DF#60#P2 @ Helgi Доброго дня и добро пожаловать. Пятница, вечер, бар "ГАРАЖ" и Deep House музыка. Новая подборка серии Deep Friday. Первая часть лайв микса, House импровизация выходного дня. Немного легкого Deep и напористого Tech House звучания, с элементами эмбиента и этническими вставками. Устраиваемся поудобнее. Слушаем и наслаждаемся. Хорошая музыка для хорошего отдыха. 00:00 01 N'Pot & Nahue Juarez - Endless Summer (Modulo & Monotribe Remix) 07:29 02 Hobo - Daydream (Original Mix) 14:27 03 Guy J - Lamur (Sebastian Leger Mix Low Bpm) 20:39 04 Namespace feat. Amber Long - Turning Back (Original) 26:55 05 Rodrigo Mateo - Carbon Monoxide (Santiago Garcia Remix) 33:37 06 Stan Kolev - Panevritmia 39:33 07 Barja feat. Dazzo - Have Fun (Alok and Gabe Remix) 46:20 08 The Cheapers - Hey Victor (Original Mix) 51:45 09 Kamilo Sanclemente & Juan Pablo Torrez - Anxiety (Original Mix)
In dieser Folge schauen wir uns an, wie wir in TypeScript Imports von Interfaces und ähnliche Interfaces für CRUD-Operationen vermeiden. Außerdem lästige Warnungen und Fehlermeldung ignorieren – „Ich weiß schon, was ich da tue“.
O kubicast de hoje promete ser o mais técnico de todos os tempos. Para dar conta do desafio fomos ao pampa gaúcho chamar nosso guru Mateus Caruccio que, juntamente com Talita Bernardes Pereira, integra nosso time.Separamos algumas novidades da versão 1.12, aquelas que mais gostamos, funcionalidades que vemos os clientes desejarem e os administradores ansiarem :DVamos às novidades:Política de rede (Stable)ipBlock: permite controlar acesso por range de IP.egress: permite configurar regras de saída de tráfego dos containers.Escolha o runtime para seu pod (Alpha)Mais uma opção de flexibilidade no deploy de seu pod, podendo escolher o runtime de um pod específico (múltiplos runtimes), uma feature muito ligada aos administradores. #NoFatDaemonsPODsCompartilhamento de Namespace dentro do pod, o que facilitará a comunicação de acessos aos PIDs e recursos. Aqui não é o namepsace do kubernetes e sim o namespace do S.O..Volume / StorageAtravés do CSI você poderá criar e restaurar snapshots de um volume em particular, utilizando as APIs do provedor de infraestrutura e sem precisar criar sua própria rotina manualmente.Topology Aware para PVC, onde é criado um delay no bind do PV, aguardando o POD estar pronto para conexão.HPA com Métricas personalizadas e VPA em betaAinda em beta, é uma feature muito aguardada. Permite conectar o HPA com sua métricas customizadas — Saiba mais aqui.Também em beta e talvez a mais aguardada; o Vertical Pod Autoscaler permite escalar verticalmente, adicionando mais poder computacional no pods, em vez de adicionar mais pods como no HPA.Segurança:Bootstrapping do TLSRotação de certificados internos do cluster, ainda em beta.E as recomendações da semana foram:Talita: Compartilhará sobre os “Desafios da Produtividade” no evento Conexão KingHost, inscrevea-se aqui.João: Filme - Desejo de Matar com Bruce WillisMateus: Desenho - Irmão do JorelAlgumas referências: CoreOS e Rancher
Добрый день уважаемые слушатели. Представляем новый выпуск подкаста RWpod. В этом выпуске: Ruby Ruby 2.4 has added additional parameters for Logger#new, Ruby Under The Hood: Memory Layout of an Object и 19 Ruby on Rails Gems which Can Amaze Improve your Ruby application's memory usage and performance with jemalloc, Writing Efficient Queries и Practical Machine Learning with Ruby Migrating from redis-namespace, Webpack 2 and Middleman 4, Rooby - a Ruby-like object oriented language written in Go и Zen Rails Security Checklist JavaScript Headless Chromium, Retiring Octane и Using AngularJS components & directives inside React CodeSandbox makes it easier to create, share and reuse React projects with others, React DOM Confetti - a react component to trigger confetti explosions on state changes и Simple-slider - extremely lightweight JavaScript carousel micro library Prettier - an opinionated JavaScript formatter, Snake * - simple attempt at creating an AI within a game и The Post JavaScript Apocalypse Douglas Crockford
How are namespaces and include files related and why do we need both?
Scope is another concept that is amazingly similar to your everyday experience. Imagine you are at home and ask your mom, Where are my slippers? You mom says, Upstairs. That is scope. And you need to understand it to program. Let me explain.
Catch the show from Friday 14th May if you missed it. Featuring tracks from: Fractal Architect, O.O.R.S. , Underworld, Marshall Watson, Amber Long & Robert Mason, Tuxedo & Monojoke, John Cosano, Audiostorm, Namespace and Kieran J. Enjoy!
Hey there Pheeshes! Here is the latest, live Progreesive House offering from myself, Ali Line. Many things going on at LovePheesh HQ, most notably me having a lil pheesh on the way. Very Exciting! Anyhoo, Tracklisting as follows, I hope you enjoy the mix.: 1. Exoplanet – Paper in the Wind (Arthur Deep Remix) 2. The Scumfrog – Running (Inkfish’s With Scisscors Mix) 3. Le Vinyl – Deep Syndicate 4. NameSpace – Not Found (Nomad in the Dark is Lost Remx) 5. Biologik – Sarin 6. Kenneth Thomas – All is Not Lost (Luiz B Remix) 7. Pacco & Rudy B – Coral Castle (Rodrigo mateo Unofficial Re:Shape) 8. Seb Dhajje – Fifth Season (Pablo Acenso 5th Remix) 9. Donatello, Kastis Torrau & Amas D – Melodrama 10. Wally Lopez & Audio Junkies – Serenade 11. Marc Poppcke – History Repeating (Deepfunk Night Mix) 12. Guy J – Lamur (Federico Monachesi Unofficial Mix 2012) 13. Ormatie – Only (DAVI Remix) Cheers and good health to you all. Ali & All @ LovePheesh. x
Admob purchased by Google. First spotting of Admob by Doyle was in the Wall Street Journal iPhone app. Dave is using Admob in his iPhone app. Google is doing right by acquiring for innovation. Microsoft built an empire on that practice, it works for a while. Writely is Google Docs. Writely from Colorado? Mobile is becoming more important in everything we do. It's critical to marketers.The DROID is a best of class device on Verizon. T-Mobile has the G2, and Sprint the Pre. The DROID is not an iPhone, but the iPhone needs the competition to be a better device. It sold over 100,000 units on the first weekend. It'll at least put pressure on AT&T. There are now options. Ari Newman switched to the DROID and has loved it so far. Competition creates a market. If you don't have competition then you don't have a market. Pressure begets innovation. Jason Mendelson says (at #BOCC ) that he doesn't want to invest in a new piece of fruit. He wants to see competitors in the space. Turn by turn is great on DROID, not available on the iPhone from Google. Competitors are $99 on the iPhone, though Google will release a free one if Apple will approve it. The interface isn't great on the DROID. Michael's son picked up the iPhone's interface at 3 with no help. Apple overtakes Nokia as the most profitable handset maker. David Pogue coins the phrase "App Phone." A phone that accepts apps via download. Dave thinks the consumer doesn't want to have to think about apps. Smart is fine. The handset market is mimicking the desktop space, except Apple is in the lead. Doyle claims the Mac is based on Linux (it's a based on BSD). Goldie Katsu says DROID is a geek's phone at Boulder Open Coffee. Studio audience laughs. Audience attendance is up 1000%.Michael geeks out on the amount of Javascript that's included in the major sites. There's only one namespace in Javascript, which means that every developer has access to everyone else's variables and functions. Possibilities include grabbing form values intended for another site. Namespace may not be the best term. You can't redefine a function name for example. Javascript is not a very secure language, but it's prevalent. It's relevant to us because of the Boulder tech community. HTML5 doesn't fix this problem, since they're two different entities. HTML5 replace some of the functionality of Javascript. HTML5 is more a threat to Adobe with the media tags, etc. Apple saw this coming? Apple has no social media presence, which is generally a worst-practice. Maybe they're not present because the fan base covers Apple enough. There are 6000ish blog posts on Apple every day. Maybe that's why they're successful. Apple's not selling Pepsi (or sugar water). John Scully wrote the preface to one of Dave's books. The Diesel (Michael Spindler) - where is he? Business week had an all black cover with the text "The death of an American icon" and Wired did a crown of thorns and the word "Pray."Black Friday is coming. Year by year more and more Black Friday sales are leaking. Ads just show up on people's blogs. Sales might not be as effective as they used to be. Michael says Black Friday sales should be in person sales only. It would take some business from online sales (though most have online presences anyway). Buying big things online make the reviews a goldmine. Is the review system a replacement for the people in the stores. Do you really trust the person at Best Buy (nothing personal)? Do they tell you what you want to hear or are they giving you what's on sale with the best spiff? Are we elite here? Or do most people get stiffed by sales people? Remember EDTV (Enhanced Definition Television)? nothing more than 480P. Yawn. But grandma bought it up.Retail is evolving to be simple showrooms. Buy now and it arrives in the mail soon. What's next? 3D showrooms? The rise and immediate fall of Cyber-monday was due to dialup and people waiting until Monday to shop on broadband. The battle is now between brick and mortar vs. online sales. Wake up Friday AM, get an email from Target, click, buy, done. So happy it's that easy. Shoppers are not purchasers. We all agree that we're purchasers and don't enjoy the shopping process. We all hang out at the Apple Store because it's fun. We see our peers, and it may have replaced the corner bar and are greeted by the employees. Cheers for the Apple Fanboy. Microsoft store? LOL. It's close... imitation is the sincerest form of flattery. They did a great job! It's a WRAP.Thanks to the studio audience and The B Side Lounge in Boulder, Colorado.
Zend Screencasts: Video Tutorials about the Zend PHP Framework (iphone)
This video covers the Zend_Session_Namespace class. It’s a short introduction to how we can use this object to simplify passing data from Zend_Controller action to another during a user’s stay on our web application.
Die Vorlesung führt in die wichtigsten Konzepte von Webdokumenten anhand des Standards XML ein.
Die Vorlesung führt in die wichtigsten Konzepte von Webdokumenten anhand des Standards XML ein.
En este programa hablamos sobre el uso de Namespace, adicionalmente tratamos un tema de Neurona Help que tiene que ver con recursos para entrarle con todo al desarrollo en .NET 2005 y para terminar platicamos de la reunión de la Comunidad .NET en la Ciudad de México
© 2020-2025 Ivy Podcast Discovery LLC
