# Yahoo Published articles for Yahoo. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Microsoft and Yahoo sign in now available for Firebase Auth DevFeed: [Microsoft and Yahoo sign in now available for Firebase Auth]() Original publisher: [Read original article]() Author: Marc Jordan Published: 2019-03-28T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Authentication](), [OAuth 2.0](), [Mobile](), [Android](), [iOS](), [Web]() Tags: [android](), [auth](), [authentication](), [firebase](), [ios](), [launch](), [microsoft](), [news](), [oauth2](), [sign-in](), [web](), [yahoo]() ### AI overview Firebase Auth now supports sign-in through Microsoft and Yahoo as federated identity providers. The article also describes generic OAuth2 provider sign-in for mobile apps, using web flows on Android and iOS to obtain provider credentials. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Innovating on Authentication Standards DevFeed: [Innovating on Authentication Standards]() Original publisher: [Read original article]() Author: mikesefanov Published: 2018-06-25T13:59:44Z Content type: article Language: en Sources: [Yahoo]() Topics: [Authentication](), [OAuth 2.0](), [Mobile]() Tags: [aol](), [authentication](), [identity](), [mobile](), [mobile-apps](), [oauth2](), [standards](), [yahoo](), [yahoo-engineering]() ### AI overview Yahoo and AOL describe how they used existing identity standards to address migrating identities in mobile apps from a legacy provider to the Oath identity platform. The article focuses on using OAuth 2.0 Token Exchange so apps can move between identity providers without requiring users to re-enter credentials. ### Source excerpt yahoodevelopers: By George Fletcher and Lovlesh Chhabra When Yahoo and AOL came together a year ago as a part of the new Verizon subsidiary Oath, we took on the challenge of unifying their identity platforms based on current identity standards. Identity standards have been a critical part of the Internet ecosystem over the last 20+ years. From single-sign-on and identity federation with SAML; to the newer identity protocols including OpenID Connect, OAuth2, JOSE, and SCIM (to name a few); to the explorations of "self-sovereign identity" based on distributed ledger technologies; standards have played a key role in providing a secure identity layer for the Internet. As we navigated this journey, we ran across a number of different use cases where there was either no standard or no best practice available for our varied and complicated needs. Instead of creating entirely new standards to solve our problems, we found it more productive to use existing standards in new ways. One such use case arose when we realized that we needed to migrate the identity stored in mobile apps from the legacy identity provider to the new Oath identity platform. For most browser (mobile or desktop) use cases, this doesn't present a huge problem; some DNS magic and HTTP redirects and the user will sign in at the correct endpoint. Also it's expected for users accessing services via their browser to have to sign in now and then. However, for mobile applications it's a completely different story. The normal user pattern for mobile apps is for the user to sign in (via OpenID Connect or OAuth2) and for the app to then be issued long-lived tokens (well, the refresh token is long lived) and the user never has to sign in again on the device (entering a password on the device is NOT a good experience for the user). So the issue is, how do we allow the mobile app to move from one identity provider to another without the user having to re-enter their credentials? The solution came from researching what ## Accessing Yahoo and AOL Mail Features Through IMAP DevFeed: [Accessing Yahoo and AOL Mail Features Through IMAP]() Original publisher: [Read original article]() Author: marcelatoath Published: 2018-05-18T16:19:38Z Content type: tutorial Language: en Sources: [Yahoo]() Topics: [Protocol (disambiguation)](), [servers](), [client](), [openssl]() Tags: [aol](), [developers](), [openssl](), [protocol](), [server](), [yahoo](), [yahoo-engineering]() ### AI overview This tutorial explains how developers can access Yahoo and AOL Mail metadata such as DECOS and THREADID through IMAP. It demonstrates an IMAP command sequence using openssl to connect, authenticate, list folders, select the inbox, and search for message UIDs. ### Source excerpt USE IMAP TO ACCESS SOME UNIQUE FEATURES By Libby Lin, Principal Product Manager Well, we actually won't show you how we create the magic in our big OATH consumer mail factory. But nevertheless we wanted to share how interested developers could leverage some of our unique features we offer for our Yahoo and AOL Mail customers. To drive experiences like our travel and shopping smart views or message threading, we tag qualified mails with something we call DECOS and THREADID. While we will not indulge in explaining how exactly we use them internally, we wanted to share how they can be used and accessed through IMAP. So let's just look at a sample IMAP command chain. We'll just assume that you are familiar with the IMAP protocol at this point and you know how to properly talk to an IMAP server. So here's how you would retrieve DECO and THREADIDs for specific messages: 1. CONNECT openssl s_client -crlf -connect imap.mail.yahoo.com:993 2. LOGIN a login username password a OK LOGIN completed 3. LIST FOLDERS a list "" "*" * LIST (\Junk \HasNoChildren) "/" "Bulk Mail" * LIST (\Archive \HasNoChildren) "/" "Archive" * LIST (\Drafts \HasNoChildren) "/" "Draft" * LIST (\HasNoChildren) "/" "Inbox" * LIST (\HasNoChildren) "/" "Notes" * LIST (\Sent \HasNoChildren) "/" "Sent" * LIST (\Trash \HasChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Trash/l2" * LIST (\HasChildren) "/" "test level 1" * LIST (\HasNoChildren) "/" "test level 1/nestedfolder" * LIST (\HasNoChildren) "/" "test level 1/test level 2" * LIST (\HasNoChildren) "/" "&T2BZfXso-" * LIST (\HasNoChildren) "/" "&gQKAqk7WWr12hA-" a OK LIST completed 4.SELECT FOLDER a select inbox * 94 EXISTS * 0 RECENT * OK [UIDVALIDITY 1453335194] UIDs valid * OK [UIDNEXT 40213] Predicted next UID * FLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $Junk $NotJunk) * OK [PERMANENTFLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $Junk $NotJunk)] Permanent flags * OK [HIGHESTMODSEQ 205] a OK [READ-WRITE] SELECT completed; ## Success at Apache: Migrating Yahoo Jobs from Apache MapReduce to Apache Tez DevFeed: [Success at Apache: Migrating Yahoo Jobs from Apache MapReduce to Apache Tez]() Original publisher: [Read original article]() Author: mikesefanov Published: 2018-02-05T14:43:07Z Content type: article Language: en Sources: [Yahoo]() Topics: [Hadoop](), [Open Source](), [data](), [Apache Spark]() Tags: [2017](), [apache](), [blog](), [bug](), [data](), [distributed](), [hadoop](), [hdfs](), [oath](), [open-source](), [spark](), [tez](), [yahoo](), [yahoo-engineering]() ### AI overview Kuhu Shukla describes her experience contributing to Apache projects at Yahoo and migrating Yahoo jobs from Apache MapReduce to Apache Tez. The article also discusses Oath's Apache-based grid infrastructure and her early work with YARN, HDFS, and Hadoop. ### Source excerpt yahoodevelopers: Kuhu Shukla (bottom center) and team at the 2017 DataWorks Summit By Kuhu Shukla This post first appeared here on the Apache Software Foundation blog as part of ASF's "Success at Apache" monthly blog series. As I sit at my desk on a rather frosty morning with my coffee, looking up new JIRAs from the previous day in the Apache Tez project, I feel rather pleased. The latest community release vote is complete, the bug fixes that we so badly needed are in and the new release that we tested out internally on our many thousand strong cluster is looking good. Today I am looking at a new stack trace from a different Apache project process and it is hard to miss how much of the exceptional code I get to look at every day comes from people all around the globe. A contributor leaves a JIRA comment before he goes on to pick up his kid from soccer practice while someone else wakes up to find that her effort on a bug fix for the past two months has finally come to fruition through a binding +1. Yahoo - which joined AOL, HuffPost, Tumblr, Engadget, and many more brands to form the Verizon subsidiary Oath last year - has been at the frontier of open source adoption and contribution since before I was in high school. So while I have no historical trajectories to share, I do have a story on how I found myself in an epic journey of migrating all of Yahoo jobs from Apache MapReduce to Apache Tez, a then-new DAG based execution engine. Oath grid infrastructure is through and through driven by Apache technologies be it storage through HDFS, resource management through YARN, job execution frameworks with Tez and user interface engines such as Hive, Hue, Pig, Sqoop, Spark, Storm. Our grid solution is specifically tailored to Oath's business-critical data pipeline needs using the polymorphic technologies hosted, developed and maintained by the Apache community. On the third day of my job at Yahoo in 2015, I received a YouTube link on An Introduction to Apache Tez. I watched ## How to Make Your Web App More Reliable and Performant Using webpack: a Yahoo Mail Case Study DevFeed: [How to Make Your Web App More Reliable and Performant Using webpack: a Yahoo Mail Case Study]() Original publisher: [Read original article]() Author: mikesefanov Published: 2017-12-13T18:27:36Z Content type: tutorial Language: en Sources: [Yahoo]() Topics: [Webpack](), [web applications](), [JavaScript](), [Development]() Tags: [case-study](), [css](), [dependency](), [developers](), [how-to](), [javascript](), [oath](), [web-app](), [webpack](), [yahoo](), [yahoo-engineering](), [yahoo-mail]() ### AI overview This Yahoo Mail case study explains how the team adopted webpack as its JavaScript module bundler to improve development cycles, reliability, and performance at scale. It describes webpack's dependency-graph and bundling model, plugin selection and development, Grunt integration, and bundle optimization before production deployment. ### Source excerpt yahoodevelopers: By Murali Krishna Bachhu, Anurag Damle, and Utkarsh Shrivastava As engineers on the Yahoo Mail team at Oath, we pride ourselves on the things that matter most to developers: faster development cycles, more reliability, and better performance. Users don't necessarily see these elements, but they certainly feel the difference they make when significant improvements are made. Recently, we were able to upgrade all three of these areas at scale by adopting webpack® as Yahoo Mail's underlying module bundler, and you can do the same for your web application. What is webpack? webpack is an open source module bundler for modern JavaScript applications. When webpack processes your application, it recursively builds a dependency graph that includes every module your application needs. Then it packages all of those modules into a small number of bundles, often only one, to be loaded by the browser. webpack became our choice module bundler not only because it supports on-demand loading, multiple bundle generation, and has a relatively low runtime overhead, but also because it is better suited for web platforms and NodeJS apps and has great community support. Comparison of webpack to other open source bundlers How did we integrate webpack? Like any developer does when integrating a new module bundler, we started integrating webpack into Yahoo Mail by looking at its basic config file. We explored available default webpack plugins as well as third-party webpack plugins and then picked the plugins most suitable for our application. If we didn't find a plugin that suited a specific need, we wrote the webpack plugin ourselves (e.g., We wrote a plugin to execute Atomic CSS scripts in the latest Yahoo Mail experience in order to decrease our overall CSS payload**). During the development process for Yahoo Mail, we needed a way to make sure webpack would continuously run in the background. To make this happen, we decided to use the task runner Grunt. Not only does Grunt ## Yahoo Mail's New Tech Stack, Built for Performance and Reliability DevFeed: [Yahoo Mail's New Tech Stack, Built for Performance and Reliability]() Original publisher: [Read original article]() Author: mikesefanov Published: 2017-06-27T15:51:49Z Content type: release Language: en Sources: [Yahoo]() Topics: [React](), [Node.js](), [Redux](), [Server-side rendering](), [Caching](), [Front end](), [Web Development](), [Routing (disambiguation)]() Tags: [cache](), [engineering](), [node-js](), [open-source](), [react](), [redux](), [routing](), [server-side-rendering](), [yahoo](), [yahoo-engineering](), [yahoo-mail]() ### AI overview Yahoo describes a rewritten desktop Yahoo Mail experience built with a front-end stack including React, Redux, Node.js, and open-source technologies. The architecture uses proximity-based routing, server-side rendering, isomorphic code, code bundling, caching, modular CSS, and open-source experimentation tools to improve loading, reliability, and payload size. ### Source excerpt By Suhas Sadanandan, Director of Engineering When it comes to performance and reliability, there is perhaps no application where this matters more than with email. Today, we announced a new Yahoo Mail experience for desktop based on a completely rewritten tech stack that embodies these fundamental considerations and more. We built the new Yahoo Mail experience using a best-in-class front-end tech stack with open source technologies including React, Redux, Node.js, react-intl (open-sourced by Yahoo), and others. A high-level architectural diagram of our stack is below. New Yahoo Mail Tech Stack In building our new tech stack, we made use of the most modern tools available in the industry to come up with the best experience for our users by optimizing the following fundamentals: Performance A key feature of the new Yahoo Mail architecture is blazing-fast initial loading (aka, launch). We introduced new network routing which sends users to their nearest geo-located email servers (proximity-based routing). This has resulted in a significant reduction in time to first byte and should be immediately noticeable to our international users in particular. We now do server-side rendering to allow our users to see their mail sooner. This change will be immediately noticeable to our low-bandwidth users. Our application is isomorphic, meaning that the same code runs on the server (using Node.js) and the client. Prior versions of Yahoo Mail had programming logic duplicated on the server and the client because we used PHP on the server and JavaScript on the client. Using efficient bundling strategies (JavaScript code is separated into application, vendor, and lazy loaded bundles) and pushing only the changed bundles during production pushes, we keep the cache hit ratio high. By using react-atomic-css, our homegrown solution for writing modular and scoped CSS in React, we get much better CSS reuse. In prior versions of Yahoo Mail, the need to run various experiments in parallel resu ## Yahoo Mail's Continuous Delivery Pipeline for Frequent, Stable Releases DevFeed: [Yahoo Mail's Continuous Delivery Pipeline for Frequent, Stable Releases]() Original publisher: [Read original article]() Author: mikesefanov Published: 2017-06-27T15:50:35Z Content type: article Language: en Sources: [Yahoo]() Topics: [CI/CD](), [Testing](), [code productivity](), [Front end](), [browsers]() Tags: [browsers](), [ci-cd](), [continuous-delivery](), [continuous-integration](), [developer](), [pipelines](), [testing](), [yahoo](), [yahoo-engineering](), [yahoo-mail]() ### AI overview An engineering article describes Yahoo Mail's continuous delivery pipeline, designed to support frequent product updates while maintaining release stability. It covers extensive unit and integration testing, staged rollout through internal, alpha, beta, and canary environments, and strategies for handling intermittent frontend test failures. ### Source excerpt By Mohit Goenka, Senior Engineering Manager Building the technology powering the best consumer email inbox in the world is no easy task. When you start on such a journey, it is important to consider how to deliver such an experience to the users. After all, any consumer feature we build can only make a difference after it is delivered to everyone via the tech pipeline. As we began building out the new version of Yahoo Mail, we wanted to ensure that our internal developer productivity would not be hindered by how our pipelines work. Keeping this in mind, we identified the following principles as most important while designing the delivery pipeline for the new Yahoo Mail experience: Product updates are pushed at regular intervals Releases are stable Builds are not blocked by irrational test failures Developers are notified of code pushes Hotfixes Rollbacks Heartbeat pushes Product updates are pushed at regular intervals We ensure that our engineers can push any code changes to all Mail users everyday, with the ability to push multiple times a day, if necessary or desired. This is possible because of the time we spent building a solid testing infrastructure, which continues to evolve as we scale to new users and add new features to the product. Every one of our builds runs 10,000+ unit tests and 5,000+ integration tests on various combinations of operating systems and browsers. It is important to push product updates regularly as it allows all our users to get the best Mail experience possible. Releases are stable Every code release starts with the company's internal audience first, where all our employees get to try out the latest changes before they go out to production. This begins with our alpha and beta environments that our Mail engineers use by default. Our build then goes out to the canary environment, which is a small subset of production users, before making it to all users. This gives us the ability to analyze quality metrics on internal and canary servers b ## Open Sourcing Bullet, Yahoo's Forward-Looking Query Engine for Streaming Data DevFeed: [Open Sourcing Bullet, Yahoo's Forward-Looking Query Engine for Streaming Data]() Original publisher: [Read original article]() Author: mikesefanov Published: 2017-06-15T15:55:29Z Content type: release Language: en Sources: [Yahoo]() Topics: [Streaming](), [data](), [real-time](), [GitHub](), [Persistence]() Tags: [big-data](), [data](), [github](), [open-source](), [persistence](), [real-time](), [storm](), [streaming](), [yahoo](), [yahoo-engineering]() ### AI overview Yahoo announces the open sourcing of Bullet, a general-purpose query engine for streaming data. Bullet queries data as it flows through the system, supports filtering, record retrieval, aggregations, and distributions, and does not use a persistence layer. ### Source excerpt By Michael Natkovich, Akshai Sarma, Nathan Speidel, Marcus Svedman, and Cat Utah Big Data is no longer just Apache server logs. Nowadays, the data may be user engagement data, performance metrics, IoT (Internet of Things) data, or something else completely atypical. Regardless of the size of the data, or the type of querying patterns on it (exploratory, ad-hoc, periodic, long-term, etc.), everyone wants queries to be as fast as possible and cheap to run in terms of resources. Data can be broadly split into two kinds: the streaming (generally real-time) kind or the batched-up-over-a-time-interval (e.g., hourly or daily) kind. The batch version is typically easier to query since it is stored somewhere like a data warehouse that has nice SQL-like interfaces or an easy to use UI provided by tools such as Tableau, Looker, or Superset. Running arbitrary queries on streaming data quickly and cheaply though, is generally much harder... until now. Today, we are pleased to share our newly open sourced, forward-looking general purpose query engine, called Bullet, with the community on GitHub. With Bullet, you can: Powerful and nested filtering Fetching raw data records Aggregating data using Group Bys (Sum, Count, Average, etc.), Count Distincts, Top Ks Getting distributions of fields like Percentiles or Frequency histograms One of the key differences between how Bullet queries data and the standard querying paradigm is that Bullet does not store any data. In most other systems where you have a persistence layer (including in-memory storage), you are doing a look-back when you query the layer. Instead, Bullet operates on data flowing through the system after the query is started - it's a look-forward system that doesn't need persistence. On a real-time data stream, this means that Bullet is querying data after the query is submitted. This also means that Bullet does not query any data that has already passed through the stream. The fact that Bullet does not rely on a persistence ## Open Sourcing Daytona: A Framework For Automated and Application-agnostic Performance Analysis DevFeed: [Open Sourcing Daytona: A Framework For Automated and Application-agnostic Performance Analysis]() Original publisher: [Read original article]() Author: mikesefanov Published: 2017-05-23T16:00:06Z Content type: release Language: en Sources: [Yahoo]() Topics: [Testing](), [benchmarking](), [Framework](), [Open Source](), [Tool](), [ui](), [Command-line interface](), [CI/CD](), [Cloud](), [on-prem]() Tags: [architecture](), [ci-cd](), [cloud](), [cloud-services](), [command-line](), [data](), [framework](), [metrics](), [on-prem](), [open-source](), [performance](), [performance-analysis](), [performance-testing](), [systems-engineering](), [tool](), [ui](), [yahoo](), [yahoo-engineering]() ### AI overview Yahoo presents Daytona as an open-source, application-agnostic framework for automated performance testing and analysis. It provides repeatable test execution, standardized reporting, profiling, a unified interface, command-line script support, scheduling, CI/CD integration, and deployment on-premises or in the cloud. ### Source excerpt By Sapan Panigrahi and Deepesh Mittal Today, we are pleased to offer Daytona, an open-source framework for automated performance testing and analysis, to the community. Daytona is an application-agnostic framework to conduct integrated performance testing and analysis with repeatable test execution, standardized reporting, and built-in profiling support. Daytona gives you the capability to build a customized test harness in a single, unified framework to test and analyze the performance of any application. You'll get easy repeatability, consistent reporting, and the ability to capture trends. Daytona's UI accepts a performance testing script that can run on a command line. This includes websites, databases, networks, or any workload you need to test and tune for performance. You can submit tests to the scheduler queue from the Daytona UI or from your CI/CD tool. You can deploy Daytona as a hosted service in your on-prem environment or on the public cloud of your choice. In fact, you can even host test harnesses for multiple applications with a single centralized service so that developers, architects, and systems engineers from different parts of your organization can work together on a unified view and manage your performance analysis on a continuous basis. Daytona's differentiation lies in its ability to aggregate and present essential aspects of application, system, and hardware performance metrics with a simple and unified user interface. This helps you maintain your focus on performance analysis without changing context across various sources and formats of data. The overall goal of performance analysis is to find ways of maximizing application throughput with minimum hardware resource and the best user experience. Metrics and insights from Daytona help achieve this objective. Prior to Daytona, we created multiple, heterogenous performance tools to meet the specific needs of various applications. This meant that we often stored test results inconsistently, maki ## Email providers in Norway DevFeed: [Email providers in Norway]() Original publisher: [Read original article]() Author: Andersos Published: 2014-11-21T18:00:00Z Content type: article Language: no Sources: [Finn.no]() Topics: [email](), [data](), [Database](), [Google](), [Microsoft]() Tags: [data](), [database](), [email](), [google](), [microsoft](), [norway](), [providers](), [yahoo]() ### AI overview The article analyzes approximately 4 million unverified email addresses retrieved on June 6, 2014, to estimate email-provider usage in Norway. Microsoft accounts for 33.57%, Google 15.32%, Telenor 12.53%, and Yahoo 4.31% of the data. ### Source excerpt It all started with a simple tweet: Er det noen som har noe norsk statistikk på bruk av e-post (gmail vs. outlook vs. online vs. yahoo osv)? F.eks @labs_finn_no eller @NRKbeta? -- Håvard Bergersen (@haavardb) March 7, 2014 "Does anyone have any Norwegian statistics on the use of email (Gmail vs. Outlook vs. Online vs. Yahoo etc.)? Eg @labs_finn_no or @nrkbeta." We have access to the data so if this will help someone why not post it. We have around 4 million email addresses in a database. These emails are not verified. The data was retrieved 2014-06-06. To answer the question "Gmail vs. Outlook vs. Online vs. Yahoo etc." we would say: Microsoft 33,57% Google 15,32% Telenor 12,53% Yahoo 4,31% The lists under shows the domain, number registered and percent of total. At the end is the table of the more popular email service providers (this list is cut off at 2500). Watch this space in the future if this is information that interests you. Popular services: Microsoft 33,57% (sum of hotmail, live, msn and outlook) hotmail.com (1106084 - 28.06%) live.no (96052 - 2.44%) hotmail.no (67602 - 1.71%) msn.com (29675 - 0.75%) live.com (15014 - 0.38%) outlook.com (9142 - 0.23%) Google 15,32% (sum of gmail and googlemail) gmail.com (599293 - 15.20%) gmail.no (2982 - 0.08%) googlemail.com (1766 - 0.04%) Telenor 12,53% (sum og online, frisurf, telenor and adsl) online.no (444897 - 11.28%) frisurf.no (41768 - 1.06%) telenor.com (3903 - 0.10%) adsl.no (3643 - 0.09%) Yahoo 4,31% yahoo.no (94029 - 2.39%) yahoo.com (75772 - 1.92%) Universities: stud.ntnu.no (7688 - 0.20%) ntnu.no (1421 - 0.04%) stud.nhh.no (1008 - 0.03%) student.bi.no (925 - 0.02%) hiof.no (921 - 0.02%) medisin.uio.no (820 - 0.02%) student.sv.uio.no (746 - 0.02%) ifi.uio.no (725 - 0.02%) uit.no (666 - 0.02%) stud.hib.no (557 - 0.01%) studmed.uio.no (522 - 0.01%) umb.no (411 - 0.01%) uus.no (408 - 0.01%) uis.no (407 - 0.01%) Telcos: online.no (444897 - 11.28%) frisurf.no (41768 - 1.06%) telenor.com (3903 - 0.10%) adsl.no (36