# 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. ## Chrome extensions with 13.4 million installs caught hijacking searches DevFeed: [Chrome extensions with 13.4 million installs caught hijacking searches]() Original publisher: [Read original article]() Author: Bill Toulas Published: 2026-10-29T16:10:31Z Content type: news Language: en Sources: [BleepingComputer]() Topics: [Chrome extension](), [Google Chrome]() Tags: [ad-fraud](), [add-ons](), [advertising](), [ai-search](), [bing](), [browser-extension](), [campaign](), [chrome](), [chrome-extension](), [code](), [computer-help](), [computer-security](), [computers](), [extensions](), [fraud](), [google-chrome](), [hijack](), [hijacking](), [infosec](), [infosec-computer-security](), [installations](), [linux](), [mac](), [malicious](), [malvertising](), [malware](), [malware-removal](), [revenue](), [search](), [search-hijacker](), [security](), [servers](), [spyware](), [support](), [tech-support](), [technical-support](), [tracking](), [users](), [virus](), [virus-removal](), [windows](), [yahoo]() ### AI overview Socket's report identifies 319 Chrome extensions with a combined 13.4 million reported installations that redirect searches through operator-controlled proxy servers to Bing or Yahoo, generating partner referral revenue. The extensions pose a broader risk because operators can change destinations without updating the add-ons; the report describes identical searches reaching different sites and warns they could be redirected to phishing pages or malicious downloads. Many extensions use Chrome's `chrome_settings_overrides` setting and require little code. The excerpt says most had been removed from the Chrome Web Store when the report was published, while new ones continued to appear. Socket recommends uninstalling listed extensions, running a full antivirus scan, and avoiding unnecessary add-ons from unknown publishers. ### Source excerpt A massive search-hijacking campaign involving 319 Chrome extensions with a combined 13.4 million reported installations redirected users' searches through tracking servers to generate advertising revenue from Bing and Yahoo. [...] ## Manage subscribers with Resend Audiences DevFeed: [Manage subscribers with Resend Audiences]() Original publisher: [Read original article]() Author: Bu Kinoshita Published: 2024-01-16T00:00:00Z Content type: release Language: en Sources: [Resend]() Topics: [self-service]() Tags: [api](), [broadcast](), [create](), [csv](), [email](), [feature](), [free](), [gmail](), [product](), [sdks](), [time](), [upgrade](), [yahoo]() ### AI overview Resend Audiences adds nine API endpoints for managing contacts, including manual and CSV imports and SDK-based creation. The feature integrates with Broadcasts and handles unsubscribe preferences and headers; the free tier supports 1,000 contacts, with paid plans starting at $40 per month for 5,000 contacts. ### Source excerpt Add, update, retrieve, and remove contacts without having to worry about the entire unsubscribe flow. ## Gmail and Yahoo's bulk sending requirements for 2024 DevFeed: [Gmail and Yahoo's bulk sending requirements for 2024]() Original publisher: [Read original article]() Author: Rafael Viana Published: 2024-01-09T00:00:00Z Content type: tutorial Language: en Sources: [Resend]() Topics: [email](), [password reset]() Tags: [email](), [email-clients](), [email-security](), [gmail](), [google](), [guides](), [yahoo]() ### AI overview Gmail and Yahoo's 2024 bulk-sender rules include one-click unsubscribe headers, DMARC alongside SPF and DKIM, and monitoring spam complaints below a 0.3% threshold. The article outlines how senders can implement unsubscribe handling and review authentication and complaint monitoring. ### Source excerpt Starting February 2024, Gmail and Yahoo will be enforcing new bulk sending requirements. ## 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. ## Hadoop Contributors Meetup at Oath DevFeed: [Hadoop Contributors Meetup at Oath]() Original publisher: [Read original article]() Author: amberwilsonla-blog Published: 2018-11-08T19:07:25Z Content type: news Language: en Sources: [Yahoo]() Topics: [Hadoop](), [Developer Events](), [hdfs](), [software-development](), [Tez](), [container]() Tags: [california](), [career](), [cloudera](), [containers](), [contributors](), [hadoop](), [hdfs](), [hiring](), [low-latency](), [meetup](), [microsoft](), [oath](), [recordings](), [slides](), [software-engineering](), [tez](), [twitter](), [yahoo](), [yahoo-engineering](), [youtube]() ### AI overview Oath hosted a day-long Hadoop Contributors Meetup in Sunnyvale, bringing together more than 80 users, contributors, committers, and PMC members. Speakers from Ampool, Cloudera, Hortonworks, Microsoft, Oath, and Twitter presented challenges and solutions across the Hadoop ecosystem. Breakout sessions covered HDFS, Tez, containers, and low-latency processing. The event's presentation recordings are available in a YouTube playlist, with links to slides in each video description. ### Source excerpt yahoodevelopers: By Scott Bush, Director, Hadoop Software Engineering, Oath On Tuesday, September 25, we hosted a special day-long Hadoop Contributors Meetup at our Sunnyvale, California campus. Much of the early Hadoop development work started at Yahoo, now part of Oath, and has continued over the past decade. Our campus was the perfect setting for this meetup, as we continue to make Hadoop a priority. More than 80 Hadoop users, contributors, committers, and PMC members gathered to hear talks on key issues facing the Hadoop user community. Speakers from Ampool, Cloudera, Hortonworks, Microsoft, Oath, and Twitter detailed some of the challenges and solutions pertinent to their parts of the Hadoop ecosystem. The talks were followed by a number of parallel, birds of a feather breakout sessions to discuss HDFS, Tez, containers and low latency processing. The day ended with a reception and consensus that the event went well and should be repeated in the near future. Presentation recordings (YouTube playlist) and slides (links included in the video description) are available here: Hadoop {Submarine} Project: Running deep learning workloads on YARN, Wangda Tan, Hortonworks Apache YARN Federation and Tez at Microsoft, Anupam Upadhyay, Adrian Nicoara, Botong Huang "HDFS Scalability and Security", Daryn Sharp, Senior Engineer, Oath The Future of Hadoop in an AI World, Milind Bhandarkar, CEO, Ampool Moving the Oath Grid to Docker, Eric Badger, Software Developer Engineer, Oath Vespa: Open Source Big Data Serving Engine, Jon Bratseth, Distinguished Architect, Oath Containerized Services on Apache Hadoop YARN: Past, Present, and Future, Shane Kumpf, Hortonworks How Twitter Hadoop Chose Google Cloud, Joep Rottinghuis, Lohit VijayaRenu Thank you to all the presenters and the attendees both in person and remote! P.S. We're hiring! Learn more about career opportunities at Oath. ## 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 ## A Peek Behind the Mail Curtain DevFeed: [A Peek Behind the Mail Curtain]() Original publisher: [Read original article]() Author: marcelatoath Published: 2018-05-18T16:19:38Z Content type: tutorial Language: en Sources: [Yahoo]() Topics: [email](), [Server](), [TLS (Transport Layer Security)]() Tags: [aol](), [features](), [imap](), [mail](), [yahoo](), [yahoo-engineering]() ### AI overview Yahoo and AOL Mail let developers retrieve message tags through IMAP: connect to the Yahoo IMAP server, log in, select a folder, search for message UIDs, then fetch X-MSG-DECOS, X-MSG-ID, and X-MSG-THREADID for a UID. The example returns DECOS values and a thread ID; the post says these tags support travel and shopping views and message threading, but does not explain their internal processing. ### 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; ## Achieving Major Stability and Performance Improvements in Yahoo Mail with a Novel Redux Architecture DevFeed: [Achieving Major Stability and Performance Improvements in Yahoo Mail with a Novel Redux Architecture]() Original publisher: [Read original article]() Author: mikesefanov Published: 2018-04-18T14:04:59Z Content type: article Language: en Sources: [Yahoo]() Topics: [Redux](), [React](), [performance-optimization](), [architecture-components]() Tags: [actions](), [also](), [api](), [application](), [apps](), [architecture](), [based](), [best](), [better](), [brand](), [but](), [change](), [developers](), [engineering](), [improvements](), [mail](), [novel](), [open-source](), [performance](), [react](), [redux](), [with](), [yahoo](), [yahoo-engineering](), [yahoo-mail]() ### AI overview Yahoo Mail reports that Redux architecture changes improved stability and performance: stability rose 20% when checking email, 30% when reading, and 20% when sending; page-load performance improved 10%, frame-rendering time 40%, and API calls fell about 20%. Instead of Thunk middleware coupling action creators to the API, action creators dispatch payloads into Redux state for action syncers to handle API requests and responses. Syncers can batch and deduplicate requests and process them when the network is available; Yahoo reports API errors fell 20-30%. Action enhancers add commonly used data to action payloads, reducing the need to pass dispatch-only props through components and, the authors say, improving frame rendering. The excerpt also says this architecture reduced development cycles, without quantifying that effect. ### Source excerpt yahoodevelopers: By Mohit Goenka, Gnanavel Shanmugam, and Lance Welsh At Yahoo Mail, we're constantly striving to upgrade our product experience. We do this not only by adding new features based on our members' feedback, but also by providing the best technical solutions to power the most engaging experiences. As such, we've recently introduced a number of novel and unique revisions to the way in which we use Redux that have resulted in significant stability and performance improvements. Developers may find our methods useful in achieving similar results in their apps. Improvements to product metrics Last year Yahoo Mail implemented a brand new architecture using Redux. Since then, we have transformed the overall architecture to reduce latencies in various operations, reduce JavaScript exceptions, and better synchronized states. As a result, the product is much faster and more stable. Stability improvements: when checking for new emails - 20% when reading emails - 30% when sending emails - 20% Performance improvements: 10% improvement in page load performance 40% improvement in frame rendering time We have also reduced API calls by approximately 20%. How we use Redux in Yahoo Mail Redux architecture is reliant on one large store that represents the application state. In a Redux cycle, action creators dispatch actions to change the state of the store. React Components then respond to those state changes. We've made some modifications on top of this architecture that are atypical in the React-Redux community. For instance, when fetching data over the network, the traditional methodology is to use Thunk middleware. Yahoo Mail fetches data over the network from our API. Thunks would create an unnecessary and undesirable dependency between the action creators and our API. If and when the API changes, the action creators must then also change. To keep these concerns separate we dispatch the action payload from the action creator to store them in the Redux state for later ## Secure Images DevFeed: [Secure Images]() Original publisher: [Read original article]() Author: marcelatoath Published: 2018-03-20T14:54:05Z Content type: release Language: en Sources: [Yahoo]() Topics: [Image]() Tags: [android](), [aol](), [desktop](), [images](), [ios](), [mobile](), [phishing](), [pixels](), [privacy](), [secure-images](), [security](), [yahoo](), [yahoo-engineering]() ### AI overview OATH says Yahoo and AOL mail will serve message images through its secure proxy servers, aiming to improve speed and security, reduce phishing and scam risks, and display inline images without users enabling them manually. The proxy is intended to preserve most image-pixel tracking of delivery and opens, including recording true opens. Senders whose dynamic content depends on recipients' IP-based location are advised to use alternatives that do not rely on IP targeting. The change applies to Yahoo and AOL desktop, iOS, and Android mail apps. ### Source excerpt oath-postmaster: By Marcel Becker The mail team at OATH is busy integrating Yahoo and AOL technology to deliver an even better experience across all our consumer mail products. While privacy and security are top priority for us, we also want to improve the experience and remove unnecessary clutter across all of our products. Starting this week we will be serving images in mails via our own secure proxy servers. This will not only increase speed and security in our own mail products and reduce the risk of phishing and other scams, but it will also mean that our users don't have to fiddle around with those "enable images" settings. Messages and inline images will now just show up as originally intended. We are aware that commercial mail senders are relying on images (so-called pixels) to track delivery and open rates. Our proxy solution will continue to support most of these cases and ensure that true mail opens are recorded. For senders serving dynamic content based on the recipient's location (leveraging standard IP-based browser and app capabilities) we recommend falling back on other tools and technologies which do not rely on IP-based targeting. All of our consumer mail applications (Yahoo and AOL) will benefit from this change. This includes our desktop products as well as our mobile applications across iOS and Android. If you have any feedback or want to discuss those changes with us personally, just send us a note to mail-questions@oath.com. ## Success at Apache: A Newbie's Narrative DevFeed: [Success at Apache: A Newbie's Narrative]() Original publisher: [Read original article]() Author: mikesefanov Published: 2018-02-05T14:43:07Z Content type: article Language: en Sources: [Yahoo]() Topics: [Tez](), [Hadoop](), [Apache Spark]() Tags: [2015](), [2017](), [apache](), [apache-software-foundation](), [asf](), [bug-fixes](), [cluster](), [code](), [community](), [contribution](), [contributor](), [dag](), [data](), [data-pipeline](), [engine](), [execution](), [frameworks](), [grid](), [hadoop](), [hdfs](), [hive](), [oath](), [open-source](), [tez](), [yahoo](), [yahoo-engineering]() ### AI overview Kuhu Shukla recounts joining Yahoo in 2015 and helping migrate its jobs from Apache MapReduce to Tez, a DAG-based engine. She learned the Hadoop ecosystem through project materials, mailing lists, a local cluster, and beginner contributions, then worked with Tez contributors through sync calls and community JIRAs to define and implement progress reporting. At Oath scale, Tez's inherited MapReduce shuffle service became a performance bottleneck, prompting a community effort to build a Tez-specific handler. After six months, the feature reached sandbox clusters; subsequent rollout and issue fixing helped complete the Tez migration and deploy the handler to research clusters. The account emphasizes shared ownership, cross-project collaboration with Hive and Pig, and the practical challenges of debugging and design. It reports roughly 100 million Tez DAGs and 50 billion tasks across nearly 38,000 nodes as of the article's timeframe. ### 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 app](), [software-development](), [Front end](), [Page Speed Optimization]() Tags: [browser](), [bundlers](), [config](), [css](), [dependency](), [dependency-graph](), [developers](), [javascript](), [loading](), [module](), [modules](), [nodejs](), [oath](), [open-source](), [overhead](), [plugin](), [plugins](), [web-app](), [webpack](), [yahoo](), [yahoo-engineering](), [yahoo-mail]() ### AI overview Yahoo Mail's webpack migration reduced development rebuild waits from 30-60 seconds to 5 seconds, moved JavaScript bundle generation from runtime to build time to reduce bundle-fetch failures, and cut payload by about 75 KB gzipped. The team used Grunt to keep webpack running and pass environment-specific settings, including source maps, HMR, and uglification; tuned UglifyJS options saved about 10 KB. They selected existing plugins where suitable and built a custom plugin and loader for Atomic CSS, including only styles in the dependency chain. Reported outcomes also include a 50% reduction in server-side render time and a 10% improvement in launch performance measured by above-the-fold render time. These are Yahoo Mail's reported results, not guarantees for other apps. ### 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: article Language: en Sources: [Yahoo]() Topics: [performance-engineering](), [Front end](), [React](), [Production Engineering](), [CI/CD](), [email](), [Cache]() Tags: [email](), [engineering](), [experience](), [fast](), [front-end](), [javascript](), [mail](), [node-js](), [open-source](), [performance](), [react](), [redux](), [reliability](), [rendering](), [stack](), [tech](), [tech-stack](), [yahoo](), [yahoo-engineering](), [yahoo-mail]() ### AI overview Yahoo Mail's rewritten desktop stack combines React, Redux, and Node.js with proximity-based routing and server-side rendering to speed initial loading, particularly for international and low-bandwidth users. Isomorphic code replaces duplicated PHP and JavaScript logic; split bundles, selective updates, and reusable CSS help maintain cache hits and reduce the JavaScript and CSS footprint by about 50% versus the previous desktop version. The text also reports faster search and message reading, lower browser memory use, and a 99.99% success rate across core flows over several billion daily user actions. Independently deployable components and continuous delivery support daily or more frequent releases. Yahoo says the experience includes six enhanced visual themes and support for assistive technologies, including screen readers. Mendel is open sourced; react-atomic-css and lazy-component were described as planned open-source releases. ### 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 ## Speed and Stability: Yahoo Mail's Forward-Thinking Continuous Integration and Delivery Pipeline DevFeed: [Speed and Stability: Yahoo Mail's Forward-Thinking Continuous Integration and Delivery Pipeline]() Original publisher: [Read original article]() Author: mikesefanov Published: 2017-06-27T15:50:35Z Content type: article Language: en Sources: [Yahoo]() Topics: [CI/CD Pipeline](), [CI/CD](), [Continuous Delivery (CD)](), [Software Testing](), [Deployment Strategies](), [progressive delivery](), [developer-productivity](), [Developer experience](), [Continuous integration](), [Integration testing](), [browser]() Tags: [browsers](), [build](), [canary](), [ci-cd](), [continuous](), [continuous-delivery](), [continuous-integration](), [delivery](), [developer](), [developer-productivity](), [developers](), [email](), [engineering](), [engineering-manager](), [environments](), [everyday](), [integration](), [mail](), [pipeline](), [speed](), [yahoo](), [yahoo-engineering](), [yahoo-mail]() ### AI overview Yahoo Mail's pipeline supports frequent releases while managing production risk through staged rollout, test recovery, and rapid remediation. Builds run more than 10,000 unit tests and 5,000 integration tests across operating systems and browsers. Releases progress through internal alpha and beta environments, then a production canary, before reaching all users; quality metrics are reviewed along the way. If browser tests fail intermittently, the pipeline records build metadata and reruns only failed tests, while the failures are analyzed to improve test stability. Developers receive email updates as their code moves through each environment. Critical production bugs can be addressed with hotfixes; rollbacks deploy a previously released stable bundle, with versions and change logs maintained. Heartbeat pushes prompt users to refresh when an important update should be adopted. The excerpt describes these mechanisms but does not detail the listed principle about build-blocking test failures beyond the rerun strategy. ### 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: [Software Testing](), [Benchmark](), [Framework](), [Open Source](), [Tool](), [User Interfaces](), [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 ## How robots.txt rules can restrict competing search engines and web archives DevFeed: [How robots.txt rules can restrict competing search engines and web archives]() Original publisher: [Read original article]() Published: 2015-05-27T00:00:00Z Content type: opinion Language: en Sources: [Danluu]() Topics: [Search engine optimization (SEO)](), [search-engines](), [DuckDuckGo](), [Google Search]() Tags: [ban](), [google](), [googlebot](), [robots-txt](), [search-engine](), [search-engines](), [yahoo]() ### AI overview The article discusses how robots.txt rules at Bell Labs and other websites can block the Internet Archive and competing search engine crawlers. It argues that blocking non-Google bots can make it harder for alternative search engines to compete and can unintentionally prevent archiving. The author also notes that archive.org and some search engines later began ignoring such blocks. ### Source excerpt TIL that Bell Labs and a whole lot of other websites block archive.org, not to mention most search engines. Turns out I have a broken website link in a GitHub repo, caused by the deletion of an old webpage. When I tried to pull the original from archive.org, I found that it's not available because Bell Labs blocks the archive.org crawler in their robots.txt: User-agent: Googlebot User-agent: msnbot User-agent: LSgsa-crawler Disallow: /RealAudio/ Disallow: /bl-traces/ Disallow: /fast-os/ Disallow: /hidden/ Disallow: /historic/ Disallow: /incoming/ Disallow: /inferno/ Disallow: /magic/ Disallow: /netlib.depend/ Disallow: /netlib/ Disallow: /p9trace/ Disallow: /plan9/sources/ Disallow: /sources/ Disallow: /tmp/ Disallow: /tripwire/ Visit-time: 0700-1200 Request-rate: 1/5 Crawl-delay: 5 User-agent: * Disallow: / In fact, Bell Labs not only blocks the Internet Archiver bot, it blocks all bots except for Googlebot, msnbot, and their own corporate bot. And msnbot was superseded by bingbot five years ago! A quick search using a term that's only found at Bell Labs1, e.g., "This is a start at making available some of the material from the Tenth Edition Research Unix manual.", reveals that bing indexes the page; either bingbot follows some msnbot rules, or that msnbot still runs independently and indexes sites like Bell Labs, which ban bingbot but not msnbot. Luckily, in this case, a lot of search engines (like Yahoo and DDG) use Bing results, so Bell Labs hasn't disappeared from the non-Google internet, but you're out of luck if you're one of the 55% of Russians who use yandex. And all that is a relatively good case, where one non-Google crawler is allowed to operate. It's not uncommon to see robots.txt files that ban everything but Googlebot. Running a competing search engine and preventing a Google monopoly is hard enough without having sites ban non-Google bots. We don't need to make it even harder, nor do we need to accidentally2 ban the Internet Archive bot. P.S. While y ## What you need to know about April 7 and your security on the web. DevFeed: [What you need to know about April 7 and your security on the web.]() Original publisher: [Read original article]() Author: Map Published: 2014-04-08T20:55:56Z Content type: article Language: en Sources: [Craig Kerstiens]() Topics: [Security](), [network security]() Tags: [amazon-com](), [data](), [developers](), [external](), [netflix](), [passwords](), [security](), [security-vulnerabilities](), [sites](), [technology](), [vulnerability](), [websites](), [yahoo](), [yahoo-mail]() ### AI overview The vulnerability reportedly let outsiders obtain data from affected websites, and the excerpt says it was easy to exploit and had existed for two years. Site operators first needed to update vulnerable systems; users were advised to avoid logging into important accounts until each site was confirmed safe, then change passwords for accounts used in the prior two years. The author cautions that this is high-level guidance, not expert security analysis. ### Source excerpt Yahoo Amazon.com Netflix Various banks Many more If you're interested in more technical details you can follow along or on the Heroku blog. The short of it is you, yes you as in everyone, should rotate your passwords once all websites are safe. For further details please continue reading. What does the vulnerability mean In this case it allowed an external party to acquire a moderate amount of data from some computer running your website. Extremely clear examples (such as shown on the right) highlight an example of random third parties easily acquiring most recently logged in Yahoo mail usernames and passwords. The first step The first step in resolving this is actually not a step required by you at all, unless you're running a production website online. The first step requires the developers running the site to update their site so they are no longer vulnerable. This as available to happen as early as April 7, and many major sites were fully updated and again safe as of April 8. Still area for concern With security vulnerabilities there are two key things to consider. First is the vulnerability itself, second is whether its therotical or can be simply acted upon. Yes, there's a range here. One of the most unfortunate pieces from talking to those that know about security is this was extremely trivial to act upon. This is made even worse in that this vulnerability has existed for 2 years without many knowing about it, meaning people have had an ability to snoop and collect parts of your data for two years What to do? First things first, be extremely cautious with any major website you connect with anything important. Any account that you have a password and you care about the account you should cease logging into it until you know its safe. As of the morning of April 8 here is a list of sites that were safe and ones that were vulnerable. You can check any site today here. Once it's clear that a site you know is now updated and safe either via that list of the latter ## Yahoo-Flavored Hadoop on GitHub DevFeed: [Yahoo-Flavored Hadoop on GitHub]() Original publisher: [Read original article]() Author: PJ Hyett Published: 2009-06-11T05:41:23Z Content type: news Language: en Sources: [GitHub Blog]() Topics: [Hadoop](), [GitHub]() Tags: [github](), [hadoop](), [news-insights](), [the-library](), [yahoo]() ### AI overview Yahoo announced that its Hadoop distribution is hosted on GitHub. ### Source excerpt Yahoo's openness continues today with their announcement of their Hadoop distribution being hosted right here on GitHub: http://github.com/yahoo/hadoop. p=. Read all about it on Yahoo's Developer Blog.