# web browser A web browser is a program that retrieves and displays web pages, using a rendering engine to display them. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## OpenTrailPaper transforms LILYGO T5 E-Paper S3 Pro devkit into a DIY e-paper bike computer DevFeed: [OpenTrailPaper transforms LILYGO T5 E-Paper S3 Pro devkit into a DIY e-paper bike computer]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-05T08:01:22Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Embedded Systems](), [ESP32-S3](), [Open Source](), [Android](), [iOS](), [Bluetooth](), [ESP-IDF](), [GitHub](), [JavaScript](), [Python](), [web browser]() Tags: [android](), [bluetooth](), [browser](), [core](), [display](), [diy](), [e-ink](), [e-paper](), [epaper](), [esp-idf](), [esp32](), [esp32-s3](), [espressif](), [firmware](), [github](), [gps](), [hardware](), [ios](), [javascript](), [lilygo](), [lora](), [open-source](), [python]() ### AI overview OpenTrailPaper is an open-source DIY e-paper bike computer project for the LILYGO T5 E-Paper S3 Pro, using ESP32-S3 firmware alongside Android and iOS companion apps. It supports ride data, offline maps, GPX routes, FIT file recording, and Bluetooth sensor connections. ### Source excerpt OpenTrailPaper is an open-source, DIY e-paper bike computer project comprised of firmware for the ESP32-S3-based T5 E-Paper S3 Pro devkit and Android and iOS companion apps for maps, routes, and settings. It shows ride data and offline maps, follows standard GPX (GPS Exchange Format) routes, records FIT (Flexible and Interoperable Data Transfer used in Garmin devices) files, and connects to Bluetooth (and soon ANT/ANT+) heart rate, power, and cadence sensors. Before looking into the project's details, let's check out the LILYGO T5 E-Paper S3 Pro specifications: ESP32-S3-WROOM-1 wireless module SoC - ESP32-S3N16R8 dual-core Tensilica LX7 microcontroller @ up to 240 MHz with 2.4 GHz 802.11n WiFi 4 and Bluetooth 5.0 LE connectivity Memory - 8MB PSRAM Storage - 16MB SPI flash PCB antenna Storage - MicroSD card slot Display - 4.7-inch e-Paper display with 960x540 resolution, 16 shades of gray, capacitive touch (GT911); ED047TC1 drive IC Wireless 2.4 GHz 802.11n [...] The post OpenTrailPaper transforms LILYGO T5 E-Paper S3 Pro devkit into a DIY e-paper bike computer appeared first on CNX Software - Embedded Systems News. ## Companion app: Changing support for Apple platforms DevFeed: [Companion app: Changing support for Apple platforms]() Original publisher: [Read original article]() Author: Bruno Pantaleão Published: 2026-07-07T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [iOS](), [macOS](), [watchOS](), [web browser](), [App](), [GitHub](), [User experience (UX)]() Tags: [announcements](), [app](), [apple](), [github](), [ios](), [macos](), [performance](), [platforms](), [update](), [ux](), [watchos](), [web-browser]() ### AI overview Home Assistant is changing Apple platform support for its Companion app. Version 2026.7.1 will be the final release supporting iOS 15, watchOS 8, and macOS 11; beginning with version 2026.8.0, the minimum versions will be iOS 16.4, watchOS 9, and macOS 12. The change will enable improved UX, stability, performance, and newer features, while older devices can still use the web frontend. ### Source excerpt We're updating which Apple platforms the Home Assistant Companion app supports, and because transparency is core to how we work, we want to be upfront about what's changing. Starting with version 2026.8.0 of the Companion app, we will no longer support iOS 15, watchOS 8, or macOS 11. The last supported version for these platforms will be 2026.7.1. Here's everything you need to know: Why we're making the change At Home Assistant, we're committed to helping you use your devices for the long haul. We know your hardware is something you rely on every day, which is why we try to keep the Companion app running on older devices for as long as possible. However, supporting older OS versions indefinitely comes at a cost, limiting our ability to adapt to modern technology. From September this year, Apple's developer tools will officially stop supporting watchOS 8 and macOS 11, making it technically difficult for us to keep building for them. With less than 1% of our users currently running these older OS versions, this update allows us to future-proof the Companion app for the vast majority of our community. By focusing our efforts on current operating system versions, we can keep our codebase maintainable for the long term. This shift removes some long-standing constraints, since older OS versions had been limiting our ability to make UX, stability, and performance improvements, including adding features such as Apple Watch complications and more advanced widgets. What this means for you A recap of what's changing: The last Companion app update for these platforms will be version 2026.7.1. After version 2026.7.1, the minimum supported versions for the Companion app will be iOS 16.4, watchOS 9, and macOS 12. Importantly, this doesn't mean your older iOS devices will become unusable. You can still control your home using the Home Assistant frontend in your device's web browser, which remains fully supported and receives regular monthly updates. The last compatible Companion ap ## \[Pentesting\] HTTP auth, part II: digest DevFeed: [\[Pentesting\] HTTP auth, part II: digest]() Original publisher: [Read original article]() Published: 2025-11-20T23:00:00Z Content type: article Language: en Sources: [Dennis Yurichev]() Topics: [HTTP](), [passwords](), [TLS (Transport Layer Security)](), [web browser]() Tags: [apache](), [attacks](), [browser](), [code](), [compatibility](), [crack](), [http](), [legacy](), [mitm](), [password](), [protection](), [protocol](), [server](), [tls](), [upgrade]() ### AI overview The article examines HTTP Digest Authentication, including how the server and browser exchange hashed credentials, how the exchange resists password interception and replay attacks, and how attackers can attempt to crack MD5-based exchanges with hashcat. It notes that Apache 2.4.63 still uses MD5 and recommends upgrading HTTP authentication to TLS. ### Source excerpt [Pentesting] HTTP auth, part II: digest ## Fix "This video format is not supported" on YouTube TV DevFeed: [Fix "This video format is not supported" on YouTube TV]() Original publisher: [Read original article]() Author: David Walsh Published: 2025-11-17T23:47:34Z Content type: tutorial Language: en Sources: [David Walsh]() Topics: [browser](), [web browser]() Tags: [browser](), [drm](), [error](), [uncategorized]() ### AI overview A troubleshooting guide explains how to resolve YouTube TV's "This video format is not supported" error by enabling Widevine DRM in the browser settings and restarting the browser. ### Source excerpt Setting up a new computer is bliss -- no old, unused apps and the machine performs much better than the previous. Unfortunately, you may encounter new problems based on the new hardware. One such issue I encountered with my new MacBook was a "This video format is not supported" message when I went to YouTube [...] The post Fix "This video format is not supported" on YouTube TV appeared first on David Walsh Blog. ## Starting Your First Discord Server DevFeed: [Starting Your First Discord Server]() Original publisher: [Read original article]() Author: Cody Sanchez Published: 2025-08-27T00:00:00Z Content type: tutorial Language: en Sources: [Discord Blog]() Topics: [Discord](), [servers](), [browser](), [Template](), [web browser]() Tags: [app](), [browser](), [channel](), [discord](), [games](), [play](), [server](), [talk](), [voice]() ### AI overview A beginner-friendly guide to creating a Discord server, explaining how servers organize conversations and how to set one up for friends, gaming, and other shared interests. ### Source excerpt Looking to create a new Discord server for the first time? How do you invite your friends to it? What even IS a text or voice channel in Discord? Follow along as we help you start up a new place to talk and play games with your friends. ## We now support VLMs in smolagents! DevFeed: [We now support VLMs in smolagents!]() Original publisher: [Read original article]() Author: Aymeric Roucher; merve; Albert Villanova del Moral Published: 2025-01-24T00:00:00Z Content type: article Language: en Sources: [Hugging Face - Blog]() Topics: [smolagents](), [Artificial Intelligence](), [AI Development](), [web browser](), [document ai]() Tags: [agentic](), [agents](), [artificial-intelligence](), [document-ai](), [multimodal](), [open-source](), [smolagents](), [vision](), [vlm](), [vlms](), [web-browser]() ### AI overview smolagents now supports vision-language models natively in agentic pipelines. The article explains how agents can receive images at initialization or dynamically through memory callbacks, enabling visual web browsing, Document AI workflows, and processing long PDFs with visual elements. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## How Chrome doubled its Speedometer scores on Android DevFeed: [How Chrome doubled its Speedometer scores on Android]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-12-04T14:00:00Z Content type: article Language: en Sources: [Chromium Blog]() Topics: [Chrome](), [Android](), [Benchmark](), [V8](), [JavaScript](), [web browser](), [CSS](), [HTML]() Tags: [android](), [benchmark](), [chrome](), [css](), [html](), [javascript](), [none](), [performance](), [the-fast-and-the-curious](), [v8]() ### AI overview The article explains how Chrome more than doubled Speedometer 2.1 scores on many Android devices since Chrome M112. It attributes the gains to build optimizations, V8 and Blink improvements, and closer coordination with Android operating-system scheduling and SoC partners. ### Source excerpt Today's The Fast and the Curious post covers how Chrome achieved best-in-class Speedometer scores on mobile devices, resulting in faster and smoother web experiences for Android users. Chrome has always been about speed. Whether it's loading pages quickly, running complex web apps smoothly, or delivering a seamless browsing experience, performance is at the heart of our browser. And we're always looking for ways to make Chrome even faster. Over the last two years, we have been hard at work on a number of performance improvements for Android devices. We're excited to share some of the progress we've made. Speedometer on Android One of the key metrics we use to track Chrome's performance is the Speedometer benchmark. This benchmark is developed in collaboration with other major web browser engines and measures how quickly Chrome can complete interactions with web pages, including parsing/rendering HTML or CSS and running JavaScript. Since the release of Chrome M112, we've seen a significant increase in Speedometer 2.1 scores on Android devices [1]. In fact, on many devices, scores more than doubled, with the newest Snapdragon® 8 Elite Mobile Platform setting new records for Speedometer performance on mobile devices! These huge accomplishments are a testament to the work not only of the Chrome and Android teams, but also our silicon and SoC partners. Since Chrome M112, Speedometer 2.1 scores have more than doubled on many Android devices. [1] How Did We Do It? The improvements resulted from several changes, including: Build optimizations: We've made a number of changes to the way Chrome is built, which has resulted in faster code execution tuned to modern premium Android devices and SoCs. V8 and Blink improvements: Many improvements to the JavaScript engine (V8) and the rendering engine (Blink) have further boosted performance. Scheduling, OS and SoCs: We worked closely with Android partners to optimize the way Chrome interacts with the operating system and its thread ## Docusaurus 3.4 DevFeed: [Docusaurus 3.4]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2024-05-31T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [configuration](), [Documentation](), [Markdown](), [web browser](), [web applications]() Tags: [announce](), [browser](), [configuration](), [experimental](), [markdown](), [offline](), [release](), [single-page-application]() ### AI overview Docusaurus 3.4 is a minor release that adds predefined tag files, experimental hash-router support for offline browsing, and experimental site-storage configuration to avoid conflicts between sites sharing a domain. It also includes translation additions and Markdown link-resolution fixes. ### Source excerpt We are happy to announce Docusaurus 3.4. ## Hack Day: Food Glorious Food DevFeed: [Hack Day: Food Glorious Food]() Original publisher: [Read original article]() Author: Rasha Ardati Published: 2023-05-31T08:45:02Z Content type: article Language: en Sources: [Guardian]() Topics: [Browser Extension](), [App](), [Artificial Intelligence](), [web browser](), [Image](), [stable-diffusion]() Tags: [ai](), [browser](), [extension](), [hack](), [images](), [stable-diffusion]() ### AI overview The Guardian's first hack day of 2023 focused on food-related ideas and produced more than 22 hacks over two days. Projects included browser extensions, recipe interfaces, a restaurant review mapper, microwave-friendly recipes, and an AI tool that generates recipe-step images using stable diffusion or DALL-E. ### Source excerpt This month, colleagues across the product and engineering department, as well as other parts of the organisation, came together for another exciting hack day For our first hack day of 2023 we kicked off with a delicious theme around 'Food', with a side of the usual 'free-for-all' of course. Hackers were invited to think about all things edible, whether as an app, a new search method for recipes, a meal planner or perhaps a choose your own adventure game where your date is coming for dinner in an hour and a half, and you have decided, perhaps too ambitiously, to cook them an elaborate Ottolenghi recipe from the Guardian archives. We produced and presented over 22 amazing hacks over the two-day event. These included: Migrating our tone/recipes page to our latest rendering tiers, A web browser extension to help users understand cooking language and become better cooks, making Guardian recipes microwave-friendly, a restaurant review mapper, implementing a Guardian app section for food content and a web browser extension to appeal to our tofu-eating readers. Continue reading... ## CVE-2021-0090: Intel Driver & Support Assistant (DSA) Elevation of Privilege (EoP) DevFeed: [CVE-2021-0090: Intel Driver & Support Assistant (DSA) Elevation of Privilege (EoP)]() Original publisher: [Read original article]() Author: bohops Published: 2021-08-07T16:30:24Z Content type: article Language: en Sources: [Bohops]() Topics: [intel](), [Utility Software](), [bug](), [Software](), [Windows](), [Web](), [web browser]() Tags: [browser](), [bug](), [configuration](), [cve](), [driver](), [intel](), [local](), [mount](), [payload](), [software](), [technical](), [uncategorized](), [web](), [windows]() ### AI overview This technical advisory examines a local privilege-escalation vulnerability in Intel Driver & Support Assistant version 20.8.30.6 and likely earlier versions. It describes how an unprivileged user can alter download and data-folder settings and potentially use a reparse point to cause a privileged file-copy operation and execute unintended code. ### Source excerpt TL;DR Intel Driver & Support Assistant (DSA) is a driver and software update utility for Intel components. DSA version 20.8.30.6 (and likely prior) is vulnerable to a local privilege escalation reparse point bug. An unprivileged user has nominal control over configuration settings within the web-based interface. This includes the ability to configure the folder location [...] ## Why SSL scanner results can be misleading for app connections DevFeed: [Why SSL scanner results can be misleading for app connections]() Original publisher: [Read original article]() Author: Question authority Published: 2020-07-01T00:00:00Z Content type: article Language: en Sources: [Signal Blog]() Topics: [SSL](), [certificates](), [web browser](), [public key](), [Firefox](), [Mozilla]() Tags: [browsers](), [certificates](), [mozilla](), [public-key](), [ssl](), [web-browser]() ### AI overview The article explains that SSL scanning utilities often focus on web-browser compatibility and performance, which can make their results misleading for connections made by applications. It also describes how browsers rely on trusted root certificates from certificate authorities to verify website connections. ### Source excerpt Sometimes people dive into Signal's code looking for domain names, and then they send us screenshots asking if they should be concerned: We reply with a short explanation that lays out why there's nothing wrong, but we understand the confusion. Nobody would be excited about getting a grade like this on a homework assignment - and you'd have to stay after class and ask the teacher what the hell a "T" even means on your report about summer vacation ("T"oo cool for school?). Let's take a deeper look at what's going on. Read more... ## A Simple WebRTC Webcam and Video Conferencing Use Case DevFeed: [A Simple WebRTC Webcam and Video Conferencing Use Case]() Original publisher: [Read original article]() Author: espen Published: 2013-11-29T09:03:00Z Content type: article Language: en Sources: [Finn.no]() Topics: [WebRTC](), [webcam](), [web browser](), [web applications]() Tags: [article](), [blog](), [video](), [web-browser](), [webcam](), [webrtc]() ### AI overview The article describes AppearIn, a browser-based video conferencing platform built with WebRTC, and discusses creating a simple webcam-related use case. It notes that implementing WebRTC can be challenging because the specification is still evolving and browser implementations have corner cases and differences. ### Source excerpt There is a Norwegian start-up called AppearIn which enables anyone to do online video conferencing with only a web browser. They utilize WebRTC to empower users to create rooms where they can hang out, do meetings, etc. We had the pleasure of having Ingrid form Appear In over for a visit and she suggested we'd contribute to their blog about use cases for appear in. That's how we became use case #7 on their blog. Naturally this should've been an arduino powered thing with lot's of sophisticated technology, but we decided we'd just get something simple working first and then make it better later on. This is a really exciting platform as it empowers developers to have video/audio communication with little effort. Dealing with WebRTC, which is still a moving specification, can be quite challenging to implement properly. There's numerous corner cases and differences between implementations. Update: Through the wonders of the internet, it turns out that we have brought the webcam thing full circle. A user on Hacker News posted a comment which linked to a wikiepedia article about the first webcam. It turns out the use case for it was exactly the same as we had. ## WebKit for Developers DevFeed: [WebKit for Developers]() Original publisher: [Read original article]() Author: Paul Irish Published: 2013-02-28T10:53:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [WebKit](), [browsers](), [web browser](), [Parsing](), [Web platform](), [Chromium]() Tags: [android](), [apple](), [browser](), [browsers](), [chrome](), [chromium](), [css](), [developers](), [html](), [javascript](), [mac-os](), [parsing](), [safari](), [web](), [web-browser]() ### AI overview This article explains WebKit as an open browser engine and examines how WebKit-based browsers share components while differing across platform-specific ports. It covers parsing, layout, rendering, networking, hardware acceleration, and WebKit's use in Safari, GTK-based environments, and mobile browsers, while preserving a historical snapshot from early 2013. ### Source excerpt Feb 2015: A lot's happened since I wrote this post two years ago. Chrome forked WebKit and started Blink, Opera adopted Chromium, and node-webkit became nw.js. This post describes a complexity of defining WebKit that doesn't exist much anymore; with Chrome's departure the WebKit world is more simple and clear. WebKit is deployed through iOS Safari and Mac Safari, and the active GTK community leverages WebKit inside the GNOME Platform. Some smaller mobile browsers use WebKit, some Chromium, some use forks of either, and many just use the system WebViews that are both powered by up-to-date version of iOS WebKit and Android Chromium. The post below is kept intact and represents a snapshot of history in early 2013, rather than the modern WebKit landscape. For many of us developers, WebKit is a black box. We throw HTML, CSS, JS and a bunch of assets at it, and WebKit, somehow.. magically, gives us a webpage that looks and works well. But in fact, as my colleague Ilya Grigorik puts it... WebKit isn't a black box. It's a white box. And not just that, but an open, white box. So let's take a moment to understand some things: What is WebKit? What isn't WebKit? How is WebKit used by WebKit-based browsers? Why are all WebKits not the same? Now, especially with the news that Opera has moved to WebKit, we have a lot of WebKit browsers out there, but its pretty hard to know what they share and where they part ways. Below we'll hopefully shine some light on this. As a result you'll be able to diagnose browser differences better, report bugs at the right tracker, and understand how to develop against specific browsers more effectively. Standard Web Browser Components Let's lay out a few components of the modern day web browser: Parsing (HTML, XML, CSS, JavaScript) Layout Text and graphics rendering Image decoding GPU interaction Network access Hardware acceleration Which of those are shared in WebKit-based browsers? Pretty much only the first two. The others are handled by individual